An object in the SAP system that represents an individual vehicle. Technically, a VSS vehicle consists of the VMS vehicle object and the individual object.
In Vehicle Sales and Service (VSS), the vehicle can be either in the dealer's stock and available as unsold and without any assignment to a customer, or assigned to a business partner or customer.
For more information about the VMS vehicle, see component Vehicle Management System (IS-A-VMS) under Vehicle. For more information about individual objects, see SAP Customer Relationship Management (CRM) under Individual Objects.

You enter this object and its data in the vehicle master and use it for handling business processes in service and warranty as well as for vehicle sales. You can use the vehicle search to help you do this.
You can execute actions for a vehicle, such as Change Vehicle and Create Goods Receipt. The system always displays the actions that are possible for the current vehicle status. For more information about vehicle actions that can be performed in VSS, see Details for Vehicle Actions .

Note

Using various function modules, you can adapt the VSS vehicles and use functions for the VSS vehicles. For more information about function modules, see Customizing for Vehicle Sales and Service (VSS) under RFC Interfaces > Function Modules > RFC VSS Vehicle.

Structure

In Customizing for VSS under Vehicle > Vehicle Master > Navigation in Vehicle Master (SAP GUI), you can define which of the following data for the object Vehicle is displayed:

Data Overview	Here you can display all the important vehicle data in summarized form. When you enter the mileage for the vehicle in the vehicle order, the system automatically updates the data in the appropriate vehicle master record.
SAP Internal Technical Data	The underlying technical VSS vehicle data for the VMS vehicle, the individual object, and the vehicle model are displayed here. This data helps SAP support find errors more easily.
VMS Vehicle History	The actions carried out for the vehicle including date, time, primary status, and secondary status are documented here. The vehicle history shows which user performed which action, at what time, and which status change resulted. You can display the document that is created from an action (see Action Control During Vehicle Processing and Execution of Vehicle Actions).
VMS General Data	Important vehicle data, such as vehicle identification number (VIN), availability, vehicle location, and primary and secondary status, is displayed here.
VMS Qualifier	You can store additional data that is neither checked nor subject to any particular logic, for example, the name of the forwarding agent. For more information about additional data, see Customizing for Logistics Execution under Vehicle Management System (IS-A-VMS) Enhancements Define Additional Data for Vehicle .
Model Data	Important vehicle model data is entered here such as the sales code and service code for the vehicle. The system copies the model data from the vehicle model. This data can be changed for the vehicle.
Vehicle Data	You can enter important additional vehicle data mainly for service such as the labor value main type and price group, for example. For a vehicle or service order, the system copies the price group from the vehicle data.
Partners	You can assign customers appropriate partner functions. When you assign a customer to the vehicle, the system assigns this customer as sold-to party. The system assigns further partner functions with standard partner determination functions that are triggered by the action Assign Customer. Furthermore, you can add or remove partners manually. When you create an order for a vehicle, the system copies the partner data defined for the vehicle as default values in the order. The Owner and Driver partner functions are relevant for the vehicle. The driver information is required if there is a different driver for the vehicle than the customer. You can use this function, for example, for fleet customers. The system determines the Owner information based on the billing document. The owner is the legal owner of the vehicle.
Registration	Here you can enter registration data such as the type and date of vehicle registration, for example. The system updates the mileage and the owner. When you create an order for the vehicle, the system copies the license plate number and the mileage of the current entry to the order header. You can overwrite the mileage in the order.
Warranty	You can define warranty conditions for the vehicle. If you create a vehicle, the system copies the valid warranty conditions according to country, division, and vehicle model, which you can later change. The system displays the warranty data in the order for the vehicle.
Options	You can assign features to the vehicle, which you can group into features classes and features categories. The system copies the standard features from the vehicle model. You can add further features classes in the vehicle master record. To do this, you can use the input help that stems from the entries made in the vehicle model, or enter other features keys. When you create a vehicle quotation or a vehicle order, the system copies the vehicle and the features with the appropriate prices as items to the order.
Keys	You can enter additional keys for the vehicle, for example the radio code, the number of the title of auto, and the number of the vehicle key. You can define the key types in Customizing for VSS under Vehicle General Data Define Key Type .
Planned Maintenance Intervals	You can define maintenance and service intervals, for example, for M.O.T. tests, exhaust emission tests and general inspections. The system displays this data in the order for the vehicle. When you enter or change the maintenance and service intervals for the vehicle in the vehicle order, the standard system automatically updates the data in the appropriate vehicle master record. You can define the service types in Customizing for VSS under Vehicle General Data Define Service Type .
Recalls	The recall contains information about the technical fault and how to repair it (for example, what tasks the mechanic has to perform, which parts are required, and repair instructions).
Texts	Descriptive texts that can be assigned to and printed out with documents.
Vehicle Change Document	There is a standard functionality that allows you to track changes made on vehicle tables, for example, who changed the value in the table, when, and what the previous value was. There are VMS change document functions for tables VLCVEHICLE (VELO: Vehicle) and VLCADDDATA (VELO: Qualifier Data for Vehicle) that are combined with the history data for the individual object.
Vehicle Prices	Here you can enter the estimated and aimed purchasing and sales prices.
Service Contracts	You can see all the service contracts and service items that are assigned to a vehicle. You can also navigate directly to the service contracts created for this vehicle (see Display of Service Contracts in Vehicle Data).
Deferred Work	You can see all the orders with order type Service Deferred Work (2201) that exist for a vehicle (see Order Processing for Additional Work and Deferred Work). You can also navigate directly to each order.
Additional Cost Overview	The system displays details of additional costs assigned to the vehicle (see Vehicle Additional Costs).
Service History	You can see a vehicle’s service history and navigate to each service order from the vehicle service history (see Vehicle Service History).
VMS Configuration	You can see this view only if you enabled it by the VMS-VSS integration. In this case it displays the material configuration of the VMS vehicle. For more information, see Enable VMS Vehicle for VSS.
Financing/Leasing	You can enter and update financing and leasing information. You must first make the appropriate settings in Customizing for Vehicle Sales and Service under Vehicle General Data Define Financing and Leasing .
Condition	You can specify data that describes the condition of the vehicle, for example if the paint is Good as New or Poor. Additionally, you can see the latest vehicle damage report. If there is more than one vehicle damage report the system displays the latest one with its description text and item overview.
Generic Options	When you create a vehicle, the system determines the generic options based on the standard features. You select generic options to specify for example the color type or the gearbox type for the vehicle. You can use the generic options in the extended vehicle search. First you have to make the appropriate settings on the SAP Easy Access screen under Vehicle Sales and Service Master Data Vehicle Model Edit Generic Options for Features .

You can use individual objects to enhance the vehicle master with additional vehicle data, in other words, with new screens and new fields.

Note

In the vehicle, you can use the Documents pushbutton to store documents Document Managment System (DMS). In addition, you can see documents, which have been attached to the vehicle in the Vehicle Management System (VMS). In Customizing for VSS under Vehicle > Business Add-Ins (BAdI) you can change and filter VMS attachments in VSS with the Business Add-In BAdI: Change and Filter of VMS Attachments in VSS Vehicle (/DBE/BADI_VEHICLE_ATTACHMENTS).
For more information, see Enable VMS Vehicle for VSS.

The following Business Add-Ins (BAdIs) are available for the vehicle in Customizing for VSS under Vehicle > Business Add-Ins (BAdIs):

Control Vehicle Search UIs
Control Vehicle Master APIs
Change and Filter of VMS Attachments in VSS Vehicle
Control Vehicle Order
Control Maintenance and Service Intervals for Vehicle
Control Vehicle Master UIs
Control Vehicle Model Master APIs
Control Vehicle Model Master UIs
Control Vehicle Model Master UI Defaults
Control Reading of Control Values
Control Vehicle Actions (VMS)
Control Vehicle Warranties
Control Replacement Vehicle Search
Dependency Check for Multiple Vehicles

Integration

In order to create a vehicle in the standard system, you first have to create a vehicle model.
You can use BAdI: Control Vehicle Master APIs (BAdI /DBE/BADI_VEHICLE_API) to copy default data from the vehicle model master to the vehicle master when you create a new vehicle. If you do not wish to use the default implementation of the BAdI, you can create a customer implementation.
You can also create a vehicle without a vehicle model. If you want to do this, there must be a material in the material master for this purpose. When you create the vehicle, you have to enter the material instead of the model, or you can implement your own logic for material determination in BAdI: Control Vehicle Master APIs.
If you create an order from the vehicle master, the vehicle data is copied to this order. To do this, implement BAdI: Control Vehicle Order (/DBE/VEHICLE_SALES).

Browser not supported