SAP Program RJBRBDS2 - Report Data Memory: Deletion of Archived Report Data

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 fromarchive files.

Features

Selection
You can execute this program as a test run or a production run. Theproduction run deletes data from the database. Depending on theCustomizing 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, andthe 'Start automatically' indicator in the Customizing settings forthis 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 theCustomizing 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 forRM_BDS. The 'Start at end' flag in the detail screen of RM_BDS must notbe set, however. This third variant can lead to a situation where adeletion program that is started very early (for the first part of acreated archive file) overtakes the archiving for the same run. Theconsequence of this could be that the run status changes from 'created'to 'archived and deleted' to 'archived' and back to 'archived anddeleted'. The program makes sure, however, that the status 'archivedand deleted' is reached at the end. For the above reasons, this variantis not recommended when archive files smaller than the data volume of arun are selected.

        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 withthis are executed one block at a time. You specify the number ofarchive data objects in a deletion block in the Customizing settingsfor RM_BDS by entering the 'Commit counter'.
        An irregular deletion and commit process may be activated if the runchanges within an archive file. If a new run starts, the programdeletes and commits the remaining data from the old run (independent ofthe block size reached) and changes the status of this run to 'archivedand deleted'. It updates the P+L archive index and then begins tocreate a new block. If the archive file is full before the next commitcounter 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 'archivedand deleted', even though there may still be data for the run in otherarchive files, or the final archiving of a run is not yet complete(only applies when the third of the above variants is used).