Archiving Request Administration Data

When you archive request administration data, you store administration and log information about requests in an archive and thus improve the performance for actions concerning requests.

When you display a request in the extraction monitor, data transfer process monitor or in the administration of an InfoProvider, the system checks whether the administration tables and log tables of the data transfer process (DTP)/InfoPackage are complete. If the entries for the request are not complete or are missing in the table, the system gives this request the status red. Since the system uses the administration data to dynamically determine the request status, this administration data is required. If the system gives a request the status red because it cannot find the administration or log information, the technical and QM status is reset in all the targets that are filled by this request. This may result in a termination, or in the queries that are defined for the affected InfoProviders displaying obsolete data, or no data at all. Therefore, you cannot delete entries from these tables.

The administration tables and log tables of the DTP/InfoPackage increase with each new request. This in turn affects performance.

If you now store the administration and log information about requests in an archive, totals records are kept in the relevant tables in the SAP NetWeaver BW. This prevents the status of the request from being changed to red because information is missing, and lets you limit the table size of the administration and log tables. In this way, you improve performance for actions performed for the request and in the affected InfoProviders and save memory space on the database, without affecting the status set by the system.

Integration into the SAP NetWeaver

The archiving concept for request administration data is based on the SAP NetWeaver data archiving concept. The archiving object BWREQARCH contains information about which database tables are used for archiving, and which programs you can run (write program, delete program, reload program). You execute these programs in transaction SARA (archive administration for an archiving object).

In addition, you can manage archiving runs for requests in archive management in the Administration functional area of the Data Warehousing Workbench. You can execute various functions for the archiving runs here.

Notes and Recommendations

Caution Note that the administration data (ADK archive runs) for the archiving object BWREQARCH cannot be archived or deleted with the archiving object BC_ARCHIVE.

Note

With certain functions and processes that write to requests, you have to reload request administration data from the archive into the administration tables and log tables. To avoid reloading data from the archive unnecessarily, we recommend that you only archive administration data from requests that are more than three months old and will probably not be edited again.

More information: Reloading Request Administration Data
Do not delete or move the archive data from the file system. If you still want to move archive data in the file system, you need to change the pointer in ADK so that it points to the current file storage.
If you copy a BW system, you need to copy the archive files for the archiving object BWREQARCH to the file system of the target system for the system copy. This is necessary in order to write to requests (with administration data archived before the copy) in the target system of the copy.

Prerequisites

If you have upgraded from SAP BW 3.x to SAP NetWeaver 7.x:

Reports RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA have been executed at least once for all objects. We recommend that you execute reports in the background.

Features

Overview of Archived Tables

Note The header table of the requests, table RSREQDONE, is not archived. It contains one record for each request. This record contains information about the status of the archiving.

Request data is archived from the following tables:

Table	Changes upon Archiving
RSSELDONE	One record remains in the table for each archived request; further records for the same request are deleted after archiving.
RSLDTDONE	Entries for the selected request are deleted after archiving.
RSDELDONE	Entries for the selected request are deleted after archiving.
RSHIEDONE	Entries for the selected request are deleted after archiving.
RSRULEDONE	Entries for the selected request are deleted after archiving.
RSMONMESS	Entries for the selected request are deleted after archiving.
RSMONRQTAB	Entries for the selected request are deleted after archiving.
RSMONFACT	Entries for the selected request are deleted after archiving.
RSUICDONE	Entries for the selected request are deleted after archiving.
RSTCPDONE	Entries for the selected request are deleted after archiving.
RSCRTDONE	Entries for the selected request are deleted after archiving.
RSMONICTAB	Entries for the selected request are deleted after archiving.
RSMONIPTAB	Entries for the selected request are deleted after archiving.
RSBMONMESS	Entries for the selected request are compressed after archiving.
RSBMNODES	Entries for the selected request are compressed after archiving.
RSBMLOGPAR	Entries for the selected request are compressed after archiving.

Functions in archive administration for archiving object BWREQARCH (transaction SARA):

Here you can:

Execute the write program for archiving request administration data.
Execute the program for deleting archived administration data belonging to the requests from the database table.
Display an overview of the archiving run.
Execute the program for reloading archived request administration data of a complete archiving session into the database table.

Functions in archive administration of requests (transaction RSREQARCH)

Here the system displays the archiving runs for archiving object BWREQARCH. Here you can:

Go to the archive administration for the archiving object BWREQARCH (transaction SARA).
Display requests with archived administration data for an archiving run.
Display the selections for an archiving run.
Reorganize archiving runs.
Compare archiving runs.
Delete archiving runs from archive administration if they no longer contain administration data for the request.
Reload archived administration data for individual requests back into the database tables.