SAP OM_OOT_GET_NODE Function Module for
OM_OOT_GET_NODE is a standard om oot get node SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 om oot get node FM, simply by entering the name OM_OOT_GET_NODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OM_TREE
Program Name: SAPLOM_TREE
Main Program: SAPLOM_TREE
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OM_OOT_GET_NODE 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 'OM_OOT_GET_NODE'".
EXPORTING
HANDLE = "
* NODE_KEY = "
* ACT_OBJEC_IN = "Work Area for Database PCH
* ACT_STRUC_IN = "Structure Information for Database PCH
IMPORTING
ACT_NODE = "
ACT_OBJEC = "
ACT_TREE_OBJEC = "
ACT_STRUC = "
ACT_TREE_STRUC = "
EXCEPTIONS
UNKNOWN_HANDLE = 1 UNKNOWN_NODE_KEY = 2 NODE_NOT_FOUND = 3
IMPORTING Parameters details for OM_OOT_GET_NODE
HANDLE -
Data type: CL_GUI_COLUMN_TREEOptional: No
Call by Reference: No ( called with pass by value option)
NODE_KEY -
Data type: TREEV_NKEY-NODE_KEYOptional: Yes
Call by Reference: No ( called with pass by value option)
ACT_OBJEC_IN - Work Area for Database PCH
Data type: OBJECOptional: Yes
Call by Reference: No ( called with pass by value option)
ACT_STRUC_IN - Structure Information for Database PCH
Data type: STRUCOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OM_OOT_GET_NODE
ACT_NODE -
Data type: TREEV_NODEOptional: No
Call by Reference: No ( called with pass by value option)
ACT_OBJEC -
Data type: OBJECOptional: No
Call by Reference: No ( called with pass by value option)
ACT_TREE_OBJEC -
Data type: TREE_OBJECOptional: No
Call by Reference: No ( called with pass by value option)
ACT_STRUC -
Data type: STRUCOptional: No
Call by Reference: No ( called with pass by value option)
ACT_TREE_STRUC -
Data type: TREE_STRUCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNKNOWN_HANDLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNKNOWN_NODE_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NODE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OM_OOT_GET_NODE 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_handle | TYPE CL_GUI_COLUMN_TREE, " | |||
| lv_act_node | TYPE TREEV_NODE, " | |||
| lv_unknown_handle | TYPE TREEV_NODE, " | |||
| lv_node_key | TYPE TREEV_NKEY-NODE_KEY, " | |||
| lv_act_objec | TYPE OBJEC, " | |||
| lv_unknown_node_key | TYPE OBJEC, " | |||
| lv_act_objec_in | TYPE OBJEC, " | |||
| lv_act_tree_objec | TYPE TREE_OBJEC, " | |||
| lv_node_not_found | TYPE TREE_OBJEC, " | |||
| lv_act_struc | TYPE STRUC, " | |||
| lv_act_struc_in | TYPE STRUC, " | |||
| lv_act_tree_struc | TYPE TREE_STRUC. " |
|   CALL FUNCTION 'OM_OOT_GET_NODE' " |
| EXPORTING | ||
| HANDLE | = lv_handle | |
| NODE_KEY | = lv_node_key | |
| ACT_OBJEC_IN | = lv_act_objec_in | |
| ACT_STRUC_IN | = lv_act_struc_in | |
| IMPORTING | ||
| ACT_NODE | = lv_act_node | |
| ACT_OBJEC | = lv_act_objec | |
| ACT_TREE_OBJEC | = lv_act_tree_objec | |
| ACT_STRUC | = lv_act_struc | |
| ACT_TREE_STRUC | = lv_act_tree_struc | |
| EXCEPTIONS | ||
| UNKNOWN_HANDLE = 1 | ||
| UNKNOWN_NODE_KEY = 2 | ||
| NODE_NOT_FOUND = 3 | ||
| . " OM_OOT_GET_NODE | ||
ABAP code using 7.40 inline data declarations to call FM OM_OOT_GET_NODE
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 NODE_KEY FROM TREEV_NKEY INTO @DATA(ld_node_key). | ||||
Search for further information about these or an SAP related objects