Vms Content 8

Actions
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_di46c2/helpdata/EN/95/47c83abc3c1a54e10000000a114084/content.htm
Created on March 24, 2015
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 21
Table of content
1 Actions
1.1 Working with Actions
1.2 Performing Actions in a Batch
1.3 Make-to-Stock Scenario:
1.4 Make-to-Order Scenario:
1.5 Configurations
1.5.1 Handling Configurations
1.5.2 Actions and Configurations
1.6 Creating Vehicles
1.7 Procurement: Purchase Order
1.8 Procurement: Incoming Invoice
1.9 Sales: Reservation, Quotation, Reservation Request, Inquiry
1.10 Sales: Sales Order
1.11 Sales: Delivery
1.12 Sales: Outgoing Invoice
1.13 Goods Movements: Goods Issue, Goods Receipt
1.14 Rework (Including Goods Movements)
1.15 Processing Returns
1.16 Trade-In and Used Vehicle Sales
1.17 Service Processing
1.18 Special VMS Actions
1.19 Warranty Processing
PUBLIC
Page 2 of 21
1 Actions
Use
Actions are business transactions that represent the business processes involved in the handling of vehicles, for example, creating a vehicle,
changing a vehicle, creating a purchase order and creating a sales order.
Features
Actions can be classified as primary or secondary actions. The terms primary and secondary should not be regarded as higher or lower level, in other
words, they do not indicate a hierarchy. Whether the actions are primary or secondary depends on the individual business processes of the user. Possible
divisions are: procurement actions versus sales actions or logistical actions (actions that affect the vehicle itself) versus financial actions (actions that affect
payment transactions).
Actions affect the vehicle status. Primary actions affect the primary status, secondary actions the secondary status. Primary and secondary statuses
exist in parallel and independently of one another. You can control which actions can follow on from one another and which change of status this causes under
Action Controls .
There are the following types of actions:
Actions that do not change the vehicle status
(for example: vehicle status quotation created , action change vehicle => vehicle status remains unchanged as quotation created ).
Actions that assign a new value to the vehicle status
(for example, old vehicle status quotation created , action create sales order => new status sales order created ).
An inter-linking action is an action that comprises two or more linked elementary actions. The term elementary action means, in this case, the same as
action.
When the inter-linking action is started, all the other elementary actions contained in it are performed in the given order. The system processes each
elementary action as a complete action, including setting a new status and updating data.
The use of inter-linking actions is critical if both actions create business documents. If the second elementary action expects data on the database
that is not written until the first action has been completed, the system cannot perform the inter-linking action.
A whole host of actions are delivered with the standard system. In Customizing, however, you can modify these actions or define your own actions.
You can find further information in the IMG documentation Program Actions under Logistics Execution Vehicle Management System Enhancements.
1.1 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
PUBLIC
Page 3 of 21
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 .
1.2 Performing Actions in a Batch

Use
As a system administrator for VMS, you can perform any actions you like in batch mode (in other words in a collective run) and schedule these runs for any time
you like. You define with which parameters you want to perform the actions in parameter variants. You can define the number of vehicles for which you wish to
perform the actions by using selection criteria.
The name of the batch program is RVLCSACREG.
Creating Parameter Variants

Choose the transaction VELOV ( Maintain Variants ).
The selection screen for choosing parameter variants appears (table VLCBATCHACT).
Choose
directly if you want to display all existing parameter variants.
Limit your selection and then choose
if you only want to display specific parameter variants, for example all parameter variants for a specific action.
A list appears that displays all the parameter variants that correspond to your selection criteria.
Choose
to create a new parameter variant.
A screen appears with the fields of all the existing action interfaces.
Choose an action. Enter a name for the parameter variant and define the further parameters with which you want to perform the action. These are then the
parameters that you have to enter on the appropriate action interface when you start the actions from the Vehicle Manager.
Save your entries.
Performing Actions with Parameter Variants in Batch Mode

Choose transaction VELOB ( Perform Actions in Batch ).
The Triggering of Action Supported by Report screen appears.
Choose the desired action and a parameter variant for this action. The parameter variant is a required field.
Limit the number of vehicles in the Vehicle Selection area of the screen to those for which you want to perform the action /exception: all actions that create
vehicles). Enter at least the plant.
Select the field Trigger Action Directly if you want the action to be performed for all the vehicles that the system finds.
Deselect the field if you do not want the action to be performed for all the vehicles but rather only for some of the vehicles, which you want to define more precisely.
Choose the status the vehicles for which the action is performed should have in the screen areas entitled Primary Sts and Secondary Sts .
Start the batch job or schedule it.
Choose
if you want to start the batch job immediately.
If you have selected the Trigger Action Directly field, a list containing error messages and success messages appears. These are either general
messages or messages with reference to a vehicle and they give you a hint on how to continue processing.
If you have not selected the Trigger Action Directly field, a list appears with all the vehicles that the system has found. You can select your desired
vehicles in this list and start the action for these vehicles with
success messages.
Action . After this intermediary step, you then also receive a list with error and
Choose Program Execute in background if you want to schedule the batch job.
The screen for entering print parameters appears. Enter the required data and choose
want the job to be executed and save your entries.
. The screen for scheduling jobs appears. Enter when you
1.3 Make-to-Stock Scenario:

Purpose
You use this procedure if your dealers work with make-to-stock production or when you order vehicles for stock yourself.
Process Flow
As importer, you sit down with your manufacturer, analyze the sales figures for the last business period and decide on quotas for the individual vehicle models for
the new business period. This decision made, you create the number of vehicles agreed on as planned vehicles (no value assignment possible) in your system.
You do not allow values to be assigned until you actually order the vehicles from the manufacturer. As soon as you receive a purchase order confirmation from the
manufacturer via IDoc, you make the vehicles visible, in other words, offer them for sale to your dealers. Your dealers can now make reservations and requests for
reservations or also create a sales order directly. As soon as a dealer has created a sales order, he/she hides the vehicle from display so that it can no longer be
PUBLIC
Page 4 of 21
seen by other dealers.

Goods movements and invoices complete the process. The process is complete when your dealer delivers the vehicle to the end customer and the sales
registration note with the license number has been returned to you.
Here is an example of this procedure. (V) signifies an
Interlinking Action.
Sequence
Action
Description
Who does this?
CRE1
Create planned vehicle (without

values)
Importer
CMOD
Change configuration of planned

vehicles
Importer
REAL + ORD1
Allow value assignment for vehicle and Importer

create purchase order (alternative to
steps 1-3 also
ORD2)
MORD
Change purchase order
Importer
CONF
Confirm purchase order (action not

contained in the Customizing settings
delivered)
OEM via EDI
SHOW
Allow vehicle for search
Importer
SHMT
Confirm transit
OEM via EDI
GORE
Create goods receipt (also possible

later in process)
Importer
INIV
Create inbound invoice (also possible

later in process)
Importer
10
RSVN
Create reservation
Dealer
11
CUOR + HIDE
Create sales order and exclude vehicle Dealer

from search
12
CHCO
Change sales order
Dealer
13
BUPA
Assign end customer
Dealer
14
DELI
Create delivery
Importer
15
GOIS
Create goods issue
Importer
16
OUIV
Create outbound invoice
Importer
1.4 Make-to-Order Scenario:

Purpose
You use this procedure if your dealers work with make-to-order production and do not produce for stock.
Process Flow
In contrast to the make-to-stock scenario, you do not create the vehicle as importer. Your dealer does this with respect to a sales order. The vehicle created
therefore has the configuration desired by the dealer or the end customer. As importer, you order the desired vehicle from the manufacturer. Larger dealers can, if
required, create the vehicle, purchase order and sales order at the same time in an inter-linking action. The manufacturer confirms the purchase order and
produces the desired vehicle. He/she updates the vehicle status using IDocs and informs you of the progress being made in production/delivery.
Goods movements and invoices complete the process. The process is complete when your dealer delivers the vehicle to the end customer and the sales
registration note with the license number has been returned to you.
Here is an example of this procedure. (V) signifies an
Sequence
Action
Description
Who does this?
CRCO (V) or
Create vehicle and sales order
Dealer
1+4
O2CO (V)
Create vehicle, purchase order and

sales order
Dealer
CHCO
Change sales order
Dealer
BUPA
Assign end customer
Dealer
ORD1
Create purchase order
Importer
MORD
Importer
PUBLIC
Page 5 of 21
2+5
CCPO (V)
Change sales order and purchase

order
Dealer
CONF
Confirm purchase order (action not

contained in the Customizing settings
delivered)
OEM via EDI
SHMT
Confirm transit
OEM via EDI
GORE
Create goods receipt (also possible

later in process)
Importer
INIV
Create inbound invoice (also possible

later in process)
Importer
10
UORD
Start rework (purchase order and

transfer posting)
Importer
11
UGRE
Finish rework (goods receipt)
Importer
12
DELI
Create delivery
Importer
13
GOIS
Create goods issue
Importer
14
OUIV
Create outbound invoice
Importer
1.5 Configurations
Features
There are the following configurations in VMS:
Vehicle Configuration
The vehicle configuration is part of the vehicle data and is stored in the vehicle table. It is the only configuration that is relevant in the vehicle search. The
vehicle configuration is displayed with the vehicle details in transaction VELO .
You can save a customer configuration using action

SOCD. This is the configuration that contains the original configuration desired by the customer. When, in a make-to-stock scenario, a customer buys a vehicle for
which the configuration does not completely fulfill his/her requirements, the configuration originally desired can be saved. Evaluations at a later date can then
determine in how far the actual and target configurations differ.
Sales Order, Offer, Inquiry Configuration
You can display the sales order configuration with the standard transaction VA03, the offer configuration with VA23 and the inquiry configuration with VA13.
Purchase Order Configuration
You can display the purchase order configuration using transaction ME23.
Subcontracting Purchase Order Configuration
You can display the subcontracting purchase order configuration using the standard transaction ME23.
You can use the icon
in the vehicle history to branch to the transactions named above.
1.5.1 Handling Configurations

Functionality
The sales order, purchase order and subcontracting purchase order configuration influence the vehicle configuration in such a way that the vehicle configuration in
the vehicle data mirrors the current physical configuration as far as possible.
There is the following priority:
1.
2.
3.
4.
Subcontracting Purchase Order Configuration

Sales Order Configuration
Planned Configuration (vehicle configuration before the documents are created)
A new or changes configuration only influences the configuration if there is no configuration that has a higher priority (further up in the above list). If, for example, a
purchase order exists, a sales order configuration does not influence the vehicle configuration, but it does if there is no purchase order.
The inquiry configuration and the offer configuration are of no importance in the respect. The inquiry configuration is stored in an inquiry document but
does not have any further control function. The offer configuration is stored in the offer document and serves as a template for the sales order
configuration.
PUBLIC
Page 6 of 21
Process Flow
Make-to-Stock Scenario:
The vehicle configuration is at the beginning of the MTS scenario. As soon as the purchase order is created at the manufacturer, the configuration for the
purchase order becomes the vehicle configuration. As soon as a subcontracting purchase order is created for rework, the additional rework characteristics
are copied to the vehicle configuration. If no rework is required, the purchase order configuration and the sales order configuration are the same. At the end,
the vehicle configuration shows what the vehicle really looks like.
Make-to-Order Scenario:
The vehicle configuration is at the beginning of the MTO scenario. As soon as the dealer creates the sales order, the configuration for the sales order
becomes the vehicle configuration. As soon as the purchase order is created, its configuration is copied to the vehicle configuration. As soon as a
subcontracting purchase order is created for rework, the additional rework characteristics are copied to the vehicle configuration. After rework, the vehicle
configuration and the sales order configuration are the same. At the end, the vehicle configuration shows what the vehicle really looks like.
Notes
All actions for which configuring a vehicle and/or deleting configurations is possible have a set
Template Configuration. You can change this template configuration using the BAdI VLC_PREPARE_ACTION (method PREPARE_FURTHER_ACTIONS).
The first elementary action always sets the template configuration for inter-linking actions.
You can split the configuration using the BAdI VLC_CONFIG_SPLITTER. Splitting is useful if you want to distinguish between global and local
characteristics. The global characteristics (OEM-relevant characteristics) are the written to the purchase order and the local characteristics to the
subcontracting purchase order for rework.
1.5.2 Actions and Configurations

Below you can find a list of all the actions which allow you a configuration to take place or which allow a configuration to be deleted. The template configuration
is the configuration with which the action is called.
Action
Description
Template Configuration
CREA/CRE1
Create vehicle (values

possible)/create planned
vehicle (no values possible)
None
A new vehicle configuration is

created If you have not
configured when you create the
vehicle, the vehicle
configuration is created but
remains empty
CMOD
Change configuration of
planned vehicles
Vehicle configuration is
changed
VDEL
Delete vehicles without

documents
Not necessary
Vehicle configuration is deleted
ORD1
changed
Purchase order configuration is

created and copied to the
vehicle configuration
MORD
changed

changed If none exists yet, one
is created
DORD
Delete order item
Not necessary
If a sales order exists, the

sales order configuration is
deleted
copied to the vehicle
configuration If not, the planned
configuration is reused
IQRY
Create inquiry
Vehicle configuration is not

changed
Inquiry configuration is created
DEIQ
Delete inquiry
Not necessary

changed
Inquiry configuration is deleted
OFFE
Create offer

changed
Offer configuration is created
DEOF
Delete offer
Not necessary

changed
Offer configuration is deleted
CUOR
Create sales order
If exists, then offer

The vehicle configuration is
configuration, otherwise vehicle only changed if no purchase
configuration
order exists
The sales order configuration is

vehicle configuration is no
purchase order exists
CHCO
Change sales order
The vehicle configuration is

only changed if no purchase
order exists
The existing sales order

configuration is changed
DECO
Delete sales order
Not necessary
If purchase order exists, the

vehicle configuration is not
changed If no purchase order
exists, the planned vehicle
configuration is reused
Sales order configuration is

deleted
UORD
Start rework (purchase order

and transfer posting)
If exists, then sales order

configuration, otherwise vehicle changed
PUBLIC
Further Configurations
Subcontracting purchase order

configuration is created and
Page 7 of 21
configuration
copied to the vehicle

configuration
UDOR
Delete rework purchase order

and transfer posting
Not necessary
reverted to what it was before
rework If several rework step,
the correct configuration can
only be reused for the correct
rework step
Subcontracting purchase order

configuration is deleted
RETU
Create return

changed
Sales order configuration is

copied to the returns document
POEU
Trade-in
changed

vehicle configuration
SOEU
Used vehicle sales: create

order

changed
A new sales order configuration

is created
SOCD
Save customers desired

configuration
Not necessary

changed
The configuration desired by

customer is created, if one
already exists, it is changed
Notes
1.6 Creating Vehicles

Process
You can find further information in the Standard documentation under

Batch Management (LO-BM), especially
Valuation for a Single Batch.
Actions
Action
Description
Prerequisites
What does the action do?
CRE1
Create planned vehicle

(without values)
Configurable material,
configuration profile, class
Creates vehicle without batch Vehicles must belong to the

and valuation type The internal same vehicle model and have
vehicle number is assigned
the same configuration
REAL
Allow values for vehicle
Planned vehicle
Creates batch and valuation

type for vehicles that have
already been created with
CRE1
CREA
Create vehicle (with values)
Configurable material,
configuration profile, class
Creates vehicle with batch and

valuation type The internal
vehicle number is assigned
The number of the batch and
the valuation type are identical
to the internal vehicle number
Vehicles must belong to the

same vehicle model and have
the same configuration
Only advisable if the vehicle
is really to exist in this form
since the valuation type cannot
be deleted later
CMOD
Change configuration of
planned vehicles
Planned vehicle
Changes configuration of
planned vehicles
Only for planned vehicles

since the configurations cannot
be changed in purchase order
documents and sales order
documents
VDEL
Delete vehicles without

documents
There must be no equipment

and no document (purchase
order, sales order etc.) for the
vehicle
Deletes vehicle without

documents If configurations
and batches exist for the
vehicle, these are also deleted
Valuation types are not deleted

with this action.
You can delete valuation types
individually and manually
using transaction MM06.
PUBLIC
Page 8 of 21
RVAL
Revaluate vehicle
Vehicle that has already been

posted in goods receipt and is
managed in stock with a
quantity of 1
Changes the vehicle value in

the valuation segment of the
material master
A price change document (LO)
and an accounting document
(FI) are created
This action is useful if costs

have been incurred in the
VMS process that have to be
activated (example: payment
of duty)
1.7 Procurement: Purchase Order

Process

Purchase Orders (MM-PUR-PO).
Actions
(V) signifies an
Action
Description
Prerequisites
Notes
ORD1
Vehicle can be assigned

values
Creditor
Purchasing info. record
Creates a purchase order at

manufacturer for existing
vehicles.
The complete configuration is

written to the purchase order
(by default).
ORD2
(V)
Create vehicle and purchase

order
MORD
Purchase order
Goods issue should not have
been posted
Changes the configuration and The selected vehicles must be

the delivery date of order items in the same purchase order;
and performs pricing again.
but not all vehicles in the
purchase order have to be
selected
You can only change the
configuration and delivery date
parameters
DORD
Delete order item
Purchase order
Goods issue should not have
been posted
Deletes purchase order items.
CREA + ORD1
1.8 Procurement: Incoming Invoice

Process
Actions
Action
Description
Prerequisites
INIV
Create incoming invoice
Purchase order
Enters incoming invoice
The goods receipt must have Currency and payment
been posted for goods-receipt- conditions are taken from the
PUBLIC
Notes
The action is used for incoming
invoices for actions ORD1
(create purchase order) and
Page 9 of 21
IIVR
Cancel incoming invoice
related invoice verification
purchase order or the

purchasing info. record
POEU (trade-in). and not for

incoming invoices after rework.
There can only be one
purchase order without an
incoming invoice for a vehicle
If there is more than one, the
incoming invoice for the newest
purchase order is
automatically posted
Incoming invoices for one-time
vendors are not possible with
this action.
Incoming invoice
Creates cancellation document The incoming invoice can only

for incoming invoice
be cancelled completely All
the vehicles in the incoming
invoice have to be selected
1.9 Sales: Reservation, Quotation, Reservation Request,

Inquiry
Process
The reservation request can be used by yourself, as importer, and by your dealers. With this process, your dealers begin the sale of vehicles, which ends in a
sales order. As importer, you can use the process for assigning a set amount of vehicles to your individual dealers. At the start of the business period you
agree with each of your dealers on how many vehicles of each model he/she wants to take. Then you create the vehicles and reserve them for each of your
dealers. By doing this, this dealer is entered in the vehicle data. Only this dealer may then create a sales order for such a vehicle.
Creating quotations and inquiries is optional in this process. It makes sense to work with quotations and inquiries if you:
want to use objects and documents from the standard SAP system (quotation and inquiry are standard objects, reservations and reservation requests are
VMS objects)
want to print documents
want to configure vehicles
The report REP_MAIN_QUEUE (transaction VELOR Update reservation queue ) deletes all expired reservations, reservation requests, quotations and inquiries.
If a reservation is deleted (from the report or manually), it results in the next reservation request becoming a reservation. If the current date does not coincide with
the validity period of this reservation, the validity date is changed to include the current date and all the following reservations move accordingly in time too.
You can display the logs for this report with transaction VELOP02 and, for example, determine for which dealer a valid reservation exists. You can
then inform this dealer per e-mail, if necessary. You can delete the logs with transaction SLG2 (object VMS_RESV).
PUBLIC
Page 10 of 21
Prerequisites
You have created vehicles but not yet entered any sales orders for these vehicles.
As soon as you create a sales order, reservations and reservation requests including the appropriate quotations and inquiries are deleted.
You have created master records in the customer master record for dealers to whom you want to sell vehicles (see also:
Creating Vendors and Customers).
Actions
(I) signifies an
Action
Description
Prerequisites
Notes
RSVN
Create reservation
No sales order, no quotation

and no reservation can exist for
the vehicles
Plant calendar (if you require
one when calculating the
validity periods)
Reserves the vehicles for a

specific dealer and writes the
dealer as customer in the
vehicle data
The standard validity amounts

to 3 working days from the
creation date You can
implement your own logic
using the BAdI
VLC_RESERVATION
You can display the
reservation and the reservation
requests in transaction VELO
(tab page Details , screen
Vehicle Data . Pushbutton
Reservations
)
OFFE
Create quotation
Reservation for the same

dealer
Creates a quotation for the

dealer for which the reservation
is also valid
RSOF
Create reservation and

quotation
RSVN + OFFE
(I)
DERS
Delete reservation
Reservations
Deletes the reservation for the
The selected vehicles must be vehicles
reserved for the same dealer
If no sales order exists, the
dealer is deleted as customer
form the vehicle data
DEOF
Delete quotation
Quotation
DERO
Delete reservation and

quotation
DERS + DEOF
RSVM
Create request for reservation
Creates a reservation request

for the vehicle
IQRY
Create inquiry
RSIQ
Create reservation request and

inquiry
Deletes the quotation Deletes

customer, end customer and
confirmed delivery date form
the vehicle master record
You can only delete an entire

document and not only
individual items
(I)
Reservation request for the

same dealer
You can display the

reservation and the reservation
requests in transaction VELO
(tab page Details , screen
Vehicle Data . Pushbutton
Reservations
)
The validity period follows up
the last reservation or
reservation request
The standard validity amounts
to 3 working days from the
creation date You can
implement your own logic
using the BAdI
VLC_RESERVATION
Creates an inquiry for the

dealer for which the reservation
request is also valid
RSVM + IQRY
(I)
DERQ
Delete reservation request
Reservation request
DEIQ
Delete inquiry
Inquiry
DERI
Delete reservation request and
PUBLIC
Deletes the reservation

requests for the vehicles
You can only delete an entire
individual items
DERQ + DEIQ
Page 11 of 21
inquiry
(I)
1.10 Sales: Sales Order

Process
For more information, see the standard documentation

Sales Order.
Actions
(I) signifies an
Action
Description
BUPA
Assign end customer
CUOR
Create sales order
CHCO
Prerequisites
Notes
Assigns an end customer to

the vehicles You can also
create an end customer
An importer can display all

end customers, a dealer can
only display his/her own , i.e.
the ones he/she created This
is controlled by entering the
dealer as a customer in the
Organizational Role
Customer master record for

dealer
Creates sales order for

vehicles and enters dealer to
which the vehicles are to be
sold and the vehicle usage in
the vehicle data
You can also create and
assign an end customer
Deletes the
reservation queue
This action cannot be used for

reselling used vehicles with
the
Trade-In process.
Change sales order
Sales order
Changes sales order If the

configuration is changed,
pricing is performed again
You can also create and
assign an end customer
The selected vehicles must be

in the same sales order; but
not all vehicles in the sales
order have to be selected
The dealer as sold-to party
cannot be changed
This action cannot be used for
reselling used vehicles with
the
Trade-In process.
DECO
Delete sales order
Sales order
Deletes sales order with the

most recent date
Deletes end customer and
dealer (customer) from the
vehicle data
You can only delete a

complete sales order, not
individual items
CRCO
Create vehicle and sales order
CREA + CUOR
Only advisable in the

MTO Scenario
Create vehicle, purchase order

and sales order
CREA + ORD1 + CUOR

MTO Scenario
Change sales order and

purchase order
CHCO + MORD
First changes the sales order

MTO Scenario
(I)
O2CO
(I)
CCPO
(I)
PUBLIC
Page 12 of 21
and then the purchase order
1.11 Sales: Delivery

Process

Delivery Processing.
Actions
Action
Description
Prerequisites
DELI
Create delivery
Sales order
Vehicle must be in importer
stock
Creates delivery for sales order You can split a sales order into
with the most recent date
different deliveries
More than one order can be
grouped into a delivery if
specific criteria have been
fulfilled For this to be the case,
the appropriate field in the
sales area data of the
customer master record (tab
page for shipping) must have
been selected
You do not have to select all
the vehicles in a sales order
Notes
DEDE
Delete delivery
Delivery
Deletes delivery for sales order You can only delete a

with the most recent date
complete delivery, not
individual items
1.12 Sales: Outgoing Invoice

Process

Billing.
Actions
Action
Description
Prerequisites
Notes
OUIV
Create outgoing invoice
Sales order
Bills the sales order with the

most recent date
Outgoing invoices are only

possible if related to sales
order, not related to delivery
More than one order can be
grouped into an outgoing
invoice if specific criteria have
been fulfilled
OIVR
Cancel outgoing invoice
Outgoing invoice
Cancels existing outgoing

invoice
You can only cancel an entire

individual items
PUBLIC
Page 13 of 21
1.13 Goods Movements: Goods Issue, Goods Receipt

Process
You can find further information in the standard documentation under

Goods Issue and
Goods Receipt.
Actions
Action
Description
Prerequisites
Notes
GORE
Create goods receipt
Purchase order
Creates material document for

the goods receipt with
reference to a purchase order
The action is used for goods

receipts for actions ORD1
(create purchase order) and
POEU (trade-in) and not for
goods receipts after rework.
There can only be one
purchase order without goods
receipt for a vehicle If there is
more than one, the goods
receipt for the newest
purchase order is
automatically posted
It cannot be posted to the sales
order stock
GRER
Cancel goods receipt
Goods receipt
Creates cancellation document This action can cancel a

for goods receipt
complete goods receipt or
individual document items
STOL
Storage location posting
Goods receipt
Vehicle cannot be in
repair/rework
Creates a material document

This action can still be
for the transfer posting from one performed after a delivery has
storage location to another
been created as long as no
goods issue has been posted
for this delivery
Posting across different plants
is not possible
GOIS
Create goods issue
Delivery
Creates a material document

for a goods issue
The storage location from which

the goods issue can be posted
cannot be changed after the
delivery has been created
Goods issue documents must
have a 1:1 relationship to the
delivery
GISR
Cancel goods issue
Goods issue
Creates a cancellation
document for the goods issue
This action only cancels a

complete document
It can only be used for goods
issues that have been created
with the action GOIS.
1.14 Rework (Including Goods Movements)

Process
PUBLIC
Page 14 of 21
The reworker is represented in the SAP system as a vendor in the role of a subcontractor. For more information, see the standard documentation
Subcontracting.
Vehicles can be reworked more than once.
Processing rework is only possible using an external service provider.
The actions DORD, MORD, GORE, GRER, INIV and IIVR cannot be used in the rework process. You can only use four actions (listed below) in
the rework process.
Prerequisites
You have defined which characteristics are to be reworked by which vendor.
If only part of the configuration is to be assigned to a subcontractor order, you have implemented BAdI VLC_CONFIG_SPLITTER, which compares the
purchase order configuration with the sales order configuration. The differences between these two define the scope of the work to be done.
Actions
Action
Description
Prerequisites
Notes
UORD
Start rework (purchase order

and transfer posting)
Procurement process
completed up to and including
goods receipt
Reworker created as creditor in
the system
Subcontractor info. record
Bill of material (if components
to be provided are being
worked on) as super BOM with
object dependencies for the
BOM explosion: the vehicle
must be a component in the
BOM
Creates subcontractor
purchase order and transfer
posting for the vehicle in the
subcontractor stock
The BOM is exploded
The components to be
provided for the subcontractor
purchase order can only be
determined by the BOM
explosion
The transfer posting of these
components to the
subcontractor stock takes
place outside VMS (in the
standard transaction MB1B)
There is only one entry in the
history so you can only display
the purchase order and not the
transfer posting
You can enter a default value
in the field Reworker with the
user parameter
VELO_REWORKER
UDOR
Delete rework purchase order

and transfer posting
The vehicle must be in

subcontracting stock
Deletes the subcontracting

purchase order and creates a
cancellation document for the
transfer posting
UGRE
Finish rework (goods receipt)
The vehicle must be in

subcontracting stock
Creates a goods receipt

The goods receipt is posted for
document with reference to the all the components to be
subcontracting purchase order provided in subcontracting
purchase order
UGRR
Rework: cancel goods receipt
Creates a cancellation
document for the goods receipt
for the subcontracting
purchase order
1.15 Processing Returns

Process
PUBLIC
Page 15 of 21
A vehicle that is sold and then returned to stock is usually resold using the normal sales process for new vehicles (see also:
Sales: Reservation, Quotation, Reservation Request, Inquiry and Sales: Sales Order). However, if the vehicle is classified as being a used vehicle, actions SPEU
and SOEU from the Trade-In process succeed the actions displayed above when the vehicle is resold.
Returns.
Actions
Action
Description
Prerequisites
RETU
Create return
Sales order
Creates return for a vehicle that A return can only be created

has already been sold
with reference to a sales order
and not with reference to an
outgoing invoice
You do not have to select all
the vehicles in the sales order
You have to define item
category, copy control and item
category determination
Notes
RELI
Create returns delivery
Return
Creates returns delivery for a

return to register the arrival of
the vehicle and to post the
vehicle to stock
REGI
Goods receipt for returns

delivery
Returns delivery
Posts goods receipt to the

blocked stock returns
RECM
Create credit memo for returns
Return
Creates a credit memo for the

return
REUS
Transfer vehicle from blocked

stock returns to unrestricteduse stock
Vehicle in blocked stock

returns
Posts vehicle from blocked

stock returns to unrestricteduse stock so that it can be
resold
1.16 Trade-In and Used Vehicle Sales

Process
The normal VMS sales process with delivery, goods

movements and outgoing invoice follows action SOEU.
Vehicles can be taken in part exchange/as a trade-in more than once.
Purchase Orders (MM-PUR-PO).
If you trade-in using a one-time vendor, the inbound invoice cannot be posted with transaction INIV but only with the SAP standard transaction.
Actions
(I) signifies an
Action
Description
CREA
Prerequisites
PUBLIC
Notes
See:
Page 16 of 21
CREA
POEU
Trade-in
GORE
Create goods receipt
CRPU
Create and trade-in vehicle
See:
Creating Vehicles
When you trade-in vehicles
that you have already sold as
an importer, you do not have to
perform this action.
Vehicle
Creates a normal purchase

order for the vehicles
In contrast to action ORD1, the
price and the vendor (also onetime vendor) have to be
entered manually in the
interface
A purchasing info. record

should not exist for the
vendor/vendors.
If a record does exist, you
must ensure (in the pricing
procedure) that the price
entered manually has priority
over and above the price in the
purchasing info. record.
See:
Goods Movements: GI, GR
CREA + POEU
(I)
SPEU
Used vehicle sales: determine The vehicle has been returned Overwrites the gross list price
price
to the importers stock due to
in the vehicle data with the
trade-ins or returns processing. resell price
The resale price is a manually
fixed price that is independent
of the configuration of the
vehicle
SOEU
Used vehicle sales: create

order
The vehicle has already been

sold once and has been
returned to stock by a trade-in
process or returns processing
Resale price (action SPEU)
PUBLIC
Creates a sales order for the

used vehicle and can overwrite
the entries for customer, end
customer and vehicle usage
This action can only be

performed for exactly one
vehicle.
This action is a very simplified

version of action CUOR and
numerous restrictions apply:
you cannot carry out
Returns Processing for sales
orders that have been created
using action SOEU. You
cannot make reservations if
you are using action SOEU.
Sales orders that have been
created with action SOEU
cannot be changed with action
CHCO but they can be deleted
with action DECO.
You should use a different
pricing procedure for pricing
than you use for action CUOR.
Background: condition type
VA00 (variant price) is
contained in the pricing
procedure fin the case of
CUOR, in other words, the
prices depend on the
configuration during pricing
(see also:
Create Variant Conditions for
Pricing). You should not,
however, use condition type
VA00 for action SOEU since
the price is independent of the
configuration here and
determined manually using
action SPEU. This resale price
is transferred as condition type
PR00 by default. You can
define a different condition type
for the resale price in BAdI
VLC_EXECUTE_ACTION,
method
DATA_CHANGES_BEFORE_
ACTION. You must then write
this condition type in
VLCACTDATA_CS-KSCHA.
If you want to be able to use
different pricing procedures for
CUOR and SOEU, you should
use different document types.
Both actions work with
document type TA (standard
order) by default. You can
change the document type in
BAdI
Page 17 of 21
VLC_EXECUTE_ACTION,
method
DATA_CHANGES_BEFORE_
ACTION. You can enter the
document type in
VLCACTDATA_CS-AUART.
1.17 Service Processing

Process
There are two options for service processing:

Processing only with a service notification, in other words, without a service order. This is the quickest type of service processing if no costs that have to be
settled are incurred.
Processing with a service notification and a service order. This is sensible if you have to plan and calculate materials, resources and work forces. If no
details are required for actions, measures, persons responsible etc., you can ignore the service notification and create a service order directly.
You can find further information in the standard documentation under
Service Object as Equipment,
Service Notification,
Service Order and
Processing Services .
Actions
(I) signifies an
Action
Description
Prerequisites
CREQ
Create equipment
Vehicle
Creates an equipment for a

vehicle and writes the
equipment number in the
vehicle data.
SMNO
Process service notification
Optional: equipment
Creates a CS service
notification with claim items
and organizational data and
allows you to change or
complete existing service
notifications. You can enter a
separate item with problem,
affected object part, reason for
claim, actions and measures
for rectifying the damage for
each claim.
If you enter the value X for user

parameter
VELO_SMNO_POPUP_MO
DE, you always branch
directly to the screen for
creating a new service
notification or, if a notification
already exists, to the screen
for changing this notification.
This is useful if you
fundamentally do not want to
allow more than one service
notification.
SMOR
Create service order
Optional: service notification
Creates a CS service order

with operations. Items in the
service notification become
operations in the service order.
You can propose planned
working times for the
operations.
The order can be released
automatically depending on
which settings have been
made in Customizing for CS.
If you enter the value X for user

parameter
VELO_SMOR_OPR_MODE,
exactly one operation will be
created in the service order.
The service notification items
are not copied.
SMCO
Confirm service order
Service order
Confirms actual working time

and used components to the
service order. Any number of
partial confirmations possible.
External services cannot be

confirmed.
SMIO
Create billing request for

service order
Service order
Creates a billing request for a

service order. The billing
request covers all confirmed
components and working times
The billing document has to be

created outside VMS (for
example, in collective
processing).
PUBLIC
Notes
Page 18 of 21
for this service order for which

no billing request yet exists.
SMOC
(I)
Create and confirm service

order
Optional: service notification
SMOR + SMCO
1.18 Special VMS Actions

Process
Actions
Action
Description
SOCD
Save customers desired

configuration
Prerequisites
SMOD
Change vehicle
CORR
Correct status (without check)
Internal action that, in contrast This action cannot be started

to the other actions, is not
manually using transaction
actually an action since it does VELO
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
HIDE
Exclude vehicle from search
Sets the vehicle attribute from

displayed 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
Defined values in VMS

Customizing for vehicle usage,
vehicle search area and
sharing level
Defined qualifiers in
Customizing and assignment to
action SMOD
PUBLIC
Notes
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
Allows changes to vehicle

attributes and qualifiers (see
also in VMS Customizing
under Enhancements
Program Actions and
Enhancements Define
Additional Data for Vehicles
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
The actions HIDE and SHOW

have no effect in themselves
only in combination with one of
the following two
implementations:
1. You can use the visibility
dependently of the VMS role
(dealer, importer) as parameter
when selecting vehicles from
the database (BAdI
VLC_SEARCH_ADAPTION)
Page 19 of 21
VLC_SEARCH_ADAPTION)
2. You can use the visibility
according to the selection in
Category Management (vehicle
filter) as parameter The second
option has the disadvantage
that the performance is not as
good, since many vehicles are
selected that are not needed
later
SHOW
Include vehicle in search
Sets the vehicle to

visible/displayed in the
vehicle attributes
CAMP
Assign sales campaign
Values for sales campaign

(transaction VELOC )
Sets the vehicle attribute

Sales campaign to a new
value
LCTN
Set vehicle location
Values for vehicle location in

Customizing for VMS
(transaction OVELO)
Sets the vehicle attribute

Vehicle location to a new
value and assigns the address
of the vehicle location to the
vehicle
SHMT
Confirm transit
STWO
Trigger Workflow event
Organizational structure
Tasks
Only useful as part of an interlinking 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
VMS Customizing for

Messages 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
under
Message/Output Control
(CA-GTF-BS) and in the
documentation for the
appropriate VMS Customizing
activities.
ADDO
Assign business documents
Assigns documents to a
vehicle
You can display the stored

documents in transaction
VELO (tab page Details ,
screen Vehicle Data .
Pushbutton
)
You can find further information
under
Business Document
Navigator
The point of this action is to

trigger pricing again in the
sales order (due to assigned
sales campaign) There are two
options:
1. You can add the field as an
object characteristic to the
vehicle configuration (see:
Adding Object Characteristics
to the Configuration)
2. You can use the options for
flexible enhancements to SD
pricing
Example for an action that only Actions such as these, for

changes the status and does
example Confirm purchase
not create any documents
order can be defined in
Customizing
1.19 Warranty Processing

Process
These three actions link the applications

Vehicle Management System (IS-A-VMS) and
Warranty Processing (IS-A-WTY). They serve to create the master data (
PUBLIC
Equipment, Master Warranty,
Page 20 of 21
Measuring Points) that is necessary to carry out the

exists for a specific vehicle or not.
Warranty Check in
Warranty Processing, in other words, to check automatically whether a warranty still
Actions
Action
Description
Prerequisites
CREQ
Creates equipment for the

vehicle
Vehicle
Creates an equipment for a

vehicle and writes the
equipment number in the
vehicle data.
WRTY
Assign master warranty
Equipment for vehicle, master

warranty, BAdI
Assigns a master warranty to

equipment that has been
created using action CREQ
MEAS
Assign measuring points
Equipment for vehicle,

reference equipment, BAdI
Assigns measuring points to

the measurement positions
and warranty counters of the
reference equipment for
equipment that has been
created using action CREQ
PUBLIC
Notes
Page 21 of 21

Vms Content 8

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Vms Content 8

Hochgeladen von

Copyright:

Verfügbare Formate

Actions

PDF download from SAP Help Portal:

1.1 Working with Actions

1.2 Performing Actions in a Batch

Creating Parameter Variants

directly if you want to display all existing parameter variants.

Limit your selection and then choose

to create a new parameter variant.

Performing Actions with Parameter Variants in Batch Mode

if you want to start the batch job immediately.

. The screen for scheduling jobs appears. Enter when you

1.3 Make-to-Stock Scenario:

seen by other dealers.

Who does this?

Create planned vehicle (without

Change configuration of planned

Allow value assignment for vehicle and Importer

Change purchase order

Confirm purchase order (action not

OEM via EDI

Allow vehicle for search

OEM via EDI

Create goods receipt (also possible

Create inbound invoice (also possible

Create sales order and exclude vehicle Dealer

Change sales order

Assign end customer

Create goods issue

Create outbound invoice

1.4 Make-to-Order Scenario:

Who does this?

Create vehicle and sales order

Create vehicle, purchase order and

Change sales order

Assign end customer

Create purchase order

Change purchase order

Change sales order and purchase

Confirm purchase order (action not

OEM via EDI

OEM via EDI

Create goods receipt (also possible

Create inbound invoice (also possible

Start rework (purchase order and

Finish rework (goods receipt)

Create goods issue

Create outbound invoice

You can save a customer configuration using action

You can use the icon

in the vehicle history to branch to the transactions named above.

1.5.1 Handling Configurations

Subcontracting Purchase Order Configuration

1.5.2 Actions and Configurations

Create vehicle (values

A new vehicle configuration is

Delete vehicles without

Vehicle configuration is deleted

Create purchase order

Purchase order configuration is

Change purchase order

Purchase Order Configuration

Purchase order configuration is

Delete order item

If a sales order exists, the