05.03.2013 Page 1 of 4

SAP Note 1916 - Logging table changes in R/3

Note Language: English Version: 17 Validity: Valid Since 21.05.2002

Summary

SymptomKey word: R3SLMOD - tabTable changes implemented using SM30, SM31, or Customizing transactions arenot logged.

Other termsRSTBPROT, RSTBSERV, RSTBHIST, RSVTPROT, change logs, recordings.

Reason and PrerequisitesControl the recording of Customizing changes.

SolutionAs 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 - arealways recorded. No intermediate buffering of the recorded data isperformed. Therefore, this concept is not suitable for recording ormanaging large quantities of data. Also note that activating the recordingfunction will cause twice as many database updates as before, resulting ina higher DB memory load and performance losses.SAP recommends using the recording function in production clients, in orderto have an exact record of which Customizing tables were changed when. Wedo not recommend using the tool for just any application tables for theabove reasons.The analysis is performed:

o Before Release 3.0: using the RSTBSERV analysis tool (an ABAP/4program), the "History" function. For more information, refer tothe 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 currentday 'Change docs. - selective' - Individual selection 'Tables w/history management' - List of tables w/recording

o 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 menupath: -> Tools -> Customizing -> Tools -> Table logging

o As of Rel. 4.5A: The report RSVTPROT now allows you to carry outthe analysis using Customizing objects (maintenance views, viewcluster or individual Customizing transactions) instead of usingsingle tables.For change logs which have been recorded in a maintenance level upto and including Release 3.1I, log analysis is restricted to thetable level due to technical reasons.

05.03.2013 Page 2 of 4

SAP Note 1916 - Logging table changes in R/3

You can call the tool via the IMG: Postition the cursor on thedesired 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" ismarked.

You can go to the technical settings via Transaction SE13 or via thepath "Tools --> ABAP Workbench --> Development --> Dictionary", enterthe 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 saveand also update these changes.

2. Logging is also set in the system profile. To do this, set profileparameter 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 theclients listed (a maximum of ten).

- ALL: Logging always, for client-specific tables in all clients.Caution: This setting is sensible only in special cases. Notethat with the "ALL" setting or when upgrading all test clients,(including SAP client 000) changes will be recorded in the logfile.

The default settings is OFF - that means, no default logging takesplace.

If rec/client is not OFF and logging is active in the dictionary,non-client specific tables are always logged. This setting is usuallyused in the period of the installation and test phase only.

Please make sure that the values for rec/client are the same on allservers of a system. Only then logging will work correctly.

With the production start, logging tables relevant to accountreporting should be activated (obligation to prove due to nationalorderliness requirements)

Remarks:When importing to the system via tp (or R3trans), logging is possible as ofRelease 3.1H. For further information, refer to Note 84052.Changes are not recorded in a client copy since this would affect theperformance and would require a large amount of additional storageresources in the database.

Header Data

05.03.2013 Page 3 of 4

SAP Note 1916 - Logging table changes in R/3

Release Status: Released for CustomerReleased on: 21.05.2002 11:36:30Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: BC-CUS-TOL-ALO Activity Log

Secondary Components:BC-CTS Change and Transport System

The Note is release-independent

Support Packages

Support Packages Release Package NameSAP_BASIS 620 SAPKB62006

Related Notes

Number Short Text1598473 Substantial growth of DBTABLOG table due to /VIRSA/ZVFATBAK1524924 The table logging issue for ALPFASSIGN1499357 Enhancement of table logging1497672 AIS| Optimization of the report RDDPRCHK1303671 Logging data changes for the table /SAPAPO/TSTROBJR1303588 Logging the data changes for the table TTSTR1265821 RCMGT/RCTRK: Audit Trail of changes1127288 DFPS Procedure when creating a decentralized system1002630 Cannot create transport entries629057 RCX & RCXEM Audit Trail of changes608835 Performance problems due to table logging?566471 Table logging: incomplete display514967 Table logging following change in the code page507595 Activating change logging for Customizing485879 Incomplete evaluation of table change logs455942 Log analysis: Termination TSV_TNEW_PAGE_ALLOC_FAILED439193 No logging for tables PSO31, KNEA423740 Table log analysis: Nonsensical header information360827 Log analysis: Termination SAPSQL_STMNT_TOO_LARGE351494 Profile parameter rec/client: max. of 10 clients323636 Log analysis: Table is not in authorization group139418 Logging user actions

05.03.2013 Page 4 of 4

SAP Note 1916 - Logging table changes in R/3

Number Short Text112388 Tables are subject to logging84052 R3trans: Table logging41300 Table DBTABPRT is very large15184 Error in table logging

Attributes

Attribute ValueTransaction codes DICTIONARYTransaction codes HIERTransaction codes RSTBHISTTransaction codes SE13Transaction codes SM30Transaction codes SM31Transaction codes TRANSAKTIONEN