SAP OVERVIEW_OBJ_CREATE Function Module for
OVERVIEW_OBJ_CREATE is a standard overview obj create 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 overview obj create FM, simply by entering the name OVERVIEW_OBJ_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: OM_INTERFACE_TEMPLATES
Program Name: SAPLOM_INTERFACE_TEMPLATES
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OVERVIEW_OBJ_CREATE 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 'OVERVIEW_OBJ_CREATE'".
EXPORTING
SCENARIO = "View in Organizational Management
CHANGEMODE = "Organizational Management: Current mode
CLASS_KEY = "Key for Org. Management object
OVERVIEW_SERVICE = "OM: Interface Object Service
MAIN_OBJECT = "Work Area for Database PCH
RELAT_OBJECT = "
ADDITIONAL_DATA = "OM Framework: Additional Parameter for Request/Service
DATE = "
FUZZY_BEGDA = "
FUZZY_ENDDA = "
IMPORTING
DYNNR = "
REPID = "
EXCEPTIONS
OBJECT_ALREADY_EXISTS = 1
IMPORTING Parameters details for OVERVIEW_OBJ_CREATE
SCENARIO - View in Organizational Management
Data type: HROMSCENOptional: No
Call by Reference: No ( called with pass by value option)
CHANGEMODE - Organizational Management: Current mode
Data type: OMACTMODEOptional: No
Call by Reference: No ( called with pass by value option)
CLASS_KEY - Key for Org. Management object
Data type: OMCLASSKEYOptional: No
Call by Reference: No ( called with pass by value option)
OVERVIEW_SERVICE - OM: Interface Object Service
Data type: OMSERVICEOptional: No
Call by Reference: No ( called with pass by value option)
MAIN_OBJECT - Work Area for Database PCH
Data type: OBJECOptional: No
Call by Reference: No ( called with pass by value option)
RELAT_OBJECT -
Data type: OBJECOptional: No
Call by Reference: No ( called with pass by value option)
ADDITIONAL_DATA - OM Framework: Additional Parameter for Request/Service
Data type: OMADDDATAOptional: No
Call by Reference: No ( called with pass by value option)
DATE -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
FUZZY_BEGDA -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
FUZZY_ENDDA -
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for OVERVIEW_OBJ_CREATE
DYNNR -
Data type: SY-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
REPID -
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_ALREADY_EXISTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OVERVIEW_OBJ_CREATE 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, " | |||
| lv_scenario | TYPE HROMSCEN, " | |||
| lv_object_already_exists | TYPE HROMSCEN, " | |||
| lv_changemode | TYPE OMACTMODE, " | |||
| lv_repid | TYPE SY-REPID, " | |||
| lv_class_key | TYPE OMCLASSKEY, " | |||
| lv_overview_service | TYPE OMSERVICE, " | |||
| lv_main_object | TYPE OBJEC, " | |||
| lv_relat_object | TYPE OBJEC, " | |||
| lv_additional_data | TYPE OMADDDATA, " | |||
| lv_date | TYPE SY-DATUM, " | |||
| lv_fuzzy_begda | TYPE SY-DATUM, " | |||
| lv_fuzzy_endda | TYPE SY-DATUM. " |
|   CALL FUNCTION 'OVERVIEW_OBJ_CREATE' " |
| EXPORTING | ||
| SCENARIO | = lv_scenario | |
| CHANGEMODE | = lv_changemode | |
| CLASS_KEY | = lv_class_key | |
| OVERVIEW_SERVICE | = lv_overview_service | |
| MAIN_OBJECT | = lv_main_object | |
| RELAT_OBJECT | = lv_relat_object | |
| ADDITIONAL_DATA | = lv_additional_data | |
| DATE | = lv_date | |
| FUZZY_BEGDA | = lv_fuzzy_begda | |
| FUZZY_ENDDA | = lv_fuzzy_endda | |
| IMPORTING | ||
| DYNNR | = lv_dynnr | |
| REPID | = lv_repid | |
| EXCEPTIONS | ||
| OBJECT_ALREADY_EXISTS = 1 | ||
| . " OVERVIEW_OBJ_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM OVERVIEW_OBJ_CREATE
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 REPID FROM SY INTO @DATA(ld_repid). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_date). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_begda). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_endda). | ||||
Search for further information about these or an SAP related objects