Skip to Content

SAP MDM for CMDM-

The prerequisite for CMDM is that other two scenarios has already been implemented which are COnsolidation of Master data and Harmonization to target systems. In a central hub MDM implementation any creation, Update, deletion of a master record has to be performed in SAP MDM first and then syndicated to remote systems-ECC. While implementing CMDM we come across following limitations in SAP MDM:

  1. Global Vs Contextual Data- One of the key challeneges in MDM project is to decide which attributes will be part of MDM data model. As suggested by SAP only global attributes should be in MDM. The limitations can be further categorized as following-
  • Nested Qualified/Tuples not supported.
  • Validations/Assignments/Matching strategies not supported for Qualifiers.
  • CHange tracking not supported for Qualified fields.

    2.   User Interface for CRUD operations- MDM GUIs are not very user friendly and has following limitations-

  • Use of Constraints/Masks very limited required for controlling access.
  • COntrolling display of sensitive fields to users.
  • Controlling access for modifications in matching strategy in Data manager.
  • ………..

Above limitations require development of Portal UI which further requires gretaer time/efforts. Portal acts as a thin client for managing the CRUD operations on MDM database for specific repositories.

3. Processes around Master data- Implementing CMDM implies also mapping the processes existing around master data, like governance rules, Approval workflow. This can be achieved via MDM native workflow which have following limitations-

  • Fixed roles and Users for tasks
  • Parallel steps not supported
  • Limited workflow history and performance
  • Limited features in Notification Steps, sending customized information is not possible.

4. Deriving the number ranges

MDM supports numbering for master records either based on Auto ID(calculated fields) or by defining remote systems with Key generation. Neither of the two methods supports external number generation which is pretty much used for some of the Customer and Vendor account groups.

Suggestion– Seeing the limitations above we can opt to use MDM for CMDM only when the Data model, Processes, Governance etc are kept simple and restricted to mostly Global attributes. A very feasible design is use CMDM for the global attributes only and for the local attributes( Sales data, Purchasing Org data etc) develop governance processes in the local systems like ECC.

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Markus Ganser
    Thanks for this interesting blog. I’d like to add two things with regards to central MDM scenarios:
    For CMDM scenarios in heterogenous landscapes, the native SAP NetWeaver MDM coverage can be considerably enhanced when using a joint approach based on SAP NetWeaver MDM and SAP NetWeaver BPM. See, for example, the Enterprise Master Data Management article.
    For ready-to-run governance in SAP environments involving a high degree of inherent business logic, you can resort to SAP Master Data Governance. See, for example, the blog about Governance for Financial Master Data
    (0) 
    1. Ravi Kumar Post author
      Thanks for your comments. Using BPM we can definitely link to multiple applications for accessing the local data or defining processes around the local data.
      I would again reiterate-SAP MDM alone is not suitable for CMDM as there are multiple limitations.
      Best regards
      Ravi
      (0) 
    2. Ravi Kumar Post author
      Thanks for your comments. Using BPM we can definitely link to multiple applications for accessing the local data or defining processes around the local data.
      I would again reiterate-SAP MDM alone is not suitable for CMDM as there are multiple limitations.
      Best regards
      Ravi
      (0) 
  2. Sergio Ferrari
    This is for sure an interesting topic.
    It would be useful to clearify what we mean with CMDM.
    It’s very important to have a common understanding about the set of information that should/could be centrally maintained.
    About Vendors for example, in add to the general data, do we consider also the accounting specific set of information depending on each company code part of the scenarios or not?
    And the same, what about purchasing attributes that depend on each purchase organization?
    About Customer we have the same with company and sales organization related attributes.
    And about Material, wow, we have several different views dependent on several organization levels.

    IMHO, CMDM limited to general data is still very ambitious but CMDM extended to all the views (accounting/purchasing accounting/sales) is not yet feasible in most of the environments.

    Sergio

    (0) 
  3. Shachar Sagi
    Hi Ravi,

    Most of the limitations that are mentioned in your blog are no longer relevant in MDM 7.1

    * Modeling: the newly introduced tuple data type enables you to model almost everything you like with any nesting level.

    * GUI: MDM WebDynpro components which were introduces in MDM 7.1 SP4 and SP5 (Search, Result Set, Item Details, Compare, Match and merger) enable the creation of configurable, intuitive and extensible Web UIs with low development effort.

    * Processes around master data: NW BPM integration is easier than ever using WD Components and WS Generator.

    See these blogs and how-to guides for more information:

    How to Build Web Applications Using MDM Web Dynpro Components.
    SAP Master Data Management (SAP MDM) – EIM – SAP Developer Network

    How to Integrate Master Data Management (MDM) and Business Process Management (BPM).
    SAP Master Data Management (SAP MDM) – EIM – SAP Developer Network

    MDM Quick Starter Package – Collaborative Creation Process for Material Master Data.
    http://www.sdn.sap.com/irj/scn/downloads?rid=/library/uuid/e02beaec-d01e-2d10-f780-b92e5def23c4

    Benefit Now From Support Package 5 for SAP NetWeaver MDM 7.1
    Benefit Now From Support Package 5 for SAP NetWeaver MDM 7.1

    Regards,
    Shachar

    (0) 

Leave a Reply