Skip to content

ABAP Keyword Documentation →  ABAP - Dictionary →  Classic Objects in ABAP Dictionary →  Database Tables →  Technical Attributes of Database Tables →  Table-Specific Technical Attributes of Database Tables 

Logging Database Tables

If logging is activated, any changes to table entries in ABAP SQL are logged in the log table DBTABLOG. This also requires the profile parameter rec/client to be set accordingly. This profile parameter can have the following values:

  • ALL
Logging is cross-client.
  • clnt1, clnt2, ...
Changes are logged only in the specified clients clnt1, clnt2, ...
  • OFF
No logging.

The logs can be analyzed using the transaction "Table History" (transaction SCU3). Logging takes place independently of updates.

If a table line has more than 16000 bytes, logging is not possible for the table. The lengths of fields with the built-in types STRING, RAWSTRING, LCHR, LRAW, and GEOM_EWKB are counted in full here.

Other versions: 7.31 | 7.40 | 7.54


  • If logging is activated, access to the database table slows down accordingly. If logging is activated for many database tables, lock situations can arise for the log table.

  • No data can be written to a database table with enabled logging using the statement INSERT with subquery.

  • The documented method IS_LOGGING_ON of the system class CL_DBI_UTILITIES can be used to verify whether logging is currently switched on for a database table.