SAP DPVMSRFC02_FCSO04_PREPARE Function Module for VMS DP : FCSO04 Prepare Function (Cancel Sales Order)
DPVMSRFC02_FCSO04_PREPARE is a standard dpvmsrfc02 fcso04 prepare SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for VMS DP : FCSO04 Prepare Function (Cancel Sales Order) 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 dpvmsrfc02 fcso04 prepare FM, simply by entering the name DPVMSRFC02_FCSO04_PREPARE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DPVMSRFC02
Program Name: SAPLDPVMSRFC02
Main Program: SAPLDPVMSRFC02
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DPVMSRFC02_FCSO04_PREPARE 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 'DPVMSRFC02_FCSO04_PREPARE'"VMS DP : FCSO04 Prepare Function (Cancel Sales Order).
EXPORTING
IS_INCOMING_FUNCTION = "VMS DP : Function data (incl. description)
IS_CURRENT_FUNCTION = "VMS DP : Function data (incl. description)
* IV_XCALLEDBYEXECUTE = "Single-Character Flag
IMPORTING
EV_VBELN = "Sales and Distribution Document Number
EV_UPD_TMSTMP = "UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)
CHANGING
CT_VLCDIAVEHI = "VELO: Table Type for VLCDIAVEHI
CS_VLCACTDATA = "VELO: Transfer Structure for Actions (Header and Items)
* CT_VLCBAPICU = "Contains the configuration of several vehicles
* CT_VLCGUIDCUOBJ = "VELO : Table with GUIDs and cuobjs
CT_RETURN = "Return parameter table
IMPORTING Parameters details for DPVMSRFC02_FCSO04_PREPARE
IS_INCOMING_FUNCTION - VMS DP : Function data (incl. description)
Data type: DPVMS_FUNCDATAOptional: No
Call by Reference: No ( called with pass by value option)
IS_CURRENT_FUNCTION - VMS DP : Function data (incl. description)
Data type: DPVMS_FUNCDATAOptional: No
Call by Reference: No ( called with pass by value option)
IV_XCALLEDBYEXECUTE - Single-Character Flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DPVMSRFC02_FCSO04_PREPARE
EV_VBELN - Sales and Distribution Document Number
Data type: VBELNOptional: No
Call by Reference: No ( called with pass by value option)
EV_UPD_TMSTMP - UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun)
Data type: TIMESTAMPLOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for DPVMSRFC02_FCSO04_PREPARE
CT_VLCDIAVEHI - VELO: Table Type for VLCDIAVEHI
Data type: VLCDIAVEHI_TOptional: No
Call by Reference: No ( called with pass by value option)
CS_VLCACTDATA - VELO: Transfer Structure for Actions (Header and Items)
Data type: VLCACTDATAOptional: No
Call by Reference: No ( called with pass by value option)
CT_VLCBAPICU - Contains the configuration of several vehicles
Data type: VLCBAPICU_TOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_VLCGUIDCUOBJ - VELO : Table with GUIDs and cuobjs
Data type: VLCGUIDCUOBJ_TOptional: Yes
Call by Reference: No ( called with pass by value option)
CT_RETURN - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DPVMSRFC02_FCSO04_PREPARE 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_ev_vbeln | TYPE VBELN, " | |||
| lv_ct_vlcdiavehi | TYPE VLCDIAVEHI_T, " | |||
| lv_is_incoming_function | TYPE DPVMS_FUNCDATA, " | |||
| lv_cs_vlcactdata | TYPE VLCACTDATA, " | |||
| lv_ev_upd_tmstmp | TYPE TIMESTAMPL, " | |||
| lv_is_current_function | TYPE DPVMS_FUNCDATA, " | |||
| lv_ct_vlcbapicu | TYPE VLCBAPICU_T, " | |||
| lv_iv_xcalledbyexecute | TYPE CHAR1, " | |||
| lv_ct_vlcguidcuobj | TYPE VLCGUIDCUOBJ_T, " | |||
| lv_ct_return | TYPE BAPIRET2_T. " |
|   CALL FUNCTION 'DPVMSRFC02_FCSO04_PREPARE' "VMS DP : FCSO04 Prepare Function (Cancel Sales Order) |
| EXPORTING | ||
| IS_INCOMING_FUNCTION | = lv_is_incoming_function | |
| IS_CURRENT_FUNCTION | = lv_is_current_function | |
| IV_XCALLEDBYEXECUTE | = lv_iv_xcalledbyexecute | |
| IMPORTING | ||
| EV_VBELN | = lv_ev_vbeln | |
| EV_UPD_TMSTMP | = lv_ev_upd_tmstmp | |
| CHANGING | ||
| CT_VLCDIAVEHI | = lv_ct_vlcdiavehi | |
| CS_VLCACTDATA | = lv_cs_vlcactdata | |
| CT_VLCBAPICU | = lv_ct_vlcbapicu | |
| CT_VLCGUIDCUOBJ | = lv_ct_vlcguidcuobj | |
| CT_RETURN | = lv_ct_return | |
| . " DPVMSRFC02_FCSO04_PREPARE | ||
ABAP code using 7.40 inline data declarations to call FM DPVMSRFC02_FCSO04_PREPARE
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