Functions
This function module from the ADK interface calls the delete methodsfor all archive classes in the archiving object. The data contained inthe current data object is deleted in the database for all classes.
A delete program must call ARCHIVE_DELETE_OBJECT_DATA every time aftercalling ARCHIVE_GET_NEXT_OBJECT(within the same loop for the same handle) to delete the class data forthe current data object (that is, the last data object that was readfrom the archive file). It is therefore not sufficient only to callARCHIVE_DELETE_OBJECT_DATA by <(>
<<)>Commit counter> data objects or to call it only in a subroutineregistered using a perform on commit.
DATA: HANDLE LIKE SY-TABIX.
...
CALL FUNCTION 'ARCHIVE_GET_NEXT_OBJECT'
...
CALL FUNCTION 'ARCHIVE_DELETE_OBJECT_DATA'
EXPORTING
ARCHIVE_HANDLE = HANDLE.
The sample program SFLIGHTD demonstrates how this is called correctly.

Further Notes
The ADK interface dos not offer an (object-specific) function fordeleting the data that was not archived using a class.
This means that all data that was written to data objects usingARCHIVE_PUT_RECORD must be deletedmanually from the database using the delete program. Contrary tocalling ARCHIVE_DELETE_OBJECT_DATA, this can occur in groups of data objects.
INCLUDE 'ARCHIVE_PARAM_HANDLE_READ' OBJECT DOKU ID TX
In this case the archive handle is used to specify the archive classesof a particular archive object.