Implementing SAP Master Data Integration with SAP S/4HANA using SOAP-based Communication and DRF

This article describes the end-to-end configuration for replicating Business Partner data from an SAP S/4HANA system to SAP Master Data Integration (MDI) using SOAP-based communication and DRF (Data Replication Framework). The prerequisites include creating an SAP MDI service instance and service key, enabling DRF in the S/4HANA system, and establishing connectivity between SAP BTP and On-Premises via SAP Cloud Connector. The configuration involves setting up WSDLs, publishing them to the Services Registry, creating an MDI system access profile, configuring logon data management, and linking service groups to the created logon data.

Replicating Business Partner data from an SAP S/4HANA system to SAP Master Data Integration (MDI) is a critical process for maintaining accurate and up-to-date master data across systems. This article outlines the end-to-end configuration for achieving this using SOAP-based communication and the Data Replication Framework (DRF).

Prerequisites

To begin the configuration process, several prerequisites must be in place:

1. SAP MDI Service Instance and Service Key: Ensure that an SAP MDI service instance and service key are created in the SAP Business Technology Platform (BTP) Cockpit.
2. DRF Enabled: The Data Replication Framework (DRF) must be enabled in the S/4HANA system.
3. Role-Based Access: Access to SOAMANAGER must be role-based.
4. Active Connectivity: There must be active connectivity between SAP BTP and the on-premises system via SAP Cloud Connector.

DRF Configuration

In the Data Replication Framework (DRF) Image (DRFIMG), create a Business System with a Business Object (BO) type and Communication System "Replication via Services" for the object "986" for Business Partner including Relationships. Ensure the Business System ID matches the one used in the MDO configuration to avoid integration errors.

WSDL Setup via SOAMANAGER

Download and customize six WSDL files as per SAP Note 2987243. These files include:

- BusinessPartnerSUITEBulkReplicateRequest_Out
- BusinessPartnerSUITEBulkReplicateConfirmation_Out
- BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out
- BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out
- KeyMappingBulkReplicateRequest_Out
- KeyMappingBulkReplicateConfirmation_Out

Add the required XML elements to each WSDL file before the /wsdl:definitions tag. These elements should contain the Master Data Integration Endpoint details.

Upload all six WSDL files in SOA Management and publish them to the Services Registry. Assign appropriate internal names, bindings, and physical systems, reusing the physical system object across all WSDLs after the first creation.

MDI System Access Profile

Create a new profile in Technical Administration with User ID/Password authentication and secured communication. Link this profile to the provider system using the same Business System ID as DRF.

Logon Data Management

In Service Administration, create credentials using the clientId as the username and clientSecret as the password from the MDI service key.

Local Integration Scenario Configuration

Add the service groups MDG_BS_SUPPLIERREPLICATEREQ, MDG_BS_SUPPLIERREPLICATECONF, KEY_MAP_REPLICATE_REQ, and KEY_MAP_REPLICATE_CONF. Assign IBC Reference to each from the MDI system and link all service groups to the created logon data.

Activate Logical Ports

Process all pending tasks in Service Administration and validate port creation via Web Service Configuration.

SOAP Endpoint Setup for MDI

For each of the six service definitions, create a service binding. Under "Transport Settings," copy the Calculated Access URL. The final endpoint URL will be used to configure the BPOUTBOUND destination in your BTP subaccount.

Conclusion

With the setup complete, your S/4HANA system is now capable of replicating Business Partner master data to SAP MDI in real-time via push or pull mechanisms. This configuration ensures secure communication, service group integration, and robust SOAP endpoints, enabling a scalable MDI architecture.

References

[1] SAP Community. (n.d.). SAP Master Data Integration (MDI) - Architecture, Deployment, and Configuration. Retrieved from https://community.sap.com/t5/technology-blog-posts-by-sap/sap-master-data-integration-mdi-sap-s-4hana-business-partner-replication/ba-p/14158651