SAP READ_ICF_NODE Function Module for Read ICF node
READ_ICF_NODE is a standard read icf node SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read ICF node processing and below is the pattern details for this FM, 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 read icf node FM, simply by entering the name READ_ICF_NODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UI5_CI_TEST
Program Name: SAPLUI5_CI_TEST
Main Program: SAPLUI5_CI_TEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function READ_ICF_NODE 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 'READ_ICF_NODE'"Read ICF node.
EXPORTING
IV_BSP_REPO = "Name of BSP application
IMPORTING
ES_RESULT = "Status of ICF node
EXCEPTIONS
NO_AUTHORIZATION = 1
IMPORTING Parameters details for READ_ICF_NODE
IV_BSP_REPO - Name of BSP application
Data type: O2APPLNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for READ_ICF_NODE
ES_RESULT - Status of ICF node
Data type: UI5_CI_S_ICF_STATUSOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORIZATION - No S_DEVELOP authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for READ_ICF_NODE 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_es_result | TYPE UI5_CI_S_ICF_STATUS, " | |||
| lv_iv_bsp_repo | TYPE O2APPLNAME, " | |||
| lv_no_authorization | TYPE O2APPLNAME. " |
|   CALL FUNCTION 'READ_ICF_NODE' "Read ICF node |
| EXPORTING | ||
| IV_BSP_REPO | = lv_iv_bsp_repo | |
| IMPORTING | ||
| ES_RESULT | = lv_es_result | |
| EXCEPTIONS | ||
| NO_AUTHORIZATION = 1 | ||
| . " READ_ICF_NODE | ||
ABAP code using 7.40 inline data declarations to call FM READ_ICF_NODE
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