SAP ECC mainstream maintenance for enhancement packages 6 to 8 ends on December 31, 2027, with extended maintenance to December 31, 2030 at a surcharge; MDG on ECC moves with it, and MDG cloud edition is positioned by SAP as complementary, so the S/4HANA move is also an MDG re-platform decision.
| SAP MDG | Lima master data |
|---|---|
| Entity type | domain in the catalogue (customer, supplier, material, GL account, cost centre…) |
| Change request | proposal in the steward queue, or a SmartApp process where approval levels are needed |
| BRFplus rule | column, row or business rule in one language, tested on live rows |
| Consolidation match configuration | match rules with two thresholds; survivorship per field |
| Key mapping | cross-reference, kept as a join |
| DRF replication | write-back through BAPIs and IDocs, acknowledged; events for other consumers |
| Hierarchy processing | versioned hierarchies with validity dates and validation |
| Change documents | the append-only audit trail, loaded with history |
A manufacturer with MDG for business partner and material on ECC listed 11 change-request types, 140 BRFplus rules and 3 hierarchies. Rules mapped one to one; four change-request types became SmartApps because they needed approval levels; the history of 2.1 million change documents loaded into the audit trail with dates and users. The S/4HANA project kept its scope: master data governance ran on Lima before the ERP cut-over and after it.
They move behind a router one at a time: SOAP consumers get a generated WSDL, SQL readers get views with the same names, API consumers get REST with the same shapes.
Yes, read-only, for as long as your retention policy needs; its history is already searchable in Lima.
The inventory: the count of domains, sources, rules, hierarchies and consumers, written before the work starts.
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.
