During the archiving business transaction, the system reads the data from the database and stores them in an archiving file. These data are generally deleted and therefore no longer available for online transactions.
Archiving helps to reduce the load on the system and cuts program runtimes by minimizing the quantities of data to be processed.
This is achieved in the system through a two-step method.
1. Archiving Session
In the first step, the data are read from the database and written to an archiving file.
The data are recorded through logical selection criteria.
2. Deletion Program:
The archive file is now read by the system. Data marked for deletion are completely or partially deleted on the database. The system deletes only the data specified in the archiving program. The data must also be deletable.
In Cost Center Accounting transaction data, with their corresponding cost center mater data, can be archived by object. For one cost center (dependent on the object definition an the selection criteria) the system generally determines, archives and deletes (except line items) all data (totals records, line items, and so on). The evaluation of archives (not currently supported) is made easier by the object orientation.
The following archiving objects are available:
Name |
Archiving Object |
Log. Database |
Cost centers (overall) |
CO_COSTCTR |
CRK |
Cost centers (actual data) |
CO_CCTR_ID |
CIK |
Cost centers (planning data) |
CO_CCTR_PL |
CPK |
Cost centers (line items) |
CO_CCTR_EP |
CEK |
Fully reversed allocations, assessments, distribution, periodic repostings and indirect activity allocation. |
CO_ALLO_ST |
SAK |
You therefore have the option of executing archiving in full, or only for sub-areas.
In Cost Center Accounting the generating of the archive, as well as the automatic start of the deletion program after closing an archive are predefined. You can adapt these settings to meet your requirements for any archiving object in general Customizing for archiving (Customizing: Overview).

Archiving does not reset the current number level of the CO document. You can not reload the data into the database.
We now show you an example of archiving for planning data.
Choose
to see more information about this demo.
Process Chain
Choose
to see the data used during this demo. Then select the first of the processes listed below:
Creating a Variant for an Archive File
Creating Archive Files
Spool Management
Archive Management
Object Structure
Reading Archive Files