Material

Limits the data to be analyzed or archived to certain material.

Serial Number

Limits the data to be analyzed or archived to certain serial numbers.

Created By

Limits the data to be analyzed or archived to that created by certain users.

Message Type

Limits the data to be analyzed or archived to certain message types.

Message Source:

Limits the data to be analyzed or archived to certain message sources.

Archiving Date of Messages

Limits the data to be analyzed or archived to a certain date.

This date must not come after the retention period defined in Customizing.

Archiving

You can use this action to archive data for closed business objects. The system executes archivability checks to determine whether data can be archived, similar to the existing data archiving function you may be used to. The system uses the ILM functions during the write phase to evaluate the rules entered in the Information Retention Manager (IRM) for each business object instance. In this way, it determines the retention period and storage location for the object. This information is persisted to the database as part of the administration data and is interpreted later during storage.

Snapshot

Snapshots are archiving runs that are used to extract data from the database but this data is not deleted from the database. Apart from checking the restrictions in the selection variant, the system does not execute any additional checks. 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 run 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

With this action, data is destroyed from the database in an archiving write session and a subsequent deletion run. The system generates temporary archive files, which are deleted automatically after the deletion phase. A run is classified as a destruction run by the DESTROY parameter. If an archiving object has not been registered in the IRM, the system ignores the DESTROY parameter and executes a normal archiving run.

Test run

Starts the write program as a test run; the system does not make changes in the database.

Production run

Starts the write program as a production run; the system makes changes in the database.

Detail log

Displays a log containing data for every analyzed data record.