SAP MCV_UPDATE_RM_INVOICE Function Module for Update statistical data billing document for risk management
MCV_UPDATE_RM_INVOICE is a standard mcv update rm invoice SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update statistical data billing document for risk management 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 update rm invoice FM, simply by entering the name MCV_UPDATE_RM_INVOICE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCS6
Program Name: SAPLMCS6
Main Program: SAPLMCS6
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function MCV_UPDATE_RM_INVOICE 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_UPDATE_RM_INVOICE'"Update statistical data billing document for risk management.
EXPORTING
CONTROL = "LIS Updating: Control Parameters
ZEITP = "Event for which updating should take place
TABLES
MCINF = "Select Option for Info Structures ((RANGES)
XMCKOMV = "Reference Structure from MCKOMV for Function Module
XMCVBPA = "Reference Structure from MCVBPA for Function Module
XMCVBRK = "Reference Structure from MCVBRK for Function Module
XMCVBRP = "Reference Structure from MCVBRP for Function Module
XMCVBUK = "Reference Structure from MCVBUK for Function Module
XMCVBUP = "Reference Structure from MCVBUP for Function Module
XVBFA = "Reference Structure of MCVBFS for Function Module
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_SAPLMCS6_001 SIS: User Exit for Billing Documents - Header Data
EXIT_SAPLMCS6_002 SIS: User Exit for Billing Documents - Item Data
IMPORTING Parameters details for MCV_UPDATE_RM_INVOICE
CONTROL - LIS Updating: Control Parameters
Data type: MCCONTROLOptional: No
Call by Reference: No ( called with pass by value option)
ZEITP - Event for which updating should take place
Data type: TMC2F-ZEITPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MCV_UPDATE_RM_INVOICE
MCINF - Select Option for Info Structures ((RANGES)
Data type: MCSOINFOptional: No
Call by Reference: Yes
XMCKOMV - Reference Structure from MCKOMV for Function Module
Data type: MCKOMVBOptional: No
Call by Reference: Yes
XMCVBPA - Reference Structure from MCVBPA for Function Module
Data type: MCVBPABOptional: No
Call by Reference: Yes
XMCVBRK - Reference Structure from MCVBRK for Function Module
Data type: MCVBRKBOptional: No
Call by Reference: Yes
XMCVBRP - Reference Structure from MCVBRP for Function Module
Data type: MCVBRPBOptional: No
Call by Reference: Yes
XMCVBUK - Reference Structure from MCVBUK for Function Module
Data type: MCVBUKBOptional: No
Call by Reference: Yes
XMCVBUP - Reference Structure from MCVBUP for Function Module
Data type: MCVBUPBOptional: No
Call by Reference: Yes
XVBFA - Reference Structure of MCVBFS for Function Module
Data type: VBFAVBOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MCV_UPDATE_RM_INVOICE 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, " | |||
| lv_zeitp | TYPE TMC2F-ZEITP, " | |||
| lt_xmckomv | TYPE STANDARD TABLE OF MCKOMVB, " | |||
| lt_xmcvbpa | TYPE STANDARD TABLE OF MCVBPAB, " | |||
| lt_xmcvbrk | TYPE STANDARD TABLE OF MCVBRKB, " | |||
| lt_xmcvbrp | TYPE STANDARD TABLE OF MCVBRPB, " | |||
| lt_xmcvbuk | TYPE STANDARD TABLE OF MCVBUKB, " | |||
| lt_xmcvbup | TYPE STANDARD TABLE OF MCVBUPB, " | |||
| lt_xvbfa | TYPE STANDARD TABLE OF VBFAVB. " |
|   CALL FUNCTION 'MCV_UPDATE_RM_INVOICE' "Update statistical data billing document for risk management |
| EXPORTING | ||
| CONTROL | = lv_control | |
| ZEITP | = lv_zeitp | |
| TABLES | ||
| MCINF | = lt_mcinf | |
| XMCKOMV | = lt_xmckomv | |
| XMCVBPA | = lt_xmcvbpa | |
| XMCVBRK | = lt_xmcvbrk | |
| XMCVBRP | = lt_xmcvbrp | |
| XMCVBUK | = lt_xmcvbuk | |
| XMCVBUP | = lt_xmcvbup | |
| XVBFA | = lt_xvbfa | |
| . " MCV_UPDATE_RM_INVOICE | ||
ABAP code using 7.40 inline data declarations to call FM MCV_UPDATE_RM_INVOICE
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 TMC2F INTO @DATA(ld_zeitp). | ||||
Search for further information about these or an SAP related objects