Description
This report (RLREOL00) archives fully processed warehousematerial movements that have existed in the system longer than aspecified run time.
You can archive records in one or several warehouse numbersconcurrently.
For testing purposes, you can start this report without actuallycreating an archive file and without deleting records in the system.For this function, the system only selects records and displays asummary log of the number of records that are to be archived.
In the report attributes, the authorization group with the value L_ARCHhas been maintained. With this value, you can prevent unauthorizedusers from starting the report. To do this, you need to maintain theauthorization object S_PROGRAM with the value L_ARCH and then includeit in the user profiles. You then need to remove the authorizationSAP_ALL from the users. Additionally, they need to have theauthorization for the object S_ARCHIVE.

Precondition
We recommend that you start archiving via the general archivingmanagement transaction /nSARA rather than starting itdirectly in the online mode. When you start this program online, youcan generally expect time-outs for larger volumes of data.
A data record for warehouse material records LSEG contains about 150bytes. When you start the archiving report, you can specify how manymaterial documents (default 1000) per data object are selected. Youdefine the size of an archive (number of data objects per archive file)in Customizing (Standard: maximum number of dataobjects = 10) One archive file contains approximately 150 bytes x 10 x1000 = 1.5MB and represents 10000 table entries (withoutcompression).
Familiarize yourself especially with the transaction/nAOBJ and the archive management transaction/nSARA before you start an archive run.
Archiving and deleting records from the database are divided into twoseparate reports. The deletion report RLREOL10 can only delete datathat it reads from the archive.
After the system writes the archive, the archiving report starts thedeletion report as a job. For this, you can specify the size of theportion of the archive file. For most data, this improves theperformance significantly, since the archive and deletion programs areprocessed in parallel.

System Setup
To set up the system proceed as follows:
Check the path and archive names that are in the table of theplatform-independent file names. The system references a logical filedirectory ((ARCHIVE_DATA_FILE) that is maintained as a systemparameter.
Please note that the table of archive names is client-dependent.
Specify the size of the archive file in MB and/or define the maximumnumber of documents per archive file with the transaction/nAOBJ.
If you want to save the archive to memory optically, you also need tomaintain the data for optical archiving using the transaction /nAOBJ.
For information about optical archiving from the correspondingdocumentation. Optical archiving is possible through a simple link.

Output
If you start the report without deleting and archiving records (whenyou select the test run field), the system displays a summary log ofthe records selected by the system. When you start the report using/nSARA with archiving and deletion, the system doesnot display a log.
You need to maintain the spool data and can decide there whether toprint a summary list of the archived and deleted records or to savethem in the spool.
You can display the data in the archive with the ReportRLRL0001.
You can best view the archive management data, the directory and filenames and the number of the archive files using transaction/nSARA.
You can display an overview of the progress of the job processing usingthe job overview transaction /nSM37. You can alsoexecute this transaction from within /nSARA.