Assignment of Vehicles to Sales Documents

Use

As importer, you can use this functionality (transaction VELO, tab page Assignmnt ) to search for sales documents that a dealer has entered and to assign an appropriate vehicle from the warehouse stock or order pipeline to each sales document.

This is particularly useful in the following cases:

  • if your dealer can access your system but has not been able to find a vehicle that corresponds to the customer’s desired configuration

  • if your dealer does not have access to your system and vehicles and enters sales document with the customer’s desired configuration “offline”, for example in SAP CRM Mobile Sales

  • if, for sales and distribution reasons, you want to assign a vehicle, which you have already promised to one customer and thus already assigned a sales document, to another customer at short notice without having to cancel the original sales document

This function is mainly used within the framework of the make-to-stock scenario (MTS) , for example as is common practice in the USA .

Prerequisites

The sales documents contain a configuration but do not yet have a tight relationship with a vehicle, in other words, batch and valuation type have not yet been definitively entered in the sales document.

No follow-on documents (delivery, billing documents etc.) for sales orders without a vehicle have been created in standard SD, in other words outside of VMS.

Features

  • The functionality refers to the sales document type inquiry, quotation and order .

  • You can search for the sales documents either according to specific selection criteria or according to vehicle model.

  • In BADI VLC_EXECUTE_ASSIGNMT you can define exactly which configuration characteristics and sales document fields or vehicle fields have to correspond so that a vehicle is suited to a sales document.

    The standard system settings dictate that all configuration characteristics have to correspond so that a sales document suits a vehicle. In other words, the sales document configuration must be 100% identical to the vehicle configuration. If you enhance the standard implementation of the BAdI appropriately, you can also include sales document or vehicle fields in the matching process.

    Furthermore, the standard settings dictate that the customer’s desired configuration is not overwritten by the vehicle configuration when a tight relationship is created (see below).

    You can also control the search for suitable vehicles for a sales document via the normal search profile for the vehicle search. BAdI and search profile act in combination during the search so that the settings for the search profile override the BAdI settings, where necessary.

    If you are working with categories, the vehicles are listed in the hit list according to the priorities defined in Category Management . You can change this sequence using the above-mentioned BAdI.

  • You can compare the configuration of a sales document with the configuration of a vehicle that is found and, based on this result, decide whether you want to assign the vehicle to the sales document.

  • When you assign a vehicle to a sales document, you can decide between a loose relationship between vehicle and sales document and a tight relationship.

    • The loose relationship is a type of reservation. Technically speaking, the relationship between sales document and vehicle is saved in a separate third table ; sales document and vehicle are “ignorant” of each other.

    • The tight relationship is a type of confirmation of the loose relationship. Technically speaking, the batch and valuation type of the vehicle are entered in the sales document and the key for the sale document is entered in the appropriate vehicle document table; sales document and vehicle therefore “know” of each other’s existence.

      Both types of relationship can be deleted again without the sales document having to be cancelled.

  • The following actions serve to create and delete relationships:

    • LORS Create loose relationship

    • TIRS Create tight relationship

    • DELR Delete loose relationship

    • DETR Delete tight relationship

      Loose relationships can be replaced by loose relationships without the original loose relationship having to be deleted beforehand. This is useful if customer B is more important than customer A, even though customer B arrived later than customer A.

  • You execute individual processing in transaction VELO, mass processing in transaction VELOAS.

    Mass processing makes sense if the manufacturer generally produces to stock and you want to find suitable vehicles for a large number of sales documents.

  • If you have not found a suitable vehicle for a sales document, you can create a vehicle with a template configuration . You have the following actions at you disposal for this:

    • CVWT Create Vehicle with Template Configuration, with Batch and Valuation Type

    • CVT1 Create Vehicle with Template Configuration, without Batch and Valuation Type

      If, in transaction VELO on the tab page Assignmnt (Assignment), you have selected a sales document without a relationship to a vehicle, the template configuration is the configuration of the sales document. If, on the other hand, you have selected a vehicle the template configuration is the configuration of the vehicle.

      You can, of course, as with all other actions, call these two actions from the tab page Detail as well, after you have searched and chosen a vehicle. Then the template configuration is always the vehicle configuration.

      Note Note

      You can use method CHANGE_KB_PARAMETERS of BAdI VLC_SCE_PARAMETERS to change the parameters for knowledge-base object and runtime version of knowledge base when you create a vehicle with the template vehicle or sales document.

      End of the note.