SAP MSG_STATUS Function Module for









MSG_STATUS is a standard msg status 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 status FM, simply by entering the name MSG_STATUS 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_STATUS 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_STATUS'"
IMPORTING
Y_ACTIVE = "
Y_APPL_LOG = "
Y_MSG_HANDLE = "Message Identification
Y_LOG_OFF_COUNT = "
.



EXPORTING Parameters details for MSG_STATUS

Y_ACTIVE -

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

Y_APPL_LOG -

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

Y_MSG_HANDLE - Message Identification

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

Y_LOG_OFF_COUNT -

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

Copy and paste ABAP code example for MSG_STATUS 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_y_active  TYPE EMSG_GEN-KZ_ACTIVE, "   
lv_y_appl_log  TYPE BALHDR-OBJECT, "   
lv_y_msg_handle  TYPE EMSG_GEN-HANDLE, "   
lv_y_log_off_count  TYPE EMSG_LOG_OFF_COUNT. "   

  CALL FUNCTION 'MSG_STATUS'  "
    IMPORTING
         Y_ACTIVE = lv_y_active
         Y_APPL_LOG = lv_y_appl_log
         Y_MSG_HANDLE = lv_y_msg_handle
         Y_LOG_OFF_COUNT = lv_y_log_off_count
. " MSG_STATUS




ABAP code using 7.40 inline data declarations to call FM MSG_STATUS

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 KZ_ACTIVE FROM EMSG_GEN INTO @DATA(ld_y_active).
 
"SELECT single OBJECT FROM BALHDR INTO @DATA(ld_y_appl_log).
 
"SELECT single HANDLE FROM EMSG_GEN INTO @DATA(ld_y_msg_handle).
 
 


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!