Ansicht
Dokumentation
REIDE_SWITCHDOC_ARCH - IS-U Archiving: Analyze/Archive Switch Documents
rdisp/max_wprun_time - Maximum work process run time Vendor Master (General Section)This documentation is copyright by SAP AG.
Purpose
This report is the first step in the process of archiving switch documents. It includes the following steps:
- Analyze switch documents with regard to possible archiving
- Write switch documents to an archive file based on the analysis carried out in the first step.
*********************************************************************
The archiving object includes the following switch document data:
- EIDESWTDOC ,,(Switch Document Header)
- EIDESWTDOCSTEP ,,(Switch Document Step)
- EIDESWTMSGDATA ,,(Message Data for Switch Document)
- EIDESWTMSGDATACO ,,(Comments in Message Data for Switch Document)
- EIDESWTDOCATTR ,,(Attribute for Activity)
- EIDESWTDOCREF ,,(Switch Document Reference)
*********************************************************************
The archiving object for archiving switch documents is ISU_SWTDOC.
*********************************************************************
*********************************************************************
Integration
*********************************************************************
Prerequisites
*********************************************************************
Features
The archiving report selects the following switch documents as standard:
- Switch documents with a status that is not Active and
- Switch documents with a retention period that has expired (the retention period refers to the date of the last change to the switch document)
You can further restrict the selection by entering an area for the switch document number and the switch document status. It is important that you enter all the zeros in the switch document number.
You define the retention period in Customizing under Define Retention Period for Archiving Objects.
You can use BAdI ISU_IDE_SWT_ARCHIVE to define further checks regarding the archivability of switch documents. For more information, see the BAdI documentation.
*********************************************************************
Selection
When you start the report you can make the following settings on the initial screen:
- Switch document number: Limit the amount of data to be analyzed to certain settlement document numbers (Enter the leading zeros).
- Switch document status: Restrict data to be analyzed to a specific status (all statuses except Active are permitted).
- Switch type: Limit the amount of data to be analyzed to certain settlement switch types.
- Switch view: Limit the amount of data to be analyzed to certain settlement switch views.
- Test mode: Start the report as a test run. This means that no changes are made to the database.
- Production mode: Start the report as a productive run. This means that changes are made to the database.
- Detail log: Display log containing extensive data for every analyzed data record (can be confusing with large amounts of data).
- Comment for archive run:Enter an individual comment for an archive run.
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.
Standard Variants
*********************************************************************
Output
*********************************************************************
Activities
*********************************************************************
Example
*********************************************************************
ABAP Short Reference RFUMSV00 - Advance Return for Tax on Sales/Purchases
This documentation is copyright by SAP AG.
Length: 6675 Date: 20240601 Time: 162228 sap01-206 ( 105 ms )
