SAP Master Data Governance runs inside S/4HANA (and as a cloud edition on BTP) with central governance, consolidation and mass processing; SAP now presents it as a core component of SAP Business Data Cloud beside Reltio.
Every SAP MDG cell carries its source number; the sources are listed at the foot of the page.
| Question | SAP MDG | Lima master data |
|---|---|---|
| Where the master data lives | Active master data is stored in the S/4HANA tables that SAP transactions reference directly, with a staging area for change requests; consolidation loads source data into its own tables before activation; replication to other systems through the data replication framework [1][2]. | Golden records are governed views over the sources, read in place through the federated engine, and materialised only where latency needs it, in your lake, under the same keys. The transactions sit in the same bed, so a merged customer and its orders change together. |
| Reaching SAP, Oracle and the lakes | The strongest single-bed story for SAP-resident transactions; other ERPs and lakes connect through SAP integration tooling and, in Business Data Cloud, 'zero-copy data sharing' with Snowflake, Databricks, BigQuery, Fabric and Athena planned for H2 2026 [3][1]. | SAP S/4HANA and ECC through released read interfaces and change capture; Oracle Fusion through REST and BI Cloud Connector extracts, E-Business Suite through JDBC and open interfaces; Snowflake, Databricks and Fabric read in place; Salesforce, ServiceNow and Workday through their APIs. Write-back through BAPIs, IDocs, REST and web services, acknowledged and logged. |
| Golden record: matching and survivorship | Consolidation: standardise with HANA smart data quality, match with HANA fuzzy search rule sets, calculate the best record with table- and field-level rules (source reliability, recency, completeness), validate and activate; key mapping for cross-system ids [1]. | Strong keys first (VAT ID, DUNS, GTIN, manufacturer part number), then standardised attribute and address matching, with a language model for the hard pairs; two thresholds per rule (review, merge); survivorship per field by source rank, recency, verification and steward override; unmerge restores the sources; every value keeps its source, rule and time. |
| Hierarchies and reference data | Hierarchy processing for cost centres, profit centres and product hierarchies through change requests; SAP Help was unreachable to fetchers, so the specifics are left unlabelled here [4]. | Levels and several hierarchies per entity, kept as versions with validity dates and validated against the facts they aggregate; reference data and crosswalks kept as small domains with the same history, rules and security. |
| Rules, security and audit | BRFplus rules for checks, derivations and matching; PFCG roles and authorisation objects for field-level access; change documents and change-request history; Forrester notes 'remarkable data privacy, security, and global compliance' [1][5]. | Column, row and business rules in one language, evaluated on save and on demand, including rules over aggregates and across tables; twelve security layers for read, write and delete; an append-only audit trail with point-in-time reads and logged reads of sensitive columns. |
| APIs and data services | OData and SOAP services and key-mapping APIs on the SAP Business Accelerator Hub; Joule as the copilot [5][4]. | REST, SOAP, SQL (JDBC and ODBC), events and an agent endpoint over one policy engine; the golden-record lookup answers with the record, the cross-reference and live related facts; page sizes and rate limits published per endpoint. |
| Analytics: pivots, measures, transactions | Analytics through S/4HANA CDS views and SAP Analytics Cloud; pivots and measures live in the analytics and planning products, outside MDG [1]. | Pivots on any hierarchy level with time on the columns and measures in the cells; calculated measures; data entry with disaggregation by weights, equal shares or a time profile; drill-down from a cell to the transactions and to the source row; charts beside grids; natural-language and SQL querying. |
| Pricing unit and trial | Licensing metric unpublished; the cloud-ready mode services (Build Process Automation, Document Management, Data Quality microservices) are licensed separately; the cloud edition can be tried on the BTP free tier; reviewers report per-user and volume-based fees and 'challenging' pricing [6][7][8]. | Platform capacity tiers (32C to 128C); domains, records, attributes and users included; the price is written before the work starts; a guided first domain on your data in one day; the showcase estate for demonstrations; a self-service sandbox tier is a decision pending (see the review notes). |
| Analyst placements 2025–26 | Gartner Magic Quadrant for MDM Solutions, April 6, 2026: Challenger; Forrester Wave MDM Q2 2025: Leader [9][5]. | Analyst evaluation is the purpose of this page set; placements to date: none. The platform pages are organised on Gartner's eight mandatory features and four implementation styles so a briefing lands in the right market. |
Choose SAP MDG when the enterprise runs its transactions on S/4HANA, when governance inside the ERP with change requests and BRFplus is the intended operating model, and when Business Data Cloud is the planned analytics layer. Its native integrity with SAP transactions and its compliance record are real advantages for an SAP-standardised organisation [9][5].
Lima suits the enterprise whose master data should be governed on the rows in place across SAP, Oracle, the CRM and the lakes, with the transactions in the same bed: the golden record and its orders in one query, rules over totals, pivots on golden dimensions with data entry and disaggregation, drill-downs to the source row, and a headless lookup that answers with live related facts. Twelve security layers and an append-only audit trail apply to every door, and the price is written before the work starts.
The domain catalogue shows thirty domains with, for each, the objects read in place in SAP S/4HANA, Oracle Fusion, Salesforce, Workday, ServiceNow, Snowflake and Databricks and the interface used for the write-back.
Facts change; re-check the sources at each review and re-date the page.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.