Skip to Content
Product Information

Integration of SAP Master Data Governance (MDG) with SAP Ariba Supplier and Lifecycle Performance (SLP)

We know that the integration and consistent availability of data are extremely important. Because not all Business Partners are created and governed centrally in a master data management application such as SAP Master Data Governance, but also in business applications, for example, SAP Ariba Supplier Lifecycle and Performance (SLP), an integration of such applications is not only reasonable but a requirement.

It is therefore not surprising that our customers have repeatedly asked for an integration of MDG with SAP Ariba SLP. Here’s good news for those who haven’t heard yet: We now offer an integration of SAP MDG-S with SAP Ariba SLP that is choreographed according to real and practice-oriented business scenarios! The integration is available for MDG on S/4HANA 1809 and higher, and MDG 9.2 (on ECC). Note that the integration is currently only available for customers running SLP as the only SAP Ariba component.

A closer look at the choreography

The choreography foresees various interaction scenarios according to the availability or non-availability of a specific supplier record in the interacting applications, for example:

  • Creation of new supplier in SLP during request or qualification: The supplier data is replicated to MDG-S where data can be changed and enriched, or where potential duplicates are detected. The result is replicated to SLP and the operational ERP system.
  • Change of supplier data in SLP: The supplier data is replicated to MDG-S where data can be changed or enriched. The result is replicated back to SLP and the operational ERP system.
  • Creation of new supplier in MDG: Supplier is created in a central governance process (change request) or a consolidation run. The result is replicated to SLP and the operational ERP system.
  • Change of supplier data in MDG (in central governance process or mass change): The result is replicated to SLP and the operational ERP system.
  • Merge active suppliers in MDG: The result is replicated to SLP and the operational ERP system.

You can find short videos about each of the scenarios here.


One of the MDG/SLP integration scenarios

For details, you can check out the SAP Roadmap Explorer.

If you’d like to get an overview or even a detailed description of the integration scenarios, visit the SAP Help Portal.

By the way, an integration also already exists for MDG-C with SAP Cloud for Customer (C4C). You can find more information in the SAP Roadmap Explorer and also on the SAP Help Portal.

While currently there’s still a direct connection between MDG and the applications, we plan on adding SAP Master Data Integration in the future as part of our integration strategy for master data. SAP Master Data Integration is planned to become the central master data sharing layer responsible for the data replication without changing the use cases and scenarios.

Find more information on SAP Master Data Governance here:

If you have any further questions, please leave a comment below or post your question to the community. Carsten Koehler will be happy to get back to you.


You must be Logged on to comment or reply to a post.
    • Hi Maria,

      yes, MDG is of course able to replicate to multiple ERP systems. The same integration scenarios can be used. The customer only has to add additional ERP system(s) within the replication model of MDG.

      This is one major difference compared to directly connecting SLP with ERP where SLP only supports one ERP system.

      KInd regards  Carsten

  • Many thanks Andrea and Carsten for your useful information.

    I would kindly ask you for clarification on the following questions:

    • could you please confirm that integration of SAP MDG-S with SAP Ariba solutions that include both SAP Ariba Supplier Lifecycle and Performance and SAP Ariba Procurement solutions, is not currently supported?
    • in this case, if both SLP and Ariba Buying solutions are implemented and we need to integrate SLP with multiple ERP (SAP ECC), what is the best practice?
    • Hi Eliana,

      Customers having Ariba Procurement Solutions in the landscape will not be able to make use of this integration (between MDG and SLP) as the direct integration between Ariba Supplier Lifecycle and Performance and Ariba Procurement Solution is not currently supported. The scenario you had described to integrate SLP with multiple ERPs and also connect with Ariba B&I needs to be discussed in detail with consulting.

      Best Regards

  • Hello leads,

    Can you please suggest the process of sending ACM_ID from SLP to ERP tables ? Will this acm_id should be sent in a enhanced custom field when sending request from SLP and should be manually maintained in ERP table like ARBCIG_SYSTIDMAP or auto population will happen ?

    Can someone explain the process of how ACM_ID will be sent to ERP via MDG-S and updating acm_id with ERP vendor id in tables ?

    • Hi Ramprasad,

      Sending the ACM_ID from SLP to MDG-S is not supported as part of the standard BP interface. Sending it via custom generic field and having custom enhancement at MDG/ERP side are to be taken up as project/custom implementation on case to case basis.

      Best Regards

      • Hello Raj Kumar,

        If we are using MDG-S as Hub type and when configuring SLP, any CIG add on is required to be installed in MDG-S separately or just activating the required Business Functions are enough ?

        Searched many blogs, and its clear that we have Addon for CIG in ERP/S-4 HANA, but activations are required in MDG-S for SLP interfaces.

  • Hello All,


    We have a similar requirement.

    in our case, ACM_ID would be sent from Ariba SLP to SAP MDG and would be stored at BP level. now this ACM_ID from BP have to be passed to vendor level. can anyone suggest how we can achieve it. is there any standard BAdi which can be implemented or we have to do it with CVI.


    Any pointers .

    • Hi Preet Lamba,

      Sending of the ACM_ID from SLP to MDG-S is not supported as part of the standard BP interface. Hence the scenario you have mentioned above needs to be dealt on project to project basis as custom based on detailed requirements.

      Best Regards

  • Thanks Andrea for the more precise information in the Ariba SLP to MDG Integration.

    In our scope, we are not using MDG Consolidation but only MD Governance(Staging) with the Ariba SLP integration.

    In this case, we have 2 main the main challenges.


    1. When the user in MDG rejects the Change Request in governance, the business user in Ariba SLP cannot see this and will not know that the Supplier data is rejected.
    2. When the inbound BP webservice fails in MDG due to a missing configuration/data issue, the business user in Ariba SLP have no idea what happens to the Supplier data he/she synced to MDG

    Do we have these challenges addressed in the latest MDG version?

    Appreciate your response.


    Thank you.




    • Hi Sankar,

      for good reasons we recommend using MDG Consolidation when a newly created supplier arrives from SLP. What can the user do in an MDG Change Request when the new supplier turns out to be a duplicate in MDG?

      Our answer is using MDG Consolidation because here you can not only run matching to find duplicates but also Best Record Calculation for merging the data of both BPs. Additionally MDG Consolidation will replicate back the result to SLP (including key mapping e.g. in case of a duplicate). This process cannot be supported by Central Governance because it only provides a duplicate check. Therefore, we strongly recommend to use Consolidation for incoming created BPs.

      To your challenges:

      1. MDG Change Request (our recommendation is for incoming changes only) should not provide any possibility to reject such a request. Process must be finalized, activated and result must be replicated back to SLP. Otherwise data between SLP and MDG would be out of sync what should never happen. By the way, for Consolidation we established a mode which ensures execution of the process w/o rejection for incoming creations as well.
      2. Normal data issues should not lead to inbound failure but data will be loaded to Change Request / Consolidation Run where data can be changed accordingly. In exceptional error situation an inbound failure might happen, therefore administrator should regularly check the cockpit on MDG side in order to resolve such situations.

      Kind regards  Carsten

      • Hello Carsten,

        Delighted to see the quick and detailed reply. Much appreciated.

        I now fully understand & agree with the recommendations above.                                                                                                                                                                                                                          Further, when I read through the SAP Could Integration Gateway(CIG) help portal, it raises me 2 more questions.

        1. I see a similar process flow described during the supplier creation in the help portal link. (similar to that you have stated above with the use of consolidation)                                                                                                                                                                                              But it does say that the scenario is achieved through SAP Master Data Governance.    Should we then say that the scenario mentioned in this link can only be achieved with Master Data Consolidation?
        2. I also went through the change scenario mentioned in the same SAP CIG help portal that describes the process with a flow diagram as well.                                                                What is mentioned in this process seems to be contradicting with the your point#1 above. Because, it says that once approved/rejected, the complete current vendor record is sent back to SLP.                                                                                                                                                                                                                                                                                                So, in case if there is a business requirement to have a rejection option for the incoming changes, does the standard MDG Governance support the process as mentioned in the help portal?


        Appreciate your reply.


        Thank you.