One can log table changes on Control tables and Customizing tables in SAP. Logging is useful when you want to trace back when a particular table was changed. This function is only recommended on customizing tables and not on master or application tables as there is performance overhead. When table recording is activated, the number of database updates will be double as a "before image" of the record that is being changed is maintained.
To enable table logging:
Call transaction SE13, enter the table name.
Click on change and in the next screen, go to technical settings.
Check the option "Log data changes"
Save the and activate the changes
To activate table logging:
Table logging doesn't begin until rec/client profile parameter is set.
Set teh profile parameter rec/client (on all instance profiles) to
OFF: Generally no recording (non-client specific tables for which logging option is checked are always logged)
nnn: Logging for client-specific tables in client nnn only
mmm,nnn,ppp ...: Logging for client-specific tables in the clients listed (a maximum of ten cleints can be included).
ALL: Logging always, for client-specific tables in all clients.
The table logs are saved in the table DBTABLOG. Make sure that you keep a tab on its size. For analysis of the table change logs use transaction SCU3.
To check which tables are getting logged heavily: In transaction SCU3, select "Administration --> Number of logs (selective)" menu option. Enter a time interval in the selection screen displayed and leave the table selection empty. The result will be a list of all logged tables with the number of recorded logs.