SAP ITOB_MESSAGE_STORE Function Module for NOTRANSL: ITOB: Speichert Systemnachricht
ITOB_MESSAGE_STORE is a standard itob 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 NOTRANSL: ITOB: Speichert Systemnachricht 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 itob message store FM, simply by entering the name ITOB_MESSAGE_STORE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ITOBS
Program Name: SAPLITOBS
Main Program: SAPLITOBS
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ITOB_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 'ITOB_MESSAGE_STORE'"NOTRANSL: ITOB: Speichert Systemnachricht.
EXPORTING
* I_MSGID = SY-MSGID "ABAP System Field: Message ID
* I_MSGTY = SY-MSGTY "ABAP System Field: Message Type
* I_MSGNO = SY-MSGNO "ABAP System Field: Message Number
* I_MSGV1 = SY-MSGV1 "ABAP System Field: Message Variable
* I_MSGV2 = SY-MSGV2 "ABAP System Field: Message Variable
* I_MSGV3 = SY-MSGV3 "ABAP System Field: Message Variable
* I_MSGV4 = SY-MSGV4 "ABAP System Field: Message Variable
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLITOBS_001 Customer Exit Creating With Copy Mmodel: Change Copied Field Contents
IMPORTING Parameters details for ITOB_MESSAGE_STORE
I_MSGID - ABAP System Field: Message ID
Data type: SY-MSGIDDefault: SY-MSGID
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGTY - ABAP System Field: Message Type
Data type: SY-MSGTYDefault: SY-MSGTY
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGNO - ABAP System Field: Message Number
Data type: SY-MSGNODefault: SY-MSGNO
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV1 - ABAP System Field: Message Variable
Data type: SY-MSGV1Default: SY-MSGV1
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV2 - ABAP System Field: Message Variable
Data type: SY-MSGV2Default: SY-MSGV2
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV3 - ABAP System Field: Message Variable
Data type: SY-MSGV3Default: SY-MSGV3
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MSGV4 - ABAP System Field: Message Variable
Data type: SY-MSGV4Default: SY-MSGV4
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ITOB_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.| DATA: | ||||
| lv_i_msgid | TYPE SY-MSGID, " SY-MSGID | |||
| lv_i_msgty | TYPE SY-MSGTY, " SY-MSGTY | |||
| lv_i_msgno | TYPE SY-MSGNO, " SY-MSGNO | |||
| lv_i_msgv1 | TYPE SY-MSGV1, " SY-MSGV1 | |||
| lv_i_msgv2 | TYPE SY-MSGV2, " SY-MSGV2 | |||
| lv_i_msgv3 | TYPE SY-MSGV3, " SY-MSGV3 | |||
| lv_i_msgv4 | TYPE SY-MSGV4. " SY-MSGV4 |
|   CALL FUNCTION 'ITOB_MESSAGE_STORE' "NOTRANSL: ITOB: Speichert Systemnachricht |
| EXPORTING | ||
| I_MSGID | = lv_i_msgid | |
| I_MSGTY | = lv_i_msgty | |
| I_MSGNO | = lv_i_msgno | |
| I_MSGV1 | = lv_i_msgv1 | |
| I_MSGV2 | = lv_i_msgv2 | |
| I_MSGV3 | = lv_i_msgv3 | |
| I_MSGV4 | = lv_i_msgv4 | |
| . " ITOB_MESSAGE_STORE | ||
ABAP code using 7.40 inline data declarations to call FM ITOB_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.| "SELECT single MSGID FROM SY INTO @DATA(ld_i_msgid). | ||||
| DATA(ld_i_msgid) | = SY-MSGID. | |||
| "SELECT single MSGTY FROM SY INTO @DATA(ld_i_msgty). | ||||
| DATA(ld_i_msgty) | = SY-MSGTY. | |||
| "SELECT single MSGNO FROM SY INTO @DATA(ld_i_msgno). | ||||
| DATA(ld_i_msgno) | = SY-MSGNO. | |||
| "SELECT single MSGV1 FROM SY INTO @DATA(ld_i_msgv1). | ||||
| DATA(ld_i_msgv1) | = SY-MSGV1. | |||
| "SELECT single MSGV2 FROM SY INTO @DATA(ld_i_msgv2). | ||||
| DATA(ld_i_msgv2) | = SY-MSGV2. | |||
| "SELECT single MSGV3 FROM SY INTO @DATA(ld_i_msgv3). | ||||
| DATA(ld_i_msgv3) | = SY-MSGV3. | |||
| "SELECT single MSGV4 FROM SY INTO @DATA(ld_i_msgv4). | ||||
| DATA(ld_i_msgv4) | = SY-MSGV4. | |||
Search for further information about these or an SAP related objects