SAP ALINK_XML_GET_COMPONENT Function Module for

Search SAP Function Modules

ALINK_XML_GET_COMPONENT is a standard alink xml get component 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 alink xml get component FM, simply by entering the name ALINK_XML_GET_COMPONENT into the relevant SAP transaction such as SE37 or SE38.

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

Function ALINK_XML_GET_COMPONENT 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 'ALINK_XML_GET_COMPONENT'"
  EXPORTING
   OBJECT_TYPE =  "SAP ArchiveLink: Object type of business object
   OBJECT_ID =  "SAP ArchiveLink: Object ID (Object Identifier)
   DOCUMENT_TYPE =  "Document Type

 IMPORTING
   MAINTYPE =  "
   SUBTYPE =  "
   SIZE =  "
   ID =  "

TABLES
   BINARCHIVOBJECT =  "Buffer Table for Storing Table Data up to Length 1024

EXCEPTIONS
   ERROR_CONTENTREPOSITORY = 1    EMPTY = 2 

.

IMPORTING Parameters details for ALINK_XML_GET_COMPONENT

OBJECT_TYPE - SAP ArchiveLink: Object type of business object

Data type: TOAOM-SAP_OBJECT
Optional: No
Call by Reference: Yes

OBJECT_ID - SAP ArchiveLink: Object ID (Object Identifier)

Data type: SAPB-SAPOBJID
Optional: No
Call by Reference: Yes

DOCUMENT_TYPE - Document Type

Data type: TOAOM-AR_OBJECT
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ALINK_XML_GET_COMPONENT

MAINTYPE -

Data type:
Optional: No
Call by Reference: Yes

SUBTYPE -

Data type:
Optional: No
Call by Reference: Yes

SIZE -

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

ID -

Data type:
Optional: No
Call by Reference: Yes

TABLES Parameters details for ALINK_XML_GET_COMPONENT

BINARCHIVOBJECT - Buffer Table for Storing Table Data up to Length 1024

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

EXCEPTIONS details

ERROR_CONTENTREPOSITORY -

Data type:
Optional: No
Call by Reference: Yes

EMPTY -

Data type:
Optional: No
Call by Reference: Yes

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

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