Data archiving is the consistent transfer of data objects from SAP system database tables to the document storage system (generally considered to be the electronic storage) outside the SAP system database. All relevant table entries that characterize a data object are written to an archive file outside the database. Business consistency is ensured by SAP archiving programs that, based on archiving objects, store all relevant table entries together elsewhere.
The central element in data archiving is the archiving object. An archiving object is the smallest unit that can be archived in and deleted from the database in its entirety, and it describes how and which database objects must be accessed for a business object to be archived completely.
The content of the business objects in the SAP system is distributed throughout several tables in the database. The activity of archiving objects that bundle logically-related tables of business objects ensures, that, in the framework of data archiving, all information regarding a business object is transferred out of the database.
An archiving object is basically made of the following components:
- Data declaration part:
The data declaration part consists of all the relevant database objects that characterize an application object.
- Customizing settings:
Customizing settings are used to set parameters specific to each archiving object for an archiving procedure.
- Programs:
Archiving object programs include the following programs:
- A write program that writes the data objects sequentially in the archive files
- A deletion program that deletes from the database all the data objects that are read in the archive file beforehand
- A display program that permits archived data objects to be read
Data Archiving Customizing (Basis Support, System Administration)
Archiving Customizing is used to set parameters that control how data is archived.
Customizing is divided into the following steps:
- Step 1: Basis Customizing
Define logical path and file names
- Step 2: Cross-archiving object Customizing
Define a server group for background processing
- Step 3: Archiving object-specific Customizing
- Size of an archive file
- Deletion program settings
These steps are usually executed by the basis support or the system administration department.
To open the Customizing settings, choose the Customizing button in the initial screen of transaction code SARA (data archiving menu path: SAP Easy Access→Tools→Administration→Administration→Data Archiving).
Step 1: Basis Customizing
In Basis Customizing (run transaction code FILE), a logical file path is defined (if one does not already exist) as a global path for data archiving, and a physical path is assigned to it. The logical path is merely used as a bookmark for the physical path that is generated at runtime.
Step 2: Cross-archiving object Customizing
The parameters set in this step apply to all application and archiving objects for using all archiving objects.
For example, you can use these parameters to show or hide the data archiving monitor (transaction code SAR_SHOW_MONITOR). Set these parameters before archiving data permits archiving-relevant information to be updated using write and deletion programs. This information can be analyzed using the data archiving monitor. In addition, alerts, such as error messages, can be triggered in case of an error.
With the SAP Fiori app MONITOR ARCHIVING JOBS you can also monitor, track and administrate archiving jobs.
Step 3: Archiving object-specific Customizing
The parameters set in this step apply only to the corresponding archiving object.
In archiving object-specific Customizing, you can maintain the following settings:
- Maintain settings for the deletion program in addition to a logical file name for the specific archiving object.
- Set if the deletion program is to be executed automatically after an archive file is generated.
- Create one variant each for the test run and the production run and specify the maximum size of an archive file in this area.
All settings for the deletion program can be maintained using the Customizing function.