SAP EHS003_MESSAGE_OUTPUT Function Module for NOTRANSL: EHS: Ausgabe von Meldungen
EHS003_MESSAGE_OUTPUT is a standard ehs003 message output 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: EHS: Ausgabe von Meldungen 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 ehs003 message output FM, simply by entering the name EHS003_MESSAGE_OUTPUT into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHS003
Program Name: SAPLEHS003
Main Program: SAPLEHS003
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHS003_MESSAGE_OUTPUT 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 'EHS003_MESSAGE_OUTPUT'"NOTRANSL: EHS: Ausgabe von Meldungen.
EXPORTING
* SPRSL = "SAP System, Current Language
* ARBGB = "Messages, Message Class
* MSGNR = "Messages, Message Number
EXCEPTIONS
OTHERS_ = 1
IMPORTING Parameters details for EHS003_MESSAGE_OUTPUT
SPRSL - SAP System, Current Language
Data type: SY-LANGUOptional: Yes
Call by Reference: Yes
ARBGB - Messages, Message Class
Data type: BALMI-MSGIDOptional: Yes
Call by Reference: Yes
MSGNR - Messages, Message Number
Data type: BALMI-MSGNOOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
OTHERS_ - Internal Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EHS003_MESSAGE_OUTPUT 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_sprsl | TYPE SY-LANGU, " | |||
| lv_others_ | TYPE SY, " | |||
| lv_arbgb | TYPE BALMI-MSGID, " | |||
| lv_msgnr | TYPE BALMI-MSGNO. " |
|   CALL FUNCTION 'EHS003_MESSAGE_OUTPUT' "NOTRANSL: EHS: Ausgabe von Meldungen |
| EXPORTING | ||
| SPRSL | = lv_sprsl | |
| ARBGB | = lv_arbgb | |
| MSGNR | = lv_msgnr | |
| EXCEPTIONS | ||
| OTHERS_ = 1 | ||
| . " EHS003_MESSAGE_OUTPUT | ||
ABAP code using 7.40 inline data declarations to call FM EHS003_MESSAGE_OUTPUT
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 LANGU FROM SY INTO @DATA(ld_sprsl). | ||||
| "SELECT single MSGID FROM BALMI INTO @DATA(ld_arbgb). | ||||
| "SELECT single MSGNO FROM BALMI INTO @DATA(ld_msgnr). | ||||
Search for further information about these or an SAP related objects