DAMA - SAP MDG: Concept #9

❗️The Problem

People treat master data like a tech object:

  • “It’s in MARA.”

  • “That’s a vendor from LFA1.”

  • “Customer number 10000217 is fine.”

But no one agrees which system is the source.
No one knows who updated it.
And every report gives different numbers.

Why?
Because master data was treated like IT housekeeping — not a strategic asset.


🧠 What DAMA Actually Means by “Master & Reference Data”

  • Master Data = the key “nouns” of your business
    (Customer, Product, Supplier, Employee...)

  • Reference Data = controlled vocabularies used across the org
    (Country codes, Payment terms, Product categories...)

But DAMA goes deeper:
It says this is the data that everything else depends on.
It must be:

  • Shared

  • Stable

  • Governed

  • Clear

  • Trusted

If transactional data is the bloodstream —
master data is the identity.


Key Concepts in DAMA

ConceptWhat It Means
Golden RecordThe single, trusted version of a business object
Data DomainsLogical groupings like “Customer”, “Product”, “Location”
HarmonizationMaking the same object consistent across systems
ConsolidationMerging duplicates, resolving conflicts
DistributionSending master data where it’s needed — reliably and timely

🔧 In SAP MDG: This Is the Core

SAP MDG exists exactly to operationalize DAMA’s vision for master data.

DAMA TermSAP MDG Component
Golden RecordStaging + Approval Process + Replication
Data DomainsBP, Material, Supplier, Custom Objects
HarmonizationFlex modeling, validations, value mapping
ConsolidationMatch/Merge tools, Duplicate Check, KMC
DistributionSOA/ALE/SLT Replication to target systems

But SAP doesn’t give you the strategy — only the tools.
You need to define:

  • What is a “trusted record”?

  • Who maintains it?

  • What systems depend on it?

  • What happens if it changes?


⚠️ What Goes Wrong

  • Every system has its own version of “the customer”

  • Material created by copy-paste from old ones

  • Suppliers exist 6 times under slightly different names

  • Analytics show fake precision with dirty core data

And the worst part:
The business doesn’t trust the data. So they work outside the system.


🧠 Questions That Drive Master Data Clarity

  • What are our critical data domains?

  • Do we have a golden source — or just systems that shout the loudest?

  • Are our reference values consistent across systems and countries?

  • Can we trace who changed a master record — and why?

If not, you’re not doing MDM. You’re just syncing noise.


💬 Bottom Line

Master data is not about centralizing tables.
It’s about creating one version of the truth — and making sure everyone uses it.

Without it, no workflow, report, or AI can be trusted.
With it, you build a business that runs on clarity.

0
Subscribe to my newsletter

Read articles from Dzmitryi Kharlanau directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Dzmitryi Kharlanau
Dzmitryi Kharlanau

SAP Logistics Consultant with 10+ years of experience in SAP SD, SAP MM, SAP LE, and SAP IS-Automotive. Skilled in SAP system support, integration, and process improvements. Achievements ✔️ Delivered custom logistics solutions, overseeing the entire process from concept to go-live. ✔️ Achieved SLA compliance in JIT environments, managing tasks from requirements to release independently. ✔️ Resolved complex issues swiftly, minimizing downtime and optimizing efficiency. Interests: Motivated to work with 🔧 S/4HANA SD, MM, BTP, and ABAP, taking responsibility for end-to-end solutions.