SAP MCEX_INTERFACE_NOTIFICATION Function Module for NOTRANSL: Interfacebaustein für Anschluß Meldungen an Customizing Cockpit









MCEX_INTERFACE_NOTIFICATION is a standard mcex interface notification 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: Interfacebaustein für Anschluß Meldungen an Customizing Cockpit 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 interface notification FM, simply by entering the name MCEX_INTERFACE_NOTIFICATION into the relevant SAP transaction such as SE37 or SE38.

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



Function MCEX_INTERFACE_NOTIFICATION 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_INTERFACE_NOTIFICATION'"NOTRANSL: Interfacebaustein für Anschluß Meldungen an Customizing Cockpit
  EXPORTING
   ZEITP =  "Event for Which an Update Is to Take Place
   CONTR =  "LIS Updating: Control Parameters
   N_VIQMEL =  "Generated Table for View VIQMEL
*  O_VIQMEL =  "Generated Table for View VIQMEL

TABLES
   N_IVIQMFE =  "Work Table for Notification Item
   N_IVIQMMA =  "Work Structure Activities
   N_IVIQMSM =  "Work Table for Actions
   N_IVIQMUR =  "Work Table for Causes
*  O_IVIQMFE =  "Work Table for Notification Item
*  O_IVIQMMA =  "Work Structure Activities
*  O_IVIQMSM =  "Work Table for Actions
*  O_IVIQMUR =  "Work Table for Causes
.



IMPORTING Parameters details for MCEX_INTERFACE_NOTIFICATION

ZEITP - Event for Which an Update Is to Take Place

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

CONTR - LIS Updating: Control Parameters

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

N_VIQMEL - Generated Table for View VIQMEL

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

O_VIQMEL - Generated Table for View VIQMEL

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

TABLES Parameters details for MCEX_INTERFACE_NOTIFICATION

N_IVIQMFE - Work Table for Notification Item

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

N_IVIQMMA - Work Structure Activities

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

N_IVIQMSM - Work Table for Actions

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

N_IVIQMUR - Work Table for Causes

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

O_IVIQMFE - Work Table for Notification Item

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

O_IVIQMMA - Work Structure Activities

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

O_IVIQMSM - Work Table for Actions

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

O_IVIQMUR - Work Table for Causes

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

Copy and paste ABAP code example for MCEX_INTERFACE_NOTIFICATION 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_zeitp  TYPE TMC5-ZEITP, "   
lt_n_iviqmfe  TYPE STANDARD TABLE OF WQMFE, "   
lv_contr  TYPE MCCONTROL, "   
lt_n_iviqmma  TYPE STANDARD TABLE OF WQMMA, "   
lv_n_viqmel  TYPE VIQMEL, "   
lt_n_iviqmsm  TYPE STANDARD TABLE OF WQMSM, "   
lv_o_viqmel  TYPE VIQMEL, "   
lt_n_iviqmur  TYPE STANDARD TABLE OF WQMUR, "   
lt_o_iviqmfe  TYPE STANDARD TABLE OF WQMFE, "   
lt_o_iviqmma  TYPE STANDARD TABLE OF WQMMA, "   
lt_o_iviqmsm  TYPE STANDARD TABLE OF WQMSM, "   
lt_o_iviqmur  TYPE STANDARD TABLE OF WQMUR. "   

  CALL FUNCTION 'MCEX_INTERFACE_NOTIFICATION'  "NOTRANSL: Interfacebaustein für Anschluß Meldungen an Customizing Cockpit
    EXPORTING
         ZEITP = lv_zeitp
         CONTR = lv_contr
         N_VIQMEL = lv_n_viqmel
         O_VIQMEL = lv_o_viqmel
    TABLES
         N_IVIQMFE = lt_n_iviqmfe
         N_IVIQMMA = lt_n_iviqmma
         N_IVIQMSM = lt_n_iviqmsm
         N_IVIQMUR = lt_n_iviqmur
         O_IVIQMFE = lt_o_iviqmfe
         O_IVIQMMA = lt_o_iviqmma
         O_IVIQMSM = lt_o_iviqmsm
         O_IVIQMUR = lt_o_iviqmur
. " MCEX_INTERFACE_NOTIFICATION




ABAP code using 7.40 inline data declarations to call FM MCEX_INTERFACE_NOTIFICATION

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 ZEITP FROM TMC5 INTO @DATA(ld_zeitp).
 
 
 
 
 
 
 
 
 
 
 
 


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!