MDG cloud edition and federated governance

So far this course has described MDG on SAP S/4HANA. SAP also offers SAP Master Data Governance, cloud edition: a software-as-a-service product built on SAP BTP. It is not a cloud copy of the on-premise product. It has its own data model, its own release cycle, and a narrower domain scope, and it is the foundation SAP positions for federated master data governance.

MDG cloud edition in brief

Recent cloud edition releases added, among other things, assignment of organizational units such as company codes, purchasing organizations and sales areas to a business partner, validation rule simulation and new data quality apps. Separately, MDG on SAP S/4HANA Cloud Public Edition added central governance for product data in release 2608. Do not confuse the two: the standalone cloud edition and MDG inside Public Edition are different products.

Cloud-ready mode in MDG on SAP S/4HANA

Since SAP S/4HANA 2023, MDG on SAP S/4HANA also offers a cloud-ready mode for business partner data (customer and supplier included), designed around clean core principles. It uses a process-based framework rather than the classic change request, key user extensibility for fields, and SAP BTP services for workflow, attachments and address validation, which are licensed separately from MDG. Classic mode and cloud-ready mode can run side by side during a transition, but processes cannot cross between them, and users see different UIs and inboxes. Data quality management works in both. Federation with the cloud edition requires cloud-ready mode.

Federated governance

In a federated model, several MDG instances each own a slice of a record. Core attributes such as name, address and tax numbers are governed by a core data owner; application-specific attributes, such as a supplier's purchasing data, are governed where they are used. A change can start anywhere, is replicated to the core data owner, which identifies and asks the affected data owners, and then distributes the agreed result. SAP describes the cloud edition as the foundation for this approach. Which instance plays which role depends on the landscape; confirm against SAP's current architecture guidance.

Where AI-assisted change requests fit

SAP offers a generative AI capability with Joule in MDG on SAP S/4HANA Cloud Private Edition: business users can search and display business partners, create or change them in natural language, ask about the status of governance processes, and get a generated summary of the changes in a request. It does not replace the governance process. A request created with Joule still runs through the same validations, workflow steps and approvals; the summary helps an approver understand what changed. Packaging and licensing for these AI features have changed more than once (SAP pages mention Joule Base and Joule Premium offerings), so check the current terms with SAP before you plan on them.

Whichever option you choose, the testing ideas in this course carry over: governed processes need routing tests with real roles, rules need passing, failing and out-of-scope cases, consolidation needs reviewed match results, and every receiver needs create, change and block tests with key mapping checked. The follow-on course sap-xpr-306 turns these ideas into a regression pack.

What goes wrong in testing

• Assuming feature parity. Test plans copied from MDG on SAP S/4HANA expect fields and steps the cloud edition does not have.
• Mixed modes in one test cycle. A request started in classic mode cannot be finished in cloud-ready mode; test each mode's processes separately.
• Treating AI output as approved. A Joule-drafted request must pass the same validation and approval tests as any other.
• Ignoring release cadence. SaaS releases change behavior on a schedule; plan regression for each cloud edition release.