Archive Files


The AFB operates using data objects. An archive file is divided into a header and several data objects. A data object is often an instance of the business object that corresponds to the archiving object.

For archiving object SD_VBAK the data for an individual sales order is saved in one data object. Such a correspondence does not have to apply to every archiving object, however.


A data object always consists of exactly the data that is written to the archive by the write program between calling up the function modules ARCHIVE_NEW_OBJECT and ARCHIVE_SAVE_OBJECT. Consequently, everything that can be read between the first and second call up of function module ARCHIVE_GET_NEXT_OBJECT belongs to the same data object.

The AFB operates using these data objects. Except for the hex display, the AFB always displays exactly one object. During the search, the system looks for data objects that correspond to particular criteria.

You can specify a data object by entering the archive file and the offset, or by entering the archive file and the number of the data object. In the AFB there is always a current data object that is represented at least by the entry of archive file and offset. The system often displays the number of the data object in addition. All displaying functions and functions for relative navigation (Next File, Previous File, Continue) relate to the current object.

Sequence of the Archive Files

The AFB always arranges archive files and data objects according to the same pattern. The data is sorted according to archiving object, session and archive file key. The runs are always displayed in descending order, so that the most recent runs are at the top.

The AFB sorting rules:

·        Files are arranged alphabetically in ascending order according to their archiving objects.

·        More recent archiving runs come before older ones

·        Within the sessions the files are in ascending order

Use of this sort order:

·        In the archive files overview

·        When searching in the list of the files to be searched

·        During the search the files are dealt with in this order

·        For the functions for relative navigation (Next File, Previous File, …) this sequence is used as the basis.

Authorization Checks

In addition to checking the authorization to access the archive (authorization object S_ARCHIVE), checks have been implemented in the AFB that allow or forbid the display of archived data in a similar way as for the Data Browser (transaction SE16). This involves the display authorization for authorization object S_TABU_DIS. The authorization to display data from a table should not change due to it being archived. The same should apply for archived data as for data from the database.

Required authorizations for different areas



Data Object

User requires display authorization for the table to be displayed. This means not all data is necessarily displayed for a data object (you receive corresponding messages in the log).

If the user does not have authorization for any of the tables of the data object, then nothing is displayed for the current data object.


User requires display authorization for the tables. Only those tables for which the user has authorization can be displayed.

Hex Display

User requires display authorization for all tables that relate to the archiving object of the file to be displayed.

If the user lacks authorization for one or more tables then nothing is displayed for the archive file.


A user can only search for the content of tables for which he or she has authorization.