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

In this article, we will learn how to enable the database table logging and how to analyze the log records using transaction code SCU3. Purpose of Table Logging: In order to track the DATA CHANGES to the customizing data (and/or even other types of data). (Field changes to the tables can be tracked from version management)

Using the logging flag we can define whether changes to the data records of a table should be logged. If logging is switched on, each change to an existing data record (with UPDATE, DELETE) by the user or application program is recorded in the database in a log table ( DBTABPRT). Steps to be followed: 1) Check if your SAP R/3 system has the logging option enabled or not This is very important step because if it is disabled and if you activate the table logging in Technical Settings for any table, it wont log the data changes to that table. In order to verify if our R/3 System has the table logging flag set or not, we can use the REPORT RSPARAM which displays all profiles in the system with their values. The parameter rec/client is used for controlling table logging at R/3 system level.

Click on Execute and following screen will appear.

Again click on Execute and it will display the following screen. Then Search the parameter rec/client and check the values as follows:

In this case, it is disabled. We can see that the values are set as OFF.

2) Enable the Table logging by Setting the parameter REC/CLIENT If you found that in step 1) that SAP R/3 system does not have the logging enabled, you need to ask your BASIS team to do it for you. Once they did it for you, you can repeat the step 1) and it will look like as follows:

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.