SAP HTTP_DEBUG_UPDATE Function Module for









HTTP_DEBUG_UPDATE is a standard http debug update 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 debug update FM, simply by entering the name HTTP_DEBUG_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function HTTP_DEBUG_UPDATE 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_DEBUG_UPDATE'"
  EXPORTING
*  USER = SY-UNAME "SAP System, User Logon Name
*  JAVA_FUBA =  "
*  GUI_IPADDRESS_GEN =  "
*  GUI_RFCSI =  "
*  SYSTEM_BPS =  "
*  TERMINAL_ID =  "
*  IS_TID_ATTACH =  "
*  IS_USR_ATTACH =  "
*  GUI_IPADDRESS_FLAG = 'X' "
*  ACTION = 'X' "
*  SYSDEBUG = ' ' "
*  TIMEOUT = '020000' "
*  NO_MESSAGE = ' ' "
*  AUTHORITY_CHECK = 'X' "
*  USER_DEPEND =  "
*  GUI_IPADDRESS =  "IP Address

CHANGING
*  INT_ICFATTRIB =  "ICF: Table Type for ICFATTRIB

EXCEPTIONS
   INTERNAL_ERROR = 1
.



IMPORTING Parameters details for HTTP_DEBUG_UPDATE

USER - SAP System, User Logon Name

Data type: SY-UNAME
Default: SY-UNAME
Optional: No
Call by Reference: No ( called with pass by value option)

JAVA_FUBA -

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

GUI_IPADDRESS_GEN -

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

GUI_RFCSI -

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

SYSTEM_BPS -

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

TERMINAL_ID -

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

IS_TID_ATTACH -

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

IS_USR_ATTACH -

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

GUI_IPADDRESS_FLAG -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACTION -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

SYSDEBUG -

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

TIMEOUT -

Data type: SYUZEIT
Default: '020000'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_MESSAGE -

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

AUTHORITY_CHECK -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

USER_DEPEND -

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

GUI_IPADDRESS - IP Address

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

CHANGING Parameters details for HTTP_DEBUG_UPDATE

INT_ICFATTRIB - ICF: Table Type for ICFATTRIB

Data type: TTYP_ICFATTRIB
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HTTP_DEBUG_UPDATE 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_user  TYPE SY-UNAME, "   SY-UNAME
lv_int_icfattrib  TYPE TTYP_ICFATTRIB, "   
lv_internal_error  TYPE TTYP_ICFATTRIB, "   
lv_java_fuba  TYPE CHAR120, "   
lv_gui_ipaddress_gen  TYPE RFCIPV6ADDR, "   
lv_gui_rfcsi  TYPE RFCSI, "   
lv_system_bps  TYPE CHAR1, "   
lv_terminal_id  TYPE SYSUUID_C32, "   
lv_is_tid_attach  TYPE SAP_BOOL, "   
lv_is_usr_attach  TYPE SAP_BOOL, "   
lv_gui_ipaddress_flag  TYPE CHAR1, "   'X'
lv_action  TYPE CHAR1, "   'X'
lv_sysdebug  TYPE CHAR1, "   SPACE
lv_timeout  TYPE SYUZEIT, "   '020000'
lv_no_message  TYPE CHAR1, "   SPACE
lv_authority_check  TYPE CHAR1, "   'X'
lv_user_depend  TYPE CHAR1, "   
lv_gui_ipaddress  TYPE RFCIPADDR. "   

  CALL FUNCTION 'HTTP_DEBUG_UPDATE'  "
    EXPORTING
         USER = lv_user
         JAVA_FUBA = lv_java_fuba
         GUI_IPADDRESS_GEN = lv_gui_ipaddress_gen
         GUI_RFCSI = lv_gui_rfcsi
         SYSTEM_BPS = lv_system_bps
         TERMINAL_ID = lv_terminal_id
         IS_TID_ATTACH = lv_is_tid_attach
         IS_USR_ATTACH = lv_is_usr_attach
         GUI_IPADDRESS_FLAG = lv_gui_ipaddress_flag
         ACTION = lv_action
         SYSDEBUG = lv_sysdebug
         TIMEOUT = lv_timeout
         NO_MESSAGE = lv_no_message
         AUTHORITY_CHECK = lv_authority_check
         USER_DEPEND = lv_user_depend
         GUI_IPADDRESS = lv_gui_ipaddress
    CHANGING
         INT_ICFATTRIB = lv_int_icfattrib
    EXCEPTIONS
        INTERNAL_ERROR = 1
. " HTTP_DEBUG_UPDATE




ABAP code using 7.40 inline data declarations to call FM HTTP_DEBUG_UPDATE

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 UNAME FROM SY INTO @DATA(ld_user).
DATA(ld_user) = SY-UNAME.
 
 
 
 
 
 
 
 
 
 
DATA(ld_gui_ipaddress_flag) = 'X'.
 
DATA(ld_action) = 'X'.
 
DATA(ld_sysdebug) = ' '.
 
DATA(ld_timeout) = '020000'.
 
DATA(ld_no_message) = ' '.
 
DATA(ld_authority_check) = 'X'.
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!