Managing Archived Change Documents  

Concept for Archiving Change Documents

Change documents can be archived in two different ways.

●      Archiving together with application data
The application data that the change documents belong to are archived using the archiving object. This archiving object includes the archiving class CHANGEDOCU of the change documents. The application data is in the application archive together with the change documents. This is often the case for transaction data, such as purchasing documents, requests, and so on that are regularly archived.

●      Archiving separately from application data
Stammdaten verbleiben selbst über einen langen Zeitraum im System und werden nicht oder nur sehr selten archiviert. The change documents of the master data can only be archived independently from the change object using the archiving object CHANGEDOCU. For example, as with the change document object MATERIAL. Material master data is not archived.

 

Function Group SCD5

This function module represents the archiving class CHANGEDOCU for the change documents (see use of archiving classes in the Archiving section of this documentation):

●       CHANGEDOCUMENT_READ_WITHOUT_ED

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

The object class is required, as a minimum.

●       CHANGEDOCU_ARCHIVE_GET_TABLE

Change documents/archiving: Reading archived objects.

●      CHANGEDOCU_ARCHIVE_NO_CONTROL

Archiving, set the Suppressing Tax Information flag.

●      CHANGEDOCU_ARCHIVE_OBJECT

With this function module you transfer to archiving the objects for which there are change documents that are to be archived.

Calling this function module must take place after calling the function module ARCHIVE_NEW_OBJECT. The change documents are then archived together with the archiving object using the function module ARCHIVE_SAVE_OBJECT.

Using the deletion flag, you can determine whether the change documents are to be deleted from the archiving using the standard deletion program after they have been archived successfully or if they are to be retained in the system.

●      CHANGEDOCU_ARCHIVE_PUT_TABLE

Adapting to SLO archive conversion.

●      CHANGEDOCU_CONVERT_OLD_DATA

Converting older change documents to new class format.

The function module converts old change documents to the new format of the archiving class CHANGEDOCU. Special development for converting the QM_CONTROL archive.

●      CHANGEDOCU_DELETE_ARCHIVE_OBJ

The function module is for deleting archived change documents.

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

All change documents that have been given a deletion flag when calling the function module CHANGEDOCUMENT_ARCHIVE_OBJECT are selected for deletion.

The documents to be deleted are collected and then deleted when a COMMIT WORK is executed in the calling program.

This is also true for multiple calls of this function module.

This achieves an improvement in the performance as opposed to deleting for each individual call.

●      CHANGEDOCU_GET_DELETE_FLAGS

Query delete flags for archiving class CHANGEDOCU.

●      CHANGEDOCU_MODIFY_DELETE_FLAGS

Change delete flags for archiving class CHANGEDOCU.

●      CHANGEDOCU_READ_ARCHIVE_OBJECT

This function module gets all change documents of the object that was previously read using 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 loads all data of the object that was previously read using the function module ARCHIVE_GET_NEXT_OBJECT.