SAP ALINK_DOCUMENTS_DISPLAY_OLEURL Function Module for
ALINK_DOCUMENTS_DISPLAY_OLEURL is a standard alink documents display oleurl 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 documents display oleurl FM, simply by entering the name ALINK_DOCUMENTS_DISPLAY_OLEURL into the relevant SAP transaction such as SE37 or SE38.
Function Group: OPTM
Program Name: SAPLOPTM
Main Program: SAPLOPTM
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ALINK_DOCUMENTS_DISPLAY_OLEURL 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_DOCUMENTS_DISPLAY_OLEURL'".
EXPORTING
* OBJECT_ID = ' ' "Business object ID
* DOCUMENT_CLASS = ' ' "Document Class
* ARCHIV_ID = ' ' "Storage System
* ARCHIV_DOC_ID = ' ' "Document ID
* WINDOW_ID = ' ' "Window ID
* WINDOW_TITLE = ' ' "Window title
EXCEPTIONS
ERROR_OLE = 1 NO_OLE_CUSTOMIZING = 2 ERROR_HTTP = 3
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLOPTM_001 SAP ArchiveLink: Customer Exit for the Function ARCHIVELINK_FUNCTION
IMPORTING Parameters details for ALINK_DOCUMENTS_DISPLAY_OLEURL
OBJECT_ID - Business object ID
Data type: TOAV0-OBJECT_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
DOCUMENT_CLASS - Document Class
Data type: TOADV-DOC_TYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ARCHIV_ID - Storage System
Data type: TOAAR-ARCHIV_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ARCHIV_DOC_ID - Document ID
Data type: TOAV0-ARC_DOC_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WINDOW_ID - Window ID
Data type: SAPB-SAPWINIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WINDOW_TITLE - Window title
Data type: SAPB-SAPWINTITLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_OLE - Error during OLE communication
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_OLE_CUSTOMIZING -
Data type:Optional: No
Call by Reference: Yes
ERROR_HTTP -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ALINK_DOCUMENTS_DISPLAY_OLEURL 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_ole | TYPE STRING, " | |||
lv_object_id | TYPE TOAV0-OBJECT_ID, " SPACE | |||
lv_document_class | TYPE TOADV-DOC_TYPE, " SPACE | |||
lv_no_ole_customizing | TYPE TOADV, " | |||
lv_archiv_id | TYPE TOAAR-ARCHIV_ID, " SPACE | |||
lv_error_http | TYPE TOAAR, " | |||
lv_archiv_doc_id | TYPE TOAV0-ARC_DOC_ID, " SPACE | |||
lv_window_id | TYPE SAPB-SAPWINID, " SPACE | |||
lv_window_title | TYPE SAPB-SAPWINTITL. " SPACE |
  CALL FUNCTION 'ALINK_DOCUMENTS_DISPLAY_OLEURL' " |
EXPORTING | ||
OBJECT_ID | = lv_object_id | |
DOCUMENT_CLASS | = lv_document_class | |
ARCHIV_ID | = lv_archiv_id | |
ARCHIV_DOC_ID | = lv_archiv_doc_id | |
WINDOW_ID | = lv_window_id | |
WINDOW_TITLE | = lv_window_title | |
EXCEPTIONS | ||
ERROR_OLE = 1 | ||
NO_OLE_CUSTOMIZING = 2 | ||
ERROR_HTTP = 3 | ||
. " ALINK_DOCUMENTS_DISPLAY_OLEURL |
ABAP code using 7.40 inline data declarations to call FM ALINK_DOCUMENTS_DISPLAY_OLEURL
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 OBJECT_ID FROM TOAV0 INTO @DATA(ld_object_id). | ||||
DATA(ld_object_id) | = ' '. | |||
"SELECT single DOC_TYPE FROM TOADV INTO @DATA(ld_document_class). | ||||
DATA(ld_document_class) | = ' '. | |||
"SELECT single ARCHIV_ID FROM TOAAR INTO @DATA(ld_archiv_id). | ||||
DATA(ld_archiv_id) | = ' '. | |||
"SELECT single ARC_DOC_ID FROM TOAV0 INTO @DATA(ld_archiv_doc_id). | ||||
DATA(ld_archiv_doc_id) | = ' '. | |||
"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) | = ' '. | |||
Search for further information about these or an SAP related objects