• SAP Data Quality
• Articles

Auditing Users Who Change Values

Key Takeaways

⇨ SAP provides change document tables (CDHDR and CDPOS) that track modifications to system data, allowing auditors to review process changes and identify responsible users.

⇨ Standard SAP transactions like FB04, MM04, and specialized reporting tools such as SCDO and S_ALR_87101238 help streamline the review of change documents, reducing the need for manual data searches.

⇨ Using broader search transactions instead of material-specific queries enhances auditing efficiency, enabling security teams to track changes by user ID across multiple materials or documents.

Performing change document reviews is a crucial part to auditing the processes, controls, and risk landscape of your SAP systems. There are two tables delivered by SAP that allow you to easily locate change documents and identify users that perform changes.

Performing change document reviews is a crucial part to auditing the processes, controls, and risk landscape of your SAP systems. There are two tables delivered by SAP that allow you to easily locate change documents and identify users that perform changes.

You can (and should) verify that only specific users are authorized to maintain data by checking various repository tables.

SAP Delivered Transactions

Explore related questions

Ask SAPi

what is this?

SAP delivers many Change Document related transactions. Many of them have “04” appended to the transaction code; for example, FB04 (Financial Document Changes). On the backend, there are two tables that contain the overall history of modified documents:

• CDHDR (Change Document Header)

• CDPOS (Change Document Items)

For example, a user has changed the Material Group field value from “01” to “02” with transaction MM02 (Change Material):

As a SAP Security resource, you need to identify who has changed this value (HINT: Change Documents!). In transaction MM04, you have the ability to pull change documents for Material data changes. The issue is: you need to define a specific material code. In this situation, it is nearly impossible to find all materials changed by a specific user. If you get lucky and execute the search for the correct material you get:

 

If you don’t get the Material correct:

If you wanted to avoid the onerous task of checking each material individually, it would be beneficial to use a subset of transactions such as SCDO, SCDN, S_ALR_87101238, and S_ALR_87101239.

Within S_ALR_87101238, you are allowed to specify all materials for the user ID you want to audit instead of being forced to define a Material first.

Learn more with Markgraf Consulting.

• 
  • SAP Data Quality

  10 Ways Microsoft Excel® Can Speed Up Your SAP® Processes & Improve Data Quality

  Reading time: 1 min

• 
  • SAP Data Quality
  • Premium

  How to Change Infotype Data Using Standard Classes and Methods

  Reading time: 18 mins

• 
  • SAP Data Quality
  • Premium

  Enhance Data Quality in Real Time Using SAP Data Quality Management Software

  Reading time: 10 mins

• 
  • SAP Data Quality

  Auditing Users Who Change Values

  Reading time: 1 mins