Ansicht
Dokumentation

/CDBASIS/SLOG_DELETE - Application Log Cleanup

/CDBASIS/SLOG_DELETE - Application Log Cleanup

Addresses (Business Address Services)   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You use this report to delete application logs based on dedicated expiry settings.

The logic does not touch any logs where the application log object and sub-object is not maintained (a blank sub-object means all sub-objects).

The system determines whether the log contains an E or Amessage to apply the expiry horizon for error logs. Logs without E or A messages are considered information logs.

No logs within the retention horizon defined by the log expiry settings (see prerequisites) are deleted.

By entering a date in the field Delete up to dateearlier than the beginning of the retention horizon, only logs up to this date are selected for deletion. In case this date is within the retention horizon, it will have no effect on the log selection and deletion.

You can choose to not delete error logs or information logs by selecting the corresponding checkbox.

Integration

You should not use the standard application log cleanup transaction (SLG2) for deleting application logs where you have maintained dedicated expiry settings.

Prerequisites

Application log expiry settings are maintained in transaction /CDBASIS/LOG_E.

Features

The following selection parameters can be used to decrease the workload of the application log cleanup.

Selection

  • Log Object:Specifies the application log object name.
  • Log Sub-Object:Specifies the application log object's sub-object. If this is empty, all sub-objects are selected.
  • User Name:Specifies the name of the user who caused the logged event.
  • Delete up to date:Defines a date earlier than the beginning of the retention horizon.
  • Do not delete error logs:Select this checkbox to not delete error logs.
  • Do not delete information logs:Select this checkbox to not delete information logs.
  • Test Mode:You can select this mode to only display the planned changes. In productive mode, the changes are executed effectively.

Standard Variants

Output

Activities

If you execute the report, application logs are cleaned up where you have maintained dedicated expiry settings.

Example






General Material Data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 3018 Date: 20240427 Time: 031109     sap01-206 ( 41 ms )