Data Mapping: Contact - Activity
The following graphic shows the mapping of the SAP ECC contact to the SAP CRM activity:
The graphic shows the relevant subobjects of the SAP ECC contact and the SAP CRM activity, as well as the names of the tables you use to define mapping rules. The allocation of the SAP ECC contact key to the CRM activity GUID is logged in the BPCT_CRM_GUIDS table.
The activities in SAP CRM are divided into two types,
contacts
and
tasks
. When developing the replication, we specified that the SAP ECC contact is to be mapped in an activity with the business transaction type
Contact
(0000) during the data transfer. However, the mapping can also take place to an activity with a different business transaction type. This business transaction type must use the
Contact
(BUS2000126) business transaction category, and must meet the following minimum requirements:
Schema |
Constraint |
|---|---|
Text determination procedure |
The text determination procedure must be defined for text object CRM_ORDERH, and must contain at least the text type A002 (“Note”). |
Partner determination procedure |
The partner determination procedure must contain entries from partner functions, which have the partner function categories 0006 "Contact Partner" and 0007 "Contact Partner". The business partner and contact partner for the IS-U contact are mapped to these entries. The determination procedure can also contain other partner functions. The system automatically allocates entries, which have the partner function category 0008 “Person Responsible” and 00005 “Employee”, to the user who created the contact in SAP Utilities. Otherwise, the standard partner determination for transactions applies for the entries. |
Date profile |
The date profile must contain at least the date type ORDERACTUAL – “Current Date”. |
In addition, the following general mapping rules apply:
A transaction with the business transaction category
Contact
(BUS2000126) is created in SAP CRM. You can select the business transaction type in the BPCT_CRM_CLASS table.
The category of the activity (for example, visit or E-mail) is determined for an SAP ECC contact using the BPCT_CRM_CLASS table.
The partner is copied to SAP CRM using the partner GUID. The SAP ECC business partner is mapped to the SAP CRM contact partner, and the SAP ECC contact partner is mapped to the SAP CRM contact partner.
The system determines the “responsible person” from the ERNAM field in the BCONT table (
created by
). If no corresponding business partner exists in SAP CRM, the system creates the activity with this "partner" anyway, and enters a corresponding error in the error log.
The system finds the “employee” in the same way as the "person responsible”.
The BPCT_CRM_DIRECT table is used to convert the contact direction.
The BPCT_CRM_PRIO table is used to convert the contact priority.
The system copies the organizational data from the template activity. If nothing is entered here, the data is determined “dynamically” according to the rules of organizational data determination for the activity.
The object links are created with the relationship category BCON in SAP CRM.
Contacts, in which a deletion flag is set, are not replicated.