Used-Vehicle Scenario

Use

Vehicles can be taken in part exchange/as a trade-in or bought back more than once.

You can find further information in the documentation for Materials Management under Purchase Orders (MM-PUR-PO) .

Note Note

If you trade-in/buy-back using a one-time vendor, you cannot post the inbound invoice with action INIV but only with the SAP standard transaction.

End of the note.

The following graphics illustrate the three possible used-vehicle process scenarios:

Scenario 1:

This graphic is explained in the accompanying text.

This an independent process with vehicle model specially used for the used vehicle scenario. Independent process means that the used vehicle process is isolated from the sales and distribution process of new vehicles and is represented in an own VMS matrix. The used vehicle record can be created in reference to a new vehicle and configuration can be mapped automatically.

Scenario 2:

This graphic is explained in the accompanying text.

This is an independent process with a used vehicle model, but without a reference to a new vehicle. Configuration can be entered manually.

Scenario 3:

This graphic is explained in the accompanying text.

The used vehicle process directly follows the sales and distribution process of new vehicles. The same matrix is used. The vehicle that is sold as a new vehicle is bought back and resold as a used vehicle.

Features

(I) signifies an Interlinking Action .

Action	Description	Prerequisites	What does the action do?	Notes
BBDF	Define/change buy-back conditions		This action allows you to define buy-back conditions, such as: Planned buy-back date Buy-back price Short and long text describing other conditions	This action can normally be executed after creation of the sales order for the new vehicle.
CREA	Create vehicle (with valuation)			See: Creating Vehicles When you trade-in vehicles that you have already sold as an importer, you do not have to perform this action. If a used-vehicle model is chosen, this action allows you to specify the original vehicle and, provided a mapping has been defined, map the original configuration to the used-vehicle configuration.
CRUV	Create used vehicle	Configurable material, configuration profile, class Model defined in transaction code veloum	This action creates the vehicle based on a used-vehicle model	This action supports automatic mapping of the configurations. The used-vehicle indicator is automatically switched.
UVSW	Switch “used vehicle” flag		Switches the flag for marking the vehicle as a used one on/off	You can use this action when your used-vehicle process follows the new- vehicle process in your matrix. In other words, when the vehicle has been created for the new-vehicle process and the same vehicle record is being used for the used-vehicle process.
POEU	Trade-in	Vehicle	Creates a normal purchase order for the vehicles In contrast to action ORD1 Create Purchase Order , the price and the vendor (also one-time vendor) have to be entered manually in the interface	A purchasing info record should not exist for the vendor. If a record does exists, you must ensure (in the pricing procedure) that the price entered manually has priority over and above the price in the purchasing info record. You can access a calculation sheet in this action, provided the former has been created for the vehicle. In this case, the fields Net Price and Currency are disabled. Their values are taken from the calculation sheet.
GORE	Create goods receipt			See: Goods Movements: GI, GR
CRPU (I)	Create and trade-in vehicle		CREA + POEU	This action can only be performed for exactly one vehicle. Actions CREA, POEU and CRPU are usually executed during buy-back. You can also execute them when buy-back conditions are defined (in other words, when the vehicle is sold) if you prefer to have the purchase order in advance, for example, for planning purposes.
RVAL	Revaluation (see also: Creating Vehicles , action RVAL)		Changes the vehicle value in the valuation segment of the material master.	If a used-vehicle model is chosen, you can access the pricing procedure and edit the corresponding section. The Debit/Credit Amount field is disabled. Its value is calculated from the appropriate section of the calculation sheet.
SPEU	Used vehicle sales: determine price	The vehicle has been returned to the importer’s stock due to trade-ins or returns processing.	Overwrites the gross list price in the vehicle data with the resell price The resale price is a manually fixed price that is independent of the configuration of the vehicle.	If a used-vehicle model is chosen, you can access the pricing procedure and edit the appropriate section. The field Resell Price is disabled. Its value is calculated from the corresponding section of the calculation sheet.
SOEU	Used vehicle sales: create order	The vehicle has already been sold once and has been returned to stock by a trade-in process or returns processing Resale price (action SPEU).	Creates a sales order for the used vehicle and can overwrite the entries for customer, end customer and vehicle usage	This action is a very simplified version of action CUOR Create Sales Order , for which numerous restrictions apply: No returns processing is allowed for sales orders that have been created with SOEU. You cannot make reservations if you are using action SOEU. Sales orders that have been created with action SOEU cannot be changed with action CHCO Change Sales Order but they can be deleted with action DECO Delete Sales Order . You should use a different pricing procedure for pricing than you use for action CUOR. Background: condition type VA00 (variant price) is contained in the pricing procedure fin the case of CUOR, in other words, the prices depend on the configuration during pricing (see also: Creating a Variant Condition for Pricing ). You should not, however, use condition type VA00 for action SOEU since the price is independent of the configuration here and determined manually using action SPEU. This resale price is transferred as condition type PR00 by default. You can define a different condition type for the resale price in BAdI VLC_EXECUTE_ACTION, method DATA_CHANGES_BEFORE_ACTION. You must then write this condition type in VLCACTDATA_CS-KSCHA. If you want to be able to use different pricing procedures for CUOR and SOEU, you should use different document types. Both actions work with document type TA (standard order) by default. You can change the document type in BAdI VLC_EXECUTE_ACTION, method DATA_CHANGES_BEFORE_ACTION. You can enter the document type in VLCACTDATA_CS-AUART.
CSCR	Create calculation sheet for used vehicle	You have defined a calculation sheet profile.	Creates a calculation sheet that is attached to the vehicle.	The calculation sheet can be accessed in the following standard actions: BBDF, POEU, RVAL and SPEU.
CSED	Edit sales order calculation sheet			You can use this action after the sales order has been created for the used-vehicle in order to change the SD order pricing. You can change the item and header pricing in the same way as in transaction VA01 .

Definition of Buy-Back Conditions

When a new vehicle is sold, buy-back conditions are defined. These conditions usually contain:

the buy-back date
the price to be paid if the vehicle is returned on this date

You can also define additional conditions. Generally speaking, these are additional prerequisites for the agreed price. If any of these additional conditions are not met, the price can be reduced (or buy-back can be rejected).

There are three possible situations when a customer initiates buy-back:

The vehicle was sold by this importer and buy-back conditions have been defined at the point of sales of the new vehicle.
The vehicle was sold by this importer but buy-back conditions have not been defined.
The vehicle was not sold by this importer.

In the first case, the price is determined based on the predefined buy-back conditions and the state of the vehicle. In cases 2 and 3, the vehicle price is determined on the whole by current market conditions.

Pricing of Used Vehicles

In contrast to price determination for new vehicles where the configuration of the vehicle plays an important role, the configuration of used vehicles (see below) has only an indirect influence on the price. The base price of used vehicles is usually determined according to the market conditions for that particular model, taking into consideration its age, mileage and several other factors. Additional discounts or surcharges may be applied based on other conditions, for example, special conditions for a particular customer.

Used-Vehicle Calculation Sheet

In order to provide an overview over the entire used-vehicle process and enable tracking of the cost structure for each step of this process, the calculation sheet is integrated in the related actions (for example, actions BBDF, POEU, RVAL and SPEU). The sheet is analogous to the standard SD pricing procedure. Sections of the sheet are assigned in Customizing to the corresponding actions and can therefore be edited only by these actions. You can assign actions to steps in your calculation sheet by using transaction code OVELO30 .

You can map a vehicle model to the calculation sheet profile that you have previously defined in Customizing for the Vehicle Management System (VMS) under Start of the navigation path Control Data Next navigation step Define Calculation Sheet Profile End of the navigation path by using transaction code VELOMCS. If there is no entry for your used-vehicle model, the global parameters from transaction OVELO00are used.

The standard pricing procedure and assignment of its sections to the VMS actions are contained in standard SD Customizing. You can use the standard settings as a copy template to create your own calculation sheet and assignments.

Note Note

You can access the calculation sheet in display mode from the vehicle detail screen.

End of the note.

Configuration of Used Vehicles

Configuration of used vehicles is general, whereas for the new vehicle every option in the configuration is usually defined on a very detailed level (for example, the exterior color can be defined as a tint of red for the new vehicle, whilst for the used vehicle all possible tints are described simply as red).

Used-Vehicle Model

You can define a used-vehicle model by using transaction code VELOUM .

There are two possible options in the used-vehicle process:

Work with the existing original vehicle

In this case you cannot change the configuration of the used vehicle. In other words, the original configuration of the new vehicle is preserved for the used-vehicle process. You can mark this vehicle as a used vehicle by executing action UVSW ( Switch “used vehicle” flag) in order to differentiate between vehicles that are new and vehicles that are used.
Work with a special model with a special “used-vehicle” configuration

Even if the vehicle object for the original new vehicle has already been created in the system, a new vehicle object has to be created in this case. New used-vehicle objects have a more generic configuration. You can maintain the link between new and used-vehicle objects and the mapping of the configurations in action CRUV.

You can use different number ranges for used-vehicle models. You can assign number ranges to vehicle models by using transaction code VELONR , provided that you have maintained your used-vehicle model by using transaction code VELOMNR.

Mapping Between the New Vehicle Configuration and the Used-Vehicle Configuration

Mapping of models

You can use transaction code VELOCM to define a mapping between a new-vehicle configuration and a used-vehicle configuration. The table below shows an example of such a mapping:

Source configuration	Source characteristic	Source Value	Assignment method	Destination configuration	Destination characteristic	Destination value
New vehicle configuration	Exterior color	Lava red	Directly in transaction VELOCM	Used vehicle configuration	Exterior color	Red
New vehicle configuration	Exterior color	Fire red	Directly in transaction VELOCM	Used vehicle configuration	Exterior color	Red
New vehicle configuration	Exterior color	Dark red	Directly in transaction VELOCM	Used vehicle configuration	Exterior color	Red
New vehicle configuration	Characteristic N		BAdI VLC_USED_VEHICLE	Used vehicle configuration	Characteristic M
….	…	….	….	….	….	…..

This configuration mapping can be performed by using the appropriate function in action CRUV. It also supports a partial mapping. In this case, you have to enter the rest of the configuration manually. Generally speaking, you can also map the characteristic values of one configuration to the next. In cases where a simple one-to-one mapping is not possible or in cases where some sort of a conversion is required, you can use BAdI VLC_USED_VEHICLE.

Mapping of characteristics

Generally speaking, the new-vehicle model is mapped to the characteristic of the used-vehicle configuration (for example, characteristic MODEL with the possible values “VW Golf 3”, “VW Golf 4”, “Audi A4” ). You can use transaction code VELOMMAP to do this. The table below shows an example of such a mapping:

Model	Destination characteristic	Destination value
VW Golf 3	Model	VW Golf 3
VW Golf 4	Model	VW Golf 4
Audi A4	Model	Audi A4