Action control determination runs automatically in the system (according to the logic explained below) as soon as you perform an action. Primary and secondary action control can be determined individually and at the same time. An example for determination at the same time is the inter-linking action CRCO Create vehicle and sales order.

First, enter the information that the system requires for determining action control using transaction VELOS. In this transaction, enter the action controls with which you want VMS to work for each vehicle model and, if necessary, for further organizational data.

Key fields are: vehicle model, plant, purchasing organization, vendor, sales organization, distribution channel, division and customer. You can define different action controls for any combination of these fields. Mostly, however, it suffices to define action controls for each combination of vehicle model and plant (primary action control) and for each combination of sales organization and customer (secondary action control).

You don not have to enter a value in all the key fields. A key field that is empty means that the entry is valid for all values that are possible for this field.

Determination of the action control then works as follows:

1. In Customizing, the system checks whether the action that you want to perform is a primary and/or a secondary action.
2. The system checks whether the appropriate action controls have already been assigned to the vehicle. If yes, it uses these.



The assignment of an action control to a vehicle cannot be changed.

3. If no, the system triggers the action control and evaluates the entries in the table for transaction VELOS. This takes place on the basis of the action data and the existing vehicle data. The system makes checks in the following order:

1. Is there a fitting entry in the table for transaction VELOS? If yes, the system uses this entry.
2. If no: is there a generic entry that fits, in other words, an entry for which fields are empty and therefore all existing values can be taken? If yes, the system uses this entry. If there is no generic entry or more than one suitable one, the system displays and error message if the action controls in the entries are not identical.

As soon as the system has found the correct action control, determination is ended. The system performs the desired action and sets the status that is stored in the system as new status for this action in the action control.

If the system does not find a suitable action control, it displays an error message and you have to correct the entries in transaction VELOS appropriately.

You want to perform a primary action with the following action data: vehicle model Sprinter, plant 7777.

No primary action control has been assigned to the vehicle.

There is no entry that fits exactly in the table for transaction VELOS, in other words, there is no entry for which only the fields vehicle model Sprinter and plant 7777 are filled.

However, there is an entry for vehicle model Sprinter, plant 7777 and vendor Opel. But this entry is too specific due to the entry of a specific vendor and cannot therefore be used.

There is another entry for the vehicle model Sprinter for which only the vehicle model has been entered and no other fields have an entry in them. This entry is taken since the missing entry in the plant field means that the entry is valid for all existing plants.