SAP Data Archiving

Introduction
Data Archiving, in general means deleting the huge volumes of the data that is no longer required in the
database to some file system or any third party storage system. It is also a service provided by SAP forthe
consistent removal of data objects from database tables of the SAP database, where all table entries that
characterize a data object are written to an archive file outside the database.
Benefits of DATA Archiving
1. Reduces the costs of memory, disk and also administration costs.
2. Ensures cost efficient system upgrades and migration.
3. Improved system performance due to shorter response time.
4. Reduces the cost of maintenance and run of growing application infrastructure.
SAP Data Archiving Process Flow
SAP Data Archiving main involves three steps:
1. Creating the Archive files.
2. Run the delete programs.
3.

Store the archive files.

Creating the archive file and running the delete programs are the mandatory steps to follow for data archiving
whereas storing the archive files is optional.

1. Creating the Archive files

In this step, a new archive file is been created and data to be archived is sequentially written in it.
2. Run the delete programs
In this step, the delete programs are executed which deletes the data from the SAP R/3 database, once the
archived data is read successfully from the archive files.
The delete programs can be triggered manually or automatically.
3. Store the Archive files
Here, the archive file with the archived data is moved to the third party storage system or copied to disk, etc.
This can also be triggered manually or automatically.
Dynamic Menu (tCode SDMO)

A list of transaction codes along-with the short description required for SAP Archiving can be found in the
dynamic menu. Go to transaction SDMO and enter search for the text as Archive.

Click on execute button. The screen will be displayed as below.

What is Archiving Object?

Archiving Object is the central component of Sap Data Archiving. Archiving Object specifies which data is to
be archived and how. Archiving Objects directs the SAP Archiving system to get the correct tables associate
with the specific Business Object. The archiving object name can be ten characters long in length.

Archiving objects are defined by the transaction AOBJ.

Fig.1. Archiving Object Details (AOBJ).

Identifying the Archive Objects
Transaction DB02 is used to identify tables with high growth in data volumes and to compare the table size
after archiving and thus to monitor growth of the database tables.
Transaction TAANA which is used to identify the appropriate archiving object when a table has more than
one archiving object
Transaction DB15 is used to identify the Archive Objects, if you know the Database tables or if you know the
Archiving Object it displays the list of associated database tables for that particular Archiving Object as
Shown in Fig.a.

Configuration of Archive Objects

1. Structure Definition.
As shown in the Fig.2. , the Structure definition contains the list of the database tables from which the
data will be archived. This is pre-configured for the Standard SAP Archive Objects.

Fig.2. Structure Definition.

2. Tables from which you only Delete Entries.
As shown in Fig.3. , this contains the list of Database tables from which the data will be only deleted and
not archived. This is pre-configured for the Standard SAP Archive Objects.

Fig.3. Tables from which You Only Delete Entries.

3. Maintain Network Graphic
This contains the list of pre-requisite Archived Objects that needs to be archived before the actually
archive objects. This is pre-configured for the Standard SAP Archive Objects.

Fig.4.Maintain Network Graphic.

4. Customizing Settings.
This should be configured as per the business requirements. As shown in the Fig.5. , this contains
details about Archive File Size, Setting for Delete programs like Test Mode Variants and Live Mode
Variant(i.e. Production Mode variant), content Repositories and the sequence of deletion. If the radio
button Start Automatically for Delete Jobs is selected, automatically the delete program is executed
after the write program. If not selected, execute the delete program manually for the particular archiving
object.

Fig.5. Customizing Settings.

5. Archiving Classes Used.

As shown in the Fig.6., this contains the details about the archiving classes used by the particular
Archiving Object.

Fig.6. Archiving Classes Used.

6. Read Programs.
This contains the details about the read programs which is used by both the archiving objects and
Archiving Class to read the data from the Archive files.

Fig.7. Read Programs.

7. Customizing Transactions.
This contains the transaction code for the application-specific customizing for the relevant archiving
object. Once this code is entered, you can go directly from transaction SARA to the application-specific
Customizing transaction, which is often used for entering residence times for an archiving object.

Fig.8. Customizing transactions.

8. Info Tables for Archive Files.
This contains the list of database tables that will give the archive file name, the criteria for archiving and
other related information.

Fig.9. Info Tables for Archive Files.