SAP MCEX_MESS_TAB_FILL Function Module for NOTRANSL: Filling the message-tab









MCEX_MESS_TAB_FILL is a standard mcex mess tab fill 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: Filling the message-tab 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 mess tab fill FM, simply by entering the name MCEX_MESS_TAB_FILL 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_MESS_TAB_FILL 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_MESS_TAB_FILL'"NOTRANSL: Filling the message-tab
EXPORTING
I_MSGID = "Messages, Message Class
I_MSGTY = "Messages, Message Type
I_MSGNO = "Messages, Message Number
* I_MSGV1 = "
* I_MSGV2 = "
* I_MSGV3 = "
* I_MSGV4 = "
.



IMPORTING Parameters details for MCEX_MESS_TAB_FILL

I_MSGID - Messages, Message Class

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

I_MSGTY - Messages, Message Type

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

I_MSGNO - Messages, Message Number

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

I_MSGV1 -

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

I_MSGV2 -

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

I_MSGV3 -

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

I_MSGV4 -

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

Copy and paste ABAP code example for MCEX_MESS_TAB_FILL 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, "   
lv_i_msgty  TYPE SY-MSGTY, "   
lv_i_msgno  TYPE SY-MSGNO, "   
lv_i_msgv1  TYPE SY, "   
lv_i_msgv2  TYPE SY, "   
lv_i_msgv3  TYPE SY, "   
lv_i_msgv4  TYPE SY. "   

  CALL FUNCTION 'MCEX_MESS_TAB_FILL'  "NOTRANSL: Filling the message-tab
    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
. " MCEX_MESS_TAB_FILL




ABAP code using 7.40 inline data declarations to call FM MCEX_MESS_TAB_FILL

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).
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_i_msgty).
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_i_msgno).
 
 
 
 
 


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!