Show TOC

Function documentationComparison Between Customer System and SAP System Locate this document in the navigation structure

 

With this function, the system compares the logging setting (logging yes or no) for tables and data elements in the SAP system with customers' own settings. It runs automatically each time the transactions Change Configuration of Logging (S_AUT01) and Display Configuration of Logging (S_AUT03) are started.

Note Note

Only objects that were configured with the transaction S_AUT01 are compared.

End of the note.

Prerequisites

For the comparison to deliver a meaningful result, you must first have changed the logging settings for tables, data elements, or long text tables at least once using the transaction S_AUT01.

Features

If you change the logging setting for a data element or table using transaction S_AUT01, the system writes the changed logging status to a table, the so-called Customizing table. At the same time, it stores an inactive version of the changed object in the database. Initially, the original status of the object is retained in the database. The system does not finally write the changed status of the object to the database and delete the inactive object until the object has been activated.

If you start transaction S_AUT01, the system compares the logging setting of all the objects stored in the Customizing table with the corresponding objects in the database. If there are no differences between the logging settings, you go directly to the Change Configuration of Logging screen.

Any differences between the corresponding objects that the system detects may be due to one of the following reasons:

  • Case 1

    As a result of the import of a Support Package or correction, an object (data element or table) was changed for which you had already changed the logging setting with S_AUT01 before the upgrade in your system. In this case, you can decide whether to keep your existing logging setting for the object or adopt the SAP standard settings.

  • Case 2

    An error occurred when an object was activated. It was not activated, or was changed with a different transaction (for example, SE11). As a result, an inactive version of the object exists in the database in addition to the active one. In this case, you cannot activate the object retrospectively from within transaction S_AUT01. Start the Mass Activation function manually and activate the relevant object retrospectively. For more information, see Remove Inactive Versions.

    Caution Caution

    Prior to activation, ensure that the inactive version contains no changes other than the logging settings. If there are other changes, contact your system administrator.

    End of the caution.

  • You have scheduled the activation of objects as a job. The job has not yet run. In this case, wait until the job has run and activation is completed.

If the system detects differences, it lists them separately as tables and data elements. You can then proceed as follows:

  • Leave the differences as they stand (applies to all reasons listed above).

  • Align the logging settings of the objects to either the status delivered by SAP or your own status (in case 1).

  • You can activate the affected objects manually using the Mass Activation function (in case 2). In doing so, you can call up information about the activated object in the log for the Mass Activation function.

After this, the system starts the Change Configuration of Logging function.