SAP BM_MODOBJ_IN_DIA Function Module for









BM_MODOBJ_IN_DIA is a standard bm modobj in dia 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 bm modobj in dia FM, simply by entering the name BM_MODOBJ_IN_DIA into the relevant SAP transaction such as SE37 or SE38.

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



Function BM_MODOBJ_IN_DIA 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 'BM_MODOBJ_IN_DIA'"
EXPORTING
* MODEL_TYP = "Model type
* OBJ_DEF = "Object Definition
* ACTIVITY = "16 byte GUID

TABLES
* PROCDIAHEADERS = "Nodes
.



IMPORTING Parameters details for BM_MODOBJ_IN_DIA

MODEL_TYP - Model type

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

OBJ_DEF - Object Definition

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

ACTIVITY - 16 byte GUID

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

TABLES Parameters details for BM_MODOBJ_IN_DIA

PROCDIAHEADERS - Nodes

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

Copy and paste ABAP code example for BM_MODOBJ_IN_DIA 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_model_typ  TYPE DF41S-MODEL_TYP, "   
lt_procdiaheaders  TYPE STANDARD TABLE OF DF40_READ, "   
lv_obj_def  TYPE DF41S-OBJ_DEF, "   
lv_activity  TYPE DF41S-ACTIVITY. "   

  CALL FUNCTION 'BM_MODOBJ_IN_DIA'  "
    EXPORTING
         MODEL_TYP = lv_model_typ
         OBJ_DEF = lv_obj_def
         ACTIVITY = lv_activity
    TABLES
         PROCDIAHEADERS = lt_procdiaheaders
. " BM_MODOBJ_IN_DIA




ABAP code using 7.40 inline data declarations to call FM BM_MODOBJ_IN_DIA

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 MODEL_TYP FROM DF41S INTO @DATA(ld_model_typ).
 
 
"SELECT single OBJ_DEF FROM DF41S INTO @DATA(ld_obj_def).
 
"SELECT single ACTIVITY FROM DF41S INTO @DATA(ld_activity).
 


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!