Business Partner Replication Introduction Before newly created business partner data from the SAP CRM system

is replicated in the SAP ERP system, you must first execute an initial data transfer. You use the Start Initial Load transaction (transaction code R3AS) to transfer the busi ness partner data to the CRM system. Make the settings described below after you have made the general settings for t he business partner in SAP CRM, as described in SAP Solution Manager, and after you have made the configuration settings. First, here is a brief summary of the concept of the business partner or SD cust omer in SAP ERP: When creating or changing a business partner with the role Sales Prospect or Con tract Partner, you can specify a sample customer (SD customer) in SAP ERP. This creates an SD customer for the business partner with the same number as the busi ness partner. Data is copied from the sample customer (tables KNA1, KNB1, KNVV, KNVP, KNVA, KNVI, KNVD, KNEX, KNVS and KNVL). Name and address data, as well as some additional fields, are transferred from the business partner. If the SD cus tomer already exists, the system only transfers part of the data from the sample customer (only the sales and distribution areas that do not yet exist). If you now connect a CRM system, the central data from the CRM business partner is exchanged with the business partner in SAP ERP, and the CRM-specific data is exchanged with the SD customer. The CRM business partner has the same number as the business partner in SAP ERP and the SD customer. You work mainly with the BUPA_MAIN queue. You only work with the CUSTOMER_MAIN q ueue when you are changing SD customer data, such as sales area data. Control Table Conversion To execute the business partner concept specific to the utilities industry, you must convert the following control tables. Make the following entries (with call indicators set) for the Business Partner o bject in the ERP table COM_BUPA_CALL_FU (transaction SM30): Event Mapping Mapping Mapping Mapping Mapping Inbound Inbound Inbound Inbound Inbound Processing Processing Processing Processing Processing Item Name of Function Module 5000 COM_BUPA_MWX_FILTER_ISU 10000 COM_BUPA_MWX_FILTER_MAIN 50000 COM_BUPA_MWX_MAP_NUMRANGE 100000 COM_BUPA_MWX_MAP_MAIN_CENTRAL 150000 COM_BUPA_MWX_MAP_ISU

ERP Object Inbound ERP Object Outbound

3000000 COM_BUPA_MAIN_INBOUND_ISU 1000000 COM_BUPA_MWX_CREATE_MAIN 100000 COM_BUPA_MWX_BPS_FILL_CENTRAL 150000 COM_BUPA_MWX_BPS_FILL_ISU

Mapping Outbound Processing Mapping Outbound Processing

Delete other entries for this event. Make the following entries (with call indicators set) for the Business Partner o bject in the CRM table CRMC_BUT_CALL_FU (transaction SM30): Event CRM Inbound Processing CRM Inbound Processing CRM Inbound Processing CRM Outbound Processing Item Name of Function Module CRM_BUPA_BDOC_MAP_NUMRANGE BUPA_MWX_BDOC_MAP_MAIN_CENTRAL CRM_BUPA_BDOC_MAP_MAIN BUPA_MWX_BDOC_BPS_FILL_CENTRAL

50000 100000 200000 100000

CRM Outbound Processing ERP Adapter Outbound CRM Inbound BUPA CRM Inbound BUPA CRM Inbound BUPA CRM Inbound BUPA CRM Inbound BUPA CRM Inbound BUPR CRM Inbound BUPR CRM Inbound BUPR CRM Inbound BUPR CRM Outbound BUPA CRM Outbound BUPA CRM Outbound BUPA CRM Outbound BUPA CRM Outbound BUPA CRM Outbound BUPR CRMOU BUPR 1200000 CRMOU BUPR 1300000 CRMOU BUPR 1400000

200000 CRM_BUPA_BDOC_BPS_FILL_DATA 100000 BUPA_MWX_BDOC_UP_CURRSTATE_SET 1000000 BUPA_INBOUNG_MAIN_CENTRAL 1100000 CRM_BUPA_INBOUND_MAIN_MD 1200000 CRM_BUPA_BDOC_MAP_MAIN 1300000 CRMPHA_MWX_BDOC_MAP_PHARMA 1400000 CRM_BUPA_KOREA_INBOUND_MAP 1000000 BUPA_INBOUND_REL_CENTRAL 1100000 CRM_BUPA_INBOUND_REL_MD 1200000 CRM_BUPA_BDOC_MAP_REL 1300000 CRMPHA_MWX_BDOC_MAP_REL_PHARMA 1000000 BUPA_OUTBOUND_BPS_FILL_CENTRA 1200000 CRM_BUPA_OUTB_BPS_FILL_MD 1300000 CRM_BUPA_BDOC_BPS_FILL_DATA 1400000 CRMPHA_MWX_BDOC_BP_FILL_PHARM 1500000 CRM_BUPA_KOREA_OUTBOUND_MAP 1000000 BUPA_OUTBOUND_BPR_FILL_CENTRA CRM_BUPA_OUTB_BPR_FILL_MD CRM_BUPA_BDOC_BPR_FILL_DATA CRMPHA_BR_BDOC_FILL_DATA

In view V_SMOFEVOB, you have to use transaction SM30 to delete the entries for t he following events in SAP CRM: 00001321 CAM_1000 CAM_2000 CAM_3000 Use transaction BF31 (Change Application modules per Publish / Subscribe Interfa ce) to change the function module allocation for the following two Business Tran saction Events (BTE) in SAP ERP: Event Applc. Function Module DE_KTOKD IS-U COM_INTERFACE_DE_KTOKD_ISU 00001321 IS-U ISU_INTERFACE_00001321 Delete all other entries for these two events. Exchanging Roles Sold-to-parties in SAP CRM are replicated as contract partners in the OLTP syste m, and vice versa. The role Installer is not transferred from SAP ERP to the CRM System. Other roles, such as customer-specific roles, are only copied from SAP ERP to SA P CRM if they are created there. Settings for Groupings and Number Ranges To ensure that business partner numbers are identical, you must create an extern al number range with the same area for each internal number range (number range object BU_PARTNER) in the other system. This external number range must then be allocated to a grouping (ERP or CRM table V_TB001; transaction SM30). During the data exchange, the system automatically selects a grouping that is allocated to this number range. Set up the areas in such way, that there is enough space for a long-term operati on. As with settings for the number range, the account group selection takes place w hen creating a business partner in SAP CRM. An external number range (number ran ge object DEBITOR) must exist for the number that is used to create a business p artner in CRM. An account group (ERP table T077D; transaction SE16) must be allo cated to this number range. This account group must also fulfill other requireme nts, such as corresponding to the role in SAP CRM (Sales Prospect or Sold-to-Par ty). If several account groups are available for selection, the group intended f or FI-CA (see table TFK077D) is used. During the initial download, you must temporarily convert all number ranges to e xternal. This makes it possible to create all the business partners with the sam e number. During the delta download the system searches for a grouping that is a

llocated a suitable external number range. Sample Customers in the Delta Upload You can store sample customers in the ERP table TCRMBP_REFCUST (transaction SE16 ). These sample customers are used when creating a business partner in SAP CRM. This means that less data is transferred than when creating an R/3 business part ner (ERP tables KNVD, KNB1, KNEX, KNVS and KNVL; transaction SE16). In table TCRMBP_REFCUST, the system searches generically for a sample customer: First it searches by Category, Grouping, and Type, then by Category and Grouping (with Type = SPACE), then only by Category (with Grouping and Type = SPACE), an d finally with all three key fields as SPACE. Initial Download Before performing the initial download, check whether an SD customer has been cr eated for all business partners in SAP ERP, for which this is desired or necessa ry. (For example, to an SD customer is necessary to use the billing engine in SA P CRM). You should also check whether business partners already exist for all SD custome rs. Business partner creation for SD customers is supported by tools (for exampl e, during the SAP for Utilities implementation). In the scenario described, you must not directly create any SD customers (except sample customers), as you are not replicating anything in SAP CRM. Note Regarding the data exchange of sales areas in delivery Customizing, check in SAP ERP whether the following three entries exist in table CRMINTBAP (transaction S E16) for the table KNVV (transaction SE16). TABNAME BAPISTRNAM KNVV KNVV KNVV BSC_SALESA BSC_SALESA BSC_SALESA INTTABFLD SPART VKORG VTWEG BAPSTRFLD

DIVISION SALES_ORG CHANNEL