Kontakt

Ansicht
Dokumentation

RJBRBDS2 - Report Data Memory: Deletion of Archived Report Data

RJBRBDS2 - Report Data Memory: Deletion of Archived Report Data

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

Title

Deletion Program for Archive Files of the VaR Report Data Memory

Purpose

This program deletes VaR report data in the database based on data from archive files.

Integration

Prerequisites

Features

Selection

You can execute this program as a test run or a production run. The production run deletes data from the database. Depending on the Customizing settings for the SAP archiving object 'RM_BDS', (Transaction AOBJ) this deletion program will:

  • Automatically start after the archiving run - provided you have set the 'Start at end' indicator in the detail screen for object RM_BDS, and the 'Start automatically' indicator in the Customizing settings for this object.
  • Need to be activated manually. If you want to use this option, you must ensure that the 'Start automatically' indicator is not set in the Customizing settings for archiving object RM_BDS.
  • Automatically start after each file change in the archiving run - provided 'Start automatically' is set in the Customizing settings for RM_BDS. The 'Start at end' flag in the detail screen of RM_BDS must not be set, however. This third variant can lead to a situation where a deletion program that is started very early (for the first part of a created archive file) overtakes the archiving for the same run. The consequence of this could be that the run status changes from 'created' to 'archived and deleted' to 'archived' and back to 'archived and deleted'. The program makes sure, however, that the status 'archived and deleted' is reached at the end. For the above reasons, this variant is not recommended when archive files smaller than the data volume of a run are selected.

Standard Variants

Output

Activities

The program opens an archive file, sequentially reads the data records, and finds and deletes the corresponding data records in the database (which are now redundant). The deletion and the commit that go with this are executed one block at a time. You specify the number of archive data objects in a deletion block in the Customizing settings for RM_BDS by entering the 'Commit counter'.

An irregular deletion and commit process may be activated if the run changes within an archive file. If a new run starts, the program deletes and commits the remaining data from the old run (independent of the block size reached) and changes the status of this run to 'archived and deleted'. It updates the P+L archive index and then begins to create a new block. If the archive file is full before the next commit counter is reached, a final deletion and commit process is carried out. In this case as well, the status of the current run is set to 'archived and deleted', even though there may still be data for the run in other archive files, or the final archiving of a run is not yet complete (only applies when the third of the above variants is used).

Example






CL_GUI_FRONTEND_SERVICES - Frontend Services   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 3255 Date: 20240531 Time: 091346     sap01-206 ( 90 ms )