Skip to Content
Product Information
Author's profile photo Mudit Saini

Customer Migration strategy: from SAP Master Data Service for Business Partners to SAP Master Data Integration Service


SAP offers Master Data service for Business Partners to enable integration of business partner master data in Integrated suite (IE) scenarios. This service is available on SAP Discovery Center as part of CPEA (Cloud Platform Enterprise Agreement) in a consumption-based license model.

With SAP Master Data Integration service (MDI) positioned as the primary solution for master data integration requirements in IE scenarios, customers are not recommended to use Master Data service for Business Partners going forward. Thus, there is a need to migrate the existing customers of the service to MDI.

Objective of this document is to cover the detailed migration strategy which can be leveraged by customers to move away from Master Data service for Business Partners towards Master Data Integration.

Migration Strategy

Current State

For ease of understanding, it is assumed that customer landscape has two systems integrated via SAP Master Data service for Business Partners in the below diagram. However same approach would hold true for multiple systems connected via the service.

Also please note the scope of integration is limited to business partner master data object only with standard delivered features of the service.


Customer Landscape: As Is

Consider the above example. System 1 and System 2 use SOAP APIs to connect to SAP Master Data service for business partners. Following SOAP messages are in scope:

  • Business Partner
  • Business Partner Relationship
  • Business Partner Key Mapping

For more information on SOAP messages and corresponding SOAP services, please refer to SOAP Service for Data Replication documentation.

Migration Steps:

Migration is broadly going to be a 6-step process as described below:

Step 1: Onboarding SAP Master Data Integration in the system landscape

This step is required to bring Master Data Integration service (MDI) into the customer landscape. At this point in time, MDI needs to only integrate with master data service for business partners.

This is required to do the initial load of business partner records into MDI. Initial load is intended to take place while the business continues as usual. This would ensure 0 downtime for initial data load into MDI.

Since Master Data service for Business Partners is intended to behave like any other consuming application for MDI, onboarding the service for business partners as a client of MDI is required. For more information, please refer to Initial Setup MDI documentation.

Step 2: Set up Data replication towards MDI in SAP Master Data service for Business Partners

This is done by creating  MDI destinations and distribution model in the legacy Master Data service for Business Partners. Please refer to SAP help documentation for more details.

After step 1 and 2, customer landscape should look as depicted in the below picture:


Introduction of MDI in Customer Landscape

Step 3: Start initial replication

Replication of records is initiated from Master Data Orchestration (MDO) subscribed with Master Data service for Business Partners. One can use ‘replicate’ functionality provided by MDO distribution model to initiate replication from Master Data service for Business Partners to Master Data integration service.

For more information, refer to Maintenance of the Distribution Model in SAP Master Data Orchestration documentation.

To being with, customers are recommended to test replication with a few BPs rather than with complete load. This will help getting accustomed with the migration process and fix any unforeseen issues for e.g. missing configuration. Customer can also create a SAP ticket with component: BC-CP-CF-ONEMDS in case they face issues.

In order to ensure proper sequencing of SOAP messages, follow the below mentioned instructions:

  1. Replicate only Business partner/ BP relationship Records. Do Not trigger Key Mapping. This can be achieved by setting Distribute Key Mapping to false in the distribution model.
  2. Once replication of BP is complete, commence with step 3. To check the completion of BP replication, use the replication status API covered in step 4 
  3. Again, replicate Business Partner and Business Partner Relationship Records, along with Key Mapping. Set Distribute Key Mapping to true in the distribution model and replicate again.
  4. With replication, BP Confirmation SOAP messages for replicated records would be sent from Master Data Integration service to Master Data service for Business Partners. As a result, key mapping information would be updated in Master Data service for business partners.
  5. Update of key mapping information in Master Data service for Business Partners will trigger key mapping distribution to connected systems with the new Master Data Integration key.
  6. All systems in the customer landscape will now have Master Data Integration Key.

Step 4: Check Initial replication status.

Once the replication of master data records is initiated, you can get the initial replication status :

Following response types would be available to give status of initial replication:

  • Response Type:
    • Open – Initial replication is not yet started.
    • In Progress – Initial replication is ongoing.
    • Completed – Replication is completed.

Please refer to SAP help documentation for details.

Step 5: Validate Migrated Records on SAP Master Data Integration 

After successful migration of master data records from the legacy SAP Master Data service for Business Partners to SAP Master Data Integration, follow the below steps to validate the records and retrigger the Business Partner replication of erroneous records.

Validate the migrated master data record: 

In order to validate replication status of records in MDI, an API is provided by SAP. This API can be leveraged to get the replication status of failed records in a flat file (CSV) which customer can download for analysis purpose.

Please refer to SAP Help documentation for details.

Retrigger Business Partner Replication:

Customer can check the validation data and retrigger BP replication to Master Data Integration from the MDO UI. In order to retrigger replication, replicate functionality for individual records provided by MDO-> Display Distribution status tile can be used.

Alternatively, customers can choose to set the filter criteria in the MDO distribution model for the failed records and retrigger replication (as mentioned in step 3). E.g., of filter criteria: BP ID of failed records.

Step 6: Re-configure integration to point to Master Data Integration service

  1. Reconfigure connected systems to point to Master Data Integration instead of Master Data service for business partners. Depending upon whether systems are connected in a point-to-point fashion (for e.g. S/4HANA) or via CPI (for e.g. CX applications), different steps would be required in the corresponding system.Please refer to the below blogs for steps required to set MDI connectivity in S/4HANA
  2. Do not activate connection to Master Data Integration service yet, in order to ensure zero downtime.
  3. Create destination and distribution model in Master Data Integration for connected systems without activating them. For more information, see Destination Configuration for Master Data Orchestration and Distribution Model Maintenance.

Customer landscape should look as depicted in the below picture


Reconfiguration with MDI

  1. As a next step,
    • Disable replication from connected systems to Master Data services for Business Partners. For e.g. in S/4HANA disable the corresponding replication model.
    • Remove all connection to the legacy service for business partners in the connected system(s).
    • Deactivate all distribution models in Master Data services for Business Partner
    • Activate all distribution models for connected system(s) in MDI. This is followed by activating replication framework in connected system towards MDI. This activity would require a minimum downtime.
  2. After completing the above step, Master Data Integration should be the de facto replication service in customer landscape and business can continue as usual.
  3. As a last step, offboard Master Data service for Business Partners by deleting all corresponding service instances and subscription. For more information, refer to the section Disconnecting a Client in Onboarding Clients
  4. The following graphic depicts the final state of customer landscape:


Deactivate Master Data Service for Business Partners


With this step, migration to MDI is complete.












Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.