Recommendation

It is recommended that you define vehicle models generally so that configuration changes can be made during the sales process without having to change the vehicle model.

Example: you have defined the vehicle model SAPcar . If the dealer receives a quotation for a SAPcar hatchback but then decides on a SAPcar limousine after all, this change is possible within the vehicle model SAPcar . However, if you have defined the vehicle model on the level of SAPcar hatchback and SAPcar limousine , in other words, you decide to work with specific characteristics on this level, changing the quotation would mean having to change the vehicle model, too. The material, however, cannot be changed in the documents. You would therefore have to cancel the quotation and create a new one.

On the other hand, you should not define vehicle models too generally . When you create a vehicle that can be assigned values, the existing material master record for the vehicle model is extended by a valuation type. This results in the material master being locked for a while. In this period of time, no other dealer can create a vehicle for this vehicle model. The same applies to goods receipt and goods issue postings. If the vehicle model has been defined very generally, the material master record threatens to become very large, which ultimately means bad performance.

Example: you have defined the vehicle models car and lorry . Every time you create a new car, the material master record is locked for a short while and extended.