SAP BBP_OM_DIALOG_V_INIT_NF Function Module for
BBP_OM_DIALOG_V_INIT_NF is a standard bbp om dialog v init nf 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 bbp om dialog v init nf FM, simply by entering the name BBP_OM_DIALOG_V_INIT_NF into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_OM_DIALOG_V
Program Name: SAPLBBP_OM_DIALOG_V
Main Program: SAPLBBP_OM_DIALOG_V
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_OM_DIALOG_V_INIT_NF 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 'BBP_OM_DIALOG_V_INIT_NF'".
EXPORTING
SCENARIO = "
PLANVERSION = "
TRANSACTION_START = "
CHANGEMODE = "
TIMEDEPENDENT = "
USER_SETTINGS_EXIST = "
IMPORTING
DATA_VALID = "
SREQUEST = "
SMAIN_OBJECT = "
SRELAT_OBJECT = "
SDETAIL_TABTYPE = "
SADDITIONAL_DATA = "
SOVERVIEW_ADD_DATA = "
SDETAIL_ADD_DATA = "
ADD_TO_NAVIGATION_STACK = "
FREQUEST = "
FMAIN_OBJECT = "
FRELAT_OBJECT = "
FDETAIL_TABTYPE = "
FADDITIONAL_DATA = "
FOVERVIEW_ADD_DATA = "
FDETAIL_ADD_DATA = "
IMPORTING Parameters details for BBP_OM_DIALOG_V_INIT_NF
SCENARIO -
Data type: HROMSCENOptional: No
Call by Reference: Yes
PLANVERSION -
Data type: PLVAROptional: No
Call by Reference: Yes
TRANSACTION_START -
Data type: FLAGOptional: No
Call by Reference: Yes
CHANGEMODE -
Data type: OMACTMODEOptional: No
Call by Reference: Yes
TIMEDEPENDENT -
Data type: HROMTIMEFLOptional: No
Call by Reference: Yes
USER_SETTINGS_EXIST -
Data type: FLAGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for BBP_OM_DIALOG_V_INIT_NF
DATA_VALID -
Data type: FLAGOptional: No
Call by Reference: Yes
SREQUEST -
Data type: OMREQUESTOptional: No
Call by Reference: Yes
SMAIN_OBJECT -
Data type: OBJECOptional: No
Call by Reference: Yes
SRELAT_OBJECT -
Data type: OBJECOptional: No
Call by Reference: Yes
SDETAIL_TABTYPE -
Data type: HRTABTYPEOptional: No
Call by Reference: Yes
SADDITIONAL_DATA -
Data type: OMADDDATAOptional: No
Call by Reference: Yes
SOVERVIEW_ADD_DATA -
Data type: OMADDDATAOptional: No
Call by Reference: Yes
SDETAIL_ADD_DATA -
Data type: OMADDDATAOptional: No
Call by Reference: Yes
ADD_TO_NAVIGATION_STACK -
Data type: FLAGOptional: No
Call by Reference: Yes
FREQUEST -
Data type: OMREQUESTOptional: No
Call by Reference: Yes
FMAIN_OBJECT -
Data type: OBJECOptional: No
Call by Reference: Yes
FRELAT_OBJECT -
Data type: OBJECOptional: No
Call by Reference: Yes
FDETAIL_TABTYPE -
Data type: HRTABTYPEOptional: No
Call by Reference: Yes
FADDITIONAL_DATA -
Data type: OMADDDATAOptional: No
Call by Reference: Yes
FOVERVIEW_ADD_DATA -
Data type: OMADDDATAOptional: No
Call by Reference: Yes
FDETAIL_ADD_DATA -
Data type: OMADDDATAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_OM_DIALOG_V_INIT_NF 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_scenario | TYPE HROMSCEN, " | |||
| lv_data_valid | TYPE FLAG, " | |||
| lv_srequest | TYPE OMREQUEST, " | |||
| lv_smain_object | TYPE OBJEC, " | |||
| lv_srelat_object | TYPE OBJEC, " | |||
| lv_sdetail_tabtype | TYPE HRTABTYPE, " | |||
| lv_sadditional_data | TYPE OMADDDATA, " | |||
| lv_soverview_add_data | TYPE OMADDDATA, " | |||
| lv_sdetail_add_data | TYPE OMADDDATA, " | |||
| lv_planversion | TYPE PLVAR, " | |||
| lv_add_to_navigation_stack | TYPE FLAG, " | |||
| lv_frequest | TYPE OMREQUEST, " | |||
| lv_transaction_start | TYPE FLAG, " | |||
| lv_changemode | TYPE OMACTMODE, " | |||
| lv_fmain_object | TYPE OBJEC, " | |||
| lv_frelat_object | TYPE OBJEC, " | |||
| lv_timedependent | TYPE HROMTIMEFL, " | |||
| lv_fdetail_tabtype | TYPE HRTABTYPE, " | |||
| lv_user_settings_exist | TYPE FLAG, " | |||
| lv_fadditional_data | TYPE OMADDDATA, " | |||
| lv_foverview_add_data | TYPE OMADDDATA, " | |||
| lv_fdetail_add_data | TYPE OMADDDATA. " |
|   CALL FUNCTION 'BBP_OM_DIALOG_V_INIT_NF' " |
| EXPORTING | ||
| SCENARIO | = lv_scenario | |
| PLANVERSION | = lv_planversion | |
| TRANSACTION_START | = lv_transaction_start | |
| CHANGEMODE | = lv_changemode | |
| TIMEDEPENDENT | = lv_timedependent | |
| USER_SETTINGS_EXIST | = lv_user_settings_exist | |
| IMPORTING | ||
| DATA_VALID | = lv_data_valid | |
| SREQUEST | = lv_srequest | |
| SMAIN_OBJECT | = lv_smain_object | |
| SRELAT_OBJECT | = lv_srelat_object | |
| SDETAIL_TABTYPE | = lv_sdetail_tabtype | |
| SADDITIONAL_DATA | = lv_sadditional_data | |
| SOVERVIEW_ADD_DATA | = lv_soverview_add_data | |
| SDETAIL_ADD_DATA | = lv_sdetail_add_data | |
| ADD_TO_NAVIGATION_STACK | = lv_add_to_navigation_stack | |
| FREQUEST | = lv_frequest | |
| FMAIN_OBJECT | = lv_fmain_object | |
| FRELAT_OBJECT | = lv_frelat_object | |
| FDETAIL_TABTYPE | = lv_fdetail_tabtype | |
| FADDITIONAL_DATA | = lv_fadditional_data | |
| FOVERVIEW_ADD_DATA | = lv_foverview_add_data | |
| FDETAIL_ADD_DATA | = lv_fdetail_add_data | |
| . " BBP_OM_DIALOG_V_INIT_NF | ||
ABAP code using 7.40 inline data declarations to call FM BBP_OM_DIALOG_V_INIT_NF
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.Search for further information about these or an SAP related objects