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

Function HTTP_READ_DEBUG 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 'HTTP_READ_DEBUG'".
EXPORTING
CALLER_IP = "IP Address
* TERMINAL_ID = "
IMPORTING
ICFATTRIB_EXP = "Description of ICF Attributes (Trace/Debugging)
SUBRC = "
REMOTE_DEBUG_KEY = "
REMOTE_DEBUG_KEY_LEN = "
IS_TID_ATTACH = "
IMPORTING Parameters details for HTTP_READ_DEBUG
CALLER_IP - IP Address
Data type: RFCIPV6ADDROptional: No
Call by Reference: Yes
TERMINAL_ID -
Data type: SYSUUID_C32Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HTTP_READ_DEBUG
ICFATTRIB_EXP - Description of ICF Attributes (Trace/Debugging)
Data type: ICFATTRIBOptional: No
Call by Reference: Yes
SUBRC -
Data type: COptional: No
Call by Reference: Yes
REMOTE_DEBUG_KEY -
Data type: USER_KEYOptional: No
Call by Reference: Yes
REMOTE_DEBUG_KEY_LEN -
Data type: IOptional: No
Call by Reference: Yes
IS_TID_ATTACH -
Data type: SAP_BOOLOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HTTP_READ_DEBUG 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_caller_ip | TYPE RFCIPV6ADDR, " | |||
| lv_icfattrib_exp | TYPE ICFATTRIB, " | |||
| lv_subrc | TYPE C, " | |||
| lv_terminal_id | TYPE SYSUUID_C32, " | |||
| lv_remote_debug_key | TYPE USER_KEY, " | |||
| lv_remote_debug_key_len | TYPE I, " | |||
| lv_is_tid_attach | TYPE SAP_BOOL. " |
|   CALL FUNCTION 'HTTP_READ_DEBUG' " |
| EXPORTING | ||
| CALLER_IP | = lv_caller_ip | |
| TERMINAL_ID | = lv_terminal_id | |
| IMPORTING | ||
| ICFATTRIB_EXP | = lv_icfattrib_exp | |
| SUBRC | = lv_subrc | |
| REMOTE_DEBUG_KEY | = lv_remote_debug_key | |
| REMOTE_DEBUG_KEY_LEN | = lv_remote_debug_key_len | |
| IS_TID_ATTACH | = lv_is_tid_attach | |
| . " HTTP_READ_DEBUG | ||
ABAP code using 7.40 inline data declarations to call FM HTTP_READ_DEBUG
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