Skip to end of metadata
Go to start of metadata

With transaction SCU3 you can evaluate change logs of table data records.

  • profile parameter rec/client is set (ALL or 000[,...]) (see transaction
  • tp parameter RECCLIENTis set within the transport domain controller if logging while import should be active
  • 'Log data changes' is set within the technical settings of the table, and the technical settings are activeted for the table (see transaction SE13)
  • an authority group is assigned to the table (see transaction SE54, radiobutton 'Assign Authoriz. Group'

If you put on table logging, than all customizing tables will be logged by default, it is not possible to log only one table, without putting off logging for all other customizing tables within the technical settings. There exists no tool to maintain more tables at the same time, you need to set the flag manually for each table within transaction SE13, and afterwards activate the technical settings. Another possibility is writing an Batch Input program for transaction SE13. 

Please note, within SAP-standard only customizing tables will be logged, therefore there should be no high system load, because the content of customizing tables will not be changed very often in a running system. Therefore it should not be necessary to put off logging for all those tables, but this is your personal choice. Additionally normally those customer entries will be imported from the development system, and this you can control separately, please read SAP-note 84052.
Logging is not designed for mass changes, it means it is not designed for application tables, but for customizing tables.    

For mass changes you can use change documents, see Transaction SCDO.


Note 1916 - Logging table changes in R/3

Note 84052 - R3trans: Table logging 

  • No labels