SAP EXIT_SAPMMCP6_001 Function Module for User Exit for Reading External Data in Planning
EXIT_SAPMMCP6_001 is a standard exit sapmmcp6 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for User Exit for Reading External Data in Planning 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 exit sapmmcp6 001 FM, simply by entering the name EXIT_SAPMMCP6_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XSOP
Program Name: SAPLXSOP
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPMMCP6_001 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 'EXIT_SAPMMCP6_001'"User Exit for Reading External Data in Planning.
EXPORTING
ISSOUR = "
IVRSIO = "Version Number
ISKEY = "Characteristic String
IPERIV = "Fiscal Year Variant
IPERKZ = "Period Indicator
IFNAME = "Name of Key Figure
IPLOBJ = "Planning Object Number
I_T445A = "
I_T445P = "
TABLES
ICOLS = "Column Index of Planning Table
WERTE = "External Data Read per Line
IMPORTING Parameters details for EXIT_SAPMMCP6_001
ISSOUR -
Data type: RMCP2-SSOUROptional: No
Call by Reference: No ( called with pass by value option)
IVRSIO - Version Number
Data type: RMCP2-VRSIOOptional: No
Call by Reference: No ( called with pass by value option)
ISKEY - Characteristic String
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IPERIV - Fiscal Year Variant
Data type: RMCP2-PERIVOptional: No
Call by Reference: No ( called with pass by value option)
IPERKZ - Period Indicator
Data type: RMCP2-SPPEROptional: No
Call by Reference: No ( called with pass by value option)
IFNAME - Name of Key Figure
Data type: MCP6_LI-FELDHOptional: No
Call by Reference: No ( called with pass by value option)
IPLOBJ - Planning Object Number
Data type: MCP6_LI-KRIT1Optional: No
Call by Reference: No ( called with pass by value option)
I_T445A -
Data type: T445AOptional: No
Call by Reference: No ( called with pass by value option)
I_T445P -
Data type: T445POptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPMMCP6_001
ICOLS - Column Index of Planning Table
Data type: PGCOLSOptional: No
Call by Reference: No ( called with pass by value option)
WERTE - External Data Read per Line
Data type: VESOPOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMMCP6_001 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: | ||||
lt_icols | TYPE STANDARD TABLE OF PGCOLS, " | |||
lv_issour | TYPE RMCP2-SSOUR, " | |||
lt_werte | TYPE STANDARD TABLE OF VESOP, " | |||
lv_ivrsio | TYPE RMCP2-VRSIO, " | |||
lv_iskey | TYPE RMCP2, " | |||
lv_iperiv | TYPE RMCP2-PERIV, " | |||
lv_iperkz | TYPE RMCP2-SPPER, " | |||
lv_ifname | TYPE MCP6_LI-FELDH, " | |||
lv_iplobj | TYPE MCP6_LI-KRIT1, " | |||
lv_i_t445a | TYPE T445A, " | |||
lv_i_t445p | TYPE T445P. " |
  CALL FUNCTION 'EXIT_SAPMMCP6_001' "User Exit for Reading External Data in Planning |
EXPORTING | ||
ISSOUR | = lv_issour | |
IVRSIO | = lv_ivrsio | |
ISKEY | = lv_iskey | |
IPERIV | = lv_iperiv | |
IPERKZ | = lv_iperkz | |
IFNAME | = lv_ifname | |
IPLOBJ | = lv_iplobj | |
I_T445A | = lv_i_t445a | |
I_T445P | = lv_i_t445p | |
TABLES | ||
ICOLS | = lt_icols | |
WERTE | = lt_werte | |
. " EXIT_SAPMMCP6_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMMCP6_001
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 SSOUR FROM RMCP2 INTO @DATA(ld_issour). | ||||
"SELECT single VRSIO FROM RMCP2 INTO @DATA(ld_ivrsio). | ||||
"SELECT single PERIV FROM RMCP2 INTO @DATA(ld_iperiv). | ||||
"SELECT single SPPER FROM RMCP2 INTO @DATA(ld_iperkz). | ||||
"SELECT single FELDH FROM MCP6_LI INTO @DATA(ld_ifname). | ||||
"SELECT single KRIT1 FROM MCP6_LI INTO @DATA(ld_iplobj). | ||||
Search for further information about these or an SAP related objects