SAP MCP_CALC_EVENT Function Module for NOTRANSL: Anwenden eventueller Events auf Detailebene für übergebene Sxyz
MCP_CALC_EVENT is a standard mcp calc event 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: Anwenden eventueller Events auf Detailebene für übergebene Sxyz 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 calc event FM, simply by entering the name MCP_CALC_EVENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCP6
Program Name: SAPLMCP6
Main Program: SAPLMCP6
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCP_CALC_EVENT 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_CALC_EVENT'"NOTRANSL: Anwenden eventueller Events auf Detailebene für übergebene Sxyz.
EXPORTING
I_REPID = "Predefined Type
I_FLG_UPD = "Update step ( I / D / U / space )
I_GSTRU = "Generated DDIC table for LIS, conditions, messages
I_VRSIO = "Version number in the information structure
I_T445A = "Planning Configuration for Info Structure
TABLES
T_SXYZE = "System Table INDX
T_SXYZ = "System Table INDX
T_SXYZ_OLD = "System Table INDX
T_LINES = "Lines Index: Planning Matrix
T_COLS = "Column Index for SOP
T_KEYFIGURE_LINK = "Reference Structure for Transferring a Link Row<->Item
T_UPDATE_PERIDS = "Reference Structure for Transferring Periods to be Updated
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_CALC_EVENT
I_REPID - Predefined Type
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_UPD - Update step ( I / D / U / space )
Data type: RMCP2-VBSCHROptional: No
Call by Reference: No ( called with pass by value option)
I_GSTRU - Generated DDIC table for LIS, conditions, messages
Data type: T445A-GSTRUOptional: No
Call by Reference: No ( called with pass by value option)
I_VRSIO - Version number in the information structure
Data type: RMCP2-VRSIAOptional: No
Call by Reference: No ( called with pass by value option)
I_T445A - Planning Configuration for Info Structure
Data type: T445AOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MCP_CALC_EVENT
T_SXYZE - System Table INDX
Data type: INDXOptional: No
Call by Reference: Yes
T_SXYZ - System Table INDX
Data type: INDXOptional: No
Call by Reference: Yes
T_SXYZ_OLD - System Table INDX
Data type: INDXOptional: No
Call by Reference: Yes
T_LINES - Lines Index: Planning Matrix
Data type: MCP6_LIOptional: No
Call by Reference: No ( called with pass by value option)
T_COLS - Column Index for SOP
Data type: PGCOLSOptional: No
Call by Reference: No ( called with pass by value option)
T_KEYFIGURE_LINK - Reference Structure for Transferring a Link Row<->Item
Data type: MCKEYFIGURE_LINKOptional: No
Call by Reference: No ( called with pass by value option)
T_UPDATE_PERIDS - Reference Structure for Transferring Periods to be Updated
Data type: MCUPDATE_PERIDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MCP_CALC_EVENT 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_repid | TYPE SY-REPID, " | |||
| lt_t_sxyze | TYPE STANDARD TABLE OF INDX, " | |||
| lt_t_sxyz | TYPE STANDARD TABLE OF INDX, " | |||
| lv_i_flg_upd | TYPE RMCP2-VBSCHR, " | |||
| lv_i_gstru | TYPE T445A-GSTRU, " | |||
| lt_t_sxyz_old | TYPE STANDARD TABLE OF INDX, " | |||
| lv_i_vrsio | TYPE RMCP2-VRSIA, " | |||
| lt_t_lines | TYPE STANDARD TABLE OF MCP6_LI, " | |||
| lt_t_cols | TYPE STANDARD TABLE OF PGCOLS, " | |||
| lv_i_t445a | TYPE T445A, " | |||
| lt_t_keyfigure_link | TYPE STANDARD TABLE OF MCKEYFIGURE_LINK, " | |||
| lt_t_update_perids | TYPE STANDARD TABLE OF MCUPDATE_PERID. " |
|   CALL FUNCTION 'MCP_CALC_EVENT' "NOTRANSL: Anwenden eventueller Events auf Detailebene für übergebene Sxyz |
| EXPORTING | ||
| I_REPID | = lv_i_repid | |
| I_FLG_UPD | = lv_i_flg_upd | |
| I_GSTRU | = lv_i_gstru | |
| I_VRSIO | = lv_i_vrsio | |
| I_T445A | = lv_i_t445a | |
| TABLES | ||
| T_SXYZE | = lt_t_sxyze | |
| T_SXYZ | = lt_t_sxyz | |
| T_SXYZ_OLD | = lt_t_sxyz_old | |
| T_LINES | = lt_t_lines | |
| T_COLS | = lt_t_cols | |
| T_KEYFIGURE_LINK | = lt_t_keyfigure_link | |
| T_UPDATE_PERIDS | = lt_t_update_perids | |
| . " MCP_CALC_EVENT | ||
ABAP code using 7.40 inline data declarations to call FM MCP_CALC_EVENT
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 REPID FROM SY INTO @DATA(ld_i_repid). | ||||
| "SELECT single VBSCHR FROM RMCP2 INTO @DATA(ld_i_flg_upd). | ||||
| "SELECT single GSTRU FROM T445A INTO @DATA(ld_i_gstru). | ||||
| "SELECT single VRSIA FROM RMCP2 INTO @DATA(ld_i_vrsio). | ||||
Search for further information about these or an SAP related objects