SAP HTTP_CHECK_ICFATTRIB Function Module for









HTTP_CHECK_ICFATTRIB is a standard http check icfattrib 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 check icfattrib FM, simply by entering the name HTTP_CHECK_ICFATTRIB 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_CHECK_ICFATTRIB 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_CHECK_ICFATTRIB'"
EXPORTING
PATH = "
* CLIENT_USER_DEPENT = ' ' "
* USER = "SAP System, User Logon Name
ATTRIB = "Single-Character Flag
* RECORDING = "

IMPORTING
ENTRY_EXISTS = "

CHANGING
* ERR_ICFATTRIB = "ICF: Table Type for ICFATTRIB
.



IMPORTING Parameters details for HTTP_CHECK_ICFATTRIB

PATH -

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

CLIENT_USER_DEPENT -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

USER - SAP System, User Logon Name

Data type: SY-UNAME
Optional: Yes
Call by Reference: Yes

ATTRIB - Single-Character Flag

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

RECORDING -

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

EXPORTING Parameters details for HTTP_CHECK_ICFATTRIB

ENTRY_EXISTS -

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

CHANGING Parameters details for HTTP_CHECK_ICFATTRIB

ERR_ICFATTRIB - ICF: Table Type for ICFATTRIB

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

Copy and paste ABAP code example for HTTP_CHECK_ICFATTRIB 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_path  TYPE STRING, "   
lv_entry_exists  TYPE C, "   
lv_err_icfattrib  TYPE TTYP_ICFATTRIB, "   
lv_client_user_depent  TYPE C, "   ' '
lv_user  TYPE SY-UNAME, "   
lv_attrib  TYPE CHAR1, "   
lv_recording  TYPE CHAR1. "   

  CALL FUNCTION 'HTTP_CHECK_ICFATTRIB'  "
    EXPORTING
         PATH = lv_path
         CLIENT_USER_DEPENT = lv_client_user_depent
         USER = lv_user
         ATTRIB = lv_attrib
         RECORDING = lv_recording
    IMPORTING
         ENTRY_EXISTS = lv_entry_exists
    CHANGING
         ERR_ICFATTRIB = lv_err_icfattrib
. " HTTP_CHECK_ICFATTRIB




ABAP code using 7.40 inline data declarations to call FM HTTP_CHECK_ICFATTRIB

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.

 
 
 
DATA(ld_client_user_depent) = ' '.
 
"SELECT single UNAME FROM SY INTO @DATA(ld_user).
 
 
 


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!