Archiving Final Results (RDB) with RDBRA_FRP
You use the archiving object RDBRA_FRP
to archive final results that are stored in the results database (RDB) of the Market Risk Analyzer
(FIN-FSCM-TRM-MR
).
Final results are archived using the Archive Development Kit (ADK)
. For more information, see SAP NetWeaver Library in the SAP Help Portal under http://help.sap.com/nw
.
Technical Data
Maximum size of archiving file: Default 500 MB
Programs
Program (Technical Name) | Function | Comments |
|---|---|---|
|
| Write | On the basis of your entries, the write program selects the final results to be archived.
You can first run the write program in the test mode to simulate archiving without writing any archive files. If you select the setting Once the test run has proved successful, you can start the write program in production mode. End of the note. |
| Delete | The deletion program deletes all archived final results. This is because, for security reasons, data deletion cannot be executed by the write program. On the selection screen, you can choose between |
Read | In the To do this, you can use the information structures delivered by SAP (after activation in transaction |
Tables
The archiving object RDBRA_FRP
is used to archive data from various tables.
Authorization Object
Authorization Object | Notes |
|---|---|
| The write program checks whether you have authorization for the archiving object |
Create archive files.
You are in the Archive Administration: Initial Screen
(transaction SARA
), and the name of the archiving object RDBRA_FRP
is entered in the Archiving Object
field.
Choose Write
.
A screen appears on which you can schedule the write program to be run in the background.
If archiving has already been performed for an archiving object and there are still archive files from that archiving run that have not yet been processed by the relevant deletion program, the system informs you of this in a separate window.
The same applies for interrupted archiving runs.
Caution
Archiving data more than once can lead to various problems. Hence some archiving objects require that data is not replicated in the archive, because this can lead to incorrect results (such as using archived data to produce totals). Ensure the following:
The new write job that needs to be scheduled does not select the same data that is contained in archive files that have not yet been processed by the deletion program.
No variants with overlapping selection values are used in parallel.
Note
If the variant that you have selected is already being used in other jobs, you can choose the Jobs with Selected Variant
pushbutton to display the variant and delete it if necessary.
Use the input help to select a variant. If no variant is available, choose Maintain
and create the variant that you require.
Enter the start date and the spool parameters.
Note
With the Archive Directory
pushbutton, you can determine how much storage space is free in the current object-specific archive directory before you start to archive.
Now you have entered all of the data required for the background job. To run the job, choose Execute
.
Note
After all archive files of a run have been written completely, the system event SAP_ARCHIVING_WRITE_FINISHED
is triggered by the ADK. In reaction to this event, processes that occur downstream from archiving (such as automated file storage) can be triggered by external tools.
Furthermore, you can navigate to the following menu options:
Customizing
Job Overview: Here you find an overview of all archiving jobs as well as functions for processing them.
Administration
DB Tables
Information System
Note
You can display the logs documenting processing by choosing Logs
from the Archive Administration initial screen.
Delete the archived data from the database.