Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Showing results for 
Search instead for 
Did you mean: 
Change Notes:
24 Aug 2021: Modified the way Provider system is configured.

In this blog, I will go through the steps necessary to connect a SAP Master Data Integration service instance with a SAP S/4HANA On-premise system. While these steps can be applied to connect any other cloud systems with S/4HANA, this blog will primarily focus on integration with MDI service on SAP Business Technology Platform.

I. Data Replication Framework Customising

In the S/4HANA, the Data Replication Framework is used to invoke theSOAP services.You can follow the steps mentioned in the webpage here to maintain DRF customising.

It is important that "Business system" value, that is used in DRF customising should be the same as MDI Business System Generic Configuration.

You can retrieve the MDI Business System Configuration via a Postman GET call on the below URL.(Use oAuth credentials of your MDI tenant)

For SAP canary environment, use the value "sap" in region placeholder.

II. Retrieving the WSDL required for the setup (Optional)

You can download WSDL files directly from here.
Note: You need to change the host Name in the URL configured in these WSDL file.

You can also fetch these files individually from system. Execute transaction sproxy in SAP S/4HANA system and download the WSDL files for the below interfaces.

BusinessPartnerSUITEBulkReplicateRequest_Out BusinessPartnerSUITEBulkReplicateConfirmation_Out BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out


III. Altering the WSDL files with MDI Endpoints

Add the following elements at the end of each of the WSDL Files before the </wsdl:definitions> tag. It is important to note that the below XML element contains a sample MDI Endpoint. You would have to replace this with your MDI details for all of them.

Eg. For BP, replace


with your MDI tenant endpoint. Additionally, make sure the endpoint contains the 443 port number suffixed after the Host Name.

a. BusinessPartnerSUITEBulkReplicateRequest_Out
<wsdl:binding name="CO_MDG_BP_RPLCTRQ" type="tns:BusinessPartnerSUITEBulkReplicateRequest_Out">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="BusinessPartnerSUITEBulkReplicateRequest_Out">
<soap:operation soapAction="" style="document"/>
<wsdl:input name="BusinessPartnerSUITEBulkReplicateRequest">
<soap:body use="literal"/>
<wsdl:service name="BusinessPartnerSUITEBulkReplicateRequestOut">
<wsdl:port name="MDI_PORT" binding="tns:CO_MDG_BP_RPLCTRQ">
<soap:address location="https://one-mds.cfapps.sap.hana.ondemand.com:443/businesspartner/v0/soap/BusinessPartnerBulkReplicateRequestIn?tenantId=mdibpconsumer1"/></wsdl:port>

b. BusinessPartnerSUITEBulkReplicateConfirmation_Out
<wsdl:binding name="CO_MDG_BP_RPLCTCO" type="tns:BusinessPartnerSUITEBulkReplicateConfirmation_Out">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="BusinessPartnerSUITEBulkReplicateConfirmation_Out">
<soap:operation soapAction="" style="document"/>
<wsdl:input name="BusinessPartnerSUITEBulkReplicateConfirmation">
<soap:body use="literal"/>
<wsdl:service name="BusinessPartnerSUITEBulkReplicateConfirmationOut">
<wsdl:port name="MDI_PORT" binding="tns:CO_MDG_BP_RPLCTCO">
<soap:address location="https://one-mds.cfapps.sap.hana.ondemand.com:443/businesspartner/v0/soap/BusinessPartnerBulkReplicateRequestConfIn?tenantId=mdibpconsumer1"/></wsdl:port>

c. BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out
<wsdl:binding name="CO_MDG_BP_RELATIONSHIP_OUT" type="tns:BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out">
<soap:operation soapAction="" style="document"/>
<wsdl:input name="BusinessPartnerRelationshipSUITEBulkReplicateRequest">
<soap:body use="literal"/>
<wsdl:service name="BusinessPartnerRelationshipSUITEBulkReplicateRequestOut">
<wsdl:port name="MDI_PORT" binding="tns:CO_MDG_BP_RELATIONSHIP_OUT">
<soap:address location="https://one-mds.cfapps.sap.hana.ondemand.com:443/businesspartner/v0/soap/BusinessPartnerRelationshipBulkReplicateRequestIn?tenantId=mdibpconsumer1"/></wsdl:port>

d. BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out
 <wsdl:binding name="CO_MDG_BP_RELATIONSHIP_CNF_OUT" type="tns:BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="BusinessPartnerRelationshipSUITEBulkReplicateConfirmation_Out">
<soap:operation soapAction="" style="document"/>
<wsdl:input name="BusinessPartnerRelationshipSUITEBulkReplicateConfirmation">
<soap:body use="literal"/>
<wsdl:service name="BusinessPartnerRelationshipSUITEBulkReplicateConfirmationOut">
<wsdl:port name="MDI_PORT" binding="tns:CO_MDG_BP_RELATIONSHIP_CNF_OUT">
<soap:address location="https://one-mds.cfapps.sap.hana.ondemand.com:443/businesspartner/v0/soap/BusinessPartnerRelationshipBulkReplicateRequestConfirmIn?tenantId=mdibpconsumer1"/></wsdl:port>

e. KeyMappingBulkReplicateRequest_Out
 <wsdl:binding name="CO_KEY_MAP_RPLCTRQ" type="tns:KeyMappingBulkReplicateRequest_Out">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="KeyMappingBulkReplicateRequest_Out">
<soap:operation soapAction="" style="document"/>
<wsdl:input name="KeyMappingBulkReplicateRequest">
<soap:body use="literal"/>
<wsdl:service name="KeyMappingBulkReplicateRequestOut">
<wsdl:port name="MDI_PORT" binding="tns:CO_KEY_MAP_RPLCTRQ">
<soap:address location="https://one-mds.cfapps.sap.hana.ondemand.com:443/businesspartner/v0/soap/KeyMappingBulkReplicateRequestIn?tenantId=mdibpconsumer1"/></wsdl:port>

f. KeyMappingBulkReplicateConfirmation_Out
  <wsdl:binding name="CO_KEY_MAP_RPLCTCO type="tns:KeyMappingBulkReplicateConfirmation_Out">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>
<wsdl:operation name="KeyMappingBulkReplicateConfirmation_Out">
<soap:operation soapAction="" style="document"/>
<wsdl:input name="KeyMappingBulkReplicateConfirmation">
<soap:body use="literal"/>
<wsdl:service name="KeyMappingBulkReplicateConfirmationOut">
<wsdl:port name="MDI_PORT" binding="tns:CO_KEY_MAP_RPLCTCO">
<soap:address location="https://one-mds.cfapps.sap.hana.ondemand.com:443/businesspartner/v0/soap/KeyMappingBulkReplicateConfirmIn?tenantId=mdibpconsumer1"/></wsdl:port>


IV. Configuring MDI system access - Profile Creation

  1. Navigate to tab “Technical Administration” and open “Profiles”.

  2. Click on "Create Profile".

  3. Enter a Name and a Profile Description for accessing SAP MDI and select “Old Profile Mode”.

  4. Click “Next” and fill out the Security Settings as follows -
    a. Authentication Method: User ID/Password
    b. Identifiable Business Context: No IBC Determination
    c. Transport Security: Select “Secured Communication”

  5. Click “Next”. In case Proxy Settings are used, fill them in. Otherwise leave them empty & click “Finish”

  6. Confirm the popup with “Yes”  and activate the profile


V. Configuring MDI as "Third party Provider System"

At this point you need to check your SAP BASIS release version. The below steps are valid only for SAP BASIS release >= 7.53. For lower version, please follow the steps mentioned in the note here.

  1. Navigate to tab “Technical Administration” and open “Provider Systems”

  2. Click on "Create Special" dropdown and select "Create Third Party System"

  3. Provide a name for the Provider System.
    NOTE: The name of the Provider system here should "exactly" match the value configured in Generic Configuration on MDI.
    In the "Profile Name" dropdown, select the value created in previous step.

  4. Click Next. Provide credentials of a system user that can access Service metadata. Ensure that the "Use WSIL user" checkbox is selected.

  5. Click Finish. At this step you will get a popup to activate the Provide system. DO NOT activate it yet.

  6. Click on the Provider System that was just created and navigate to "WSDL assignments" tab.

  7. Click on "Upload" button and select the WSDL file from your system.

  8. Click "Next". Do not modify the WSDL.

  9. Click Next. Ensure that the Service Definition Name is selected.

  10. Click "Next" and then click "Confirm".

  11. Repeat the above step for all the WSDL Files that you want to upload.

  12. Finally, click on "Activate".

VI. Logon Data Management

  1. Navigate to tab “Service Administration” and open “Logon Data Management”.

  2. Click on “Create”. Provide a meaningful Logon Data Name & Description.

  3. Provide Logon Data for MDI by entering User Name & Password. From the service keys of MDI instance, clientId is the username and clientSecret is the passwrod.Ensure that the instance should be generated using correct BusinessSystemId parameter. (Refer Section 1 of this blog)

  4. Click “Finish” and confirm the popup with “Yes” to activate the Logon Data immediately.


VII. Configure Local Integration Scenario

The local integration scenario will only contain the outbound messages from SAP S/4 HANA to SAP MDI. In principal it would also be possible to configure the corresponding inbound services as well. However, the current SAP S/4 HANA – MDI – integration requires a different alternative access URL. Therefore, the configuration for the inbound services must be done (manually) outside the Local Integration Scenario Configuration.

  1. Navigate to tab “Service Administration” and open “Local Integration Scenario Configuration”

  2. Create new integration scenario by clicking “Create”.

  3. Provide a meaningful Name & Description.

  4. Click “Next”. Since no inbound services shall be configured here (explanation see above), click “Next”.

  5. Add the following Service Groups

  6. Select all the Service Groups and click on "Assign IBC Reference". Execute search, chose MDI System from the search result, and click “Assign to Service Group”.

  7. The result should look like this.

  8. Select the Logon Data for each Service Group from the dropdown. Choose the Logon Data created earlier for all the service groups.

  9. Click “Finish”. Confirm the popup with “Yes” if you want the integration scenario to be activated immediately.

  10. Activate the pending tasks. Navigate to them by clicking the link.

  11. Click “Process List” to activate the logical ports

  12. If everything has been done properly, the logical ports should be activated successfully. Confirm the popup with “OK”.

  13. If everything has been configured as desired, navigate to tab “Service Administration” and open “Web Service Configuration.

  14. As search criteria, enter one of the Consumer Proxy

    and click “Search”

  15. Ensure that a Logical Port is created for the our Provider System. Additionally, select the Logical Port and click on "Set Log. Port Default"

  16. Similarly, you can verify Logical Port creation for other Service Groups.

  17. At this point you Business Partners created in this system will be replicated to your MDI tenant. (Assuming necessary configuration is done at MDI. More details available here.)


VIII. Creating SOAP Endpoint to receive Business Partner and Key Mapping data from SAP MDI

  1. Navigate to tab “Service Administration” and open “Web Service Configuration.


  3. Click on "Create Service"

  4. Provide value for
    - Service Name: any meaningful name
    - New Binding Name: any meaningful name
    Click Next.

  5. Select SSL as Transport Level Security. Enable UserId/password as Transport Channel authentication.

  6. Click Next and then click Finish.

  7. To view the created binding, click on Display button.

  8.  Navigate to "Transport Settings" tab.Copy the contents of "Calculated Access URL" field.

  9. The SOAP Endpoint is concatenation of Host Name of the ERP system and the "Calculated Access URL" field.
    To retrieve HostName execute transaction smicm and then Click Shift +F1.
    So, the final BP Endpoint URL will look like this.

    You should use this URL to configure the BPOUTBOUND destination in your subaccount.

  10. Repeat Steps 2 - 6 for Service Definitions
    c. BP Relationship Confirmation: BUSINESSPARTNERRELATIONSHIPSU1


Thank You.