Ansicht
Dokumentation
REAARCH_ARCH_EXRESP - Archive TOU Exception Responses
Addresses (Business Address Services) BAL Application Log DocumentationThis documentation is copyright by SAP AG.
Purpose
This report is the second step in the process of archiving TOU exception responses: The writing of TOU exception responses to an archive file, based on the analysis performed in the first step.
Integration
First step in the data archiving process for TOU exception responses: Analysis of TOU exception responses with regard to potential archiving.
REAARCH_ARCH_EXRESP
Second step: Archive the TOU exception responses selected in the first step.
Third step: Delete TOU exception responses from the database on the basis of the previously created archive.
Use this report to reload data that has been archived and already deleted. Note that you cannot reload individual TOU exception responses, but must always 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).
You can use this report to read a TOU exception response from the archive before the deletion program has been run, and display it in a list. It displays the data in a technical view.
Prerequisites
Before starting this archiving report, you must perform at least one analysis with the REAARCH_ANALYSE_EXRESP report.
Features
The archiving report selects TOU exception responses for which a corresponding entry exists in the index table ETOUEXCEPTRESPAR, whose entries are generated by the analysis report. The system writes the entries found to the archive. If you start the report in the test mode, the system does not write the data to the archive, and only displays an overview of the documents you can archive (if a detailed log display is required).
Selection
When you start the report you can make various settings on the initial screen:
1. Log type: General statistical data, detail log with detailed data for each analyzed record or detail log with detailed data for documents that could not be archived.
2. Test run: If you start the report as a test run, no data is written to the database.
3. Comment on archive run: Here you can enter an individual comment for an archiving run.
In variant maintenance for the write program, the following actions from SAP NetWeaver Information Lifecycle Management are available to you:
- Archiving
You can use this action to archive data for completed business objects. The system performs archivability checks to establish whether data can be archived. The function is identical to standard data archiving in this respect. The ILM enhancements mean that during the write phase, the system can evaluate the rules maintained in the Information Retention Manager (IRM) for each object instance and therefore determine the retention period and the storage location for the object. This information is persisted to the database as part of the administration data and is interpreted later during storage.
- Snapshots
Snapshots are archiving sessions that are used to extract data from the database but this data is not deleted from the database. The system does not execute any additional checks other than checking the restrictions in the selection variant. You can use this option to write data to the archive from current, open business transactions. To prevent data from being lost, this type of session is not provided for data deletion. Therefore, snapshots always create redundant copies of data from the database. The snapshot function is mainly intended for use in conjunction with the ILM Retention Warehouse component when decommissioning older systems.
- Data Destruction
This action destroys data from the database in an archiving write session and then in a subsequent delete run. This creates temporary archive files that are deleted at the end of the deletion phase. The system automatically deletes these files and any administration data related to them. A run is classified as a destruction run in technical terms by the DESTROY parameter. If an archiving object has not been registered in the IRM, the system ignores the DESTROY parameter and executes a standard archiving session.
Standard Variants
Output
Activities
Example
CL_GUI_FRONTEND_SERVICES - Frontend Services ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 5132 Date: 20240601 Time: 053541 sap01-206 ( 108 ms )
