Skip to Content

SAP Master Data Management – Info Update

SAP Master Data Management has evolved from a single product to a holistic solution suite facilitating all master data scenarios and use cases, both in SAP Business Suite-centric environments and heterogeneous multi-system landscapes.

In this Webinar, SAP MDM Vice President, Gerd Danner, provides you with an up-to-date picture of SAP’s MDM solution portfolio and informs you about what is planned in the near future. In particular, the Webinar will cover the following topics:

SDN Webinar – Agenda 

SAP Solutions for Master Data Management –
Info Update 

October 5, 2010

15:00 – 16:00 GMT
17:00 – 18:00 CEST (GMT + 02:00)08:00 – 09:00 Pacific Time (US & Canada)

1. Master Data Management – Brief Introduction 

2. SAP Solutions for Master Data Management – Overview 

3. Release-specific Information 

4. Summary 

5. Q & A Session

To join the 1-hour SAPConnect session, please find the following dial-in information:

Session Link: 

Participant Code:


Telephony Information:



  • Germany, Frankfurt: +49 69 71044 5497
  • Switzerland, Zurich: +41 43 456 9604
  • UK, London: +44 20 7153 9921
  • France, Paris: +33 1 70 99 43 40
  • Italy, Milan: +39 02 3041 0328
  • USA, New York: +1 212 999 6675
  • Brazil, Sao Paulo: +55 11 3351 7063
  • China: +86 400 810 2682
  • India, Bangalore: +91 80 6127 5001
  • Japan, Tokyo: +81 3 5767 9356
  • Singapore, Singapore: +65 6622 1189
The Webinar will be held in English.
You must be Logged on to comment or reply to a post.
  • Hi,

    Thanks for an informative session. It would be great if you can please address the following questions regarding Enterprise and Embedded MDM positioning:

    1. From the roadmap presented, SAP is looking to offer MDG based applications for central management of master data objects in ERP6 EHP4 and beyond. What about roadmap for central MDM applications based on BPM/NW MDM?

    2. In case of Embedded MDM, when a customer uses multiple business suite applications, e.g. CRM, SRM, E-Recruiting, etc with different data models, which data model will be considered master?

    3. It was mentioned that a common technology foundation will be developed for both Enterprise and Embedded MDM. Which workflow tool will SAP use in this case, SAP workflow or BPM workflow?

    4. What is the advice for customers who have started investing heavily in developing Central MDM applications based on NW MDM and BPM? If SAP plans to deliver central MDM functionality based on Embedded MDM, and if it is fit for purpose, is there any value in development using Enterprise MDM?

    Thanks and regards,


    • Hi Shehryar,

      Thanks for the feedback. See my comments as follows.

      cf 1: 
      As of SAP NetWeaver MDM 7.1 SP 4 and SP 5 there is a tight integration with SAP NetWeaver BPM , and a Quick Starter Package for Collaborative Material Data Creation (based on NW MDM and BPM) has been provided. Additional Quick Starter packages are planned.
      Generally, NW MDM and BPM provide a flexible infrastructure for collaborative MDM scenarios in heterogeneous landscapes.

      ERP data models are the basis

      In enterprise MDM there is a need for cross-system workflows, for which BPM is the perfect technology foundation. As embedded MDM is on top of the SAP Business Suite it is logical to use SAP Business Workflow.

      cf. 4:
      SAP NetWeaver MDM and BPM are particularly suited for collaborative master data creation/maintenance scenarios in heterogeneous landscapes, but are also applicable in SAP contexts. Generally, embedded MDM relates to an out-of-the-box application with re-usability of SAP Business Suite logic (validations. etc) while scenarios based on SAP NetWeaver MDM and BPM are a flexible infrastructure for MDM scenarios with focus on globally relevant (identifying attributes). Generally, when SAP NetWeaver MDM and BPM is a fit, there is no need to change horses midstream. 

      • Hi Markus,

        Thanks for the clarification. Much appreciated. Follow up questions on 1, 3 and 4 above:

        1. While Quick Starters are planned, these are not standard SAP solutions for Central MDM on top of BPM+NW MDM. For these quick starters, there is no formal delivery channel, support, or roadmap. Consequently, customers essentially have to resort to 100% custom developed solution if they want Enterprise MDM. Please correct me if I am wrong.

        3. If enterprise and embedded MDM use different workflow tools and run on different application server environments, what does the notion of common technology foundation for both mean?

        4. I agree that there is no need to change horses midstream. However, if a customer has to breed the horse before they can actually take it to the race course, building custom apps for central governance on BPM+NW MDM in this case, I think it makes sense to re-evaluate the TCO of both approaches. As it stands today, there is no standard offering from SAP for Central MDM based on BPM+NW MDM. However, SAP is planning to offer Central MDM through embedded MDM. The question is: if the functionality being delivered through embedded MDM roughly matches 40-50% of customer requirements, the rest 50-60% being fulfilled by custom development/enhancement, is it better than a 100% custom developed solution or not? I know you can’t address this question since it depends on customer requirements. Hence, it is becoming even more important for customers to understand the product roadmap and re-evaluate their investments in MDM products from SAP. Introduction of embedded MDM has created some confusion in understanding the value for money of an Enterprise MDM solution. Using NW MDM for typical data cleansing and consolidation tasks is fine. But building applications on top of it, with significant custom development, is something to be evaluated. You have hit the nail when talking about re-usability of SAP Business Suite logic (validations. etc) in embdedded MDM. To replicate standard and extended validations in NW MDM is a significant undertaking. What I’d have expected from SAP was ease of consumption of standard SAP validations from the outside (BPM). On the contrary, SAP has decided to invest in embedded MDM based central MDM processes. The question customers have to ask is: if SAP is not investing in Central MDM applications based on Enterprise MDM by offering out of the box solutions, should the customers continue on this route? A clear roadmap for Central master data management applications on top of Enterprise MDM will address this question I think.



        • Dear Shehryar,

          Thanks for your latest feedback. Let me comment as follows:

          cf.1: Generally, infrastructure components (such as NW MDM and BPM) need more configuration and implementation work than out-of-the box solutions. That’s the nature of generic components. That’s why we help customers by
          providing quick starter packages as implementation templates to help accelerate
          MDM implementations and the time to value. When these are adopted by customers, there is a good chance for inclusion into the standard. For example, as of SAP NetWeaver MDM 7.1 SP05 great parts of the Quick starter content have already been included in the standard delivery. Additional implementation templates are planned (see also the information about rapid deployment solutions).

          cf. 3: As of today, certain use cases may in fact require different workflow techniques.
          But common foundation means that there is an overarching concept to tie these together. For example, in an end-to-end governance scenario, SAP NetWeaver MDM can be leveraged as enterprise MDM hub keeping the enterprise-relevant (identifying) attribute sets. This can be complemented with SAP MDG to extend the master data information to SAP ERP-relevant attribute sets. The entire process can be controlled by single-workflow governance based on SAP NetWeaver BPM.

          cf. 4:
          Obviously, there are cases where the option whether to use NW MDM plus BPM or SAP Master Data Governance is quite clear based on the prevailing system landscape, based on the data domain that is involved, or simply based on the philosophy pursued in a specific organization: If a company generally sees MDM as an application-agnostic strategy, they’d tend to resort to infrastructure components and enterprise MDM (where, by the way, the SAP NetWeaver MDM Business Content may also be helpful in accelerating implementations), if they see master data as an integral part of the application, they’d probably prefer out-of-the-box solutions and embedded MDM.
          It is also obvious that there are borderline cases which require a closer look. But no
          matter how an architecture expert decides after analyzing the context in a specific case, SAP’s MDM strategy is to have the best of two worlds combined into a solution suite with investments continuing in both enterprise MDM and embedded MDM.

          This discussion is very rich, so I’d recommend to shift it to the MDM discussion forum.

          Thanks, Markus

  • Hi,

    Is there a video recording of this session available? It will greatly benefit those who could not make it to the session.



  • Markus,
    As mentioned in the webinar, it appears that several customers are already using Embedded MDM (MDG)for Financials.
    Is there any documentation available for MDG?
    I understand MDG will be built upon SAP Business Suite but looking for some more information on the architecture and usage of MDG.