Below is a description of how action QTIP (Prepare Repurchase) changes and/or deletes vehicle data. There are two cases.
A)
A repurchased vehicle might already exist in the system as it might have previously been sold as a new vehicle. In this case, you do not have to create a new vehicle record. Instead, action QTIP converts the existing new vehicle to a used vehicle.
This action deletes and changes the vehicle data as follows:

The vehicle business transaction type is changed from NEC (New Vehicle) to USC (Used Vehicle) in the vehicle master table according to the settings in the vehicle life cycle customizing (see Vehicle Life Cycle Management).
Deletes organizational vehicle sales data (sales organization, distribution channel) from table VLCVEHICLE (VELO: Vehicle). This data is reassigned when the vehicle is assigned to a customer again by using the vehicle action QACU (Assign Customer VSS).
Deletes the vehicle customer number and the vehicle partner data. This data is also reassigned by action QACU (Assign Customer VSS).
Changes the valuation class of the vehicle from New to Used.
Does not automatically change or delete the vehicle registration number or any existing vehicle registration history records. You should create a new registration history record of registration type 02 (deregistration) when the vehicle is repurchased.
Does not clear the Vehicle Usage field in the data overview of the vehicle master. The field is automatically filled by a VMS action in according to your Customizing settings.
Allows you to change the Margin Taxation field.
Clears the vendor as the last vendor (importer or manufacturer in the case of a new vehicle).
Clears the Sales Date field.
Vehicle options with prices might have been used in the original new vehicle purchase order sent to the OEM. As the vehicle options are not relevant for used vehicle purchase pricing, the flag indicating non-relevance to the purchase order is set for such options. Similarly, the new vehicle options and prices are also irrelevant for the sales order. Therefore, sales-order-relevancy flags are also set accordingly.

B)
A vehicle that is repurchased as a used vehicle may already exist as a used vehicle in the system. Even if the vehicle is already used, some additional steps are still required to prepare it for repurchase. Some of the steps required in the new to used transformation are not necessary. The list below mentions the differences and/or similarities:

Business transaction type remains USC
Organizational data is deleted
Partner data is deleted
The valuation class remains the same because the vehicle is already a used vehicle.
Vehicle registration data: as above
Vehicle usage: as above
Margin taxation: as above
Vendor: as above
Sales date: as above
Relevancy of options to the purchase order: as above
As the vehicle is already a used one, the data is most likely to be correct already.

In both cases A and B above, a new internal order is usually created. Batch and valuation class need to be handled. There are the following two cases for this:

The vehicle is repurchased by the plant that last sold it.
In this case, the batch and valuation type can remain as they are. The only required change is the valuation class assigned to the valuation type. The valuation class is used to differentiate used vehicles from new vehicles in Financial Accounting and/or Controlling. You can only change the valuation class for a valuation type as long as the vehicle is not in stock.

The vehicle is repurchased by a different plant.
In this case, the valuation class is set to Used. Furthermore, the batch and valuation type for the vehicle may not yet exist in the plant, unless, for example, a plant transfer was carried out at some time in the past. If this information is not yet available, it is created for the vehicle in this plant.

Browser not supported