Ansicht
Dokumentation

RLREOB00 - Archiving Report for Transf.Requirements in WM System

TXBHW - Original Tax Base Amount in Local Currency   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Purpose

This report archives only completely processed transfer requirements that have been in the Warehouse Management system for a specified number of days.

Using this program, it is possible to archive transfer requirements in several warehouse numbers simultaneously.

For test purposes you can display a summary list of the number of transfer requirements that will be archived and deleted from the system before initiating the process. See the instructions under "Output" below.

In the attributes of the report, you must enter the value L_ARCH into the authorization group. In this way, you can protect the archiving programs from being started unintentionally. For this purpose, an authorization with the value L_ARCH must be maintained for the authorization object S_PROGRAM and this value must also be entered into the respective user profiles. The authorization SAP_ALL must be removed from the user profiles.

Requirements

We recommend that you do not start this report directly, but rather with the transaction /nSARA which initializes the general archiving administration program.

You should become particulary familiar with the transaction /nSARA before you start an archiving program. Archiving and the deletion of transfer requirements from the data base have been separated into two reports in Release 3.0 of the SAP system. The deletion report can only delete data that it reads from the Archive.

The archive report creates the archives and then starts the deletion program as a job for each archive. The size of the archive files can be set in advance. For much of the data, the performance can be improved significantly in this manner since archiving and deletion programs are processed simultaneously.

You set up the system as follows:

1. Check the path and archive names that are in the platform-independent table of archive names. The system then references a logical data path that you can maintain as a system parameter.
2. Create variants for the reports:
   For the deletion report use transaction /nSARA
   For the archiving report use transaction /nSARA
3. Define the size of the archive file in MB and/or limit the maximum number of documents per archive file using transaction /nSARA.
4. If you want to save the archive optically, you maintain the data for optical archiving with transaction /nSARA. For information about optical archiving, see the documentation that is marked as such. Optical archiving can be used as a simple add-on function.

Output

If you start this report without deleting transfer requirements and without archiving (that is, if you select only the check box for Test run), the system displays a summary log with the number of transfer requirements that will be archived from each table. When you start the report to archive and delete transfer requirements using the transaction /nSARA, the system does not display a log online.

In any case, you have to maintain the spool data and can decide whether you want the summary of the archived and deleted documents to be printed or stored in a spool file.

To display data in the archive, use report RLRB0001.

You can find archiving management data using the transaction /nSARA, in particular, the path and file names.

To display an overview that shows the status of the jobs, use /nSM37. You can also start the job overview directly from within transaction /nSARA.

CPI1466 during Backup   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 3988 Date: 20240531 Time: 113914     sap01-206 ( 77 ms )