SAP SRT_WSP_CHECK_ICF_NODES Function Module for Check whether SRT ICF notes are active
SRT_WSP_CHECK_ICF_NODES is a standard srt wsp check icf nodes SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check whether SRT ICF notes are active 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 srt wsp check icf nodes FM, simply by entering the name SRT_WSP_CHECK_ICF_NODES into the relevant SAP transaction such as SE37 or SE38.
Function Group: SRT_WSP_CONFIG_FW_INIT
Program Name: SAPLSRT_WSP_CONFIG_FW_INIT
Main Program: SAPLSRT_WSP_CONFIG_FW_INIT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SRT_WSP_CHECK_ICF_NODES 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 'SRT_WSP_CHECK_ICF_NODES'"Check whether SRT ICF notes are active.
EXPORTING
* SAP_CLIENT = "Client to be checked
* DEEP_INSPECTION = ABAP_FALSE "X=check ICF node settings on existence; space=otherwise
IMPORTING
ALL_NODES_ACTIVE = "X=all SRT ICF notes active; space=Only some or none active
TABLES
T_RETURN = "Return Parameter(s)
* T_XREF = "Cross reference for ICF node messages to BAPIRET2 table
IMPORTING Parameters details for SRT_WSP_CHECK_ICF_NODES
SAP_CLIENT - Client to be checked
Data type: MANDTOptional: Yes
Call by Reference: No ( called with pass by value option)
DEEP_INSPECTION - X=check ICF node settings on existence; space=otherwise
Data type: BOOLEANDefault: ABAP_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SRT_WSP_CHECK_ICF_NODES
ALL_NODES_ACTIVE - X=all SRT ICF notes active; space=Only some or none active
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for SRT_WSP_CHECK_ICF_NODES
T_RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: Yes
T_XREF - Cross reference for ICF node messages to BAPIRET2 table
Data type: SRT_WSP_ICF_XREF_CHECKOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for SRT_WSP_CHECK_ICF_NODES 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: | ||||
| lt_t_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_sap_client | TYPE MANDT, " | |||
| lv_all_nodes_active | TYPE BOOLEAN, " | |||
| lt_t_xref | TYPE STANDARD TABLE OF SRT_WSP_ICF_XREF_CHECK, " | |||
| lv_deep_inspection | TYPE BOOLEAN. " ABAP_FALSE |
|   CALL FUNCTION 'SRT_WSP_CHECK_ICF_NODES' "Check whether SRT ICF notes are active |
| EXPORTING | ||
| SAP_CLIENT | = lv_sap_client | |
| DEEP_INSPECTION | = lv_deep_inspection | |
| IMPORTING | ||
| ALL_NODES_ACTIVE | = lv_all_nodes_active | |
| TABLES | ||
| T_RETURN | = lt_t_return | |
| T_XREF | = lt_t_xref | |
| . " SRT_WSP_CHECK_ICF_NODES | ||
ABAP code using 7.40 inline data declarations to call FM SRT_WSP_CHECK_ICF_NODES
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_deep_inspection) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects