SAP BAPI_VEHICLE_CHANGE_MULTIPLE2 Function Module for Change One or More Vehicles









BAPI_VEHICLE_CHANGE_MULTIPLE2 is a standard bapi vehicle change multiple2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change One or More Vehicles 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 bapi vehicle change multiple2 FM, simply by entering the name BAPI_VEHICLE_CHANGE_MULTIPLE2 into the relevant SAP transaction such as SE37 or SE38.

Function Group: VELO19
Program Name: SAPLVELO19
Main Program: SAPLVELO19
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_VEHICLE_CHANGE_MULTIPLE2 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 'BAPI_VEHICLE_CHANGE_MULTIPLE2'"Change One or More Vehicles
  EXPORTING
   VEHICLEACTION =  "BAPI Data Element for BAPI of Vehicle Management System
   VEHIACTIONDATA_HEAD =  "Transfer Structure for Actions (Header Data)
*  REQUESTEDTABLEX =  "List of parameters to be issued
*  VEHIACTIONDATA_HEADX =  "Transfer Structure for Actions (Header Data)
*  VEHIACTIONDATA_ITEMX =  "Transfer Structure for Actions (Item Data)
   VEHICLE_ID_TYPE =  "Identifying Number for Multiple-BAPI

 IMPORTING
   CHANGED_VEHIACTIONDATA_HEAD =  "Transfer Structure for Actions (Header Data)

TABLES
   VEHIACTIONDATA_ITEM =  "Transfer Structure for Actions (Header Data)
*  CHANGED_CONFIG_DATA =  "CU: Configuration Data
*  CHANGED_CONFIG_INSTANCE =  "Instances of Several Configurations
*  CHANGED_CONFIG_CHARSVAL =  "Characteristic Values of Several Configurations
*  EXTENSIONOUT =  "Reference Structure for BAPI Parameters ExtensionIn / ExtensionOut
*  RETURN =  "Return Parameters
*  CONFIG_VARCONDNKEYS =  "Variant Condition Keys in Configurations
*  CHANGED_CONFIG_VARCONDNKEYS =  "Variant Condition Keys in Configurations
*  VEHICLE_DATA =  "
   CONFIG_REFERENCES =  "Reference between Vehicle GUID and Config ID
   CONFIG_DATA =  "Configuration Data of Vehicle
   CONFIG_INSTANCES =  "Instances of Several Configurations
   CONFIG_CHARSVALUES =  "Characteristic Values of Several Configurations
*  VEHICLE_QUALIFIERS =  "Structure for Creating/Changing Addnl Vehicle Attributes
*  EXTENSIONIN =  "Reference Structure for BAPI Parameters ExtensionIn / ExtensionOut
*  CHANGED_VEHIACTIONDATA_ITEM =  "Transfer Structure for Actions (Header Data)
*  CHANGED_VEHICLE =  "Main Attributes of Created Vehicle
.



IMPORTING Parameters details for BAPI_VEHICLE_CHANGE_MULTIPLE2

VEHICLEACTION - BAPI Data Element for BAPI of Vehicle Management System

Data type: BAPIVEHIACTION-VEHICLEACTION
Optional: No
Call by Reference: No ( called with pass by value option)

VEHIACTIONDATA_HEAD - Transfer Structure for Actions (Header Data)

Data type: BAPIVEHIACTIONDATA_HEAD
Optional: No
Call by Reference: No ( called with pass by value option)

REQUESTEDTABLEX - List of parameters to be issued

Data type: BAPIREQUESTEDTABLESX
Optional: Yes
Call by Reference: No ( called with pass by value option)

VEHIACTIONDATA_HEADX - Transfer Structure for Actions (Header Data)

Data type: BAPIVEHIACTIONDATA_HEADX
Optional: Yes
Call by Reference: No ( called with pass by value option)

VEHIACTIONDATA_ITEMX - Transfer Structure for Actions (Item Data)

Data type: BAPIVEHIACTIONDATA_ITEMX
Optional: Yes
Call by Reference: No ( called with pass by value option)

VEHICLE_ID_TYPE - Identifying Number for Multiple-BAPI

Data type: BAPIVEHICLE_ID_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_VEHICLE_CHANGE_MULTIPLE2

CHANGED_VEHIACTIONDATA_HEAD - Transfer Structure for Actions (Header Data)

Data type: BAPIVEHIACTIONDATA_HEAD
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BAPI_VEHICLE_CHANGE_MULTIPLE2

VEHIACTIONDATA_ITEM - Transfer Structure for Actions (Header Data)

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

CHANGED_CONFIG_DATA - CU: Configuration Data

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

CHANGED_CONFIG_INSTANCE - Instances of Several Configurations

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

CHANGED_CONFIG_CHARSVAL - Characteristic Values of Several Configurations

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

EXTENSIONOUT - Reference Structure for BAPI Parameters ExtensionIn / ExtensionOut

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

RETURN - Return Parameters

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

CONFIG_VARCONDNKEYS - Variant Condition Keys in Configurations

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

CHANGED_CONFIG_VARCONDNKEYS - Variant Condition Keys in Configurations

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

VEHICLE_DATA -

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

CONFIG_REFERENCES - Reference between Vehicle GUID and Config ID

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

CONFIG_DATA - Configuration Data of Vehicle

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

CONFIG_INSTANCES - Instances of Several Configurations

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

CONFIG_CHARSVALUES - Characteristic Values of Several Configurations

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

VEHICLE_QUALIFIERS - Structure for Creating/Changing Addnl Vehicle Attributes

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

EXTENSIONIN - Reference Structure for BAPI Parameters ExtensionIn / ExtensionOut

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

CHANGED_VEHIACTIONDATA_ITEM - Transfer Structure for Actions (Header Data)

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

CHANGED_VEHICLE - Main Attributes of Created Vehicle

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

Copy and paste ABAP code example for BAPI_VEHICLE_CHANGE_MULTIPLE2 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_vehicleaction  TYPE BAPIVEHIACTION-VEHICLEACTION, "   
lt_vehiactiondata_item  TYPE STANDARD TABLE OF BAPIVEHIACTIONDATA_ITEM, "   
lv_changed_vehiactiondata_head  TYPE BAPIVEHIACTIONDATA_HEAD, "   
lt_changed_config_data  TYPE STANDARD TABLE OF BAPICUCFG, "   
lt_changed_config_instance  TYPE STANDARD TABLE OF BAPICUINS, "   
lt_changed_config_charsval  TYPE STANDARD TABLE OF BAPICUVAL, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lt_config_varcondnkeys  TYPE STANDARD TABLE OF BAPICUVK, "   
lt_changed_config_varcondnkeys  TYPE STANDARD TABLE OF BAPICUVK, "   
lt_vehicle_data  TYPE STANDARD TABLE OF BAPIVEHICLE, "   
lt_config_references  TYPE STANDARD TABLE OF BAPICONFIG_REFERENCES, "   
lv_vehiactiondata_head  TYPE BAPIVEHIACTIONDATA_HEAD, "   
lt_config_data  TYPE STANDARD TABLE OF BAPICUCFG, "   
lv_requestedtablex  TYPE BAPIREQUESTEDTABLESX, "   
lt_config_instances  TYPE STANDARD TABLE OF BAPICUINS, "   
lv_vehiactiondata_headx  TYPE BAPIVEHIACTIONDATA_HEADX, "   
lt_config_charsvalues  TYPE STANDARD TABLE OF BAPICUVAL, "   
lv_vehiactiondata_itemx  TYPE BAPIVEHIACTIONDATA_ITEMX, "   
lv_vehicle_id_type  TYPE BAPIVEHICLE_ID_TYPE, "   
lt_vehicle_qualifiers  TYPE STANDARD TABLE OF BAPIVEHICLEQUALIFIERS, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_changed_vehiactiondata_item  TYPE STANDARD TABLE OF BAPIVEHIACTIONDATA_ITEM, "   
lt_changed_vehicle  TYPE STANDARD TABLE OF BAPIVEHICLE. "   

  CALL FUNCTION 'BAPI_VEHICLE_CHANGE_MULTIPLE2'  "Change One or More Vehicles
    EXPORTING
         VEHICLEACTION = lv_vehicleaction
         VEHIACTIONDATA_HEAD = lv_vehiactiondata_head
         REQUESTEDTABLEX = lv_requestedtablex
         VEHIACTIONDATA_HEADX = lv_vehiactiondata_headx
         VEHIACTIONDATA_ITEMX = lv_vehiactiondata_itemx
         VEHICLE_ID_TYPE = lv_vehicle_id_type
    IMPORTING
         CHANGED_VEHIACTIONDATA_HEAD = lv_changed_vehiactiondata_head
    TABLES
         VEHIACTIONDATA_ITEM = lt_vehiactiondata_item
         CHANGED_CONFIG_DATA = lt_changed_config_data
         CHANGED_CONFIG_INSTANCE = lt_changed_config_instance
         CHANGED_CONFIG_CHARSVAL = lt_changed_config_charsval
         EXTENSIONOUT = lt_extensionout
         RETURN = lt_return
         CONFIG_VARCONDNKEYS = lt_config_varcondnkeys
         CHANGED_CONFIG_VARCONDNKEYS = lt_changed_config_varcondnkeys
         VEHICLE_DATA = lt_vehicle_data
         CONFIG_REFERENCES = lt_config_references
         CONFIG_DATA = lt_config_data
         CONFIG_INSTANCES = lt_config_instances
         CONFIG_CHARSVALUES = lt_config_charsvalues
         VEHICLE_QUALIFIERS = lt_vehicle_qualifiers
         EXTENSIONIN = lt_extensionin
         CHANGED_VEHIACTIONDATA_ITEM = lt_changed_vehiactiondata_item
         CHANGED_VEHICLE = lt_changed_vehicle
. " BAPI_VEHICLE_CHANGE_MULTIPLE2




ABAP code using 7.40 inline data declarations to call FM BAPI_VEHICLE_CHANGE_MULTIPLE2

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 VEHICLEACTION FROM BAPIVEHIACTION INTO @DATA(ld_vehicleaction).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!