Working with Actions (SAP Library - Vehicle Management System (IS-A-VMS))

Working with Actions

Use

Actions form the central functions in VMS. With the exception of actions for creating vehicles, they involve one or more vehicles that you have previously sought and chosen (see also: Vehicle Search, Searching for Vehicles and Vehicle Overview and Vehicle Details).

Features

You can control every action with authorizations (authorization object C_AUTO_VMS). So you can set up your VMS system so that you, as importer, are allowed to perform all actions, but your dealer only the actions for the sales orders, inquiries/reservation requests. offers/reservations, assigning of end customer and hiding/displaying of vehicles.

You call an action by choosing it in the action list field in the upper screen area and confirming with

. You can branch to actions that you have placed on pushbuttons (see below) directly by choosing the appropriate pushbutton. The tab page Action appears. If you have already found and chosen vehicles, they are copied to the left-hand screen area. In the right-hand screen area you can make your entries for the chosen action.

If you have not chosen any vehicles yet, only actions for creating new vehicles are displayed in the action list field. If you have already chosen vehicles, you only see the actions that are possible in the current process. If the primary and secondary action control is not yet known, too many actions may be displayed.

The default settings dictate that only the actions that are allowed for all the selected vehicles are displayed. You can use the parameter name VELO_ACTLISTBOX = X to define that all the actions are displayed that are allowed for at least one of the selected vehicles.

You can place up to four actions that you use most often on pushbuttons. These pushbuttons are then displayed in the uppermost screen area and always at your disposal.

If you want to do this, enter one or more of the following parameters: VELO_ACT1, VELO_ACT2, VELO_ACT3 and VELO_ACT4 and assign an action to each parameter as value. You can find the keys for the actions (for example, CREA for Create vehicle) in Customizing for VMS (transaction OVELO1).

Actions refer to all the vehicles in the left-hand screen area of the tab page Action.

All actions are performed for all vehicles at the same time. You therefore only choose once. For some actions, however, you may need to assign specific data to each vehicle, for example Assign end customer or Create inbound invoice. You can recognize these vehicles by the fact that the internal vehicle number is displayed in the right-hand screen area. Make the required entries for the first vehicle, then select the next vehicle in the left-hand screen area, make the entries for this vehicle and so on. When you have completed all the vehicles, choose once.

You can see whether the action has been performed successfully or not by the success indicator in the left screen area next to each vehicle and the appropriate message in the status line. You can find further information on any errors that may have occurred in the log. Choose Log.

Only the current VMS run is logged. As soon as you exit the transaction VELO, the log can no be displayed. You can use user parameter VELO_ACTPROTOCOL = X to make settings to define that the log is written to the database. You can then call it with transaction VELOP03 or delete it with transaction SLG2 (object VMS_ACTION). Saving the log is particularly useful for the test phase.

If you perform an action after you have called the log, the log is not updated automatically. Close the log and call it again.

The default setting dictates that all the actions (that create documents) create exactly one document with one item per vehicle. The quantity per item is always 1. If, for example, you order 10 vehicles, one purchase order with 10 items is created.

Depending on certain settings in SD, you can create more than one document at the same time, but only for the action DELI Create delivery.