How-To Guide for High-Volume. Channel Partner Segmentation Bases. Creation of InfoSets, Data Sources, Attribute List and Report Execution

Transcription

1 How-To Guide for High-Volume Channel Partner Segmentation Bases Creation of InfoSets, Data Sources, Attribute List and Report Execution How-To Guide for High-Volume Channel Page 1 of 12

2 1 Overview Prerequisites InfoSet Creation InfoSet CRM_MKTHV_IS_ACC_OF_CP InfoSet CRM_MKTHV_IS_ACC_OF_CP_D Data Source and Attribute List Creation Data Source Creation Attribute List Creation Creation and Update of Segmentation Bases Page 2 of 12

3 1 Overview This document describes the steps required to create and update segmentation bases for channel partners in the high-volume segmentation scenario. This is similar to the existing report CRM_MKTTG_MGR_GEN_CHM_ACCOF (All Business Partners by Channel Partner) used for classic segmentation. These segmentation bases are required to perform channel partner segmentation where each channel partner uses a unique segmentation basis that contains their end customers. A channel partner is a business partner that is created using the technical role PRMP (Channel Partner). The relationship type between the channel partner and the end customer is CRME02 (Is End Customer of or Has End Customer). A segmentation basis for a channel partner contains all business partners that are related to the channel partner using the CRME02 relationship type. Chapter 2 describes the coding prerequisites. Chapter 3 contains a step-by-step guide to creating InfoSets. Chapter 4 describes the creation of a data source and an attribute list, which are required to execute the generation report explained in chapter 5. Page 3 of 12

4 2 Prerequisites The steps described in this document are only relevant for SAP enhancement package 1 for SAP CRM 7.0 or a higher release in which the business function CRM_MKT_HVS (High- Volume Marketing) is activated Additionally, SAP Note must be implemented or the following support packages must be deployed to the SAP CRM System: Support Package 08 for SAP Enhancement Package 1 for SAP CRM 7.0 or Support Package 03 for SAP Enhancement Package 2 for SAP CRM 7.0 Page 4 of 12

5 3 InfoSet Creation The steps described in this chapter are only necessary if the enhancement was implemented using SAP Note If the support packages were applied to the CRM system, the InfoSets are already installed. To perform segmentation for the channel partner relationship, you must first upload the data to the TREX used in the segmentation application. This requires you to create an InfoSet that retrieves this information. This chapter describes the creation of two separate InfoSets for the initial load and delta load of the business partner data to the TREX system. 3.1 InfoSet CRM_MKTHV_IS_ACC_OF_CP The following steps describe the creation of the initial load InfoSet CRM_MKTHV_IS_ACC_OF_CP. Call transaction SQ02 and create a new InfoSet CRM_MKTHV_IS_ACC_OF_CP: Make sure that you select the checkbox no automatic text recognition. Page 5 of 12

6 Define an alias table using the table BUT000: button and enter the alias BUT000_REL for Add the tables BUT050 and BUT000_REL to the InfoSet using the button. Join the tables BUT000, BUT050 and BUT000_REL as shown in the following screenshot: Select Create empty field groups: Page 6 of 12

7 Adjust the field groups: Add the field BUT000-PARTNER to field group 01. Add the field BUT000_REL- PARTNER_GUID to field group 02: Use the button and adjust the code section Record Processing: by adding CHECK but050-reltyp EQ 'CRME02'. When asked for a package when saving the InfoSet, choose the package CRM_MKTTG. Generate the InfoSet using the button. Page 7 of 12

8 Set the role assignment to CRM_MKTHV: 3.2 InfoSet CRM_MKTHV_IS_ACC_OF_CP_D The following steps describe the creation of the delta load InfoSet CRM_MKTHV_IS_ACC_OF_CP_D. This is only required if you are using the delta load function. Since the creation of the delta InfoSet is similar to the initial-load InfoSet described in chapter 3.1, this section only describes the differences. Choose CRM_MKTHV_IS_ACC_OF_CP_D as InfoSet name. In addition to the tables BUT000, BUT050 and BUT000_REL, the table CRMD_MKTHV_DTA must also be included in the join with the field BUT000_REL-PARTNER_GUID against CRMD_MKTHV_DTA-OBJ_GUID: Page 8 of 12

9 Adjust the field groups: Add the following fields to the field groups: Assign the user group CRM_MKTHV_D to the InfoSet: Page 9 of 12

10 4 Data Source and Attribute List Creation Segmentation bases in the high-volume scenario are segments with selection criteria that are evaluated at runtime (for example: count of a segment). Segmentation bases in the classic scenario are persisted lists of business partners that are comparable to target groups. To create the high-volume segmentation bases for the channel partners (as described in chapter 5), it is therefore necessary to have corresponding data sources and attribute lists. 4.1 Data Source Creation Call transaction CRMD_MKTDS and create a new data source for high-volume segmentation using the InfoSets described in chapter 3: 4.2 Attribute List Creation Call transaction CRMD_MKTDS and create a new attribute list for a high-volume usage: Select the checkbox for the Business Partner Number attribute (field BUT000-PARTNER). Page 10 of 12

11 5 Creation and Update of Segmentation Bases Call transaction SA38 and execute report CRM_MKTTG_MGR_GEN_CHM_HV. Select the Create Segmentation Basis checkbox to display the input fields. Use the value help to select the attribute list created in chapter 4.2. Choose the attribute Business Partner Number as Attribute for Channel Partner using the value help. Select the Usage for the segmentation bases using the list box. During execution, the report performs the following steps: Find the top-level segmentation basis for the channel scenario and the selected usage: o If a top-level segmentation basis does not exist, it is created automatically. o If a top-level segmentation basis exists, it is updated. Note: each usage has its own top-level segmentation basis. Note: the top-level segmentation basis is created with the same description as the top-level channel partner segmentation basis in the classic segmentation scenario ( CHM DTG 2003 CRM4.0 SP02 ). The description can be changed without affecting its purpose as top-level segmentation basis for the channel scenario. Technical information: the top-level segmentation basis is identified using the field SEL_ID in the database table CRMD_MKTTG_SET_M. The identifier for the channel scenario is hardcoded in the attribute GC_CHM_DTG_SEL_ID of class CL_CRM_CHM_PDM_UTIL. Determination of all business partners with the role Channel Partner (PRMP). The corresponding segmentation basis is determined for each channel partner: o If a segmentation basis for the channel partner exists, the selection criteria for the corresponding segment are updated and all previous selection criteria are discarded. o If no segmentation basis for the channel partner exists, it is created. Note: The description of the individual segmentation bases is the business partner number of the corresponding channel partner, similar to the classic segmentation scenario. Page 11 of 12

12 Finally, the actual count of the segmentation basis is updated. It is recommended to execute the report in batch if the system contains a large amount of channel partners to avoid a time out of the dialog workprocess. Page 12 of 12