SAP MCV_SHIPMENT_DOCUMENT_UPDATE Function Module for NOTRANSL: Führt Belegupdate für Transportkopf und -strecken aus
MCV_SHIPMENT_DOCUMENT_UPDATE is a standard mcv shipment document update 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: Führt Belegupdate für Transportkopf und -strecken aus 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 shipment document update FM, simply by entering the name MCV_SHIPMENT_DOCUMENT_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCVA
Program Name: SAPLMCVA
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCV_SHIPMENT_DOCUMENT_UPDATE 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_SHIPMENT_DOCUMENT_UPDATE'"NOTRANSL: Führt Belegupdate für Transportkopf und -strecken aus.
EXPORTING
I_FLG_OPTIONS = "New Input Values
I_FLG_UPD = "New Input Values
IMPORTING Parameters details for MCV_SHIPMENT_DOCUMENT_UPDATE
I_FLG_OPTIONS - New Input Values
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
I_FLG_UPD - New Input Values
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MCV_SHIPMENT_DOCUMENT_UPDATE 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_flg_options | TYPE XFLAG, " | |||
| lv_i_flg_upd | TYPE XFLAG. " |
|   CALL FUNCTION 'MCV_SHIPMENT_DOCUMENT_UPDATE' "NOTRANSL: Führt Belegupdate für Transportkopf und -strecken aus |
| EXPORTING | ||
| I_FLG_OPTIONS | = lv_i_flg_options | |
| I_FLG_UPD | = lv_i_flg_upd | |
| . " MCV_SHIPMENT_DOCUMENT_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM MCV_SHIPMENT_DOCUMENT_UPDATE
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