SAP MCV_STATISTICS_UPD_V1_ORDER Function Module for NOTRANSL: Fortschreibung Kundenauftrag
MCV_STATISTICS_UPD_V1_ORDER is a standard mcv statistics upd v1 order 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: Fortschreibung Kundenauftrag 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 mcv statistics upd v1 order FM, simply by entering the name MCV_STATISTICS_UPD_V1_ORDER into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCS1
Program Name: SAPLMCS1
Main Program: SAPLMCS1
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function MCV_STATISTICS_UPD_V1_ORDER 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 'MCV_STATISTICS_UPD_V1_ORDER'"NOTRANSL: Fortschreibung Kundenauftrag.
EXPORTING
CONTROL = "
ZEITP = "
TABLES
MCINF = "
XMCVBUK = "
XMCVBUP = "
XMCFPLT = "
XMCKOMV = "
XMCVBAK = "
XMCVBAP = "
XMCVBAPF = "
XMCVBEP = "
XMCVBFA = "
XMCVBKD = "
XMCVBPA = "
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_SAPLMCS1_001 SIS: User Exit for SD Document - Header Data
EXIT_SAPLMCS1_002 SIS: User Exit for SD Document - Item Data
IMPORTING Parameters details for MCV_STATISTICS_UPD_V1_ORDER
CONTROL -
Data type: MCCONTROLOptional: No
Call by Reference: No ( called with pass by value option)
ZEITP -
Data type: TMC5-ZEITPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MCV_STATISTICS_UPD_V1_ORDER
MCINF -
Data type: MCSOINFOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBUK -
Data type: MCVBUKBOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBUP -
Data type: MCVBUPBOptional: No
Call by Reference: No ( called with pass by value option)
XMCFPLT -
Data type: MCFPLTBOptional: No
Call by Reference: No ( called with pass by value option)
XMCKOMV -
Data type: MCKOMVBOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBAK -
Data type: MCVBAKBOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBAP -
Data type: MCVBAPBOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBAPF -
Data type: MCVBAFBOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBEP -
Data type: MCVBEPBOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBFA -
Data type: MCVBFABOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBKD -
Data type: MCVBKDBOptional: No
Call by Reference: No ( called with pass by value option)
XMCVBPA -
Data type: MCVBPABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MCV_STATISTICS_UPD_V1_ORDER 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_mcinf | TYPE STANDARD TABLE OF MCSOINF, " | |||
| lv_control | TYPE MCCONTROL, " | |||
| lt_xmcvbuk | TYPE STANDARD TABLE OF MCVBUKB, " | |||
| lt_xmcvbup | TYPE STANDARD TABLE OF MCVBUPB, " | |||
| lt_xmcfplt | TYPE STANDARD TABLE OF MCFPLTB, " | |||
| lv_zeitp | TYPE TMC5-ZEITP, " | |||
| lt_xmckomv | TYPE STANDARD TABLE OF MCKOMVB, " | |||
| lt_xmcvbak | TYPE STANDARD TABLE OF MCVBAKB, " | |||
| lt_xmcvbap | TYPE STANDARD TABLE OF MCVBAPB, " | |||
| lt_xmcvbapf | TYPE STANDARD TABLE OF MCVBAFB, " | |||
| lt_xmcvbep | TYPE STANDARD TABLE OF MCVBEPB, " | |||
| lt_xmcvbfa | TYPE STANDARD TABLE OF MCVBFAB, " | |||
| lt_xmcvbkd | TYPE STANDARD TABLE OF MCVBKDB, " | |||
| lt_xmcvbpa | TYPE STANDARD TABLE OF MCVBPAB. " |
|   CALL FUNCTION 'MCV_STATISTICS_UPD_V1_ORDER' "NOTRANSL: Fortschreibung Kundenauftrag |
| EXPORTING | ||
| CONTROL | = lv_control | |
| ZEITP | = lv_zeitp | |
| TABLES | ||
| MCINF | = lt_mcinf | |
| XMCVBUK | = lt_xmcvbuk | |
| XMCVBUP | = lt_xmcvbup | |
| XMCFPLT | = lt_xmcfplt | |
| XMCKOMV | = lt_xmckomv | |
| XMCVBAK | = lt_xmcvbak | |
| XMCVBAP | = lt_xmcvbap | |
| XMCVBAPF | = lt_xmcvbapf | |
| XMCVBEP | = lt_xmcvbep | |
| XMCVBFA | = lt_xmcvbfa | |
| XMCVBKD | = lt_xmcvbkd | |
| XMCVBPA | = lt_xmcvbpa | |
| . " MCV_STATISTICS_UPD_V1_ORDER | ||
ABAP code using 7.40 inline data declarations to call FM MCV_STATISTICS_UPD_V1_ORDER
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 ZEITP FROM TMC5 INTO @DATA(ld_zeitp). | ||||
Search for further information about these or an SAP related objects