Table logs

The logging setting for each table is not client-dependent. However, you can set the table logging to client-level using the system profile parameter rec/client . This setting then applies to all the tables that you have selected for table logging. You cannot make a distinction between Customizing tables and other tables. With the rec/client profile parameter, bear in mind that the system logs changes to client-independent tables as soon as table logging is activated in a client.

The archiving of table logs using the archiving object BC_DBLOGS is client-independent.

The evaluation of table logs using the report RSVTPROT (both archived and non-archived) and the transaction AUT10 is client-dependent.

Change documents

The logging setting for each data element for the creation of change documents is client-independent. However, many applications allow you to create change documents in application-specific Customizing. For more information, see SAP note 582342.

In most cases, the system archives change documents together with the object that contains the changes.

The evaluation of change documents using application-specific evaluation functions and the transaction AUT10 is client-dependent.

Long Text Logs

The system logs changes to long texts as table logs. Basically, the same conditions apply to long text logs as to table logs. However, the configuration of long-text deletion in transaction AUT04, and long text deletion using transaction AUT05 or report AUT_DEL, is client-dependent.You can also activate or deactivate the logging of long text changes completely for each client and text object using the filter for long text logging. For more information, see Filter for Long Text Logging .

The archiving of long text logs using the archiving object ELR_LTXTS is client-dependent. The evaluation of archived long text logs using the Archive Information System and the evaluation of non-archived long text logs using transaction AUT10 are also client-dependent.