...
- Directly for the vehicle
In the vehicle master record, you can select one of the actions offered. Otherwise, an action is executed using the RFC module. - Implicitly on the basis of the VSS order
Vehicle actions can be triggered by means of order control.
Info title Note In Customizing for VSS, you can define which action the system has to execute when an order of a certain order type is created and deleted or rejected by choosing Order > Order Control > Order Control VMS Extension > Define Table of Criteria for Order Control - VMS Action Determination. For example, the standard system executes action QCUO when a vehicle order (order type 3000) is created and action QDCO when it is deleted.
| Anchor | ||||
|---|---|---|---|---|
|
Action Control for the Vehicle Management System (VMS), which controls the actions for the VSS vehicle, and order control for Vehicle Sales and Service (VSS) interact in the standard system as follows:
As soon as a vehicle is used in a VSS order, the order control takes over control of the next step such as goods issue or invoice creation.
At the same time, the order control also triggers vehicle actions, which ensure that the system updates the vehicle history accordingly and that the links to various documents generated in the background are saved.
You can change the Customizing settings in such a way that VMS action control influences and also controls the order process.
...
- The vehicle actions must be permitted in the action grid in Customizing for VMS by choosing Control Data > Define Action Controls and Define Action Matrices.
- Vehicle actions that do not appear as actions in the vehicle master and that should be executable only using the VSS order are identified as internal actions in Customizing for VMS under Control Data > Define Actions.
- The vehicle actions must be made known to VSS by means of control values in Customizing for VSS under Vehicle > Enter Control Value.
| Anchor | ||||
|---|---|---|---|---|
|
You have defined the following in Customizing for VMS under Control Data:
- Actions
- At least one action control
- Vehicle status
- One action grid for each action control
| Anchor | ||||
|---|---|---|---|---|
|
- You can control every action with authorizations (authorization object C_AUTO_VMS). This means, for example, that you can configure VSS in such a way that you, as management, are authorized to perform all actions, but your employees only specific actions.
- In the vehicle master record, you can only choose those actions that are possible for the current vehicle status in accordance with the action grid. The system does not display the other actions.
- If the system executes an action, this can result in a change in the status of the vehicle, depending on the definition in Customizing. A primary action influences the primary status, a secondary action the secondary status.
- In the vehicle master record under VMS Vehicle History, you can track the actions that have already been executed with primary and secondary statuses.
- A whole host of actions are delivered with the standard system. In Customizing, however, you can change these actions or define and program your own actions.
- The standard actions can be assigned to the following business processes:
- Business Add-Ins (BAdIs) are available for the most important actions in the standard SAP system. You can use these BAdIs to adapt the EXECUTE modules for the actions to suit your own specific requirements.
...
For more information about the vehicle actions that can be executed in VSS, see Details for the Vehicle Actions.
| Anchor | ||||
|---|---|---|---|---|
|
Vehicle History
Action | Primary Status | Secondary Status |
Create vehicle with internal order | Vehicle created | |
Order vehicle | Vehicle ordered | |
Create goods receipt | Vehicle received | |
Assign customer | Vehicle received | Customer assigned |
Create vehicle order | Vehicle received | VSS order created |
Change vehicle | Vehicle received | VSS order created |
...