SAP VELO40_GETDATA Function Module for Function module to collect the updated data
VELO40_GETDATA is a standard velo40 getdata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function module to collect the updated data 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 velo40 getdata FM, simply by entering the name VELO40_GETDATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: VELO40
Program Name: SAPLVELO40
Main Program: SAPLVELO40
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 2

Function VELO40_GETDATA 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 'VELO40_GETDATA'"Function module to collect the updated data.
EXPORTING
IV_ACTION = "Action
* IS_VLCACTDATA = "VELO: Transfer Structure for Actions (Header and Items)
IT_VLCDIAVEHI = "VELO: Dialog Structure for Vehicles
IMPORTING Parameters details for VELO40_GETDATA
IV_ACTION - Action
Data type: VLC_ACTIONOptional: No
Call by Reference: No ( called with pass by value option)
IS_VLCACTDATA - VELO: Transfer Structure for Actions (Header and Items)
Data type: VLCACTDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_VLCDIAVEHI - VELO: Dialog Structure for Vehicles
Data type: VLCDIAVEHI_TOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VELO40_GETDATA 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_iv_action | TYPE VLC_ACTION, " | |||
| lv_is_vlcactdata | TYPE VLCACTDATA, " | |||
| lv_it_vlcdiavehi | TYPE VLCDIAVEHI_T. " |
|   CALL FUNCTION 'VELO40_GETDATA' "Function module to collect the updated data |
| EXPORTING | ||
| IV_ACTION | = lv_iv_action | |
| IS_VLCACTDATA | = lv_is_vlcactdata | |
| IT_VLCDIAVEHI | = lv_it_vlcdiavehi | |
| . " VELO40_GETDATA | ||
ABAP code using 7.40 inline data declarations to call FM VELO40_GETDATA
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