SAP Basis

ADM100 Lesson: Performing Data Archiving
The Archiving Run
The actual archiving run is scheduled and processed as a background job.
It selects the data objects from the database. When doing this, the integrity
conditions that characterize a data object are taken into account. The
system then checks whether each data object can be archived. If it can be
archived, the data object is written to the archive file. If the Customizing
settings specify that the delete program is to run automatically, the
associated deletion run is automatically started, when a file is closed.
Hint: If the delete program is scheduled in parallel to the write
program, there should be at least two background work processes
configured on the SAP system.
The delete run must be separately scheduled, if the delete program is
not automatically run by the settings in the archiving object-specific
Customizing. When doing this, you must also select the archive files, from
which the data objects are to be read in the current delete run, and then
deleted from the database.
An archiving run is scheduled using transaction SARA by choosing the
Write button. It is divided into four steps:
• Creating an archiving variant
• Specifying the execution user
• Specifying the start time
• Defining the spool parameters
The data that is to be archived for the selected archiving object is specified
in archiving variants. In principle, archiving variants can only be reused
if the associated jobs are deleted. The definition of the variant must also
specify whether it is a test run or a production run.
The user under which the archiving program is started requires at least
an appropriate authorization for the authorization object S_ARCHIVE.
S_ARCHIVE is the main authorization object used for data archiving. By
selecting the corresponding field entries for this authorization object, you
can restrict the archiving objects to be used. The user also requires the
relevant authorizations for the application transaction for which data is
to be archived. As data archiving runs in the background, the user also
requires authorizations for background processing (authorization object
S_BTCH_JOB).
The start times to be specified for archiving jobs are the same as those
for standard job scheduling.
2003/Q3 © 2003 SAP AG. All rights reserved. 189