SAP ICL_NAVTREE_GET Function Module for Navigation Tree
ICL_NAVTREE_GET is a standard icl navtree get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Navigation Tree 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 icl navtree get FM, simply by entering the name ICL_NAVTREE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICL_NAVTREE
Program Name: SAPLICL_NAVTREE
Main Program: SAPLICL_NAVTREE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICL_NAVTREE_GET 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 'ICL_NAVTREE_GET'"Navigation Tree.
IMPORTING
ET_NAVTREE = "Navigation Tree
EV_TREETYPE = "Navigation Tree Type
TABLES
* ET_TREESTR = "Structure of Navigation Tree
EXPORTING Parameters details for ICL_NAVTREE_GET
ET_NAVTREE - Navigation Tree
Data type: ICL_NAVTREE_TOptional: No
Call by Reference: Yes
EV_TREETYPE - Navigation Tree Type
Data type: ICL_TREETYPEOptional: No
Call by Reference: Yes
TABLES Parameters details for ICL_NAVTREE_GET
ET_TREESTR - Structure of Navigation Tree
Data type: TICL069Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for ICL_NAVTREE_GET 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_et_navtree | TYPE ICL_NAVTREE_T, " | |||
| lt_et_treestr | TYPE STANDARD TABLE OF TICL069, " | |||
| lv_ev_treetype | TYPE ICL_TREETYPE. " |
|   CALL FUNCTION 'ICL_NAVTREE_GET' "Navigation Tree |
| IMPORTING | ||
| ET_NAVTREE | = lv_et_navtree | |
| EV_TREETYPE | = lv_ev_treetype | |
| TABLES | ||
| ET_TREESTR | = lt_et_treestr | |
| . " ICL_NAVTREE_GET | ||
ABAP code using 7.40 inline data declarations to call FM ICL_NAVTREE_GET
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