Page tree
Skip to end of metadata
Go to start of metadata

What is table logging?

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?
What was changed?
When was the change made?

In order to use table logging you need to do 2 steps:

  1. You must set the profile paramter rec/client on all application servers if you have more than one.
      As the parameter rec/client is used for controlling table logging at R/3 system level.
      This is a very important step because if it is disabled and if you activate the table logging  in Technical Settings for any table, it won’t log the data changes to that table.

  2. Activate the technical settings of the table - you can do this in transaction SE13.

Using the logging flag you can define whether changes to the data records of a table should be logged.
If logging is switched on, any changes of table data(with INSERT, UPDATE, DELETE) by the user or application program is recorded in the database in a log table DBTABLOG

Please note that the table logging is not designed for massive changes but rather for manual changes to customizing tables.
If you want to record the massive changes, please use the change documents.

You can create change document object and its associated updater module following this path

Tools -> ABAP Workbench -> Development -> Other Tools -> SCDO - Change Documents

Useful SAP notes

1916        Logging table changes in R/3
84052      R3trans: Table logging 
608835    Performance problems through table logging?

  • No labels