Secure Table Log For Free

The logging flag defines whether changes to the data records of a table should be logged. Use: Every change (with UPDATE, DELETE) to an existing data record by a user or an application program is recorded in a log table in the database.

Procedure Position the cursor in the IMG on the IMG activity for which you want to track changes. Choose Goto Change Log or the Change Log pushbutton. Specify the period you want to analyze, under Restrictions. Choose Program Execute.

Enable table logging. Set profile parameter rec/client = ALL. ... Define tables to be logged. Which tables are important for auditors? ... Activate logging for the defined tables. For some tables logging is set by default, for others set it in the technical settings (transaction codes: SE11 or SE13): Follow ups.

Use transaction SE13 to change the Log data changes flag for these or other tables. For more information, also see SAP Notes 1916 and 112388.

The SCU3 event is used to evaluate the generated logs of SAP tables and objects.

The standard SAP security reports will not record if someone makes a change directly to a table using SM30, or if a programmer writes a program to making changes on the table. Table logging is a track mechanism, that makes possible to record user activity in a system It is useful if you want to know: Who made a change?

... Choose Tools ® ABAP Workbench ® Development ® Dictionary (SE11) in the initial screen. Enter the name of the table whose log settings you want to check. Choose Change. The table is displayed. ... Choose Goto ? Technical Settings. Select/Deselect the Log Data Changes checkbox. ... Choose Activate.