Table changes implemented using SM30, SM31, or Customizing transactions are not logged.
As of Release 2.1, you can record changes to the following tables:
- Control tables (system logic control)
- Customizing tables
"Before images" - thus, the complete set of entries before the change - are always recorded. No intermediate buffering of the recorded data is performed. Therefore, this concept is not suitable for recording or managing large quantities of data. Also note that activating the recording function will cause twice as many database updates as before, resulting in a higher DB memory load and performance losses.
SAP recommends using the recording function in production clients, in order to have an exact record of which Customizing tables were changed when. We do not recommend using the tool for just any application tables for the above reasons.
The analysis is performed:
- Before Release 3.0: using the RSTBSERV analysis tool (an ABAP/4 program), the "History" function. For more information, refer to the online documentation for program RSTBSERV.
You reach the tool via the following menu:
-> Tools -> Case -> Maintenance
-> Comparison utilities -> Table analyses
-> Function "History" (as of Rel. 2.1F)
-> 'Change docs. - Daily evaluatn' - Changes from the current day
'Change docs. - selective' - Individual selection
'Tables w/history management' - List of tables w/recording
- As of Release 3.0: using the RSTBHIST tool. Via the menu interface, you reach the tool (only as of Release 3.0D) by using the menu path: -> Tools -> Customizing -> Tools -> Table logging
- As of Rel. 4.5A: The report RSVTPROT now allows you to carry out the analysis using Customizing objects (maintenance views, view cluster or individual Customizing transactions) instead of using single tables.
For change logs which have been recorded in a maintenance level up to and including Release 3.1I, log analysis is restricted to the table level due to technical reasons.
You can call the tool via the IMG: Postition the cursor on the desired Customizing activity and select 'Goto -> Change log' (button 'Change log').
For further information, refer to the program documentation.
For a table to be logged, 2 requirements must be met:
1. In the technical settings of the table, checkbox "Log data changes" is marked.
You can go to the technical settings via Transaction SE13 or via the path "Tools --> ABAP Workbench --> Development --> Dictionary", enter the table name and click on "Change". On the next screen, click on "Technical settings" (Ctrl+Shift+F9).
If you change the technical attributes of a table, make sure you save and also update these changes.
2. Logging is also set in the system profile. To do this, set profile parameter rec/client (lower-case!) to one of the following values:
OFF: Generally no recording (e.g. central system switch)
nnn: Logging for client-specific tables only in client nnn
mmm,nnn,ppp ...: Logging for client-specific tables in the clients listed (a maximum of ten).
ALL: Logging always, for client-specific tables in all clients. Caution: This setting is sensible only in special cases. Note that with the "ALL" setting or when upgrading all test clients, (including SAP client 000) changes will be recorded in the log file.
The default settings is OFF - that means, no default logging takes place.
If rec/client is not OFF and logging is active in the dictionary, non-client specific tables are always logged. This setting is usually used in the period of the installation and test phase only.
Please make sure that the values for rec/client are the same on all servers of a system. Only then logging will work correctly.
With the production start, logging tables relevant to account reporting should be activated (obligation to prove due to national orderliness requirements)
When importing to the system via tp (or R3trans), logging is possible as of Release 3.1H. For further information, refer to Note 84052.
Changes are not recorded in a client copy since this would affect the performance and would require a large amount of additional storage resources in the database.