Archiving Change Documents (BC-SRV-ASF-CHD)

Background

Application programs write change documents for statutory or technical reasons. They must sometimes be retained for a long time. Documents which no longer require direct access can be archived, to reduce the database load. They are then saved in these archives for the statutory or technically-required period.

Technical Implementation

The change document archiving tools were developed with the Archive Development Kit (ADK), which supports object-oriented programming. The archiving object CHANGEDOCU contains the required database tables and the archiving class CHANGEDOCU with function modules to process them. Only programs can access the archiving object CHANGEDOCU. All the function modules in the archiving class CHANGEDOCU belong to the function group SCD5. This function group also includes the function modules which the archiving programs use to call the ADK functions.

Database tables

The change document archiving object CHANGEDOCU contains the following database tables:

Table	Description
CDKEYTAB	Virtual table with the object key (only in archive, not in database)
CDHDR	Change document header in the database
CDPOS	Change document items in the database
CDPOS_UID	Change document item key per table, if it is > 70 characters. CDPOS-TBAKEY then contains the UID for this entry.
CDPOS_STR	Change document item for STRING fields. CDPOS-TBAKEY then contains the UID for this entry

Authorizations

To archive, you need authorizatio for:

Archiving in general

For more information, see User Authorization Checks

Integration

You can display archived change documents with the Archive Explorer (transaction SARE).

To display the tables in archiving object CHANGEDOCU in the Archive Information System, you need an information structure based on the standard field catalog SAP_CHANGEDOCU1 delivered by SAP. The information structure must be set up and active.

For more information about information structures, see also Using the Archive Information System.