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.
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. For the scenario description for SAP S/4HANA, follow this link.
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:
- Exchange knowledge: SAP Community | Q&A | Blog
- Try SAP Master Data Governance on S/4HANA for free: Trial Version
- Learn more: Latest Release | Webinars | Help Portal | How-to Guides
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.
Thanks Andrea for sharing. The videos are awesome!
Thanks Carsten & Andrea for publishing this blog. This is very precise and referring to the links for details wherever required.
Very nice. Easy read and very informative. The videos are awesome as well. Thank you Andrea & Carsten.
Thanks a lot, Andrea, this is really very useful!
Just one question: the described scenarios are valid also in case of multiple ERPs?
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:
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.
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 ?
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.
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.
The CIG add-on needs to be installed separately in MDG-S Hub system.
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.
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.
Do we have these challenges addressed in the latest MDG version?
Appreciate your response.
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:
Kind regards 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.
Appreciate your reply.
Kind regards Carsten
Thank you very much for the reply & clarifying the questions.
Much appreciated !
Does the native integration of Ariba SLP with MDG-S supports '1 BP to multiple vendors assignment' setup?
We are also exploring the option of '1 Business Partner to multiple vendors assignments' due to our multiple ECC target systems.
Does the Ariba SLP to MDG-S integration support this feature?
Hello Shivakumar, hello Sankar,
Ariba SLP does not know about multiple vendors assignment so this is also not supported by the integration with MDG-S.
Multiple customers / vendors assignment is offered in S/4HANA as well as in MDG-C / MDG-S. It is not planned to offer this functionality beyond these applications.
Kind regards Carsten
Thank you for the details & confirmation.
I'm not able to watch the video despite I've successfully logged in, getting error '403. You don't have rights to view this page'. Can someone help me here?
Sorry to hear the link isn't working for you. I just tried and it worked fine for me - please give this one a try. Let me know if you run into problems with that one as well and we'll figure it out :).
Hello Andrea Hoffmann,
Thank you for this blog and the many links to the videos on scenarios. They have been helpful.
However, I do have a question about the Restrictions mentioned in your blog as well as here:
Does this still apply and in what context?
I have recently seen SLP and MDG-S integrated with 3 SAP ECC systems where Ariba Procurement solutions were also implemented (Suite integrated end-to-end Ariba Solution) using Ariba CIG. There is no mention of such a restriction in the Ariba CIG guides either.
Perhaps this is a different solution offering? Could you please provide some information on this?
Thanks for your message. I've forwarded your comment to the product owner who'll get back to you to clarify the question.
The restriction mentioned is about 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 implementation scenario that you had described with SLP integrated to MDG-S connected to multiple ERPs and with Ariba B&I could be possible without the direct integration between Ariba Supplier Lifecycle & Ariba B&I but needs to be evaluated on a case to case basis on customer's requirement.
Thank you Kumar and Andrea,
That answers my question.
Hi Andrea, thanks for your sharing.
We're planning to integrate the SLP and SAP ECC.
I've some questions about the MDG-S and MDG foundation, whether any license is required for MDG-S and MDG foundation?
Whether MDG is mandatory for integration SLP between ECC?
If not, is DRF the alternative way?
And for the step# 2 - Send supplier to MDG via SOA Service, is there any existing standard service can be used in ECC?
Thanks a lot.
no MDG licence is required for integrating SLP and SAP ECC. DRF can be used for replication independent from MDG. You only have to configure DRF in a way that incoming suppliers from SLP are directly written to active area instead triggering an MDG process (option Staging Area).
You can use the same SOA Service as for integrating with MDG.
Kind regards Carsten
Thank you, Carsten.
Does this integration work the same way with MDG 2022? or there are some new or something has changed?
integration works the same way with MDG on S/4HANA 2022.
Kind regards Carsten