SAP ICLX_BO_NODE_RETRIEVE_APP Function Module for Calls Retrieve Method for a BO Node
ICLX_BO_NODE_RETRIEVE_APP is a standard iclx bo node retrieve app SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calls Retrieve Method for a BO 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 iclx bo node retrieve app FM, simply by entering the name ICLX_BO_NODE_RETRIEVE_APP into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICLX_TOOLS_APP
Program Name: SAPLICLX_TOOLS_APP
Main Program: SAPLICLX_TOOLS_APP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICLX_BO_NODE_RETRIEVE_APP 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 'ICLX_BO_NODE_RETRIEVE_APP'"Calls Retrieve Method for a BO Node.
EXPORTING
IV_BO_NODE_TYPE = "Business Object Node Type
IV_BO_GUID = "Business Object GUID
* IV_LANGUAGE = SY-LANGU "Language Key
* IV_FILL_FIELD_DESCR = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
* IS_GUID = "
* IS_ASSIGNMENT = "
* IT_GUID = "
* IT_ASSIGNMENT = "Assignment Table of BO Node Instances (Category, GUID)
* IS_VALIDITY = "Claims Facade: Period for History Entries
IMPORTING
EV_SUBRC = "Return Value from ABAP Statements
EV_EXCEPTION = "Exception
ES_DATA = "
ET_DATA = "
ET_RETURN = "Table for Error Structure BAPIRET2
IMPORTING Parameters details for ICLX_BO_NODE_RETRIEVE_APP
IV_BO_NODE_TYPE - Business Object Node Type
Data type: ICLX_BO_NODE_TYPE_DOptional: No
Call by Reference: Yes
IV_BO_GUID - Business Object GUID
Data type: ICLX_BO_GUID_DOptional: No
Call by Reference: Yes
IV_LANGUAGE - Language Key
Data type: SPRASDefault: SY-LANGU
Optional: Yes
Call by Reference: Yes
IV_FILL_FIELD_DESCR - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: Yes
Call by Reference: Yes
IS_GUID -
Data type: ANYOptional: Yes
Call by Reference: Yes
IS_ASSIGNMENT -
Data type: ANYOptional: Yes
Call by Reference: Yes
IT_GUID -
Data type: STANDARD TABLEOptional: Yes
Call by Reference: Yes
IT_ASSIGNMENT - Assignment Table of BO Node Instances (Category, GUID)
Data type: ICLX_NODE_ASSIGNMENT_TOptional: Yes
Call by Reference: Yes
IS_VALIDITY - Claims Facade: Period for History Entries
Data type: ICLX_VALIDITY_SOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ICLX_BO_NODE_RETRIEVE_APP
EV_SUBRC - Return Value from ABAP Statements
Data type: SYSUBRCOptional: No
Call by Reference: Yes
EV_EXCEPTION - Exception
Data type: ICLX_EXCEPTION_DOptional: No
Call by Reference: Yes
ES_DATA -
Data type: ANYOptional: No
Call by Reference: Yes
ET_DATA -
Data type: STANDARD TABLEOptional: No
Call by Reference: Yes
ET_RETURN - Table for Error Structure BAPIRET2
Data type: ICL_BAPIRET2_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICLX_BO_NODE_RETRIEVE_APP 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_ev_subrc | TYPE SYSUBRC, " | |||
| lv_iv_bo_node_type | TYPE ICLX_BO_NODE_TYPE_D, " | |||
| lv_iv_bo_guid | TYPE ICLX_BO_GUID_D, " | |||
| lv_ev_exception | TYPE ICLX_EXCEPTION_D, " | |||
| lv_es_data | TYPE ANY, " | |||
| lv_iv_language | TYPE SPRAS, " SY-LANGU | |||
| lv_et_data | TYPE STANDARD TABLE, " | |||
| lv_iv_fill_field_descr | TYPE BOOLE_D, " | |||
| lv_is_guid | TYPE ANY, " | |||
| lv_et_return | TYPE ICL_BAPIRET2_TAB, " | |||
| lv_is_assignment | TYPE ANY, " | |||
| lv_it_guid | TYPE STANDARD TABLE, " | |||
| lv_it_assignment | TYPE ICLX_NODE_ASSIGNMENT_T, " | |||
| lv_is_validity | TYPE ICLX_VALIDITY_S. " |
|   CALL FUNCTION 'ICLX_BO_NODE_RETRIEVE_APP' "Calls Retrieve Method for a BO Node |
| EXPORTING | ||
| IV_BO_NODE_TYPE | = lv_iv_bo_node_type | |
| IV_BO_GUID | = lv_iv_bo_guid | |
| IV_LANGUAGE | = lv_iv_language | |
| IV_FILL_FIELD_DESCR | = lv_iv_fill_field_descr | |
| IS_GUID | = lv_is_guid | |
| IS_ASSIGNMENT | = lv_is_assignment | |
| IT_GUID | = lv_it_guid | |
| IT_ASSIGNMENT | = lv_it_assignment | |
| IS_VALIDITY | = lv_is_validity | |
| IMPORTING | ||
| EV_SUBRC | = lv_ev_subrc | |
| EV_EXCEPTION | = lv_ev_exception | |
| ES_DATA | = lv_es_data | |
| ET_DATA | = lv_et_data | |
| ET_RETURN | = lv_et_return | |
| . " ICLX_BO_NODE_RETRIEVE_APP | ||
ABAP code using 7.40 inline data declarations to call FM ICLX_BO_NODE_RETRIEVE_APP
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_iv_language) | = SY-LANGU. | |||
Search for further information about these or an SAP related objects