SAP OIU_STORE_MESSAGE Function Module for Store error message and parameters









OIU_STORE_MESSAGE is a standard oiu store message 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 error message and parameters 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 oiu store message FM, simply by entering the name OIU_STORE_MESSAGE into the relevant SAP transaction such as SE37 or SE38.

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



Function OIU_STORE_MESSAGE 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 'OIU_STORE_MESSAGE'"Store error message and parameters
EXPORTING
I_MSG = "Message structure
* I_DOC_ID = "Document used to display details
* I_EXITP = "User exit program
* I_EXITF = "User exit form

TABLES
* T_PARAMS = "

EXCEPTIONS
NO_HEADER = 1 APPL_LOG_ERROR = 2 DOC_EXIT_ERROR = 3 OTHERS = 4
.



IMPORTING Parameters details for OIU_STORE_MESSAGE

I_MSG - Message structure

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

I_DOC_ID - Document used to display details

Data type: BALHDRI-ALTEXT
Optional: Yes
Call by Reference: Yes

I_EXITP - User exit program

Data type: BALMI-USEREXITP
Optional: Yes
Call by Reference: Yes

I_EXITF - User exit form

Data type: BALMI-USEREXITF
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for OIU_STORE_MESSAGE

T_PARAMS -

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

EXCEPTIONS details

NO_HEADER - No header object

Data type:
Optional: No
Call by Reference: Yes

APPL_LOG_ERROR - APPL_LOG function error

Data type:
Optional: No
Call by Reference: Yes

DOC_EXIT_ERROR - Document and user-exit both shouldn't be entered

Data type:
Optional: No
Call by Reference: Yes

OTHERS - Others

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OIU_STORE_MESSAGE 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_msg  TYPE IWERRORMSG, "   
lt_t_params  TYPE STANDARD TABLE OF SPAR, "   
lv_no_header  TYPE SPAR, "   
lv_i_doc_id  TYPE BALHDRI-ALTEXT, "   
lv_appl_log_error  TYPE BALHDRI, "   
lv_i_exitp  TYPE BALMI-USEREXITP, "   
lv_doc_exit_error  TYPE BALMI, "   
lv_others  TYPE BALMI, "   
lv_i_exitf  TYPE BALMI-USEREXITF. "   

  CALL FUNCTION 'OIU_STORE_MESSAGE'  "Store error message and parameters
    EXPORTING
         I_MSG = lv_i_msg
         I_DOC_ID = lv_i_doc_id
         I_EXITP = lv_i_exitp
         I_EXITF = lv_i_exitf
    TABLES
         T_PARAMS = lt_t_params
    EXCEPTIONS
        NO_HEADER = 1
        APPL_LOG_ERROR = 2
        DOC_EXIT_ERROR = 3
        OTHERS = 4
. " OIU_STORE_MESSAGE




ABAP code using 7.40 inline data declarations to call FM OIU_STORE_MESSAGE

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 ALTEXT FROM BALHDRI INTO @DATA(ld_i_doc_id).
 
 
"SELECT single USEREXITP FROM BALMI INTO @DATA(ld_i_exitp).
 
 
 
"SELECT single USEREXITF FROM BALMI INTO @DATA(ld_i_exitf).
 


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!