Replicating Business Partners from SAP S/4HANA Cloud to SAP Master Data Integration Service
SAP Master Data Integration (MDI) service provides a Central Data Model to various Master Data Objects. It supports objects such as Business Partner, Product, Cost Center etc.
In addition, the service provides easy access to Business Partner data across the enterprise landscape. Below are the steps required to set up the Business Partner Integration with SAP S/4HANA Cloud.
I. Creation of Communication User
- Log in to the SAP S/4HANA Cloud system and ensure that you have the appropriate role assigned to your user to access the Communication Management tiles.
- Click Maintain Communication Users tile and click New. Provide a name for the Communication user and a password.
Note that this user will act as the communication user to the SAP S/4HANA Cloud system. The Business Partners will also be created via this user.
- Click Save.
II. Creation of Business System
- Click Communication Systems tile.
- Provide System ID and System Name. While this can be any alphanumeric value, it is recommended that you set this value the same as “identityzone” value in the service keys. Click Create.
- Navigate to the service keys copy the “uri” field.
- Paste the “uri” value in the Host Name field and provide any value for the Logical System field. Additionally, ensure that the value for “Business System” and “System ID” are the same.
- In next steps, we’ll add an inbound and outbound user to our Business System.
Navigate to Users for Inbound Communication section and click on the Add button. Select the Communication user that was earlier created and click OK.
The outbound user will be used to communicate with the SAP MDI service. We’ll use basic authentication for this setup. The clientid from the service keys is the username and clientsecret is the password.
- Save the Business System.
III. Creation of Communication Arrangement
- Select the Communication Arrangements tile.
- Click New and select the scenario SAP_COM_0008.
- Choose the Business System that was created earlier.
- Disable all the 5 Idocs interfaces.
- Change the service endpoints’ paths as shown in below screenshot and configure them to below values:
Business Partner – Replicate from SAP S/4HANA Cloud to Client:
Business Partner Relationship – Replicate from SAP S/4HANA Cloud to Client:
Business Partner – Send Confirmation from SAP S/4HANA Cloud to Client:
BP Relationship – Send Confirmation from SAP S/4HANA Cloud to Client:
- Provide a Replication Model Name. Set Replication mode as Change replication. If you want to replicate all the existing business partners from your SAP S/4HANA Cloud system to SCP Master Data for business partners you can set it to Initial replication.
Additionally, you can output mode to Direct Output or Pooled.
- Click on Save and Activate.
The Communication Arrangement setup is now complete.
In this blog post, we covered the necessary steps for configuration on the SAP S/4HANA Cloud side. The configuration necessary on SAP MDI is mentioned here.
Very good info Bisht!!
Hi Shivankit Bisht, thanks for this detailed blog.
I have some problems regarding the communication arrangement SAP_COM_0008 though.
I have setup the arrangement which refers to a communication system with "one-mds.cfapps.eu10.hana.ondemand.com" as a host value and "MDI" as the logical and business system value, which is also set as the configured value. The System ID & name itself is different.
This system has a outbound user, which is used in the arrangement. It uses USER ID & password authentication method, and the values are the clientID & clientsecret from the MDI service instance (as mentioned in your blog). When I check the connection of the outbound SOAP services (Business Partner - Replicate from SAP S/4HANA Cloud to Client f.e.) I get a 403 Forbidden error.
Is any configuration done wrong? I can't seem to figure out what the problem exactly is.
Thanks in advance!!
Update: apparently the ping option is not available for SOAP endpoints in communication arrangement SAP_COM_0008.
If you get above error, don't worry, the outbound SOAP service should work despite getting it.