SAP ARCHIV_DISPLAY_META Function Module for
ARCHIV_DISPLAY_META is a standard archiv display 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 display meta FM, simply by entering the name ARCHIV_DISPLAY_META into the relevant SAP transaction such as SE37 or SE38.
Function Group: OPTB
Program Name: SAPLOPTB
Main Program: SAPLOPTB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ARCHIV_DISPLAY_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_DISPLAY_META'".
EXPORTING
* ARCHIV_DOC_INDEX = ' ' "Direct access to part document
* AR_OBJECT = ' ' "Object type to be stored
* AUTH_FLAG = ' ' "
* DISPLAY_FLAG = ' ' "List (space), documents direct (1) or icons (2)
OBJECT_ID = "Unique object ends of the application
SAP_OBJECT = "Calling application
* WINDOW_ID = ' ' "Unique identifier for display windows
* WINDOW_TITLE = ' ' "Title at the upper border of window
* NO_WORKFLOWINFOS = ' ' "
EXCEPTIONS
ERROR_ARCHIV = 1 ERROR_COMMUNICATIONTABLE = 2 ERROR_CONNECTIONTABLE = 3 ERROR_KERNEL = 4 ERROR_PARAMETER = 5 ERROR_VERSION = 6
IMPORTING Parameters details for ARCHIV_DISPLAY_META
ARCHIV_DOC_INDEX - Direct access to part document
Data type: SAPB-SAPADOKIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
AR_OBJECT - Object type to be stored
Data type: TOAOM-AR_OBJECTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
AUTH_FLAG -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY_FLAG - List (space), documents direct (1) or icons (2)
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECT_ID - Unique object ends of the application
Data type: SAPB-SAPOBJIDOptional: No
Call by Reference: No ( called with pass by value option)
SAP_OBJECT - Calling application
Data type: TOAOM-SAP_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
WINDOW_ID - Unique identifier for display windows
Data type: SAPB-SAPWINIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WINDOW_TITLE - Title at the upper border of window
Data type: SAPB-SAPWINTITLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_WORKFLOWINFOS -
Data type: TOAOM-AR_STATUSDefault: SPACE
Optional: Yes
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 - No linking table created
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)
ERROR_VERSION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ARCHIV_DISPLAY_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, " SPACE | |||
| lv_error_communicationtable | TYPE TOAOM, " | |||
| lv_auth_flag | TYPE TOAOM, " SPACE | |||
| lv_error_connectiontable | TYPE TOAOM, " | |||
| lv_display_flag | TYPE TOAOM, " SPACE | |||
| lv_error_kernel | TYPE TOAOM, " | |||
| lv_object_id | TYPE SAPB-SAPOBJID, " | |||
| lv_error_parameter | TYPE SAPB, " | |||
| lv_sap_object | TYPE TOAOM-SAP_OBJECT, " | |||
| lv_error_version | TYPE TOAOM, " | |||
| lv_window_id | TYPE SAPB-SAPWINID, " SPACE | |||
| lv_window_title | TYPE SAPB-SAPWINTITL, " SPACE | |||
| lv_no_workflowinfos | TYPE TOAOM-AR_STATUS. " SPACE |
|   CALL FUNCTION 'ARCHIV_DISPLAY_META' " |
| EXPORTING | ||
| ARCHIV_DOC_INDEX | = lv_archiv_doc_index | |
| AR_OBJECT | = lv_ar_object | |
| AUTH_FLAG | = lv_auth_flag | |
| DISPLAY_FLAG | = lv_display_flag | |
| OBJECT_ID | = lv_object_id | |
| SAP_OBJECT | = lv_sap_object | |
| WINDOW_ID | = lv_window_id | |
| WINDOW_TITLE | = lv_window_title | |
| NO_WORKFLOWINFOS | = lv_no_workflowinfos | |
| EXCEPTIONS | ||
| ERROR_ARCHIV = 1 | ||
| ERROR_COMMUNICATIONTABLE = 2 | ||
| ERROR_CONNECTIONTABLE = 3 | ||
| ERROR_KERNEL = 4 | ||
| ERROR_PARAMETER = 5 | ||
| ERROR_VERSION = 6 | ||
| . " ARCHIV_DISPLAY_META | ||
ABAP code using 7.40 inline data declarations to call FM ARCHIV_DISPLAY_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). | ||||
| DATA(ld_ar_object) | = ' '. | |||
| DATA(ld_auth_flag) | = ' '. | |||
| DATA(ld_display_flag) | = ' '. | |||
| "SELECT single SAPOBJID FROM SAPB INTO @DATA(ld_object_id). | ||||
| "SELECT single SAP_OBJECT FROM TOAOM INTO @DATA(ld_sap_object). | ||||
| "SELECT single SAPWINID FROM SAPB INTO @DATA(ld_window_id). | ||||
| DATA(ld_window_id) | = ' '. | |||
| "SELECT single SAPWINTITL FROM SAPB INTO @DATA(ld_window_title). | ||||
| DATA(ld_window_title) | = ' '. | |||
| "SELECT single AR_STATUS FROM TOAOM INTO @DATA(ld_no_workflowinfos). | ||||
| DATA(ld_no_workflowinfos) | = ' '. | |||
Search for further information about these or an SAP related objects