SAP MDIALOG_MOD_CHECK Function Module for









MDIALOG_MOD_CHECK is a standard mdialog mod check 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 mdialog mod check FM, simply by entering the name MDIALOG_MOD_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function MDIALOG_MOD_CHECK 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 'MDIALOG_MOD_CHECK'"
EXPORTING
I_OBJNAME = "
I_OBJTYPE = "

IMPORTING
E_MOD_DIALOG = "
E_INVALID_DIALOGS = "
E_MOD_RESULT = "

TABLES
* ERROR_DIALOGS = "Flags dialogs for IMPFLAG

EXCEPTIONS
DIALOG_NOT_EXISTING = 1 OBJECTNAME_MISSING = 2 OBJECTTYPE_ERROR = 3 OBJECT_NOT_EXISTING = 4 VIEWVARIANT_NOT_EXISTING = 5 VIEWCLUSTER_NOT_COMPLETE = 6 INTERNAL_ERROR = 7
.



IMPORTING Parameters details for MDIALOG_MOD_CHECK

I_OBJNAME -

Data type: OBJH-OBJECTNAME
Optional: No
Call by Reference: No ( called with pass by value option)

I_OBJTYPE -

Data type: OBJH-OBJECTTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MDIALOG_MOD_CHECK

E_MOD_DIALOG -

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

E_INVALID_DIALOGS -

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

E_MOD_RESULT -

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

TABLES Parameters details for MDIALOG_MOD_CHECK

ERROR_DIALOGS - Flags dialogs for IMPFLAG

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

EXCEPTIONS details

DIALOG_NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

OBJECTNAME_MISSING -

Data type:
Optional: No
Call by Reference: Yes

OBJECTTYPE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_EXISTING -

Data type:
Optional: No
Call by Reference: Yes

VIEWVARIANT_NOT_EXISTING - Layout Does not Exist

Data type:
Optional: No
Call by Reference: Yes

VIEWCLUSTER_NOT_COMPLETE -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MDIALOG_MOD_CHECK 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_i_objname  TYPE OBJH-OBJECTNAME, "   
lv_e_mod_dialog  TYPE OBJH, "   
lt_error_dialogs  TYPE STANDARD TABLE OF SV54I_UF, "   
lv_dialog_not_existing  TYPE SV54I_UF, "   
lv_i_objtype  TYPE OBJH-OBJECTTYPE, "   
lv_e_invalid_dialogs  TYPE CHAR1, "   
lv_objectname_missing  TYPE CHAR1, "   
lv_e_mod_result  TYPE SV54I_RES, "   
lv_objecttype_error  TYPE SV54I_RES, "   
lv_object_not_existing  TYPE SV54I_RES, "   
lv_viewvariant_not_existing  TYPE SV54I_RES, "   
lv_viewcluster_not_complete  TYPE SV54I_RES, "   
lv_internal_error  TYPE SV54I_RES. "   

  CALL FUNCTION 'MDIALOG_MOD_CHECK'  "
    EXPORTING
         I_OBJNAME = lv_i_objname
         I_OBJTYPE = lv_i_objtype
    IMPORTING
         E_MOD_DIALOG = lv_e_mod_dialog
         E_INVALID_DIALOGS = lv_e_invalid_dialogs
         E_MOD_RESULT = lv_e_mod_result
    TABLES
         ERROR_DIALOGS = lt_error_dialogs
    EXCEPTIONS
        DIALOG_NOT_EXISTING = 1
        OBJECTNAME_MISSING = 2
        OBJECTTYPE_ERROR = 3
        OBJECT_NOT_EXISTING = 4
        VIEWVARIANT_NOT_EXISTING = 5
        VIEWCLUSTER_NOT_COMPLETE = 6
        INTERNAL_ERROR = 7
. " MDIALOG_MOD_CHECK




ABAP code using 7.40 inline data declarations to call FM MDIALOG_MOD_CHECK

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 OBJECTNAME FROM OBJH INTO @DATA(ld_i_objname).
 
 
 
 
"SELECT single OBJECTTYPE FROM OBJH INTO @DATA(ld_i_objtype).
 
 
 
 
 
 
 
 
 


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!