SAP MCP_EVENT_READ Function Module for NOTRANSL: Lesen Ereignisse zum Planungsobjekt

Search SAP Function Modules

MCP_EVENT_READ is a standard mcp event read 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: Lesen Ereignisse zum Planungsobjekt 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 mcp event read FM, simply by entering the name MCP_EVENT_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function MCP_EVENT_READ 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 'MCP_EVENT_READ'"NOTRANSL: Lesen Ereignisse zum Planungsobjekt
  EXPORTING
   IPLOBJ =  "Planning object
   ISTFNA =  "Field name
   IVRSIO =  "Version
*  ISSOUR = '    ' "Supply source
   IOPERA =  "Operation (+, *)
*  IFABKL = '  ' "

TABLES
   TMCP6VE =  "Transfer table

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMCP6_001 User Exit for Extrapolating Sales for OTB
EXIT_SAPLMCP6_002 User Exit for Checking OTB Within a Purchase Order

IMPORTING Parameters details for MCP_EVENT_READ

IPLOBJ - Planning object

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

ISTFNA - Field name

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

IVRSIO - Version

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

ISSOUR - Supply source

Data type: ERZU-SSOUR
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

IOPERA - Operation (+, *)

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

IFABKL -

Data type: T001W-FABKL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MCP_EVENT_READ

TMCP6VE - Transfer table

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

Copy and paste ABAP code example for MCP_EVENT_READ 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.

ABAP code using 7.40 inline data declarations to call FM MCP_EVENT_READ

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.

Search for further information about these or an SAP related objects