Archiving Final Results (RDB) with RDBAA_FRP

You use the archiving object RDBAA_FRP to archive final results that are stored in the results database (RDB) of the Accounting Analyzer (FIN-FSCM-TRM-AA).

Technical Data

Maximum size of archiving file: 500 MB

Tables

The archiving object RDBAA_FRP is used to archive data from various tables.

Authorization Object

The archiving functions check for the authorization object S_ARCHIVE. See also: Authorization Check

Structure

The following programs are available:

Program (Technical Name)	Function	Comments
RDBAA_FRP_ARC	Write	On the basis of your entries, the write program selects the final results to be archived. Note You can first run the write program in the test mode to simulate archiving without writing any archive files. If you select the setting Complete for the detailed log and set the Display All Errors indicator, the detailed log contains all processed objects including the related messages. Once the test run has proved successful, you can start the write program in production mode. End of the note.
RDBAA_FRP_DEL	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 Test Mode and Production Mode. The archived positions are deleted only in the production mode.

Program (Technical Name)

Function

Comments

RDBAA_FRP_ARC

Write

On the basis of your entries, the write program selects the final results to be archived.

Note Note

You can first run the write program in the test mode to simulate archiving without writing any archive files. If you select the setting Complete for the detailed log and set the Display All Errors indicator, the detailed log contains all processed objects including the related messages.

Once the test run has proved successful, you can start the write program in production mode.

End of the note.

RDBAA_FRP_DEL

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 Test Mode and Production Mode. The archived positions are deleted only in the production mode.

Final results are archived using the Archive Development Kit (ADK). See also: The documentation on Data Archiving in SAP NetWeaver Library, in particular the section relating to archiving using the Archive Development Kit (ADK).

Procedure

Create archive files.
1. You are in the Archive Administration: Initial Screen (transaction SARA), and the name of the archiving object RDBAA_FRP is entered in the Archiving Object field.
2. 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.
  End of the caution.
  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.
  
  End of the note.
3. Use the input help to select a variant. If no variant is available, choose Maintain and create the variant that you require.
4. 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.
  
  End of the note.
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.

End of the note.

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.

End of the note.
Delete the archived data from the database.