How to Enable Database Table Logging and analyze the log records using Transaction Code SCU3


3)     Enable LOG DATA CHANGES FLAG in Technical Settings of Table using SE13

In this step, set the Log data changes flag for the tables that we want to have logged. Once this enabled, the table log changes will be logged in the table DBTABPRT.

4)     Check logs using the transaction SCU3.

Finally, if there are any data changes made to the customizing table, we can view the logs.

In the next screen, enter the Customizing Object/Table name as shown in below screenshot.

After that click on execute and it will show the data changes as follows.

In case, the given selection criteria (Date Range, Table Name) does not contain any data changes, it will show the result as follows:

IMPORTANT NOTE: Logging slows down accesses that change the table. First of all, a record must be written in the log table for each change. Secondly, a number of users access this log table in parallel. This can cause lock situations although the users are working with different application tables.

P.S.: This document does not recommend that table logging should be enabled for all the tables. This is just to show that how to enabled it and analyze the data changes to the important customizing tables.

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image