Big4GuyWelcome to Big4Guy.com. Big4Guy is an online resource where I will share with you the latest news, insights, knowledge and some experiences as a Big 4 consultant. We will discuss some of the important issues which organisations are facing today in the areas of information security, security and controls in SAP R/3, Oracle Applications, J.D.Edwards, Peoplesoft and various other ERP's. You will also find information on latest complaince regulations like Sarbanes Oxley, Basel II and so on. Big4guy will also attempt to provide valuable resources for individuals interested in examinations the CISA, CISM, CISSP, PMP and various other security certifications considered essential for entry in any Big 4 accounting, auditing and consulting firms. You are invited to post your comments and viewpoints to posts here. I sincerely hope this online journal will be useful to everyone from a budding student to a professional in the accounting, auditing, management and consultancy professions.
|
Master Data forms the basis of all transactions in SAP. There are many masters in SAP such as the customer master, vendor master, material master etc. Let me put this straight, if your masters are wrong your transactions are bound to go haywire. That is why there is so much stress on master data controls in SAP. As far as master data in SAP is concerned, there can be configuration, manual, procedural, and monitoring controls to check the master data. But our topic for discussion today is some of the common mistakes that occur in master data in SAP.
Improper Access - Inappropriate access to master data is one of the most costliest mistake that can occur. You might have the best manual, procedural controls for your master data, but if the same is not protected from unauthorized access, you are putting your master data to risk.
Lack of Accountability - Mistake number two. Any master in SAP has to become the responsibility of a specific individual in the organization. Of course, there can be many people maintaining the masters, but an officer in the company should be made responsible for each master data table in SAP. Almost 60% of the companies do not have such responsibility specifically assigned to a person.
Inadequate Standards of Master Data Elements - As a best practice, master data elements in SAP should have standards defined. There should be standard naming conventions defined for all master data elements. Periodically, someone should download all master data tables and checked them against naming conventions set.
Lack of Segregation of Duties - Segregation of Duties takes imprtance with master data. There should be adequate SOD defined while handling master data. I have personally seen in many companies that the person responsible for handling transactions in SAP is also responsible for maintaining master data. Adequate segregation of duties can go a long way in controlling your master data.
Lack of Configurable Controls - Many companies do not make full use of configurable controls available in SAP for controlling their master data. Configurable controls are designed to maintain the integrity of master data. If your configurations are messed up, there is no way your master data can be correct. My advice is get your configurations correct, all else will follow.
More on SAP >>
Sales Order Cycle , List of Sales Orders , Available to Promise Quantity
No Comments for this post yet...
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| << < | > >> | |||||
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||