Entering content frame

Function documentation Archiving Request Administration Data Locate the document in its SAP Library structure

Use

The administration tables of the scheduler, and the log tables of the extraction monitor (tables RSMON* und RS*DONE), increase with each new request from BI. This affects performance.

When you display a request in the extraction monitor or in InfoProvider administration, the system checks the completeness of these administration and log tables. 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.

Archiving request administration data allows you to store the administration and log information for a request in an archive. In BI, tables store the totals records that the system requires so that the request is not set to red because information is missing. The function allows you to restrict the size of the administration and log tables RSMON* und RS*DONE. This means that you can save memory space on the database, without affecting status determination.

If you want to update data from an InfoProvider and this InfoProvider contains requests for which the administration data is already archived, the system creates a new request. This means that the system does not have to read the archive. This also applies to loading data from the PSA (in a data transfer process) for requests with archived administration data.

If the system can only execute a process with request administration data that has been reloaded, this involves setting the QM status and rebuilding the process from the PSA.

Integration

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 archive runs for requests in the archive management for requests in the Administration functional area of the Data Warehousing Workbench. You can execute various functions for the archive runs here.

Prerequisites

Reports RSSTATMAN_CHECK_CONVERT_DTA and RSSTATMAN_CHECK_CONVERT_PSA have been executed in the background at least once for all objects.

Features

Request data is archived from the following tables:

Table

 

RSREQDONE

Header table of the request

One record for each archived request remains in the table. This contains information on the archiving status.

RSSELDONE

One record for each archived request remains in the table

RSLDTDONE

Entries for the selected request are deleted during archiving

RSCRTDONE

Entries for the selected request are deleted during archiving

RSDELDONE

Entries for the selected request are deleted during archiving

RSHIEDONE 

Entries for the selected request are deleted during archiving

RSRULEDONE

Entries for the selected request are deleted during archiving

RSMONMESS

Entries for the selected request are deleted during archiving

RSMONFACT

Entries for the selected request are deleted during archiving

RSUICDONE

Entries for the selected request are deleted during archiving

RSTCPDONE

Entries for the selected request are deleted during archiving

RSMONICTAB

Entries for the selected request are deleted during archiving

RSMONIPTAB

Entries for the selected request are deleted during archiving

RSMONRQTAB

Entries for the selected request are deleted during archiving

 

In archive administration for the archiving object BWREQARCH (transaction SARA), you can:

·         Execute the write program for archiving request administration data

·         Start the program for deleting archived administration data belonging to the request from the database table

·         Display an overview of the archiving run

·         Execute the program for reloading archived administration data belonging to the request into the database table

In archive administration for the request in BI (transaction RSREQARCH), the system displays the archive runs for the archiving object BWREQARCH. You can:

·        Display requests with archived administration data for an archive run

·        Display the selections for an archiving run

·        Reorganize archiving runs

·        Compare archiving runs

·        Delete archiving runs from archive administration in BI if they no longer contain administration data for the request

·        Reload archived administration data for a request back into the database tables.

Constraints

It is currently not possible to archive request administration data for data transfer processes.

Recommendations

To avoid reloading data from the archive unnecessarily, we recommend that you only archive request administration data for requests that are more than three months old and will probably not be edited again.

Note: Do not archive the administration data for too many requests in one archiving run.

See also:

Archiving Request Administration Data

Reloading Request Administration Data

 

Leaving content frame