Ansicht
Dokumentation

REPDAR_ARCH_LINES_ILM - Archive Print Document Line Items

BAL Application Log Documentation   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Title

Archive Print Document Line Items

Purpose

This report is the second step in the process of archiving print document line items: The writing of print document line items to an archive file, based on the analysis carried out in the first step.

The archiving object related to the archiving of print document line items is called ISU_PRDOCL.

You can use the AOBJ transaction to access the definition of the ISU_PRDOCL archiving object and the corresponding Customizing settings.

You can use the SARA transaction to access archiving administration and the corresponding Customizing settings.

You can use the SARI transaction to access the technical view of an archive.

You can use the standard IS-U transaction SISU to access the accounting view of an archived print document.

Integration

• REPDAR_ANALYSE_HEAD

First step in the process of archiving print document line items: Analysis of the print documents with regard to potential archiving of the line items.

• REPDAR_DEL_LINES

Third step: Deletion of the print document line items in the database on the basis of the previously created archive.

• REPDAR_REL_LINES

Use this report to reload data that has been archived and already deleted. Note that you cannot reload individual documents. You have to reload the entire archiving run. This procedure should not normally be used and should be limited to extreme problem cases (for example, incorrect retention period in Customizing).

• REPDAR_READ_ARCHIVE_LINES

This report allows you to read a print document line item archive and to display parts of the data in a list before the deletion program has been executed. It displays the data in a technical view.

Prerequisites

Before starting this archiving report, you have to carry out at least one analysis with the REPDAR_ANALYSE_HEAD report.

Features

The analysis report selects the print documents that have archiving indicator 1 (print document line item can be archived). The print document line items of these print documents are selected, written to an archive file, and their archiving indicator is set to 2 (print document line item can be deleted). If you start the report in test mode the changes to the database described above are not carried out, and and the system just displays a detailed overview (you can set the level of detail) of the documents whose line items you can archive.

Notes on Starting the Program

When you start the report you can make various settings on the initial screen:

• Log type: General statistical data or detail log (can become confusing with large amounts of data).

• Run time restriction: If you activate the run time restriction, the analysis report terminates when the end date and end time is reached. This means that you can let the analysis report run as a job during short time frames.

• Test run: If you start the report as a test run, no changes are made to the database (updating the archiving indicator, writing to the archive file, etc.).

• Comment on archive run: Here you can enter an individual comment for an archiving run. Where necessary, set indicator to 2.

In variant maintenance for the write program the following actions from SAP NetWeaver Information Lifecycle Management are available:

• Archiving

With this action, you can archive the data of closed business objects. The system performs archivability checks to check if the data can be archived. In this respect, this function corresponds to the function of standard data archiving that you are used to. By means of the ILM enhancements, the system evaluates the rules maintained in the Information Retention Manager (IRM) for each object instance during the write phase, and thereby determines the retention period and the storage location for the object. This information is persisted on the database as part of the management data and is later interpreted when the data is stored.

• Snapshot

Snapshots represent archiving runs that extract data from the database, but do not delete this data from the database. Except for considering the restrictions in the selection variant, the system does not perform any additional checks. Using this option, therefore, you can also write data from current, not yet completed business transactions to the archive. To exclude the possibility of losing data, runs of this type are not offered for deletion. With snapshots therefore, you always create redundant copies of data from the database. This function is especially useful for system decommissioning in conjunction with the ILM component Retention Warehouse.

• Destruction of Data

The destruction of data from the database takes place using an archiving write run followed by a deletion run. During this process, temporary archive files are created that are then deleted again after the deletion phase is completed. The system automatically deletes these files along with the file-related management data. The technical classification of a run as a destruction run is made using the parameter DESTROY. If an archiving object is not registered in IRM, the parameter DESTROY is completely ignored, and a normal archiving run takes place.

Example

CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 5907 Date: 20240520 Time: 124719     sap01-206 ( 127 ms )