SAP Master Data Governance on SAP S/4HANA FAQ

FAQ for SAP Master Data Governance on S/4HANA collected from various workshops. Not all incoming questions were specifically related to the SAP MDG on SAP S/4HANA product version (vs. SAP MDG on SAP ERP), but the answers are generally provided from the SAP MDG on SAP S/4HANA perspective. With the SAP S/4HANA 2023 release, the cloud-ready mode in MDG was implemented. Questions that are specific to this mode of operation are grouped in a separate chapter on this page.

What is SAP Master Data Governance on SAP S/4HANA?

SAP Master Data Governance lets you define, enforce, monitor, and improve master data quality for central or decentralized approaches to master data management (MDM).

This FAQ page collects common questions about SAP Master Data Governance in general. The answers are based on the SAP Master Data Governance on SAP S/4HANA product version.

Please note that there is another FAQ page about SAP Master Data Governance, cloud edition which is a complementary deployment option.

Frequently Asked Questions (specific to cloud-ready mode in MDG)

What are classic mode and cloud-ready mode in SAP Master Data Governance?

As of SAP S/4HANA 2023, SAP Master Data Governance (SAP MDG) on SAP S/4HANA offers two different modes of using MDG processes: The standard delivery option of SAP MDG known as “SAP Master Data Governance” is referred to as “classic mode in SAP Master Data Governance”. The second mode is “cloud-ready mode in SAP Master Data Governance”, which is an alternative to classic mode in SAP MDG. See the description of cloud-ready mode and classic mode in the SAP Help Portal.

Which master data domain(s) supports cloud-ready mode in MDG?

As of today, cloud-ready mode is applicable for business partner (incl. customer and supplier) data. Product data is planned according to information on SAP Roadmap Explorer.

How does the data model for Business Partner differentiate between cloud-ready mode and classic mode?

Both classic mode and cloud-ready mode are based on the SAP S/4HANA data model for business partner (incl. customer and supplier).

Can classic mode and cloud-ready mode be operated in parallel?

Cloud-ready mode in MDG is one consistent common framework for all MDG scenarios. It enables new apps in newest SAP Fiori design system for:

  • Central governance (single processing and mass processing
  • Consolidation

Data quality management apps can be used seamlessly in cloud-ready mode and classic mode.

The coexistence of classic mode and cloud-ready mode is possible for central governance (typically for a transition phase). This means that when cloud-ready mode in MDG is switched on, central governance in classic mode can still be applied in parallel. Consolidation requires the use of the new app. And mass processing is also based on the new app for central governance. Data quality management processes do not require new apps.

When cloud-ready mode is switched on: can the user select the domain(s) for cloud-ready mode: for example, select cloud-ready mode for business partner, customer, supplier and keep classic mode for material?


How can the data model be extended in cloud-ready mode?

The data model can be extended in cloud-ready mode using SAP S/4HANA key user extensibility for fields. Node extensibility is a roadmap topic.

Does the usage of optional services with the cloud-ready mode require separate licenses?

The cloud-ready mode of SAP Master Data Governance allows the optional usage of SAP Build Process Automation, SAP Document Management Service, and SAP Data Quality Management, microservices for location data. The usage of these services is not included in the license for SAP Master Data Governance. As such, these services need to be licensed separately, for example by using a Cloud Platform Enterprise Agreement (CPEA).

Cloud-ready mode provides process monitoring for business partner, customer, and supplier data: How does this relate to the process analytics capabilities in classic mode?

The process monitoring, using the Process Path Overview app, is only provided for visualizing cloud-ready processes, which is not available for classic mode. This is independent of the process analytics app Master Data Process Overview for Business Partner. Both can be used in parallel.

When activating the cloud-ready mode: will the previously used process analytics apps for material and financial data stay active?

The process analytics apps for MDG domains are not planned to be deprecated. These apps can still be used after switching on cloud-ready mode.

Is the matching configurable in cloud-ready mode?

Yes. You can use the Configure Matching app (already available for classic mode). Most of the fields are configurable and weighting and fuzziness are supported.

Must users stick to the pre-delivered workflows or can users create custom workflows?

Users can adjust the process templates (created in MDG Customizing) and optionally assign workflows per process step. These workflow definitions are managed in BTP Business Application Studio (BAS). 

How is the data replication at the end of the workflow triggered?

The data replication is based on the replication set-up of SAP S/4HANA. It is not triggered by the workflow.

In data import and consolidation there are process templates specific to data sources. What does this mean exactly?

The process templates are preselected based on the types of data sources: either for business partner or for business partner plus relationships.

Can users adjust the pre-defined rules for best record calculation or create new rules?

Yes. This can be done like in classic mode.

Are there two separate processes required to load business partner and business partner relationships to the source tables?

Up to now, you must use two different import apps for BP and for BP relationships. Planned to be harmonized in one unified app.

Can users create custom fields and how are these distributed?

Yes. SAP S/4HANA key user extensibility (Custom Fields app) provides these fields in the common replication protocols.

Frequently Asked Questions (specific to federated governance)

When the ownership is defined based on hierarchies, is this valid for the selected node including leaves, and, if applicable, including sub-nodes and their leaves?

Yes. All sub-nodes and leaves are included.