SAP MCEX_MESSAGE_LONG Function Module for NOTRANSL: Direkte Langtextanzeige einer MESSAGE









MCEX_MESSAGE_LONG is a standard mcex message long 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: Direkte Langtextanzeige einer MESSAGE 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 mcex message long FM, simply by entering the name MCEX_MESSAGE_LONG into the relevant SAP transaction such as SE37 or SE38.

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



Function MCEX_MESSAGE_LONG 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 'MCEX_MESSAGE_LONG'"NOTRANSL: Direkte Langtextanzeige einer MESSAGE
EXPORTING
* MELD_ID = 'MCEX' "Message Class
MELD_NR = "Message Number
* MSGV1 = ' ' "Message Variable 1
* MSGV2 = ' ' "Message Variable 2
* MSGV3 = ' ' "Message Variable 3
* MSGV4 = ' ' "Message Variable 4
* LANGU = SY-LANGU "Language
* TITEL = "

IMPORTING
E_CANCEL = "

EXCEPTIONS
MSG_NOT_FOUND = 1
.



IMPORTING Parameters details for MCEX_MESSAGE_LONG

MELD_ID - Message Class

Data type: SHKONTEXT-MELD_ID
Default: 'MCEX'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MELD_NR - Message Number

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

MSGV1 - Message Variable 1

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

MSGV2 - Message Variable 2

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

MSGV3 - Message Variable 3

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

MSGV4 - Message Variable 4

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

LANGU - Language

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

TITEL -

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

EXPORTING Parameters details for MCEX_MESSAGE_LONG

E_CANCEL -

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

EXCEPTIONS details

MSG_NOT_FOUND - Message text not found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MCEX_MESSAGE_LONG 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_meld_id  TYPE SHKONTEXT-MELD_ID, "   'MCEX'
lv_e_cancel  TYPE FLAG, "   
lv_msg_not_found  TYPE FLAG, "   
lv_meld_nr  TYPE SHKONTEXT-MELD_NR, "   
lv_msgv1  TYPE C, "   SPACE
lv_msgv2  TYPE C, "   SPACE
lv_msgv3  TYPE C, "   SPACE
lv_msgv4  TYPE C, "   SPACE
lv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_titel  TYPE SHKONTEXT-TITEL. "   

  CALL FUNCTION 'MCEX_MESSAGE_LONG'  "NOTRANSL: Direkte Langtextanzeige einer MESSAGE
    EXPORTING
         MELD_ID = lv_meld_id
         MELD_NR = lv_meld_nr
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
         LANGU = lv_langu
         TITEL = lv_titel
    IMPORTING
         E_CANCEL = lv_e_cancel
    EXCEPTIONS
        MSG_NOT_FOUND = 1
. " MCEX_MESSAGE_LONG




ABAP code using 7.40 inline data declarations to call FM MCEX_MESSAGE_LONG

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 MELD_ID FROM SHKONTEXT INTO @DATA(ld_meld_id).
DATA(ld_meld_id) = 'MCEX'.
 
 
 
"SELECT single MELD_NR FROM SHKONTEXT INTO @DATA(ld_meld_nr).
 
DATA(ld_msgv1) = ' '.
 
DATA(ld_msgv2) = ' '.
 
DATA(ld_msgv3) = ' '.
 
DATA(ld_msgv4) = ' '.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
"SELECT single TITEL FROM SHKONTEXT INTO @DATA(ld_titel).
 


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!