Transferring Master Data from SAP ERP  

Use

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

Activities

Transferring Master Data

Start transaction R3AS in SAP CRM and make the following entries:

Object names: The condition tables have object names, each beginning with DNL_COND*.

Start the program individually for each of these objects.

Defining New Download Objects

Not all of the condition tables have download objects. You can create new download objects with transaction R3AC5.

...

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

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

       3.      Choose a block size, for example 1000 or 10000.

       4.      UnderInitial Flow Contexts, choose R/3 as the source site.

       5.      Under Tables/Structures, include the leading condition table (A table) and the related tables; KONP, KONH, KONM, KONW and TMC1K. If entries exist, include table TMC1D. For condition tables with a lot of entries, we recommend that you enter only one condition table per download object.

       6.      Download mapping modules: Enter CND_MAP_MAST_EXCHANGE_MAIN_MBD as the module name. Choose 1.2 as the call order (for more information on these values, see the Middleware documentation).

The program carries out the following steps:

●      It first deletes the old content of the condition tables in SAP CRM.

●      The contents of the condition tables (A tables) are transferred from SAP ECC into the condition tables (price tables) in SAP CRM.

●      The condition records are saved.

●      By making appropriate settings, the condition records are replicated to the consolidated database (CDB).

Log

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

Delta Download

When you change or create a condition record in SAP ERP, the information is automatically transferred to SAP CRM and, if necessary, to the CDB.

Customer-Specific Fields

It is not possible to transfer master data for every condition table from SAP ERP to SAP CRM. You need to make sure that the mapping of field names and field 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 SAP ERP field to be converted must be defined in structure CND_MAPT_ACS_REM_CUST. A data element must be entered that corresponds in format to the data element of the field in SAP ERP.

●      The target field in SAP CRM must be entered in one of the following structures with the correct data element. (This occurs automatically when creating new fields in the field catalog. The data element must first be created with transaction SE11):

○       CRMT_ACS_H_HEADER_ONLY (header fields)

○       CRMT_ACS_I_PRE (item fields that are mostly the same for all items)

○       CRMT_ACS_I_SEL (item fields that are mostly different for all items)

●      If the field should be saved in the transaction, it must be entered (with the same name as in the previous step) in one of the following database tables:

○       CRMT_CUSTOMER_I_INT (item data purely for internal processing)

○       CRMT_CUSTOMER_I_EXT (item data that can be displayed externally)

○       CRMT_CUSTOMER_H_INT (header data purely for internal processing)

○       CRMT_CUSTOMER_H_EXT (header data that can be displayed externally)

●      If you want to process a field dynamically, the BAdI CRM_COND_COM_BADI is available.

●      The relationship between SAP ERP 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 exist in both tables, the entry from CND_MAPM_CNV_FLM is used). If there is no entry, this must be listed in the table CND_MAPM_CNV_FLM. Use the view V_CND_MAP_CNVFLD (transaction SM30). The mapping type for the field contents must also be entered in the specified table. ‘A’ means that the content is copied. It is necessary that the formats of the source field and target field allow this. If ‘B’ is used, 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 table CND_MAPM_CNV_FLM (transaction SE16).