Introduction: This document details out the standard SAP Archival process and also the possible customizations which we can implement while archiving.Data Archiving is the process where in, huge volume of data is deleted from the system which has not been used for a long time. SAP recommends this process of data archiving to clean up the SAP standard tables, to improve the system performance and usability which yield to shorter response time.
Transaction’s Used in Data Archival :
The standard transaction’s used to archive the business objects are SARA, SARJ.
Data Archival Process Flow:
SAP Archival process mainly involves the below steps:
Preprocessing Operation: This is an optional step , which makes the date/flag value set for the data which needs to be archived, but doesn’t delete the data . This is not found in all archiving objects.
Write Operation : It is a mandatory step which mainly writes the archival file in the logical file path before deletion occurs, based on the criteria chosen.
Delete Operation: It is a mandatory step which deletes the archival file which has been written out in the above step.
Read Operation: It reads the archived data from the storage area after the deletion.
SAP Standard Archiving Objects:
SAP provides many archiving objects , few of the most commonly used are listed below.
Archiving Object for Application Log
Archiving Business Partners
This document explains in detail about the various configurations and possible customizations considering the Activity Archiving object – CRM_ACT_ON.
The first section of this document briefs on the various configurations which must be maintained before the archival happens. And the later section details out on the various operations performed during the archival process.
Configuration Steps in Archiving the Object:
Step1: Goto SARA Transaction and identify the Archiving Business Object for Activity Transaction – CRM_ACT_ON.
Step2: We find many tabs in this transaction. We shall discuss below the most important tabs.
Step3: Customizing: Click on the tab – Customizing. You get many options when you choose the customizing settings.
Step4: Click the Technical Settings under the Cross- Archiving Object Customizing. You can change these as per the business requirements or retain the same.
Step5: Check and Delete will show for which archiving objects pre-check is active.
Step6: Under the Archiving Object Specific Customizing settings, we get the below screens.
Step7: Under Technical Settings, we mainly need to maintain the logical file name and the file size.
Maximum size in DB represents the file size. If this size exceeds , it generates another file.
The radio button under Delete Jobs-> Start Automatically will trigger the Delete Job soon after the Write Job.
Step8: Under Check and Delete we find the below screen.
Step9: Under Archive Routing we link the archiving object with the logical file name.
Step10: Click on rules and maintain the logical file name.
Step 11: Under conditions we can maintain the Selection Criteria which appears in the report program if needed or can be maintained as blank.
Step 12: Click on Basis Customizing, this navigates to FILE transaction. In the FILE transaction we maintain a Logical file name and maintain the same under the Archive Routing. The logical file name indicates where the archival file needs to be placed.
Step13: Choose the Logical file path and click on the Assignment of physical path to logical path to maintain the actual storage location of the Archived files in the system.
Step 14: Click on the Logical File Name Definition, to maintain the file name in which the archived files would be generated.
Step15: By default standard SAP provides the below naming convention for the files.
PARAM_1: This is a two-character application abbreviation for the classification of the archive files in the system. The value of the definition is determined from the relevant archiving object at runtime.
PARAM_2: Single-character alphanumerical code (0-9, A-Z). If, when creating a new archive file, an existing file with an identical physical name would result in a conflict, the ADK increases this value by 1. This value must, therefore, always be a part of the physical name.
PARAM_3: This parameter is filled at runtime with the name of the archiving object. In archive management, this enables you to check the file contents or to store the archive files by archiving objects.