SAP EXIT_SAPMMCP6_017 Function Module for User Exit for Influencing Key Figure Block
EXIT_SAPMMCP6_017 is a standard exit sapmmcp6 017 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 Influencing Key Figure Block 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 017 FM, simply by entering the name EXIT_SAPMMCP6_017 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_017 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_017'"User Exit for Influencing Key Figure Block.
EXPORTING
I_GSTRU = "
I_SCTYP = "
TABLES
T_KEYFIGURES_FOR_ENQUEUE = "
IMPORTING Parameters details for EXIT_SAPMMCP6_017
I_GSTRU -
Data type: T445A-GSTRUOptional: No
Call by Reference: No ( called with pass by value option)
I_SCTYP -
Data type: T445P-SCTYPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPMMCP6_017
T_KEYFIGURES_FOR_ENQUEUE -
Data type: MCENQUEUE_PLANOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPMMCP6_017 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_gstru | TYPE T445A-GSTRU, " | |||
lt_t_keyfigures_for_enqueue | TYPE STANDARD TABLE OF MCENQUEUE_PLAN, " | |||
lv_i_sctyp | TYPE T445P-SCTYP. " |
  CALL FUNCTION 'EXIT_SAPMMCP6_017' "User Exit for Influencing Key Figure Block |
EXPORTING | ||
I_GSTRU | = lv_i_gstru | |
I_SCTYP | = lv_i_sctyp | |
TABLES | ||
T_KEYFIGURES_FOR_ENQUEUE | = lt_t_keyfigures_for_enqueue | |
. " EXIT_SAPMMCP6_017 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPMMCP6_017
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 GSTRU FROM T445A INTO @DATA(ld_i_gstru). | ||||
"SELECT single SCTYP FROM T445P INTO @DATA(ld_i_sctyp). | ||||
Search for further information about these or an SAP related objects