Action Control You can represent your business processes in the system with action controls. You define which actions can follow one after the other when handling vehicles and which changes to the status of the vehicle are involved in this.
Example
A vehicle that the importer has ordered from the manufacturer receives the status
Ordered
. After the manufacturer has confirmed the purchase order, in other words has performed the action
Confirm purchase order
, the status changes automatically to
Purchase order confirmed
.
Caution
You can access an emergency report with transaction VELOE. VMS administrators can use this report to change the status of vehicles without the action controls being checked. This is only to be recommended if you want to sort out data inconsistencies. You should not use this report under normal VMS business circumstances. In other words, this report should be used with care!
You have defined the following parameters in Customizing for VMS under
Control Data
:
Actions (transaction OVELO1)
Vehicle status (transaction OVELO12)
Vehicle availability (transaction OVELO13)
Vehicle locations (transaction OVELOL
You can distinguish between primary and secondary action controls , depending on the process that is being represents by the action control. The primary action control usually represents the procurement process, in other words, ordering the vehicle from the manufacturer and the secondary action control the sales process, in other words, sale of the vehicle to the dealer. However, a subdivision into a logistics and a financial process is also possible.
You can “finely tune” the primary and secondary processes with different action controls. This means that processes can be different depending on the sales organization or vehicle model etc.
Example
The delivery schedules are longer for the sales organization Sweden than they are for Germany if you, as importer, have your registered office in Germany; certain specific vehicle models do not require any actions for local rework or for reservations etc.
Choose (transaction OVELO11) in Customizing for VMS. Define the following there:
Define the action controls for the vehicles that you require for your business processes.
Create an action matrix for each action control.
In this matrix you define which action is allowed for which vehicle status and to which status the action converts the vehicle. By doing this, you represent your internal business process in the system.
For specific combinations of action control and action, create an entry with data on availability, delivery schedule and vehicle address .
You can also store these entries for each combination of action control, action and status for actions that are performed on a regular basis and result in different statuses.
Example
The action
Change sales order
can be performed either early in the process before the purchase order is created or later after the purchase order has been created. Depending on when it is performed, the elapsed time until the vehicle is delivered is either longer or shorter. You then require different data for delivery scheduling.
This matrix uses a procurement process to illustrate how actions have an effect on the status of a vehicle.
