SAP OM_OOT_FILL_NODE_AND_ITEMS Function Module for









OM_OOT_FILL_NODE_AND_ITEMS is a standard om oot fill node and items 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 fill node and items FM, simply by entering the name OM_OOT_FILL_NODE_AND_ITEMS 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_FILL_NODE_AND_ITEMS 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_FILL_NODE_AND_ITEMS'"
EXPORTING
* ACT_TREE_OBJEC = "
* ACT_HROBJMSG = "
* ACT_TREE_STRUC = "
* ACT_MAX_DEPTH = "
* ACT_BEGDA = "
* ACT_ENDDA = "
* ACT_PATHID = "
* VIRTUAL_ROOT = "
* KEY_DATE = "

TABLES
TREE_COLUMN_TABLE = "
* USER_ROW_CONTENT = "
TREE_NODE_TABLE = "
TREE_ITEM_TABLE = "
.



IMPORTING Parameters details for OM_OOT_FILL_NODE_AND_ITEMS

ACT_TREE_OBJEC -

Data type: TREE_OBJEC
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACT_HROBJMSG -

Data type: HROBJMSG
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACT_TREE_STRUC -

Data type: TREE_STRUC
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACT_MAX_DEPTH -

Data type: GDSTR-TDEPTH
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACT_BEGDA -

Data type: OBJEC-BEGDA
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACT_ENDDA -

Data type: OBJEC-ENDDA
Optional: Yes
Call by Reference: No ( called with pass by value option)

ACT_PATHID -

Data type: GDSTR-WEGID
Optional: Yes
Call by Reference: No ( called with pass by value option)

VIRTUAL_ROOT -

Data type: OBJEC
Optional: Yes
Call by Reference: No ( called with pass by value option)

KEY_DATE -

Data type: OBJEC-BEGDA
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for OM_OOT_FILL_NODE_AND_ITEMS

TREE_COLUMN_TABLE -

Data type: TREEV_COL
Optional: No
Call by Reference: No ( called with pass by value option)

USER_ROW_CONTENT -

Data type: ORGCOLCON
Optional: Yes
Call by Reference: No ( called with pass by value option)

TREE_NODE_TABLE -

Data type: TREEV_NODE
Optional: No
Call by Reference: No ( called with pass by value option)

TREE_ITEM_TABLE -

Data type: MWBITEM
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for OM_OOT_FILL_NODE_AND_ITEMS 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_act_tree_objec  TYPE TREE_OBJEC, "   
lt_tree_column_table  TYPE STANDARD TABLE OF TREEV_COL, "   
lv_act_hrobjmsg  TYPE HROBJMSG, "   
lt_user_row_content  TYPE STANDARD TABLE OF ORGCOLCON, "   
lv_act_tree_struc  TYPE TREE_STRUC, "   
lt_tree_node_table  TYPE STANDARD TABLE OF TREEV_NODE, "   
lv_act_max_depth  TYPE GDSTR-TDEPTH, "   
lt_tree_item_table  TYPE STANDARD TABLE OF MWBITEM, "   
lv_act_begda  TYPE OBJEC-BEGDA, "   
lv_act_endda  TYPE OBJEC-ENDDA, "   
lv_act_pathid  TYPE GDSTR-WEGID, "   
lv_virtual_root  TYPE OBJEC, "   
lv_key_date  TYPE OBJEC-BEGDA. "   

  CALL FUNCTION 'OM_OOT_FILL_NODE_AND_ITEMS'  "
    EXPORTING
         ACT_TREE_OBJEC = lv_act_tree_objec
         ACT_HROBJMSG = lv_act_hrobjmsg
         ACT_TREE_STRUC = lv_act_tree_struc
         ACT_MAX_DEPTH = lv_act_max_depth
         ACT_BEGDA = lv_act_begda
         ACT_ENDDA = lv_act_endda
         ACT_PATHID = lv_act_pathid
         VIRTUAL_ROOT = lv_virtual_root
         KEY_DATE = lv_key_date
    TABLES
         TREE_COLUMN_TABLE = lt_tree_column_table
         USER_ROW_CONTENT = lt_user_row_content
         TREE_NODE_TABLE = lt_tree_node_table
         TREE_ITEM_TABLE = lt_tree_item_table
. " OM_OOT_FILL_NODE_AND_ITEMS




ABAP code using 7.40 inline data declarations to call FM OM_OOT_FILL_NODE_AND_ITEMS

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 TDEPTH FROM GDSTR INTO @DATA(ld_act_max_depth).
 
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_act_begda).
 
"SELECT single ENDDA FROM OBJEC INTO @DATA(ld_act_endda).
 
"SELECT single WEGID FROM GDSTR INTO @DATA(ld_act_pathid).
 
 
"SELECT single BEGDA FROM OBJEC INTO @DATA(ld_key_date).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!