SAP MSG_ACTION Function Module for

Search SAP Function Modules

MSG_ACTION is a standard msg action 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 action FM, simply by entering the name MSG_ACTION 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_ACTION 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_ACTION'"
  EXPORTING
*  X_MSG_HANDLE =  "
   X_ACTION =  "Function Code
*  X_MSG_BREAK =  "
*  X_LOG_OFF_IDENT =  "

 IMPORTING
   Y_LAST_MSG =  "
   YT_LOGNUMBERS =  "
   YT_MESSAGES =  "
   Y_TAB_MSGPLAIN =  "

CHANGING
*  XY_LOG_OFF_HANDLE =  "

EXCEPTIONS
   ACTION_NOT_SUPPORTED = 1    HANDLE_INVALID = 2    NOT_FOUND = 3 

.

IMPORTING Parameters details for MSG_ACTION

X_MSG_HANDLE -

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

X_ACTION - Function Code

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

X_MSG_BREAK -

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

X_LOG_OFF_IDENT -

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

EXPORTING Parameters details for MSG_ACTION

Y_LAST_MSG -

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

YT_LOGNUMBERS -

Data type: EEMSG_LOGNUMBER_TABLE
Optional: No
Call by Reference: Yes

YT_MESSAGES -

Data type: EEMSG_MSG_TABLE
Optional: No
Call by Reference: Yes

Y_TAB_MSGPLAIN -

Data type: EEMSG_MSG_SINGLE_TAB
Optional: No
Call by Reference: Yes

CHANGING Parameters details for MSG_ACTION

XY_LOG_OFF_HANDLE -

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

EXCEPTIONS details

ACTION_NOT_SUPPORTED - This function is not supported

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

HANDLE_INVALID -

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

NOT_FOUND -

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

Copy and paste ABAP code example for MSG_ACTION 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.

ABAP code using 7.40 inline data declarations to call FM MSG_ACTION

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