Changing Table and Data Element Logging
Use
This function enables you to:
Prerequisites
To create change documents, and therefore change the logging setting for data elements, the underlying table must be included in a change document object. In addition, this change document object must be implemented in the application in which the data change is to be logged. If this is not the case, only the table as a whole can be logged.
The system defines whether a table is contained in a change document object, and whether this is implemented in the application. This can only be changed by modifying the system.
Features
Where-used list
For the selected data element, you can first access a where-used list. Here, the system determines which tables use the data element. However, it only takes into consideration tables that are assigned to a change document object.
When the change document objects are checked, the system only takes account of registered change document objects, that is to say, those that were created with transaction SCDO.
As a result of this check, the system displays a list of the tables and table fields in which at least one of the selected data elements is used.
Access the where-used list before every change to the logging setting to determine possible effects on other tables.
Logging setting for data elements (change document creation)
Once you have selected a table, you can select one or more data elements and activate or deactivate the logging of changes made to the table fields that are linked to this data element.
If a change document object does not exist for the selected table, the system displays a warning. Generally, a change to the logging setting has no effect where this data element is concerned (exception: use in non-registered change document objects).
If you change the logging setting of a data element, this takes effect across the whole system on all table fields that are based on this data element.
You can only change the logging setting if the selected data element is not locked by another user or request. When you save the changed setting, the system first creates an inactive version of the changed data element. When you activate the settings, the system creates an active version of the changed logging setting.
Change logging settings for whole tables
In addition to change document creation, you can select a table, and activate or deactivate logging by selecting or deselecting the logging indicator. Here, too, when you save, the system first creates an inactive version, which then has to be activated.
Activate changed objects
Depending on your authorizations, the system uses different methods to activate the inactive objects.
Case 1: You have authorization for the mass activator:
In this case, after you save, the system starts the mass activator. You can process the changed objects with the functions available in the mass activator.
Case 2: You do not have authorization for the mass activator:
In this case, the system activates the inactive objects in the background. You cannot access the objects.
You can choose Goto ® Activation logs to display the logs of all objects activated in the system with the mass activator. For this, you need the following authorization:
S_DEVELOP: DEVCLASS=SDBT; OBJTYPE=PROG; OBJNAME=RADPROTA; ACTVT=03;
S_PROGRAMM: ACTVT=SUBMIT
Assign table to a transaction
Once you have finished changing the logging setting for tables or data elements, you can assign the changed table or changed change document to a transaction. It then appears in the structure tree under Own assignments and can therefore be accessed more easily at a later date. In addition, the changed table or related change document object is displayed in the SAP Easy Access Menu under the assigned transaction.
You can also assign tables or change document objects to transactions in transaction AUT01. However, we recommend that you use transaction AUT02 for this as it contains a wider range of assignment features.
Icons used:
The following icons indicate the object status. The icons appear in transaction AUT01 next to the description of the table or data element.
Configuration already completeThe logging setting of this table or data element has already been changed with transaction AUT01 and the object activated.
Already changedThe logging setting of the table or data element has been changed, but the change has not yet been saved.
Inactive version existsThe logging setting of the table or data element has been changed and saved. In addition to the previously active version, the database contains a changed version with an inactive status. For the change to take effect for the object, you must activate it using the
mass activator.
Object lockedThe table or data element is currently locked from processing (by another user or request). Wait until the object is released for processing.
ChangeableYou can change the logging setting of this object.