SAP MESSAGE_STORE Function Module for Store transferred message or output directly

Search SAP Function Modules

MESSAGE_STORE is a standard message store SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Store transferred message or output directly processing and below is the pattern details for this FM, 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 message store FM, simply by entering the name MESSAGE_STORE into the relevant SAP transaction such as SE37 or SE38.

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

Function MESSAGE_STORE 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 'MESSAGE_STORE'"Store transferred message or output directly
  EXPORTING
   ARBGB =  "Message ID
*  EXCEPTION_IF_NOT_ACTIVE = 'X' "X = exception not_active is initialized if
   MSGTY =  "Type of message (I, S, W, E, A)
*  MSGV1 = ' ' "First variable parameter of message
*  MSGV2 = ' ' "Second variable parameter of message
*  MSGV3 = ' ' "Third variable parameter of message
*  MSGV4 = ' ' "Fourth variable parameter of message
   TXTNR =  "Message Number
*  ZEILE = ' ' "Reference line (if it exists)

 IMPORTING
   ACT_SEVERITY =  "Level of current message
   MAX_SEVERITY =  "Maximum level of severity

EXCEPTIONS
   MESSAGE_TYPE_NOT_VALID = 1    NOT_ACTIVE = 2 

.

IMPORTING Parameters details for MESSAGE_STORE

ARBGB - Message ID

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

EXCEPTION_IF_NOT_ACTIVE - X = exception not_active is initialized if

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

MSGTY - Type of message (I, S, W, E, A)

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

MSGV1 - First variable parameter of message

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

MSGV2 - Second variable parameter of message

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

MSGV3 - Third variable parameter of message

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

MSGV4 - Fourth variable parameter of message

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

TXTNR - Message Number

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

ZEILE - Reference line (if it exists)

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

EXPORTING Parameters details for MESSAGE_STORE

ACT_SEVERITY - Level of current message

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

MAX_SEVERITY - Maximum level of severity

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

EXCEPTIONS details

MESSAGE_TYPE_NOT_VALID - Type of message not I, S, W, E or A

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

NOT_ACTIVE - Collection of messages not activated

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

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

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