SAP Data Archiving


Archive Programs

The below mentioned Program in the SAP System should be assigned to the Archiving Objects.

1.     Preprocessing(Optional)

This program prepares the data for archiving marking the data by setting the deletion indicator to ‘X’, but it does not delete any data from the database. Preprocessing Programs operates on the database and no Archive files are required. Preprocessing Programs are scheduled manually and run in Archive Administration (tCode: SARA).     

2.     Write

This program creates a new archive file and writes the data in them. At this point, No data is been deleted from the database. The Write programs can be executed in two processing modes.

a.     Test Mode.

b.    Production Mode.

       In the Test Mode, No archive files will be created whereas in Production Mode, Archive                     files will be created.

3.     Delete

This program reads the data from the archived files and deletes the data from the database. The delete programs can be executed in two processing modes.

a.     Test Mode.

b.    Production Mode.

In the Test Mode, the log after the execution shows the entries of the data going to be deleted from the database whereas in the production Mode it shows the statistics of the deleted data from the database.           

4.     Postprocessing(Optional)

This program also operates on the Database and does not require any Archive files. This is final program and can be executed asynchronously with the delete program.

If the data from the database id not deleted by the delete programs, it can be deleted by the Post processing Programs. It is also used for different functions like updating the statistical data, deleting the log data log that is no longer required, etc.  

5.     Reload Programs(Optional)

This program is used to reload the archived data from the external storage system back into respective SAP Database tables. It is not available for all the archiving objects.  

6.     Index Programs(Optional)

This program builds or deletes an index that allows individual access.

Check Archivability

Checking the Archivabilty of the business objects precedes the actual archiving process. This should ensure that the data is not archived, if some other application still needs it. The business objects are considered to be archivable if it:

1.     Is Completed.

2.     Has reached the desired residence time.

3.     Does not serve as basis for other Business Objects.

It is also recommend not be archive Master Data but the Transaction Data.

Residence Time: is the minimum length of time that data must spend in the database before it meets the archivability criteria.

Retention Time: is the entire time that data spends in the database before it is archived.

Setting up the connection between the SAP R/3 database and the External Storage system

Maintain the Content Repository(tCode OAC0) 

The content repository is maintained for every archiving object. Below is the content Repository Maintained for  MM_EKKO.

To retrieve the content repository details, double click on content repository. Details are as below.

Maintain the Document Type (TCode OAC2)

 The document type is maintained by transaction OAC2. Every Archiving object is associated with the document type which is in turn linked to document class. The document class identifies archive format for document in Content server.  

Linking the content repository to Document type (tCode OAC3)

 In transaction OAC3, the content Repository will be linked to Document Type.

Click here to continue...

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image