SAP CJGG_GET_EXPANDED_NODES Function Module for NOTRANSL: liefert aufgeklappte Knoten
CJGG_GET_EXPANDED_NODES is a standard cjgg get expanded 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 NOTRANSL: liefert aufgeklappte Knoten 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 cjgg get expanded nodes FM, simply by entering the name CJGG_GET_EXPANDED_NODES into the relevant SAP transaction such as SE37 or SE38.
Function Group: CJGG
Program Name: SAPLCJGG
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CJGG_GET_EXPANDED_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 'CJGG_GET_EXPANDED_NODES'"NOTRANSL: liefert aufgeklappte Knoten.
EXPORTING
* TYPE_IMP = '3' "Generic Type
TABLES
NODE_EXP = "Tree Control: Table with Node Keys
IMPORTING Parameters details for CJGG_GET_EXPANDED_NODES
TYPE_IMP - Generic Type
Data type: CDefault: '3'
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for CJGG_GET_EXPANDED_NODES
NODE_EXP - Tree Control: Table with Node Keys
Data type: TREEV_NKSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CJGG_GET_EXPANDED_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_node_exp | TYPE STANDARD TABLE OF TREEV_NKS, " | |||
| lv_type_imp | TYPE C. " '3' |
|   CALL FUNCTION 'CJGG_GET_EXPANDED_NODES' "NOTRANSL: liefert aufgeklappte Knoten |
| EXPORTING | ||
| TYPE_IMP | = lv_type_imp | |
| TABLES | ||
| NODE_EXP | = lt_node_exp | |
| . " CJGG_GET_EXPANDED_NODES | ||
ABAP code using 7.40 inline data declarations to call FM CJGG_GET_EXPANDED_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_type_imp) | = '3'. | |||
Search for further information about these or an SAP related objects