SAP DOCU_HTML_GET Function Module for
DOCU_HTML_GET is a standard docu html get 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 docu html get FM, simply by entering the name DOCU_HTML_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: SEF1
Program Name: SAPLSEF1
Main Program: SAPLSEF1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DOCU_HTML_GET 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 'DOCU_HTML_GET'".
EXPORTING
IV_ID = "Document Class
IV_OBJECT = "Documentation Object
IV_LANGUAGE = "SAP R/3 System, Current Language
IV_MSGV1 = "Messages, Message Variable
IV_MSGV2 = "Messages, Message Variable
IV_MSGV3 = "Messages, Message Variable
IV_MSGV4 = "Messages, Message Variable
IV_LINKS = "Single-Character Flag
IMPORTING
EV_HTML_TABLE = "Table with HTMLLINE
EV_HTML_LINKS = "Positions of Hyperlinks in HTML Table
EXCEPTIONS
DOCUMENT_NOT_FOUND = 1
IMPORTING Parameters details for DOCU_HTML_GET
IV_ID - Document Class
Data type: DOKU_IDOptional: No
Call by Reference: No ( called with pass by value option)
IV_OBJECT - Documentation Object
Data type: DOKU_OBJOptional: No
Call by Reference: No ( called with pass by value option)
IV_LANGUAGE - SAP R/3 System, Current Language
Data type: SYLANGUOptional: No
Call by Reference: No ( called with pass by value option)
IV_MSGV1 - Messages, Message Variable
Data type: SYMSGVOptional: No
Call by Reference: No ( called with pass by value option)
IV_MSGV2 - Messages, Message Variable
Data type: SYMSGVOptional: No
Call by Reference: No ( called with pass by value option)
IV_MSGV3 - Messages, Message Variable
Data type: SYMSGVOptional: No
Call by Reference: No ( called with pass by value option)
IV_MSGV4 - Messages, Message Variable
Data type: SYMSGVOptional: No
Call by Reference: No ( called with pass by value option)
IV_LINKS - Single-Character Flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DOCU_HTML_GET
EV_HTML_TABLE - Table with HTMLLINE
Data type: HTMLTABLEOptional: No
Call by Reference: No ( called with pass by value option)
EV_HTML_LINKS - Positions of Hyperlinks in HTML Table
Data type: DOKUT_LINKPOSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DOCUMENT_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DOCU_HTML_GET 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_iv_id | TYPE DOKU_ID, " | |||
| lv_ev_html_table | TYPE HTMLTABLE, " | |||
| lv_document_not_found | TYPE HTMLTABLE, " | |||
| lv_iv_object | TYPE DOKU_OBJ, " | |||
| lv_ev_html_links | TYPE DOKUT_LINKPOS, " | |||
| lv_iv_language | TYPE SYLANGU, " | |||
| lv_iv_msgv1 | TYPE SYMSGV, " | |||
| lv_iv_msgv2 | TYPE SYMSGV, " | |||
| lv_iv_msgv3 | TYPE SYMSGV, " | |||
| lv_iv_msgv4 | TYPE SYMSGV, " | |||
| lv_iv_links | TYPE CHAR1. " |
|   CALL FUNCTION 'DOCU_HTML_GET' " |
| EXPORTING | ||
| IV_ID | = lv_iv_id | |
| IV_OBJECT | = lv_iv_object | |
| IV_LANGUAGE | = lv_iv_language | |
| IV_MSGV1 | = lv_iv_msgv1 | |
| IV_MSGV2 | = lv_iv_msgv2 | |
| IV_MSGV3 | = lv_iv_msgv3 | |
| IV_MSGV4 | = lv_iv_msgv4 | |
| IV_LINKS | = lv_iv_links | |
| IMPORTING | ||
| EV_HTML_TABLE | = lv_ev_html_table | |
| EV_HTML_LINKS | = lv_ev_html_links | |
| EXCEPTIONS | ||
| DOCUMENT_NOT_FOUND = 1 | ||
| . " DOCU_HTML_GET | ||
ABAP code using 7.40 inline data declarations to call FM DOCU_HTML_GET
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