February 15, 2011 // By: By Daniel Hardt and Holger Reimer // Keeping Tabs on Master Data
If you’re planning to implement a new solution to manage your master data, make sure you take a close look at the technical prerequisites and the business requirements for each individual master data object. You should also develop a strategy to ensure that the decision will stand the test of time.
Agile and heterogeneous: SAP NetWeaver MDM
Because SAP NetWeaver technology functions irrespective of other software, SAP NetWeaver MDM is especially suited if there’s a possibility that new companies with heterogeneous systems will be integrated at some point. The product provides a suitable and flexible data model for such a scenario. The technology is also recommended if your developers tend to have programming skills in Java rather than ABAP, or if any Web Dynpro experience at the customer is also based on Java. Other criteria include experience with SAP NetWeaver Business Process Management (SAP NetWeaver BPM) or if you are not planning on implementing enhancement package 5.
Homogeneous and static: SAP Master Data Governance
SAP Master Data Governance is a standardized data management tool that you should think about implementing if you use SAP ERP as your master data server and you have already hooked up your own custom developments to optimize processes. These complex validations are usually programmed in ABAP, and knowledge of ABAP – both at your company and your company’s customer – are factors that speak for SAP Master Data Governance. If, for example, you use the object “material” only within SAP Business Suite and in quite a static way, then you can’t go far wrong with SAP Master Data Governance.
For more detailed advice, SAP partner Camelot ITLab provides a checklist that enables the most suitable master data management tool to be selected for each object.