Master Data CRUD Usability in SAP
I have seen this over and over. Many companies that choose to implement Master Data Governance, end up creating a centeralize Center of Exellence (COE) team to take care of this on behalf of the actual business users. This has been seen specially in many companies that have implemented SAP.
SAP is a great ERP tool and now has begun to invest heavily in the MDM arena. Netweaver MDM is still maturing, but has great potential. One thing that is missing in MDM is consideration for audience. It is as if, the designers of MDM have designed it particularly for a COE audience. It is too technical for say a product manager to create its material within MDM or a sales person to create customers and manage them there. You may say, well they can do it in ECC, but that integration is not as seamless as it should be.
This is more important when it comes to data quality control in SAP. Duplication and cleansing reports should be built in the back and be seamelss to the users. Even though MDM and ECC could be as part of a tightly coupled architecture, they still don’t feel that way to an end user.
SAP has certainly taken the right step toward stronger data management and model capabilities by investing in MDM. In order for NeWeaver MDM to be a successful product, however, it should be a part of a longer term strategy that seamlessly integrate its fucntionaly with ECC. This would allow the CRUD process operations for master data to get back to the users who actually need this data rather than a group of represntatives in a COE organization.