Skip to Content

Central Master-Data Management

Master data is a company asset. The better the data, the better business operation (and the lower the costs)

In addition to enabling reliable cross-group analytics and improving overall master data quality (through the Master-Data Consolidation and Master-Data Harmonization scenarios), companies could want to:

  • Seek support for central, corporate-defined standards for data creation, approval and maintenance
  • Ensure defined data ownership and responsibilities in heterogeneous environments to substantially improve master data quality

SAP NetWeaver MDM enables centralized maintenance and storage of globally relevant master data information and allows subsequent distribution to client systems. It differs from master-data harmonization in that master data is created centrally using the MDM rich clients or SAP NetWeaver Portal.

With SAP NetWeaver MDM, a central comprehensive repository can be created with enriched content that can be used as the single source of truth for all enterprise master data on an inter and intra-enterprise scale.

The main process flow in the central master-data management IT scenario is as follows:


*) Also possible using SAP NetWeaver Portal (iViews)
**) Can be used in addition to MDM Syndicator/Syndicator Batch

In summary, central master-data management provides a single source of record by creating/updating master data centrally on MDM, supported by workflow-controlled approvals and periodic distribution to client systems.

SAP NetWeaver MDM provides the following benefits:

  • Support implementation of company-wide quality standards and data ownership
  • Ensure central control of master data as soon as the data is created
  • Enable federated data maintenance processes by management and synchronization of globally relevant master data information and local completion in client systems

Hope this helps you to see master data management from a scenario and process perspective.

Best regards,

Markus Ganser

You must be Logged on to comment or reply to a post.
  • Where in this scenario is defined what data needs to go to which system ? This is a key aspect of data distribution. ( Think of the ALE distribution model with destinations, data filters, segment filters..) I think this is one of the main outages of SAP MDM in this scenario..


    • Hi Dirk,

      Depending on the use case, there are two main options:
      1. Select the set of records to be distributed to a client system using the search capabilities of the MDM Syndicator.
      2. Distribute only the records that a have a remote key using the "Suppress Records Without Key" feature in the MDM Syndicator.


      • Hi Markus,

        Thanks for your reply..

        I think that option (2) is not relevant as it just shifts the problem to "for which records do you want MDM to generate a remote key". To my knowledge, this is even a functionality that's not yet available...

        Using scenario (1).. This would mean that if SAP MDM would be used to connect to 100 different R/3 instances .. you would have 100 syndications running...  I would think that it would be much better to have one syndicator and have SAP XI handle the distribution and routing. Only downside of that is that XI would not know what "data" has changed so it would not be able to "avoid" sending the same data over and over again...   

  • Markus,

    These days a lot of manuafcturing sites have MES systems which have to be kept in sync with ERP.
    Is MDM able to distribiute data to MES systems as well?- via XI? and xMII? (MES systems = ABB, Siemens, Honeywell. OsiSoft).
    If not is the solution to have interfaces between ERP and MES like in the good alod days?

    • Hi Gabriela,

      Since SAP NetWeaver MDM uses SAP Exchange Infrastructure for data distribution
      in the required target format I don't see an issue with distributing data to
      MES systems.