sap data archiving

SAP

DATA

ARCHIVING

INDEX

1. Introduction...................................................................................................

2. Archiving Objects.........................................................................................
2.1 Definition..................................................................................................................................... 2.2 Archiving objects and related tables.......................................................................................... 2.3 Transaction Code SARA and its use for Administration of archiving objects............................ 2.3.0 SARA........................................................................................................................................ 2.3.1 ICONS and their explanation....................... ............................................................................ 2.3.2 Network Graphic...................................... ................................................................................ 2.3.3 Information................................................................................................................................ 2.3.4 Job Overview............................................................................................................................. 2.3.5 Log............................................................................................................................................ 2.3.6 Customizing............................................................................................................................... 2.3.7 Database Table.......................................................................................................................... 2.3.8 Information system....................................................................................................................

3. AOBJ - Configuration of Archiving Objects................................................ 3.1 Structure definition..................................................................................................................... 3.2 Tables from which you only delete entries................................................................................. 3.3 Maintain network Graphic.......................................................................................................... 3.4 Customizing settings................................................................................................................... 3.5 Archiving classes Used............................................................................................................... 3.6 Read programs............................................................................................................................. 3.7Archiving classes Used................................................................................................................ 3.7 Customizing transaction.............................................................................................................. 3.8 Retention Period.......................................................................................................................... 3.9 Residence time............................................................................................................................ 3.10 Info Tables for Archive Files.................................................................................................... 3.11 Exit Routine Assignment Generation.......................................................................................

4. PROCESS FLOW FOR THE SAP DATA ARCHIVING.......................... 4.1 Creating Archive Files................................................................................................................. 4.2 Storing Archive Files................................................................................................................... 4.3 Execute delete program...............................................................................................................

5. An example of Archiving Process...............................................................

6. Reference.....................................................................................................

1. Introduction

In an introduction part of Data archiving, we are going to see the difference between the data back up and data archiving. Everyone is aware of data back up so difference between data back up and data archiving will help to understand, what Data Archiving is ?.

The key difference between the data backup anddata archiving is that data backups are designed for the rapid recovery of operation data, while data archiving stores data that's no longer in day to day use but must be retained. Data backup applications tend to keep data in a proprietary format which can be a problem for long term data retention. Data archiving is intended as repository for data that needs to be stored for periods that may extend to decades.

In general Data archiving means deleting huge volumes of data that is no longer required in the database and writing it to the some file system or any third party usage system. SAP provides the service for 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. Archiving objects are used to archive data objects in SAP.

2.Archiving Objects.

2.1 Definition:

The archiving object is a central component of SAP Data Archiving. The archiving object specifies precisely which data is archived and how. It describes which database objects must be handled together as a single business object. And interprets the data irrespective of the technical specifications at the time of archiving (such as release and hardware) (From saphelp.com)

2.2 Archiving objects and related tables:

Transaction code DB15 gives archiving object and its related tables, it means, if you know the name of the Archiving object you can identify tables and, if you know the table then you can identify the related archiving object as illustrated below.

Example: If we have to find Archiving object for table EABPL then,

Transaction Code: DB15

So we have archiving object as ISU_BBP which will archive the data from table EABPL.

2.3 Transaction Code SARA and its use for Administration of archivingobjects:

Important T-codes which is useful while working with Archiving object isSARA

TIP: There are archiving object specific transaction code. One can get the list of all object specific transaction code through the transaction code SDMO. SDMO is transaction code which gives list of transaction codes along with its short description.

Go to transaction code SDMO and enter SEARCH TEXT FOR as ARCHIVING and execute.

2.3.0 SARA:

Transaction SARA is used to administer the Archiving Object.

2.3.1 ICONs and their uses are explained below.

2.3.2 Network Graphic: This gives the Archiving session sequence.

e.g. If we have to archive the Budget billing plan using archiving object, the sequence that we have to follow is Archive print document line item---Then---Archive print document header----and then-----Archive Budget billing plan.

2.3.3 Information:Information ICONgives all technical as well as functional information on the entered Archiving object.

2.3.4 Job Overview: This ICON takes you to simple job selection (SM37) screen. You will be able to see the job name, if you have scheduled any archiving object.

2.3.5 Log: This ICON takes you to the log summary of the executed archival object. Job logs, spool lists, job overview.

2.3.5 Customizing: This ICON takes you to the customization done for Archiving object which we are going to see while dealing with transaction code AOBJ.

2.3.7 Database Table: This ICON takes you to the Transaction code DB15 and gives the details of tables from which DATA is archived.

2.3.8 Information system: This ICON takes you to the Central management of the Archive information system. Using this you can restore the archived data.

3. AOBJ - Configuration of Archiving Objects.

AOBJ- AOBJ is a transaction code which deals with the configuration of archiving object.

In this document we are going to see archiving object ISU_BBP to understand archiving objects configuration.

3.1 Structure definition:

Select the archiving object & click on the structure definition.

Structure definition folder of archiving object gives list of database tables from which data will be archived. For standard SAP objects this is preconfigured.

3.2 Tables from which you only delete entries:

This folder of archiving object contains list of database tables from which data will only be deleted and not archived. For standard SAP archival objects, this is preconfigured. An example of archiving object which we have taken does not have such tables. Hence records are blank. Entries will be there for archival object for which such tables exist.

3.3 Maintain network Graphic:

This contains the list of predecessor archival object. It means to archive our aimed object one should archive the predecessor archival object. This is preconfigured for standard SAP object. Before executing archival object ISU_BBP requisite is that object ISU_PRDOCH should be executed successfully.

3.4Customizing settings:

Customizing settings contain the details about Archive file size, Logical file name, and settings for delete program, content Repositories and the sequence of deletion.

3.5 Archiving classes Used:

This folder contains the details about the archiving classes used by particular Archiving Object.Archiving classes make possible object-oriented processing of the data to be archived. They simplify access to the data of business entities for archiving. Archival object ISU_BBP which we have selected as an example does not have any archival classes used. For reference we can see the archival object named IDOC.

3.6 Read programs:

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

3.7Customizing transaction:

This contains the transaction code for the application specific customizing for the relevant archiving object. Once this code is entered, you can go to the application specific Customizing transaction, which is often used for entering residence times and retention time.
E.g. Archiving Object ISU_BBP

3.8 Retention Period:

The retention period is the entire time that data spends in the database before it is archived.

3.9 Residence time:

The residence time is the minimum length of time that data must spend in the database before it meets the achievability criteria.The retention period cannot be set.

If the residence time is a month, data that has been in the system for two months will be archived. Data that is only three weeks old remains in the database.

3.10 Info Tables for Archive Files:

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

3.11 Exit Routine Assignment Generation.

This contains details about the customizing code (user exits/ Business add in the archive and delete programs.

4. PROCESS FLOW FOR THE SAP DATA ARCHIVING

Different actions that can be taken on to the Archiving object are enlisted just below the name of the archiving object in transaction SARA.

SAP Data archiving mainly involves three steps:

1) Creating the Archive files

2) Store the archive files

3) Execute delete program

4.1 Creating the Archive files:

Write Program creates an archive file. The data to be archived is then read from the database and is written to the archive file in the background. This process continues until one of following three events occurs.

A) All the data is written to an archive file.

B) Archiving is not complete, but the archive file reaches the maximum size Specified in archiving object-specific Customizing

C) The archiving is not yet finished, but the archive file contains the maximum Number of data objects specified in Customizing.

4.2 Storing Archive Files:
Once created by the write program, archive files can be stored in various ways.
Content Management Service: If a storage system is connected to the SAP system, and the write run has completed successfully (the corresponding settings are contained in Archiving Object-Specific Customizing) the storage system is instructed to store the archive files. You can also store archive files manually.
HSM systems: If you maintain the file path of an HSM system in Customizing (transaction FILE), you don’t need to communicate with the archive system using Archive Link because the HSM system stores the files autonomously. If you use an HSM system, it is sufficient to maintain the file name in Customizing (Transaction FILE). You do not then need to communicate with the storage system using the Content Management Service, because the HSM system stores the files on tertiary media according to access frequency and disk space.
Manual storage: Once the delete program has processed the relevant archive file, you can manually copy archive files to tape.

4.3 Execute delete programs:
After closing the first archive file, the archive management system creates a new archive file and continues with the archiving process. While this happens, another program reads the archived data from the completed archive file and deletes it from the database. This procedure guarantees that only data that has been correctly saved in the archive file is deleted from the database.
If you do not carry out deletion until after the data has been stored, you can make a setting in Archiving Object-Specific Customizing so that the system will read archive files the from the storage system during deletion. In this way, you can detect errors in good time which might arise when transferring or saving the archive files in the storage system.

5. An example of Archiving Process

Here is an example of archival of Print Document Header lines. To archive the print document header lines, Archiving object used is ISU_PRDOCH.

Network graphic shows that, before archiving print document header line, print document line item should be archived. Print document line items can archive using archiving object ISU_PRDOCL.Soarchival of print document header is two step processes. First step we archive ISU_PRDOCL and second step we archive ISU_PRDOCH.

STEP 1:

Archival of object ISU_PRDOCL

We are archiving the print document: 101000000049

Actions that can be taken on archiving object are described below.

1) Preprocessing:

This is optional activity. Some archiving objects require a preprocessing program that prepares the data for archiving. This preprocessing program marks data to be archived, but it does not delete any data from the database. Preprocessing programs must always be scheduled manually and are run from Archive Administration.

Preprocessing Result for ISU_PRDOCL

Clicking on the spool

Preprocessing log says that document can be archived

2) Write:

This program creates archive files and writes data to them. At this point, however, no data is being deleted from the database. You can specify in archiving object-specific Customizing whether the next phase (delete) is to take place automatically after the archive files have been created. Delete jobs can also be event-triggered. To do this, you set up the trigger event in archiving object-specific Customizing.

Clicking on the spool

Log Summary for write job:

Log summary for store job

Log summary for Delete job

Now there is no entry in the table DBERDL for print document which we archived.
It means print document line items are archived.

But there will be entry in the table ERDK as we have not archived header data for print document.

STEP 2: Archival print document header (ISU PRDOCH)

Network graphic shows that archival of Print document line items (ISU_PRDOCL) is successful. Now we can archive print document header line.

Performing the same steps as we did for ISU_PRDOCL

1) Preprocessing:

Log for preprocessing job:

2)Writing:

Log summary for writing:

Log for storing job

Log for delete job

Since we have archived print document header for document 101000000049, entry will not be there in ERDK table

Reference

1) Website: help.sap.com

Link: http://help.sap.com/saphelp_nw2004s/helpdata/EN/8d/3e4d2f462a11d189000000e8323d3a/frameset.htm THANK YOU