Transferring Master Data from SAP CRM to SAP ECC 

Use

You use this function to transfer master data from SAP CRM.

Activities

       1.      Start transaction R3AS in SAP CRM and use the object name. Condition tables have object names, each beginning with UPL_CRM. These objects are defined as upload objects.

Start the program individually for each of these objects.

The program carries out the following steps:

       2.      The data is transferred to SAP ECC and is saved there.

Records that have already been loaded to SAP ECC, but which are now no longer sent, are deleted.

Only some of the condition tables have upload objects. You can create new objects with transaction R3AC5.

       3.      Choose CONDITIONS as the object class and the name of the new download object as the object name.

       4.      Choose a relevant messaging BDoc as a linked BDoc (for example, CND_MAST_DEEP_SUP).

       5.      Choose something like 1000 or 10000 as a block size.

       6.      Under Initial Flow Contexts, choose CRM as the source site type and SMOF_ERPSITE R/3 as the target site type. The consumer is CRM.

       7.      Include the dominant condition table from SAP CRM (for example, CNCCRMPRCUS523 or /1CN/CCFCUS776) under Tables/Structures. If necessary, maintain filters where no filter ranges are currently supported, only individual values.

       8.      Mapping modules R/3 -> CRM: Enter the module name CND_MAP_MAST_EXCHANGE_MAIN_MBD. Enter X under InQueue and ‘S’ as the Call mode. Choose 1.2 as the Call Order (for more information on these values, see the Middleware documentation).

       9.      Mapping modules CRM -> R/3: as the mapping module for the load to SAP ECC, enter module CND_MAP_MAST_UPLOAD_R3A.

Log

You get a log of the data transfer with transaction SLG1 or CND_MAP_LOG_DISPLAY (object: COND_EXCHANGE, subobject: CONDITIONS).

Delta Download

When changing or creating a condition record in SAP CRM, the information is automatically transferred to SAP ECC. For the delta upload of the contents of an SAP CRM condition table, an upload object must exist for this table, otherwise the data is not transferred. The filter settings of the upload object that belongs to the corresponding condition table are also applied during the delta upload.

If the rebate status changes for conditions of the usage Rebate in SAP ECC, then this change is transferred to SAP CRM again. Otherwise, no download is supported for rebate conditions.

Customer-Specific Fields

It is not possible to transfer master data for all condition tables from SAP CRM to SAP ECC. You need to make sure that the mapping of field names and -content for all fields of the variable key (VAKEY) and the variable data part (VADAT) has been defined. Particularly for condition tables that contain fields defined by the user, it is important to make sure that the way in which these fields are treated is defined in SAP CRM.

 

The following steps are required here:

●      The name of the corresponding SAP ECC field (target field for an upload) must be defined in structure CND_MAPT_ACS_REM_CUST. A data element must be entered which corresponds in format to the data element of the field in SAP ECC.

●      The field in SAP CRM must be contained in the field catalog for the condition technique.

●      The relationship between SAP ECC field names and SAP CRM field names must be defined in one of the tables CND_MAPC_CNV_FLM or CND_MAPM_CNV_FLM. CND_MAPC_CNV_FLM contains the field relationships delivered by SAP, whereas CND_MAPM_CNV_FLM contains the user's. (If an entry exists in both tables, the entry from CND_MAPM_CNV_FLM is used). If there is no entry, it must be included in the table CND_MAPM_CNV_FLM. Use the view V_CND_MAP_CNVFLD (transaction SM30). For the upload, you must select conversion direction ‘B’ (from local system to external system). The mapping type must also be entered in the specified table for the field contents. ‘A’ means that the content is copied. It is necessary that the formats of the source- and target field allow this. In the case of ‘B’, conversion is defined by the user with the help of the Business Add In CND_MAP_CNV_FIELD. Implementation of the BAdI is dependent on the filter. The filter value corresponds to the name of the field to be converted.

Restrictions

Not all condition tables are transferred in the data exchange. This depends on the key fields of the condition tables.

The key fields taken into account in the data transfer can be found in the table CND_MAPC_CNV_FLM (transaction SE16).

You must include your own key fields in the table CND_MAPM_CNV_FLM using the view V_CND_MAP_CNVFLD.

For the upload, only condition tables for the Trade Promotion Management process with usages PR (pricing), BO (rebates), FG (free goods) and CD (campaign determination) are supported.