SAP ARCHIVE_GET_INFORMATION Function Module for Archive Object Information Is Transferred Due to a Handle









ARCHIVE_GET_INFORMATION is a standard archive get information SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Archive Object Information Is Transferred Due to a Handle processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for archive get information FM, simply by entering the name ARCHIVE_GET_INFORMATION into the relevant SAP transaction such as SE37 or SE38.

Function Group: ARCH
Program Name: SAPLARCH
Main Program: SAPLARCH
Appliation area: S
Release date: 03-Jan-1995
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ARCHIVE_GET_INFORMATION pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'ARCHIVE_GET_INFORMATION'"Archive Object Information Is Transferred Due to a Handle
EXPORTING
ARCHIVE_HANDLE = "Open Archive Handle

IMPORTING
ARCHIVE_CREATION_DATE = "Date on Which the Archive Was Created
ARCHIVING_CLASS = "Archiving Class
OBJECT_NUMBER_IN_FILE = "Number of objects in an archive file
OBJECT_NUMBER_IN_RUN = "Number of Objects in an Archiving Session
ARCHIVE_CREATION_RELEASE = "Release Uner Which the Archive Was Created
ARCHIVE_CREATION_SYSTEM = "SAP System Uder Wich the Archive Was Created
ARCHIVE_DOCUMENT = "Archiving Session According to Archive Management
ARCHIVE_NAME = "Archive Key According to Archive Management
OBJECT = "Name of the Object Edited with the Handle
ARCHIVE_CODE_PAGE = "Name of Codepage
ARCHIVE_NUMBER_FORMAT = "Number Format Name
ADK_VERSION = "

TABLES
* USED_CLASSES = "

EXCEPTIONS
INTERNAL_ERROR = 1 WRONG_ACCESS_TO_ARCHIVE = 2
.



IMPORTING Parameters details for ARCHIVE_GET_INFORMATION

ARCHIVE_HANDLE - Open Archive Handle

Data type: SY-TABIX
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ARCHIVE_GET_INFORMATION

ARCHIVE_CREATION_DATE - Date on Which the Archive Was Created

Data type: HEADA-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVING_CLASS - Archiving Class

Data type: ARCH_CLAS_
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_NUMBER_IN_FILE - Number of objects in an archive file

Data type: ADMI_COUNT
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_NUMBER_IN_RUN - Number of Objects in an Archiving Session

Data type: ADMI_COUNT
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVE_CREATION_RELEASE - Release Uner Which the Archive Was Created

Data type: HEADA-SAPRL
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVE_CREATION_SYSTEM - SAP System Uder Wich the Archive Was Created

Data type: HEADA-SYSID
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVE_DOCUMENT - Archiving Session According to Archive Management

Data type: ADMI_RUN-DOCUMENT
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVE_NAME - Archive Key According to Archive Management

Data type: HEADA-ARKEY
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT - Name of the Object Edited with the Handle

Data type: ARCH_OBJ-OBJECT
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVE_CODE_PAGE - Name of Codepage

Data type: TCP00-CPCODEPAGE
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVE_NUMBER_FORMAT - Number Format Name

Data type: TCP00-CPCODEPAGE
Optional: No
Call by Reference: No ( called with pass by value option)

ADK_VERSION -

Data type: HEADA-SAPRL
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ARCHIVE_GET_INFORMATION

USED_CLASSES -

Data type: ADK_CLASSES
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INTERNAL_ERROR - Internal error

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

WRONG_ACCESS_TO_ARCHIVE - Incorrect Archive Access

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ARCHIVE_GET_INFORMATION Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lt_used_classes  TYPE STANDARD TABLE OF ADK_CLASSES, "   
lv_archive_handle  TYPE SY-TABIX, "   
lv_internal_error  TYPE SY, "   
lv_archive_creation_date  TYPE HEADA-DATUM, "   
lv_archiving_class  TYPE ARCH_CLAS_, "   
lv_object_number_in_file  TYPE ADMI_COUNT, "   
lv_object_number_in_run  TYPE ADMI_COUNT, "   
lv_wrong_access_to_archive  TYPE ADMI_COUNT, "   
lv_archive_creation_release  TYPE HEADA-SAPRL, "   
lv_archive_creation_system  TYPE HEADA-SYSID, "   
lv_archive_document  TYPE ADMI_RUN-DOCUMENT, "   
lv_archive_name  TYPE HEADA-ARKEY, "   
lv_object  TYPE ARCH_OBJ-OBJECT, "   
lv_archive_code_page  TYPE TCP00-CPCODEPAGE, "   
lv_archive_number_format  TYPE TCP00-CPCODEPAGE, "   
lv_adk_version  TYPE HEADA-SAPRL. "   

  CALL FUNCTION 'ARCHIVE_GET_INFORMATION'  "Archive Object Information Is Transferred Due to a Handle
    EXPORTING
         ARCHIVE_HANDLE = lv_archive_handle
    IMPORTING
         ARCHIVE_CREATION_DATE = lv_archive_creation_date
         ARCHIVING_CLASS = lv_archiving_class
         OBJECT_NUMBER_IN_FILE = lv_object_number_in_file
         OBJECT_NUMBER_IN_RUN = lv_object_number_in_run
         ARCHIVE_CREATION_RELEASE = lv_archive_creation_release
         ARCHIVE_CREATION_SYSTEM = lv_archive_creation_system
         ARCHIVE_DOCUMENT = lv_archive_document
         ARCHIVE_NAME = lv_archive_name
         OBJECT = lv_object
         ARCHIVE_CODE_PAGE = lv_archive_code_page
         ARCHIVE_NUMBER_FORMAT = lv_archive_number_format
         ADK_VERSION = lv_adk_version
    TABLES
         USED_CLASSES = lt_used_classes
    EXCEPTIONS
        INTERNAL_ERROR = 1
        WRONG_ACCESS_TO_ARCHIVE = 2
. " ARCHIVE_GET_INFORMATION




ABAP code using 7.40 inline data declarations to call FM ARCHIVE_GET_INFORMATION

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single TABIX FROM SY INTO @DATA(ld_archive_handle).
 
 
"SELECT single DATUM FROM HEADA INTO @DATA(ld_archive_creation_date).
 
 
 
 
 
"SELECT single SAPRL FROM HEADA INTO @DATA(ld_archive_creation_release).
 
"SELECT single SYSID FROM HEADA INTO @DATA(ld_archive_creation_system).
 
"SELECT single DOCUMENT FROM ADMI_RUN INTO @DATA(ld_archive_document).
 
"SELECT single ARKEY FROM HEADA INTO @DATA(ld_archive_name).
 
"SELECT single OBJECT FROM ARCH_OBJ INTO @DATA(ld_object).
 
"SELECT single CPCODEPAGE FROM TCP00 INTO @DATA(ld_archive_code_page).
 
"SELECT single CPCODEPAGE FROM TCP00 INTO @DATA(ld_archive_number_format).
 
"SELECT single SAPRL FROM HEADA INTO @DATA(ld_adk_version).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!