8/17/2021

SAP for Automotive

Generated on: 2021-08-17 13:43:43 GMT+0000

SAP ERP Support Package Versions | 6.0 EHP8 SP13

PUBLIC

Original content: https://help.sap.com/viewer/15f6005df5a343d096f63b554e47e14a/6.18.13/en-US

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product documentation. The
information included in custom documentation may not re ect the arrangement of topics in the SAP Help Portal, and may be missing important
aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/viewer/disclaimer.

Vehicle Management System (IS-A-VMS)

Purpose
The Vehicle Management System (VMS) is an application for the Automotive industry. It supports, in the area of Sales & Services, the business
processes that you require as vehicle importer when dealing with your original equipment manufacturers (OEMs) and your dealers in new and used

This is custom documentation. For more information, please visit the SAP Help Portal 1
 8/17/2021
vehicle sales . VMS offers you complete integration of all the relevant processes such as procurement, sales, rework, returns processing, trade-in
and service processing. It also supports the archiving of vehicle data. In other words, it allows you to react exibly to customers’ requirements in
the area of production (using the “pull strategy”) and fast delivery times with reduced warehouse stock and sales/distribution costs.

For the vehicle importer , VMS serves as a central tool for managing, procuring, sales/distribution and tracking of vehicles. Your dealers use it as a
workplace for con guration, searching, purchasing, and tracking of vehicles for your end customers. The dealers can log in to your system remotely
via the Internet and access your data. You do not require your own SAP system for this. You only need an Internet browser, via which you work with
a simpli ed VMS internet interface .

You can enhance or change this internet interface, for example, if you wish to adapt it to your suit your corporate design.

 Note
The word importer is used as an umbrella term to include organizations such as distribution centers, logistics centers, OEM-owned sales
organizations and such like. For reasons of ease, however, the word importer is used in this documentation.

The following graphic shows the use of VMS in vehicle procurement, vehicle sales, and service:

Integration
VMS is completely integrated into the SAP application components MM, SD, CS and FI/CO .

For vehicle con guration in VMS, you can use SAP Internet Pricing and Con gurator (SAP IPC) or the characteristic value assignment
screen . The characteristic value assignment screen is activated in the standard.

You can implement VMS together with SAP Advanced Planning and Optimization ( SAP APO ) as the planning system and with SAP
Business Information Warehouse (SAP BW) as the reporting system for analysis and evaluation purposes. You can use the following
functions in SAP APO : cooperative demand planning and characteristics-based forecasting.

Dealers can use a Web Dynpro-based user interface.

Furthermore, there are two interfaces to further external SAP applications ( SAP TREX , SAP SCEM , SAP CRM ); these applications can be
used optionally.

The following graphic displays the complete integration from demand planning to evaluation and analysis.

This is custom documentation. For more information, please visit the SAP Help Portal 2
 8/17/2021

Features
Vehicle Master Data

You can manage all your vehicles centrally in a vehicle data pool and thus make them available to yourself and your dealers. You can store
both business and technical master data for a vehicle in this data pool. The business details include data such as status of the vehicle
(created, ordered and so on) or the availability of the vehicle (available, reserved, sold etc.). The technical details include data such as the
individual features of the vehicle (horsepower, motor type, color etc.) as they have been de ned in SAP variant con guration. For more,
general information on standard variant con guration functions, see: Variant Con guration .

Vehicle Search

There are various comprehensive functions which both you and your dealers can use to search for vehicles in the data pool. Search criteria
are, for example, vehicle data, con guration, vehicle status, posting documents or end customer/consumer . The basis for the search is
always a speci c vehicle model or a selection of models. These models must have been created as con gurable materials in the SAP system
(see also: Constructing a Vehicle Con guration

A lter concept ensures that dealers who log in to your system only see vehicles that you have assigned to them or released for their
viewing.

Execution of Actions

You can call and execute actions for a vehicle easily and quickly from VMS. By an action we mean a business function that affects the
procurement of a vehicle at the manufacturer by the importer or the sale of the vehicle to the dealer. Examples are: create or change
vehicle, create purchase order (at manufacturer), create sales order/delivery/outgoing invoice (for dealer) and post goods receipt/goods
issue.

A large part of the actions delivered by SAP are based on the SAP standard transactions: they are delivered in a separate and easy-to-use
interface but with the complete functionality.

The posting documents that are created by these actions are also SAP standard posting documents that are stored in the application
components MM, SD, CS or FI/CO in the SAP system.

Apart from these general business actions, there are also Special VMS Actions , for example, actions for making reservations, actions that
hide or display vehicles for other dealers, actions for changing vehicles, for setting a vehicle location or for assigning a sales campaign.

You can enhance the actions that are delivered to suit your own requirements or program your own actions . The action concept is on a
modular basis and exible so that you can adjust it at any time to suit changes in your business processes.

There is a one screen transaction (based on the vehicle as object) with an integrated interface for vehicle master data, vehicle searches and
actions (see: Transaction Codes for VMS ). To access this transaction, choose Logistics LogisticsExecution Vehicle ManagementSystem Vehicle
Manager or transaction VELO from the SAP Easy Access screen.

Vehicle Procurement and Sales

Purpose

This is custom documentation. For more information, please visit the SAP Help Portal 3
 8/17/2021
The typical scenario when using VMS revolves around the procurement and sale of new vehicles . As importer, you procure vehicles from one or
more manufacturers and sell them to your dealers or directly to large end customers, for example, rent-a-car companies.

This process is supported by VMS in both directions:

Pull strategy : the requirement/sale can trigger procurement ( MTO = Make-to-Order , make-to-order production)

Push strategy : procurement can come before sales ( MTS = Make-to-Stock , make-to-stock production)

The technical and business integration of all processes and business partners in VMS allows you to shorten delivery times and – in the case of MTO
– consider customer requirements and therefore increase customer satisfaction.

Prerequisites
VMS has been installed in your system; your dealers have access to this system via Internet. Your system is linked to the manufacturer
(OEM) systems via interfaces.

You have created the master data required for VMS.

Process Flow
1. The end customer would like to purchase a vehicle with speci c features and approaches one of your dealers.

2. The dealer searches your stock using the Internet to see if an appropriate vehicle exists.

3. If yes, the dealer enters additional characteristics for the vehicle, which are then installed later in the course of local rework activities (for
example, installing a radio, dog grate, telephone, different tyres etc.). He/she then determines the price for the desired con guration and
creates a sales order in your system for this vehicle (scenario: make-to-stock production).

If no, the dealer also creates a sales order, but not for an existing vehicle. He/she creates a sales order for the customer’s dream car. The
importer then creates a purchase order for this vehicle at the manufacturer’s and thus triggers production (scenario: make-to-order
production).

4. Status updates per EDI from the manufacturer give you and the dealer up-to-date information on the status of the vehicle, in other words,
information on the progress in production or delivery. The dealers have access to this information via Internet and can forward the
information directly to the end customers.

5. VMS supports vehicle procurement and sales, including all the postings involved and oversees the entire business process until the time
when your dealer delivers the desired car to the end customer.

The following graphic displays which documents are exchanged via VMS between OEM, dealer and importer during vehicle procurement, vehicle
sales and service.

This is custom documentation. For more information, please visit the SAP Help Portal 4
 8/17/2021

Vehicle

De nition
A vehicle is a business object (BUS1200) in the SAP system.

A vehicle is the result of using a create action in VMS to create a vehicle for a vehicle model. It is therefore, an instance of a vehicle model , in other
words, an individual object. A con guration is always created for a vehicle; the characteristics in the con guration may have not yet had any values
assigned to them, partly have had values assigned or have had all values assigned. You can identify the vehicle by its vehicle number and de ne it
further using a batch, valuation type and, where appropriate, an equipment number.

Use
The vehicle is a central object in the Vehicle Management System. Vehicle searches and actions for the business processes involved always relate
to at least one vehicle. The only exception is the function Assignment of Vehicles to Sales Documents , which does not start from the vehicle but
from the sales document.

Structure
Assigning Values

When you create a vehicle it receives an internal vehicle number . This number is the also the batch number and the valuation type number . Each
vehicle, therefore, has its own batch and valuation type. You can display valuated stock using transaction MMBE Stock Overview .

 Caution
You are recommended to use valuation for a single batch with VMS. The valuation of sales order stock is not supported by VMS.

 Note
Create a purchasing info. record manually for each vendor. Leave the eld Valuation type under Purchasing organization 1 empty. Do not use
the Customizing setting (Customizing for Materials Management ) under Purchasing Environment Data De ne Default Values for Buyers ,
indicator InfoUpdate – Purchase order ), which de nes that a purchasing info. record is created automatically when a purchase order is
created. The eld Valuation Type is lled when this Customizing setting has been made. This leads to problems when you want to create
vehicles.

You can nd further information in the documentation for Logistics-General under Batch Management (LO-BM) , especially Valuation for a Single
Batch .

Vehicle Data

A vehicle is characterized by its vehicle data (vehicle master, see table VLCVEHICLE). The following belong to the vehicle data:

GUID Global Unique Identi er. A 22-character technical key assigned by the system
when the importer creates the vehicle.

This key is unique and therefore also differentiates between vehicles that
have been created in different systems. The GUID serves only internal
technical control purposes and does not appear on the interface.

Internal vehicle number An identi cation number from an internal number range. It is assigned by the
system when the importer creates the vehicle.

The vehicle number is created independently of the vehicle identi cation

number (VIN).

External vehicle number Identi cation number assigned by the manufacturer (for example, production
number, vehicle number)

Vehicle identi cation number (VIN) 17-character number that identi es a vehicle and is created when the vehicle
is assembled, for example, during the assembly process in the
manufacturer’s production system.

The VIN is an international standard.

This is custom documentation. For more information, please visit the SAP Help Portal 5
 8/17/2021
Batch (only for vehicles that can be assigned values) A vehicle represents exactly one batch . The batch number is the same as the
internal vehicle number (see above).

Valuation type (only for vehicles that can be assigned values) Each vehicle has a valuation type ( Valuation for a Single Batch ). The
valuation type number is the same as the internal vehicle number (see above).

Plant Location, organizational unit of importer

Storage location Actual storage location of the nished vehicle in the importer’s plant

Vehicle Model Basic type of a vehicle that can be varied.

Vehicle models are created as con gurable materials in the SAP system.

A vehicle model can be a general vehicle type or a vehicle type for which
speci c characteristic values have been prede ned using object
dependencies.

Con guration Characteristics and assigned characteristic values (for example: color: blue;
special features: radio, air conditioning).

Primary Action Control , primary status + date + time, secondary action The action control de nes (in an action matrix) which actions can follow one
control, secondary status + date + time another when dealing with vehicles and which vehicle status change is
connected with this.

Example: a vehicle that the importer has ordered from the manufacturer
receives the status Ordered . After the manufacturer has con rmed the
purchase order, in other words has performed the action Con rm purchase
order , the status changes automatically to Purchase order con rmed .

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 (ordering
the vehicle from the manufacturer) and the secondary action control the sales
process (sale of the vehicle to the dealer). However, a subdivision into a
logistics and a nancial process is also possible.

Availability status Status that displays whether the vehicle is available for sale (for example:
Not released, Available, Reserved, Sold ).

The status changes automatically depending on the action you perform.

The availability status can remain the same for a series of different vehicle
statuses. Example: a vehicle that receives the statuses Vehicle created ,
Vehicle ordered , Purchase order con rmed and Transit con rmed retains
the availability status Not released .

The availability status is only for information purposes and has no controlling
effect.

Address Address (from central address management) where the vehicle is to be found.

This address can be the address of a vendor, customer, end customer or of

any other location de ned in Customizing for VMS.

Production date (time stamp) Date on which the vehicle is produced.

The importer enters the planned production date that he has agreed on with
the manufacturer in the appropriate eld when the vehicle is created or the
vehicle data is changed. The manufacturer updates this date regularly during
the production process using data transfer per external interface. The
production date thus changes from being a planned date to being an actual
production date.

This time stamp contains data on the construction year and month, which are
required for the trade-in.

Planned delivery date (time stamp) Date on which the vehicle is planned to arrive at the dealer or end customer.

The system determines this date automatically from the appropriate

Customizing settings.

Gross list price + currency Price that results from the vehicle con guration.

This price is independent of business partner-speci c discounts.

The gross list price changes if the vehicle con guration is changed later.

This is custom documentation. For more information, please visit the SAP Help Portal 6
 8/17/2021
You must create an organizational role with the key GROS (see: Calculating the
Gross List Price Using Organizational Roles )if you want the system to be able
to calculate the gross list price.

Vehicle usage Planned usage for the vehicle, for example, use as end customer vehicle, in
eet sales, as demonstration car and so on.

This data can be used to help you prioritize cars when processing purchase
orders and can be transferred to the manufacturer.

Sales campaign Campaign for a speci c length of time for the sale of a speci c vehicle model
or con guration at a reduced price. You can assign a sales campaign to a
vehicle using the action CAMP .

Examples: sale of old models for which the new model is already on the
market, sale of old stock with unusual con gurations etc.

You can trigger special pricing functions in the sales documents of vehicles
that belong to a sales campaign. There are two options:

You can add the eld as an object characteristic to the vehicle

con guration (see: Adding Object Characteristic to Con guration )

You can use the options for exible enhancements to SD pricing

Visibility Indicator in the vehicle table that can be used to in uence whether a vehicle
can be seen by dealers during the vehicle search or not.

This indicator is controlled by the actions SHOW and HIDE .

There are two options for removing a vehicle form the hit list of the vehicle
search:

You can use the visibility dependently of the Organization Role as

parameter when selecting vehicles from the database (BAdI
VLC_SEARCH_ADAPTION)Example: a VMS user at the importer’s can
display all the vehicles but a VMS user at the dealer’s can only
display the vehicles that are visible for all the dealers and additionally
all the vehicles (also not visible) for which he or she has created a
sales order or offer or for which, for example, he or she has been
assigned as customer during the reservation process.

You can use the visibility according to the selection in Category

Management as parameter. This second option has the disadvantage
that the performance is not as good, since many vehicles are selected
that are then ltered out later.

Customer Business partner to whom the vehicle is sold.

This is usually the dealer. It may, however, also be an end customer, for
example, a car rental or hire company that wants to buy an entire eet of cars
from the importer, or an employee of the importer who wants to buy a vehicle
directly from the importer.

You can manage one-time customers, for example the employees of the
importer, using a CpD one-time or suspense account in the customer master
record.

End customer End customer for the vehicle.

The data for the end customer are stored in the functions for business partner
management. You can assign an end customer by using action BUPA or by
using the function End Customer , which is available in several actions.

You can assign multiple end customers to a vehicle by using action ADCU .

Dealers can create end customer data; this end customer data is then
assigned to the appropriate dealer and can only be viewed by him or her.

Vendor Business partner from whom the vehicle is procured.

This is usually the manufacturer (OEM). In cases where there is multi-level

procurement, it may be an intermediate vendor, for example a distribution
center.

This is custom documentation. For more information, please visit the SAP Help Portal 7
 8/17/2021
When a used vehicle is being exchanged for cash, the vendor can also be, for
example, a rent-a car company or any other person. Such a business partner
may also be managed at the same time as a customer in the system.

You can manage one-time vendors, for example the previous owner when
exchanging a vehicle for cash, using a CpD one-time or suspense account in
the customer master record.

Vehicle Search Area Geographical or organizational area in which vehicles are made available and
searched for.

This area de nes the outermost limit within which a vehicle search can take
place. You can assign a vehicle search area using action SMOD .

A vehicle search area can include more than one sales organization.

Each vehicle can only belong to exactly one vehicle search area.

You can de ne rules for the vehicle search and search areas in Category
Management and thus represent a uniform policy. Prerequisite: all the
vehicles within one vehicle search area are technically compatible and
allowed in every other geographical region.

Sharing Level In a scenario in which more than one dealer, SD organization etc. can access
the same vehicle stock (de ned by the vehicle search area), you can increase
or decrease the availability of a vehicle for other dealers, sales organizations
etc. by using the sharing level.

The sharing level is used as a parameter in Category Management .

Created by System user who created the vehicle.

Registration date

Counter/meter reading + unit

You can display this vehicle data . Choose transaction VELO (Vehicle Manager), perform a vehicle search, choose a vehicle and then choose the tab
page Detail .

The vehicle data is the result of actions that have been performed for a vehicle. The data is enhanced and updated continuously. Example: the
following data is entered and determined on creating a vehicle: internal vehicle number, plant, vehicle model, con guration, primary action control,
primary status, availability status, gross list price and, where appropriate, production date and vendor. When the purchase order is created, this
data is completed with entries for the vendor and the location.

Most of the vehicle data is also available as a parameter for the vehicle search .

 Note
You can de ne further vehicle data according to your requirements. To do this, choose Customizing for the Vehicle Management System
(VMS) Enhancements De ne Additional Data for Vehicle (transaction OVELO4). If you are dealing with quali ers in the additional table, you
can display the data separately (transaction VELO, tab page Detail , screen Vehicle Data , function Addnl Data ). If you are dealing with
vehicle attributes in the vehicle table, they are displayed as elds in the lists of the vehicle overview and the vehicle details. You can nd further
information under Programming Your Own Actions .

 Note
You can enter and store documents for each vehicle (action ADDO Assign documents ) and display them (transaction VELO , tab page Detail ,
screen Vehicle Data , pushbutton Documents ). You can nd further information under Business Document Navigator

Master Data

Use
Every vehicle model that is managed with VMS is described by a con gurable material and the appropriate class . Before you can work with VMS,
you must rst maintain characteristics, classes, variant conditions, object dependencies and material master records.

Furthermore, you have to create speci c basic and Customizing data.

This is custom documentation. For more information, please visit the SAP Help Portal 8
 8/17/2021
Integration
The master data that you require belongs to the following SAP applications:

Material Master Record

Classi cation System

Variant Con guration

Pricing (SD and MM)

Business Partner Administration

Features
Vehicle model with material master and con guration

Vendor and customer , in general manufacturer and dealer

End customer as customer of the dealer

VMS role for centralized control of VMS (organization role, vehicle model, con guration role)

Action control for representing the business process

Vehicle IDoc for transferring vehicle data between manufacturer and importer

Vehicle Model

De nition
A vehicle model is a basic type of vehicle that can be varied.

Use
Vehicle models for the basis form the vehicle search . You search for vehicles with a speci c con guration or speci c other data within one or more
vehicle models.

Furthermore, the vehicle models form the basis for creating vehicles . Each vehicle that you create is an instance of a speci c vehicle model.

Structure
Vehicle models are created in the SAP DIMP system as con gurable materials (material type VEHI = con gurable vehicle). Classes with
characteristics are assigned to the materials.

A vehicle model can be a general vehicle type or a vehicle type for which speci c characteristic values have been prede ned using object
dependencies.

 Note
VMS does not use material variants.

 Recommendation
It is recommended that you de ne vehicle models generally so that con guration changes can be made during the sales process without
having to change the vehicle model.

Example: you have de ned the vehicle model SAPcar . If the dealer receives a quotation for a SAPcar hatchback but then decides on a SAPcar
limousine after all, this change is possible within the vehicle model SAPcar . However, if you have de ned the vehicle model on the level of
SAPcar hatchback and SAPcar limousine , in other words, you decide to work with speci c characteristics on this level, changing the quotation
would mean having to change the vehicle model, too. The material, however, cannot be changed in the documents. You would therefore have to
cancel the quotation and create a new one.

This is custom documentation. For more information, please visit the SAP Help Portal 9
 8/17/2021
On the other hand, you should not de ne vehicle models too generally . When you create a vehicle that can be assigned values, the existing
material master record for the vehicle model is extended by a valuation type. This results in the material master being locked for a while. In this
period of time, no other dealer can create a vehicle for this vehicle model. The same applies to goods receipt and goods issue postings. If the
vehicle model has been de ned very generally, the material master record threatens to become very large, which ultimately means bad
performance.

Example: you have de ned the vehicle models car and lorry . Every time you create a new car, the material master record is locked for a short
while and extended.

Example

Vehicle model SAPcar

Characteristics
Exterior colour

Interior colour

Motor

Number of doors

Number of seats

Number of gears

Special features (radio, air-conditioning, GPS, central locking, seat

heating, sunroof)

See also:

Creating a Vehicle Model

Constructing a Vehicle Con guration

Creating a Vehicle Model

Use
Every vehicle model that is managed with VMS is described by a con gurable material and the appropriate class . Before you can work with VMS
you must have created material master records for the vehicle models.

You can nd further information in the documentation for Logistics – General under Material Master (LO-MD-MM) .

Prerequisites
Within the project, you have decided on which level you want to de ne vehicle models – whether as a general vehicle type or as a vehicle type for
which some characteristics have already been prescribed via object dependencies.

Procedure
The following only describes elds in the material master record that you require and that are evaluated in VMS. All other required elds are elds
that the standard system requires and not VMS. Identical elds that appear in more than one view are mentioned each time they appear.

1. Choose transaction MM01 in order to create the material master for a vehicle model. Enter plant, sales organization and distribution
channel.

2. Choose the material type for a con gurable vehicle ( VEHI ).

Similar to the material type for con gurable materials ( KMAT ), this material type de nes that the vehicle model can be con gured and,
furthermore, (unlike the material type KMAT ), it can be purchased/bought in.

3. Make entries in the elds as follows:

This is custom documentation. For more information, please visit the SAP Help Portal 10
 8/17/2021

View Field Field Value

Basic Data 1 Base unit of measure Piece/unit (or the unit for which has been
de ned – in transaction CUNI – that it is
internally and automatically converted to
piece/unit)

Division

Item category group VMS0 (vehicle VMS) (see: Special VMS Master
Data in Customizing for Sales and Distribution )

Basic Data 2 Material is con gurable Set indicator

Classi cation Class type 300 (variant class), enter model class

Optional: 001 (material class), enter family

class (see: Constructing a Vehicle Con guration
)

Sales and Distribution: Sales Organization 1 Base unit of measure Piece/unit (or the unit for which has been
de ned – in transaction CUNI – that it is
internally and automatically converted to
piece/unit)

Division

Sales and Distribution: Sales Organization 2 Across different distribution channels: general VMS0 (Vehicle VMS)
item category group

Dependent on distribution channel: item VMS0 (Vehicle VMS)

category group

Sales and Distribution: General/Plant Batch management requirement Set indicator (see: Vehicle )

Availability check No check

Purchasing Base unit of measure Piece/unit (or the unit for which has been
de ned – in transaction CUNI – that it is
internally and automatically converted to
piece/unit)

Batch management requirement Set indicator

Manufacturer Optional.

If you enter a Manufacturer here, it is copied as

vendor to the vehicle data. You can overwrite it
in VMS.

MRP 1 MRP type No MRP

Accounting 1 Base unit of measure Piece/unit (or the unit for which has been
de ned – in transaction CUNI – that it is
internally and automatically converted to
piece/unit)

Division

Value assignment/valuation category X (automatic, batch)

If you want to de ne valuation category X for a

newly created plant, you may rst have to enter
the following in Customizing for Materials
Management under Valuation and Account
Assignment Split Valuation Activate Split
Valuation Local De nitions Categories and
activate Organizational Units: Valuation
Category X for the new plant.

Valuation class 3100 (trading goods)

Price control Moving average price

4. Save your entries.

This is custom documentation. For more information, please visit the SAP Help Portal 11
 8/17/2021

Special VMS Master Data in Customizing for Sales and Distribution

Item Category Determination

One item category is basically used in the sales order.Item category determination is controlled by the sales document type and the item category
group . You can nd the item category group in the material master record for the view Sales and Distribution: Sales Organization 2 .

I tem category group VMS0 ( Vehicle VMS ) is delivered for VMS as standard, which links to the special VMS item category VTAC that is also
delivered as standard.

Item category VTAC differs from the standard item category TAC by billing relevance “B”. VTAC can be billed related to the order, in other words,
the billing document can be created as soon as the sales order has been created.

If you enter item category group VMS0 in the material master record (see also: Creating a Vehicle Model ). You still have to copy the entries for the
sales document types AF, AG and RE for the item category 0002 to the VMS item category VMSO.

You can also create your own item category groups and item categories. To do this, choose the following activities in Customizing for Sales and
Distribution (in the given order):

1. 1. Sales Sales Documents Sales Document Item De ne Item Category Groups

2. Sales Sales Documents Sales Document Item De ne Item Categories

3. Sales Sales Documents Sales Document Item Assign Item Categories

 Note
If you decide to use your own item category, you should use the existing item category VTAC as a template to copy from as far as
possible. Then check and test all the settings you have copied, such as copy control and statistics updates.

Determining the Requirement Type

In VMS, the requirement type is determined via the transaction. Check the settings in Customizing for Sales and Distribution under Basic
Functions Availability Check and Transfer of Requirements Transfer of Requirements Determination of Requirement Types Using Transaction.

Determination of the requirement type via the transaction overrides determination via the strategy group (view MRP 3 ) or the MRP group (view
MRP 1 ) in the material master. Check the Customizing settings for Production under Production Planning Master Production Scheduling Planned
Independent Requirements Planning Strategy De ne Strategy.

Requirement type 041 (order/delivery requirement) is normally determined for item category VTAC . Requirement type 041 links to requirements
class 041 . Check the Customizing settings for Sales and Distribution under Basic Functions Availability Check and Transfer of
Requirements Transfer of Requirements De ne Requirements Types .

No account assignment category has been de ned in requirements class 041 since VMS works with individual batch valuation. Check the settings in
Customizing for Sales and Distribution under Basic Functions Availability Check and Transfer of Requirements Transfer of Requirements De ne
Requirements Classes..

 Note
Although account assignment category E is often used for con gurable materials, this is not possible for VMS since the vehicles are not
managed as sales order stock.

Constructing a Vehicle Con guration

Use
If you want to be able to con gure a vehicle in VMS, you have to maintain characteristics, classes, variant conditions and object dependencies for
the basic vehicle model .

For more information, see the documentation for Logistics – General or the documentation for Cross-Application Components .

Variant Con guration (LO-VC)

This is custom documentation. For more information, please visit the SAP Help Portal 12
 8/17/2021
Classi cation System (CA-CL)

Prerequisites
Within the project, you have decided how you want to de ne vehicle models – whether as a general vehicle type or as a vehicle type for which some
characteristics already exist.

Procedure
1. Optional: de ne a characteristics group . To do this , choose Classi cation System Characteristics De ne Characteristics Groups in
Customizing for Cross-Application Components .

It is advisable to create one or more characteristic groups for the application VMS in order to group the characteristics created for VMS
and differentiate them from other characteristics used in the DIMP system. You can then search quickly and easily for all the VMS
characteristics by entering the characteristic group and using the matchcode search. You can, for example, create a single characteristic
group for all VMS characteristics or a characteristics group for each set of characteristics for a speci c vehicle group.

2. Create vehicle characteristics with characteristic values in the characteristic group (transaction CT04).

Enter a description and, if required, a characteristic group , status (must be released ), data type , number of characters , and values .

3. Create a class with class type 300 ( variants ) for VMS and assign the vehicle characteristics to this class (transaction CL04). If you are
dealing with groups of similar vehicles, also create a model family class 001 ( material class ) and assign vehicle characteristics to this
class.

Add the characteristics that are the same across several variant classes (within one vehicle family) to this family class. This allows you,
when searching for a vehicle, to search several vehicle models for speci c characteristic attributes, for example, search for all red vehicles
irrespective of vehicle model.

4. Optional: group the characteristics together in order to display them on the interface on their own tab page or in their own le
(transactions CU50 and CL30N).

Transaction CU50: Call this transaction and choose Value Assignment Interface Design Characteristic Grouping. This transaction allows
you to group characteristics in the SAP Internet Pricing and Con gurator (SAP IPC) and in the characteristic value assignment screen into
les. If you want to use this function, you must have entered a name in the interface design eld on the con guration initial screen tab in the
con guration pro le.

Transaction CL30N: Call this transaction and choose Value Assignment Characteristic Grouping. The characteristics are then displayed on
different tab pages when you search for vehicles in VMS.

5. Create material master records for your vehicle models and enter the classes in the material master (see: Creating a Vehicle Model ).

6. Create a con guration pro le for the vehicle model you have created for class type 300 (transaction CU41).

The con guration pro le allows you to create object dependencies for the vehicle model and make additional settings that are not possible
in the material master record. You assign speci c pricing characteristics to the con guration characteristics of the vehicle model in the
object dependency functions (see: Creating a Variant Condition for Pricing ).

Result
The con guration data is now complete and available in the VMS in the Vehicle Search ) and in the Characteristic Value Assignment Screen .
However, this data is not available to you in SAP IPC until you have downloaded it to the IPC system.

 Note
You can add object characteristics to the vehicle con guration (transaction VELOOBJC), for example, the characteristic sales campaign . For
more information, see the documentation for the Classi cation System under Reference Characteristics and in the VMS documentation under
Adding an Object Characteristic to a Con guration .

Creating a Variant Condition for Pricing

Use
Pricing in VMS is based on the condition technique .

This is custom documentation. For more information, please visit the SAP Help Portal 13
 8/17/2021
In the organizational role GROS , you can de ne which pricing procedure should be used in vehicle con guration to determine the price.

We recommend using the standard pricing procedure RVAA01 (delivered by SAP) as the default value for the pricing procedure. However, you can
enter your own pricing procedure as the default.

There are three types of price:

Gross listed price (action CREA Create vehicle ) as list price for the con gured vehicle without dealer discounts and other discounts

MM price (action ORD1 Create purchase order ) and SD price (action CUOR Create sales order )

SD and MM prices are formed from the gross price , the variant prices for the individually con gured characteristics and, where applicable,
the discounts.

For more information, see the documentation for Sales and Distribution and Materials Management under:

Pricing and Conditions (SD)

Conditions and Price Determination (MM-PUR-VM)

Prerequisites
You have de ned pricing procedure RVAA01 (see above) as the default value.

Procedure
This procedure only describes a very simple example as a guide for creating variant conditions. Variant conditions can be very complex.

1. Create gross prices for the vehicle that has not been con gured – once in sales and once in purchasing.

Sales: transaction VK11, condition type PR00, enter key combination material with release status : sales organization , distribution
channel and material .

Purchasing: transaction MEK1, condition type PB00, enter key combination material info. record : enter vendor , material and
purchasing organization .

2. Create object characteristics for pricing in your characteristics group – once in sales and once in purchasing (transaction CT04) and assign
them to your class (transaction CL04).

These characteristics must have multiple values and are not allowed to be displayed. The characteristics do not have any values.

Enter the following data on the tab page Additional Data :

for characteristics in sales: table name SDCOM (structure which the sales order accesses), eld name VKOND

for characteristics in purchasing: table name MMCOM (structure which the purchase order accesses), eld name VKOND

3. Create a relationship (transaction CU01 and enter a description, the status as released and, if required, a dependency group and the
dependency type/relationship type as procedure). Link the con guration characteristics to the price characteristics using object
dependencies.

 Example
Example:

$SELF.SD pricing characteristic = 'Variant condition for con guration characteristic_1 and characteristic value_1' IF con guration
characteristic_1 EQ 'characteristic value_1'

You must include the characteristic values in inverted commas. Each expression must be completed with a comma, except the last one.

 Caution
If you have created the key for the variant con guration with small letters, you must also use small letters for the object dependencies.
Likewise capital letters.

For more information, see the Basis documentation under Dependency Syntax: General Rules .

You can also use variant tables to link the con guration characteristics to the price characteristics.

This is custom documentation. For more information, please visit the SAP Help Portal 14
 8/17/2021
4. Create a variant condition with a price for this characteristic value for each con guration characteristic and each possible value – once in
sales and once in purchasing.

Sales: transaction VK11, condition type VA00, enter key combination variants : sales organization , distribution channel and material .

Purchasing: transaction MEK1, condition type VA00, enter key combination variants for info. record : vendor , material , purchasing
organization and info. record category .

5. Assign the dependency to the con guration pro le (transaction CU42).

Result
The pricing data is now complete and is available in the Characteristic Value Assignment Screen . The data is not available in the IPC until it has
been downloaded, however.

Adding an Object Characteristic to a Con guration

Use
An object characteristic is not a con guration characteristic but rather a characteristic that is created with reference to a table . In VMS, this can
be the vehicle table VLCVEHICLE or the additional data table VLCADDDATA. The vehicle table contains the standard vehicle data and additional
vehicle data that you have created as vehicle attribute and assigned to the vehicle table. The additional data table is a separate table that also
contains vehicle data, however only the data that you have created as quali ers. Attributes and quali ers are the same as far as business is
concerned, but differ in their technical realization.

You can nd further information on object characteristics in the documentation for the Classi cation System under Reference Characteristics and
further information on additional data and the appropriate tables in the documentation for the IMG activity De ne Additional Data for Vehicle.

If you add an object characteristic to the con guration as described below, you can store object dependencies for this object characteristic. This
may be useful, for example, if you want to link speci c sales campaigns to discounts.

Procedure
1. Create the desired object characteristic in your characteristic group (transaction CT04) and assign it to your class (transaction CL04).

No values are assigned to this characteristic.

Enter the following data on the tab page Additional Data :

for a characteristic with reference to the vehicle table: table name VLCVEHICLE , < eld name of desired eld> (example: sales
campaign: eld name CMPGN )

for a characteristic with reference to the additional data table: table name VLCADDDATA , eld name QAUSP

2. Add the characteristic to the con guration (transaction VELOOBJC).

Enter the table, eld and characteristic name again for each object characteristic and de ne whether the characteristic should be displayed
on the interface in the Vehicle Manager or not.

In this table you have to specify which quali er you want to use (for a characteristic with reference to the additional table). Enter the name
of the quali er in the eld Field name . You can nd this number in Customizing for VMS under Enhancements De ne Additional Data for
Vehicle De ne Quali ers (transaction OVELO4).

Vendor and Customer

Use
The customer is the business partner to whom the vehicle is to be sold (debtor).

This is usually the dealer in the importer scenario supported by VMS. It may, however, also be an end customer , for example, a car
rental/hire company that wants to buy an entire eet of cars from the importer, or an employee of the importer who wants to buy a vehicle
directly from the importer.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 15
 8/17/2021
You can manage one-time customers , for example the employees of the importer, using a CpD one-time suspense/collective account in
the customer master record.

The vendor is the business partner from whom the vehicle is procured (creditor).

In the importer scenario supported by VMS, this is usually the manufacturer (OEM). In cases where there is multi-level procurement, it may
be an intermediate vendor, for example a distribution center.

When a used vehicle is being exchanged for cash, the vendor can also be, for example, a rent-a car company or any other person. Such a
business partner may also be managed at the same time as a customer in the system.

 Note
You can manage one-time vendors , for example the previous owner when exchanging a vehicle for cash, using a CpD one-time
suspense/collective account in the customer master record.

You require this master data for the following activities:

the execution of speci c actions (the vendor, for example for the action ORD1 Create purchase order , the customer, for example, for the
action CUOR Create sales order )

the assignment of the organizational data to VMS roles, transaction VELORO (customer)

the entry of the manufacturer in the material master record in the purchasing view (vendor)

Activities
You must enter some master data when you create vendors and customers since not all the required data can be set on the VMS action interface.

Choose transaction XK01 to create a vendor centrally.

Enter the required general data, purchasing data and company code data. For VMS the following data for the vendor is particularly
important:

Location

Payment conditions

Incoterms (international commercial terms)

Purchase order currency

Purchasing group (alternatively also in the purchasing info. record)

Indicator for goods-receipt-based invoice veri cation (alternatively also in the purchasing info. record)

This indicator is not necessary if you are not working with goods-receipt-based invoice veri cation.

 Caution
Create a purchasing info. record manually for each vendor. Leave the eld Valuation type under Purchasing organization 1 empty.
Do not use the Customizing setting (Customizing for Materials Management ) under Purchasing Environment Data De ne
Default Values for Buyers , indicator InfoUpdate – Purchase order ), which de nes that a purchasing info. record is created
automatically when a purchase order is created. The eld Valuation Type is lled when this Customizing setting has been made.
This leads to problems when you want to create vehicles.

Choose transaction XD01 to create a customer centrally.

Enter the required general data, sales area data and company code data. For VMS the following data for the customer is particularly
important:

Location

Currency

Incoterms (international commercial terms)

Payment conditions

Shipping conditions

This is custom documentation. For more information, please visit the SAP Help Portal 16
 8/17/2021
Account assignment group

Tax code

You also have to enter a reconciliation account and bank details in the company code data for vendors and customers.

See also:

Vendor Master Data

Processing Customer Master Records

End Customer

Use
The end customer is the customer of the dealer.

End customer data is very sensitive data. Every dealer wants to create his or her own end customer data and be absolutely sure that this data
remains hidden from all other dealers.

In an environment like the leasing companies where the actual end customer is the employee and not the leasing company itself it is required to
associate multiple end customers to a vehicle.

This is provided by the action ADCU Additional End Customers . Using this action you can associate multiple end customers to a vehicle for a
particular role along with validity dates.

You can view the associated multiple end customers in a subscreen provided in the Details tab of the Vehicle Manager screen.

The entry for the end customer, as also the entry for the manufacturer and the dealer, belongs to the vehicle data .

Integration
The data for the end customer are stored in the functions for business partner management.

You can nd further information under SAP Business Partner (SAP-BP) .

Prerequisites
You have de ned number ranges and groupings in Customizing for Business Partner Administration and de ned one of the groupings as an internal
standard grouping. This grouping is then chosen automatically if do not assign a business partner number or a grouping when you create a
business partner.

Features
Data Control

End customer data is controlled using organizational roles. An organization role is a role to which organization data is assigned. Organizational
data is dealer or importer data ( plant, sales organization, distribution channel, division, SD document type, customer, ship-to party and payer ).
Roles for which the eld Customer is lled with a value indicate a debtor, in other words a dealer. Roles for which the Customer eld is empty are
for importers.

The eld Customer determines that the dealer entered can only view the end customers that he or she has created himself or herself and not
customers created by other dealers. If the eld is empty, in other words if you are dealing with an importer, all the end customers can be viewed.

Customizing for Business Partner Administration

Business partner role VLC001 End Customer for creating end customers is contained in the Customizing that is delivered. All end customers that
you or your dealers create as explained above are automatically assigned to this role.

Additional end customers with different roles apart from VLC001 can be assigned using action ADCU.

This is custom documentation. For more information, please visit the SAP Help Portal 17
 8/17/2021
You can nd further information under Business Partner Role (BP Role) .

Activities
You can create, change, display and assign an end customer as follows:

by using action BUPA Assign end customer

by using the function Manage end customer

You can use this function in the following actions:

OFFE Create Quotation

RSOF Create Reservation and Offer

CUOR Create Sales Order

CHCO Change Sales Order

BUPA Assign End Customer

ADCU Additional End Customers

SOEU Used Vehicle Sales: Create Order

O2CO Create Vehicle, Purchase Order and Sales Order

CRCO Create Vehicle and Sales Order

CCPO Change Sales Order and Purchase Order

In both cases you branch directly to the functions contained in SAP business partner administration.

 Caution
You can create relationships between the end customers for end customer handling using the actions named above. You cannot use business
partner relationships from SAP Business Partner Administration in this case.

Role

Use
A VMS role serves as a central control element in VMS . You create roles in Customizing, feed them with data in the VMS basic data functions and
then assign them to the users.

Prerequisites
You have created the VMS roles with key and description in Customizing for VMS under De ne VMS Roles (transaction OVELO19).

Features

This is custom documentation. For more information, please visit the SAP Help Portal 18
 8/17/2021

There are three types of role:

Organizational Role

This is a role to which organizational data is assigned. Organizational data is dealer or importer data ( plant, sales organization, distribution
channel, division, SD document type, customer, ship-to party , and payer ). A role for which the eld Customer is lled with a value indicates
a debtor, in other words a dealer.

These elds are usually evaluated in the VMS Internet interface . If a dealer wants to create a sales order in the importer’s system via the
Internet, the elds in the sales order are lled with the appropriate organizational data. The dealer cannot change this data.

The Customer eld is also evaluated in the SAP graphical user interface ( SAP GUI ). If there is an entry in this eld, the dealer that has
been entered can only see the end customers that he/she has created him/herself but not end customers of another dealer. If the eld is
empty, all the end customers are visible.

 Note
If you work with the user parameters VELO_SOLDTO Customer, Sold-to party , VELO_SHIPTO Ship-to party and VELO_BILLING Bill-to
party , you do not need to create a separate organizational role for each individual dealer. You only require one role for all your dealers.
Each dealer is then identi ed by the user parameters as a speci c dealer.

Furthermore, you can assign a vehicle search area and an original ordering party to the organizational role. These elds are required in
category management. The vehicle search area controls which users are allowed to see which vehicles during the search.

You can also assign a pricing procedure and a currency . These elds are required in SAP Internet Pricing and Con gurator (SAP IPC) and in
the Characteristic Value Assignment Screen . The prices are displayed in the currency speci ed. Furthermore, the currency eld controls the
currency in which the user sees the prices in the vehicle overview and in the detail data for the vehicle.

The elds that affect purchasing are currently not evaluated and therefore have no signi cance. However, they can be included in BAdIs as
and when required in order to meet customer requirements.

Vehicle Model Role

This is a role to which vehicle models are assigned. This role determines which vehicles the system displays to the user in the vehicle model
list.

 Example
You are an importer and want to see and manage all vehicle models; dealer X sells only small cars, dealer Y only motorcycles.

A vehicle model can be assigned to more than one vehicle model role.

Con guration role

This is a role that is assigned to a con guration change pro le .

Depending on the vehicle model, status and so on, the con guration role speci es which vehicle characteristics the system should make
visible for the user and which changes the user is allowed to make to the vehicle characteristics.

 Recommendation
This is custom documentation. For more information, please visit the SAP Help Portal 19
 8/17/2021
It is recommended that you create at least two con guration roles: one for yourself as importer and one for all your dealers. In this way
you can be sure that you, as importer, are able to change more con gurations than your dealers.

Activities
1. Assign vehicle models to the vehicle model roles (transaction VELORM).

2. Assign organizational data to the organizational roles (transaction VELORO).

3. Optional: if desired, de ne con guration change pro les and, in the pro le determination, de ne which pro le can be used for which
con guration roles (transaction VELOP).

4. Assign roles to the users (transaction VELORU).

You should assign exactly one organizational role, one con guration role and one or more vehicle model roles to a user.

 Caution
Use a role only ever in exactly one function. For example, only assign vehicle models to a vehicle model role and not organizational data.
In this way, you achieve maximum exibility when changes are made later.

Creating a Con guration Change Pro le

Use
Depending on the status of the vehicle and which con guration role the VMS user has, a con guration change pro le determines which
con guration characteristics can still be changed in the SAP Internet Pricing and Con gurator (SAP IPC) and which cannot. For example, when you
create a sales order or change a purchase order, characteristics that can no longer be changed can either be displayed or hidden to the user.

For example, you can subdivide the con guration characteristics into characteristics relevant to the order such as color or engine, and
characteristics relevant to rework or accessories, such as a roof rack. The dealer can then, as of a speci c point in time, only change the second
type of characteristic whereas the importer can still change both.

Characteristics that are visible but cannot be changed can be characteristics, for example, that involve country-speci c requirements (right-hand
or left-hand drive, yellow headlights, and so on) or characteristics that relate to levels of emission allowed by law, such as exhaust pipes or
catalysts.

Prerequisites
You have created the required material master data and con guration data . If you use SAP IPC for vehicle con guration, you have
downloaded the data to the IPC system.

You have created a con guration role for each role in the con guration activity (such as importer employee or dealer employee).

Procedure
1. In transaction VELOP, create a con guration change pro le for every combination of characteristics that can be changed and under De ne
Visibility of Characteristics , de ne which con guration characteristics you want to be visible but not changeable and which you do not want
to be visible.

To do this, you must know the con guration characteristics for the vehicle models for which you want to create the con guration change
pro le.

2. De ne when you want the pro le to be used under De ne Determination of Pro le .

Determination can be dependent on the following parameters:

Con guration role

Vehicle model

Availability status

Primary action control

Primary status
This is custom documentation. For more information, please visit the SAP Help Portal 20
 8/17/2021
Secondary action control

Secondary status

 Note
For primary and secondary statuses you can also use a generic status, that is, a status with placeholders such as MM* or SD*.

For more information, see Vehicle and Action Control .

All this data is for optional elds, in other words, you can choose how much or how little data you want to include. The entry that best ts
the vehicle is used.

Create an entry for each status combination for which you can execute an action with con guration. You can group together more than
one status with the generic status and thus reduce the number of entries.

 Note
You can analyze the determination of the con guration change pro le with transaction VELOPR. For example, you can display which
con guration change pro les already exist for a speci c vehicle model and a speci c characteristic. With this information you can then
check whether your entries in the table for de ning con guration change pro les (transaction VELOP) are correct and complete.

Result
When you start SAP IPC or the characteristic value assignment screen from the Vehicle Manager in order to con gure a vehicle, the system
determines which con guration role has been assigned to the user, which vehicle model the user is currently con guring, and the status of the
vehicle being con gured.

Depending on these input parameters, the system determines which con guration change pro le has to be used during the con guration and
transfers this pro le to SAP IPC or to the characteristic value assignment screen.

 Note
You can de ne your own determination logic in the Business Add-In (BAdI) VLC_DETERM_CHPROFILE.

Example
There are two con guration roles, importer and dealer, for which you have created the VMS roles KPIM and KPHD .

The vehicle model MEDIUMCAR has the con guration characteristics MOTOR , AUSSENFARBE (exterior color) and INNENFARBE (interior color) .

When the manufacturer has con rmed the purchase order (let us presume this is primary status MM10 of primary action control MMCT ), the
importer is no longer allowed to change the engine and the dealer is not allowed to change the engine or the exterior color or the interior color.

You therefore need the following two con guration change pro les:

Pro le Description Characteristic Changeability

CP_ONE Engine cannot be changed MOTOR Cannot be changed

CP_TWO Engine, exterior color, interior color MOTOREXTERIOR_COLORINTERIOR_COLOR Cannot be changedCannot be

cannot be changed changedCannot be changed

Pro le determination is then as follows:

Pro le Role Material Primary action control Primary status

CP_ONE KPIM MEDIUMCAR MMCT MM10

CP_TWO KPHD MEDIUMCAR MMCT MM10

Calculation of Gross List Price Using Organizational Roles

Use
This is custom documentation. For more information, please visit the SAP Help Portal 21
 8/17/2021
When you create and con gure a vehicle, VMS calculates the gross list price from the basic price of the vehicle model and the prices for the
individual characteristics . The system automatically adjusts the gross list price when changes are made to the con guration. This gross list price
is independent of customers to which the vehicle is sold or has been sold and does not contain any discounts. It is, therefore, not the price for which
you sell the vehicle to the dealer.

You can then use the gross list price in the vehicle search to search for vehicles in a speci c price range.

Features
The system simulates a sales order when it calculates the gross list price and it therefore requires all the data that you have to enter when you
create a sales order. It writes the price that it calculates to the vehicle data as the gross list price.

The system acquires the data it needs for simulating a sales order from the organizational role GROS (stands for gros s list price). There must,
therefore, be an organizational role with this name in the system.

This organizational role speci es the data for a speci c sales organization. If you want to perform pricing for different vehicle models for not just
one but for several different sales organizations, you can use the BAdI (business add-in) VLC_CALCULATE_GPRICE.

Activities
1. Create an organizational role with the key GROS in transaction VELORO.

2. Make an entry in the following elds in this organizational role:

Plant

Sales organization

Distribution channel

Division

Sales document type

Pricing procedure

Currency

All vehicles should have gross list prices in the same currency so that you can search for vehicles in a speci c price range without
having to convert prices.

Action Control

Use
You can represent your business processes in the system with action controls. You de ne 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 con rmed the
purchase order, in other words has performed the action Con rm purchase order , the status changes automatically to Purchase order
con rmed .

 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!

Prerequisites
You have de ned the following parameters in Customizing for VMS under Control Data :

This is custom documentation. For more information, please visit the SAP Help Portal 22
 8/17/2021
Actions (transaction OVELO1)

Vehicle status (transaction OVELO12)

Vehicle availability (transaction OVELO13)

Vehicle locations (transaction OVELOL

Features
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 nancial process is
also possible.

You can “ nely 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 speci c vehicle models do not require any actions for local rework or for reservations etc.

Activities
Choose Control Data De ne Action Controls and De ne Action Matrices (transaction OVELO11) in Customizing for VMS. De ne the following
there:

1. De ne the action controls for the vehicles that you require for your business processes.

2. Create an action matrix for each action control.

In this matrix you de ne 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.

3. For speci c 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.

Example for Procurement Matrix

This matrix uses a procurement process to illustrate how actions have an effect on the status of a vehicle.

This is custom documentation. For more information, please visit the SAP Help Portal 23
 8/17/2021

Example for Action Control

Availability Status and Action

The following graphic displays how the actions can in uence the availability status. In the graphic below, a little ag shows the actions and their
sequence, the bubbles the appropriate new availability status. The availability status can remain the same for several actions (for example, 3 and
4).

Address/Location and Action

The following graphic displays how the actions can in uence the address and/or the location of a vehicle. In the graphic below, a little ag shows
the actions and their sequence, the bubbles the appropriate new location. The location can remain the same for several actions (for example, 3
and 4).

Depending on the action, the location is determined from one of the following sources:

Vendor master (for example, for the action Con rm order )

Customer master (for example, for the action Transfer to dealer )

Customizing of vehicle locations (for example, location In transit for action Post goods issue )

This is custom documentation. For more information, please visit the SAP Help Portal 24
 8/17/2021

Determination of Action Control

Purpose
Action control determination runs automatically in the system (according to the logic explained below) as soon as you perform an action. Primary
and secondary action control can be determined individually and at the same time. An example for determination at the same time is the inter-
linking action CRCO Create vehicle and sales order .

You can de ne your own logic for action control determination using the BAdI VLC_DETERMINE_CONTRL.

Prerequisites
You have de ned the action controls in Customizing for VMS under Control Data (transaction OVELO11).

You have entered the information, which the system requires for determining action control, using transaction VELOS. You have entered the action
controls with which you want VMS to work for each vehicle model and, if necessary, for further organizational data. The following elds are key
elds:

Vehicle model

Plant

Purchasing organization

Vendor

Sales organization

Distribution channel

Division

Customer

You can de ne different action controls for any combination of these elds. Mostly, however, it suffices to de ne an action control for each
combination of vehicle model and plant for the primary action controls and for each combination of sales organization and customer for the
secondary action controls.

This is custom documentation. For more information, please visit the SAP Help Portal 25
 8/17/2021
You don not have to enter a value in all the key elds. A key eld that is empty means that the entry is valid for all values that are possible for this
eld.

Process Flow
Determination of the action control works as follows:

In Customizing, the system checks whether the action that you want to perform is a primary action, a secondary action or both.

The system checks whether the appropriate action controls have already been assigned to the vehicle. If yes, it uses these.

The assignment of an action control to a vehicle cannot be changed.

If no, the system triggers the action control and evaluates the entries in the table for transaction VELOS. This takes place on the basis of the
action data and the existing vehicle data. The system makes checks in the following order:

a. Is there a tting entry in the table for transaction VELOS? If yes, the system uses this entry.

b. If no: is there a generic entry that ts, in other words, an entry for which elds are empty and therefore all existing values can be taken? If yes,
the system uses this entry. If there is no generic entry or more than one suitable one and if the action controls in the entries are not identical, the
system displays an error message.

Result
As soon as the system has found the correct action control, determination is ended. The system performs the desired action and sets the status
that is stored in the system as new status for this action in the action control.

If the system does not nd a suitable action control, it displays an error message and you have to correct the entries in transaction VELOS
appropriately.

Example
You want to perform a primary action with the following action data: vehicle model Sprinter, plant 7777.

No primary action control has been assigned to the vehicle.

There is no entry that ts exactly in the table for transaction VELOS, in other words, there is no entry for which only the elds vehicle model
Sprinter and plant 7777 are lled.

However, there is an entry for vehicle model Sprinter , plant 7777 and vendor: Opel . But this entry is too speci c due to the entry of a speci c
vendor and cannot therefore be used.

There is another entry for the vehicle model Sprinter for which only the vehicle model has been entered and no other elds have an entry in them.
This entry is taken since the missing entry in the plant eld means that the entry is valid for all existing plants.

Vehicle IDoc

De nition
The vehicle IDoc VEHCLE01 is part of VMS. It serves to transfer vehicle data between manufacturer and importer or between different sales
organizations. It can be an inbound or an outbound IDoc .

For more information, see the documentation for the SAP Web Application Server under Processing of IDocs .

Use

This is custom documentation. For more information, please visit the SAP Help Portal 26
 8/17/2021
The inbound IDoc serves mainly as a communication means between the manufacturer and yourself as importer. The manufacturer can
con rm your vehicle order via the IDoc and update the vehicle status ( in production , in transit etc.) regularly with current production data .
To do this, VMS evaluates the Customizing table for transaction OVELO5 under Control Data De ne External Status ): it nds an action
and a plant for the organization channel and the external status. As soon as the system performs this action, the vehicle is set to the
internal status stored in the appropriate action matrix.

You can display inbound IDocs using the standard transactions WE02 or the VMS transaction VELOM Status Monitor for Vehicle IDoc .

The outbound IDoc is linked to VMS message control (see Customizing for VMS). As importer, you can send faxes, e-mails and IDocs
containing the vehicle data to subordinate or superior sales organizations using action MSSO . The system then uses the plant and the
action to nd an organization channel and an external status in the above-named Customizing table and writes these to the IDoc. If the
recipient of the IDoc also uses VMS, he/she can evaluate this data and process it automatically using the same Customizing table in his/her
own VMS.

 Note
You can use user parameter VELO_ORGCH to enter a default value for the organization channel for outbound IDocs.

You can display outbound IDocs using the standard transaction WE05.

 Caution
Outbound and inbound IDocs use the same Customizing table (transaction OVELO5) and read it once forwards and once backwards.
Please ensure that the table only contains clear and precise entries. If the outbound IDoc nds ambiguous entries, the data is sent but it
cannot be processed any further on the receiving side and a warning message appears.

Structure
The vehicle IDoc VEHCLE01 contains the following segments :

E1VLCK1 vehicle identi cation : required segment, number 1 (organization channel, external status, vehicle ID, internal/external vehicle
number, vehicle identi cation number)

E1VLCK2 vehicle data : optional segment, number 1 (vehicle model, plant, storage location, vendor, customer, end customer, visibility,
availability, address, production date, delivery date, vehicle use, sales campaign, gross list price, currency, vehicle search area,
original ordering party, access authorization)

E1VLCC1 con guration data : optional segment, number 1

E1VLCC2 instance data: optional segment, number n

E1VLCC3 part of data: optional segment, number n

E1VLCC4 characteristic value assignment: optional segment, number n

E1VLCA1 additional data : optional segment, number n (quali er, quali er characteristics)

E1EDS01 general totals segment : required segment, number 1

The elds Organization channel , External status and one of the vehicle numbers must be lled in segment E1VLCK1 for inbound IDocs and in
segment E1VLCK2 the eld Vehicle model (only for Create actions).

The inbound vehicle IDoc has message type VLCCPO Vehicle: purchase order con rmation/status tracking , the outbound vehicle IDoc has
message type VLCVDT Vehicle detail data .

Example for an Inbound IDoc

As importer you receive a purchase order con rmation from manufacturer X that contains a small con guration change. The vehicle has, for
example, a different colour from that speci ed in the purchase order. The external status is Purchase order con rmed with change . In
Customizing you have assigned the action Change purchase order to the external status Purchase order con rmed with change and the
organization channel XY. As soon as you con rm the con guration change, the system performs this action. The vehicle receives the internal
status Purchase order con rmed and the purchase order is changed accordingly.

Calling the Status Monitor for the Vehicle IDoc

Use
This is custom documentation. For more information, please visit the SAP Help Portal 27
 8/17/2021
You can use the status monitor to display incoming vehicle IDocs. You can also see exactly which vehicle data has changed and you can accept or
reject the changes manually .

 Note
You can display logs for the status monitor with transaction VELOP01 or by choosing Hist. Logs in the selection screen of the status monitor.
You can delete the logs with transaction SLG2 (object VMS_IDOC).

Procedure
1. Choose transaction VELOM Status Monitor for Vehicle IDoc .

The selection screen for the status monitor appears.

2. Choose an organization channel.

The values displayed via F4 (combination of organizational channel and external status) are values that have been de ned in Customizing
for VMS under Control Data De ne External Status (transaction OVELO5).

3. Choose a period of time, one or more IDoc statuses and further selection parameters, if required.

Only the following IDoc statuses are possible:

51: the IDoc has not been posted because as error has occurred (red traffic light)

52: the IDoc has not been posted because changes have been made that must be con rmed (amber traffic light)

53: the IDoc has been posted (green traffic light).

4. Set the indicator Execute Immediately if you want the action (that has been assigned to the external status of a vehicle) to be performed
straightaway. The IDoc status 52 changes to 53. Set this indicator only if you are sure that you want to accept all the changes.

Deselect the indicator if you want to trigger this process manually by selecting the desired IDocs from the list and choosing Accept .

5. Choose Execute.

A screen displaying the selected IDocs appears. You see different data in different colors for each IDoc with status 51 or 52: the pale area
displays con guration characteristics, the yellow area the quali ers and the blue area the vehicle data. Only the new or the changed data is
displayed; new and old values are displayed next to one another so that you can compare them.

6. Select the desired IDocs with status 52 and accept the IDoc data with Accept or reject the data with Reject .

 Note
You can branch to the general IDoc monitor by double clicking on the IDoc number (transaction BD87) - all the IDoc processing functions
are then at your disposal.

Result
If you accept the IDocs, the action that is assigned to the external status of the vehicles is performed, and the vehicles are set to their internal
status that is in the appropriate action matrix. Vehicle data and documents are changed appropriately.

Irrespective of whether you have accepted or rejected the changes, the IDoc status changes from 52 to 53.

 Note
If you are sure that vehicle data in IDocs is to be accepted automatically as soon as the IDoc takes effect, you can de ne this directly in
Customizing for VMS under Control Data De ne External Status (transaction OVELO5).

Vehicle Manager

Use
The Vehicle Manager (transaction VELO) is the central transaction in the Vehicle Management System and contains all the most important
functions in a concise form.

This is custom documentation. For more information, please visit the SAP Help Portal 28
 8/17/2021
Prerequisites
You have entered the master data required for the Vehicle Management System.

If you use SAP Internet Pricing and Con gurator (SAP IPC) for vehicle con guration, you have connected the VMS and SAP IPC. If you use
the characteristic value assignment screen for vehicle con guration, you do not have to install SAP IPC.

Features
Call the vehicle manager using transaction VELO . This is a one-screen transaction in which you have all the functions you require for your business
processes displayed on different tab pages. This means that no menu entries are required.

The following graphic displays a simpli ed layout of the Vehicle Manager screen that you access by using transaction VELO.

The following functions are available on the relevant tab pages:

Vehicle Search

Search for vehicles that ful ll speci c criteria. The default settings dictate that this tab page is in the foreground.

This is custom documentation. For more information, please visit the SAP Help Portal 29
 8/17/2021
Vehicle Overview

Hit list for the vehicle search with numerous lter options.

Vehicle Details

Data for the vehicles that you have chosen in the vehicle overview.

Execution of Actions

Execution of business transactions for the chosen vehicles, such as change vehicle, create purchase order, or create sales order.

Assignment of Vehicles to Sales Documents

Search for sales documents that a dealer has entered and thatdo not have a reference to a vehicle, and assignment of suitable vehicles
from the warehouse stock or the order pipeline.

Warranty Claim Display for the vehicle

For all functions, the vehicle is the central object. If vehicles are assigned to sales documents, the basis is the sales document rather than the
vehicle.

 Note
You can enhance the scope of functions of the Vehicle Manager by using BAdI VLC_USER_INTERFACE.

Vehicle Search

Use
You use the vehicle search (transaction VELO, tab page Find ) to search for vehicles that ful ll certain criteria in the vehicle stock.

Your dealers search in the vehicles that you have assigned to them, for example for a vehicle for which the con guration coincides with the desired
con guration of the end customer. If you nd a vehicle with the desired con guration, you reserve it for the end customer, create a sales order for
this end customer or perform another action. If you do not nd a vehicle of the desired con guration, create a new vehicle, provided you have the
authorization to do so.

As importer , you use the vehicle search as follows:

for your own Work ow : you select, for example, all vehicles with the primary status Vehicle created and the secondary status Sales order
created and order them from the manufacturer.

for evaluation purposes , for example to get an overview of how many vehicles have been assigned to which dealer, how many vehicles have
been reworked in the last week, how many reservations a speci c dealer has created in a speci c period of time an so on.

Features
Apart form the normal database search, you can also use the fast search using an external search machine .

 Note
You can enhance the scope of functions in the vehicle search with the following BAdIs :

VLC_MODELLIST_NO_FIL: Adaptation of model list (without lter)

VLC_VHVIN_PREPRARE: Large and small letters for VIN

VLC_SEARCH_INTERFACE: Adaptation of search interface

VLC_SEARCH_PROFILE: Search pro le for vehicle search

VLC_SEARCH_ADAPTION: Vehicle search

VLC_EXTSE_SEARCH: Vehicle search using external search machine

VLC_SE_DELTA_LOAD: Delta load to external search machine

This is custom documentation. For more information, please visit the SAP Help Portal 30
 8/17/2021
If you know the internal or external vehicle number or the vehicle identi cation number (VIN), you can enter this number and search for a
vehicle directly .

 Note
The internal vehicle number (I) is set as default for the number type. You can use the user parameter VELO_SSEARCH to make settings
to use the external vehicle number (E) or the vehicle identi cation number (V).

The vehicle identi cation number (VIN) has 17 characters. If you work with this number, it usually suffices to enter the last 10 characters
since the rst seven often indicate the model. The system then searches for *VIN. An error message is displayed if the system nds more
than one vehicle.

If you do not know a number, you can search for vehicles according to speci c criteria . You have the following groups of criteria, so-called
search views, at your disposal:

Con guration

Vehicle history

You can use this search view to nd vehicles for which a speci c action was performed in a speci c period of time. If this action was
not performed in this period of time, the hit list is empty.

In this view you can, for example, also search using a speci c vehicle location. As importer, you can nd information on questions such
as how many vehicles have been assigned the status In transit today? How many orders did reworker X receive last month?

General vehicle data

Vehicle status

Business partner/addresses

You can use this search view, for example, if you are implementing a multi-plant scenario and you wish to search by plant. This view
can also be used for searching vehicles by specifying additional end customer details as search criteria.

Documents ( purchasing documents, transfer posting/rework documents, sales documents, service document s)

Search pro le management

If you often search for a speci c combination of criteria, you can save your search template to a user-speci c search pro le and call
it at any time. For more information, see: Working with a Search Pro le .

Customer-speci c

 Note
If you use SAP Supply Chain Event Management (SAP SCEM) , you have two more search views at your disposal.

If you choose more than one criterion (in different views), the vehicles must ful ll all the given criteria ( AND operation ). The more
criteria you choose, the more you limit the possible number of vehicles that can be found.

 Note
You can replace existing views or create your own ones. To do this, choose Vehicle Search De ne Search Views in Customizing
for VMS. If your additional search view is not a standard selection screen, you also have to implement BAdI
VLC_SEARCH_INTERFACE.

You can search across more than one vehicle model . This is only possible for the search using the con guration if you have assigned the
appropriate vehicle models to a common family class (see also: Constructing a Vehicle Con guration ).

You can display the vehicles found, with con guration and vehicle data, in an overview .

Provided you have implemented BAdI VLC_PRESELECTION in Customizing under Logistics Execution Vehicle Management System
(VMS) Business Add-Ins (BAdIs) Vehicle Search Preselection of Vehicle Models and you are using aclass hierarchy that has been de ned
and to which all VMS vehicle models have been assigned,you can make a preselection of vehicle models.

You can use the Toggle function to switch between the at ALV vehicle model list and the hierarchical ALV model tree.

Searching for a Vehicle

This is custom documentation. For more information, please visit the SAP Help Portal 31
 8/17/2021
Searching for an Individual Vehicle
You use this type of search if you are looking for a speci c vehicle and you know one of the vehicle identi ers (internal or external vehicle number or
vehicle identi cation number). This returns the single vehicle you are looking for.

Choose transaction VELO.

The Vehicle Manager screen appears and you can see the tab page Find on this screen.

At the top right, choose the vehicle identi cation type that you want to use for the search (next to the eld Indiv. Vehicle ).

Enter the number of the desired vehicle and choose .

The tab page Detail appears. Here you can display the vehicle data, the data for the customer and end customer, the con guration and the vehicle
history.

Vehicle Search Using Search Criteria

You use this type of search if you are not looking for any speci c vehicle. The hit list may contain a number of vehicles that correspond to your
search criteria.

Choose transaction VELO.

The Vehicle Manager screen appears and you can see the tab page Find on this screen.

On the left you see the vehicle models that have been assigned to you via one or more vehicle model roles .

Select the vehicle model that you want your search to be based on. You can select a collection of vehicle models that belong together or use to
select all the vehicle models.

If the selected vehicle models have the same family class or you have chosen only one vehicle model, the search view Con guration is displayed.If
more than one model is selected and the characteristics of the chosen model are not the same, you cannot perform a search for con guration
criteria. In this case, the search view General Vehicle Data is displayed.

Enter values for the desired search criteria. The criteria can belong to different views. For all search views other than the con guration view, the
search criteria are additive (AND operator is used). In other words, the more search criteria you choose, the more restricted the search will be.

Entering values for two different characteristics in the con guration view is also treated as an AND operator. You can only use OR or EXACT for
multi-value characteristics. By making the appropriate selection form the drop-down box for the search mode, you can search by using the
operators OR, AND or EXACT.

You can search by using a wildcard lter for the technical names of the values. The function Comparison type allows you to speci cally include or
exclude certain characteristic values.

Using the eld Validity date , you can search for a con guration that is/was valid on a particular date. Entering a date in uences the following:

The description of the characteristic and its’ assigned values, for example, a value of characteristic “color” could be named “lava red” on 1 st July
2003 and its name could have been changed to “ re red” on 1 st August 2004.

The availability of characteristics and their values. For example, the value “winter package” is added to the characteristic “packages” on1 st
October 2004. This value can only be found if the validity date is1 st October 2004or later.

You can nd more information on family classes under Constructing a Vehicle Con guration .

If you are unsure which criteria are active and therefore want to reset the search criteria, choose the blank entry in the list in the eld Search
Pro le (no search pro le). Then all the search criteria are reset. If the eld Search Pro le was already empty, choose to reset the search
criteria.

Choose .

The search is started. All your chosen search criteria are taken into account irrespective of which search view is currently displayed.

This is custom documentation. For more information, please visit the SAP Help Portal 32
 8/17/2021

If you do not have sufficient authorization to view a particular vehicle or group of vehicles, your search may result in no results even though the
vehicle record exists.

If the number of vehicles found is more than a certain value, a dialog box appears with a performance warning. Here you can choose whether you
want to terminate the process and enter more speci c search criteria, or whether, despite possible performance problems, you wish to display all
the vehicles found including the con gurations, or whether you wish to display the vehicles without the con guration data. If you choose the last of
these options, you can load the con guration data at a later date by choosing Update Vehicles on the right-hand side of the vehicle overview. You
de ne the threshold value for the number of vehicles in user parameter VELO_PERFWARNING.

The tab page Overview appears. All the vehicles that correspond to the search criteria are displayed in the hit list.

Working with a Search Pro le

Use
In a search pro le, you can group a combination of search criteria (user-speci c) together under a pro le name. You can then call this combination
of criteria under this name any time you like at a later date.

Procedure
1. Choose transaction VELO.

The Vehicle Manager screen appears and you can see the tab page Find on this screen.

2. Select the vehicle model that you want your search to be based on.

3. Choose your desired search criteria on the different search views.

Choose the entry for search pro le management in the eld View .

4. Enter a name and a description for the search pro le.

5. Save your entries.

Result
This search pro le now appears in the list nest to the eld Pro le .

You can change the pro le by calling it, changing the criteria as required and saving the changes under the same pro le name under the entry for
search pro le management.

 Note
If you have activated a search pro le and changed search criteria but want to return to the original settings for the search pro le, choose to
update the search pro le.

Category Management

Use
Categories i.e. groups of vehicles whose similarities are de ned by certain rules are formed in category management. These rules are evaluated
during the vehicle search .

You can de ne which vehicles you want to be displayed for which dealers.

You can nd further information in the documentation for Financial Accounting under Rules and Boolean Logic/Syntax .

This is custom documentation. For more information, please visit the SAP Help Portal 33
 8/17/2021
Integration
You can de ne categories per vehicles search area, per organizational role, per combination of these two or completely independently of the
vehicle search area and organizational role.

You do not necessarily have to work with vehicle search areas to use category management.

Prerequisites
1. You have created rules in Customizing for VMS under Vehicle Search Vehicle Search Areas De ne Vehicle Categories (transaction
OVELO20).

2. You have prioritized and put these rules in an order in Customizing for VMS under Vehicle Search Vehicle Search Areas Assign Roles and
Vehicle Categories (transaction OVELO21).

When you de ne these rules, you can ll speci c table elds, which reference to the vehicle or the vehicle searcher, with values and then link
these elds to mathematical expressions using Boolean operators.

 Note
Only tables in the vehicle table can be taken into account for vehicle data, not con guration characteristics.

A vehicle can belong to more than one category.

Features
For each vehicle that corresponds to the search criteria, the system checks the rules that have been de ned and evaluates them in the given
sequence. As soon as the system nds a rule that is “true”, the appropriate vehicle counts as having been “found”. If no rules are “true”, the vehicle
is excluded.

The vehicles that are found appear in the vehicle overview in the order in which the categories are searched. By skillful prioritizing, therefore, you
can ensure that the vehicles that you want to be sold quickest appear at the top of the vehicle search hit list.

Example
The categories and their sequence could look similar to those listed below for a dealer that belongs to the organizational role Dealer Müller :

Category 1:

Vehicles that are not displayed, belong to dealer Müller and have not been sold to the end customer yet

Displayed = ' ' AND customer = 'dealer Müller' AND end customer = ' '

Category 2:

Vehicles that are not displayed and belong to dealer Müller

Displayed = ' ' AND customer = 'dealer Müller'

Category 3:

Vehicles that are displayed and generally available for all dealers

Displayed = 'X' AND availability = '02'

Vehicle Search Area and Sharing Level

Use
A vehicle search area is a geographical area in which a vehicle is made available and searched for. It de nes the outermost limit within which a
vehicle search can take place.

In a scenario in which more than one dealer, SD organization and so on access the same vehicle stock (de ned by the vehicle search area), you can
control the visibility of a vehicle for the other dealers, sales organizations etc. by using the sharing level.

This is custom documentation. For more information, please visit the SAP Help Portal 34
 8/17/2021
You can evaluate vehicle search areas and sharing levels by de ning rules for the vehicle search for these parameters. These rules can help you to
set up a uniform SD policy in the system. You can nd further information under Category Management .

Prerequisites
You have created sharing levels in Customizing for VMS under Vehicle Search Vehicle Search Areas De ne Sharing Levels (transaction
OVELO27).

You have created vehicle search areas in Customizing for VMS under Vehicle Search Vehicle Search Areas De ne Vehicle Search Areas
(transaction OVELO20).

All the vehicles within one vehicle search area are technically compatible and allowed in every other geographical region.

Features
Vehicle search area

The vehicle search area can be dependent on product data (base con guration) and organizational structures (sales organization, plant). In
the standard system, it is only dependent on the plants.

A vehicle search area can include more than one sales organization.

Each vehicle can only belong to exactly one vehicle search area.

 Example
The vehicle search area Benelux is allowed for the sales organizations Belgium , Luxembourg and The Netherlands. So, a dealer in
Belgium also has vehicles from the stock for the sales organization “The Netherlands” at his/her disposal.

For certain reasons, it may be advantageous to separate vehicle search areas on product family level. The above example can be limited
to the most popular models of a vendor, there can also be an additional vehicle search area Europe Sprinter for the expensive model
Sprinter that is seldom sold. A dealer in Belgium would then only have the vehicles in the area Benelux at his/her disposal for standard
models and the entire stock for the area Europe Sprinter for the Sprinter model.

Assigning Vehicle Search Area and Sharing Level

You can assign either exactly one plant or more than one plant (multi-plant scenario) and one default sharing level to each vehicle search area in
the standard system . These values are then copied automatically to the vehicle data when you create a vehicle. If you want a different assignment
when you create the vehicle, choose one of the following options:

Create your vehicles using transaction VELO . If you create the vehicles using BAdI (VLC_EXECUTE_ACTION, method
DATA_CHANGES_BEFORE_ACTION), assign a vehicle search area and sharing level to the vehicles.

Create your vehicles using a BAPI (BAPI_VEHICLE_CREATE) and at the same time use this BAPI to assign a vehicle search area and sharing
level to the vehicles.

Create your vehicles using a BAPI (see above) and if you create them using a BAdI (see above), assign a vehicle search area and sharing
level.

You can change the vehicle search area and sharing level for a vehicle in retrospect using action SMOD ( Change vehicle ).

Vehicle Overview

De nition
The vehicle overview in the Vehicle Manager screen (transaction VELO, tab page Overview ) displays the hit list , which is the result of the vehicle
search.

Use
After you have searched for vehicles using speci c criteria, the tab page Overview appears.

Structure

This is custom documentation. For more information, please visit the SAP Help Portal 35
 8/17/2021
In the vehicle overview you can see the hit list for the vehicle search on the right-hand side, in other words, all the vehicles that are found with
vehicle details. On the left-hand side you can see all the vehicle criteria (for example: availability, location, status, customer, vehicle model,
con guration or plant) with appropriate values displayed in a tree structure.

You can deactivate this value by double-clicking on a value in the tree structure on the left. Then all the vehicles that contain this value are
excluded from the hit list. If you double-click on the value again, it is reactivated. With Only Activate This Value you can ensure that, for any one
criterion, only the value chosen by clicking on it is activated and all the other values are deactivated.

The symbols have the following meanings:

Vehicles with this value are displayed.

Vehicles with this value are not displayed.

 Caution
If, for example, you have only selected available vehicles in the search and then set the value Available for the criteria Availability to red
in the criteria tree structure in the left-hand screen area, the hit list is empty. The other values in the tree still have a green symbol.

The default settings dictate that the rst six characteristics for the con guration are displayed in their own columns in the right-hand screen area.
No more than six characteristics can be displayed. If you have searched over several vehicle models, only the characteristics for a common family
class are displayed, if they exist. If no family class exists, no characteristics are displayed and the appropriate columns are empty.

All the characteristics that are contained in the vehicles displayed are displayed in the tree structure in the left-hand screen area under
Con guration . By double-clicking on a characteristic you can determine which characteristics are displayed in their own columns and which not.

The symbols have the following meanings:

Characteristic is displayed as column in the hit list.

Characteristic is not displayed as column in the hit list.

Vehicle Details

De nition
On the Vehicle Manager screen (transaction VELO, tab page Detail ), the vehicle details refer to the vehicle in the left screen area that you have
activated using a hotspot and display the vehicle details , data for the customer and end customer , the con guration and the vehicle history .

Use
After you have searched for one speci c vehicle, the tab page Detail appears.

After you have searched for vehicles using speci c criteria, the tab page Overview appears. If you use the Control key to select more than
one vehicle on the tab page Overview and then choose the tab page Detail , the vehicles you have selected are copied to the left-hand
screen area and you can display the details for the individual vehicles one after the other. To do this, click on the internal vehicle number in
the left-hand screen area.

If you do not choose a vehicle on the tab page Overview , all the vehicles are copied to the tab page Detail .

Structure
The vehicle details consist of the following areas:

Customer data, end customer data

If there is more than one end customer associated with the vehicle, you can select an end customer and display the details. The system
provides an end customer subscreen where you can select the end customer role and end customer to fetch the details from the system.

Vehicle data

There are some additional pushbuttons in this area. The symbol next to the appropriate function indicates that data exists. The following
table lists the functions and explains what is displayed when you choose a speci c function.

This is custom documentation. For more information, please visit the SAP Help Portal 36
 8/17/2021

Function What is Displayed

Additional Data Further customer-speci c data (see: Programming Your Own Actions )

Messages Messages that have been sent with the action MSSO Output Messages

You can also send new messages manually in addition to the message
types de ned in Customizing, for example, trigger the printing of the
vehicle data.

Documents Documents that have been added with action ADDO Assign Documents

Reservations Reservations and reservation requests that have been created with action
RSVN Create Reservation or RSVM Create reservation request

SCEM Information on SAP Supply Chain Event Management (SAP SCEM)

MW/MeasP Master warranties and measuring points for Warranty Claim Processing

Next to the elds Primary Status , Secondary Sts : Active primary or secondary action matrix

The action is displayed on the left, the old status in the column header,
the new status underlined in yellow at the point of intersection. If you click
on an action on the left, scroll horizontally to the next status entry
underlined in yellow. You can set the original status again by clicking on
the eld in the top left-hand corner.

If you click on any of the status elds, you go to a view where you can see
the old status on the left, the new status in the column header and the
action underlined in yellow at the point of intersection. Actions underlined
in red represent multiple values, in other words, there is more than one
action that converts a vehicle form status X to status Y. If you click on any
eld on the left in the column with the old status, you can switch the red
elds through all the existing values.

Con guration

Vehicle history

All the actions that have already been performed for this vehicle are listed in the vehicle history. The primary and secondary status and a
row of further parameters are displayed for each action. Interlinking actions are listed in a separate column and the appropriate elementary
actions are displayed in individual lines.

The symbol on the left next to an entry in the vehicle history indicates that a SAP standard document, for example, a sales order has been
created by the action. Click on the symbol in order to display the document in the appropriate standard transaction. For sales orders, this is,
for example, transaction VA03 Display Sales Order .

 Note
You can replace each of these areas by a customer-speci c screen. You have the following BAdIs at your disposal for this purpose:

VLC_DETAIL_CONFIG

VLC_DETAIL_DEALER

VLC_DETAIL_ENDCUST

VLC_DETAIL_HISTORY

VLC_DETAIL_OVERVIEW

 Caution
If you have just performed an action and the update posting has not been completed yet, the data for the con guration, vehicle history,
additional data, documents and reservations is not yet up-to-date . If more than one user accesses the data at the same time, the
opposite may happen and the data is no longer up-to-date after a while. Refresh your display with Update Vehicle List or with
Update Vehicles.

Action

Use
This is custom documentation. For more information, please visit the SAP Help Portal 37
 8/17/2021
An action is a business transaction with which you represent part of the business process for the procurement and sales of vehicles, for example:
create vehicle, change vehicle, create purchase order or create sales order.

Features
An action can be a primary action or a secondary action . 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 distinctions are:

Procurement actions versus sales actions

Logistical actions, in other words actions that involve the vehicle itself versus nancial actions, in other words actions that involve
the payment transactions.

An action can in uence the vehicle status. A primary action in uences the primary status, a secondary action 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 Control .

Furthermore, there is the following distinction:

Example

Action that does not change the vehicle status

1. Old vehicle status Quotation created

2. Action Change vehicle is executed

3. Vehicle status remains unchanged as Quotation created

Action that sets the vehicle status to a new value

1. Old vehicle status Quotation created

2. Action Create sales order is executed

3. New vehicle status: Sales order created

An interlinking 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 interlinking 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.

 Caution
The use of interlinking 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 rst action has been completed, the system cannot perform the interlinking action.

A whole host of actions are delivered with the standard system. In Customizing, however, you can modify these actions or de ne and
programme your own actions .

BAdIs are available for the most important actions in the SAP standard system. You can use these BAdIs to adapt the EXECUTE modules for
the actions to suit your own speci c requirements.

Execution of Actions

Use
The execution of actions is the central function of VMS (transaction VELO, tab page Action ). An action always refers to one or more vehicles that
you have previously sought and selected (see: Vehicle Search , Searching for a Vehicle , 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.

This is custom documentation. For more information, please visit the SAP Help Portal 38
 8/17/2021
You call an action by choosing it in the action list eld in the upper screen area and con rming with . 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 eld. 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 de ne 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 nd the key for an action, for example CREA for Create Vehicle in Customizing for VMS under
Control Data De ne Actions (transaction OVELO1).

An action basically refers 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 speci c data to each vehicle, for example for the actions BUPA Assign end customer or INIV 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 rst 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 nd 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 de ne 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.

 Note
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 one. If your order 10 vehicles, for example, a purchase order with 10 order items is created (default).

Only action DELI Create Delivery can, depending on speci c settings in Customizing for Sales and Distribution, create more than one
document at a time.

Performing an Action In Batch Mode

Use
As a system administrator for VMS, you can perform any action you like in batch mode (in other words in a collective run ) and schedule these runs
for any time you like. You de ne with which parameters you want to perform the action in a parameter variant . You can de ne the number of
vehicles for which you wish to perform the action by using selection criteria.

The name of the batch program is RVLCSACREG .

Creating Parameter Variants

1. Choose the transaction VELOV Maintain Variants .

The selection screen for choosing parameter variants appears.

2. Choose Execute directly if you want to display all existing parameter variants.

Only if you want to display speci c parameter variants, for example all parameter variants for a speci c action, should you restrict the
selection and then choose Execute.

A list appears that displays all the parameter variants that correspond to your selection criteria.

3. Choose Create to create a new parameter variant.

This is custom documentation. For more information, please visit the SAP Help Portal 39
 8/17/2021
A screen appears with the elds of all the existing action interfaces.

4. Choose an action. Enter a name for the parameter variant and de ne 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.

5. Save your entries.

Performing an Action with a Parameter Variant in Batch Mode

1. Choose transaction VELOB Perform Actions in Batch .

The Triggering of Action Supported by Report screen appears.

2. Choose the desired action and a parameter variant for this action. The parameter variant is a required eld.

3. 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.

4. If you want the action to be performed for all the vehicles found, set the indicator for performing the action immediately.

Deselect this indicator 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 de ne more precisely.

5. Choose the status that the vehicles for which you want to perform the action should have in the screen areas entitled Primary Sts and
Secondary Sts .

6. Start the batch job or schedule it.

If you want to start the batch job immediately, choose Execute .

If you have set the Trigger Action Directly indicator, 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 set the Trigger Action Directly indicator, 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 Action . After this intermediary step, you then also
receive a list with error and success messages.

¡If you want to schedule the batch job, choose Program Execute in Background .

The screen for entering print parameters appears. Enter the required data and choose . The screen for scheduling jobs appears.
Enter when you want the job to be executed and save your entries.

Programming Your Own Actions

Use the following link to access a comprehensive guideline on programming your own actions (in PDF format). This guideline has been written with
consultants and system administrators in mind.

Creating Actions in VMS

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 gures 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 con rmation 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 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.

This is custom documentation. For more information, please visit the SAP Help Portal 40
 8/17/2021
Here is an example of this procedure. (V) signi es an Interlinking Action .

Sequence Action Description Who does this?

1 CRE1 Create planned vehicle (without Importer

values)

2 CMOD Change con guration of planned Importer

vehicles

3 REAL + ORD1 Allow value assignment for vehicle Importer

and create purchase order
(alternative to steps 1-3 also ORD2 )

4 MORD Change purchase order Importer

5 CONF Con rm purchase order (action not OEM via EDI

contained in the Customizing
settings delivered)

6 SHOW Allow vehicle for search Importer

7 SHMT Con rm transit OEM via EDI

8 GORE Create goods receipt (also possible Importer

later in process)

9 INIV Create inbound invoice (also Importer

possible later in process)

10 RSVN Create reservation Dealer

11 CUOR + HIDE Create sales order and exclude Dealer

vehicle 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 outgoing invoice Importer

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 con guration 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 con rms 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) signi es an Interlinking Action .

Sequence Action Description Who does this?

1 CRCO (V) or Create vehicle and sales order Dealer

1+4 O2CO (V) Create vehicle, purchase order and Dealer

sales order

This is custom documentation. For more information, please visit the SAP Help Portal 41
 8/17/2021

Sequence Action Description Who does this?

2 CHCO Change sales order Dealer

3 BUPA Assign end customer Dealer

4 ORD1 Create purchase order Importer

5 MORD Change purchase order Importer

2+5 CCPO (V) Change sales order and purchase Dealer

order

6 CONF Con rm purchase order (action not OEM via EDI

contained in the Customizing
settings delivered)

7 SHMT Con rm transit OEM via EDI

8 GORE Create goods receipt (also possible Importer

later in process)

9 INIV Create inbound invoice (also Importer

possible later in process)

10 UORD Start rework (purchase order and Importer

transfer posting)

11 UGRE Finish rework (goods receipt) Importer

12 DELI Create delivery Importer

13 GOIS Create goods issue Importer

14 OUIV Create outgoing invoice Importer

Con guration Management

Features

In VMS; we distinguish between the following types of con guration:

Con guration Display Option, Notes

Vehicle con guration Transaction VELO, tab page Detail

The vehicle con guration is part of the vehicle data and is stored in the
vehicle table. It is the only con guration that is relevant in the vehicle
search.

You can save the customer’s desired con guration using action SOCD .
This is the con guration that contains the original con guration desired by
the customer. When, in a make-to-stock scenario , a customer buys a
vehicle for which the con guration does not completely ful ll his/her
requirements, the con guration originally desired can be saved. You can
then evaluate at a later date in how far the actual and target con gurations
differ.

Sales order con guration Standard transaction VA03

In the vehicle list, you can use Display Document to go to this

transaction and to go to the ones mentioned below.

Quotation con guration Standard transaction VA23

Inquiry con guration Standard transaction VA13

Purchase order con guration Standard transaction ME23

Subcontracting purchase order con guration Standard transaction ME23

The sales order, purchase order and subcontracting purchase order con guration in uence the vehicle con guration in such a way that the
vehicle con guration in the vehicle data mirrors the current physical con guration as far as possible.

This is custom documentation. For more information, please visit the SAP Help Portal 42
 8/17/2021
There is the following priority:

1. a. Subcontracting purchase order con guration

2. b. Purchase order con guration

3. c. Sales order con guration

4. d. Planned con guration (vehicle con guration before the documents are created)

A new or changes con guration only in uences the con guration if there is no con guration that has a higher priority (further up in
the above list). If, for example, a purchase order exists, a sales order con guration does not in uence the vehicle con guration, but it
does if there is no purchase order.

 Note
The inquiry con guration and the offer con guration are of no importance in the respect. The inquiry con guration is stored in an
inquiry document but does not have any further control function. The quotation con guration is stored in the quotation document
and serves as a template for the sales order con guration.

Con guration Management in MTS and MTO

Purpose
This process describes how speci c con gurations in uence the vehicle con guration in the MTS and MTO scenario (see below). This process runs
in the background and automatically.

Process Flow
Make-to-Stock-Scenario(MTS)

1. The vehicle con guration is at the beginning of the MTS scenario.

2. As soon as the purchase order is created at the manufacturer, the con guration for the purchase order becomes the vehicle con guration.

3. As soon as a subcontracting purchase order is created for rework, the additional rework characteristics are copied to the vehicle
con guration. If no rework is required, the purchase order con guration and the sales order con guration are the same.

4. At the end, the vehicle con guration shows what the vehicle really looks like.

Make-to-Order-Scenario(MTO)

1. The vehicle con guration is at the beginning of the MTO scenario.

2. As soon as the dealer creates the sales order, the con guration for the sales order becomes the vehicle con guration.

3. As soon as the purchase order is created, its con guration is copied to the vehicle con guration.

4. As soon as a subcontracting purchase order is created for rework, the additional rework characteristics are copied to the vehicle
con guration. After rework, the vehicle con guration and the sales order con guration are the same.

5. At the end, the vehicle con guration shows what the vehicle really looks like.

 Note
All actions for which con guring a vehicle and/or deleting con gurations is possible have a set Template Con guration . You can change
this template con guration using the BAdI VLC_PREPARE_ACTION (method PREPARE_FURTHER_ACTIONS).

The rst elementary action always sets the template con guration for inter-linking actions.

 Note
You can split the con guration 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.

Actions and Con gurations

This is custom documentation. For more information, please visit the SAP Help Portal 43
 8/17/2021
Use
Some actions have a reference or template con guration ; this is the con guration with which the action is called. Actions in uence the vehicle
con guration and in some circumstances may create further con gurations.

Features
Below you can nd a list of all the actions which allow a con guration to take place or which allow a con guration to be deleted.

Action Template Con guration Vehicle con guration Further Con gurations

CREA/CRE1 Create vehicle (values None A new vehicle con guration is

possible)/ create planned vehicle created. If you have not con gured
(no values possible) when you create the vehicle, the
vehicle con guration is created but
remains empty.

CVWT/CVT1 Create vehicle with Template con guration form sales A new vehicle con guration is
template con guration (values document or vehicle created. If you have not con gured
possible)/ Create planned vehicle when you create the vehicle, the
with template con guration (no vehicle con guration is created but
values possible) remains empty.

CMOD Change con guration of Vehicle con guration Vehicle con guration can be changed.
planned vehicles

VDEL Delete vehicles without Not required Vehicle con guration can be deleted.
documents

ORD1 Create purchase order Vehicle con guration Vehicle con guration can be changed. Purchase order con guration is
created and copied to the vehicle
con guration.

MORD Change purchase order Purchase order con guration Vehicle con guration can be changed. Purchase order con guration is
changed. If none exists yet, one is
created.

DORD Delete purchase order item Not required If a sales order exists, the sales Purchase order con guration is
order con guration is copied to the deleted.
vehicle con guration. If not, the
planned con guration is reused.

IQRY Create inquiry Vehicle con guration Vehicle con guration is not changed. Inquiry con guration is created.

DEIQ Delete inquiry Not required Vehicle con guration is not changed. Inquiry con guration is deleted.

OFFE Create quotation Vehicle con guration Vehicle con guration is not changed. Quotation con guration is created.

DEOF Delete quotation Not required Vehicle con guration is not changed. Quotation con guration is deleted.

CUOR Create Sales Order If exists, then quotation con guration, The vehicle con guration can only be The sales order con guration is
otherwise vehicle con guration changed if no purchase order exists. created and copied to the vehicle
con guration if no purchase order
exists.

CHCO Change sales order Sales order con guration The vehicle con guration can only be The existing sales order con guration
changed if no purchase order exists. is changed.

DECO Delete sales order Not required If purchase order exists, the vehicle Sales order con guration is deleted.
con guration is not changed. If no
purchase order exists, the planned
vehicle con guration is reused.

UORD Start rework (purchase order If exists, then sales order Vehicle con guration can be changed. Subcontracting purchase order
and transfer posting) con guration, otherwise vehicle con guration is created and copied
con guration to the vehicle con guration.

UDOR Rework: Delete purchase Not required Vehicle con guration is reverted to Subcontracting purchase order
order and transfer posting what it was before rework. If several con guration is deleted.
rework steps, the correct
con guration can only be reused for
the correct rework step.

This is custom documentation. For more information, please visit the SAP Help Portal 44
 8/17/2021

Action Template Con guration Vehicle con guration Further Con gurations

RETU Create return Sales order con guration Vehicle con guration is not changed. Sales order con guration is copied to
the returns document.

POEU Trade-in Vehicle con guration Vehicle con guration can be changed. Purchase order con guration is
created and copied to the vehicle
con guration.

SOEU Used Vehicle Sales: Create Vehicle con guration Vehicle con guration is not changed. A new sales order con guration is
Order created.

SOCD Save customer’s desired Not required Vehicle con guration is not changed. The con guration desired by
con guration customer is created, if one already
exists, it is changed.

Details for Actions

Use
Since the number of actions delivered by SAP is very large, it is not possible to explain them all in detail in this documentation. Therefore, for the
purposes of this documentation, the standard actions have been grouped together with a short description and commentary.

Features
The standard actions can be assigned to the following business processes:

Standard processing

Vehicle procurement

Vehicle sales and shipping

Goods movements

Special processing

Rework

Processing returns

Trade-in and used vehicle sales

Service processing

Warranty claim processing

Special VMS Actions

Creating Vehicles

Use
The following graphic displays how actions that involve the creation of vehicles can follow one after the other.

This is custom documentation. For more information, please visit the SAP Help Portal 45
 8/17/2021

You can nd further information in the documentation for Logistics – General under Batch Management (LO-BM) , especially Valuation for a Single
Batch .

Prerequisites
You have set the indicator for no update in Customizing for Logistics – General under Material Master Basic Settings Make Global Settings in
the group box for updating administration/management data. This indicator ensures better system performance when vehicles are created. Since
each vehicle of a vehicle model has its own batch and valuation type, the update of the administration data for batch and valuation type when
vehicles are created can be very timely.

Features

Action Description Prerequisites What does the action do? Notes

CRE1 Create planned vehicle Con gurable material, Creates vehicle without Vehicles must belong to the
(without valuation) con guration pro le, class batch and valuation type. same vehicle model and
have the same con guration
The internal vehicle number
is assigned

REAL Allow values for vehicle Planned vehicle Creates batch and valuation
type for vehicles that have
already been created with
CRE1 or CVT1

CVT1 Create planned vehicle with Con gurable material, Creates vehicle without
template con guration (no con guration pro le, class, batch and valuation type and
values possible) template con guration from copies the template
sales document or vehicle con guration from the sales
document or vehicle

CREA Create vehicle (with Con gurable material, Creates vehicle with batch Vehicles must belong to the
valuation) con guration pro le, class and valuation type same vehicle model and
have the same con guration
The internal vehicle number
is assigned The number of Only advisable if the vehicle
the batch and the valuation is really to exist in this form
type are identical to the since the valuation type
internal vehicle number cannot be deleted later

CVWT Create vehicle with template Con gurable material, Creates vehicle with batch
con guration (values con guration pro le, class, and valuation type and
possible) template con guration from copies the template
sales document or vehicle con guration from the sales
document or vehicle

This is custom documentation. For more information, please visit the SAP Help Portal 46
 8/17/2021

Action Description Prerequisites What does the action do? Notes

CMOD Change con guration of Planned vehicle Changes con guration of Only for planned vehicles
planned vehicles planned vehicles since the con gurations
cannot be changed in
purchase order documents
and sales order documents

VDEL Delete vehicles without There must be no equipment Deletes vehicle without Valuation types are not
documents and no document (purchase documents. deleted with this action.
order, sales order etc.) for
If con gurations and batches You can delete valuation
the vehicle
exist for the vehicle, these types individually and
are also deleted. manually using transaction
MM06.

RVAL Revaluate vehicle Vehicle that has already been Changes the vehicle value in This action is useful if costs
posted in goods receipt and the valuation segment of the have been incurred in the
is managed in stock with a material master. VMS process that have to be
quantity of 1 activated (example: payment
A price change document
of duty)
(LO) and an accounting
document (FI) are created.

Procurement: Purchase Order

Use
The following graphic displays how actions that involve purchase orders can follow one after the other.

You can nd further information in the documentation for Materials Management under Purchase Orders (MM-PUR-PO) .

Features
(I) signi es an Interlinking Action .

Action Description Prerequisites What does the action do? Notes

ORD1 Create purchaseorder Vehicle to which you can Creates a purchase order at The complete con guration
assign values, creditor, manufacturer for existing is written to the purchase
purchasing info. record vehicles order (by default).

ORD2 (V) Create vehicle and CREA + ORD1

purchase order

MORD Change purchase order Purchase order Changes the con guration The selected vehicles must
and the delivery date of be in the same purchase
Goods issue should not have
order items and performs order; but not all vehicles in
been posted
pricing again the purchase order have to
be selected

You can only change the

con guration and delivery
date parameters

This is custom documentation. For more information, please visit the SAP Help Portal 47
 8/17/2021

Action Description Prerequisites What does the action do? Notes

DORD Delete order item Purchase order Deletes purchase order

items.
Goods issue should not have
been posted

Procurement: Incoming Invoice

Use
The following graphic displays how actions that involve incoming invoices follow one after the other.

Features

Action Description Prerequisites What does the action do? Notes

INIV Create incoming invoice Purchase order Enters incoming invoice The action is used for
incoming invoices for actions
The goods receipt must have Currency and payment
ORD1 Create purchase
been posted for goods- conditions are taken from the
order and POEU Trade-in
receipt-related invoice purchase order or the
and not for incoming invoices
veri cation purchasing info. record
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 cannot be
created with this action.

IIVR Cancel incoming invoice Incoming invoice Creates cancellation The incoming invoice can
document for incoming only be cancelled completely
invoice All the vehicles in the
incoming invoice have to be
selected

Sales: Reservation, Quotation, Reservation Request, Inquiry

Use
The following graphic displays how actions that involve reservations, quotations, reservation requests and inquiries follow one after the other.

This is custom documentation. For more information, please visit the SAP Help Portal 48
 8/17/2021

The reservation process 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 do the following:

Use objects and documents from the standard SAP system (quotation and inquiry are standard objects, reservations and reservation
requests are VMS objects)

Print documents

Con gure 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.

 Note
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).

Prerequisites

This is custom documentation. For more information, please visit the SAP Help Portal 49
 8/17/2021
You have created vehicles but not yet entered any sales orders for these vehicles.

 Note
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: Vendor and Customer ).

Features
(I) signi es an Interlinking Action .

Action Description Prerequisites What does the action do? Notes

RSVN Create reservation No sales order, no quotation Reserves the vehicles for a The standard validity
and no reservation can exist speci c dealer and writes amounts to three working
for the vehicles the dealer as customer in the days from the creation date
vehicle data You can implement your own
Plant calendar (if you require
logic using the BAdI
one when calculating the
VLC_RESERVATION
validity periods)
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 Creates a quotation for the
dealer dealer for which the
reservation is also valid

RSOF (I) Create reservation and RSVN + OFFE

quotation

DERS Delete reservation Reservations Deletes the reservation for

the vehicles
The selected vehicles must
be reserved for the same If no sales order exists, the
dealer dealer is deleted as
customer form the vehicle
data

DEOF Delete quotation Quotation Deletes the quotation; You can only delete an entire
deletes customer and end document and not only
customer from the vehicle individual items
master and con rms delivery
date

DERO (I) Delete reservation and DERS + DEOF

quotation

RSVM Create request for Creates a reservation You can display the
reservation request for the vehicle 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 three working
days from the creation date
You can implement your own
logic using the BAdI
VLC_RESERVATION

This is custom documentation. For more information, please visit the SAP Help Portal 50
 8/17/2021

Action Description Prerequisites What does the action do? Notes

IQRY Create inquiry Reservation request for the Creates an inquiry for the
same dealer dealer for which the
reservation request is also
valid

RSIQ (I) Create reservation request RSVM + IQRY

and inquiry

DERQ Delete reservation request Reservation request Deletes the reservation

requests for the vehicles

DEIQ Delete inquiry Inquiry You can only delete an entire

document and not only
individual items

DERI (I) Delete reservation request DERQ + DEIQ

and inquiry

Sales: VMS Actions in Sales Order

Use
The following graphic displays how actions that involve sales orders one after the other.

For more information, see the documentation for Sales and Distribution under Sales Order

Features
(I) signi es an Interlinking Action .

Action Description Prerequisites What does the action do? Notes

BUPA Assign end customer Assigns an end customer to An importer can display all
the vehicles end customers, a dealer can
only display his or her own ,
You can also create an end
i.e. the ones he or she
customer
created. This is controlled by
entering the dealer as a
customer in the
Organizational Role

This is custom documentation. For more information, please visit the SAP Help Portal 51
 8/17/2021

Action Description Prerequisites What does the action do? Notes

ADCU Additional End Customers Assigns multiple end End customers created in
customers to a vehicle along speci c roles can also be
with business partner roles assigned to different roles by
and validity dates. You can specifying the required data
also create new end in the end customer details
customers or can change for that particular role.
existing end customer data.

CUOR Create sales order Customer master record for Creates sales order for This action cannot be used
dealer vehicles and enters dealer to for reselling used vehicles
which the vehicles are to be with the Trade-In process.
sold and the vehicle usage in
the vehicle data; deletes the
reservation queue .

You can also create and

assign an end customer

CHCO Change sales order Sales order Changes sales order The selected vehicles must
be in the same sales order;
If the con guration is
but not all vehicles in the
changed, pricing is
sales order have to be
performed again.
selected.
You can also create and
The dealer as sold-to party
assign an end customer.
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 You can only delete a
most recent date. complete sales order, not
individual items.
Deletes end customer and
dealer (customer) from the
vehicle data

CRCO (I) Create vehicle and sales CREA + CUOR Only advisable in the MTO
order Scenario

O2CO (I) Create vehicle, purchase CREA + ORD1 + CUOR Only advisable in the MTO
order and sales order Scenario

CCPO (I) Change sales order and CHCO + MORD Only advisable in the MTO
purchase order Scenario
First changes the sales order
and then the purchase order.

Sales: Assignment of Vehicles to Sales Documents

Use
The following graphic displays how actions that involve the assignment of vehicles to sales documents can follow one after the other.

This is custom documentation. For more information, please visit the SAP Help Portal 52
 8/17/2021

You can nd further information under Assignment of Vehicles to Sales Documents .

Features

Action Description Prerequisites What does the action do? Notes

LORS Create loose relationship Sales document, vehicle Loosely assigns an A link between the sales
appropriate vehicle to a document and vehicle is
sales document with a saved
customer’s desired
con guration

DELR Delete loose relationship Loose relationship

TIRS Create tight relationship Sales document, vehicle Tightly assigns an Batch and valuation type of
appropriate vehicle to a vehicle are entered in the
sales document with a sales document, and the key
customer’s desired of the sales document in
con guration entered in the vehicle
document table

DETR Delete tight relationship Tight relationship The sales document does not
have to be deleted

Sales: Outgoing Invoice

Use
The following graphic displays how actions that involve outgoing invoices can follow one after the other.

For more information, see the documentation for Sales and Distribution under Billing .

Features

Action Description Prerequisites What does the action do? Notes

This is custom documentation. For more information, please visit the SAP Help Portal 53
 8/17/2021

Action Description Prerequisites What does the action do? Notes

OUIV Create outgoing invoice Sales order Bills the sales order with the Outgoing invoices are only
most recent date possible if related to sales
order, not related to delivery

More than one order can be

grouped into an outgoing
invoice if speci c criteria
have been ful lled

OIVR Cancel outgoing invoice Outgoing invoice Cancels existing outgoing You can only cancel an entire
invoice document and not only
individual items

Shipping: Delivery

Use
The following graphic displays how actions that involve deliveries follow one after the other.

For more information, see the documentation for Logistics Execution under Delivery Processing .

Features

Action Description Prerequisites What does the action do? Notes

DELI Create delivery Sales order Creates delivery for sales You can split a sales order
order with the most recent into different deliveries
Vehicle must be in importer’s
date
stock More than one order can be
grouped into a delivery if
speci c criteria have been
ful lled For this to be the
case, the appropriate
indicator in the sales area
data of the customer master
record (tab page for
shipping) must have been
set

You do not have to select all

the vehicles in a sales order

DEDE Delete delivery Delivery Deletes delivery for sales You can only delete a
order with the most recent complete delivery, not
date individual items

Goods Movements: Goods Issue, Goods Receipt

Use
The following graphic displays how actions that involve goods movements can follow one after the other.

This is custom documentation. For more information, please visit the SAP Help Portal 54
 8/17/2021

You can nd further information in the documentation for Logistics Execution under Goods Issue and in the documentation for Materials
Management under Goods Receipt .

Features

Action Description Prerequisites What does the action do? Notes

GORE Create goods receipt Purchase order Creates material document The action is used for goods
for the goods receipt with receipts for actions ORD1
reference to a purchase order 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 This action can cancel a
document for goods receipt complete goods receipt or
individual document items.

STOL Storage location posting Goods receipt Creates a material document This action can still be
for the transfer posting from performed after a delivery
Vehicle cannot be in
one storage location to has been created as long as
repair/rework
another 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 The storage location from
for a goods/stock issue 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 This action only cancels a
document for the complete document.
goods/stock issue
It can only be used for goods
issues that have been
created with the action GOIS.

Rework (With Goods Movements)

This is custom documentation. For more information, please visit the SAP Help Portal 55
 8/17/2021
Use
The following graphic displays how actions that involve rework follow one after the other.

The reworker is represented in the SAP system as a vendor in the role of a subcontractor. For more information, see the documentation for
Materials Management under Subcontracting .

Vehicles can be reworked more than once.

 Caution
Processing rework is only possible using an external service provider.

 Caution
Actions DORD, MORD, GORE, GRER, INIV and IIVR cannot be used in the rework process. You can only use the four actions (listed below) in the
rework process.

Prerequisites
You have de ned which characteristics are to be reworked by which vendor.

If only part of the con guration is to be assigned to a subcontractor order, you have implemented BAdI VLC_CONFIG_SPLITTER, which
compares the purchase order con guration with the sales order con guration. The differences between these two de ne the scope of the
work to be done.

Features

Action Description Prerequisites What does the action do? Notes

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

You can enter a default value

in the eld Reworker with the
user parameter
VELO_REWORKER

This is custom documentation. For more information, please visit the SAP Help Portal 56
 8/17/2021

Action Description Prerequisites What does the action do? Notes

UDOR Delete rework purchase The vehicle must be in Deletes the subcontracting
order and transfer posting subcontracting stock purchase order and creates a
cancellation document for
the transfer posting

UGRE Finish rework (goods The vehicle must be in Creates a goods receipt The goods receipt is posted
receipt) subcontracting stock document with reference to for all the components to be
the subcontracting purchase provided in subcontracting
order purchase order

UGRR Rework: cancel goods Creates a cancellation

receipt document for the goods
receipt for the
subcontracting purchase
order

Processing Returns

Use
The following graphic displays how actions that involve returns follow one after the other.

A vehicle that is sold and then returned to stock is usually resold using the normal sales process for new vehicles (see: Sales: Reservation,
Quotation, Reservation Request, Inquiry and Sales: Sales Order ). However, if the vehicle is classi ed as being a used vehicle, actions SPEU and
SOEU from the Trade-In process succeed the actions displayed above when the vehicle is resold.

For more information, see the documentation for Sales and Distribution under Returns .

Features

Action Description Prerequisites What does the action do? Notes

RETU Create return Sales order Creates return for a vehicle A return can only be created
that 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 de ne item

category, copy control and
item category determination

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 Returns delivery Posts goods receipt to the
delivery blocked stock returns

This is custom documentation. For more information, please visit the SAP Help Portal 57
 8/17/2021

Action Description Prerequisites What does the action do? Notes

RECM Create credit memo for Return Creates a credit memo for
returns the return

REUS Transfer vehicle from Vehicle in blocked stock Posts vehicle from blocked
blocked stock returns to returns stock returns to unrestricted-
unrestricted-use stock use stock so that it can be
resold

Used-Vehicle Scenario

Use
Vehicles can be taken in part exchange/as a trade-in or bought back more than once.

You can nd further information in the documentation for Materials Management under Purchase Orders (MM-PUR-PO) .

 Note
If you trade-in/buy-back using a one-time vendor, you cannot post the inbound invoice with action INIV but only with the SAP standard
transaction.

The following graphics illustrate the three possible used-vehicle process scenarios:

Scenario 1:

This an independent process with vehicle model specially used for the used vehicle scenario. Independent process means that the used vehicle
process is isolated from the sales and distribution process of new vehicles and is represented in an own VMS matrix. The used vehicle record can
be created in reference to a new vehicle and con guration can be mapped automatically.

Scenario 2:

This is custom documentation. For more information, please visit the SAP Help Portal 58
 8/17/2021

This is an independent process with a used vehicle model, but without a reference to a new vehicle. Con guration can be entered manually.

Scenario 3:

This is custom documentation. For more information, please visit the SAP Help Portal 59
 8/17/2021

The used vehicle process directly follows the sales and distribution process of new vehicles. The same matrix is used. The vehicle that is sold as a
new vehicle is bought back and resold as a used vehicle.

Features
(I) signi es an Interlinking Action .

Action Description Prerequisites What does the action do? Notes

BBDF De ne/change buy-back This action allows you to This action can normally be
conditions de ne buy-back conditions, executed after creation of the sales
such as: order for the new vehicle.

Planned buy-back
date

Buy-back price

Short and long text

describing other
conditions

CREA Create vehicle (with See: Creating Vehicles

valuation)
When you trade-in vehicles that you
have already sold as an importer,
you do not have to perform this
action.

If a used-vehicle model is chosen,

this action allows you to specify the
original vehicle and, provided a
mapping has been de ned, map the
original con guration to the used-
vehicle con guration.

This is custom documentation. For more information, please visit the SAP Help Portal 60
 8/17/2021

Action Description Prerequisites What does the action do? Notes

CRUV Create used vehicle Con gurable material, This action creates the This action supports automatic
con guration pro le, class vehicle based on a used- mapping of the con gurations.
vehicle model
Model de ned in The used-vehicle indicator is
transaction code veloum automatically switched.

UVSW Switch “used vehicle” ag Switches the ag for You can use this action when your
marking the vehicle as a used-vehicle process follows the
used one on/off new- vehicle process in your matrix.
In other words, when the vehicle has
been created for the new-vehicle
process and the same vehicle
record is being used for the used-
vehicle process.

POEU Trade-in Vehicle Creates a normal purchase A purchasing info record should not
order for the vehicles exist for the vendor.

In contrast to action ORD1 If a record does exists, you must

Create Purchase Order , ensure (in the pricing procedure)
the price and the vendor that the price entered manually has
(also one-time vendor) have priority over and above the price in
to be entered manually in the purchasing info record.
the interface
You can access a calculation sheet
in this action, provided the former
has been created for the vehicle. In
this case, the elds Net Price and
Currency are disabled. Their values
are taken from the calculation sheet.

GORE Create goods receipt See: Goods Movements: GI, GR

CRPU (I) Create and trade-in CREA + POEU This action can only be performed
vehicle for exactly one vehicle.

Actions CREA, POEU and CRPU are

usually executed during buy-back.
You can also execute them when
buy-back conditions are de ned (in
other words, when the vehicle is
sold) if you prefer to have the
purchase order in advance, for
example, for planning purposes.

RVAL Revaluation Changes the vehicle value in If a used-vehicle model is chosen,

the valuation segment of the you can access the pricing
(see also: Creating Vehicles
material master. procedure and edit the
, action RVAL)
corresponding section. The
Debit/Credit Amount eld is
disabled. Its value is calculated
from the appropriate section of the
calculation sheet.

SPEU Used vehicle sales: The vehicle has been Overwrites the gross list If a used-vehicle model is chosen,
determine price returned to the importer’s price in the vehicle data you can access the pricing
stock due to trade-ins or with the resell price procedure and edit the appropriate
returns processing. section. The eld Resell Price is
The resale price is a
disabled. Its value is calculated
manually xed price that is
from the corresponding section of
independent of the
the calculation sheet.
con guration of the vehicle.

This is custom documentation. For more information, please visit the SAP Help Portal 61
 8/17/2021

Action Description Prerequisites What does the action do? Notes

SOEU Used vehicle sales: create The vehicle has already Creates a sales order for the This action is a very simpli ed
order been sold once and has used vehicle and can version of action CUOR Create
been returned to stock by a overwrite the entries for Sales Order , for which numerous
trade-in process or returns customer, end customer and restrictions apply:
processing vehicle usage
No returns processing is
Resale price (action SPEU). allowed for sales orders that
have been created with
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 Change Sales
Order but they can be
deleted with action DECO
Delete Sales Order .

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 n the case of CUOR, in
other words, the prices depend on
the con guration during pricing (see
also: Creating a Variant Condition
for Pricing ). You should not,
however, use condition type VA00
for action SOEU since the price is
independent of the con guration
here and determined manually using
action SPEU. This resale price is
transferred as condition type PR00
by default. You can de ne 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
VLC_EXECUTE_ACTION, method
DATA_CHANGES_BEFORE_ACTION.
You can enter the document type in
VLCACTDATA_CS-AUART.

CSCR Create calculation sheet You have de ned a Creates a calculation sheet The calculation sheet can be
for used vehicle calculation sheet pro le. that is attached to the accessed in the following standard
vehicle. actions: BBDF, POEU, RVAL and
SPEU.

CSED Edit sales order You can use this action after the
calculation sheet sales order has been created for the
used-vehicle in order to change the
SD order pricing. You can change the
item and header pricing in the same
way as in transaction VA01 .

This is custom documentation. For more information, please visit the SAP Help Portal 62
 8/17/2021
De nition of Buy-Back Conditions

When a new vehicle is sold, buy-back conditions are de ned. These conditions usually contain:

the buy-back date

the price to be paid if the vehicle is returned on this date

You can also de ne additional conditions. Generally speaking, these are additional prerequisites for the agreed price. If any of these additional
conditions are not met, the price can be reduced (or buy-back can be rejected).

There are three possible situations when a customer initiates buy-back:

The vehicle was sold by this importer and buy-back conditions have been de ned at the point of sales of the new vehicle.

The vehicle was sold by this importer but buy-back conditions have not been de ned.

The vehicle was not sold by this importer.

In the rst case, the price is determined based on the prede ned buy-back conditions and the state of the vehicle. In cases 2 and 3, the vehicle
price is determined on the whole by current market conditions.

Pricing of Used Vehicles

In contrast to price determination for new vehicles where the con guration of the vehicle plays an important role, the con guration of used
vehicles (see below) has only an indirect in uence on the price. The base price of used vehicles is usually determined according to the market
conditions for that particular model, taking into consideration its age, mileage and several other factors. Additional discounts or surcharges may
be applied based on other conditions, for example, special conditions for a particular customer.

Used-Vehicle Calculation Sheet

In order to provide an overview over the entire used-vehicle process and enable tracking of the cost structure for each step of this process, the
calculation sheet is integrated in the related actions (for example, actions BBDF, POEU, RVAL and SPEU). The sheet is analogous to the standard
SD pricing procedure. Sections of the sheet are assigned in Customizing to the corresponding actions and can therefore be edited only by these
actions. You can assign actions to steps in your calculation sheet by using transaction code OVELO30 .

You can map a vehicle model to the calculation sheet pro le that you have previously de ned in Customizing for the Vehicle Management System
(VMS) under Control Data De ne Calculation Sheet Pro le by using transaction code VELOMCS. If there is no entry for your used-vehicle model,
the global parameters from transaction OVELO00are used.

The standard pricing procedure and assignment of its sections to the VMS actions are contained in standard SD Customizing. You can use the
standard settings as a copy template to create your own calculation sheet and assignments.

 Note
You can access the calculation sheet in display mode from the vehicle detail screen.

Con guration of Used Vehicles

Con guration of used vehicles is general, whereas for the new vehicle every option in the con guration is usually de ned on a very detailed level
(for example, the exterior color can be de ned as a tint of red for the new vehicle, whilst for the used vehicle all possible tints are described simply
as red).

Used-Vehicle Model

You can de ne a used-vehicle model by using transaction code VELOUM .

There are two possible options in the used-vehicle process:

Work with the existing original vehicle

In this case you cannot change the con guration of the used vehicle. In other words, the original con guration of the new vehicle is
preserved for the used-vehicle process. You can mark this vehicle as a used vehicle by executing action UVSW ( Switch “used vehicle” ag)
in order to differentiate between vehicles that are new and vehicles that are used.

Work with a special model with a special “used-vehicle” con guration

This is custom documentation. For more information, please visit the SAP Help Portal 63
 8/17/2021
Even if the vehicle object for the original new vehicle has already been created in the system, a new vehicle object has to be created in this
case. New used-vehicle objects have a more generic con guration. You can maintain the link between new and used-vehicle objects and the
mapping of the con gurations in action CRUV.

You can use different number ranges for used-vehicle models. You can assign number ranges to vehicle models by using transaction code VELONR ,
provided that you have maintained your used-vehicle model by using transaction code VELOMNR.

Mapping Between the New Vehicle Con guration and the Used-Vehicle Con guration

Mapping of models

You can use transaction code VELOCM to de ne a mapping between a new-vehicle con guration and a used-vehicle con guration. The table below
shows an example of such a mapping:

Source Source Source Value Assignment method Destination Destination Destination value
con guration characteristic con guration characteristic

New vehicle Exterior color Lava red Directly in Used vehicle Exterior color Red
con guration transaction VELOCM con guration

New vehicle Exterior color Fire red Directly in Used vehicle Exterior color Red
con guration transaction VELOCM con guration

New vehicle Exterior color Dark red Directly in Used vehicle Exterior color Red
con guration transaction VELOCM con guration

New vehicle Characteristic N BAdI Used vehicle Characteristic M

con guration con guration
VLC_USED_VEHICLE

…. … …. …. …. …. …..

This con guration mapping can be performed by using the appropriate function in action CRUV. It also supports a partial mapping. In this case, you
have to enter the rest of the con guration manually. Generally speaking, you can also map the characteristic values of one con guration to the
next. In cases where a simple one-to-one mapping is not possible or in cases where some sort of a conversion is required, you can use BAdI
VLC_USED_VEHICLE.

Mapping of characteristics

Generally speaking, the new-vehicle model is mapped to the characteristic of the used-vehicle con guration (for example, characteristic MODEL
with the possible values “VW Golf 3”, “VW Golf 4”, “Audi A4” ). You can use transaction code VELOMMAP to do this. The table below shows an
example of such a mapping:

Model Destination characteristic Destination value

VW Golf 3 Model VW Golf 3

VW Golf 4 Model VW Golf 4

Audi A4 Model Audi A4

Service Processing

Use
The following graphic displays how actions that involve service follow one after the other.

This is custom documentation. For more information, please visit the SAP Help Portal 64
 8/17/2021

There are two options for service processing:

Processing only with a service noti cation , 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 noti cation and a service order . This is sensible if you have planned and have to calculate materials, resources
and work forces. If no details are required for actions, measures, persons responsible etc., you can ignore the service noti cation and create
a service order directly.

You can nd further information in the documentation for Customer Service under Service Object as Equipment , Service Noti cation , Service
Order and Processing Services .

Features
(I) signi es an Interlinking Action .

Action Description Prerequisites What does the action do? Notes

CREQ Create equipment Vehicle Creates an equipment for a

vehicle and writes the
equipment number in the
vehicle data

SMNO Process service noti cation Optional: equipment Creates a CS service If you enter the value X for
noti cation with claim items user parameter
and organizational data and VELO_SMNO_POPUP_MODE,
allows you to change or you always branch directly to
complete existing service the screen for creating a new
noti cations. service noti cation or, if a
noti cation already exists, to
You can enter a separate item
the screen for changing this
with problem, affected object
noti cation. This is useful if
part, reason for claim,
you fundamentally do not
actions and measures for
want to allow more than one
rectifying the damage for
service noti cation.
each claim.

SMOR Create service order Optional: service noti cation Creates a CS service order If you enter the value X for
with operations. user parameter
VELO_SMOR_OPR_MODE,
Items in the service
exactly one operation will be
noti cation become
created in the service order.
operations in the service
The service noti cation items
order. You can propose
are not copied.
planned working times for
the operations.

The order can be released

automatically depending on
which settings have been
made in Customizing for CS.

SMCO Con rm service order Service order Con rms actual working time External services cannot be
and used components to the con rmed.
service order.

Any number of partial

con rmations possible.

This is custom documentation. For more information, please visit the SAP Help Portal 65
 8/17/2021

Action Description Prerequisites What does the action do? Notes

SMIO Create billing request for Service order Creates a billing request for The billing document has to
service order a service order. be created outside VMS (for
example, in collective
The billing request covers all
processing).
con rmed components and
working times for this service
order for which no billing
request yet exists.

SMOC (I) Create and con rm service Optional: service noti cation SMOR + SMCO
order

Warranty Claim Processing

Use
This function allows you to link warranty to a vehicle. There are two possible ways you can link a warranty to a vehicle:

Warranty Claim Processing with Equipment

Warranty Claim Processing without Equipment

Features
Warranty Claim Processing with Equipment

The following graphic displays how actions that involve a warranty follow one after the other

These three actions link the applications Vehicle Management System (IS-A-VMS) and Warranty Processing (LO-WTY). They serve to create the
master data ( Equipment, Master Warranty, Measuring Points ) that is necessary to carry out the Warranty Check in Processing , in other words, to
check automatically whether a warranty still exists for a speci c vehicle or not .

Action Description Prerequisites What does the action do? Notes

CREQ Creates equipment for the Vehicle Creates an equipment for a

vehicle vehicle and writes the
equipment number in the
vehicle data.

This is custom documentation. For more information, please visit the SAP Help Portal 66
 8/17/2021

Action Description Prerequisites What does the action do? Notes

WRTY Assign master warranty Equipment for vehicle, Assigns master warranties to You can use BAdI
master warranty equipment that has been VLC_MASTER_WARRANTY to
created using action CREQ. read master warranties for
vehicles for which you have
created equipment using
action CREQ. These master
warranties are then to be
assigned to all vehicles in
action WRTY.

MEAS Assign measuring points Equipment for vehicle, Creates measuring points for
reference equipment the measurement positions
and warranty counters for the
reference equipment for
equipment that has been
created using action CREQ.

Warranty Claim Processing without Equipment

Action GEOB creates a type of intermediate object for a vehicle for which no equipment exists. This action is required technically if you want to
assign measuring points or master warranties to a vehicle without equipment.

You can assign the master warranties and measuring point in the vehicle detail screen by choosing MW/Meas.P . The master warranty is assigned
in the upper detail screen. Do the following:

1. Choose Append Row.

2. Enter warranty type, master warranty and start date.

The measuring points are assigned in the lower detail screen.

3. Choose Creat e measuring points .

4. Enter the measurement position, description and characteristic.

These values are de ned in the template object. In Customizing choose Plant Maintenance and Customer Service Warranty Claim
Processing Warranty Claim De ne Template Objects .

Action Description Prerequisites What does the action do? Notes

GEOB General object number Vehicle Creates a type of This action is technically
intermediate object for a required if you want to
vehicle for which no assign measuring points or
equipment exists. master warranties to a
vehicle without equipment.

This is custom documentation. For more information, please visit the SAP Help Portal 67
 8/17/2021

Action Description Prerequisites What does the action do? Notes

WYVH Assign master warranty Vehicle, master warranty Assigns master warranties This action is required for
to a vehicle for which there batch processing.
is no equipment.

Special VMS Actions

Features

Action Name Prerequisites What does the action do? Notes

SOCD Save customer's desired Saves additional This action serves above all to
con guration con guration for vehicle store a desired con guration for
the vehicle which you can then
later compare with the actual
con guration

SMOD Change vehicle De ned values in Allows changes to vehicle Example for an action that works
Customizing for vehicle attributes and quali ers (see with additional data ( lled by
usage, vehicle search area Customizing under additional elds on the initial
and sharing level Enhancements Program screen) and with quali ers (ALV
Actions and list on entry screen)
De ned quali ers in
Enhancements De ne
Customizing and You can program any number of
Additional Data for Vehicle )
assignment to action SMOD such actions that work with
different elds

CORR Correct status (without Internal action that, in This action cannot be started
check) contrast to the other actions, manually using transaction VELO
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

HIDE Exclude vehicle from Sets the vehicle attribute for The actions HIDE and SHOW have
search visibility to not displayed no effect in themselves only in
combination with one of the
The dealer usually performs
following implementations:
this action in the MTS
Scenario as soon as he has You can use the visibility
bought a vehicle so that dependently of the VMS
other dealers do not have role (dealer, importer) as
access to the vehicle parameter when selecting
vehicles from the
Default setting = vehicles not
database (BAdI
displayed
VLC_SEARCH_ADAPTION)

You can use the visibility

according to the selection in
SHOW Allow vehicle for search Sets the vehicle attribute for Category Management (vehicle
visibility to displayed lter) as parameter. Allows
changes to vehicle attributes and
quali ers (see Customizing under
Enhancements Program
Actions and
Enhancements De ne
Additional Data for Vehicle )

CAMP Assign sales campaign Values for sales campaign Sets the vehicle attribute The point of this action is to
(transaction VELOC) Sales campaign to a new trigger pricing again in the sales

This is custom documentation. For more information, please visit the SAP Help Portal 68
 8/17/2021
value order (due to assigned sales
Action Name Prerequisites What does the action do? Notes
campaign) There are two options:

You can add the eld as an object

characteristic to the vehicle
con guration (see: Adding Object
Characteristic to Con guration)

You can use the options for

exible enhancements to
SD pricing

LCTN Set vehicle location Values for vehicle locations Sets the vehicle attribute
in Customizing for VMS Vehicle location to a new
(transaction OVELOL) value and assigns the
address of the vehicle
location to the vehicle

SHMT Con rm transit Example for an action that Actions such as these, for
only changes the status and example Con rm purchase
does not create any order can be de ned in
documents Customizing

STWO Trigger Work ow event Organizational structure, Only useful as part of an

tasks inter-linking action

Triggers the sending of e-

mails with Work ow items,
these refer to the actions
with which the action STWO
has been linked

MSSO Output messages Customizing for VMS for Outputs messages (possibly You can display the sent
message determination as part of an inter-linking messages in transaction VELO
action) (tab page Details, screen Vehicle
Data, button Messages ).
Pushbutton )

You can nd 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 Assigns documents to a You can display the stored
documents vehicle documents in transaction VELO
(tab page Detail, screen Vehicle
Data, button Messages ).
Pushbutton Documents )

You can nd further information in

the documentation for Cross-
Application Components under
Business Document Navigator.

ARCS Set archiving indicator The action matrix must be Flags vehicles for archiving See: Archiving Vehicles
set so that only vehicles
This action is an internal action
with the appropriate status
that is executed within transaction
(example: sold, delivered,
VELOARSL
paid) are agged for
archiving.

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 Reports SAP SCEM events to See: Connection to SAP SCEM
vehicle must exist in SAP the Event Handler, which is
You can display the SCEM
This is custom documentation. For more information, please visit the SAP Help Portal 69
 8/17/2021
You can display the SCEM
SCEM. assigned to the vehicle
Action Name Prerequisites What does the action do? Notes
information in transaction VELO
(tab page Detail, screen Vehicle
Data. Pushbutton SCEM).

CRMV Export vehicle to CRM Individual object setup on Transfers vehicle data, See: Connection to SAP CRM
CRM must have been con guration data, history
Sales process takes place in SAP
prepared to import VMS entries and relationships
DIMP
vehicles with dealers and end
customers to SAP CRM and Then post-sales processes, for
maps vehicle to “individual which the vehicle is the center of
object” 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 Transfers Assignment of See: Connection to SAP CRM
attached to the replicated Vehicles to Sales Documents
Sales process takes place in SAP
sales document using the to SAP CRM
CRM. The assignment of vehicles
Late Order Assignment
to sales documents, however,
functionality
takes place beforehand in SAP
DIMP

Furthermore, there are the following VMS actions for the multi-plant scenario:

Action Name Prerequisites What does the action do? Notes

CPGM Cross-Plant Goods Enables the goods

Movement movement of a vehicle from
one plant/storage location to
another plant/storage
location

REPL Realize in plant Creates a batch for a vehicle You can execute REPL on any
in an additional plant 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 speci c plant if a batch
has been created in this
plant.

The standard system provides you with the technical basis required to implement a multi-plant scenario. However, you still have to develop
additional actions using the VMS standard EXECUTE function modules. For more information, see Programming Your Own Actions.

Assignment of Vehicles to Sales Documents

Use
As importer, you can use this functionality (transaction VELO, tab page Assignmnt ) to search for sales documents that a dealer has entered and to
assign an appropriate vehicle from the warehouse stock or order pipeline to each sales document.

This is particularly useful in the following cases:

if your dealer can access your system but has not been able to nd a vehicle that corresponds to the customer’s desired con guration

This is custom documentation. For more information, please visit the SAP Help Portal 70
 8/17/2021
if your dealer does not have access to your system and vehicles and enters sales document with the customer’s desired con guration
“offline”, for example in SAP CRM Mobile Sales

if, for sales and distribution reasons, you want to assign a vehicle, which you have already promised to one customer and thus already
assigned a sales document, to another customer at short notice without having to cancel the original sales document

This function is mainly used within the framework of the make-to-stock scenario (MTS) , for example as is common practice in the USA .

Prerequisites
The sales documents contain a con guration but do not yet have a tight relationship with a vehicle, in other words, batch and valuation type have
not yet been de nitively entered in the sales document.

No follow-on documents (delivery, billing documents etc.) for sales orders without a vehicle have been created in standard SD, in other words
outside of VMS.

Features
The functionality refers to the sales document type inquiry, quotation and order .

You can search for the sales documents either according to speci c selection criteria or according to vehicle model.

In BADI VLC_EXECUTE_ASSIGNMT you can de ne exactly which con guration characteristics and sales document elds or vehicle elds
have to correspond so that a vehicle is suited to a sales document.

The standard system settings dictate that all con guration characteristics have to correspond so that a sales document suits a vehicle. In
other words, the sales document con guration must be 100% identical to the vehicle con guration. If you enhance the standard
implementation of the BAdI appropriately, you can also include sales document or vehicle elds in the matching process.

Furthermore, the standard settings dictate that the customer’s desired con guration is not overwritten by the vehicle con guration when a
tight relationship is created (see below).

You can also control the search for suitable vehicles for a sales document via the normal search pro le for the vehicle search. BAdI and
search pro le act in combination during the search so that the settings for the search pro le override the BAdI settings, where necessary.

If you are working with categories, the vehicles are listed in the hit list according to the priorities de ned in Category Management . You can
change this sequence using the above-mentioned BAdI.

You can compare the con guration of a sales document with the con guration of a vehicle that is found and, based on this result, decide
whether you want to assign the vehicle to the sales document.

When you assign a vehicle to a sales document, you can decide between a loose relationship between vehicle and sales document and a
tight relationship.

The loose relationship is a type of reservation. Technically speaking, the relationship between sales document and vehicle is saved in
a separate third table ; sales document and vehicle are “ignorant” of each other.

The tight relationship is a type of con rmation of the loose relationship. Technically speaking, the batch and valuation type of the
vehicle are entered in the sales document and the key for the sale document is entered in the appropriate vehicle document table;
sales document and vehicle therefore “know” of each other’s existence.

Both types of relationship can be deleted again without the sales document having to be cancelled.

The following actions serve to create and delete relationships:

LORS Create loose relationship

TIRS Create tight relationship

DELR Delete loose relationship

DETR Delete tight relationship

Loose relationships can be replaced by loose relationships without the original loose relationship having to be deleted beforehand.
This is useful if customer B is more important than customer A, even though customer B arrived later than customer A.

You execute individual processing in transaction VELO, mass processing in transaction VELOAS.

This is custom documentation. For more information, please visit the SAP Help Portal 71
 8/17/2021
Mass processing makes sense if the manufacturer generally produces to stock and you want to nd suitable vehicles for a large number of
sales documents.

If you have not found a suitable vehicle for a sales document, you can create a vehicle with a template con guration . You have the following
actions at you disposal for this:

CVWT Create Vehicle with Template Con guration, with Batch and Valuation Type

CVT1 Create Vehicle with Template Con guration, without Batch and Valuation Type

If, in transaction VELO on the tab page Assignmnt (Assignment), you have selected a sales document without a relationship to a
vehicle, the template con guration is the con guration of the sales document. If, on the other hand, you have selected a vehicle the
template con guration is the con guration of the vehicle.

You can, of course, as with all other actions, call these two actions from the tab page Detail as well, after you have searched and
chosen a vehicle. Then the template con guration is always the vehicle con guration.

 Note
You can use method CHANGE_KB_PARAMETERS of BAdI VLC_SCE_PARAMETERS to change the parameters for knowledge-base
object and runtime version of knowledge base when you create a vehicle with the template vehicle or sales document.

Assigning a Vehicle to a Sales Document

Individual Processing
1. Choose transaction VELO and then tab page Assignmnt (Assignment) in the Vehicle Manager screen.

2. In the area entitled Search for Sales Documents , select one or more vehicle models. Then choose whether you are want to search for
inquiries, quotations or sales orders by selecting the appropriate entry in the Transaction gro up eld. Start the search by choosing Find
with Models .

Alternatively, you can restrict your search further by choosing Selection Options. In the selection options screen, you can display further
selection options via New Field Selection and activate them by double-clicking. The elds and values in the search are saved dynamically
and proposed for the next search.

In the area Search Result: Vehicles and Sales Documents , all the sales documents that are found are displayed in the upper table. The
search only nds sales documents without a link to a vehicle (no symbol) and sales documents with a loose relationship to a vehicle (symbol
), but not sales documents with a tight relationship.

3. Select exactly one sales document in the list of sales documents.

4. If necessary, choose a search pro le for the vehicle search and start the search with Find Vehicle.

In the lower table, all the vehicles are displayed that belong to the sales document and also the vehicles for which there is already a tight
relationship between the vehicle and a sales document (symbol ).

5. Select exactly one entry in the list of vehicles.

6. Compare the con guration of the selected sales document with that of the selected vehicle. Choose Con guration Sales Document
above the upper table or Con guration Vehicle above the lower table.

7. In the action list eld, choose action LORS to create a loose relationship or action TIRS to create a tight relationship and con rm with
Okay.

The tab page Action appears. You can see the chosen vehicle on the left-hand side, and details for the sales document and vehicle on the
right-hand side. Here you can compare the con gurations of sales document and vehicle again.

8. Start the action with Execute Action.

The system executes the action. You can display the details of the action execution in the log.

Mass Processing
1. Choose transaction VELOAS.

All the vehicle models that are assigned to the user are displayed automatically.

This is custom documentation. For more information, please visit the SAP Help Portal 72
 8/17/2021
You can change the selection manually with Selection Options. In the selection options screen, you can display further selection options
via New Field Selection and activate them by double-clicking. The elds and values in the search are saved dynamically and proposed for
the next search.

2. In the Transaction group eld, choose whether you want to search for inquiries, quotations or orders, choose the desired action and, if
necessary, a search pro le for the vehicle search.

3. Choose Execute.

The system displays a list of the vehicles that are found.

4. Select the desired sales documents and choose Execute.

The system executes the action. No vehicle list is displayed for the assignment of the vehicles to the sales documents, but rather the
vehicle with the highest priority is chosen and assigned. You can display the details of the action execution in the log.

Warranty Claim Display

Use
In the Vehicle Manager (transaction VELO, tab page Warranty ), you can now display warranty claims that have been created for the appropriate
vehicle in component LO-WTY Warranty Claim Processing (transaction WTY).

You can nd further information in the documentation for Warranty Claim Processing

Tab page Warranty is active in the standard system. You can deactivate this tab page by using BAdI VLC_USER_INTERFACE.

Features
Preparing the Vehicles

You have to prepare the VMS vehicles for the creation of warranty claims in warranty claim processing. To do this, create the master data( master
warranties , measuring points, if required also equipment) that is necessary to carry out the warranty check in processing , that is, the procedure
required to automatically check whether a warranty exists for this vehicle.

This can happen in one of two ways:

Procedure with Creation of Equipment

In VMS, you create an equipment item for each vehicle with action CREQ . With action WRTY, assign one or two master warranties to the
equipment (not directly to the vehicle), use action MEAS to assign measuring points to the equipment. Next, enter warranty claims for the vehicle
in the component Warranty Claim Processing .

You can use BAdI VLC_MASTER_WARRANTY to read master warranties for vehicles for which you have created equipment using action CREQ.
These master warranties are then to be assigned to all vehicles in action WRTY. The default settings dictate that the master warranty that was
entered on the interface of action WRTY is used. If the BAdI is implemented, the data entered on the interface is overwritten.

Procedure without Creation of Equipment

You do not use actions CREQ, WRTY or MEAS and do not create equipment for the vehicle, but you assign master warranties and measuring points
directly to the vehicle.

First of all, as preparation, you create a general object number with action GEOB . This step is technically essential and creates a type of
intermediate object in the background.

You then choose MW /MeasP in the vehicle detail sapurl_link_0003_0009_0009 display and assign master warranties and measuring points.

This is custom documentation. For more information, please visit the SAP Help Portal 73
 8/17/2021

If you want to assign master warranties for more than one vehicle at the same time, you can use action WYVH Assign Master Warranty to Vehicle.

Display of Warranty Claims(tab page Warranty )

All existing warranty claimsfor the chosen vehicle with all the warranty claim data is displayed

By double-clicking on the claim number you can access the Warranty Claim Processing transaction (transaction WTY) and display the warranty
claim with all the information on its processing.

Archiving Vehicles

Use
You can archive in batch vehicles that have been sold and that you only require for evaluations and for displaying history. This enables you to keep
the load on the database to a minimum. And thus you can improve system performance when you search for current vehicles.

There are no rules dictating when vehicles should be archived. The Vehicle Management System is very exible as regards how and where it is used
and therefore the business requirements in this respect can be very different.

 Recommendation
We recommend that you do not archive vehicles within the warranty period.

Integration
SAP standard archiving is used for archiving vehicles.

You can nd in the documentation for Cross-Application Components under Introduction to Data Archiving (CA-ARC) .

Features
First of all, vehicle archiving allows you to select the vehicles you wish to archive (transaction VELOARSL) and then archive them by using
SAP standard archiving (standard transaction SARA, object name VEHICLE ). If required, you can display the archived vehicles again
(transaction VELOARDI).

 Note
You can delete the archiving indicator with transaction VELOARSL.

Only the VMS internal data , that is vehicle data including customer-speci c elds, additional quali ers, vehicle history, links to standard
documents, additional con gurations, links to dealers and end customers, and the con guration data is archived. The actual documents
that are linked to the vehicle are not archived.

You have two views at your disposal when you archive vehicles:

Technical view: list of tables/structures and elds

Vehicle view: “ at” (not hierarchical) display of vehicle data, con guration, history and additional data. This display is similar to the
display on the tab page Detail of transaction VELO. The only difference is that information is not made available via toggle bars – it is
listed and can be scrolled.

The following actions are executed in the background when you execute transaction VELOARSL.

ARCS Set archiving indicator

ARCD Delete archiving indicator

These actions are de ned as internal actions in the standard Customizing settings. You cannot, therefore, call them interactively
from transaction VELO. The actions are required in VMS so that they can be added to the action matrix of an action control and be
linked to a status. In this way, you can ensure that only vehicles with an appropriate status (for example, sold , delivered or paid ) are
agged for archiving and not any vehicles that are still required.
This is custom documentation. For more information, please visit the SAP Help Portal 74
 8/17/2021

 Caution
Archived vehicles cannot be reloaded.

Activities
1. Choose transaction VELOARSL to ag vehicles for archiving. Enter the desired selection criteria and choose Execute. A list appears that
displays all the vehicles that correspond to your selection criteria. Select the desired vehicles from this list and choose Execute again.
The archiving indicator is set for the vehicles you have selected.

 Note
The archiving indicator is not displayed with the vehicle details in transaction VELO. If you want to check which vehicles are to be
archived, you can set, in transaction VELOARSL, the indicator for deleting the archiving indicator and execute the report without
entering any further selection criteria. The results list then displays all the vehicles for which the archiving indicator is set.

2. Choose transaction SARA to archive the agged vehicles. Choose the object name VEHICLE in the initial screen.

3. Choose transaction VELOARDI to display the archived vehicles. Enter the desired selection criteria (vehicle numbers, vehicle model, plant)
and choose Execute.

A list appears that displays all the vehicles that correspond to your selection criteria. You can display the details for a vehicle by double-
clicking on it in this list. To do this, choose either the technical view or the vehicle view.

ILM-Based Information for the Archiving Objects

You can use the archiving object VEHICLE with the VEHICLE ILM object as part of SAP Information Lifecycle Management. In order to do so, you
must activate the associated business function Information Lifecycle Management (ILM) (transaction SFW5). The system then also displays the
ILM Actions frame. You can use these actions to archive documents with the retention periods de ned in the Information Retention Manager. You
can also make snapshots (copies) of data or delete data that ful lls the prerequisites.

For more information about the Relevance business functions for SAP ILM, see Activating SAP ILM.

For more information about ILM Enhancements in data archiving, see ILM-Speci c Enhancements to Archive Administration

The following elds for VEHICLE de ned in the ILM policy and are visible when processing ILM policies (transaction IRMPOL):

Available Time Bases

Last Changed On (LAST_CHANGE_DATE)

Available Condition Fields

Storage location (LGORT)

Plant (WERKS)

Available Policy Categories

RTP: Retention Rules

For more information, see SAP Information Lifecycle Management.

Technical Integration

Use
VMS is not only completely integrated with the standard components MM (Materials Management), SD (Sales and Distribution), CS (Customer
Service) and FI/CO (Financial Accounting and Controlling) , but also contains interfaces to external SAP components.

Features
You can connect the following SAP components to VMS:

SAP component Scope of Functions

This is custom documentation. For more information, please visit the SAP Help Portal 75
 8/17/2021

SAP Internet Pricing and Con gurator ( SAP IPC ) Con guration of vehicles in VMSYou can connect SAP IPC as an alternative to
the standard characteristic value assignment screen .

SAP Retrieval and Classi cation ( SAP TREX ) Quick search for vehicle con gurations and vehicle master data in VMS

SAP Business Information Warehouse ( SAP BW ) Evaluation of vehicle con gurations and vehicle master data

SAP Supply Chain Event Management ( SAP SCEM ) Tracking of VMS vehicles at any point along the supply chain

SAP Customer Relationship Management ( SAP CRM ) Processing of post-sales processes with vehicles that have been imported
from VMS in the Interaction Center for Automotive

Internet Accesses

Dealer Portal for VMS (vehicle sales) Web Dynpro-based VMS user interface for car dealers

There are different ways for users to log on to VMS. Users at a car dealership will normally use an Internet connection to access the SAP
Enterprise Portal, the SAP Business Client for HTML, or the SAP Business Client as a desktop-based integration platform.

Users at the importers can choose whether they want to log on via SAP GUI or use the Internet access in the same way as at the dealers.

 Note
All components are optional.

Connection to SAP IPC

Use
SAP Internet Pricing and Con gurator (SAP IPC) is used in numerous SAP applications to con gure products via the Internet. Technically speaking,
SAP IPC belongs to SAP Customer Relationship Management (SAP CRM), but it can also be installed separately on its own database
("standalone").

As of SAP CRM 5.0, SAP IPC 7.0 is a component of the Application Platform (AP). Compared to the previous release (SAP IPC 4.0), the technology
has been switched to SAP Virtual Machine Container (VMC), which is part of the SAP Web Application Server (SAP Web AS) and SAP NetWeaver
2004s. Installation of a separate database is not required since SAP IPC 7.0 has been moved to SAP Web AS. This was done in order to use VMC.

 Note
This is not a J2EE Server, which is also a part of the SAP Web AS.

 Note
The use of SAP IPC for vehicle con guration was mandatory up to SAP enhancement package 4 for SAP ERP 6.0. As of SAP enhancement
package 5 for SAP ERP 6.0, you can use SAP IPC as an alternative to the characteristic value assignment screen .

Based on your requirements, you must decide if you want to use SAP IPC or the characteristic value assignment screen for vehicle
con guration.The advantage of the characteristic value screen is that you do not have to install any additional software components and
connect them to the VMS.

Prerequisites
If you want to use SAP IPC 7.0, you must have made the following settings:

You have created an Extended Con guration Management (XCM) scenario in the relevant J2EE server and set up an RFC connection to the
J2EE server.

If you want to use SAP IPC 4.0 (IPC standalone scenario), you have installed it and implemented the BAdI VLC_IPC_SELECT.

 Note
For more information, see SAP Service Marketplace at service.sap.com/instguides SAP Business Suite Applications SAP CRM .

You can use the BAdI VLC_CALL_CONFIG to connect to another, external con gurator. For more information, see Customizing for the
Vehicle Management System (VMS) under Business Add-Ins (BAdIs) Vehicle Con gurations BAdI: Connection to External
Con gurator .

This is custom documentation. For more information, please visit the SAP Help Portal 76
 8/17/2021

You have connected VMS to SAP IPC if that is the con gurator you wish to use.

You have carried out an initial load for the IPC, which lls the relevant IPC database tables in the ERP system.To do this, the system reads
data from the tables of the LO-VC component and writes them to the IPC tables. For each vehicle model you want to con gure in the IPC,
the initial load and the delta load (see below) require a knowledge base object and a runtime version of the knowledge base object.

Features
The connection between VMS and the IPC database area remains intact even after the initial load. As soon as there are changes to the
con guration master data in VMS, the changed data is automatically replicated to the IPC database area (delta load).

You can change the parameters with which SAP IPC is called by using BAdI VLC_SCE_PARAMETERS.

SAP IPC is called for every con guration transaction in VMS, that is, every time you choose Con gure when you execute an action.

 Note
You can con gure the user parameter VELO_SCE_FULLSCREEN to de ne that SAP IPC is called in full-screen mode and not integrated
into the Action tab page.

Connection to SAP TREX or Another External Search Engine

Use
SAP Retrieval and Classi cation (SAP TREX) is a powerful SAP external search engine that is used in many SAP applications. Technically speaking,
SAP TREX belongs to SAP Enterprise Portal , but can also be installed as an individual component.

In addition to the normal database search, VMS provides a generic interface through which you can connect VMS to any external search engine
you choose. Based on this generic interface, VMS also provides an interface adapted to suit SAP’s search engine SAP TREX. The search via an
external search engine or SAP TREX substantially increases performance in the vehicle search , above all when the number of vehicles to be
searched is very large.

The framework provided by the Search Engine Service (SES), which is part of SAP NetWeaver 2004s, is used to connect to SAP TREX.

The SES central workbench is used to:

Manage and monitor the download of objects to SAP TREX

Manage indexes

Specify the RFC destination for SAP TREX server for a business object

Schedule and execute jobs for delta download of vehicles

If Customizing settings are made in SES for the object VMSVEHICLE, the vehicles are searched with SAP TREX using the SES. The transaction used
is SES_ADMIN.

If SES is not used, the connection takes place technically through the BAdIs VLC_EXTSE_SEARCH Vehicle Search Using External Search Engine and
VLC_SE_DELTA_LOAD Delta Load to External Search Engine. In the standard system, the BAdIs are empty and VMS is not connected to any
search. Both of the above-mentioned BAdIs have an example implementation with a commentary and example coding for an initial load report.

Prerequisites
The prerequisites mentioned here refer only to the connection of SAP TREX.

You have installed SAP TREX 6.0 or higher.

 Note
For more information, see SAP Service Marketplace at service.sap.com\instguides SAP NetWeaver SAP NetWeaver 7.0 (2004s
) Installation Installation Standalone Engines SAP NetWeaver Search and Classi cation TREX

You have connected VMS to SAP TREX.

This is custom documentation. For more information, please visit the SAP Help Portal 77
 8/17/2021
You have implemented BAdIs VLC_EXTSE_SEARCH and VLC_SE_DELTA_LOAD, and programmed and executed a report for the initial load if
SES is not used.

In Customizing for VMS under Vehicle Search De ne Fields for TREX Download , you have entered the vehicle data that you want to be
transferred. All the elds from the vehicle table VLCVEHICLE and customer-speci c data from APPEND structures are counted as potential
vehicle data. The con guration data is basically always transferred and does not have to be selected separately.

Features
You can connect VMS to the SAP search engine SAP TREX or also to any other external search engine you like.

You can download vehicle data, con guration data and also customer-speci c data to the search engine and thus make it available for the
fast search for vehicles. This means that you can freely de ne which search criteria you want to add to the fast search.

In the rst instance, the interface provides all the con guration data and vehicles data. You should restrict the maximum amount of data to
a reasonable amount in order to retain the performance advantage that the external search engine offers.

All the vehicles are downloaded to the search engine for the rst time in the initial load. All the changed data and all the vehicles created
after the initial load are transferred automatically and continually in the delta load. If SES is used change pointer is written to the database
and changes are picked up and transferred to SAP TREX through a background job. If SES is not used, you can use a BAdI to de ne,
according to your own requirements, which data is to be relevant to the search engine (see above).

If you have connected VMS to an external search engine, the system rst executes the search in this search engine. Then it transfers the hit
list to the normal database for further processing.

Using SES administration workbench you can create, activate or deactivate search index. If SES is not used, you can decide yourself which
vehicles or vehicle models you want to assign to which search index in the external search engine, and in this way you can nd your own
optimal solution for increasing performance.

All the vehicles that you want to include in the same search should be in the same search index. You can create several search indexes, for
example, a search index for each model family. However, a cross-model-family search would then no longer be possible.

 Caution
There are the following restrictions in the use of SAP TREX:

If you want to work with selection criteria with intervals, due to technical restrictions, the search is automatically transferred to the
normal database search and not to SAP TREX.

SAP TREX only supports a search with exact attributes and not fuzzy searches.

Connection to SAP BW

Use
SAP Business Information Warehouse (SAP BW) allows the evaluation of data from operative SAP applications, from any other business
applications, and from external data sources such as databases, online services, and Internet. You use queries to analyze the data. Queries target
speci c views on the data according to the individual issues in question. Every authorized person can use these queries to access both historical
and current data in any desired summarized or detailed form.

With the connection of VMS to SAP BW, you can apply the different business questions to your vehicle data .

Prerequisites
You have installed SAP BW 3.0 or higher.

 Note

For more information, see SAP Service Marketplace at service.sap.com\instguides SAP NetWeaver.

You have connected VMS to SAP BW.

If required, you have mapped the VMS con guration characteristics and BW characteristics in VMS as described below (transaction
VELOBWC Assign Class Characteristics to BW Characteristics ).

This is custom documentation. For more information, please visit the SAP Help Portal 78
 8/17/2021
Features
Several extractors are available in VMS. You can use these extractors independently of one another to extract the following data to the
appropriate DataSources and this makes it available to SAP BW for evaluation and analysis purposes:

The most important vehicle attributes : all vehicle numbers, vehicle model, supplier, customer, action control, primary and secondary
statuses, availability status, gross list price, planned production date, planned delivery date, and so on (extractor
VELO26_VLC_BW_GA)

The con guration characteristics of the vehicles, for example, color, engine, special features (extractor VELO26_VLC_BW_GC) and
the texts for the appropriate values (extractor VELO26_VLC_BW_GCT)

Vehicle document links, for example, links to purchasing or sales documents that have been assigned to a vehicle (extractor
0AU_VM_BW_GD)

Organizational data of a VMS user (extractor 0AU_VM_BW_GO): the corresponding DataSource extracts only the elds that are
necessary for checking the authorization of a user for displaying dealer manager queries

 Note
Extractors 0AU_VM_BW_GD and 0AU_VM_BW_GO are available for BI Content 3.52 and higher.

Queries can relate to vehicle data and con guration characteristics and can, for example, answer the following question: how many
90 horsepower vehicles of vehicle model SAPCar have I, as importer, sold to dealer Smith within a speci c period of time?

You can map the special VMS con guration characteristics to BW characteristics . A class with characteristics is assigned to each vehicle
model in VMS; each characteristic has a speci c number of possible characteristic values (see: Constructing a Vehicle Con guration ). So
that vehicles are comparable with regards to their characteristics, it makes sense to map these special vehicle-model-dependent
characteristics to general vehicle-model-independent characteristics. These BW characteristics then contain all possible characteristic
values.

 Example
The vehicle-model-dependent VMS characteristics for exterior colour_SAPCar and exterior colour_SAPRover can be mapped to the
vehicle-model-independent BW characteristic for exterior colour.

In this way, queries for BW characteristics are possible across all vehicle models, for example, a query for the question: how many red
vehicles (vehicles with the characteristic colour: red ) have I sold in the last two months?

A further advantage of mapping is that you can control which and how many characteristics should be relevant to BW. As a result, BW
reporting is more efficient.

In SAP BW, you can execute the queries delivered by SAP in the standard system or create your own queries . Possible questions in this
respect could be:

How many vehicles with which con guration characteristics have I sold to dealer Smith? Such a question provides valuable data for a
new sales forecast.

Which dealers have I sold the most vehicles to?

Of which vehicle model have I sold the most vehicles?

How popular is air-conditioning, seat heating, and so on?

Connection to SAP SCEM

Use

This functionality can only be used in pilot projects and after discussion with SAP.

SAP Supply Chain Event Management ( SCEM ) allows you to de ne speci c expected events for a business process (such as a transport) or for a
business object (sales order), and use rules to de ne which actions (a status change, for example) should be linked to which event. At the same
time you can de ne planned, baseline dates for the events. If the appropriate event is then con rmed with an actual time for this process or object,

This is custom documentation. For more information, please visit the SAP Help Portal 79
 8/17/2021
the status is changed, for example, and the planned scheduling for the following events is updated. In this way you can monitor each step of the
logistics chain, refer to critical situations with alerts and be proactive by sending the appropriate messages.

Technically speaking, SAP SCEM is part of SAP Supply Chain Management (SAP SCM) and cannot be installed separately.

For more information, see SAP Help Portal under

http://help.sap.com/saphelp_em70/helpdata/de/6e/b4393c95b04325e10000000a11405a/frameset.htmSAPEventManagement

You can constantly monitor and log actions that you execute in VMS with reference to speci c vehicles via the connection of VMS to SAP SCEM.
This means that you can always provide your dealers with the latest information on the progress being made in production and transport, track
down delays, and initiate appropriate measures in good time.

Prerequisites
You have installed SAP SCM 4.0 or higher.

For more information, see SAP Service Marketplace atservice.sap.com\instguides→ SAP Business Suite Applications → SAP SCM

You have connected VMS to SAP SCEM.

You have implemented BAdI VLC_USER_INTERFACE. This BAdI checks whether SAP SCEM has been connected to VMS and calls the tracking data
(see below).

You have activated the SCEM search views via BAdI VLC_SEARCH_PROFILE (see below).

For all SCEM-relevant actions, you have set the SCEM Rel. indicator in Customizing for VMS under Control Data → De ne Actions.

An event handler is then created in SAP SCEM for the vehicle for which you execute the action. If an event handler already exists for this vehicle,
the information parameters for this event handler are updated. An event handler is the SCEM version of the application object Vehicle in VMS,
which allows you to process con rmed events for this application object in SAP SCEM.

You have executed the action EMMI . This action reports events for SAP SCEM.

Features
Displaying SCEM Information

You call SCEM information for a vehicle in transaction VELO via the Detailtab page, and then function SCEM under Vehicle Data .A screen with
the following tab pages appears:

Tab Page Description

Expected Events List of de ned and expected events in SAP SCEM for the application object
Vehicle with target and, where appropriate, actual scheduling. The target
scheduling is based on the planned production date. Events that have already
been reported are shown by the symbol

Event Messages List of the events already reported for this vehicle.

Error Messages List of the error messages that have occurred in connection with the event
messages.

Status Display List of the possible statuses as de ned in SAP SCEM with the status values
based on the events that have been reported for this vehicle.

Finding SCEM Information

You have two additional search views at your disposal in the vehicle search when you are searching for SCEM information:

Search View Description

This is custom documentation. For more information, please visit the SAP Help Portal 80
 8/17/2021

Search View Description

Event Manager Search for vehicles with SCEM parameters such as application object type,
set of rules, status pro le, pro le of expected events, administrative data
and transport data.

Messages and Status Search for vehicles with a speci c SCEM status or with speci c event or error
messages.

Connection to SAP CRM

Use
SAP Customer Relationship Management (SAP CRM) supports all customer-related processes within the entire customer relationship cycle from
market segmentation, lead generation, and opportunities through to after-sales and customer service.

For more information, see SAP Help Portal under

http://help.sap.com/saphelp_crm70/helpdata/de/e1/8e51341a06084de10000009b38f83b/frameset.htmSAPCustomerRelationshipManagement

If you connect VMS to CRM, you can transfer the vehicles created in VMS with all the appropriate data (vehicle data, con guration, vehicle history,
relationships to dealers and end customers) via an interface to SAP CRM. There, they are mapped from SAP CRM to the individual object Vehicle
and are available for after-sales processes that are processed via the Interaction Center.

Transferring vehicles to SAP CRM and mapping vehicles to individual objects takes place using the actions CRMV Export Vehicle to CRM and CRMS
Add Vehicle to CRM Order . You must make additional settings for mapping data in BAdI VLC_CRM_INTEGRATOR.

Prerequisites
You have installed SAP CRM 4.0 or higher.

For more information, see SAP Service Marketplace atservice.sap.com\instguides→ SAP Business Suite Applications → SAP CRM

You have connected VMS to SAP CRM.

So that BAdI VLC_CRM_INTEGRATOR is called, you have set the CRM Rel. indicator for all CRM-relevant actions in Customizing for VMS under
Control Data → De ne Actions.

You have programmed BAdI VLC_CRM_INTEGRATOR.

You have transferred the VMS sales orders with vehicle reference to SAP CRM. You have transferred sales documents without a vehicle reference
and that have been created in SAP CRM to VMS and found suitable vehicles for these sales documents in VMS.

You have executed action CRMV Export Vehicle to CRM in VMS and thus transferred vehicle data, con guration data, and history entries such as
relationship with dealer and end customer to SAP CRM. You have executed action CRMS Add Vehicle to CRM Order in VMS and thus transferred
the assignment of vehicles to the sales documents to SAP CRM.

Features
The Interaction Center for Automotive is an enhancement of the SAP CRM Interaction Center with a workspace speci c to the automotive industry
in which the customer- and partner-oriented view is enhanced by a vehicle-oriented view; the latter is based on the data of the individual vehicle.
The vehicles can be either company cars or external vehicles and the appropriate data can be processed manually or be imported automatically
from VMS or from any other external system, for example from the production control system.

The Interaction Center has been designed for Interaction Center agents who work at the manufacturers or importers.It offers two interfaces (UIs):
the IC WinClient and the IC WebClient.

It supports the following processes:

This is custom documentation. For more information, please visit the SAP Help Portal 81
 8/17/2021
Information inquiry

Service and support

Complaints management

Sale of accessories

Marketing campaigns

For more information, see SAP Help Portal under

http://help.sap.com/saphelp_crm70/helpdata/de/42/dfae70af4b2cede10000000a1553f7/frameset.htmInteractionCenterforAutomotive .

Exchange of Vehicle-Related Data Between VMS and SAP CRM

Use
You use this function to transfer vehicle data from the Vehicle Management System (VMS) in SAP DIMP to SAP CRM. By doing this you can, for
example, reuse vehicles and attributes that you have created in the Vehicle Management System in the SAP CRM Interaction Center for the
automotive industry. This means that you have detailed information about customers and their vehicles at your ngertips in the Interaction Center.

Integration
You can use the CRM Middleware XIF adapter for the import and export of vehicles and other individual objects. The XIF adapter can be used in
combination with XML/SOAP and ALE/IDOC technology. This means that you can connect both to SAP ERP systems and external ERP systems. For
the Vehicle Management System in SAP DIMP, vehicles can also be transferred to the plug-in for CRM Middleware using the VMS adapter.

Prerequisites
You have made the following settings:

Customizing settings in tables CRMCONSUM and CRMRFCPAR

Settings for system connections

Settings for SAP CRM Middleware

Features
Importing Vehicle Data from SAP DIMP to SAP CRM

You can transfer the following Vehicle Management System data from SAP DIMP to SAP CRM, using either the VMS adapter or the XIF adapter:

Vehicle (for example, vehicle ID, vehicle short text, model, year of manufacture)

Vehicle con guration (for example, color, motor)

Reference model for the vehicle

Vehicle to business partner relationships (such as dealer or owner of vehicle)

Vehicle history

This is custom documentation. For more information, please visit the SAP Help Portal 82
 8/17/2021

Overview: Data Exchange Between SAP DIMP, External Systems and SAP CRM

Activities
Initial Data Transfer

Make the appropriate settings in SAP CRM Middleware.

Start the initial vehicle download in SAP CRM and transfer the following data to SAP CRM:

Vehicle with con guration

Vehicle history

Relationships between vehicle and dealers/end customers

Delta Data Transfer (with the Vehicle Management System)

Start the data transfer in the SAP DIMP Vehicle Management System .

SAP CRM adopts the following updated data:

New vehicles and their con guration

Additional history records for vehicles

Relationships between vehicle and dealers/end customers

Connection to SAP Web AS with DIWI

This is custom documentation. For more information, please visit the SAP Help Portal 83
 8/17/2021

 Caution
As of SAP enhancement package 4 for SAP ERP 6.0, we recommend no longer using the Discrete Industries Web Interface (DIWI) add-on,
which contains the version of the dealer portal that is based on the Business Server Pages. The functions are still available in the Web Dynpro-
based dealer portal.

For more information, see Automotive Dealer Portal .

Use
SAP Web Application Server (SAP Web AS) is the technological enhancement and further development of the hitherto SAP Basis System and
includes Internet capabilities as well as the SAP implementation model. With SAP Web AS, Internet applications can be programmed or installed
quickly and easily.

For more information, see SAP Help Portal under SAP Web Application Server.

Discrete Industries Web Interface (DIWI) supports sales and after-sales processes at the vehicle dealer, from the creation of the quotation to the
ordering of spare parts. It composes the three Internet interfaces for the DIMP applications VMS, Warranty Claim Processing and Spare Parts
Procurement; these are called via separate URLs. DIWI can run on SAP Web AS. The user only needs to ensure that an Internet browser has been
installed.

Prerequisites
You have installed SAP Web AS 6.20 or higher.

 Note
For more information, see SAP Service Marketplace at service.sap.com/instguides SAP NetWeaver SAP NetWeaver Components
(before SAP NetWeaver 2004) SAP Web Application Server .

You have installed DIWI 3.0.

Features
The VMS Internet interface in DIWI offers you the following functions:

Display of vehicles at importer.

Display of own dealer vehicles.

Creation of a virtual vehicle pool of vehicles from the manufacturer’s stock or also of own dealer stock.

Combined vehicle search according to status, models and con gurations.

Vehicle con guration with SAP Internet Pricing and Con gurator (SAP IPC).

Placing individual sales orders in the importer’s or the manufacturer’s system.

Transfer between dealers if the desired vehicle is to be found in another dealer’s stock and this dealer has de ned the vehicle as not
viewable for the other dealers.

Maintenance of end customer data and saving of desired con gurations for later purchase orders or for evaluating customers’ wishes.

Automotive Dealer Portal (IS-A-DP)

Use
This component enables employees from different areas of the automotive industry to work together and communicate using the Internet,
including:

Original equipment manufacturers

Importers

Car distributors

This is custom documentation. For more information, please visit the SAP Help Portal 84
 8/17/2021
Car dealers

You can use the dealer portal Web-based user interface to manage vehicle sales, spare parts procurement, and warranty claim processing. You use
roles to control which functions are available to the users of the dealer portal.

 Note
In the following documentation, the term importer can also mean employees from the following areas:

Distribution centers

Logistics centers

Original equipment manufacturers

Car distributors

Vehicle sales representatives, spare parts clerks, and warranty processing clerks are employees of dealers who belong to the organization of
the importer.

This documentation is intended for system administrators of the importer or consultants who con gure the system and therefore require basic
knowledge about the available functions.

 Note
It is assumed that the reader already has knowledge regarding vehicle sales, spare parts processing, and warranty claim processing in the back-
end system. For more information, see:

Vehicle Management System (IS-A-VMS) (Vehicle Sales)

Sales and Distribution (SD) (Spare Parts Procurement)

Warranty Claim Processing (LO-WTY)

Implementation Considerations
The Web-based user interface of the dealer portal is technically based on the SAP Business Client for HTML, the SAP Business Client as a desktop-
based integration platform, or on the SAP Enterprise Portal.

Integration
With Other SAP Components

Required Function in Dealer Portal Component Necessary

Vehicle Sales Vehicle Management System (IS-A-VMS)

Spare Parts Procurement Sales and Distribution (SD)

Warranty Claim Processing Warranty Claim Processing (LO-WTY)

Vehicle Sales

Use
Vehicle sales representatives can use the vehicle sales functions at the dealer's location to con gure vehicles, create orders for vehicles, and nd
available vehicles at the importer's location.

Dealers can transfer vehicles from one location to another. The dealer portal therefore uses real time data and search criteria to enable dealers to
search for a vehicle at the end customer's request. If there is not a suitable vehicle available, the vehicle sales representative can create an order
in the dealer portal for the desired vehicle, based on the current vehicle prices and con guration options. The importer uses the dealer portal to
report changes in production or vehicle deliveries to the dealer, so that the vehicle sales representative can immediately inform the end customer.

This is custom documentation. For more information, please visit the SAP Help Portal 85
 8/17/2021
Integration
If the dealer portal for vehicle sales and the Vehicle Management System (VMS) are installed on different systems, the dealer portal uses an RFC
connnection to communicate with the back-end system.

Prerequisites
For many Customizing settings, you can use Switch BC sets that contain the system settings required for vehicle sales in the dealer portal. You can
tailor these settings to meet your requirements in Customizing under Logistics Execution Vehicle Management System (VMS) Dealer Portal .

In addition to the automatic settings of the BC sets, you have made the following settings:

In Customizing for the Dealer Portal:

If the dealer portal and the back-end system are installed on different systems, you must de ne an RFC destination in the Customizing
activity De ne Back-End RFC Destination, so that the dealer portal can communicate with the back-end system of the Vehicle
Management System.

In Customizing for the Vehicle Management System (VMS):

You have de ned the organizational roles in the Customizing activity De ne VMS Roles, since users can only work with the dealer portal if
they are assigned to an organizational role.

You have de ned comprehensive organizational roles in the Customizing activity De ne Comprehensive Organizational Roles. You have
assigned organizational roles to these comprehensive organizational roles so that dealer portal users can work with several organizational
roles.

SAP Business Client for HTML

You have assigned the SAP_COCKPIT_DPVMS role to authorized users (such as vehicle sales representatives) in the back-end system (transaction
PFCG). This role contains a user menu for vehicle sales that is available in the dealer portal to users who have been assigned to this role.

Vehicle Sales: Work Overview

Use
You can use this function to make queries regarding the vehicle stock, the vehicle transfer, and vehicle deliveries and display this speci c
information. The following queries are available in the standard system:

Display reserved vehicles from stock

Display vehicles from stock that are assigned to an end customer

Display inbound and outbound transfer requests for a vehicle

Display delivered vehicles and vehicles yet to be delivered

You can also implement your own queries.

Prerequisites
In the Customizing activity Determine Work Overview under Logistics Execution Vehicle Management System (VMS) Dealer Portal , you have
de ned which queries should be available for which organizational roles in the dealer portal.

Features
After you have executed a query, the system displays the desired information in a table. You can call detailed information for each transaction type
(vehicle or sales document), which the system then displays in a separate browser window.

For more information, see Displaying Detailed Information.

In addition, you can execute user actions for each operation type (vehicle, sales document, vehicle and sales document).

For more information, see User Actions.

This is custom documentation. For more information, please visit the SAP Help Portal 86
 8/17/2021

Vehicle Search

Use
You can use this function to search for vehicles in vehicle stock that ful ll speci c criteria:

You can search for one or more vehicles according to speci c search criteria, such as model, vehicle status, availability, and location.

If you have con gured a vehicle using the New Con guration function, you can copy this con guration, possibly change it, and then use it for
the vehicle search.

The system determines con guration data based on a validity date. For example, a new color for a vehicle model is only available for the
con guration starting on a speci c date.

If the con guration contains multi-value characteristics, you can decide which search mode you want the system to use (search with OR,
search with AND, exact search). The system ags multi-value characteristics with an asterisk *. You can con gure default values for the
search mode by using the Personalization function.

If you nd a vehicle with the con guration you want, you can reserve it for the end customer, directly create a sales order for the end customer, or
carry out otheruser actions in a separate browser window.

You can also display detailed information for each vehicle and SD document in a separate browser window.

Prerequisites
To determine con guration data based on a validity date, you have installed the Engineering Change Management (LO-ECH) component and have
made the appropriate Customizing settings under Logistics General Engineering Change Management .

To add elds to the vehicle search, you can implement the DPVMS_BADI_VEHICLE_SEARCH BAdI. Make this Customizing setting under Logistics
Execution Vehicle Management System (VMS) Dealer Portal Business Add-Ins (BAdIs) BAdI: Enhancement of Vehicle Search Screen .

Document Search

Use
You can use this function to search for documents that ful ll speci c criteria:

You can search for one or more SD documents according to speci c search criteria (such as end customer, sales area, and purchase order
number).

You can search for SD documents for a speci c vehicle model.

If the search is successful, the system displays the SD documents that match your search criteria in a table. You can then carry out user actions in
a separate browser window for these SD documents, such as changing, deleting, or cancelling an order. You can also display detailed information
for each SD document and vehicle in a separate browser window.

Prerequisites
To add elds to the document search, you can implement the DPVMS_BADI_SDDOC_SEARCH BAdI. Make this Customizing setting under Logistics
Execution Vehicle Management System (VMS) Dealer Portal Business Add-Ins (BAdIs) BAdI: Enhancement of Sales Document Search Screen .

End Customer Search

Use
This function enables you to search for end customer data using speci c search criteria (such as customer name and address data).

If the search is successful, the system displays the end customers that match your search criteria in a table. You can change or delete these end
customers, for example. You can also create new end customers.

In addition, you can display detailed information for each end customer in a separate browser window.

This is custom documentation. For more information, please visit the SAP Help Portal 87
 8/17/2021
Prerequisites
To add elds to the end customer search, you can implement the DPVMS_BADI_BS_ADJUSTMENTS BAdI. Make this Customizing setting under
Logistics Execution Vehicle Management System (VMS) Dealer Portal Business Add-Ins (BAdIs) BAdI: BAdI: Enhancement of Business Partner
Screens .

Displaying Detailed Information

Use
You can use this function to display detailed information about vehicles, documents, and end customers.

After you have executed a query or have searched for vehicles, documents, or end customers, the system displays the desired information in a
table. You can call detailed information for each operation type (vehicle or sales document) or for each end customer. The system then displays
this information in a separate browser window.

You can also display the item details of sales documents as a print preview.

Examples of vehicle details:

Overview tab page:

Vehicle Identi cation Number (VIN)

Partner data (customer/dealer, end customer)

Dates (planned delivery date, production date)

Vehicle status

Con guration tab page:

Con guration data (such as model, color)

History tab page:

Vehicle history

Attachments tab page:

Attachments for the vehicle (such as model descriptions)

Examples of item details of a sales document:

Overview tab page:

Sales document number

Partner data (such as goods recipient, bill-to party, end customer)

Dates

Con guration tab page:

Con guration data (such as model, color)

Header Preis and Item Price tab pages:

Vehicle prices

Examples of end customer details:

Overview tab page:

Address data

Vehicles tab page:

Sales orders or reserved vehicles already created for this end customer (sorted by vehicles)

Documents tab page:

This is custom documentation. For more information, please visit the SAP Help Portal 88
 8/17/2021
Sales orders already created for this end customer (sorted by sales documents)

Prerequisites
To be able to display item details for sales documents in a print preview, you have already assigned form type PDF for output types AF00 (Inquiry)
and BA00 (Order Con rmation). Make this Customizing setting under Sales and Distribution Basic Functions Output Control Output
Determination Output Determination Using the Condition Technique Maintain Output Determination for Sales Documents Maintain Output
Types Processing routines .

User Actions

Use
This function enables you to carry out actions that refer to an operation type (vehicle, sales document, vehicle and sales document), such as:

Create, change, cancel sales orders

Create, change, cancel vehicles and sales orders

Reserve vehicles, cancel reservations

Accept, con rm, execute, reject vehicle transfers

Create, change, delete inquiries

Prerequisites
In the Customizing activity De ne Action Controls and De ne Action Matrices under Logistics Execution Vehicle Management System
(VMS) Control Data , you have de ned action controls for vehicles and then created an action matrix for each action control. For more information
about action control in the VMS back-end system, see Action Control.

In addition, Switch BC Sets contain standard settings as to which user actions you can execute with reference to a operation type (vehicle, sales
document, vehicle and sales document). You can tailor these settings to meet your requirements in Customizing under Logistics Execution Vehicle
Management System (VMS) Dealer Portal .

Determine Operation Types

De ne Operation Types

De ne User Actions

De ne Contexts for User Actions

De ne Process Control

De ne Validity Checks for User Actions

De ne Functions

De ne Screen Navigation

You can also use transaction LPD_CUST to tailor the LaunchPad (role: DPVMS, instance: DPVMS_SALES_REP), which is contained in a Switch BC
Set, to meet your requirements.

New Con guration

Use
You can use this function to create documents in the dealer portal.

 Note
With this function, you can only create vehicles with documents. You can create vehicles without documents in the back-end system of the
Vehicle Management System (VMS).

This is custom documentation. For more information, please visit the SAP Help Portal 89
 8/17/2021
A table or tree structure with available vehicle models serves as the initial point of access for creating documents. You can select a speci c vehicle
model from this table that you want to con gure. You make the con guration on the characteristic value assignment screen or in the Internet and
Pricing Con gurator (IPC).

If you decide you want the con guration, the following functions are available:

Create inquiry

You can save a vehicle con guration for an end customer as a request, without creating a vehicle.

Create sales order

Create sales order with vehicle

Execute price simulation (gross list price)

Search for vehicles in vehicle stock that match the con guration

Prerequisites
Characteristic Value Assignment Screen and IPC

In the standard system, the characteristic value assignment screen is available for the vehicle con guration. No additional settings are required for
using the characteristic value assignment screen.

To be able to use the IPC for vehicle con guration, you must ful ll the prerequisites described in Connection to SAP IPC.

If you already use the IPC for vehicle con guration and want to use the characteristic value assignment screen instead, go to Customizing for
Logistics General Product Lifecycle Management (PLM) Variant Con guration and choose activity Maintain Reference to Con guration User
Interfaces. Check the Application using IPC UI eld with the entry Vehicle Manager and make sure that there are no entries in the Sub Application
and XCM Scenario elds.

If the dealer portal and the back-end are installed on different systems and you want to use the characteristic value assignment screen, you must
have de ned an RFC destination in the Customizing activity De ne RFC Destinations under Cross-Application Components Processes and Tools
for Enterprise Applications Settings for BO Framework and Navigation BO Framework .

Vehicle Models in a Table or Tree Structure

If you implement the GET_ROOT_CLASS method of the VLC_PRESELECTION BAdI, you can decide in Vehicle Sales: Personalization if you want the
system to display the available vehicle models in a list or in a tree structure. Make this Customizing setting under Logistics Execution Vehicle
Management System (VMS) Business Add-Ins (BAdIs) Vehicle Search BAdI: Preselection of Vehicle Models .

Creating End Customers

Use
You can use this function to create end customer data. Once you have created an end customer, you can create a con guration for a vehicle model
and then a sales order, for example.

Prerequisites
When you create an end customer, the end customer's address has a country-speci c format. You can select the address format relevant for you
by using the Personalization function.

In Customizing for the Dealer Portal under Assign WD Components to Country-Speci c End Customer Address Formats, you can de ne which
country-speci c address formats should be available and which address format should be the default value.

Vehicle Sales: Personalization

Use
You can use this function to customize how vehicle sales is displayed in the dealer portal according to your user-speci c requirements:

This is custom documentation. For more information, please visit the SAP Help Portal 90
 8/17/2021
By selecting the organizational role, you can decide which dealer you are working for. You can also decide to display or hide the
organizational role in the corresponding browser windows. If you are only working for one dealer, it is advisable to hide the organizational
role so that it does not take up space in the browser windows.

You can de ne which country-speci c format you want to use when creating end customer data and which search method you want to use
for multi-value characteristics.

You can decide if you want the system to display the available vehicle models in a list or in a tree structure.

Prerequisites
To be able to choose from different organizational roles, you must have already de ned several organizational roles in the Customizing activity
De ne VMS Roles under Logistics Execution Vehicle Management System (VMS) Vehicle Management System (VMS) .

Since address formats are different for each country, you can de ne in the Customizing activity Assign Web Dynpro Components to Country-
Speci c Address Formats under Logistics Execution Dealer Portal which Web Dynpro component you want the system to use for displaying end
customer addresses.

If you implement the GET_ROOT_CLASS method of the VLC_PRESELECTION BAdI, you can decide if you want the system to display the available
vehicle models in a list or in a tree structure. Make this Customizing setting under Logistics Execution Vehicle Management System
(VMS) Business Add-Ins (BAdIs) Vehicle Search BAdI: Preselection of Vehicle Models .

Transaction Codes for VMS

Customizing for VMS

Transaction Code Description

Number Ranges

OVELO2 De ne number ranges for internal vehicle number

OVELO3 De ne number ranges for action control determination

OVELO8 De ne number ranges for determination of con guration change pro le

Other

OVELO19 De ne VMS roles

OVELO7 Assign own dialog messages

Vehicle Search

OVELO27 De ne sharing levels

OVELO18 De ne vehicle search areas

OVELOVSRINIT Initialize category maintenance

OVELO20 De ne vehicle categories

OVELO21 Assign roles and vehicle categories

OVELOTREX De ne elds for TREX download

OVELO29 De ne search views

SES_ADMIN Search Engine Service: Administration

Control Data

OVELO1 De ne actions

OVELO12 De ne vehicle status

OVELO5 De ne external status

OVELO13 Determine availability

OVELOL De ne vehicle locations

This is custom documentation. For more information, please visit the SAP Help Portal 91
 8/17/2021

Transaction Code Description

OVELO14 De ne vehicle usage

OVELO11 De ne action controls and actions matrices

OVELO00 De ne global VMS parameters

OVELO30 De ne calculation sheet pro le

Message Determination

OVELOM04 De ne eld catalog for messages

OVELOM01 Maintain condition tables

OVELOM11 De ne access sequences

OVELOM21 De ne message types

OVELOM31 De ne message determination schema/procedure

OVELOM41 Assign message determination schema/procedure to plant

Enhancements

OVELO6 Enter technical data for actions

OVELO4 De ne additional data for vehicle

Master Data

Transaction Code Description

Material Master Record

MM01, MM02 Create and change material master records for vehicle models

Classi cation System, Variant Con guration

CT04 Create and change vehicle characteristics with characteristic values

CL04 Create, change classes

CU50 and CL30N Group characteristics on interface

CU41, CU42 Create, change con guration pro les

CU01, CU02 Create, change relationship and object dependencies

Pricing

VK11, VK12 Create and change variant conditions in SD

MEK1, MEK2 Create and change variant conditions in MM

Business Partner

XK01, XK02 Create, change vendor (creditor) centrally

XD01, XD02 Create, change customer (debtor) centrally

Vehicle Management System (VMS)

To nd the VMS transactions, choose Logistics Logistics Execution Vehicle Management System from the SAP Easy Access screen.

Transaction Code Description

VELO Vehicle Manager

VELOM Status monitor for the vehicle IDoc

VELOMCS Assign models to calculation sheet pro le

This is custom documentation. For more information, please visit the SAP Help Portal 92
 8/17/2021

Transaction Code Description

VELOUM De ne used-vehicle models

VELOMNR Models with user-de ned number ranges

VELONR De ne number ranges for vehicle models

VELOCM Con guration mapping

VELOMMAP Assign vehicles to characteristics of used-vehicle con guration

Basic Data

VELORM Assign vehicle models to VMS role

VELORO Assign organizational data to VMS role

VELORU Assign VMS roles to user

VELOS De ne action control determination

VELOC De ne sales campaigns

VELOP De ne con guration change pro les

VELOPR Analyze con guration change pro les

VELOOBJC Add object characteristics to a con guration

VELOK De ne message condition records

VELOBWC Assign class characteristics to BW characteristics

Reports for Administrators

VELOV De ne variants for actions in batch

VELOB Perform actions in a batch

VELOAS Assign vehicles to sales documents in batch

VELOR Update reservation queue

VELOE Correct incorrect vehicle statuses

VELOP01 Log: status monitor for vehicle IDoc (not in menu)

VELOP02 Log: update reservation queue (not in menu)

VELOP03 Log: action execution in Vehicle Manager (not in menu)

SLG2 Application log: delete expired logs (not in menu)

VELOARSL Set/delete archiving indicator

VELOARDI Display archived vehicles

Business Add-Ins (BAdIs) for VMS

For all Business Add-Ins (BadIs) that are relevant for VMS, see Customizing for Vehicle Management System (VMS) under Business Add-Ins
(BADIs) .

This is custom documentation. For more information, please visit the SAP Help Portal 93