SAP ARCHIV_CONNECTINFO_GET_META Function Module for

Search SAP Function Modules

ARCHIV_CONNECTINFO_GET_META is a standard archiv connectinfo get 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 connectinfo get meta FM, simply by entering the name ARCHIV_CONNECTINFO_GET_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_CONNECTINFO_GET_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_CONNECTINFO_GET_META'"
  EXPORTING
*  ARCHIV_ID = ' ' "
*  AR_OBJECT = ' ' "Object type to be stored
*  DOC_TYPE = ' ' "
   OBJECT_ID =  "Unique object key of the application
   SAP_OBJECT =  "Calling application
*  LIMITED =  "SAP ArchiveLink: Status (X = active, otherwise inactive)

 IMPORTING
   NUMBER =  "
   REDUCEDBYLIMIT =  "SAP ArchiveLink: Status field
   REDUCEDBYAUTHORITY =  "SAP ArchiveLink: Status field
   COUNT =  "

TABLES
*  CONNECT_INFO =  "archiv_id and archiv_doc_id

EXCEPTIONS
   ERROR_CONNECTIONTABLE = 1 

.

IMPORTING Parameters details for ARCHIV_CONNECTINFO_GET_META

ARCHIV_ID -

Data type: TOAV0-ARCHIV_ID
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
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DOC_TYPE -

Data type: TOAOM-DOC_TYPE
Default: SPACE
Optional: Yes
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)

SAP_OBJECT - Calling application

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

LIMITED - SAP ArchiveLink: Status (X = active, otherwise inactive)

Data type: TOAOM-AR_STATUS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ARCHIV_CONNECTINFO_GET_META

NUMBER -

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

REDUCEDBYLIMIT - SAP ArchiveLink: Status field

Data type: SAESTATUS
Optional: No
Call by Reference: Yes

REDUCEDBYAUTHORITY - SAP ArchiveLink: Status field

Data type: SAESTATUS
Optional: No
Call by Reference: Yes

COUNT -

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

TABLES Parameters details for ARCHIV_CONNECTINFO_GET_META

CONNECT_INFO - archiv_id and archiv_doc_id

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

EXCEPTIONS details

ERROR_CONNECTIONTABLE -

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

Copy and paste ABAP code example for ARCHIV_CONNECTINFO_GET_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.

ABAP code using 7.40 inline data declarations to call FM ARCHIV_CONNECTINFO_GET_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.

Search for further information about these or an SAP related objects