Skip to Content

What to consider when planning to achieve clean master data management in SAP R/3 Series Part 1 of 3

What to consider when planning to for clean master data management in SAP R/3 Series Part 1 of 3

The definition of master data management comprises of terms such as data quality, governance, processes and standards. For those of us experienced with implementations for large enterprise customers running SAP are aware of the growing volume of data being entered into SAP on a daily basis with limited process control resulting in duplicate and incomplete records.

•     So how do we talk to our customer about the need to improve data quality?
•     Or introduce the subject of data governance and standards to the CIO?

Broach the subject of master data management across all IT systems and applications, one may receive a look of disbelief then the silent response;  finger (hopefully the index finger), door, now.

We understand our customers need to do something about improving their SAP data, so what options to they have which can be implemented in a short time scale (6-8 weeks), focus on a problem which can be fixed and most importantly bring satisfaction to the business users giving kudos to the IT stakeholder and you the chance to be chargeable another day.

Here are a few simple points to consider to help achieve clean master data in SAP

•     Don’t introduce fluffy, high in the sky diagrams – give practical examples and pick an area which causes the most business pain.
•     Obtain business stakeholder interest and commitment
•     Budget for master data initiative – don’t forget about data cleansing

SAP master data management, data cleansing, data management, workflow, notifications, naming standards, EOTD, SAP Materials Master, SAP Customer Master, SAP Vendor Master, SAP Bill of Material.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.