Show TOC

Deleting Archived Data from the DatabaseLocate this document in the navigation structure


  • In Archive Administration, there are archiving sessions for which the delete phase is not yet complete.

  • You have waited for the write phase to be completed.

    More information: Settings for the Delete Program


In the third archiving step (after creating and storing archive files), Archive Administration starts the delete program. This reads the archived data from the archive file and deletes it from the database.

Depending on the settings you have made in archiving object-specific Customizing, the deletion process for an archive file can run at the same times as the creation of new archive files.

If you want to save the archive files prior to deletion or if you the next available timeframe for the delete phase is insufficient, you can schedule the delete program manually. You do the scheduling in Archive Administration (transaction SARA), directly with an external job scheduler, or you use the program RSARCHD.


If you do not carry out deletion until after the archive file has been stored, you can make a setting in Archiving Object-Specific Customizing so that the system will read archive files the from the storage system during deletion. In this way, you can detect early on errors that might arise when transferring or saving the archive files in the storage system.

Delete Run Followed by Event

After all delete jobs for an archiving session have been completed, the Archive Development Kit (ADK) triggers the system event SAP_ARCHIVING_DELETE_FINISHED. As a result of the reaction to the system event, you have the option of scheduling subsequent archiving jobs automatically. These include refilling indexes or the value help as well as saving archive files. The event parameter is always the number of the archiving session.

For additional automation of the archiving process, you can transfer the archiving session number to the function module ARCHIVE_GET_FILES_OF_SESSION. This determines the platform-independent name and path of the archive files that were written for an archiving session.

To define new jobs, use transaction SM36. To define events, use transaction SM62.


You can also schedule event-controlled delete runs to start automatically. You can define the event that triggers the delete program in the Settings for the Delete Program group box in archiving object-specific Customizing.


  1. Call Archive Administration (transaction SARA).

  2. On the initial screen, enter the name of the archiving object in the Object Name field.

  3. Choose Delete.

    This takes you to a screen in which you can schedule a background job for the program.


    If you only want to run the delete program for test purposes (so that the data is not deleted from the database), select the Test Mode checkbox.

  4. Choose Archive Selection.

    This takes you to a dialog box that contains the archiving sessions for this archiving object. This should be the current archiving session.

  5. If you want to edit a complete archiving session, select an archiving session and choose Continue. You return to the initial screen.

    f you want to edit one or more specific archive files, expand the archiving session. Select the required archive files, than choose Continue.

  6. Enter the start date and the spool parameter.

    More information:

    Entering the Start Date

    Entering the Spool Parameter


You have entered all data required for the background job. Start the job with Execute.


You can view the logs for the started process from the initial screen of Archive Administration.

More information: Logs