Get Example source ABAP code based on a different SAP table
BEGIN_SECTION VERSION 5 OUT • CL_DBI_UTILITIES ABAP_CLASS END_SECTION VERSION 5 OUT
ABAP_DDIC - Logging Database Tables If logging is activated, any changes to table entries done in AB_SQL are logged in the log table DBTABLOG. BEGIN_SECTION VERSION 5 OUT As a prerequisite, the profile parameter rec/client must be set accordingly. This profile parameter can have the following values:
<(>ALL<)> Logging is client-independent.
<(>clnt1, clnt2, ...<)> Changes are logged only in the specified clients clnt1, clnt2 , ...
<(>OFF<)> No logging. The logs can be evaluated using the transaction Table History (transaction code SCU3). Logging is independent of updates. END_SECTION VERSION 5 OUT If a table row 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 completely here.
Latest notes:
If logging is activated, access to the DDIC database table slows down accordingly. If logging is activated for many DDIC database tables, lock situations can occur for the log table.
No data can be written to a DDIC database table with enabled logging using the statement INSERT with subquery. NON_V5_HINTS
The documented method IS_LOGGING_ON of the system class CL_DBI_UTILITIES can be used to check whether logging is currently switched on for a DDIC database table. ABAP_HINT_END BEGIN_SECTION SAP_INTERNAL_HINT See also <(>https://wiki.wdf.sap.corp/wiki/display/ABAPSECIMS<)> <(>/Table+logging<)>. END_SECTION SAP_INTERNAL_HINT
