Managing Archived Change Documents

Change Document Archiving Concept

Change documents can be archived in two ways.

  • Archiving together with the application data

    The application data to which the change documents belong are archived with the application archiving object. This archiving object contains the change document archiving class CHANGEDOCU. The application archive contains the application data and the change documents. This is often the case for transaction data, such as purchasing documents and orders that are regularly archived.

  • Archiving separately from the application data

    Master data remains in the system for a long time, and is not, or rarely, archived. The master data change documents can only be archived independently of the application object, with the archving object CHANGEDOCU. This is, for example the case for change document object MATERIAL. Material master data is not archived.

Function Group SCD5

This function module is the archiving class CHANGEDOCU for change documents
CHANGEDOCUMENT_READ_WITHOUT_ED

The function module reads change documents without formatting, cross-client.

The object class is required, as a minimum.
CHANGEDOCU_ARCHIVE_GET_TABLE Change Documents/Archiving: Read archived objects.
CHANGEDOCU_ARCHIVE_NO_CONTROL Archiving, set Soppress Control Information flag.
CHANGEDOCU_ARCHIVE_OBJECT

This function module passes the objects for which change documents are to be archived, to the archiving.

This function module must be called after the function module ARCHIVE_NEW_OBJECT. The change documents are then archived together with the archiving object by the function module ARCHIVE_SAVE_OBJECT.

The deletion flag indicates whether change documents are to be deleted by the standard archiving deletion program after archiving.
CHANGEDOCU_ARCHIVE_PUT_TABLE Adjustment to SLO archiving conversion.
CHANGEDOCU_CONVERT_OLD_DATA

Convert old change documents into new class format.

The function module converts old change documents into the new archiving class CHANGEDOCU format. Special development to convert archive QM_CONTROL.
CHANGEDOCU_DELETE_ARCHIVE_OBJ

The function module deletes archived change documents.

An authorization check is performed. The caller needs authorization to delete change documents (authorization object 'Change Documents').

All change documents which were flagged for deletion when the function module CHANGEDOCUMENT_ARCHIVE_OBJECT was called, are flagged for deletion.

The documents to be deleted are collected and only then deleted at COMMIT WORK in the calling program.

This also applies if the function module is called several times.

This improves performance compared to deleting after each call.
CHANGEDOCU_GET_DELETE_FLAGS Read archiving class CHANGEDOCU deletion flag.
CHANGEDOCU_MODIFY_DELETE_FLAGS Change archiving class CHANGEDOCU deletion flag.
CHANGEDOCU_READ_ARCHIVE_OBJECT

This function module gets all change documents of the object previously read by the function module ARCHIVE_GET_NEXT_OBJECT.

The handle must have been created with the function module ARCHIVE_OPEN_FOR_READ (or ARCHIVE_OPEN_FOR_MOVE).
CHANGEDOCU_RELOAD_ARCHIVE_OBJ This function module writes all data of the object previously read by the function module ARCHIVE_GET_NEXT_OBJECT back to the database.