SAP MCP_EVENT_READ_BLOCK Function Module for NOTRANSL: Lesen Block von Ereignissen zu Liste von Planungsobjekten / Feld

Search SAP Function Modules

MCP_EVENT_READ_BLOCK is a standard mcp event read block 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 Block von Ereignissen zu Liste von Planungsobjekten / Feld 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 block FM, simply by entering the name MCP_EVENT_READ_BLOCK 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_BLOCK 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_BLOCK'"NOTRANSL: Lesen Block von Ereignissen zu Liste von Planungsobjekten / Feld
  EXPORTING
   IVRSIO =  "Version number in the information structure
*  ISSOUR = ' ' "Statistic(s) origin

TABLES
   T_PLOBJ =  "PLOBJ and STFNA (Table Type)
   INT_V_EVENT =  "Generated Table for View

EXCEPTIONS
   NO_EVENT = 1 

.

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_BLOCK

IVRSIO - Version number in the information structure

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

ISSOUR - Statistic(s) origin

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

TABLES Parameters details for MCP_EVENT_READ_BLOCK

T_PLOBJ - PLOBJ and STFNA (Table Type)

Data type: EVENT_PLOBJ_TAB
Optional: No
Call by Reference: Yes

INT_V_EVENT - Generated Table for View

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

EXCEPTIONS details

NO_EVENT -

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

Copy and paste ABAP code example for MCP_EVENT_READ_BLOCK 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_BLOCK

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