SAP CNET_GET_NODES_ORDERED Function Module for Determine order of the hierarchy nodes
CNET_GET_NODES_ORDERED is a standard cnet get nodes ordered SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine order of the hierarchy nodes 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 cnet get nodes ordered FM, simply by entering the name CNET_GET_NODES_ORDERED into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNET
Program Name: SAPLCNET
Main Program:
Appliation area: S
Release date: 16-Apr-1997
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNET_GET_NODES_ORDERED 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 'CNET_GET_NODES_ORDERED'"Determine order of the hierarchy nodes.
EXPORTING
* STATUS_TEXT = ' ' "Text in status line
* WINID = ' ' "Window ID
TABLES
ALL_NODES = "Node table
EXCEPTIONS
INV_WINID = 1 NO_BATCH = 2 FRONTEND_ERROR = 3 INV_COMMUNICATION = 4
IMPORTING Parameters details for CNET_GET_NODES_ORDERED
STATUS_TEXT - Text in status line
Data type: NET_GRAPH-STATUSTEXTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WINID - Window ID
Data type: NET_GRAPH-WINIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CNET_GET_NODES_ORDERED
ALL_NODES - Node table
Data type: CHG_INODESOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INV_WINID - Incorrect window ID
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_BATCH -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FRONTEND_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INV_COMMUNICATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNET_GET_NODES_ORDERED 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_all_nodes | TYPE STANDARD TABLE OF CHG_INODES, " | |||
| lv_inv_winid | TYPE CHG_INODES, " | |||
| lv_status_text | TYPE NET_GRAPH-STATUSTEXT, " SPACE | |||
| lv_winid | TYPE NET_GRAPH-WINID, " SPACE | |||
| lv_no_batch | TYPE NET_GRAPH, " | |||
| lv_frontend_error | TYPE NET_GRAPH, " | |||
| lv_inv_communication | TYPE NET_GRAPH. " |
|   CALL FUNCTION 'CNET_GET_NODES_ORDERED' "Determine order of the hierarchy nodes |
| EXPORTING | ||
| STATUS_TEXT | = lv_status_text | |
| WINID | = lv_winid | |
| TABLES | ||
| ALL_NODES | = lt_all_nodes | |
| EXCEPTIONS | ||
| INV_WINID = 1 | ||
| NO_BATCH = 2 | ||
| FRONTEND_ERROR = 3 | ||
| INV_COMMUNICATION = 4 | ||
| . " CNET_GET_NODES_ORDERED | ||
ABAP code using 7.40 inline data declarations to call FM CNET_GET_NODES_ORDERED
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.| "SELECT single STATUSTEXT FROM NET_GRAPH INTO @DATA(ld_status_text). | ||||
| DATA(ld_status_text) | = ' '. | |||
| "SELECT single WINID FROM NET_GRAPH INTO @DATA(ld_winid). | ||||
| DATA(ld_winid) | = ' '. | |||
Search for further information about these or an SAP related objects