Two-Tier ERP : Experience sharing during 1RO Master Data Integration Configuration

[shruthi_j_b]

In a Two-Tier ERP strategy, global organizations operate on two or more distinct ERP systems to cater to market demands. A key component of this approach is the integration of master data, such as the replication of customer data in a Two-Tier scenario utilizing the SAP Data Replication Framework (DRF).

1RO is mandatory scope item for Master Data Integration in S/4 HANA Public Cloud. The practices outlined here are w.r.t the below communication scenarios :

• Master Data integration for Business Partner, Customer, and Supplier (SAP_COM_0008)
• Master Data integration for Product Master (SAP_COM_0009)

Image 1 : SOAMANAGER->Technical Settings-> SAP Client Settings->Central Configuration->Central System Checkbox marked.

•  Maintaining consistency between the Domain system and Domain name is a recommended practice.
•  Maintain the Domain Weight accordingly and always ensure the domain is activated after creation.In case, you need to delete the Domain, always deactivate it first and then delete. 

   Image 2 : Domain Activation

• Under SOAMANAGER->Service Administration->Logon Data Management, please ensure that Maintenance template is created first and then the relevant assignment for the same. As such, the Assignment template created gets changed to type ‘Central’ only when the Service Group Connections under Integration Scenario Configuration is successfully activated.

In case you need to delete the Logon Data Management, thumb rule of deactivating the Integration Scenario Configuration or deleting the Service Group Connections under the same is to be primarily done followed by deactivation of Maintenance template and then deletion.

• Under SOAMANAGER->Service Administration->Integration Scenario Configuration->Service Group Connections, ensure Actor 1 always corresponds to the on-premise system and Actor 2 is the then created relevant domain.Ensure that after creation of the Service Group Connections, the Logon Data Assignments are reflecting and check for the Ping state for the same.

        Image 3 : Check for the corrrectness of the Logon Data Assignment under Service Groups Connection

Image 4 : Release created the Integration Scenario Configuartion

When it comes to Master Data Management (MDM) and integration, organizations often encounter common challenges. Let’s explore these issues and their potential resolutions.

SI No	Error	Possible Resolution
1	Activate logical ports for service group "MDM_PRD_REPLICATE_REQ" and application "<Domain Name >/sap.com/BusinessApplicationExternal"	1.       Check if Domain is activated. 2.       Hit the Release button in Integration Scenario Configurations and in the pop-up check domain availability and hit release till the state shows ‘Success’.
2	Service Group ‘MDM_PRD_REPLICATE_REQ’ used in IS “does not exist in the system”.	1.       Check the Service Group maintained in Logon Data Management. 2.       Check SOAMANAGER->Service Administration->Web Service Configuration > Filter on Object Type = Service group and Object Name = Service Group name. 3.       Check for the ‘Configuration’ facet and look for the ping state. 4.       This will give visibility on the state and relevant correction can be made.
3	From 'CLIENT <Automatically Created Domain>' to 'CLIENT <Domain Name>' in IS '<Integration Scenario Name>' user account doesn't match settings in <Domain Name>. Example: From 'CLIENT / EXI/916 / EXI/916' to 'CLIENT / ANDINA3_BP / ANDINA3_BP' in IS 'G5YCLNT100_BP_BPR' user account doesn't match settings in 'ANDINA3_BP'	1.       Check the data in Domain System 2.       Check if Domain is activated. 3.       Check for SOAMANAGER->Technical Settings->Domain Systems check for the following: WSIL Service credentials is filled. IBC References are assigned. Business Applications-> Retrieve Business Application is retrieved. 4.       Check for Logon Data Management Data Credentials. 5.       After verifying the above, delete and recreate Service Group Connections and then Save ->Edit->Activate->Edit->Release the Integration Scenario Configuration.
4	Assign IBC Reference CLIENT / EXI/916 / EXI/916 (ID = B3CA0A111BFB1EDEB99C53CDBA2D685B) to a Domain System)	Under SOAMANAGER->Technical Settings->Domain Systems check for the following: 1.       WSIL Service credentials is filled. 2.       IBC References are assigned. 3.       Business Applications-> Retrieve Business Application is retrieved.
5	DRFIMG Configuration a.        Under node-> Define Technical Settings for Business Systems b.       Under node-> Define Replication Models	Ensure proper Logical System is maintained via TCODE: BD54 and the same is defined against the created Business System. Maintain the appropriate Outbound Implementation is assigned.
6	DRFOUT execution error: Error in Key Mapping	1.       Ensure that settings in DRFIMG under nodes Define Technical Settings for Business Systems and Define Replication Models is correct w.r.t Logical System and other relevant data. 2.       Refer these blogs : https://community.sap.com/t5/supply-chain-management-q-a/quot-error-in-keymapping-quot-in-s4-product.... https://community.sap.com/t5/technology-blogs-by-sap/key-mapping-in-master-data-management/ba-p/1335...

The practices mentioned above are some of the key learnings from our journey. By addressing challenges and grasping the fundamental concepts of MDM and integration, we can attain overall efficiency.

References:

SAP Master Data Integration | SAP Help Portal