Activating Table Change Logs in the System. Transaction SCU3
Activating Table Change Logs in the System. Transaction SCU3
Explanation of the Issue
You logged into the system to analyze table change logs (let’s assume that), using transaction SCU3, but received the following message:
A similar situation occurs if you choose the command Goto -> Change log in the SPRO context menu.
Let’s figure out how to enable these logs.
Solution
Modify the rec/client parameter for your system profile. This can be done via transaction RZ10.
An example of modifying the system parameter in the profile is presented in the note: Problems When Launching a WebDynpro Application.
The rec/client parameter can take the following values:
- ALL – if you want to activate logging in all available clients of the system;
- client1, client2, client3 – if you want logging only in the specified clients of the system.
N.B. Pay attention: using the ALL parameter may negatively affect system performance.
N.B. After making changes to the system profile, you must restart the application server.
See: REC/CLIENT Parameter in the System Profile
See: Setting Rec/Client Parameter for Logging
Check the results by launching transaction SCU3 for the table you're interested in.
For more information, refer to SAP Note 2437986 - SCU3 | How to enable logging in the system
See also the PDF version of the above SAP Note: SCU3 | How to enable logging in the system