SAP OM_OOT_FIND_NEXT Function Module for









OM_OOT_FIND_NEXT is a standard om oot find next 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 find next FM, simply by entering the name OM_OOT_FIND_NEXT into the relevant SAP transaction such as SE37 or SE38.

Function Group: OM_TREE
Program Name: SAPLOM_TREE
Main Program: SAPLOM_TREE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function OM_OOT_FIND_NEXT 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_FIND_NEXT'"
  EXPORTING
   HANDLE =  "Column Tree Control
*  NO_MESSAGE =  "General Flag
*  REPEAT_SEARCH = 'X' "General Flag

 IMPORTING
   NEXT_HIT =  "

EXCEPTIONS
   UNKNOWN_HANDLE = 1    NO_MESSAGE = 2
.



IMPORTING Parameters details for OM_OOT_FIND_NEXT

HANDLE - Column Tree Control

Data type: CL_GUI_COLUMN_TREE
Optional: No
Call by Reference: Yes

NO_MESSAGE - General Flag

Data type: FLAG
Optional: Yes
Call by Reference: Yes

REPEAT_SEARCH - General Flag

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for OM_OOT_FIND_NEXT

NEXT_HIT -

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

EXCEPTIONS details

UNKNOWN_HANDLE -

Data type:
Optional: No
Call by Reference: Yes

NO_MESSAGE - General Flag

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OM_OOT_FIND_NEXT 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_next_hit  TYPE TV_NODEKEY, "   
lv_unknown_handle  TYPE TV_NODEKEY, "   
lv_no_message  TYPE FLAG, "   
lv_no_message  TYPE FLAG, "   
lv_repeat_search  TYPE FLAG. "   'X'

  CALL FUNCTION 'OM_OOT_FIND_NEXT'  "
    EXPORTING
         HANDLE = lv_handle
         NO_MESSAGE = lv_no_message
         REPEAT_SEARCH = lv_repeat_search
    IMPORTING
         NEXT_HIT = lv_next_hit
    EXCEPTIONS
        UNKNOWN_HANDLE = 1
        NO_MESSAGE = 2
. " OM_OOT_FIND_NEXT




ABAP code using 7.40 inline data declarations to call FM OM_OOT_FIND_NEXT

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_repeat_search) = 'X'.
 


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!