SOCD

Save customer’s desired configuration

Saves additional configuration for vehicle

This action serves above all to store a desired configuration for the vehicle which you can then later compare with the actual configuration

SMOD

Change vehicle

Defined values in Customizing for vehicle usage, vehicle search area and sharing level

Defined qualifiers in Customizing and assignment to action SMOD

Allows changes to vehicle attributes and qualifiers (see Customizing for VMS under  Enhancements Program Actions and  Enhancements Define Additional Data for Vehicle )

Example for an action that works with additional data (filled by additional fields on the initial screen) and with qualifiers (ALV list on entry screen)

You can program any number of such actions that work with different fields

CORR

Correct status (without check)

Internal action that, in contrast to the other actions, is not actually an action since it does not link to a primary or secondary matrix

If you execute transaction VELOE ( Emergency Monitoring ), which you can use to change the vehicle status in case of an error, an entry is written to the vehicle history so that the status conversion is logged The action CORR is written to the history

This action cannot be started manually using transaction VELO

HIDE

Exclude vehicle from search

Sets the vehicle attribute for visibility to not displayed

The dealer usually performs this action in the MTS Scenario as soon as he has bought a vehicle so that other dealers do not have access to the vehicle

Default setting = vehicles not displayed

The actions HIDE and SHOW have no effect in themselves – only in combination with one of the following implementations:

You can use the visibility according to the selection in Category Management (vehicle filter) as parameter. Allows changes to vehicle attributes and qualifiers (see Customizing for VMS under  Enhancements Program Actions and  Enhancements Define Additional Data for Vehicle )

SHOW

Allow vehicle for search

Sets the vehicle attribute for visibility to displayed

CAMP

Assign sales campaign

Values for sales campaign (transaction VELOC )

Sets the vehicle attribute Sales campaign to a new value

The point of this action is to trigger pricing again in the sales order (due to assigned sales campaign) There are two options:

You can add the field as an object characteristic to the vehicle configuration (see: Adding Object Characteristic to Configuration )

LCTN

Set vehicle location

Values for vehicle locations in Customizing for VMS (transaction OVELOL)

Sets the vehicle attribute Vehicle location to a new value and assigns the address of the vehicle location to the vehicle

SHMT

Confirm transit

Example for an action that only changes the status and does not create any documents

Actions such as these, for example Confirm purchase order , can be defined in Customizing.

STWO

Trigger Workflow event

Organizational structure, tasks

Only useful as part of an inter-linking action

Triggers the sending of e-mails with Workflow items, these refer to the actions with which the action STWO has been linked

MSSO

Output messages

Customizing for VMS for message determination

Outputs messages (possibly as part of an inter-linking action)

You can display the sent messages in transaction VELO (tab page Details , screen Vehicle Data, Pushbutton ).

You can find further information in the documentation for Cross-Application Components under Message Control (CA-GTF-BS) and in the IMG for VMS in the documentation for message determination.

ADDO

Assign business documents

Assigns documents to a vehicle

You can display the stored documents in transaction VELO (tab page Detail , screen Vehicle Data , Pushbutton Documents ).

You can find further information in the documentation for Cross-Application Components under Business Document Navigator .

ARCS

Set archiving indicator

The action matrix must be set so that only vehicles with the appropriate status (example: sold, delivered, paid ) are flagged for archiving.

Flags vehicles for archiving

See: Archiving Vehicles

This action is an internal action that is executed within transaction VELOARSL

ARCD

Delete archiving indicator

Deletes archiving indicator

See: Archiving Vehicles

This action is an internal action that is executed within transaction VELOARSL

EMMI

Report events for SCEM

An event handler for the vehicle must exist in SAP SCEM.

Reports SAP SCEM events to the Event Handler, which is assigned to the vehicle

See: Connection to SAP SCEM

You can display the SCEM information in transaction VELO (tab page Detail , screen Vehicle Data . Pushbutton SCEM )

CRMV

Export vehicle to CRM

Individual object setup on CRM must have been prepared to import VMS vehicles

Transfers vehicle data, configuration data, history entries and relationships with dealers and end customers to SAP CRM and maps vehicle to “individual object”

See: Connection to SAP CRM

Sales process takes place in SAP DIMP

Then post-sales processes, for which the vehicle is the centre of attention, can take place in SAP CRM

You cannot transfer two vehicles with the same VIN to CRM.

In the VMS used-vehicle process, there can be duplication of VINs.The CRMV action should be used either for the new vehicle or the corresponding used vehicle, but not for both.

CRMS

Add vehicle to CRM order

A vehicle must have been attached to the replicated sales document using the Late Order Assignment functionality

Transfers Assignment of Vehicles to Sales Documents to SAP CRM

See: Connection to SAP CRM

Sales process takes place in SAP CRM. The assignment of vehicles to sales documents, however, takes place beforehand in SAP DIMP

CPGM

Cross-plant goods movement

Enables the goods movement of a vehicle from one plant/storage location to another plant/storage location

REPL

Realize in plant

Creates a batch for a vehicle in an additional plant

You can execute REPL on any existing vehicle. You specify the plant on the action screen; a batch and a valuation type will then be created for the vehicle in this plant. This is necessary because a sales order can only be created for a vehicle in a specific plant if a batch has been created in this plant.