SAP MCV_BROADCAST_INV Function Module for NOTRANSL: Übertragung Fakturabelege
MCV_BROADCAST_INV is a standard mcv broadcast inv 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: Übertragung Fakturabelege 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 broadcast inv FM, simply by entering the name MCV_BROADCAST_INV into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCSGB
Program Name: SAPLMCSGB
Main Program: SAPLMCSGB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCV_BROADCAST_INV 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_BROADCAST_INV'"NOTRANSL: Übertragung Fakturabelege.
EXPORTING
CONTROL = "LIS Updating: Control Parameters
ZEITP = "Event for Which an Update Is to Take Place
* XVBUP = "Table for Structure VBUPVB
IMPORTING Parameters details for MCV_BROADCAST_INV
CONTROL - LIS Updating: Control Parameters
Data type: MCCONTROLOptional: No
Call by Reference: Yes
ZEITP - Event for Which an Update Is to Take Place
Data type: TMC5-ZEITPOptional: No
Call by Reference: Yes
XVBUP - Table for Structure VBUPVB
Data type: VA_VBUPVB_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for MCV_BROADCAST_INV 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_control | TYPE MCCONTROL, " | |||
| lv_zeitp | TYPE TMC5-ZEITP, " | |||
| lv_xvbup | TYPE VA_VBUPVB_T. " |
|   CALL FUNCTION 'MCV_BROADCAST_INV' "NOTRANSL: Übertragung Fakturabelege |
| EXPORTING | ||
| CONTROL | = lv_control | |
| ZEITP | = lv_zeitp | |
| XVBUP | = lv_xvbup | |
| . " MCV_BROADCAST_INV | ||
ABAP code using 7.40 inline data declarations to call FM MCV_BROADCAST_INV
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