SAP OM_OBJECT_MANAGER_CALL_FUNC Function Module for
OM_OBJECT_MANAGER_CALL_FUNC is a standard om object manager call func 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 object manager call func FM, simply by entering the name OM_OBJECT_MANAGER_CALL_FUNC into the relevant SAP transaction such as SE37 or SE38.
Function Group: OM_OBJECTMANAGER
Program Name: SAPLOM_OBJECTMANAGER
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OM_OBJECT_MANAGER_CALL_FUNC 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_OBJECT_MANAGER_CALL_FUNC'".
EXPORTING
CALL_FUNCTION = "
* RELAT_OBJECT = "
* FCODE = "
* CONTEXT_MENU_HANDLE = "
* PLVAR = "
OTYPE = "
* DATE = "
* FUZZY_BEGDA = "
* FUZZY_ENDDA = "
* GRID_HANDLE = "
* COLNAME = "
* MAIN_OBJECT = "
IMPORTING
DYNNR = "
REPID = "
TABLES
SEARCH_TOOL = "
SEARCH_TOOL_INT = "
* RESULT_TAB = "
* COLUMN_HEADERS = "
* SEARCH_DATA = "
* COLOTYPES = "
* CELL_BEHAVIOUR = "
* OBJECTMANAGER_EVENT = "
IMPORTING Parameters details for OM_OBJECT_MANAGER_CALL_FUNC
CALL_FUNCTION -
Data type: CHAR40Optional: No
Call by Reference: Yes
RELAT_OBJECT -
Data type: OBJECOptional: Yes
Call by Reference: Yes
FCODE -
Data type: SY-UCOMMOptional: Yes
Call by Reference: Yes
CONTEXT_MENU_HANDLE -
Data type: CL_CTMENUOptional: Yes
Call by Reference: Yes
PLVAR -
Data type: OBJEC-PLVAROptional: Yes
Call by Reference: No ( called with pass by value option)
OTYPE -
Data type: OTYPEOptional: No
Call by Reference: Yes
DATE -
Data type: OBJEC-BEGDAOptional: Yes
Call by Reference: Yes
FUZZY_BEGDA -
Data type: OBJEC-BEGDAOptional: Yes
Call by Reference: Yes
FUZZY_ENDDA -
Data type: OBJEC-ENDDAOptional: Yes
Call by Reference: Yes
GRID_HANDLE -
Data type: CL_GUI_ALV_GRIDOptional: Yes
Call by Reference: Yes
COLNAME -
Data type: TV_ITMNAMEOptional: Yes
Call by Reference: Yes
MAIN_OBJECT -
Data type: TREE_OBJECOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for OM_OBJECT_MANAGER_CALL_FUNC
DYNNR -
Data type: SY-DYNNROptional: No
Call by Reference: Yes
REPID -
Data type: SY-REPIDOptional: No
Call by Reference: Yes
TABLES Parameters details for OM_OBJECT_MANAGER_CALL_FUNC
SEARCH_TOOL -
Data type: OMSEARCHTOOptional: No
Call by Reference: No ( called with pass by value option)
SEARCH_TOOL_INT -
Data type: OMSEARCHTIOptional: No
Call by Reference: No ( called with pass by value option)
RESULT_TAB -
Data type: TREE_OBJECOptional: Yes
Call by Reference: No ( called with pass by value option)
COLUMN_HEADERS -
Data type: OMCOLHEADOptional: Yes
Call by Reference: No ( called with pass by value option)
SEARCH_DATA -
Data type: OMSEAATTOptional: Yes
Call by Reference: No ( called with pass by value option)
COLOTYPES -
Data type: T77COLOTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
CELL_BEHAVIOUR -
Data type: OMDDMAT_TOptional: Yes
Call by Reference: No ( called with pass by value option)
OBJECTMANAGER_EVENT -
Data type: OMOMAEVENTOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OM_OBJECT_MANAGER_CALL_FUNC 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_dynnr | TYPE SY-DYNNR, " | |||
| lt_search_tool | TYPE STANDARD TABLE OF OMSEARCHTO, " | |||
| lv_call_function | TYPE CHAR40, " | |||
| lv_relat_object | TYPE OBJEC, " | |||
| lv_fcode | TYPE SY-UCOMM, " | |||
| lv_context_menu_handle | TYPE CL_CTMENU, " | |||
| lv_plvar | TYPE OBJEC-PLVAR, " | |||
| lv_repid | TYPE SY-REPID, " | |||
| lt_search_tool_int | TYPE STANDARD TABLE OF OMSEARCHTI, " | |||
| lv_otype | TYPE OTYPE, " | |||
| lt_result_tab | TYPE STANDARD TABLE OF TREE_OBJEC, " | |||
| lv_date | TYPE OBJEC-BEGDA, " | |||
| lt_column_headers | TYPE STANDARD TABLE OF OMCOLHEAD, " | |||
| lv_fuzzy_begda | TYPE OBJEC-BEGDA, " | |||
| lt_search_data | TYPE STANDARD TABLE OF OMSEAATT, " | |||
| lt_colotypes | TYPE STANDARD TABLE OF T77COLOTYP, " | |||
| lv_fuzzy_endda | TYPE OBJEC-ENDDA, " | |||
| lv_grid_handle | TYPE CL_GUI_ALV_GRID, " | |||
| lt_cell_behaviour | TYPE STANDARD TABLE OF OMDDMAT_T, " | |||
| lv_colname | TYPE TV_ITMNAME, " | |||
| lt_objectmanager_event | TYPE STANDARD TABLE OF OMOMAEVENT, " | |||
| lv_main_object | TYPE TREE_OBJEC. " |
|   CALL FUNCTION 'OM_OBJECT_MANAGER_CALL_FUNC' " |
| EXPORTING | ||
| CALL_FUNCTION | = lv_call_function | |
| RELAT_OBJECT | = lv_relat_object | |
| FCODE | = lv_fcode | |
| CONTEXT_MENU_HANDLE | = lv_context_menu_handle | |
| PLVAR | = lv_plvar | |
| OTYPE | = lv_otype | |
| DATE | = lv_date | |
| FUZZY_BEGDA | = lv_fuzzy_begda | |
| FUZZY_ENDDA | = lv_fuzzy_endda | |
| GRID_HANDLE | = lv_grid_handle | |
| COLNAME | = lv_colname | |
| MAIN_OBJECT | = lv_main_object | |
| IMPORTING | ||
| DYNNR | = lv_dynnr | |
| REPID | = lv_repid | |
| TABLES | ||
| SEARCH_TOOL | = lt_search_tool | |
| SEARCH_TOOL_INT | = lt_search_tool_int | |
| RESULT_TAB | = lt_result_tab | |
| COLUMN_HEADERS | = lt_column_headers | |
| SEARCH_DATA | = lt_search_data | |
| COLOTYPES | = lt_colotypes | |
| CELL_BEHAVIOUR | = lt_cell_behaviour | |
| OBJECTMANAGER_EVENT | = lt_objectmanager_event | |
| . " OM_OBJECT_MANAGER_CALL_FUNC | ||
ABAP code using 7.40 inline data declarations to call FM OM_OBJECT_MANAGER_CALL_FUNC
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 DYNNR FROM SY INTO @DATA(ld_dynnr). | ||||
| "SELECT single UCOMM FROM SY INTO @DATA(ld_fcode). | ||||
| "SELECT single PLVAR FROM OBJEC INTO @DATA(ld_plvar). | ||||
| "SELECT single REPID FROM SY INTO @DATA(ld_repid). | ||||
| "SELECT single BEGDA FROM OBJEC INTO @DATA(ld_date). | ||||
| "SELECT single BEGDA FROM OBJEC INTO @DATA(ld_fuzzy_begda). | ||||
| "SELECT single ENDDA FROM OBJEC INTO @DATA(ld_fuzzy_endda). | ||||
Search for further information about these or an SAP related objects