Cross-Archiving Object Customizing 
Use
The settings that you make here apply on a cross-application and cross-archiving object basis for all archiving objects.
Features
Data archiving monitor
Use this checkbox to activate or deactivate the data archiving monitor (transaction
SAR_SHOW_MONITOR) .If you mark this checkbox before data archiving, archiving-relevant information on the write and deletion runs is updated. This information can be analyzed using the data archiving monitor. If there are errors, alerts are issued.
The data archiving monitor offers the following information:
The data archiving monitor is a part of SAP CCMS-monitor collection (transaction
RZ20 ) and can be found under SAP CCMS Monitor Templates à Database à Data Archiving.For more information, refer to
Data archiving monitor.
Access check for archive selection
When selecting files for reading, deleting, analyzing or reloading, this function enables you to check for the existence of an archive file, that is, whether this archive file is accessible in the archive administration. You can use this function to check for stored archive files and archive files that still exist in the file system.
If an archive file is not found by the access check, the file is marked as "not accessible" in the selection screen.

In the case of an access check for stored files, access to the storage system is required. The check can therefore be very time consuming and should only be used if strictly necessary.
Verification of archive files
You can use this function to specify whether, during the writing phase, archive files are to be given verification information that is to be analyzed at a later point. Storing verification information does not affect the size of the archive files. The availability of verification information is a prerequisite for the subsequent evaluation when deleting, reading or reloading.
The system uses this information to verify the status of the archive files before accessing them. Incorrect files are recognized and reported immediately, and deletion from the database does not start.
You can specify whether the verification information is to be stored, and at what point (during deletion, read or reload phase) the information is to be analyzed.
See also:
General Customizing Archiving Object-Specific Customizing