Here, you set the control parameters for running the delete program.
Delete program variants are client-specific. Consequently, you must make the variant settings in all the clients for which you want to carry out archiving sessions.
When archiving for the first time using a selected archiving object, the relevant test mode and production mode variants for the delete program must be fully maintained. Check whether both variants exist. Note especially, that if a production mode variant is not available, data is not deleted form the database when the delete program is run.
As a part of the delete job, you specify when the delete program is to be run in the background.
This radio button is of interest primarily if you want to save the archive files before the delete phase. If there is a long time period between the write phase and the delete phase, there is a danger that the data could be changed before it is deleted, which means that the data in the archive and in the database are no longer the same. The delete phase should therefore be carried out as soon as possible after the write phase.
Since Before Images has been deactivated for the rollback segments, there ought to be enough space available (Oracle’s Rollback Tablespace).
After the completion of all delete jobs for an archiving session, the ADK issues the event SAP_ARCHIVING_DELETE_FINISHED. The event parameter is the number of the archiving session. You can use this event for event-driven scheduling of accumulated archiving jobs. and the automatic backup of archive files using external tools.
You can use transaction SM62 to display and maintain events.
Rather than use this function for single document access, we recommend that you use the