SAP MSG_OPEN Function Module for
MSG_OPEN is a standard msg open 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 msg open FM, simply by entering the name MSG_OPEN into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMSG
Program Name: SAPLEMSG
Main Program: SAPLEMSG
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function MSG_OPEN 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 'MSG_OPEN'".
EXPORTING
* X_NO_DIALOG = ' ' "
* X_LOG = ' ' "
* X_NEXT_MSG = ' ' "
* X_OBJ_TWICE = ' ' "
IMPORTING
Y_MSG_HANDLE = "
CHANGING
* XY_PARM = "Additional parameters
EXCEPTIONS
FAILED = 1 SUBS_INVALID = 2 LOG_INVALID = 3
IMPORTING Parameters details for MSG_OPEN
X_NO_DIALOG -
Data type: EMSG_GEN-NO_DIALOGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_LOG -
Data type: EMSG_GEN-KZ_LOGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_NEXT_MSG -
Data type: EMSG_GEN-NEXT_MSGDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_OBJ_TWICE -
Data type: EMSG_GEN-OBJ_TWICEDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MSG_OPEN
Y_MSG_HANDLE -
Data type: EMSG_GEN-HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for MSG_OPEN
XY_PARM - Additional parameters
Data type: EEMSG_PARM_OPENOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBS_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LOG_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MSG_OPEN 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_failed | TYPE STRING, " | |||
lv_xy_parm | TYPE EEMSG_PARM_OPEN, " | |||
lv_x_no_dialog | TYPE EMSG_GEN-NO_DIALOG, " ' ' | |||
lv_y_msg_handle | TYPE EMSG_GEN-HANDLE, " | |||
lv_x_log | TYPE EMSG_GEN-KZ_LOG, " ' ' | |||
lv_subs_invalid | TYPE EMSG_GEN, " | |||
lv_x_next_msg | TYPE EMSG_GEN-NEXT_MSG, " ' ' | |||
lv_log_invalid | TYPE EMSG_GEN, " | |||
lv_x_obj_twice | TYPE EMSG_GEN-OBJ_TWICE. " ' ' |
  CALL FUNCTION 'MSG_OPEN' " |
EXPORTING | ||
X_NO_DIALOG | = lv_x_no_dialog | |
X_LOG | = lv_x_log | |
X_NEXT_MSG | = lv_x_next_msg | |
X_OBJ_TWICE | = lv_x_obj_twice | |
IMPORTING | ||
Y_MSG_HANDLE | = lv_y_msg_handle | |
CHANGING | ||
XY_PARM | = lv_xy_parm | |
EXCEPTIONS | ||
FAILED = 1 | ||
SUBS_INVALID = 2 | ||
LOG_INVALID = 3 | ||
. " MSG_OPEN |
ABAP code using 7.40 inline data declarations to call FM MSG_OPEN
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 NO_DIALOG FROM EMSG_GEN INTO @DATA(ld_x_no_dialog). | ||||
DATA(ld_x_no_dialog) | = ' '. | |||
"SELECT single HANDLE FROM EMSG_GEN INTO @DATA(ld_y_msg_handle). | ||||
"SELECT single KZ_LOG FROM EMSG_GEN INTO @DATA(ld_x_log). | ||||
DATA(ld_x_log) | = ' '. | |||
"SELECT single NEXT_MSG FROM EMSG_GEN INTO @DATA(ld_x_next_msg). | ||||
DATA(ld_x_next_msg) | = ' '. | |||
"SELECT single OBJ_TWICE FROM EMSG_GEN INTO @DATA(ld_x_obj_twice). | ||||
DATA(ld_x_obj_twice) | = ' '. | |||
Search for further information about these or an SAP related objects