Federated Master Data Governance – Read enough? How about a video for a change?
You may already have seen and learned quite a bit about the federation of master data governance, the many benefits it can have for your organization, and how you can optimize master data management through federated data governance.
For example, in his insightful blog post Plan your own MDM roadmap with SAP Master Data Governance, Markus Kuppe explains how federation provides value, and why this could be the more effective approach for organizations that are eager to strike a balance between central and decentralized master data management to become more modular, and to be able to handle master data as perfectly as possible, exactly where it is best understood.
You can also find a broader perspective in a recent SAP Thought Leadership Paper that describes why you need the right mix of technology and organizational support as well as effective data governance to optimize data management, all in the context of federated master data governance.
As an addition to the existing blog posts and papers, we’ve published a video about Federated Master Data Governance that uses the creation of a new customer record in SAP Sales Cloud as an example to show the connection between:
- the management of core master data in SAP Master Data Governance, cloud edition,
- the management of application-specific data in the application where it is best understood, and
- a master data management process for the governance of core and application data across different applications.
Watch the video here:
For anyone who would like to learn more, here’s a list of links to the most important assets:
- Blog post Extended portfolio and additional deployment options for SAP Master Data Governance
- Conceptual Video: Extended Portfolio and Additional Deployment Options for SAP Master Data Governance, discussing the concept of federation and the purpose of SAP MDG, cloud edition in this context
- Conceptual Article: Extended Portfolio and Additional Deployment Options for SAP Master Data Governance, very similar content as in the above video for everyone who prefers reading
- News Release: Integrate Your Business Processes Today: Free Trial of SAP Master Data Governance, Cloud Edition
- Blog post Harness the Agility and Flexibility of a Cloud-Based Master Data Management Solution
- Demo Video: Create a New Business Partner in SAP MDG, cloud edition
- Demo Video: Analyze Data Quality and Remediate Errors in SAP MDG, cloud edition
- Trial SAP MGD, cloud edition: Christian’s blog post and SAP MGD, cloud edition Trial welcome page
- SAP Roadmap Explorer: Please see the roadmap for SAP Master Data Governance
- FAQ Page on SAP MDG, cloud edition and Federated MDG, get answers to frequently asked questions
Don’t forget to follow the MDGUpdates2021 tag to see more SAP Community blog posts about SAP Master Data Governance.
Thank you for sharing the video. Quick question on the exception scenarios. In this new architecture, MDI forms the kind of middle layer between the various applications and MDG Cloud Edition. There could be exceptions arising at every process step.
Step 1: Let's say a duplicate BP is identified at MDG cloud and the data steward decides not to create or merge. What happens to the BP created in MDI and Sales Cloud. Does it have to be deleted manually? Or is there a over-arching CR process which takes care of this automatically through a click of a button?
Step 2: Let's say at the AMDG on S4H EU, the Master data steward of Sales decides not to proceed further with the extension of this new BP to FR sales org. What happens to the BP created in MDG Cloud, MDI and the Sales cloud?
If you can shed some light on these exception scenarios, that would help.
thank you, very good questions!
Step 1: If data steward on MDG Cloud identifies the new BP being a duplicate then he / she will merge the core BP data on MDG Cloud. The information about the match group will reach MDI where data / key mapping will be merged accordingly. This shall be part of the process we plan to implement from MDG side, no manual deletion required.
Step 2: Stopping the process on AMDG must no be an option, the process must be finalized. But of course the user in AMDG EU shall be able to decide about deactivating sales org FR for this BP. The result will be synced back to MDI.
Kind regards Carsten
Thank you Carsten.
Thank you for the informative video. It already provides some use-cases in hybrid system landscapes.
From what I've heard, MDI is only capable of managing the core/shared master data. In this example however, I see that also sales organizational data, that is not part of the One Domain Model (ODM), is shared from SAP Sales Cloud towards the S/4HANA systems.
Is my understanding correct that MDI can distribute data outside of the ODM defined attributes?
ODM for Business Partner was already extended by several fields of the customer sales arrangement, will soon be published. The goal is to enhance ODM for Business Partner by all fields being relevant for distribution between applications. This also includes distribution between two S/4HANA applications. So step by step the ODM will be enhanced by all customer fields being relevant for replication.
MDI will continue to rely on ODM. This means MDI will only replicate attributes being part of ODM.
Kind regards Carsten
Thank you for the information, this is very clear now.
Is the API Business Hub still the place to check for the supported ODM attributes?
For me it was not clear which S/4HANA BP model attributes that were supported via the ODM explorer.
API Business Hub is the valid place to check for ODM attributes. First version of BP ODM is planned to become visible with 2105. However, the BP ODM will be extended step-by-step in the subsequent releases.
Kind regards Carsten
Thank you Carsten, this is very useful information!