SAP OIU_INCREASE_MESSAGE_LEVEL Function Module for Store message sub-header and increase level
OIU_INCREASE_MESSAGE_LEVEL is a standard oiu increase message level 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 message sub-header and increase level 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 increase message level FM, simply by entering the name OIU_INCREASE_MESSAGE_LEVEL 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:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function OIU_INCREASE_MESSAGE_LEVEL 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_INCREASE_MESSAGE_LEVEL'"Store message sub-header and increase level.
EXPORTING
* I_LOGNUMBER = "Log number
I_SUBHEADER_TEXT = "Sub-header text
EXCEPTIONS
NO_HEADER = 1 SUB_TEXT_MISSING = 2 APPL_LOG_ERROR = 3
IMPORTING Parameters details for OIU_INCREASE_MESSAGE_LEVEL
I_LOGNUMBER - Log number
Data type: BALNRI-LOGNUMBEROptional: Yes
Call by Reference: Yes
I_SUBHEADER_TEXT - Sub-header text
Data type: BALMI-MSGV1Optional: No
Call by Reference: Yes
EXCEPTIONS details
NO_HEADER - Header not entered
Data type:Optional: No
Call by Reference: Yes
SUB_TEXT_MISSING - Sub-header text not entered
Data type:Optional: No
Call by Reference: Yes
APPL_LOG_ERROR - Appl_Log function error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIU_INCREASE_MESSAGE_LEVEL 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_no_header | TYPE STRING, " | |||
lv_i_lognumber | TYPE BALNRI-LOGNUMBER, " | |||
lv_i_subheader_text | TYPE BALMI-MSGV1, " | |||
lv_sub_text_missing | TYPE BALMI, " | |||
lv_appl_log_error | TYPE BALMI. " |
  CALL FUNCTION 'OIU_INCREASE_MESSAGE_LEVEL' "Store message sub-header and increase level |
EXPORTING | ||
I_LOGNUMBER | = lv_i_lognumber | |
I_SUBHEADER_TEXT | = lv_i_subheader_text | |
EXCEPTIONS | ||
NO_HEADER = 1 | ||
SUB_TEXT_MISSING = 2 | ||
APPL_LOG_ERROR = 3 | ||
. " OIU_INCREASE_MESSAGE_LEVEL |
ABAP code using 7.40 inline data declarations to call FM OIU_INCREASE_MESSAGE_LEVEL
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 LOGNUMBER FROM BALNRI INTO @DATA(ld_i_lognumber). | ||||
"SELECT single MSGV1 FROM BALMI INTO @DATA(ld_i_subheader_text). | ||||
Search for further information about these or an SAP related objects