Skip to Content
Author's profile photo Former Member

Technical Setting for Data Archiving

This blog is tended to address the Basis settings needed for small data archiving projects using standard SAP programs or  proof-of-concept archiving projects.

The technical configuration changed by Basis folks could be started with calling Tcode AOBJ, select the archiving object from the right window, then doubleclick on “Customizing Settings” on the left.


The first parameter would be “Logical File Name”.


SAP Note 71935 explains the storage options for data archiving files.

If the data archiving files will stay on the file systems, you could define corresponding logical files from Tcode FILE. For example, logical file Z_/SYS/global/, and the archiving files will stay there only temporarily. How to specify the  storage system is explained in the last set of the parameters.

The second set of the parameters, “Maximum Size in MB” and “Maximum Number of Data Objects”, is about writing the data to the archiving files.


The data in the archiving file is compressed from the information in the database. Meanwhile big numbers, as long as supported by the file system and/or the storage system, can be specified. If it is planned to move the archiving files with media like CD-ROM or USB memory stick, please consider those limitations here. On the other hand, it is fast to retrieve data from small archiving files. You could give big numbers on test environment first, and fine tune them based on the results of the test archiving/retrieving runs.

The next set of parameters is related to the deletion process.


Typically there is a default value for “Commit Counter” like 10 or 100. If it is absent, it is safe to put a similar number. The “Test Mode Variant” and “Production Mode Variant” should be selected from what SAP has defined, something like SAP&TEST or SAP&PROD. The other parameters are about when deletion jobs are triggered, and they are well self-explained.

The last set of parameters is relevant to the storage system.


Leave the “Content Repository” blank if the archiving files are planned to be stored on the file systems.

Fill the proper “Content Repository” if the archiving files are stored in the storage systems. (How to install and configure different storage systems is out of the scope of this blog.) The other parameters are straight forward. “Start Automatically” could save you from scheduling separate jobs. And “Store Before Deleting” with “Delete Program Reads from Storage System” could serve as validation process for the archiving files.

Upon the functional settings for the same archiving object is ready, the data archiving jobs can be scheduled from Tcode SARA.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.