Determination of Action Control

This process runs automatically in the system (according to the logic explained below) as soon as you perform a vehicle action. Primary and secondary action control can be determined individually and at the same time.

Prerequisites

• You defined the action control settings in Customizing for VMS under Control.
• You stored the information required by the system for determining the action control in the application from the SAP Easy Access screen under Logistics Execution > Vehicle Management System > Basic Data > Set Determination of Action Control (VELOS). You have entered the action controls with which you want Vehicle Sales and Service (VSS) to work for each vehicle model and, if necessary, for further organizational data. The following fields are key fields:
  • Vehicle model
  • Plant/Location
  • Purchasing org.
  • Supplier
  • Sales org.
  • Distr. channel
  • Division
  • Customer

You can define different action controls for any combination of these fields. Mostly, however, it suffices to define an action control for each combination of vehicle model and plant for primary action controls and for each sales organization for secondary action controls.
You do not need to fill all of the key fields. A key field that is empty means that the entry is valid for all values that are possible for this field.

Process

1. In Customizing, the system checks whether the action that you want to perform is a primary action, a secondary action, or both.

2. The system checks whether the appropriate action controls have already been assigned to the vehicle. If this is the case, the system uses these.

   Note

   The primary or secondary action control is assigned when the primary or secondary action is performed, respectively. If necessary, the new assignment can be subsequently triggered using the implementation of the method DETERMINE_CONTROL —> FORCE_REDETERMINATION of the BAdI Determination of Action Control.
3. If this is not the case, the system triggers determination of the action control and evaluates the entries in the table for the transaction Set Determination of Action Control (VELOS). This takes place on the basis of the action data and existing vehicle data. The system carries out checks in the following order:
   1. Does the table contain an entry that matches the transaction Set Determination of Action Control (VELOS)? If so, the system uses this entry.
   2. If no: Is there a generic entry that matches, that is, an entry for which fields are empty and therefore all existing values can be taken? If so, the system uses this entry. If there is no generic entry or more than one entry that matches, and if the action controls in the entries are not identical, the system displays an error message.

Result

As soon as the system has found a suitable action control, determination is ended. The system performs the desired action and sets the status that is stored in the system as the 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 the transaction Set Determination of Action Control (VELOS) appropriately.

Example

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 model. This usually means that the vehicle model has just been created.
The table does not contain any entries that exactly match transaction VELOS, in other words, it does not contain an 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 cannot be not found, since it includes a very specific vendor and the user has not entered a vendor.
There is another entry for the vehicle model Sprinter for which only the vehicle model has been entered and no other fields have been filled. This entry is taken since the missing entry in the Plant field means that the entry is valid for all existing plants.
The system always uses the most fitting entry from the table for transaction VELOS that matches the data specified.