Show TOC

 Archiving Table Change Logs (BC-DWB-CUS)Locate this document in the navigation structure

 

Definition

The archiving object BC_DBLOGS is used for archiving Customizing table change logs. The SAP system logs Customizing table changes if:

  1. The Log Data Changes checkbox has been selected in the technical settings for the table.
  2. Logging is active.
    Note

    Logging can be activated and deactivated for a particular client using the profile parameter rec/client.

Use

We recommend that you archive the change logs periodically, for example, quarterly or annually.

Structure

The logs are saved in the table DBTABLOG. The archiving object archives this table only.

The following functions are available for BC_DBLOGS:

Function/Program Assignment

Function

Program

Write

BC_DBLOGS_WRI

Delete

RSLDARCH02

Read
  • RSLDARCH03 (for the entire archiving session)
  • BC_DBLOGS_READ_AR_BY_INDEX
    Caution

    Archiving automatically generates a comment in the archiving session management entry. This comment contains the time period that was archived. Do not delete this text.

Read

For a read by program RSLDARCH03, the archive contents are output in the form of a print list. You can evaluate and print the table logs using the IMG Log (transaction SCU3).

For a read by program BC_DBLOGS_READ_AR_BY_INDEX, the results are output in the form of an ALV Grid. Under Extras, you can choose the data source from which the data is read. The options that are available depend on whether you call the program in archive management (transaction SARA) or in the ABAP Editor (transaction SE38). Using the ABAP Editor, you can specify whether the data is read from the database or from the archive. If you choose to access the archive, then you can either select the archived data manually, or you can read the data from the Archive Information System based on an index. The prerequisite for reading the data from the Archive Information System is that you have activated the info structure SAP_BC_DBLOGS in transaction SARI. This info structure is filled automatically after each archiving run. However, you can also generate it explicitly in transaction SARI.

Integration

This archiving object does not depend on any other archiving objects.

Log entries are archived independently of the client.

You can use the archiving object BC_DBLOGS within the framework of Information Lifecycle Management. To be able to do this, you must activate the related business functions. The system then shows the ILM Actions group box. Using these actions, you can, for example, run archiving during which the system evaluates the retention periods entered in Information Retention Manager. You can also create snapshots (copies) of data, and you can delete data that does not meet your criteria.