SAP MCV_INVOICE_CHECK_AND_SET Function Module for NOTRANSL: Statistikfortschreibung Neuaufbau Faktura: Prüfen und ergänzen

Search SAP Function Modules

MCV_INVOICE_CHECK_AND_SET is a standard mcv invoice check and set 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: Statistikfortschreibung Neuaufbau Faktura: Prüfen und ergänzen 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 invoice check and set FM, simply by entering the name MCV_INVOICE_CHECK_AND_SET into the relevant SAP transaction such as SE37 or SE38.

Function Group: MCS6
Program Name: SAPLMCS6
Main Program: SAPLMCS6
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCV_INVOICE_CHECK_AND_SET 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_INVOICE_CHECK_AND_SET'"NOTRANSL: Statistikfortschreibung Neuaufbau Faktura: Prüfen und ergänzen
  EXPORTING
   ZVBRK =  "Billing document header

 IMPORTING
   UPDATE =  "Indicator document adds 'X'
   ZVBRK =  "Billing document header

TABLES
   XKOMV =  "Billing document condition
   XVBFA =  "Billing document flow
   XVBPA =  "Billing document partner
   XVBRP =  "Billing document item
   XVBUK =  "Billing document header status
   XVBUP =  "Billing document item status

EXCEPTIONS
   ERROR = 1 

.

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_INVOICE_CHECK_AND_SET

ZVBRK - Billing document header

Data type: VBRKVB
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for MCV_INVOICE_CHECK_AND_SET

UPDATE - Indicator document adds 'X'

Data type: TVFK-STATI
Optional: No
Call by Reference: No ( called with pass by value option)

ZVBRK - Billing document header

Data type: VBRKVB
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for MCV_INVOICE_CHECK_AND_SET

XKOMV - Billing document condition

Data type: KOMV
Optional: No
Call by Reference: No ( called with pass by value option)

XVBFA - Billing document flow

Data type: VBFAVB
Optional: No
Call by Reference: No ( called with pass by value option)

XVBPA - Billing document partner

Data type: VBPAVB
Optional: No
Call by Reference: No ( called with pass by value option)

XVBRP - Billing document item

Data type: VBRPVB
Optional: No
Call by Reference: No ( called with pass by value option)

XVBUK - Billing document header status

Data type: VBUKVB
Optional: No
Call by Reference: No ( called with pass by value option)

XVBUP - Billing document item status

Data type: VBUPVB
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR - Error occurred: no further processing

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MCV_INVOICE_CHECK_AND_SET 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.

ABAP code using 7.40 inline data declarations to call FM MCV_INVOICE_CHECK_AND_SET

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.

Search for further information about these or an SAP related objects