SAP ARCHIV_GET_SERVER_META Function Module for









ARCHIV_GET_SERVER_META is a standard archiv get server meta SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 archiv get server meta FM, simply by entering the name ARCHIV_GET_SERVER_META into the relevant SAP transaction such as SE37 or SE38.

Function Group: OPTD
Program Name: SAPLOPTD
Main Program: SAPLOPTD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ARCHIV_GET_SERVER_META 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 'ARCHIV_GET_SERVER_META'"
  EXPORTING
*  ARCHIV_DOC_INDEX = ' ' "Direct access to part document
   AR_OBJECT =  "Object type to be stored
   OBJECT_ID =  "Unique object key of the application
   PATH =  "
   SAP_OBJECT =  "Calling application

EXCEPTIONS
   ERROR_ARCHIV = 1    ERROR_COMMUNICATIONTABLE = 2    ERROR_CONNECTIONTABLE = 3    ERROR_KERNEL = 4    ERROR_PARAMETER = 5    NOT_UNIQUE = 6
.



IMPORTING Parameters details for ARCHIV_GET_SERVER_META

ARCHIV_DOC_INDEX - Direct access to part document

Data type: SAPB-SAPADOKID
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

AR_OBJECT - Object type to be stored

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

OBJECT_ID - Unique object key of the application

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

PATH -

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

SAP_OBJECT - Calling application

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

EXCEPTIONS details

ERROR_ARCHIV - Error from IXARCON

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

ERROR_COMMUNICATIONTABLE - Table TOAAR

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

ERROR_CONNECTIONTABLE - Error from the linking tables

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

ERROR_KERNEL - Error from SAP kernels

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

ERROR_PARAMETER - Invalid transfer parameters

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

NOT_UNIQUE - Object contains several archive authorization objects

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

Copy and paste ABAP code example for ARCHIV_GET_SERVER_META 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:
lv_error_archiv  TYPE STRING, "   
lv_archiv_doc_index  TYPE SAPB-SAPADOKID, "   SPACE
lv_ar_object  TYPE TOAOM-AR_OBJECT, "   
lv_error_communicationtable  TYPE TOAOM, "   
lv_object_id  TYPE SAPB-SAPOBJID, "   
lv_error_connectiontable  TYPE SAPB, "   
lv_path  TYPE SAPB-SAPPFAD, "   
lv_error_kernel  TYPE SAPB, "   
lv_sap_object  TYPE TOAOM-SAP_OBJECT, "   
lv_error_parameter  TYPE TOAOM, "   
lv_not_unique  TYPE TOAOM. "   

  CALL FUNCTION 'ARCHIV_GET_SERVER_META'  "
    EXPORTING
         ARCHIV_DOC_INDEX = lv_archiv_doc_index
         AR_OBJECT = lv_ar_object
         OBJECT_ID = lv_object_id
         PATH = lv_path
         SAP_OBJECT = lv_sap_object
    EXCEPTIONS
        ERROR_ARCHIV = 1
        ERROR_COMMUNICATIONTABLE = 2
        ERROR_CONNECTIONTABLE = 3
        ERROR_KERNEL = 4
        ERROR_PARAMETER = 5
        NOT_UNIQUE = 6
. " ARCHIV_GET_SERVER_META




ABAP code using 7.40 inline data declarations to call FM ARCHIV_GET_SERVER_META

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 SAPADOKID FROM SAPB INTO @DATA(ld_archiv_doc_index).
DATA(ld_archiv_doc_index) = ' '.
 
"SELECT single AR_OBJECT FROM TOAOM INTO @DATA(ld_ar_object).
 
 
"SELECT single SAPOBJID FROM SAPB INTO @DATA(ld_object_id).
 
 
"SELECT single SAPPFAD FROM SAPB INTO @DATA(ld_path).
 
 
"SELECT single SAP_OBJECT FROM TOAOM INTO @DATA(ld_sap_object).
 
 
 


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!