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 are logged in the log table DBTABLOG. This also require 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 there are more than 250 characters in the table key or if a full table row has more than 16000 bytes, the table cannot be logged. The lengths of fields with the predefined types STRING, RAWSTRING, LCHR, and LRAW are counted in full here.

Other versions: 7.31 | 7.40 | 7.54


Note

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.