SAP VELO04_READ_VEHICLES Function Module for VELO : Selektieren von Fahrzeugen









VELO04_READ_VEHICLES is a standard velo04 read vehicles SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for VELO : Selektieren von Fahrzeugen 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 velo04 read vehicles FM, simply by entering the name VELO04_READ_VEHICLES into the relevant SAP transaction such as SE37 or SE38.

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



Function VELO04_READ_VEHICLES 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 'VELO04_READ_VEHICLES'"VELO : Selektieren von Fahrzeugen
TABLES
* SEL_VGUID_IT = "
* SEL_MMTSP_IT = "
* SEL_SDSTA_IT = "
* SEL_SDTSP_IT = "
* SEL_PSTSP_IT = "
* SEL_PDTSP_IT = "
* SEL_VHCEX_IT = "
VLCVEHICLE_ET = "VELO : Fahrzeugdaten
* SEL_VHCLE_IT = "
* SEL_VHVIN_IT = "
* SEL_MATNR_IT = "
* SEL_LIFNR_IT = "
* SEL_KUNNR_IT = "
* SEL_AVAIL_IT = "
* SEL_LOCTN_IT = "
* SEL_MMSTA_IT = "

EXCEPTIONS
NO_VEHICLE_FOUND = 1
.



TABLES Parameters details for VELO04_READ_VEHICLES

SEL_VGUID_IT -

Data type: VLCH_SEL_VGUID_PT
Optional: Yes
Call by Reference: Yes

SEL_MMTSP_IT -

Data type: VLCH_SEL_MMTSP_PT
Optional: Yes
Call by Reference: Yes

SEL_SDSTA_IT -

Data type: VLCH_SEL_SDSTA_PT
Optional: Yes
Call by Reference: Yes

SEL_SDTSP_IT -

Data type: VLCH_SEL_SDTSP_PT
Optional: Yes
Call by Reference: Yes

SEL_PSTSP_IT -

Data type: VLCH_SEL_PSTSP_PT
Optional: Yes
Call by Reference: Yes

SEL_PDTSP_IT -

Data type: VLCH_SEL_PDTSP_PT
Optional: Yes
Call by Reference: Yes

SEL_VHCEX_IT -

Data type: VLCH_SEL_VHCEX_PT
Optional: Yes
Call by Reference: Yes

VLCVEHICLE_ET - VELO : Fahrzeugdaten

Data type: VLCVEHICLE
Optional: No
Call by Reference: Yes

SEL_VHCLE_IT -

Data type: VLCH_SEL_VHCLE_PT
Optional: Yes
Call by Reference: Yes

SEL_VHVIN_IT -

Data type: VLCH_SEL_VHVIN_PT
Optional: Yes
Call by Reference: Yes

SEL_MATNR_IT -

Data type: VLCH_SEL_MATNR_PT
Optional: Yes
Call by Reference: Yes

SEL_LIFNR_IT -

Data type: VLCH_SEL_LIFNR_PT
Optional: Yes
Call by Reference: Yes

SEL_KUNNR_IT -

Data type: VLCH_SEL_KUNNR_PT
Optional: Yes
Call by Reference: Yes

SEL_AVAIL_IT -

Data type: VLCH_SEL_AVAIL_PT
Optional: Yes
Call by Reference: Yes

SEL_LOCTN_IT -

Data type: VLCH_SEL_LOCTN_PT
Optional: Yes
Call by Reference: Yes

SEL_MMSTA_IT -

Data type: VLCH_SEL_MMSTA_PT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NO_VEHICLE_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VELO04_READ_VEHICLES 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:
lt_sel_vguid_it  TYPE STANDARD TABLE OF VLCH_SEL_VGUID_PT, "   
lv_no_vehicle_found  TYPE VLCH_SEL_VGUID_PT, "   
lt_sel_mmtsp_it  TYPE STANDARD TABLE OF VLCH_SEL_MMTSP_PT, "   
lt_sel_sdsta_it  TYPE STANDARD TABLE OF VLCH_SEL_SDSTA_PT, "   
lt_sel_sdtsp_it  TYPE STANDARD TABLE OF VLCH_SEL_SDTSP_PT, "   
lt_sel_pstsp_it  TYPE STANDARD TABLE OF VLCH_SEL_PSTSP_PT, "   
lt_sel_pdtsp_it  TYPE STANDARD TABLE OF VLCH_SEL_PDTSP_PT, "   
lt_sel_vhcex_it  TYPE STANDARD TABLE OF VLCH_SEL_VHCEX_PT, "   
lt_vlcvehicle_et  TYPE STANDARD TABLE OF VLCVEHICLE, "   
lt_sel_vhcle_it  TYPE STANDARD TABLE OF VLCH_SEL_VHCLE_PT, "   
lt_sel_vhvin_it  TYPE STANDARD TABLE OF VLCH_SEL_VHVIN_PT, "   
lt_sel_matnr_it  TYPE STANDARD TABLE OF VLCH_SEL_MATNR_PT, "   
lt_sel_lifnr_it  TYPE STANDARD TABLE OF VLCH_SEL_LIFNR_PT, "   
lt_sel_kunnr_it  TYPE STANDARD TABLE OF VLCH_SEL_KUNNR_PT, "   
lt_sel_avail_it  TYPE STANDARD TABLE OF VLCH_SEL_AVAIL_PT, "   
lt_sel_loctn_it  TYPE STANDARD TABLE OF VLCH_SEL_LOCTN_PT, "   
lt_sel_mmsta_it  TYPE STANDARD TABLE OF VLCH_SEL_MMSTA_PT. "   

  CALL FUNCTION 'VELO04_READ_VEHICLES'  "VELO : Selektieren von Fahrzeugen
    TABLES
         SEL_VGUID_IT = lt_sel_vguid_it
         SEL_MMTSP_IT = lt_sel_mmtsp_it
         SEL_SDSTA_IT = lt_sel_sdsta_it
         SEL_SDTSP_IT = lt_sel_sdtsp_it
         SEL_PSTSP_IT = lt_sel_pstsp_it
         SEL_PDTSP_IT = lt_sel_pdtsp_it
         SEL_VHCEX_IT = lt_sel_vhcex_it
         VLCVEHICLE_ET = lt_vlcvehicle_et
         SEL_VHCLE_IT = lt_sel_vhcle_it
         SEL_VHVIN_IT = lt_sel_vhvin_it
         SEL_MATNR_IT = lt_sel_matnr_it
         SEL_LIFNR_IT = lt_sel_lifnr_it
         SEL_KUNNR_IT = lt_sel_kunnr_it
         SEL_AVAIL_IT = lt_sel_avail_it
         SEL_LOCTN_IT = lt_sel_loctn_it
         SEL_MMSTA_IT = lt_sel_mmsta_it
    EXCEPTIONS
        NO_VEHICLE_FOUND = 1
. " VELO04_READ_VEHICLES




ABAP code using 7.40 inline data declarations to call FM VELO04_READ_VEHICLES

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!