Configuring the Multiple Back-End
Scenario
Before you start to implement a multiple back-end scenario, refer to SAP note 1084315.
To set up the multiple back-end scenario you have to perform various configuration steps:
1. Ensure that during the generation of the CRM system the multiple system exchange projects (MEP) specific generator group CRMEP has been generated.
2. To activate the multiple back-end scenario and the logging and monitoring, call transaction SM30. In view ISPCFG add a new entry under parameter name: CRMMEP. Make sure that the following parameters are set:
Parval=X (multiple back-end is active)
Parval2=X (monitoring/logging is active)
If you want to view the logs after having implemented the scenario, call transaction CRMMEP_MBLOG. You can check the following details:
● output from ABAP MapBox in XML format
● input to ABAP MapBox in XML format
● corresponding CRM Middleware trace
3. Customizing objects have to be loaded from one ERP back-end into the CRM system. There is no MEP-specific functionality for the initial load of customizing objects available. The customizing objects can be enhanced manually in the CRM system.
4. To map the CRM organizational data to more then one ERP system, implement SAP note 1062970. You can either download the organizational data or maintain them manually in the CRM system. Check and maintain the mapping of CRM organizational units to ERP organizational units (transaction PPOMA_CRM).
5. Maintain global parameters in the IMG: Customer Relationship Management → CRM Middleware and related Components → Multiple Exchange Projects (MEP) → Maintain Global Parameters.
In this view the mapping for business objects between multiple ERP systems and one CRM system can be enabled.
To enable the business partner mapping, the following settings have to be made:
ParName1 = MAPBOXACTIVE (MapBox is active for a special object)
ParName2 = CUST_MAIN, CUST_REL, MATERIAL (see Maintain Object Repository → Bdoc Type)
ParName3 = Logical System
ParVal1 = X (bi-directional), D (download), U (upload)
6. Maintain the prefix for business partners in the IMG: Customer Relationship Management → CRM Middleware and related Components → Multiple Exchange Projects (MEP) → Maintain Prefix for Business Partners.
Here you can set up prefixing for Business Partners (to identify via a prefix in which system they were created). To be able to incorporate the prefixing logic, you have to implement SAP note 1062808.
Make sure the following entries are made:
Enter the logical name of the CRM system in Logical System and KUNNR as field type. As prefix you can enter a numerical or alphanumeric value.
An evaluation has to be made before a decision to include Prefixing is considered. Entries are customer-specific and the following has to be ensured if any prefixing is in place:
The respective target ranges have to match the source interval PLUS the prefix in CRM and assigned accordingly to the account group/BP groupings that are mapped to each other in the backend (TA PIDE.)
This can be verified in the following IMG activities:
CRM → Cross Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings
In the ERP system:
Logistics-General → Business Partner → Customers → Control → Define and Assign Customer Number Ranges.
Further transaction to check is PIDE, if the Account Group being used is mapped to the CRM grouping for the direction ERP to CRM and the CRM Classification is assigned to an Account Group in ERP in the direction CRM to ERP.
7. Maintain the field mapping for a business object in the IMG: Customer Relationship Management → CRM Middleware and related Components → Multiple Exchange Projects (MEP) → Maintain Field Mapping for Business Object. The mapped fields for the supported business objects are displayed in this view.
Scenario Object
The view contains the list of scenarios (business objects) delivered as standard for mapping with a brief description.
Maintain Operation Field
Entry in Scenario ID should match an entry in the IMG view MEP-> “Maintain Object Repository”-> CRMMEP Scenario->Explanation.
For every scenario maintained above it is possible to maintain the input fields in the “Maintain operation field section”. The fields should have the same name as in the Input BAPI structure. For each of these fields, the type of operation can be specified.
There are two operation types:
MAP - mapping according to certain rules that are already existing.
COPY - copy the input.
The operation type of fields can be changed.
Example: For the mapping of business partners enter the field name Partner under scenario ID PARTNER_INBOUND_R3 and PARTNER_OUTBOUND_R3. Specify the operation type MAP and set Error Handling as ‘X.
Similarly for all other existing Customizing we can control the operation type.
8. Maintain the object repository in the IMG: Customer Relationship Management → CRM Middleware and related Components → Multiple Exchange Projects (MEP) → Maintain Object Repository.
For the supported business objects the following detailed information regarding the object repository and the mapped BAPIMTCS structure is displayed:
CRMMEP Object
Header information for every business object to be used in the data exchange between multiple back-end systems and the CRM system.
CRMMEP Structure
This is used to store the input structures of every business object, which are exchanged between the ERP system and the CRM system. The names of the structures need to be identical with the names in the data dictionary
CRMMEP Scenario
This is used to differentiate between the different scenarios:
● Inbound scenario for the direction ERP to CRM.
● Outbound scenario for the direction CRM to ERP.
Do not modify the contents shipped as
standard.
Settings in the Solution Manager
Before you perform the configuration steps in the Solution Manager system you have to implement RFC connections between the ERP systems and the CRM system. Call transaction SCIDM_CONFIG. The ID types are displayed. Define your business system. Enter a name, assign the RFC connection and flag the CRM system as integration server.
1. Define Type Groups
In transaction SCIADM you can define the type groups you want to use with your Integration Server and assign the relevant ID Types to it (example: CRMMEP_ATTR01 for field ATTR01).
2. Define ID Mapping
In transaction SCIDM_CONFIG define the fields mapping for the customizing tables. Select one system in ID Types with Source Systems and click on Display IDs from System. You can use drag and drop to assign the values to the mapping table. Repeat the steps for all mapped fields.
Field Mapping Business Partner:
Fields Mapped (CRM/ERP) |
CRM View |
ERP View |
CRM Table |
ERP Table |
ATTR01 |
V_CRMC_ATTR01 |
V_TVK1 |
|
|
ATTR02 |
V_CRMC_ATTR02 |
V_TVK2 |
|
|
ATTR03 |
V_CRMC_ATTR03 |
V_TVK3 |
|
|
ATTR04 |
V_CRMC_ATTR04 |
V_TVK4 |
|
|
ATTR05 |
V_CRMC_ATTR05 |
V_TVK5 |
|
|
ATTR06 |
V_CRMC_ATTR06 |
V_TVK6 |
|
|
ATTR07 |
V_CRMC_ATTR07 |
V_TVK7 |
|
|
ATTR08 |
V_CRMC_ATTR08 |
V_TVK8 |
|
|
ATTR09 |
V_CRMC_ATTR09 |
V_TVK9 |
|
|
ATTR10 |
V_CRMC_ATTR10 |
V_TVK0 |
|
|
CUSTGRP1 |
CRMV_CUSTGRP1 |
V_TVV1 |
|
|
CUSTGRP2 |
CRMV_CUSTGRP2 |
V_TVV2 |
|
|
CUSTGRP3 |
CRMV_CUSTGRP3 |
V_TVV3 |
|
|
CUSTGRP4 |
CRMV_CUSTGRP4 |
V_TVV4 |
|
|
CUSTGRP5 |
CRMV_CUSTGRP5 |
V_TVV5 |
|
|
CUSTOMERGROUP |
CRMV_CUSTGRP |
V_T151 |
|
|
PRICEGRP |
CRMV_PRICEGRP |
V_TMFK4 |
|
|
PRICELIST |
CRMV_PRICELIST |
V_T189 |
|
|
DISTRICT |
CRMV_DISTRICT_MD |
V_T171 |
|
|
OFFICE |
V_T018P |
V_T018P |
|
|
GROUP |
|
V_TVV1 |
CRMC_SGRP_R3GRP |
|
SHIP_COND |
CRMV_SHIP_COND |
V_TVSB |
|
TB019 |
TB019 |
TB019 |
|
|
|
INCOTERMS1 |
CRMV_INCOTERM |
V_TINC |
|
|
INCOTERMS2 |
CRMV_INCOTERM |
V_TINC |
|
|
DLV_PRIO |
CRMV_DLV_PRIO |
V_TPRIO |
|
|
Field Mapping Products:
Fields Mapped (ERP → CRM) |
CRM View |
ERP View |
CRM Table |
ERP Table |
CRMC_ITEM_CAT_GR |
CRMV_ITEM_CAT_GR |
V_TPTM |
|
|
TVKO |
|
|
CRMC_SORG_R3ORG |
TVKO |
CRMC_DISTCHAN |
|
|
CRMC_DISTCHAN |
TVTW |
CRMC_DIVISION |
|
|
CRMC_DIVISION |
TSPA |
CRMC_PRC_PRGRP |
|
|
CRMC_PRC_PRGRP |
T178 |
TVKM |
|
|
CRMC_ACGRPPROD |
TVKM |
T006_ |
|
|
T006 |
T006 |
3. Transfer Customizing Mapping from Solution Manager to CRM
To be able to transfer the customizing mapping from Solution Manage, you have to establish the RFC connection in the following IMG activity: Customer Relationship Management → CRM Middleware and related Components → Multiple Exchange Projects (MEP) → Transfer Customizing Mapping from Solution Manager.
In the CRM system navigate to the following IMG activity: Customer Relationship Management → CRM Middleware and related Components → MEP → Maintain Global Parameters.
For Parameter Name 1 enter MEPSMCUST and enter X.
In the CRM system run program CRMMEP_SOLMAN_CUSTMAP to retrieve the mappings from Solution Manager. Enter the logical system name of the CRM system as integration server and enter the logical system name of the Solution Manager system as RFC destination.
Customer Enhancements
Additional Field Mapping for Existing Business Objects
To map a customizing field, that is not mapped in the standard, execute the following steps:
The Enhancement Spot that is used for the exit is CRMMEP_IN_SCENARIO (TA SE18)
The BADI definition is CRMMEP_IN_SCENARIO (TA SE18)
The Interface is IF_CRMMMEP_SCENARIO and method where the Customer specific code has to be put is DO_TRANSFORM. An Implementation for this BADI has to be specified and the mapping logic for the specific field has to be implemented here. (TA SE19)
Once the mapping logic is completed and implemented, the reference variable lr_in_msg should have the all the structures along with the new mapped field, as this is the reference variable passed forward for the standard mapping procedure.
New Business Objects
To enable business objects, that are currently not supported in the standard (e.g. sales documents), execute the following steps:
The Enhancement Spot that is used for the exit is CRMMEP_NEW_SCENARIO.
The BADI definition is CRMMEP_NEW_SCENARIO. The Interface is IF_CRMMEP_NEW_SCENARIO and method where the customer-specific code has to be added is DO_TRANSFORM.
An implementation for this BADI has to be specified and the mapping logic for the specific field has to be implemented.