Dear,
Data Accuracy means - perfect and exact definition of master data in system reflecting the business.
Master Data is something that can be reused in transaction processing.
I think an example will make it easier to understand. Typically there are hundreds of attributes of a simple thing like customer. To begin with there is always a name , physical address, email address and other contact details. To further elaborate customer may have specific locations where they want products to be delivered. They may have specific conditions controlling their taxability. There may be more than one contact person for a specific business organization acting as customer. There may be a different billing address v/s shipping. If we get into details , we can define hundreds of fields to represent a customer in an business oriented IT system.
It will be so much waste of time (and effort) if all these fields are to be reentered every time a new sales order is received from a specific customer. Alternatively , we can maintain all this data once in one place and may be assign a number to this customer data set. This number can be used while processing say order booking transaction. By virtue of using a single number in order booking , we can tell system to copy all the relevant data in the sales order. Most of this data is defaulted to begin with and is allowed to be changed in the transaction eg shipping address is defaulted and if the custom wants a different address for the specific order under progress , the address can be changed on the fly.
However , it wouldn't make any sense to maintain master data objects if there is no reuse. More reuse , more value.
The power of SAP R3 (ECC) lies in definition and structure of its master data objects. The success of an SAP R3 implementation vastly depends upon the extent and accuracy of master data maintained.
Most parts of a business transaction can be automated if proper master data is pre-maintained. But some times its a chicken egg story. We can't get the users to start entering master data till they see the value of system. But they can't see the value of system till the master data is maintained accurately. This is a bridge that every implementation team goes thru and one of the biggest challenge in adoption. There are number of tools available to bring the data from legacy systems. These tools can automate many manual parts of data transformation but no tool can replace the human judgment on data accuracy and field mapping still remains an a work of experienced consultant.
Some of the most commonly used master data objects on SAP R3 are
Customer Master
Vendor Master
Material Master
Pricing data ( and other condition records)
HR Master Data
Bill of Materials
Standard Networks
Standard WBS
Work Centers
Regards,
Syed Hussain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.