VMS.pdf

Vehicle Management Management System S ystem (IS-A-VMS) (IS -A-VMS) PDF download from SAP Help Portal: http://he htt p://help.sap.com/saphe lp.sap.com/saphelp_dbm70 lp_dbm70 0/helpdata 0/helpdata/en/8d/88c /en/8d/88c 43ace7a3 43ace7a3b46e10000000 b46e10000000 a11 a114084/frameset.h 4084/frameset.htm tm

Created on May 25, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

PUBLIC © 201 2 014 4 SAP SE or an SAP aff affili ili ate co com m pa pany. ny. All Al l rights ri ghts reserved. reserved.

Page 1 of 65

Table Tab le of content cont ent 1 Vehicle Management System (IS-A-VMS) (IS-A-VMS) 1.1 1.1 Vehicle Procurement and Sales 1.2 Vehicle 1.3 1.3 Master Data 1.3.1 1.3.1 Vehicle Model 1.3.1. 1.3.1.1 Creating a Vehicle Model 1.3.1. 1.3.1.1.1 1.1 Special Specia l VMS Master Data in Customizing for Sales and Distributio 1.3.1.2 1.3.1.2 Constructing Constr ucting a Vehicle Vehic le Configuration Configurat ion 1.3.1. 1.3.1.2.1 2.1 Creating a Variant Condition for Pricing 1.3.1. 1.3.1.2.2 2.2 Adding an Object Characteristic Characte ristic to a Configuration 1.3.2 1.3.2 Vendor and Customer 1.3.3 1.3.3 End Customer 1.3.4 Role 1.3.4.1 1.3.4.1 Creating a Configuration Configuration Change Change Profile 1.3.4.2 1.3.4.2 Calculation of Gross List Price Using Organizational Roles 1.3.5 1.3.5 Action Control 1.3.5.1 1.3.5.1 Example for Action Control 1.3.5.2 1.3.5.2 Determination of Action Control Control 1.3.6 Vehicle Vehicl e IDoc 1.3.6.1 1.3.6.1 Calling the the Status Monitor for the Vehicle IDoc 1.4 1.4 Vehicle Manager 1.4.1 1.4.1 Vehicle Search 1.4.1.1 1.4.1.1 Searching Sear ching for a Vehicle Vehicl e 1.4.1.2 1.4.1.2 Working Wor king with a Search Sear ch Profile Profi le 1.4.1. 1.4.1.3 Category Management 1.4.1. 1.4.1.4 Vehicle Search Area and Sharing Sharing Level Level 1.4.2 1.4.2 Vehicle Overview Overv iew 1.4.3 1.4.3 Vehicle Details 1.4.4 Action 1.4.4.1 1.4.4.1 Execution of Actions 1.4.4.2 1.4.4.2 Performing an Action Action In Batch Mode 1.4.4.3 1.4.4.3 Programming Your Your Own Actions 1.4.4.3.1 Programming Progra mming Actions Acti ons in VMS 1.4.4.3. 1.4.4.3.2 2 Aktionen programmieren programmie ren im VMS 1.4.4.4 1.4.4.4 Make-to-Stock Scenario 1.4.4.5 1.4.4.5 Make-to-Order Scenario 1.4.4.6 1.4.4.6 Configuration Management 1.4.4.6.1 Configuration Configura tion Management Manageme nt in MTS and MTO 1.4.4.6. 1.4.4.6.2 2 Actions and Configurations Configurations 1.4.4.7 1.4.4.7 Details for Actions 1.4.4.7.1 Creat Cr eating ing Vehicles Vehicl es 1.4.4.7. 1.4.4.7.2 2 Procurement: Procureme nt: Purchase Order 1.4.4.7.3 Procureme Proc urement: nt: Incoming Invoice 1.4.4.7. 1.4.4.7.4 4 Sales: Reservation, Quotation, Reservation Reserv ation Request, Inquiry Inquiry 1.4.4.7. 1.4.4.7.5 5 Sales: VMS Actions in Sales Order 1.4.4.7. 1.4.4.7.6 6 Sales: Assignment of Vehicles to Sales Sales Documents 1.4.4.7.7 Sales: Sale s: Outgoing Invoice 1.4.4.7.8 Shipping: Shipp ing: Delivery Deliv ery 1.4.4.7. 1.4.4.7.9 9 Goods Movements: Moveme nts: Goods Issue, Goods Receipt 1.4.4.7. 1.4.4.7.10 10 Rework (With Goods Movements) Moveme nts) 1.4.4.7.11 1.4.4.7.11 Process Proc essing ing Returns 1.4.4.7. 1.4.4.7.12 12 Used-Vehicle Scenario 1.4.4.7. 1.4.4.7.13 13 Service Processing Proces sing 1.4.4.7. 1.4.4.7.14 14 Warranty Claim Processing Proces sing 1.4.4.7. 1.4.4.7.15 15 Special Specia l VMS Actions 1.4.5 1.4.5 Assignment of Vehicles to Sales Documents 1.4.5.1 1.4.5.1 Assigning a Vehicle to a Sales Sales Document 1.4.6 1.4.6 Warranty Claim Display 1.5 1.5 Archiving Vehicles 1.6 1.6 Technical Integration Integration


Page 2 of 65

Table Tab le of content cont ent 1 Vehicle Management System (IS-A-VMS) (IS-A-VMS) 1.1 1.1 Vehicle Procurement and Sales 1.2 Vehicle 1.3 1.3 Master Data 1.3.1 1.3.1 Vehicle Model 1.3.1. 1.3.1.1 Creating a Vehicle Model 1.3.1. 1.3.1.1.1 1.1 Special Specia l VMS Master Data in Customizing for Sales and Distributio 1.3.1.2 1.3.1.2 Constructing Constr ucting a Vehicle Vehic le Configuration Configurat ion 1.3.1. 1.3.1.2.1 2.1 Creating a Variant Condition for Pricing 1.3.1. 1.3.1.2.2 2.2 Adding an Object Characteristic Characte ristic to a Configuration 1.3.2 1.3.2 Vendor and Customer 1.3.3 1.3.3 End Customer 1.3.4 Role 1.3.4.1 1.3.4.1 Creating a Configuration Configuration Change Change Profile 1.3.4.2 1.3.4.2 Calculation of Gross List Price Using Organizational Roles 1.3.5 1.3.5 Action Control 1.3.5.1 1.3.5.1 Example for Action Control 1.3.5.2 1.3.5.2 Determination of Action Control Control 1.3.6 Vehicle Vehicl e IDoc 1.3.6.1 1.3.6.1 Calling the the Status Monitor for the Vehicle IDoc 1.4 1.4 Vehicle Manager 1.4.1 1.4.1 Vehicle Search 1.4.1.1 1.4.1.1 Searching Sear ching for a Vehicle Vehicl e 1.4.1.2 1.4.1.2 Working Wor king with a Search Sear ch Profile Profi le 1.4.1. 1.4.1.3 Category Management 1.4.1. 1.4.1.4 Vehicle Search Area and Sharing Sharing Level Level 1.4.2 1.4.2 Vehicle Overview Overv iew 1.4.3 1.4.3 Vehicle Details 1.4.4 Action 1.4.4.1 1.4.4.1 Execution of Actions 1.4.4.2 1.4.4.2 Performing an Action Action In Batch Mode 1.4.4.3 1.4.4.3 Programming Your Your Own Actions 1.4.4.3.1 Programming Progra mming Actions Acti ons in VMS 1.4.4.3. 1.4.4.3.2 2 Aktionen programmieren programmie ren im VMS 1.4.4.4 1.4.4.4 Make-to-Stock Scenario 1.4.4.5 1.4.4.5 Make-to-Order Scenario 1.4.4.6 1.4.4.6 Configuration Management 1.4.4.6.1 Configuration Configura tion Management Manageme nt in MTS and MTO 1.4.4.6. 1.4.4.6.2 2 Actions and Configurations Configurations 1.4.4.7 1.4.4.7 Details for Actions 1.4.4.7.1 Creat Cr eating ing Vehicles Vehicl es 1.4.4.7. 1.4.4.7.2 2 Procurement: Procureme nt: Purchase Order 1.4.4.7.3 Procureme Proc urement: nt: Incoming Invoice 1.4.4.7. 1.4.4.7.4 4 Sales: Reservation, Quotation, Reservation Reserv ation Request, Inquiry Inquiry 1.4.4.7. 1.4.4.7.5 5 Sales: VMS Actions in Sales Order 1.4.4.7. 1.4.4.7.6 6 Sales: Assignment of Vehicles to Sales Sales Documents 1.4.4.7.7 Sales: Sale s: Outgoing Invoice 1.4.4.7.8 Shipping: Shipp ing: Delivery Deliv ery 1.4.4.7. 1.4.4.7.9 9 Goods Movements: Moveme nts: Goods Issue, Goods Receipt 1.4.4.7. 1.4.4.7.10 10 Rework (With Goods Movements) Moveme nts) 1.4.4.7.11 1.4.4.7.11 Process Proc essing ing Returns 1.4.4.7. 1.4.4.7.12 12 Used-Vehicle Scenario 1.4.4.7. 1.4.4.7.13 13 Service Processing Proces sing 1.4.4.7. 1.4.4.7.14 14 Warranty Claim Processing Proces sing 1.4.4.7. 1.4.4.7.15 15 Special Specia l VMS Actions 1.4.5 1.4.5 Assignment of Vehicles to Sales Documents 1.4.5.1 1.4.5.1 Assigning a Vehicle to a Sales Sales Document 1.4.6 1.4.6 Warranty Claim Display 1.5 1.5 Archiving Vehicles 1.6 1.6 Technical Integration Integration


Page 2 of 65

1.6.1 Connection Connec tion to SAP IPC 1.6.2 1.6.2 Connection to SAP TREX TREX or Another Another External Search Sear ch Engine Engine 1.6.3 1.6.3 Connection to SAP SAP BW BW 1.6.4 Connection Connect ion to SAP SCEM 1.6.5 1.6.5 Connection to to SAP CRM 1.6.6 1.6.6 Exchange of Vehicle-Related Data Between VMS and SAP CRM CRM 1.6.7 1.6.7 Connection to SAP SAP Web AS with DIWI 1.6.8 1.6.8 Connection to SAP E EP P with BP for Automotive Channel Management 1.7 1.7 Transaction Codes Codes for VMS 1.8 1.8 Business Add-Ins Add-Ins (BAdIs) (BAdIs) for VMS


Page 3 of 65

Vehicle Management System (IS-A-VMS) Purpose The Vehicl e Management System (VMS) is an app lication for the Automotive industry. It sup ports, 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 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 flexibly 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 configuration, searching, purchasing and tracking of vehicles for your end customers. The dealers can log in to your system remotely via 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 simplified 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.

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 compl etely integrated into the SAP appl ication components MM, SD, CS and FI/CO . · SAP Internet Pricing and Configurator (SAP IPC) is used for vehicle configuration in VMS. · You can implement VMS together with SAP Advanced Planning and Optimization (SAP APO) as the planning system and withSAP 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. · There are two Internet acces ses for dealer access (SAP EP, SAP Web AS). · Furthermore, there are two interfaces to further external SAP app lications (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.

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

PUBLIC © 2014 SAP SE or an SAP affili ate company. All rights reserved.

Page 4 of 65

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 defined in SAP variant configuration. For more, general information on standard variant configuration functions, see: Variant Configuration. · 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, configuration, vehicle status, posting documents or end customer/consumer . The basis for the search is always a sp ecific vehicle model or a selection of models. These models must have been created as configurable materials in the SAP system (see also: Constructing a Vehicle Configuration). A filter ensures that dealers that log in to your system only see those vehicles which you have assigned to them or released for their viewing. · Executing 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 b ased 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 alsoSpecial 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 programme your own actions. The action concept is on a modular basis and flexible so that you can adjust it at any time to suit changes in your business processes. There is a one scr een transaction (based on the vehicle as object) with an integrated interface for vehicle master data, vehicle searches and actions (see: Transaction Codes for VM S). To access this transaction, choose Logistics ® Logistics Execution ® Vehicle Management System ® Vehicle Manager or transaction VELO from the SAP Easy Access screen .

1.1 Vehicle Procurement and Sales Purpose 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 , m ake-to-order p roduction) · 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 b een installed in your system; your dealers have acc ess to this sys tem via Internet. Your system is link ed to the manufacturer (OEM) sys tems via interfaces. · You have created the master data required for VMS.

Process Flow 1. The end customer would like to purc hase a vehicle with spec ific features and approaches one of your dealers. 2. The dealer searches y our stock using the Internet to see if an appropriate vehic le exists. 3. If yes, the dealer enters additional characteristics for the vehicle, whic h are then installed later in the course of local rework activities (for example, i nstalling a radio, dog grate, telephone, different tyres etc.). He/she then determines the price for the desired configuration 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 y ou and the dealer up-to-date information on the status of the vehicle, in other words, i nformation 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 sup ports vehicle procurement and sales, includi ng all the postings involved and oversees the entire business p rocess 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.


Page 5 of 65

1.2 Vehicle Definition 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 configuration is always created for a vehicle; the characteristics in the configuration 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 define 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 val uated stock using transaction MMBE Stock O verview .

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

Create a purc hasing info. record manually for each vendor. Leave the field Valuation type under Purchas ing organization 1 empty . Do not use the Customizing setting (Customizing for Materials Management ) under Purchasing ® Environment Data ® Define Default Values for Buyers , indicator InfoUpdate – Purchase order ), which defines that a purc hasing info. record is created automatically when a purchase order is created. The field Valuation Type is filled when this Customizing setting has been made. This leads to problem s when you want to create vehicl es. You can find 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 Identifier. A 22-character technical key assigned by the system when the im porter creates the vehicle. This key i s un ique 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 identification number from an internal number range. It is assigned by the system when th e im porter creates the vehicle. The vehicle number is created independently of the vehicle identification number (VIN).

External vehicle number

Identification number assigned by the manufacturer (for example, production number, vehicle number)

Vehicle identification number (VIN)

17-character number that identifies 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.


Page 6 of 65

Batch (only for vehi cles that can be assigned values)

A vehicle represents exactly one vehicle nu mber (see above).

Valuation type (onl y for vehicles that can be assigned values)

Each vehicle has a valuation type ( Valuation for a Singl e 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 finished vehicle in the importer’s plant

Vehicle Model

Basic type of a vehicle that can be varied. Vehicle models are created as configurable materials in the SAP system. A vehicle model can be a general vehicle type or a vehicle type for which specific characteristic valu es have been predefined usin g object dependencies.

Configuration

Characteristics and assigned characteristic val ues (for example: color: blue; special features: radio, air conditionin g).

Primary Action Control, primary status + date + time, secondary action control, secondary status + date + time

The action control defines (i n an action m atrix) whi ch actions can follow on e another when dealing with vehicles and which vehicle status change is connected with this. Example: a vehicle that the i mporter has ordered from the m anufacturer receives the

batch. The batch number is the same as the internal

status Ordered . After the manufacturer has confirm ed the purchase order, in other words has performed the action Confirm purchase order , the status changes automatically to Pur chase order confirmed . You can distin guish between primary and secondary action controls, depending on th e process that is being r epresents by the action control. The prim ary action control u sually represents the procurem ent process (ordering the vehi cle from the m anufacturer) and the secondary action control the sales process (sale of the vehi cle to the dealer). However, a subdivision into a logistics and a financial 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 confirmed and Transit confirm ed 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 defined in Customizing for VMS.

Production date (time stamp)

Date on which the vehicle is produced. The im porter enters the planned production date that he has agreed on wi th the manu facturer in the appropriate field when the vehicle is created or the vehicle data is changed. The m anufacturer updates this date regularly durin g the production process usin g 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 configuration. This price is in dependent of busin ess partner-specific discounts. The gross list pri ce changes if the vehi cle configuration is changed later. You must create an organizational role with the key GROS (see: Calculating the Gross List Price Using Organizational Roles) if you want th e system to be able to calculate the gross list pri ce.

Vehicle usage

Planned usage for the vehicle, for example, use as end customer vehicle, in fleet sales, as demonstration car and so on. This data can be used to help you prioriti ze cars when processing purchase orders and can be transferred to the manufacturer.

Sales campaign

Campaign for a specific length of time for the sale of a specific vehicle model or configuration at a reduced price. You can assign a sal es campaign to a vehicle u sing th e action CAMP. Examples: sale of old models for which the new model is already on the market, sale of old stock with unusual configurations etc. You can trigger special pricing functions i n the sales documents of vehicles that belong to a sales campaign. There are two options:

● You can add the field as an object charac teristic to the vehicle c onfiguration (see: Adding Object Characteristic to Configuration) ● You can use the options for flexib le enhancements to SD pri cing Visibility

Indicator in the vehicle table that can be used to influence whether a vehicle can be seen by dealers during the vehi cle search or n ot. This i ndicator 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 visibi lity 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


Page 7 of 65

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 visib ility acc ording 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 filtered 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 fleet 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 su spense account in th e customer master record.

End customer

End customer for the vehicle. The data for the end customer are stored in th e functions for busin ess partner management. You can assign an end customer by using action BUPA or by using the function End Customer , whi ch 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 hi m 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. When a used vehicle i s being exchanged for cash, the vendor can also be, for example, a rent-a car company or any other person. Such a busi ness partner m ay 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 whi ch vehicles are made available and searched for. This area defines 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 veh icle search area. You can define ru les 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 all owed in every other geographical region.

Sharing Level

In a scenario in whi ch more than on e dealer, SD organization etc. can access the same vehicle stock (defined by the vehicle search area), you can increase or decrease the availability of a vehi cle for other dealers, sales organi zations etc. by using th e 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 (Vehicl e Manager), perform a vehicle search, c hoose a vehicle and then choose the tab p age 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, configuration, 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.

You can define further vehicle data acc ording to your requirements. To do this, choose Customizing for the Vehicl e Management Sys tem (VMS) ® Enhancements ® Define Additional Data for Vehicl e (transaction OVELO4). If you are dealing with qualifiers in the additional tabl e, 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 fields in the lists of the vehicle overview and the vehicle details. You can find further information under Programming Your Own Actions.

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 find further information under

Business Document Navigator

1.3 Master Data Use Every vehicle model that is managed with VMS is describ ed by a configurable m aterial and the appropriate class. Before you can work with VMS, you must first maintain characteristics, classes, variant conditions, object dependencies and material master records. Furthermore, you have to create specific basic and Customizing data.


Page 8 of 65

Integration The master data that you require belongs to the following SAP applications: · · · · ·

Material Master Record Class ification System Variant Configuration Pricing (SD and MM) Busines s Partner Adminis tration

Features Vehicle model with material master and configuration Vendor and customer , in general manufacturer and dealer End customer as customer of the dealer VMS role for centralized c ontrol of VMS (organization role, vehi cle model, configuration role) Action control for representing the business process Vehicle IDoc for transferring vehicle data between manufacturer and importer

1.3.1 Vehicle Model Definition 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 specific configuration or specific 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 specific vehicle model.

Structure Vehicle models are created in the SAP DIMP system as configurable m aterials (material type VEHI = configurable vehicle). Classes with characteristics are assigned to the materials. A vehicle model can be a general vehicle type or a vehicle type for which specific characteristic values have been p redefined using object dependencies.

VMS does not use material variants.

It is recommended that you define vehicle models g enerally so that configuration changes c an be made dur ing the sales process without having to change the vehicle model. Exampl e: you have defined the vehic le model SAPc ar . If the dealer receives a quotation for a SAPc ar hatchback but then decides on a SAPcar limousine after all, this change is p ossible within the vehicle model SAPcar . However, if you have defined the vehicle model on the level of SAPcar hatchback and SAPcar limousine , in other words, you decide to work with specific 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. On the other hand, you should not define 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 defined very generally, the material master record threatens to become very large, which ultimately means bad performance. Exampl e: you have defined the vehic le models car and lorry . Every time you create a new car, the material master record is locked for a short while and extended.

Example Vehicl e model Characteristics

SAPcar

· · · · · ·


Ex terior colour Interior colour Motor Numb er of doors Number of seats Number of gears · Sp ecial features (radio, air-conditioning, GPS , central locking, seat heating, sunroof)

Page 9 of 65

See also:

· Creating a Vehicle Model · Constructing a Vehi cle Configuration

1.3.1.1 Creating a Vehicle Model Use Every vehicle model that is managed with VMS is describ ed by a configurable material and the appropriate class . Before you can work with VMS you must have created material master records for the vehicle models. You can find further information in the documentation for Logistics – General under

Material Mas ter (LO-MD-MM).

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

Procedure The following only describes fields in the material master record that you require and that are evaluated in VMS. All other required fields are fields that the standard system requires and not VMS. Identical fields that appear in more than one view are mentioned each time they appear. 1. Choose transaction MM0 1 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 configurable vehicl e ( VEHI ). Simil ar to the material typ e for configurabl e materials ( KMAT ), this material type defines that the vehicle model can be configured and, furthermore, (unlike the material type KMAT ), it can be purchased/bought in. 3. Make entries in the fields as follows: View

Basic Data 1

Field

Base unit of measure

Field Value

Piece/unit (or the unit for which has been defined – 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 configurable

Set indicator

Classification

Class type

300 (variant class), enter model class Optional: 001 (material class), enter fami ly class (see: Constructing a Vehicle Configuration )

Sales and Distribution: Sales Organization 1



Division Sales and Distribution: Sales Organization 2

Sales and Distribution: General/Plant

Across different distribution channels: general item category group

VMS0 (Vehicle VMS)

Dependent on distribution channel: item category group

VMS0 (Vehicle VMS)

Batch management requirement

Set indicator (see: Vehicle)

Availability check

No check



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 i n VMS.

MRP 1

MRP type

No MRP

Accounting 1



Division

Purchasing


Page 10 of 65

Value assignm ent/valuation category

Valuation class Price control

X (autom atic, batch) If you want to define valuation category X for a newly created plant, you may first have to enter the following in Customizing for Materials Management under Valuation and Account Assignment ® Split Valuation ® Activate Split Valuation ® Local Definitions ® Categories and activate Organizational Units: Valuation Category X for the new plant. 3100 (trading goods) Moving average price

4. Save your entries.

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 find the item category group in the material master record for the view Sales and Di stribution: Sales O rganization 2 . Item 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 activi ties in Customizing for Sales and D istrib ution (in the given order): 1. Sales ® Sales Documents ® Sales Document Item ® Define Item Category Groups 2. Sales ® Sales Documents ® Sales Document Item ® Define Item Categories 3. Sales ® Sales Documents ® Sales Document Item ® Assign Item Categories

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 Distrib ution under Basic Func tions ® 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 ® Define 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 ® Define Requirements Types . No account assignment category has been defined in requirements class 041 since VMS works with individual batch valuation. Check the settings in Customizing for Sales and Distribution under B asic Functions ® Availability Check and Transfer of Requirements ® Transfer of Requirements ® Define Requirements Classes..

Although account assignment category E is often used for configurable materials, this is not possibl e for VMS since the vehicles are not managed as sales order stock.

Constructing a Vehicle Configuration Use If you want to be able to configure a vehicle in VMS, you have to maintain characteristics, c lasses, variant conditions and object dependencies for the basic vehicle model. You can find further information in the documentation for Logistics – General or in the documentation for Cross-A pp lication Components . ●

Variant Configuration (LO -VC)

●

Classification System (CA-CL)

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


Page 11 of 65

Procedure 1. Op tional: define a characteristics group. To do this , choose Classification System ® Characteristics ® Define Characteristics Groups in Customizing for Cross-App lication 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 specific vehicle group. 2. Create vehic le characteristics with characteristic values in the characteris tic 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 v ehicle 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 specific characteristic attributes, for example, search for all red vehicles irrespective of vehicle model. 4. Op tional: group the characteris tics together in order to disp lay them on the interface on their own tab page or in their own file (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 SAP Internet Pricing and Configurator (SAP IPC) together into files. If you want to use this function, you must have entered a name in the interface design field on the configuration initial screen tab in the configuration profile. 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 r ecords for your vehicle models and enter the classes in the material master (see: Creating a Vehicle Model). 6. Create a configuration profile for the vehicle model you have created for class type 300 (transaction CU41). The configuration profile 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 specific pricing characteristics to the configuration characteristics of the vehicle model in the object dependency functions (see: Creating a Variant Condition for Pricing).

Result The configuration data is thus complete and available in the VMS vehicle search functions (see: Vehicle Search). However, this data is not available to you in SAP IPC until you have downloaded it to the IPC system.

You can add objec t characteristics to the vehicle configuration (transaction VELOO BJC), for example, the characteristic sales cam paign . You can find further information in the documentation for the Classification System under under Adding an Object Characteristic to the Configuration.

Reference Characteristics and in the VMS documentation

1.3.1.2.1 Creating a Variant Condition for Pricing Use Pricing in VMS is based on condition technique . The basis is always the pricing procedure that has been defined as default in the SAP Internet Pricing and Configurator (SA P IPC). It is recommended to use the standard prici ng procedure RVAA0 1 as default value. However, you can enter your own prici ng procedure as the default. In the organization roles (transaction VELORO) you can also enter other procedures for specific organizations. These values then override the default value. There are three types of price: · Gross listed price (action CREA Create vehicle ) as list p rice for the configured vehicle without dealer discounts and other discounts · MM price (action ORD1 Create purchase order ) and SD p rice (action CUOR Create sales order ) SD and MM prices are formed from the gross price, the variant prices for the individual configures characteristics and, where appropriate, the discounts. You can find further information in the documentation for Sales and Dis tribution ond/or Materials Management under: ·

Pricing and Conditions (SD)

·

Conditions and Price Determination (MM-PUR-VM)

Prerequisites You have defined pricing procedure RVAA01 (see above) as the default value in SAP IPC.

Procedure This procedure only describes a very simple example as a guide for creating variant conditions. Variant conditions can be very complex. Create gross prices for the vehicle that has not been configured – once in sales and once in purchasing. ¡ Sales: transaction VK11, condition typ e PR00 , key combi nation material with release status; enter sales organization, distribution channel and material. ¡ Purchas ing: transaction MEK1, condition type PB0 0, k ey combina tion material info. record; enter vendor, material and purchas ing organization. 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 p age Additional Data :


Page 12 of 65

¡ for characteristics in sales: table name SDCOM (structure which the sales order accesses), field name VKOND ¡ for characteristics in purchasing: table name MMCOM (structure which the purchase order accesses), field name VKOND 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 configuration characteristics to the price characteristics using object dependencies.

Example: $SELF.SD pricing characteristic = 'Variant condition for configuration characteristic_1 and characteristic value_1' IF configuration 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.

If you have created the key for the variant configuration with small letters, you must also use small letters for the object dependencies. Likewise capital letters. You can find further information in the Basis documentation under

Dependency Sy ntax: General Rules.

You can also use variant tables to link the configuration characteristics to the price characteristics. Create a variant condition with a price for this characteristic value for each configuration characteristic and each possible value – once in sales and once in purchasing. ¡ Sales: transaction VK11, condition typ e VA00 , key combi nation variants; enter sales organization, distribution channel and material. ¡ Purchas ing: transaction MEK1, condition type VA0 0, k ey combina tion variants for info. record; enter vendor, material, purchas ing organization and info. record category. Assign the dependency to the configuration profile (transaction CU42).

Result The price determination data is now complete. However, this data is not available to you until you have downloaded it to the IPC system.

Adding an Object Characteristic to a Configuration Use An object characteristic is not a configuration characteristic but rather a characteristic that is cr eated 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 qualifiers. Attributes and qualifiers are the same as far as business is concerned, but differ in their technical realization. You can find further information on object characteris tics in the documentation for the Classific ation Sys tem under Reference Characteristics and further information on additional data and the app ropriate tables in the documentation for the IMG activi ty Define Additional Data for Vehicle. If you add an object characteristic to the configuration as described below, you can store object d ependencies for this object characteristic. This may be useful, for example, if you want to link specific sales campaigns to discounts.

Procedure 1. Create the desired obje ct characteristic in your characteristic group (transaction CT04) and assi gn it to your class (transaction CL04). No values are assigned to this characteristic. Enter the following data on the tab p age Additional Data : ¡ for a characteris tic with reference to the vehic le table: table name VLCVEHICLE, (example: sales campaign: field name CMPGN) ¡ for a characteris tic with reference to the additional data table: table name VLCADDDATA, field name QAUSP 2. Add the characteristic to the configuration (transaction VELOO BJC). Enter the table, field and characteristic name again for each object characteristic and define whether the characteristic should be displayed on the interface in the Vehicle Manager or not. In this table you have to specify which qualifier you want to use (for a characteristic with reference to the additional table). Enter the name of the qualifier in the field Field name . You can find this number in Customizing for VMS under Enhancements ® Define Additional Data for Vehicle ® Define Qualifiers (transaction OVELO4).

1.3.2 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 fleet 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 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


Page 13 of 65

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.

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 specific ac tions (the vendor, for example for the action ORD1 Create purchas e order , the customer, for examp le, 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 purchas ing view (ven dor)

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 c entrally. 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) ¡ Purchas e order currency ¡ Purchasi ng group (alternatively also in the purc hasing info. record) ¡ Indicator for goods-receip t-based invoice verification (alternatively also in the purc hasing info. record) This indicator is not necessary if you are not working with goods-receipt-based invoice verification.

Create a purc hasing info. record manually for each vendor. Leave the field Valuation type under Purchas ing organization 1 empty . Do not use the Customizing setting (Customizing for Materials Management ) under Purchasing ® Environment Data ® Define Default Values for Buyers , indicator InfoUpdate – Purchase order ), which defines that a purc hasing info. record is created automatically when a purchase order is created. The field Valuation Type is filled when this Customizing setting has been made. This leads to problem s when you want to create vehicl es. · Choose transaction XD0 1 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 ¡ Ship ping conditions ¡ Acc ount assignm ent 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

1.3.3 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 b y the action ADCU Additional End Customers . Using this action you can associate multip le end customers to a vehicl e 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 find further information under

SAP Business Partner (SAP-BP).

Prerequisites You have defined number ranges and groupings in Customizing for Busines s Partner Adminis tration and defined one of the groupings as an internal standard


Page 14 of 65

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 field Customer is filled with a value indic ate a debtor, in other words a dealer. Roles for which the Customer field is emp ty are for importers. The field Customer determines that the dealer entered can only view the end customers that he or she has c reated himself or herself and not customers created by other dealers. If the field is empty, in other words if you are dealing with an importer, all the end customers can be viewed.

Customizing for Business Partner Administration

Busines s partner role VLC00 1 End Customer for creating end customers is contained in the Customizing that is delivered. All end cus tomers 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 b e assigned using action ADCU. You can find 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 Ass ign 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 Assi gn End Customer ○ ADCU Additional End Customers ○ SOEU Used Vehicl e Sales: Create Order ○ O2CO Create Vehicle, Purchase Order and Sales Order ○ CRCO Create Vehicl e 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.

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.

1.3.4 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 descrip tion in Customizing for VMS under Define VMS Roles (transaction OVELO19 ).

Features


Page 15 of 65

There are three types of role: · Org anizational R ole This is a role to which organizational data is assigned. Organizational data is dealer or importer data ( plant, sales organization, distribution channel, divis ion, SD document type, cus tomer, ship -to party and pay er ). A role for which the field Customer is filled with a value indicates a debtor, in other words a dealer. These fields 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 fields in the sales order are filled with the appropriate organizational data. The dealer cannot change this data. The Customer field is also evaluated in the SAP grap hical user interface (SAP GUI ). If there is an entry in this field, 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 field is empty, all the end customers are visible.

If you work with the user parameters VELO_SO LDTO Customer, Sold-to party , VELO_SHIPTO Ship-to party and VELO_ BILLING Bill-to party , you do not need to create a sep arate organizational role for each indi vidual dealer. You only require one role for all y our dealers. Each dealer is then identified by the user parameters as a sp ecific dealer. Furthermore, you can assign a vehicl e search area and an original ordering party to the organizational role. These fields 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 fields are required inSAP Internet Pricing and Configurator (SAP IPC). The prices in SAP IPC are displayed in the given currency and the pricing procedure overrides the pricing procedure that is contained within SAP IPC as a standard setting. Furthermore, the currency field controls the currency in which the user sees the prices in the vehicle overview and in the detail data for the vehicle. The fields that affect purchasing are currently not evaluated and therefore have no significance. 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.

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. · Configuration role This is a role that is assigned to a configuration change profile. Depending on the vehicle model, status and so on, the configuration role specifies which vehicle characteristics the system should make visible for the user and which changes the user is allowed to make to the vehicle characteristics.

It is recommended that you create at least two configuration 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 configurations than your dealers.

Activities 1. Assi gn vehicle models to the vehicle model roles (transaction VELORM). 2. Assi gn organizational data to the organizational roles (transaction VELORO ). 3. Op tional: if desired, define configuration change p rofiles and, i n the profile determination, define which profile can be used for which configuration roles (transaction VELOP). 4. Assi gn roles to the users (transaction VELORU). You should assign exactly one organizational role, one configuration role and one or more vehicle model roles to a user.

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 flexibility when changes are made later.

Creating a Configuration Change Profile Use A configuration change profile controls, depending on the status of the vehicle and the configuration role that the VMS user has, which configuration characteristics can still b e changed in the SAP Internet Pricing and Configurator (SAP IPC) and which cannot. For example, when you create a sales order or change a purchase order etc., characteristics that can no longer be changes can either be displayed or rendered invisible to the user.


Page 16 of 65

You can, for example, subdivide the configuration characteristics into characteristics relevant to the order such as colour or motor, and characteristics relevant to rework , such as accessories, for example a roof rack. The dealer can then, as of a specific 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-specific requirements (right-hand or left-hand drive, yellow headlights etc.) or characteristics that relate to levels of emission allowed by law, such as exhaust pipes or catalysts.

Prerequisites · You have created the necessary material master data and configuration data and downloaded it to the IPC system. · You have created a configuration role for each role that there is to be in the configuration activity in SAP IPC (for example, importer employee, dealer employee).

Procedure 1. In transaction VELOP, create a configuration change profile for every combination of characteris tics that can be changed and under Define Visib ility of Characteristics , define which configuration characteristic s you want to be vi sib le but not changeable and which you do not want to be vi sib le. To do this, you must know the configuration characteristics for the vehicle models for which you want to create the configuration change profile. 2. Define when you want the profile to be used under Define Determination of Profile . Determination can be dependent on the following parameters: ¡ Configuration role ¡ Vehicl e model ¡ Availability status ¡ Primary action control ¡ Primary status ¡ Secondary action control ¡ Secondary status

For primary and secondary statuses you can also use a generic status, for example a status with placeholders such as MM* or SD*. You can find further information under Vehicle and under Action Controls. All this data is for optional fields, in other words, you can choose how much or how little data you want to include. The entry that best fits the vehicle is used. Create an entry for each status combination for which you can execute an action with configuration. You can group together more than one status with the generic status and thus reduce the number of entries.

You can analyze the determination of the configuration change profile with transaction VELOPR. For example, you can display which configuration change profiles already exist for a specific vehicle model and a specific characteristic. With this information you can then check whether your entries in the table for defining configuration change profiles (transaction VELOP) are correct and complete.

Result When you start SAP IPC from the Vehicle Manager in order to configure a vehicle, the system determines which configuration role has been assigned to the user, which vehicle model the user is currently configuring and the status of the vehicle that is being configured. Depending on these input parameters, the system determines which configuration profile has to be used during the configuration and transfers this profile to SAP IPC.

You can define your own determination logic in the business add-in (BAdI) VLC_DETERM_CHPROFILE.

Example There are the two configuration roles, im porter and dealer, for which you have created the VMS roles KPIM and KPHD . The vehicl e model M EDIUMCAR has the configuration change characteristics MOTOR , AUSSENFARBE ( exterior colour) and INNENFARBE (interior colour) . When the manufacturer has confirmed the purchase order (let us presum e this is primary status MM10 of prim ary action control MMCT ), then the importer is no longer allowed to change the m otor and the deale r is allowed to change neither the motor nor the ex terior nor the interior color. You therefore need the following two configuration profiles: Profile

Description

Characteristic

Changeability

CP_ONE

Engine cannot be changed

MOTOR

cannot be changed

CP_TWO

Engine, exterior color, interior color cannot

MOTOR

cannot be changed

be changed

EXTERIOR_COLOR INTERIOR_COLOR

cannot be changed cannot be changed

Profile determination is then as follows: Profile

Role

Material

Primary action control

Primary status

CP_ONE

KPIM

MEDIUMCAR

MMCT

MM10

CP_TWO

KPHD

MEDIUMCAR

MMCT

MM10


Page 17 of 65

Calculation of Gross List Price Using Organizational Roles Use When you create and configure 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 configuration. 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 specific 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 specifies the data for a specific 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 GRO S in transaction VELORO . 2. Make an entry in the following fields in this organizational role: ¡ Plant ¡ Sales organization ¡ Dis tribution channel ¡ Division ¡ Sales document type ¡ Pricing procedure ¡ Currency All vehicles should have gross list p rices in the same currency so that you can search for vehicles in a sp ecific price range without having to convert prices.

1.3.5 Action Control Use You can represent your business processes in the system with action controls. You define which actions can follow one after the other when handling vehicles and which changes to the status of the vehicle are involved in this.

A vehicle that the importer has ordered from the manufacturer receives the status Ordered . After the manufacturer has confirmed the purchase order, in other words has performed the action Confirm purchas e order , the status changes automatically to Purchas e order confirmed .

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 defined the following parameters in Customizing for VMS under Control Data : · · · ·

Actions (transaction OVELO 1) Vehicl e status (transaction OV ELO12) Vehicle availability (transaction OVELO13) Vehicl e locations (transaction OVELOL

Features You can distinguish between primary and secondar y 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 financial process is also possible. You can “finely tune” the primary and secondary processes with different action controls. This means that processes can be different depending on the sales


Page 18 of 65

organization or vehicle model etc.

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 specific vehicle models do not require any actions for local rework or for reservations etc.

Activities Choose Control Data ® Define Action Controls and Define Action Matrices (transaction OVELO11) in Customizing for VMS. Define the following there: 1. D efine 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 define 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 sys tem. 3. For speci fic combinations of action control and action, create an entry with data on availability, delivery s chedule 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.

The action Change sales order can be p erformed either early in the process b efore the purchase order is created or later after the purchas e 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.

1.3.5.1 Example for Action Control Availability Status and Action The following graphic displays how the actions can influence the availability status. In the graphic below, a little flag 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).


Page 19 of 65

Address/Location and Action The following graphic displays how the actions can influence the address and/or the location of a vehicle. In the graphic below, a little flag 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 Confirm order ) · Customer master (for exampl e, for the action Transfer to dealer ) · Customizing of vehicl e locations (for examp le, location In transit for action Post goods issue )

1.3.5.2 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 i ndividual ly and at the same time. An exam ple for determination at the same time is the inter-link ing action CRCO Create vehicle and sales order .

You can define your own logic for action c ontrol determination us ing the B AdI VLC_ DETERMINE_CONTRL.

Prerequisites · You have defined the action controls in Customizing for VMS under Control Data (transaction OVELO11). · You have entered the information, which the s ystem requires for determining ac tion control, using transac tion 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 fields are key fields: ¡ Vehicl e model ¡ Plant ¡ Purchas ing organization ¡ Vendor ¡ Sales organization ¡ Dis tribution channel ¡ Division ¡ Customer You can define different action controls for any combination of these fields. Mostly, however, it suffices to define an action control for each combination of vehicle model and plant for the primary action controls and for each combination of sales or ganization and cus tomer for the secondary action controls. You don not have to enter a value in all the key fields. A key field that is empty means that the entry is valid for all values that are possible for this field.

Process Flow Determination of the action c ontrol works as follows: 1. In Customizing, the sy stem chec ks whether the action that you want to perform is a p rimary ac tion, a secondary action or both. 2. The system checks whether the appropriate action controls have already been assi gned to the vehicle. If yes, it uses these.

The assignment of an action control to a vehicle cannot be changed. 3. If no, the sys tem triggers the action control and evaluates the entries in the table for transaction VELOS. This takes p lace on the basis of the action data and the existing vehicle data. The system makes checks in the following order: a. Is there a fitting entry in the table for transaction VELOS? If yes, the sys tem uses this entry. b. If no: is there a generic entry that fits, in other words, an entry for which fields are empty and therefore all existing values c an 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.


Page 20 of 65

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 ac tion in the ac tion control. If the system does not find 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 ac tion with the following action data: vehic le model Sprinter, p lant 77 77 . No primary action control has been assigned to the vehicle. There is no entry that fits exactly i n the table for transaction VELOS , in other words, there is no entry for which only the fields vehicl e model Sprinter and pla nt 7777 are filled. However, there is an entry for vehicle model Sprinter , plant 777 7 and vendor: Opel . But this entry is too specific due to the entry of a specific vendor and cannot therefore be used. There is another entry for the vehicl e model Sprinter for which only the vehic le model has b een entered and no other fields have an entry in them. This entry is taken since the missing entry in the plant field means that the entry is valid for all existing plants.

1.3.6 Vehicle IDoc Definition 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 Applic ation Server under

Processing of IDocs.

Use · The inbound IDoc serves mainly as a communication means between the manufacturer and yourself as importer. The manufacturer can confirm 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 ® Define External Status ): it finds 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 Vehi cle 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 find 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.

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.

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 finds 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 identification : required segment, number 1 (organization channel, external status, vehicle ID, internal/external vehicle number, vehicle identification 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, s ales camp aign, gross l ist price, currency, vehicle s earch area, original ordering party, access authorization) ¡ E1VLCC1 configuration 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 (qualifier, qualifier characteristics) · E1EDS01 general totals segment: required segment, number 1 The fields Organization channel , External status and one of the vehicle numb ers must be filled in segment E1VLCK1 for inbound IDocs and in segment E1VLCK2 the field Vehicl e model (only for Create actions). The inbound vehicle IDoc has message type VLCCPO Vehicle: purchase order confirmation/status tracking , the outbound vehicle IDoc has message type VLCVDT Vehicle detail data .


Page 21 of 65

Example for an Inbound IDoc As importer you receive a purchase order confirmation from manufacturer X that contains a small configuration change. The vehicle has, for example, a different colour from that speci fied in the purchase order. The external status is Purchase order confirmed with change . In Customizing you have assi gned the action Change purchas e order to the external status Purchas e order confirmed with change and the organization channel XY . As soon as you confirm the configuration change, the system p erforms this action. The vehicle recei ves the internal status Purchas e order confirmed and the purchase order is changed accordingly.

Calling the Status Monitor for the Vehicle IDoc Use 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 r eject the changes manually.

You can displ ay logs for the status monitor with transaction VELOP 01 or by choosing You can delete the logs with transaction SLG2 (object VMS_IDOC).

Hist. Logs in the selection screen of the status monitor.

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 defined in Customizing for VMS under Control Data ® Define 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 p osted because as error has occurred (red traffic light) ¡ 52: the IDoc has not been p osted because ch anges have b een made that must be confirmed (amb er 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 vehicl e) to be p erformed straightaway. The IDoc status 52 changes to 53. Set this indicator only if you are sure that you want to accept all the changes. Deselec t the indicator if you want to trigger this process manually by selecting the desired IDocs from the list and choosing

Acc ept .

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 configuration characteristics, the yellow area the qualifiers 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 accep t the IDoc data with

Acc ept or reject the data with

Reject .

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.

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

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

Prerequisites · You have maintained the master data required for the Vehicle Management System · You have linked VMS to the SAP Internet Pricing and Configurator (SAP IPC). · 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


Page 22 of 65

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 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. For this reason there are no entries in the menu. The following graphic display s a simplified layout of the Vehicle Manager screen that you access by using transaction VELO.

There are the following functions on the appropriate tab pages: · Vehicle Search Search for vehicles that fulfill specific requirements. The default settings dictate that this tab page is in the foreground. · Vehicle Overview Hit list for the vehicle search with numerous filter options. · Vehicle Detail Data for the vehicles that you have chosen in the vehicle overview. · Executing Actions Execution of business transactions for the chosen vehicles, for example 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 that still do not have a reference to a vehicle and assignment of suitable vehicles from the warehouse stock or the order pipeline. · Display of Warranty Claims for the vehicle For all functions, the vehicle is the central object. Only when the vehicles are assigned to sales documents is the basis the sales document and not the vehicle.

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

1.4.1 Vehicle Search Use You use the vehicle searc h (transaction VELO, tab p age Find ) to search for vehic les that fulfill 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 configuration coincides with the desired configuration of the end customer. If you find a vehicle with the desired configuration, you reserve it for the end customer, create a sales order for this end customer or perform another action. If you do not find a vehicle of the desired configuration, create a new vehicle, provided you have the authorization to do so. As importer , you use the vehicle search as follows: ● for your own Workflow: 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 specific dealer has created in a specific period of time an so on.

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


Page 23 of 65

You can enhance the scope of functions in the vehicle search with the following BAdIs : VLC_MODELLIST_NO_FIL: Adaptation of model list (without filter) VLC_VHVIN_PREPRARE: Large and small letters for VIN VLC_S EARCH_INTERFACE: Adaptation of search interface VLC_SEARCH_PROFILE: Search profile 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 ● If you know the internal or external vehic le number or the vehicle identification number (VIN), you can enter this number and search for a vehicle directly .

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 identification number (V). The vehicle identification number (VIN) has 17 characters. If you work with this number, it usually suffices to enter the last 10 characters since the first seven often indicate the model. The system then searches for *VIN. An error message is displayed if the system finds more than one vehicle. ● If you do not know a number, y ou can search for vehicles according to specific criteria . You have the following groups of criteria, so-called search views, at your disposal: ○ Configuration ○ Vehicl e history You can use this search view to find vehicles for which a specific action was performed in a specific 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 specific vehicle location. As importer, you can find information on questions such as how many vehic les have been ass igned the status In transit today? How many orders did reworker X receive las t month? ○ General vehicle data ○ Vehicl e 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 profile management If you often search for a specific combination of criteria, you can save your search template to a user-specific search profile and call it at any time. For more information, see: Working with a Search Profile. ○ Customer-specific

If you use SAP Sup ply 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 fulfill all the given criteria (AND operation). The more criteria you choose, the more you limit the possible number of vehicles that can be found.

You can replace exis ting views or create your own ones. To do this, choose Vehicl e Search ® Define 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 configuration if you have assigned the appropriate vehicle models to a common family class (see also: Constructing a Vehi cle Configuration). You can display the vehicles found, with configuration and vehicle data, in an overview. ● Provided you have imp lemented BAdI VLC_PRESELECTION in Customizing under Logistic s Execution ® Vehicl e Management Sys tem (VMS) ® Business Add-Ins (BAdIs) ® Vehicle Search ® Preselection of Vehicle Models and you are using a class hierarchy that has been defined and to which all VMS vehicle models have been ass igned, you can make a p reselection of vehicle models. ● You can use the Toggle function to switch between the flat ALV vehicle model list and the hierarchical ALV model tree.

1.4.1.1 Searching for a Vehicle Searching for an Individual Vehicle You use this type of search if you are looking for a specific vehicle and you know one of the vehicle identifiers (internal or external vehicle number or vehicle identification number). This returns the single vehicle you are looking for. 1. Choose transaction VELO. The Vehicle Manager screen appears and you can see the tab page Find on this screen. 2. At the top right, choose the vehic le identification type that you want to use for the search (next to the field Indiv. Vehicl e ). 3. 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 configuration and the vehicle history.

Vehicle Search Using Search Criteria You use this type of search if you are not looking for any specific vehicle. The hit list may contain a number of vehicles that correspond to your search criteria. 1. 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. 2. Select the vehicle model that you want your search to be bas ed 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 clas s or you have chosen only one vehicle model, the search view Configuration is disp layed. If more


Page 24 of 65

than one model is selected and the characteristics of the chosen model are not the same, you cannot perform a search for configuration criteria. In this case, the search view General Vehicle Data is displayed. 3. Enter values for the desired search criteria. The criteria can bel ong to different views. For all search views other than the configuration 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 configuration 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 filter for the technical names of the values . The function Comparison type allows you to sp ecifical ly inclu de or exclude certain characteristic values. Using the field Validi ty date , you can search for a configuration that is/was valid on a particular date. Entering a date influences the following: · The descrip tion of the characteristic and its’ as signed val ues, for example, a value of characteris tic “color” could be named “lav a red” on 1st July 2003 and its name could have been changed to “fire red” on 1st August 2004. · The availabil ity of characteris tics and their values. For examp le, the value “winter pac kage” is added to the characteristic “pac kages” on 1st October 2004. This value can only be found if the validity date is 1 st October 2004 or later. You can find more information on family classes under Constructing a Vehic le Configuration. 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 field Search Profile (no search profile). Then all the search criteria are reset. If the field Search Profile was already empty, choose

to reset the search criteria.

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

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 specific search criteria, or whether, despite possible performance problems, you wish to display all the vehicles found including the configurations, or whether you wish to display the vehicles without the configuration data. If you choose the last of these options, you can load the configuration data at a later date by c hoosing Update Vehic les on the right-hand side of the vehicle overview. You define 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.

1.4.1.2 Working with a Search Profile Use In a search profile, you can group a combination of search criteria (user-specific) together under a profile 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 b ased on. 3. Choose your desired search criteria on the different search views . Choose the entry for search p rofile management in the field View . 4. Enter a name and a descrip tion for the search p rofile. 5. Save your entries.

Result This search profile now app ears in the list nest to the field Profile . You can change the profile by calling it, changing the criteria as required and saving the changes under the same profile name under the entry for search profile management.

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

to

1.4.1.3 Category Management Use Categories i.e. groups of vehicles whose similarities are defined by certain rules are formed in category management. These rules are evaluated during the vehicle search. You can define which vehicles you want to be displayed for which dealers.


Page 25 of 65

You can find further information in the documentation for Financial Accounting under

Rules and

Boolean Logic/Syntax.

Integration You can define 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 ® Define 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 define these rules, you can fill specific table fields, which reference to the vehicle or the vehicle searcher, with values and then link these fields to mathematical expressions using Boolean operators.

Only tables in the vehicle table can be taken into account for vehicle data, not configuration 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 defined and evaluates them in the given sequence. As soon as the system finds 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 sequenc e could look sim ilar to those lis ted below for a dealer that belongs to the organizational role Dealer Mül ler : · 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 defines 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 (defined 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. You can evaluate vehicle search areas and sharing levels b y defining 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 find further information under Category Management.

Prerequisites · You have created sharing levels in Customizing for VMS under Vehicle Search ® Vehicle Search Areas ® Define Sharing Levels (transaction OVELO27). · You have created vehicle search areas in Customizing for VMS under Vehicle Search ® Vehicle Search Areas ® Define Vehicle Search Areas (transaction OVELO20). · All the vehicles within one vehicle searc h area are technicall y compatib le and allowed in every other geographical region.

Features Vehicle search area

· The vehicle s earch area can b e dependent on product data (base c onfiguration) and organizational structures (sales organization, plant). In the standard


Page 26 of 65

system, it is only dependent on the plants. · A vehicl e search area can include more than one sales organization. · Each vehicle can only bel ong to exactly one vehicle searc h area.

The vehicle search area Benelux is allowed for the sales organizations Belgium, Luxemb ourg 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 vehicl e search area Europe Sp rinter for the expensiv e model Spri nter that is seldom sold. A dealer in Belgium would then only have the vehicles i n the area Benelux at his/her disp osal for standard models and the entire stock for the area Europe Sprinter for the Spri nter 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 vehicl e, c hoose one of the following options: · Create your vehic les using transaction VELO . If you create the vehicles using BAdI (VLC_ EXECUTE_ACTION, m ethod DATA_CHANGES_BEFORE_ACTION), assi gn a v ehicle search area and sharing level to the vehicles. · Create your vehic les 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 vehic les 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 ).

1.4.2 Vehicle Overview Definition 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 specific c riteria, the tab p age Overview appears.

Structure 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 c riteria (for example: availability, location, status, customer, vehicle model, configuration 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-cli ck on the value again, it is reactivated. With clicking on it is activated and all the other values are deactivated.

Only Ac tivate This Value you can ensure that, for any one criterion, only the value chosen by

The symbols have the following meanings: ·

Vehicles with this value are displayed.

·

Vehicl es with this value are not disp layed.

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 first six characteristics for the configuration 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 Configuration . By doubleclicking 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 disp layed as column in the hit list.

·

Characteristic is not disp layed as column in the hit list.

1.4.3 Vehicle Details Definition On the Vehicle Manager sc reen (transaction VELO, tab p age 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 configuration and the vehicle history.


Page 27 of 65

Use ● After you have searched for one specific vehicle, the tab p age Detail appears. ● After you have searched for vehic les using sp ecific cri teria, the tab pa ge Ov erview app ears. If you use the Control key to selec t more than one vehicle on the tab p age 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 p age Overview , all the vehicles are copied to the tab p age 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. ● Vehicl e data There are some additional pushb uttons in this area. The symb ol next to the appropriate function indicates that data exists. The following table lists the functions and explains what is displayed when you choose a specific function. Function

What is Displayed

Additional Data

Further customer-specific data (see: Programmin g Your Own Actions) Messages that have been sent with the action MSSO Ou tput Messages

Messages

You can also send new messages manually in addition to the message types defined 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 r equests 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 fields 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 fi eld in th e top left-hand corner. If you click on any of the status fi elds, you go to a view w here 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 i s more than one action that converts a vehicle form status X to status Y. If you click on any field on the left in the column with the old status, you can switch the red fields through all the existing values.

● Configuration ● Vehicl e 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 .

You can replace each of these areas by a customer-specific 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

If you have just performed an action and the update posting has not been completed yet, the data for the configuration, 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 disp lay with

Update Vehicl e List or with

Update Vehicl es.

1.4.4 Action Use 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.


Page 28 of 65

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 vehicl e itself versus financ ial actions, in other words actions that involve the paym ent transactions. · An action can influence the vehic le status. A primary action influences 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. O ld vehicl e status Quotation created 2. Ac tion Change vehicle is executed 3. Vehicl e status remains unchanged as Quotation created

Action that sets the vehicle status to a new value

1. O ld vehicl e status Quotation created 2. A ction Create sales order is executed 3. New vehicl e 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.

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 first action has been completed, the system cannot perform the interlinking action. · A whole host of actions are deliv ered with the standard system. In Customizing, however, you can modify these actions or define 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 specific requirements.

1.4.4.1 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 vehic les that you have previously sought and selected (see: Vehicle Search, Searching for a Vehicle, Vehicle Overview and Vehicle Details).

Features · You can control every ac tion with authorizations (authorization object C_AUTO_VMS). So you can set up your VMS system so that you, as importer, are allowed to perform all actions, but your dealer only the actions for the sales orders, inquiries/reservation requests. offers/reservations, assigning of end customer and hiding/displaying of vehicles. · You call an action by choosing it in the action list field in the upp er screen area and confirming with . The tab page Action app ears. 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 y et, only actions for creating new vehicles are displayed in the action list field. If you have already chosen vehicles, you only see the actions that are possible in the current process. If the primary and secondary action control is not yet known, too many actions may be displayed. The default settings dictate that only the actions that are allowed for all the selected vehicles are displayed. You can use the parameter name VELO_ACTLISTBOX = X to define that all the actions are displayed that are allowed for at least one of the selected vehicles. · You can p lace up to four actions that you use most often on pushbuttons . These pushbuttons are then displayed in the uppermost screen area and always at your disposal. If you want to do this, enter one or more of the following parameters: VELO_ACT1, VELO_ACT2, VELO_ACT3 and VELO_ACT4 and assign an action to each parameter as value. You can find the key for an action, for example CREA for Create Vehicl e in Customizing for VMS under Control Data ® Define Actions (transaction OVELO1). · An action bas ically 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 specific data to each vehic le, for examp le for the actions BUPA Ass ign end customer or INIV Create inbound invoice . You can recognize these vehicles b y the fact that the internal vehicle number is displayed in the right-hand screen area. Make the required entries for the first vehicle, then select the next vehicle in the left-hand screen area, make the entries for this vehicl e and so on. When you have compl eted all the vehic les, choose once. · You can see whether the action has been performed succes sfully or not by the success indicator in the left screen area next to each vehicle and the appropriate message in the status line. You can find further information on any errors that may have occurred in the log . Choose Log. Only the current VMS run is logged. As soon as you exit the transaction VELO, the log can no be displayed. You can use user parameter VELO_ACTPROTOCOL = X to make settings to define that the log is written to the database. You can then call it with transaction VELOP03 or delete it with transaction SLG2 (object VMS_ACTION). Saving the log is particularly useful for the test phase.

If you perform an action after you have called the log, the log is not updated automatically. Close the log and call it again. · The default setting dictates that all the actions (that create documents) c reate exactly one document with one item per v ehicle. The quantity per item is always


Page 29 of 65

one. If your order 10 vehicles, for example, a purchase order with 10 order items is created (default). Only ac tion DELI Create Delivery can, dep ending on sp ecific settings in Customizing for Sales and Distrib ution, create more than one document at a time.

Performing an Action In Batch Mode Use As a sys tem 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 define with which parameters you want to perform the action in a parameter variant. You can define 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 direc tly if you want to disp lay all exis ting parameter variants. Only if you want to display specific parameter variants, for example all parameter variants for a specific 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. A screen appears with the fields of all the existing action interfaces. 4. Choose an ac tion. Enter a name for the parameter variant and define the further p arameters with which y ou 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 Sup ported by Report screen app ears. 2. Choose the desired action and a parameter variant for this action. The parameter variant is a required field. 3. Limit the number of vehicles in the Vehicl e Selection area of the screen to those for which you want to perform the action /exc eption: all actions that create vehicles). Enter at least the plant. 4. If you want the action to be performed for all the vehic les 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 define 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 schedul e it. ¡ If you want to start the batch job immediately , choose Execute . If you have set the Trigger Action Direc tly indicator, a list containing error messages and succes s message s app ears. 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 app ears with all the vehicles that the system has found. You can select your desired vehic les 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 app ears. Enter the required data and choose the job to be executed and save your entries.

. The screen for scheduling jobs ap pears . Enter when you want

1.4.4.3 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

PDF Content This page content is in PDF format.

Download

PDF Content This page content is in PDF format.

Download


Page 30 of 65

1.4.4.4 Make-to-Stock Scenario Purpose You use this procedure if your dealers work with make-to-stock production or when you order vehicles for stock yourself.

Process Flow As importer, you sit down with your manufacturer, analyze the sales figures for the last business p eriod and decide on quotas for the individual vehicle models for the new business period. This decision made, you create the number of vehicles agreed on as planned vehicles (no value assignment possible) in your system. You do not allow values to be assigned until you actually order the vehicles from the manufacturer. As soon as you receive a purchase order confirmation from the manufacturer via IDoc, you make the vehicles visible, in other words, offer them for sale to your dealers. Your dealers can now make reservations and requests for reservations or also create a sales order directly. As soon as a dealer has created a sales order, he/she hides the vehicle from display so that it can no longer be seen by other dealers. Goods movements and invoices complete the process. The process is complete when your dealer delivers the vehicle to the end customer and the sales registration note with the license number has been returned to you. Here is an example of this procedure. (V) signifies an Interlinking Action.

Sequence

Action

Description

Who does this?

1

CRE1

Create planned vehicle (without values)

Importer

2

CMOD

Change configuration of planned vehicles

Importer

3

REAL + ORD1

Allow value assignment for vehicle and Importer create purchase order (alternative to steps 13 also ORD2)

4

MORD

Change purchase order

Importer

5

CONF

Confirm purchase order (action not contained in the Customizing settings delivered)

OEM via EDI

6

SHOW

Allow vehicle for search

Importer

7

SHMT

Confirm transit

OEM via EDI

8

GORE

Create goods receipt (also possible later in process)

Importer

9

INIV

Create inbound in voice (also possible later Importer in process)

10

RSVN

Create reservation

11

CUOR + HIDE

Create sales order and exclude vehicle from Dealer 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

Dealer

1.4.4.5 Make-to-Order Scenario Purpose You use this procedure if your dealers work with make-to-order production and do not produce for stock.

Process Flow In contrast to the make-to-stock scenario, you do not create the vehicle as importer. Your dealer does this with respect to a sales order. The vehicle created therefore has the configuration desired by the dealer or the end customer. As importer, you order the desired vehicle from the manufacturer. Larger dealers can, if required, create the vehicle, purchase order and sales order at the same time in an inter-linking action. The manufacturer confirms the purchase order and produces the desired vehicle. He/she updates the vehicle status using IDocs and informs you of the progress being made in production/delivery. Goods movements and invoices complete the process. The process is complete when your dealer delivers the vehicle to the end customer and the sales registration note with the license number has been returned to you.


Page 31 of 65

Here is an example of this procedure. (V) signifies 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 sales order

Dealer

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 order

Dealer

6

CONF

Confirm purchase order (action not contained in the Customizing settings delivered)

OEM via EDI

7

SHMT

Confirm transit

OEM via EDI

8

GORE

Create goods receipt (also possible later in process)

Importer

9

INIV

Create inbound in voice (also possible later Importer in process)

10

UORD

Start rework (purchase order and transfer posting)

Importer

11

UGRE

Finish rework (goods receipt)

Im porter

12

DELI

Create delivery

Importer

13

GOIS

Create goods issue

Importer

14

OUIV


Importer

1.4.4.6 Configuration Management Features · In VMS; we distinguish between the following types of configuration: Configuration

Display Option, Notes

Vehicle configuration

Transaction VELO, tab page Detail The vehicle configuration is part of the vehicle data and is stored in the vehicle table. It is the only configuration that is relevant in the vehicle search. You can save the customer’s desir ed confi guration using action SOCD. This is the configuration that contains the original configuration desired by the customer. When, in a make-to-stock scenario, a customer buys a vehicle for which the configuration does not completely fulfill his/her requirements, the configuration originally desired can be saved. You can then evaluate at a later date in how far th e actual and target configurations differ.

Sales order configuration

Standard transaction VA03 In the vehicle list, you can use go to the ones mentioned below.

Quotation configuration

Standard transaction VA23

Inquiry configuration

Standard transaction VA13

Purchase order configuration

Standard transaction ME23

Subcontracting purchase order configuration

Standard transaction ME23

Display Docum ent to go to this transaction and to

· The sales order, purchas e order and sub contracting purchase order configuration influence the vehicle c onfiguration in such a way that the vehicle configuration in the vehicle data mirrors the current physical configuration as far as possible. There is the following priority: a. Sub contracting purc hase order configuration b. Purchas e order configuration c. Sales order configuration d. Planned configuration (vehic le configuration before the documents are created) A new or changes configuration only influences the configuration if there is no configuration that has a higher priority (further up in the above list). If, for example, a purchase order exists, a sales order configuration does not influence the vehicle configuration, but it does if there is no purchase order.

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


Page 32 of 65

order configuration.

Configuration Management in MTS and MTO Purpose This process describes how specific configurations influence the vehicle configuration 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 configuration is at the beginning of the MTS scenario. 2. As soon as the purc hase order is created at the manufacturer, the configuration for the purchas e order bec omes the vehicle configuration. 3. As s oon as a sub contracting purchas e order is created for rework, the additional rework characteristic s are copied to the vehicle c onfiguration. If no rework is required, the purchase order configuration and the sales order configuration are the same. 4. At the end, the vehicle configuration shows what the vehicle reall y looks lik e. Make-to-Order-Scenario (MTO) 1. 2. 3. 4.

The vehicle configuration is at the beginning of the MTO scenario. As soon as the dealer creates the sales order, the configuration for the sales order becomes the vehicle c onfiguration. As soon as the purchas e order is created, its configuration is copied to the vehicle configuration. As soon as a subcontracting purchas e order is created for rework, the additional rework characteristics are copi ed to the vehicle configuration. After rework, the vehicle configuration and the sales order configuration are the same. 5. At the end, the vehicle configuration shows what the vehicle reall y looks lik e.

All actions for which configuring a vehicle and/or deleting configurations is p ossible have a set Template Configuration. You can change this template configuration using the BAdI VLC_PREPARE_ACTION (method PREPARE_FURTHER_ACTIONS). The first elementary action always sets the template configuration for inter-linking actions.

You can split the configuration using the BAdI VLC_CONFIG_SPLITTER. Splitting is useful if you want to distinguish between global and local characteristics. The global characteristics (OEM-relevant characteristics) are the written to the purchase order and the local characteristics to the subcontracting purchase order for rework.

1.4.4.6.2 Actions and Configurations Use Some actions have a reference or template configuration; this is the configuration with which the action is called. Actions influence the vehicle configuration and in some circumstances may create further configurations.

Features Below you can find a list of all the actions which allow a configuration to take place or which allow a configuration to be deleted.

Action

Template Configuration


CREA/CRE1 Create vehicle (values possible)/ create planned vehicle (no values possible)

None

A new vehicle configuration is created. If you have not configured when you create the vehicle, the vehicle configuration is created but remains em pty.

CVWT/CVT1 Create vehicle with template configuration (values possible)/ Create planned vehicle with template configuration (no values possible)

Template configuration form sales document or vehicle

A new vehicle configuration is created. If you have not configured when you create the vehicle, the vehicle configuration is created but remains em pty.

CMOD Change configuration of planned vehi cles


Vehicle configuration can be changed.

VDEL Delete vehicles without documents

Not required

Vehicle configuration can be deleted.

ORD1 Create purchase order

V eh icl e con fi gu rati on

V eh icl e con fi gu rati on can be ch an ged.


Further Configurations

P ur ch ase or der con fi gu rati on i s cr eated an d copied to the vehicle configuration.

Page 33 of 65

MORD Change pur chase order

Purchase order configuration


Purchase order configuration is changed. If none exists yet, one is created.

DORD Delete purchase order item

Not required

If a sales order exists, the sales order configuration is copied to the vehi cle configuration. If not, the planned configuration is reused.

Purchase order configuration is deleted.

IQRY Create inquiry


Vehicle configuration is not changed.

Inquiry configuration is created.

DEIQ Delete inquiry

Not required


Inquiry configuration is deleted.

OFFE Create quotation



Quotation configuration is created.

DEOF

Not required


Quotation configuration is deleted.

CUOR Create Sales Order

If exists, then quotation configuration, otherwise vehicle configuration

The vehicle configuration can only be changed if no purchase order exists.

The sales order configuration i s created and copied to the vehicle configuration if n o purchase order exists.

CHCO Change sales order

Sal es order con fi gu rati on

Th e veh icl e con fi gu rati on can on ly be changed if no purchase order exists.

The existing sales order configuration is changed.

DECO Delete sales order

Not required

If purchase order exists, the vehicle Sales order configuration i s deleted. configuration is n ot changed. If no purchase order exists, the planned vehicle configuration is reused.

UORD

If exists, then sales order configuration,


Start rework (pur chase order and transfer posting)

otherwise vehicle configuration

UDOR Rework: Delete purchase order and transfer posting

Not required

Vehicle configuration is reverted to what it Subcontracting purchase order was before rework. If several rework steps, configuration is deleted. the correct configuration can onl y be reused for the correct rework step.

RETU Create return

Sales order configuration


Sales order configuration is copied to the returns document.

POEU Trade-in

V eh icl e con fi gu rati on

V eh icl e con fi gu rati on can be ch an ged.

P ur ch ase or der con fi gu rati on i s cr eated an d copied to the vehicle configuration.

SOEU



A new sales order configuration is created.

Not required


The configuration desired by customer is created, if one already exists, it is changed.

Delete quotation

Subcontracting purchase order configuration is created and copied to the vehicle configuration.

Used Vehicle Sales: Create Order SOCD Save customer’s desired configuration

1.4.4.7 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 shipp ing ¡ Goods movements · Special processing ¡ Rework ¡ Processing returns ¡ Trade-in and used vehic le sales ¡ Service processing ¡ Warranty claim processing · Special VMS Actions

1.4.4.7.1 Creating Vehicles PUBLIC © 2014 SAP SE or an SAP affili ate company. All rights reserved.

Page 34 of 65

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

You can find 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 (without valuation)

Configurable material, configuration profile, class

Creates vehicle without batch and valuation type. The internal vehicle number is assigned

Vehicles must belong to the same vehicle model and have the same configuration

REAL

Allow values for vehicle

Planned vehicle

Creates batch and valuation type for vehicles th at have already been created with CR E1 or CVT1

CVT1

Create planned vehicle with template configuration (no values possible)

Configurable material, configuration profile, class, template configuration from sales document or vehicle

Creates vehicle without batch and valuation type and copies the template configuration from the sales document or vehicle

CREA

Create vehicle (with valuation)

Configurable material, configuration profile, class

Creates vehicle with batch and valuation type The internal vehicle number is assigned The nu mber of the batch and the valuation type are identical to the internal vehicle number

Vehicles must belong to the same vehicle model and have the same configuration Only advisable if the vehicle is really to exist in this form since the valuation type cannot be deleted later

CVWT

Create vehicle with template configuration (values possible)

Configurable material, configuration profile, class, template configuration from sales document or vehicle

Creates vehicle with batch and valuation type and copies the template configuration from the sales document or vehicle

CMOD

Change configuration of planned vehicles

Planned vehicle

Changes configuration of planned Only for planned vehicles since vehicles the configurations cannot be changed in pu rchase order docum ents and sales order documents

VDEL

Delete vehicles without documents

There must be no equipment and no document (pur chase order, sales order etc.) for the vehicle

Deletes vehicle without documents. If configurations and batches exist for the vehicle, th ese are also deleted.

Valuation types are not deleted with this action. You can delete valuation types individually and manually using transaction MM06.

Vehicle that has already been

Changes the vehicle value in the

This action is useful if costs have

posted in goods receipt and is managed in stock with a quantity of 1

valuation segment of the material master. A price change document (LO) and an accounti ng document (FI)

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

RVAL

Revaluate vehicle


Page 35 of 65

are created.

1.4.4.7.2 Procurement: Purchase Order Use The following graphic displays how actions that involve purchase orders can follow one after the other.

You can find further information in the documentation for Materials Managem ent under

Purchase Orders (MM-PUR-PO).

Features (I) signifies an Interlinking Action. Action ORD1

ORD2 (V)

Description

Create purchase order

Prerequisites


Vehicle to which you can assign values, creditor, purchasing info. record

Creates a purchase order at The complete configuration i s manufacturer for existing vehicles written to the pur chase order (by default).

Create vehicle and purchase order

Notes

CREA + ORD1

MORD

C han ge pu rch ase order

Pu rch ase order Goods issue should not have been posted

Changes the configuration and the The selected vehicles m ust be in delivery date of order items an d the same purchase order; but not performs pricing again all vehicles in the purchase order have to be selected You can onl y change the configuration and delivery date parameters

DORD

Delete order item

Purchase order Goods issue should not have been posted

Deletes purchase order items.

1.4.4.7.3 Procurement: Incoming Invoice Use The following graphic displays how actions that involve incoming invoices follow one after the other.

Features Action INIV

Description

C reate i ncom i ng i nv oi ce

Prerequisites


Notes

P ur ch ase or der Enters incoming invoice The action is used for incoming The goods receipt m ust h ave been Currency and payment conditions invoi ces for actions ORD1 Create posted for goods-receipt-related are taken from th e purchase order purchase order and POEU invoice verifi cation


or the purchasing i nfo. record

Trade-in and not for incoming invoi ces after rework. There can only be one purchase order without an incoming invoice for a vehicle If there is more than

Page 36 of 65

one, the incoming invoice for the newest purchase order is automatically posted Incoming invoices for one-time vendors cannot be created with this action. Cancel incom ing invoice

IIVR

Incom ing invoice

Creates cancellation docum ent for The incoming invoice can only be incoming in voice cancelled completely 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.

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 d ealers . 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 sy stem (quotation and inquiry are standard objec ts, reservations and reservation requests are VMS objects) · Print documents · Configure vehicles The report REP_MAIN_QUEUE (transaction VELOR Update reservation queue ) deletes all exp ired reservations, reservation requests, quotations and inquiries. If a reservation is deleted (from the report or manually), it results in the next reservation request becoming a reservation. If the current date does not coincide with the validity period of this reservation, the validity date is changed to include the current date and all the following reservations move accordingly in time too.

You can display the logs for this report with transaction VELOP02 and, for example, determine for which dealer a valid reservation exists. You can then inform this dealer per e-mail, if necessary. You can delete the logs with transaction SLG2 (object VMS_RESV).

Prerequisites You have created vehicles but not yet entered any sales orders for these vehicles.


Page 37 of 65

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) signifies an Interlinking Action. Action RSVN

Description

C reate reservati on

Prerequisites


Notes

N o sal es order, n o qu otati on an d no reservation can exist for the vehicles Plant calendar (if you require one when calculating the validity periods)

Reserves the vehicles for a specific dealer and wri tes the dealer as customer in the vehicle data

The standard validity amounts to three working days from the creation date You can im plement your own logic using the BAdI VLC_RESERVATION You can display the reservation and the reservation requests in transaction VELO (tab page Details , screen Vehicle Data . Pushbutton Reservations

OFFE

C reate qu otati on

RSOF

Create reservation and quotation

R eser vati on for th e sam e deal er

)

C reates a qu otati on for th e deal er for which the reservation is also valid RSVN + OFFE

(I) DERS

Delete reservation

Reservations The selected vehicles mu st be reserved for the sam e dealer

Deletes the reservation for the vehicles If no sales order exists, th e dealer is deleted as customer form the vehicle data

DEOF

Delete quotation

Quotation

Deletes the quotation; deletes customer and end customer from the vehicle master and confirms delivery date

DERO

Delete reservation and quotation

DERS + DEOF

Create request for reservation

Creates a reservation request for

You can display the reservation

the vehicle

and the reservation requests in transaction VELO (tab page Details , screen Vehicle Data .

You can onl y delete an entire document and not only individual items

(I) RSVM

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 im plement your own logic using the BAdI VLC_RESERVATION IQRY

RSIQ

(I)

Create inquiry

Reservation request for the same

Creates an inquiry for the dealer

dealer

for which the reservation request is also valid

Create reservation request and inquiry

RSVM + IQRY

DERQ

D el ete reservati on requ est

R eservati on requ est

DEIQ

Delete inquiry

Inquiry

DERI

(I)

Delete reservation request and inquiry

Del etes th e reservati on r equ ests for the vehicles You can only delete an entire document and not only individual items DERQ + DEIQ

1.4.4.7.5 Sales: VMS Actions in Sales Order Use The following graphic displays how actions that involve sales orders one after the other.


Page 38 of 65

For more information, see the documentation for Sales and Di stribu tion under

Sales Order

Features (I) signifies an Interlinking Action. Action

Description

BUPA

Assign end customer

ADCU

Prerequisites

Additional End Customers


Notes

Assigns an end customer to the

An importer can display all end

vehicles You can also create an end customer

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

Assigns multiple end customers to a vehicle along with business partner roles and vali dity dates. You can also create new end customers or can change existing end customer data.

End customers created in specific roles can also be assigned to different roles by specifyin g the required data in the end customer details for that particular role.

CUOR

Create sales order

Customer master record for dealer Creates sales order for vehicles and enters dealer to which the vehicles are to be sold and the vehicle usage in th e vehicle data; deletes the reservation queue. You can also create and assign an end customer

This action cannot be used for reselling used vehicles with the Trade-In process.

CHCO

Change sales order

Sales order

Changes sales order If the configuration i s changed, pricing is performed again. You can also create and assign an end customer.

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

DECO

Delete sales order

Sales order

Deletes sales order with the most recent date. Deletes end customer and dealer (customer) from the vehi cle data

You can only delete a complete sales order, not individual items.

CRCO (I)

Create vehicle and sales order

CREA + CUOR

Only advisable in the MTO Scenario

O2CO (I)

Create vehicle, purchase order and sales order

CR EA + O RD 1 + C UO R

O nl y advi sabl e i n th e MTO Scenario

CCPO (I)

Change sales order and purchase order

CHCO + MORD First changes the sales order and then the pu rchase order.

Only advisable in the MTO Scenario

Sales: Assignment of Vehicles to Sales Documents Use


Page 39 of 65

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

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

Features Action

Description

Prerequisites


L oosel y as si gn s an appr opri ate A link between the sales vehicle to a sales document with a docum ent and vehicle is saved customer’s desired configuration

LORS

C reate l oose rel ati on sh ip

S al es docu men t, veh icl e

DELR

Delete loose relationship

Loose relationship

TIRS

C reate ti gh t r el ati on sh ip

S al es docu men t, veh icl e

Ti gh tl y assi gn s an appr opr iate

Notes

Batch and valuation type of vehicle

vehicle to a sales document with a are entered in the sales document, customer’s desired configuration and the key of the sales document in entered in the vehicle document table DETR

Delete tight relationship

Tight relationship

The sales docum ent does not have to be deleted

1.4.4.7.7 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 Di stribu tion under

Billing.

Features Action

Description

Prerequisites


Notes

OUIV


Sales order

Bills the sales order with the most Outgoing invoices are only recent date possible if r elated to sales order, not related to delivery More than one order can be grouped into an outgoing invoice if specific criteria have been fulfil led

OIVR

C an cel ou tgoi ng i nvoi ce

O utgoi ng i nvoi ce

Can cel s exi sti ng ou tgoi ng i nvoi ce You can on ly can cel an en ti re document and not only individual items

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


Page 40 of 65

For more information, see the documentation for Logistics Execution under

Delivery Processing.

Features Action DELI

Description

Create delivery

Prerequisites


Notes

Sales order Vehicle must be in importer’s stock

Creates delivery for sales order with the most recent date

You can spli t a sales order into different deliveries More than one order can be grouped into a delivery if specific criteria have been fulfilled For this to be the case, the appropriate indicator in the sales area data of the customer m aster record (tab page for shi pping) 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 order with the most recent date

You can only delete a complete delivery, n ot 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.

You can find further information in the documentation for Logistics Execution under Goods Receipt.

Goods Issue and in the documentation for Materials Management under

Features Action GORE

Description

Create goods receipt

Prerequisites


Purchase order

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

GRER

Cancel goods receipt

Goods receipt

STOL

S tor age l ocati on posti ng

G oods r ecei pt Creates a material document for Vehicle cannot be in repair/rework the transfer posting from one


Notes

receipts for actions ORD1 Create Purchase Order and POEU Trade-in and not for goods receipts after r ework. There can only be one purchase order withou t goods receipt for a vehicle If there is more than one, the goods receipt for th e newest purchase order is automatically posted. It cannot be posted to the sales order stock.

Creates cancellation document for This action can cancel a complete goods receipt goods receipt or indivi dual document items. This action can still be performed after a delivery has been created

Page 41 of 65

storage location to another

as long as no goods issue has been posted for this delivery. Posting across different plants is not possible.

GOIS

Create goods issue

Delivery

Creates a material document for a The storage location from w hich goods/stock issue the goods issue can be posted cannot be changed after the delivery has been created. Goods issue documents must have a 1:1 relationship to the delivery.

GISR

Cancel goods issue

Goods issue

Creates a cancellation document for the goods/stock is sue

This action onl y cancels a complete docum ent. It can only be used for goods issues that have been created with the action GOIS.

1.4.4.7.10 Rework (With Goods Movements) Use The following graphic displays how actions that involve rework follow one after the other.

The reworker is repres ented in the SAP sys tem as a v endor in the role of a sub contractor. For more information, se e the documentation for Materials Ma nagement under

Subcontracting.

Vehicles can be reworked more than once.

Processing rework is only p ossible using an external service p rovider.

Actions DO RD, MORD, G ORE, 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 defined which characteris tics are to be reworked by which vendor. · If only p art of the configuration is to be assigned to a subc ontractor order, you have impl emented BAdI VLC_CO NFIG_ SPLITTER, which comp ares the purchase order configuration with the sales order configuration. The differences between these two define the scope of the work to be done.

Features Action

Description

Prerequisites


Notes

UORD

Start rework (pur chase order and transfer posting)

Procurement process completed up to and i ncluding goods receipt Reworker created as creditor in th e system Subcontractor info. record Bill of material (if components to be provided are being worked on) as super BOM with object

Creates subcontractor purchase order and transfer posting for the vehicle in the su bcontractor stock The BOM is exploded

The components to be provided for the subcontractor purchase order can only be determined by exploding the BOM The transfer posting of these components to the subcontractor stock takes place outside VMS (i n the standard transaction MB1B)

dependencies for the BO M explosion: the vehicle must be a component in the BOM

UDOR

Delete rework purchase order and The vehicle must be in transfer posting subcontracting stock


There is only one entry in the history so you can only display the purchase order and not the transfer posting You can enter a default valu e in the field Reworker with the user parameter VELO _REWORKER Deletes the su bcontracting purchase order and creates a cancellation document for the

Page 42 of 65

transfer posting UGRE

Finish rework (goods receipt)

UGRR

Rework: cancel goods receipt

The vehicle must be in subcontracting stock

Creates a goods receipt document with reference to the subcontracting purchase order

The goods receipt is posted for all the components to be provided in subcontracting purchase order

Creates a cancellation document for the goods receipt for the subcontracting purchase order

1.4.4.7.11 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 classified as being a used vehicle, actions SPEU and SOEU from the Trade-In process succeed the actions displayed above when the vehicle is resold. For more information, see the documentation for Sales and Di stribu tion under

Returns.

Features Action RETU

Description

Create return

Prerequisites


Sales order

Creates return for a vehicle that has already been sold

Notes

A return can only be created with reference to a sales order and not with reference to an outgoing invoice You do not have to select all the vehicles in the sales order You have to define item category, copy control and item category determination

RELI

Create returns delivery

Return

REGI

Goods receipt for returns delivery Returns delivery

Creates returns delivery for a return to register the arrival of the vehicle and to post the vehi cle to stock Posts goods receipt to the blocked stock return s

RECM

Create credit memo for returns

REUS

Transfer vehicle from blocked stock returns to un restricted-use stock

Return

Creates a credit memo for the return

Vehicle in blocked stock returns

Posts vehicle from blocked stock returns to unr estricted-use stock so that it can be resold

1.4.4.7.12 Used-Vehicle Scenario Use Vehicles can be taken in part exchange/as a trade-in or bought back more than once. You can find further information in the documentation for Materials Managem ent under

Purchase Orders (MM-PUR-PO).

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:


Page 43 of 65

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 configuration can be mapped automatically. Scenario 2:

This is an independent process with a used vehicle model, but without a reference to a new vehicle. Configuration can be entered manually. Scenario 3:

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 b ought back and resold as a used vehicle.


Description

BBDF

Define/change buy-back conditions

CREA

Prerequisites

Create vehicle (with valuation)



Notes

This action allows you to define buy-back conditions, su ch as: · P lanned buy-back date · Bu y-back price · Short and long text describing other conditions

This action can normally be executed after creation of the sales order for the new vehicle.

See: Creating Vehicles When you trade-in vehicles that you have alr eady sold as an importer, you do not have to

Page 44 of 65

perform this action. If a used-vehicle model is chosen, this action all ows you to specify the original vehicle and, provided a mapping has been defined, map the original configuration to the used-vehicle configuration. CRUV

Create used vehicle

UVSW

Switch “used vehicle” flag

POEU

Trade-in

Configurabl e m aterial , configuration profile, class Model defined in transaction code veloum

Vehicle

This action creates the vehicle based on a used-vehicle m odel

This action supports automatic mapping of the configurations. The used-vehicle indicator is automatically switched.

Switches the flag for marking the vehicle as a u sed one on/off

You can use this action when your used-vehicle process follows the new- vehicle process in your matrix. In other words, when the vehicle h as been created for the new-vehicle process and the same vehicle record is being used for the used-vehicle process.

Creates a normal purchase order A purchasing info record should for the vehicles not exist for the vendor. In contrast to action OR D1 Create If a record does exists, you m ust Purchase Order , the price and the ensure (in the pricing procedure) vendor (also one-time vendor) that the price entered manually have to be entered manually in the has priority over and above the interface price in the pur chasing info record. You can access a calculation sheet in this action, provided the former has been created for the vehicle. In this case, the fields Net Price and Curr ency are disabled. Their values are taken from the calculation sheet.

GORE

Create goods receipt

CRPU

Create and trade-in vehicle

See: Goods Movements: GI, GR CREA + PO EU

(I)

This action can only be perform ed for exactly one vehicle. Actions CREA, POEU and CRPU are usually executed during buyback. You can also execute them when buy-back conditions are defined (in other words, when the vehicle is s old) if you prefer to have the purchase order in advance, for example, for planning purposes.

RVAL

Revaluation (see also: Creating Vehicles, action RVAL)

SPEU

Used vehicle sales: determine price

SOEU

Used vehicle sales: create order

Changes the vehicle value in the valuation segment of the material master.

If a used-vehicle model is chosen, you can access the pricin g procedure and edit the corresponding section. Th e Debit/Credit Amount field is disabled. Its value is calculated from th e appropriate section of the calculation sheet.

The vehicle has been return ed to the im porter’s stock due to tradeins or returns processing.

Overwrites the gross list price in the vehicle data with the resell price The resale price is a manually fixed price that is i ndependent of the configuration of the vehicle.

If a used-vehicle model is chosen, you can access the pricin g procedure and edit the appropriate section. The field Resell Price is disabled. Its value is calculated from th e corresponding s ection of the calculation sheet.

The vehicle has already been sold once and has been returned to stock by a trade-in process or returns processing Resale price (action SPEU).

Creates a sales order for the used vehicle and can overwrite the entries for customer, end customer and vehicle usage

This action is a very simplified version of action CUOR Create Sales Order , for which numerous restrictions apply:


● No returns processing is 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 .

Page 45 of 65

You should use a different pricing procedure for pricing than y ou use for action CUOR. Background: condition type VA00 (variant pri ce) is contained in the pricing procedure fin the case of CUO R, in other words, the pri ces depend on the configuration during pricing (see also: Creating a Variant Condition for Pricing). You shoul d not, however, use condition type VA00 for action SOEU since the price is in dependent of the configuration here and determined manually u sing action SPEU. This r esale price is transferred as condition type PR00 by default. You can define a different condition type for the resale price in BAdI VLC_EXECUTE_ACTION, method DATA_CHANGES_BEFORE_A CTION. You m ust 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_A CTION. You can enter the docum ent type in VLCACTDATA_CS-AUART. CSCR

Create calculation sheet for used vehicle

CSED

Edit sales order calculation sheet

You have defined a calculation sheet profile.

Creates a calculation sheet that is attached to the vehicle.

The calculation sheet can be accessed in th e followin g standard actions: BBDF, POEU, RVAL and SPEU. You can use this action after the 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.

Definition of Buy-Back Conditions When a new vehicle is sold, buy-back conditions are defined. These conditions usually contain: ● the buy-back date ● the price to be pai d if the vehicle is returned on this date You can also define 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 c an be rejected). There are three possible situations when a customer initiates buy-back: ● The vehicle was sold by this i mporter and buy-b ack c onditions have b een defined at the point of sales of the new vehicle. ● The vehic le was sold by this importer but buy-bac k conditions have not been defined. ● The vehicle was not sold by this imp orter. In the first case, the price is determined based on the predefined 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 configuration of the vehicle plays an important role, the configuration of used vehicles (see below) has only an indirect influence 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 .


Page 46 of 65

You can map a vehicle model to the calculation sheet profile that you have previously defined in Customizing for the Vehicl e Management System (VMS) under Control Data ® Define Calculation Sheet Profile by using transaction code VELOMCS . If there is no entry for your used-vehicle model, the global parameters from transaction OVELO00 are 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.

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

Configuration of Used Vehicles Configuration of used vehicles is general, whereas for the new vehicle every option in the configuration is usually defined on a very detailed level (for example, the exterior color can be defined 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 define 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 configuration of the used vehicle. In other words, the original configuration of the new vehicle is preserved for the usedvehicl e process. You can mark this vehicle as a used vehic le by exec uting action UVSW ( Switch “used vehicl e” flag) in order to differentiate between vehicles that are new and vehicles that are used. ● Work with a sp ecial model with a speci al “used-vehic le” configuration 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 usedvehicle objects have a more generic configuration. You can maintain the link between new and used-vehicle objects and the mapping of the configurations 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 , p rovided that you have maintained your used-vehicle model by using transaction code VELOMNR.

Mapping Between the New Vehicle Configuration and the Used-Vehicle Configuration Mapping of models

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

Source configuration

Source characteristic Source Value

Assignment method

Destination

Destination

configuration

characteristic

Destination val ue

New vehicle configuration

Exterior color

Lava red

Directly in transaction VELOCM

Used vehicle configuration

Exterior color

Red


Exterior color

Fire red



Exterior color

Red


Exterior color

Dark red



Exterior color

Red

New vehicle

Characteristic N

BAdI

Used vehicle

Characteristic M

configuration ….

VLC_USED_VEHICLE configuration …

….

….

….

….

…..

This configuration 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 configuration manually. Generally speaking, you can also map the characteristic values of one configuration 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 configuration (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


Page 47 of 65

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

There are two options for service processing: · Processing only with a service notification , in other words, without a service order. This is the quickest type of service processing if no costs that have to be settled are incurred. · Processing with a service notification and a service or der . 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 notification and create a service order directly. You can find further information in the documentation for Customer Service under

Service Object as Equipment,

Service Notification,

Service Order and

Processing Services.


Description

Prerequisites


Notes

CREQ

Create equipment

Vehicle

Creates an equipment for a vehicle and writes the equipment number in the vehicle data

SMNO

P roces s s er vi ce n oti fi cati on

O pti on al : equ ipm en t

C reates a C S ser vi ce n oti fi cati on with claim items and organizational data and all ows you to change or complete existin g service notifications. You can enter a separate item with problem, affected object part, reason for claim, actions and measures for rectifying the

If you enter the value X for user parameter VELO_SMNO_POPUP_MODE, you always branch dir ectly to the screen for creating a n ew service notification or, if a notification already exists, to th e screen for changing this notification. This is useful if you fundamentally do not

damage for each claim .

want to allow more than one service notification.

C reates a C S ser vi ce or der wi th operations. Items in the service notification become operations in the service

If you enter the value X for user parameter VELO_SMOR_OPR_MODE, exactly one operation wil l be

SMOR

C reate s er vi ce or der

O pti on al : s er vi ce n oti fi cati on

order. You can propose planned created in th e service order. The working times for the operations. service notification items are not The order can be released copied. automatically depending on which settings have been made in Customizing for CS. SMCO

SMIO

Confirm service order

Service order

Create billing request for service

Service order

order

SMOC (I)

Create and confirm service order

Optional: service notification

Confirms actual working time and External servi ces cannot be used components to the service confirmed. order. Any number of partial confirmations possible. Creates a billing request for a

The billing document has to be

service order. The billing request covers all confirmed components and working times for this service order for which no billing request yet exists.

created outside VMS (for example, in collective processing).

SMOR + SMCO

1.4.4.7.14 Warranty Claim Processing PUBLIC © 2014 SAP SE or an SAP affili ate company. All rights reserved.

Page 48 of 65

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 Equipm ent ● Warranty Claim Processi ng without Equipm ent

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 ( Equipment, Master Warranty, Measuring Points) that is necessary to carry out the whether a warranty still exists for a specific vehicle or not.

Warranty Processing (LO-WTY). They serve to create the master data Warranty Check in

Processing, in other words, to check automatically

Action

Description

Prerequisites


Notes

CREQ

Creates equipment for the vehicle

Vehicle

Creates an equipment for a vehicle and writes the equipment number in the vehicle data.

WRTY

Assign master warranty

Equipment for vehicle, master warranty

Assigns master warranties to equipment th at has been created using action CREQ.

MEAS

Assign measuring points

Equipment for vehicle, reference equipment

Creates measuring points for the measurement positions and warranty counters for th e reference equipment for equipment that has been created using action C REQ.

You can use BAdI VLC_MASTER_WARRANTY to read master warranties for vehicles for which you have created equipment u sing action CREQ. These master warranties are then to be assigned to all vehicles in action WRTY.

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 vehic le detail screen by c hoosing MW/Meas.P . The master warranty is assi gned in the upp er 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 defined in the template obje ct. In Customizing choose P lant Maintenance and Customer Servic e ® Warranty Claim ® Define Template Objects .

Action GEOB

Description

General object number

Warranty Claim Process ing ®

Prerequisites


Notes

Vehicle

Creates a type of intermediate object for a vehicle for whi ch no equipment exists.

This action is technically required if you want to assign measuring points or master warranties to a vehicle without equipment.


Page 49 of 65

WYVH

Assign master master warranty warranty

Vehicle,, master warrant Vehicle warranty y

Assigns master master warranties warranties to a vehicle for which there is no equipment.

This action is required for batch batch processing.

1.4.4.7.15 Special VMS Actions Use The following graphic display which special VMS actions there are and how they can follow one after the other.

Features Acti on

Descri ption

SOCD

Save customer’s desired configuration

P rerequ i si tes

Wh at does th e acti on do?

Notes

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

SMOD

CORR

Change vehicle

Defined values in Custom iz izing for Allows change changes s to vehicle vehicle usage, vehi cle search search area attributes and qualifiers (see and sharing level Customizing for VMS under Defined qualifiers qualifiers in Customizing Enhanc Enhanceme ements nts ® Pro Progra gram m

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

and assignment to action SMOD

list on entry screen) You can program any number of such actions that work with different fields

Correc Corr ectt sta status tus (witho (without ut chec heck) k)

Actions and Enhance Actions Enhancements ments ® Define Additional Data for Vehicle)

Internall ac Interna actio tion n tha that, t, in cont ontras rastt to This act action ion cannot be started the other actions, is not actually an manually using transaction action si nce it does not link to a action primary or secondary matrix If you exec execute ute transaction VELOE ( Emerge Emergency ncy Monito Monitoring ring ), 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

Exclud Exc lude e ve vehic hicle le fr from om se sear arc ch


Sets the ve Sets vehic hicle le at attr tribu ibute te fo for r visibility to not displayed The dealer usually performs this action in the MTS Scenario as Scenario as soon as he has bought a vehi cle so that other dealers do not have access to the vehicle Default setting = vehicles not

VELO

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

· You can use the vis ibi lity dependently of the VMS role (dealer, importer) as parameter when selecting

Page 50 of 65

displayed SHOW

Allow vehicle vehicle for for search search

Sets the vehicle att attribute ribute for visibility to displayed

CAMP

Assign sales sales campaig campaign n

Values for sales ca campaign mpaign (transact (transa ction ion VELOC VELOC )

Sets the vehicle attribute Sales campaign ca mpaign to a new new value

vehicles from the database (BAdI VLC_SEARCH_ ADAPTION) · You can use the vis ibi lity according to the selection in Category Management (vehicle filter) as parameter. Allows changes to vehicle attributes and qualifiers (see Customizing for VMS under Enhancement Enhancements s ® Program Actions and Enhancements Enha ncements ® Define Additional Data for Vehicle) The point of this act action ion i s to trigger pricing again in the sales order (due to assigned sales campaign) There are two options:

· You can add the field as an object characteristic to the vehicle configuration (see: Adding Object Characteristic to Configuration)) Configuration · You can use the options options for flexible enhancements to SD p ricin ricing g LCTN

Set veh ic icl e l oc ocati on on

Val ue ues for ve veh ic icl e l oc ocati on on s i n Sets the vehicle attribute attribute Vehicle Customizing for VMS (transaction loc locatio ation n to a new value and and OVELOL) assigns the address of the vehicle location locat ion to the vehi cle

SHMT

Confi rm transit

STWO

Tri rig gger Wo Work rkfflo low w eve event nt

Org Or gani niz zatio iona nall stru struc ctur ure e, task tasks s

MSSO

O ut utput m es essages

Custom iz izi ng ng for VMS for m es essage Outputs messages (possibly as determination part of an inter-linking action)

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

Actions such Actions such as these these,, for example exa mple Confirm purchase purchase orde order r can be defined in Customizing

Only use Only useful as as pa part of an an inte interlinking action Triggers the sending of e-mails with Workflow items, these refer to the actions with which the action STWO has been linked You can can display th e sent messages in transaction VELO (tab page Details , screen screen Vehicle Data . Pushbutto Pushbutton n ) You can find further information in the documentation for Cross Applicatio Applic ation n Components Components under under Message Control (CA-GTF-BS) and in the IMG for VMS in the docum doc um entation for message determination.

ADDO

Assign business business doc documents uments

Assigns doc documents uments to a vehicle vehicle

You can You can display display the sto stored red documents in transaction VELO (tab page Detail , scree screen n Vehicle Data . Pushbutton Pushbutton Documents Doc uments ) You can find further information in the documentation documentation for for Cross Applicatio Applic ation n Components Components under Business Document Navigator .

ARCS

Sett arc Se rchi hivi ving ng in ind dic ica ator

ARCD

Delete archi ving indi cator

EMMI

Rep Re port eve vent nts s fo for SCE SCEM M

The actio ion n mat matri rix x mus mustt be se sett so Fl ag ags ve veh ic icl es es fo for ar ar ch iv ivi ng ng that only vehicles with the appropriate appro priate status status (example: sold, delivered, paid ) are flagged flagged for archiving. Cancels archi ving flag

An eve event nt ha hand ndle lerr fo for the the ve vehic hicle must exist in SAP SCEM.

S ee ee: Archiving Vehicles Vehicles This action is an internal action that is executed within transaction VELOARSL

See: Archiving Vehicles Vehicles This action is an internal action that is executed within transaction VELOARSL

Reports SAP SCEM events to the See: Connection to SAP SCEM Event Handler, which is assigned You can can display th e SCEM to the vehicle information in transaction VELO (tab page Detail , scree screen n Vehicle Data Dat a . Pushb Pushbutt utton on


SCEM )

Page 51 of 65

E xp xpor t v eh eh ic icl e to CR CR M

CRMV

In di di vi vi du du al al ob obj ec ect se setu p on CR CR M mu st have been prepared to import VMS vehicles

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

See: Connection to SAP CRM Sales process takes takes place in S AP DIMP Then postpost-sales sales processes, for which the vehicle is the centre of attention, can take place in SAP CRM You cannot transfer two vehicles with the same VIN to CRM. Dupli cat cation ion of VINs ca can n occur in VMS Used Vehi cle Sales Process. Process. This action should either be used for the new vehicle or the successor succe ssor used vehi cle and not for both

Add vehicle to CRM order order

CRMS

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

Transfers Assignment of Transfers Assignment of Vehicles Vehicles See: Connection to SAP CRM to Sales Documents to Documents to SAP CRM Sales process is initiated in SAP CRM and continued in VMS. The assignment of vehicles to sales docum doc um ents, h owever, takes place beforehand in SAP DIMP

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

Descri ption

P rerequ i si tes

Wh at does th e acti on do?

CPG M

Cross-pl ant goods m ovem ent

Enabl es the goods m ovem ent of a vehicle from one plan t/storag t/storage e location locat ion to another pl ant/storag ant/storage e location

REPL

Realize in plant

Creates a batch for a vehicle in an additional plant

Notes

You can can execute REPL on any existing vehi cle. You You specify the plant on the action screen; a batch and a valuation type will then be created creat ed for the vehicle in th is plant. This is n ece ecessary ssary because a sales order can only be created for a vehicle in a specific specific plant i f a batch has been created created in thi s 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 on this, see: Programming Your Own Actions. Actions.

Assignment of Vehicles to Sales Documents Use As importer, you you can use this functio functionality nality (transactio (transaction n VELO, tab page Assignmnt ) to search for for sales documents documents that a dealer has has entered and and to assign an appropriate appropriat e vehicle from the warehouse stock or or der pipelin pipeline e to each sales document. This is particularly useful in the following cases: · if your dealer can access y our system but has not been able to find find a vehicl e that corresponds to the the customer’s desired configuration · if your dealer does not not have acces s to your system and vehic les and enters s ales document with the customer’s desired c onf onfiguration iguration “offline”, “offline”, for example in SAP CRM Mobile Sales · if, for sales and dis tribution reasons, you want to assign a veh icle, whic h you have already promised to one one customer and thus already assigned a sal es 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), (MTS), for example as is common practice in the USA.

Prerequisites The sales documents contain a configuration but do not yet have a tight relationship with a vehicle, in other words, batch and valuation type have not yet been definitively 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 and order . · The functionality functionality refers to the sales document type inquiry, quotation and · You can search for the the sales documents either according to specific s election criteria or according to to vehicle model. · In BADI VLC_EXECUT VLC_EXECUTE_ASS E_ASS IGNMT you can define exactly which configuration characteristics and sales document fields or vehicle fields fields have to


Page 52 of 65

· ·

·

· ·

correspond so that a vehicle is suited to a sales document. The standard system settings dictate that all configuration characteristics have to correspond so that a sales document suits a vehicle. In other words, the sales document configuration must be 100% identical to the vehicle configuration. If you enhance the standard implementation of the BAdI appropriately, you can also include sales document or vehicle fields in the matching process. Furthermore, the standard settings dictate that the customer’s desired configuration is not overwritten by the vehicle configuration 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 profile for the vehicle search. BAdI and search profile act in combination during the search so that the settings for the search profile override the BAdI settings, where necessary. If you are working with categories, the vehicles are listed in the hit list according to the priorities defined in Category M anagement. You can change this sequence using the above-mentioned BAdI. You can compare the configuration of a sales document with the configuration 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 vehicl e to a sales document, you can decide b etween a loose relationship between vehic le and sales document and a tight relationship . ¡ The loose r elationship 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 confirmation 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 D elete 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 p rocessing in transaction VELO, mass p rocessing in transaction VELOAS . Mass processing makes sense if the manufacturer generally produces to stock and you want to find suitable vehicles for a large number of sales documents. If you have not found a suitab le vehic le for a sales document, you can create a vehicle with a template configuration . You have the following actions at you disposal for this: ¡ CVWT Create Vehicle with Template Configuration, with Batch and Valuation Typ e ¡ CVT1 Create Vehicle with Template Configuration, without Batch and Valuation Typ e If, in transaction VELO on the tab p age Ass ignmnt (Ass ignment), you have selected a sales document without a relationship to a vehicle, the template configuration is the configuration of the sales document. If, on the other hand, you have selected a vehicle the template configuration is the configuration 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 configuration is always the vehicle configuration.

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 Ass ignmnt (Ass ignment) in the Vehicl e Manager screen. 2. In the area entitled Search for Sales Documents , selec t 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 field. Start the search by choosing Alternatively, you can restrict your search further by choosing

Find with Models .

Selection Options. In the selection options screen, you can display further selection

options via New Field Selection and activate them by double-c lick ing. The fields and values in the search are saved dynamical ly and proposed for the next search. In the area Search Result: Vehicles and Sales D ocuments , all the sales documents that are found are display ed in the upp er table. The search only finds sales documents without a link to a vehicle (no sym bol) and sales documents with a loose relationship to a vehicle (symb ol with a tight relationship. 3. Select exactly one sales document in the list of sales documents.

), but not sales documents

4. If necess ary, choose a search profile for the vehicl e 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 vehicl e and a sales document (symb ol 5. Select exactly one entry in the list of vehicl es.

).

6. Compare the configuration of the selec ted sales document with that of the selec ted vehicl e. Choose table or

Configuration Sales Document above the upp er

Configuration Vehicl e above the lower table.

7. In the action list field, choose action LORS to create a loose relationship or action TIRS to create a tight relationship and confirm with Ok ay. The tab p age Action app ears. You can see the chosen vehic le on the left-hand side, and details for the sales document and vehicl e on the right-hand side. Here you can compare the configurations 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. You can change the selec tion manually with

Selection Op tions. In the selec tion options screen, you can disp lay further selec tion options via


New

Page 53 of 65

Field Selection and activate them by double-clicking. The fields and values in the search are saved dynamically and p roposed for the next search. 2. In the Transaction group field, choose whether you want to search for inquiries, quotations or orders, choose the desired action and, if necess ary, a searc h profile for the vehicle search. 3. Choose Execute. The system displays a list of the vehicles that are found. 4. Selec t 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 clai ms that have been created for the appropriate vehic le in component LO-WTY Warranty Claim Processing (transaction WTY). You can find 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_ 00 03_ 00 09_ 00 09 display and assign master warranties and measuring points.

If you want to assi gn master warranties for more than one vehic le at the same time, you can us e action WYVH Assi gn Master Warranty to Vehicle. · Display of Warranty Claims (tab page Warranty ) ¡ All existing warranty claims for the chosen vehicle with all the warranty claim data is displayed ¡ By double-cli ckin g on the claim numb er you can access the Warranty Claim Processi ng transaction (transaction WTY) and display the warranty claim with all the information on its processing.

1.5 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 flexible as regards how and where it is used and therefore the business requirements in this respect can be very different.

We recommend that you do not archive vehicles within the warranty period.

Integration SAP standard archiving is used for archiving vehicles. You can find in the documentation for Cross-App lication Components under

Introduction to Data Archiving (CA-ARC).


Page 54 of 65

Features · First of all, vehi cle archiv ing allows you to select the vehicles y ou wish to archive (transac tion VELOARSL) and then archive them by using SA P standard archivi ng (standard transaction SARA, object name VEHICLE ). If required, you can display the archived vehic les again (transaction VELOARDI).

You can delete the archiving indicator with transaction VELOARSL. · Only the VMS internal data , that is vehicle data including customer-specific fields, additional qualifiers, vehicle history, links to standard documents, additional configurations, links to dealers and end customers, and the configuration 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 fields ¡ Vehicl e view: “flat” (not hierarchic al) disp lay of vehicle data, configuration, history and additional data. This disp lay is s imilar to the disp lay on the tab page Detail of transaction VELO. The only difference is that information is not made availab le via toggle bars – it is lis ted and can be scrolled. · The following actions are executed in the background when you execute transaction VELOARSL. ¡ ARCS Set archiv ing indicator ¡ ARCD Delete archiv ing indicator These actions are defined 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 flagged for archiving and not any vehicles that are still required.

Archived vehicles cannot be reloaded.

Activities 1. Choose transaction VELOARSL to flag vehic les for archiv ing. Enter the desired selection criteria and choose the vehicl es that correspond to your selection criteria. Select the desired vehicles from this list and choose for the vehicles you have selected.

Execute. A list app ears that disp lays all

Execute again. The archivi ng indicator is set

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

1.6 Technical Integration Use VMS is not only integrated completely with the standard components MM (Materials Management), SD (Sales and Dis tribution), CS (C ustomer Service) and FI/CO ( Financial Accounting and Controlling) , but it also contains interfaces to external SAP components.

Features You can connect the following SAP components to VMS: SAP Component

Scope of Functions

SAP Internet Pricing and Configurator (SAP IPC)

Configuration of vehicles in VMS

SAP Retrieval and Classification (SAP TREX)

Fast search for vehi cle configurations and vehicle m aster data in V MS

SAP Business Information Warehouse (SAP BW)

Evaluation of vehi cle configurations and vehicle master data

SAP Supply Chain Event Management (SAP SCEM)

Tracking of VMS vehi cles that are to be found at any place along the su pply chain

SAP Customer Relationship Management (SAP CRM)

Processing of post-sales processes with veh icles that have been imported from VMS , i n the Interaction Center for Automotive

Internet Accesses

SAP Web Application Server (SAP Web AS) with Discrete Industries Web Interface (DIWI)

Access to VMS via the Internet

SAP Enterprise Portal (SAP EP) with Busi ness Package for Automotive Channel Management

Access to VMS via the Internet


Page 55 of 65

Users can log on to VMS in different ways. The users at the vehicle dealers will usually do this via an internet connection to SAP EP or SAP Web AS. The dealer only needs to ensure that an Internet browser has been installed. The users at the importers have the choice whether they want to log on via SAP GUI or use the Internet access in the same way as at the dealers.

All components are optional, with the exception of SAP IPC. The component SAP IPC must be installed is you want to work with VMS.

1.6.1 Connection to SAP IPC Use SAP Internet Pricing and Configurator (SAP IPC) is used in numerous SA P app lications to configure products through the Internet. SAP IPC belongs, technical ly sp eaking, 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 the SAP IPC 7.0 is a component of the Application Platform (AP). Compared to the previous release that is 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 as SAP IPC 7.0 is moved to the SAP Web AS. This was done in order to use VMC.

This is not a J2EE Server, which is also a part of the SAP Web AS. The use of SAP IPC is obligatory in connection with VMS, since vehicle c onfiguration and pricing d uring the configuration in VMS can only be executed with SAP IPC.

Prerequisites ● If you want to use the default configurator for VMS, which is S AP IPC 7.0 : You should have created Extended Configuration Management (XCM) scenario in the corresponding J2EE server and made RFC connection to the J2EE server. ● If you want to use SAP IPC 4.0 (IPC standalone scenario), you should have installed it and im plem ented the BAdI VLC_IPC_SELECT.

You can find further information in SAP Servic e Marketplace under service.sap.com/instguides ® mySAP CRM . You can connect to a different external configurator by us ing BAdI VLC_CALL_ CONFIG in Customizing for the Vehicl e Management System under B usiness Add-Ins (BAdIs) ® Vehicle Configuration ® BAdI: Connection to External Configurator. ● You have connected VMS to SAP IPC, if that is the configurator you wish to use. ● You have executed an initial load from VMS to a new, emp ty IPC databas e and also a knowledge-ba se object, a knowledge-bas e profile and a runtime version.

Features ● The connection between VMS and the IPC database rem ains intact ev en after the initial load. As soon as the configuration master data in VMS change, the changed data is automatically replicated to the IPC database (delta load). ● You can change the parameters with which SAP IPC is called by using BAdI VLC_SCE_P ARAMETERS. ● SAP IPC is called for every configuration transaction in VMS, in other words, every time you choose

Configure when you execute an action.

You can implement user parameter VELO_SCE_FULLSCREEN to define that SAP IPC is called in full-screen mode and not integrated into the tab page Action .

Connection to SAP TREX or Another External Search Engine Use SAP Retrieval and Classification (SAP TREX) is a powerful SAP external search engine that is used in many SAP ap plications. SAP TREX belongs, technically speaking, to SAP Enterprise Portal , b ut it 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 c hoose. Based on this generic interface, VMS also provides an interface adapted to suit SAP’s search engine SAP TREX. The search through 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: ● ● ● ●

Adminis trate and monitor download of objec ts to SAP TREX Manage indexes Spec ify the RFC destination for SAP TREX server for a business obj ect Schedule and exec ute jobs for delta download of vehicles

If Customizing settings are done in SES for the object VMSVEHICLE, then the vehicles are searched using SAP TREX through SES. The transaction used is SES_ADMIN. If SES is not used then the connection takes place technically through the BAdIs VLC_EXTSE_SEARCH Vehicle Search Using External Search Engine and


Page 56 of 65

VLC_SE_ DELTA_LO AD Delta Load to External Search Engine. The BAdIs are empty and VMS is not connected to any search engine in the standard system. Both of the above-mentioned BAdIs have an example implementation with a commentary and example coding for an initial load report.

Prerequisites The prerequisites that are mentioned here refer only to the connection of SAP TREX. ● You have installed SAP TREX 6.0 or higher.

You can find further information in SAP Service Marketplac e under service.sap.com\instguides ® mySAP CRM ® SAP CRM 5.0 ® Installing Retrieval and Classification (TREX) in a Non-Portal Environment. ● You have connected VMS to SAP TREX. ● You have implemented BAdIs VLC_ EXTSE_SEARCH and VLC_SE_D ELTA_LOA D, and programmed and executed a report for the initial load, if SES is not used. ● In Customizing for VMS under Vehicl e Search ® Define Fields for TREX Download , you have entered the vehicle data that you want to be transferred. All the fields from the vehicle table VLCVEHICLE and customer-specific data from APPEND structures are counted as potential vehicle data. The configuration 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, configuration data and also customer-specific data to the search engine and thus make it available for the fast search for vehicles. This means that you can freely define, which search criteria you want to add to the fast search. In the first instance, the interface provides all the configuration 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 vehic les are downloaded to the search engi ne for the first 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 define, 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 searc h engine, the sy stem first executes the s earch in this s earch engine. Then it transfers the hit list to the normal database for further processing. ● Using SES adminis tration workb ench you can create, activate or deactivate search index. If SES is not used, you can decide y ourself which vehicles or vehicle models you want to assign to which search index in the external search engine, and in this way you can find 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.

There are the following restrictions in the use of SAP TREX: If you want to work with selection criteria with intervals, the search is, due to technical restrictions, automatically transferred to the normal database search and not to SAP TREX. SAP TREX only supports searching with exact attributes and not fuzzy searches.

1.6.3 Connection to SAP BW Use SAP Bus iness 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, for example, databases, online services and Internet. You use queries to analyze the data. Queries target specific 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. You can find further information in the SAP Help P ortal under Business Information Warehouse: Overview . 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.

You can find further information in SAP Servic e Marketplace under service.sap.com\instguides ® mySAP Business Intelligence . · You have connected VMS to SAP BW. · In VMS, you have mapp ed the VMS configuration characteris tics and BW characteris tics, if required, as describ ed below (transaction VELOBWC Ass ign Class Characteristics to BW Characteristics ).

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, v ehicle model, supp lier, customer, action control, primary and secondary statuses, availability s tatus, gross lis t price, planned production date, planned delivery date, and so on (extractor VELO26_VLC_BW_G A)


Page 57 of 65

¡ The configuration 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 assi gned to a vehicle (extractor 0AU_V M_BW_G D) ¡ Organizational data of a VMS user (extractor 0AU_V M_B W_G O): the corresponding DataSource extracts only the fields that are necessary for checking the authorization of a user for displaying dealer manager queries

Extractors 0 AU_VM_BW_G D and 0 AU_VM_BW_G O are available for BI Content 3.52 and higher. Queries can relate to vehicle data and configuration characteristics and can, for example, answer the following question: how many 90 horsepower vehicles of vehicl e model SAPCar have I, as importer, sold to dealer Smith within a speci fic period of time? · You can map the special VMS configuration characteristics to BW characteristics . A class with characteristics is ass igned to each vehicle model in VMS; each characteristic has a sp ecific number of possible c haracteristic values (see: Constructing a Vehic le Configuration). So that vehicles are comparable with regards to their characteristics, it makes sense to map these special vehicle-model-dependent characteristics to general vehicle-modelindependent characteristics. These BW characteristics then contain all possible characteristic values.

The vehic le-model-dependent VMS characteristics for ex terior colour_SAPCar and exterior colour_SAPRover can be mapped to the vehic lemodel-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 characteris tic colour: red ) have I sold in the last two months? A further advantage of mapping is that you can control flexibly 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 d elivered b y SAP in the standard system or create your own queries . Possible questions in this respect could be: ¡ How many vehi cles with which configuration characteris tics have I sold to dealer Smith? S uch a question provides valuab le data for a new sales forecast. ¡ Which dealers have I sold the most vehicl es to? ¡ From which vehic le model have I sold the most vehicles? ¡ How popular is air-conditioning, heating under the seats, and so on?

1.6.4 Connection to SAP SCEM Use This functionality can only be used in pilot projects and after discussion with SAP. SAP Sup ply Chain Event Management (SAP SCEM) allows you to define speci fic expec ted events for a busines s process , for exampl e a transp ort, or for a business object, for example a sales order, and define via rules which actions, for example a status change, should be linked to which event. At the same time you can define planned, baseline dates for the events. If the appropriate event is then confirmed with an actual time for this process or object, 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 c hain, refer to critical situations with alerts and be proactive by sending the appropriate messages. Technically sp eaking, SAP SCEM is part of SAP Supp ly Chain Management (SAP SCM) and cannot be installed separately. You can find further information in the SAP Help Portal under SAP Event Management. You can constantly monitor and log actions that you execute in VMS with reference to specific vehicles via the connection of VMS to SAP SCEM. This means that you can always provide your dealers with the latest information on process 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.

You can find further information in SAP Servic e Marketplace under service.sap.com\instguides ® mySAP SCM . · You have connected VMS to SAP SCEM. · You have impl emented BAdI VLC_USER_INTERFACE. This BAdI chec ks whether SAP SCEM has b een connected to VMS and cal ls the tracking data (see below). · You have activated the SCEM search views via BAdI VLC_S EARCH_PROFILE (see below). · You have set, for all SCEM-relevant actions, the S CEM Rel. indicator in Customizing for VMS under Control Data ® Define 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 appl ication object Vehicl e in VMS, whic h allows you to process confirmed events for this application object in SAP SCEM. · You have executed action EMMI. This action reports events for SAP SCEM.

Features · Displaying SCEM Information You call SCEM information for a vehicl e via transaction VELO, tab page Detail and then function following tab pages then appears: Tab Page

SCEM under Vehicl e Data . A screen with the

Description


Page 58 of 65

Expected Events

List of defined and expected events in SAP SCEM for the application object Vehicle with target and, where appropriate, actual scheduling. The target schedulin g 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 stati defined in SAP SCEM with the status values as they are, due to the events that h ave been reported for this vehicle.

· Searching for SC EM Information You have two more search views at your disposal in the vehicle search when you are searching for SCEM information: Search View

Description

Event Manager

Search for vehicles with SCEM parameters such as application object type, set of rules, status profile, profile of expected events, admin istrative data and transport data.

Messages and Status

Search for vehicles with a specific SCEM status or with specific event or error messages.

1.6.5 Connection to SAP CRM Use SAP Customer Relationship Management (SAP CRM) supp orts all customer-related process es within the entire Customer Relationship cycle form market segmentation, lead generation and opportunities through to after-sales and customer service. You can find further information in the SAP Help P ortal under mySAP Customer Relationship Management. If you connect VMS to CRM, you can transfer the vehicles that were created in VMS with all the appropriate data (vehicle data, configuration, vehicle history, relationships to dealers and end customers) via an interface to SAP CRM. There, they are mapped from SAP CRM to the individual objec t Vehicl e and are available for after-sales pr ocesses that are processed via the Interaction Center . Transferring vehicles to SAP CRM and mapp ing vehicles to individual objects takes plac e via actions CRMV Exp ort Vehicl e to CRM and CRMS Add Vehicle to CRM Order . You must make additional settings for mapp ing data in BAdI VLC_CRM_INTEGRATOR.

Prerequisites · You have installed SAP CRM 4.0 or higher.

You can find further information in SAP Servic e Marketplace under service.sap.com\instguides ® mySAP CRM . · You have connected VMS to SAP CRM. · So that BAdI VLC_CRM_ INTEGRATOR is cal led, you have set, for all CRM-relevant actions, the CRM Rel. indicator in Customizing for VMS under Control Data ® Define Actions. · You have deprogrammed BAdI VLC_CRM_INTEGRATOR. · You have transferred the VMS ales orders with vehic le reference to SAP CRM. You have transferred sales documents without a vehic le 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 vehic le data, configuration data and history entries such as relationship with dealer and end customer to SAP CRM. You have executed action CRMS Add Vehic le 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 specific 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 manufac turers or imp orters. It offers two interfaces (UIs): the IC WinClient and the IC WebClient. It supports the following processes: · · · · ·

Information inqui ry Service and supp ort Reclamation and compl aints management Sales of acces sories Marketing campaigns

You can find further information in the SAP Help P ortal under Interaction Center for Automotive.


Page 59 of 65

Exchange of Vehicle-Related Data Between VMS and SAP CRM Use You use this function to transfer vehicle data from the Vehicl e Management System in SAP D IMP to SAP CRM. By doing this you can, for examp le, reuse vehicl es and attributes that you have created in the Vehicl e Management System in the SAP CRM Interaction Center for the automotive industry sector. This means that you have detailed information about customers and their vehicles at your fingertips 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/S OAP and ALE/IDO C technology. This means that you can connect to both SAP and external ERP systems . For the Vehicl e Management System in SAP DIMP vehicles can also be transferred using the VMS adapter in the plug-in for CRM Middleware.

Prerequisites You have made the following settings: · Customizing settings in tables CRMCONSUM and CRMRFCPAR · Settings for system connections · Settings for SAP CRM Middleware You can find further information on these settings and Customizing in SAP Solution Manager under Basic Settings for mySA P CRM ® Data Replication ® Master Data Replication Between SAP R/3 and SAP CRM Server ® Replication of Materials ® [Automotive:] Set Up Data Exchange of Single Objects and in SAP note 665087.

Features Importing Vehicle Data from SAP DIMP to SAP CRM You can transfer the following Vehicl e Management System data from SAP D IMP to SAP CRM either by usi ng the SAP adapter or the XIF adapter: · · · · ·

Vehicl e (for exampl e, vehicl e ID, vehicle short text, model, year of manufacture) Vehicl e configuration (for examp le, colour, motor) Reference model for the vehicle Relationships vehi cle – busines s partner (for example, dealer, owner of vehicle) V ehicle history

Overview: Data Exchange Between SAP DIMP, External Systems and SAP CRM

Activities Initial Data Transfer 1. Make the app ropriate settings in SAP CRM Middleware. You can find further information on the required settings in the SAP Solution Manager . 2. Start the initial vehicle download in SAP CRM and load the following data to SAP CRM: ¡ Vehicl e with configuration ¡ Vehicl e history ¡ Relationships between vehicle and dealers/ end customers


Page 60 of 65

Delta Data Transfer (with the Vehicle Management System) 1. Start the data transfer in the Vehicl e Management System of SAP DIMP. 2. SAP CRM adopts the following updated data: ¡ New vehicles and their configuration ¡ Additional history records for vehicles ¡ Relationships between vehicle and dealers/ end customers

Connection to SAP Web AS with DIWI

We no longer recommend using the DIWI Dealer Portal, which is technically based on Bus iness Server Pages, b ut the new Dealer Portal. The new Dealer Portal is b ased on Web D ynpro for ABAP and can only b e accessed using the Enterprise Portal.

For more information ab out the Automotive D ealer P ortal, see: Business Package for Automotive Dealer Portal for Vehicle Management 1.4 Business Package for Automotive Dealer Portal for Spare Parts 1.4 Business Package for Automotive Dealer Portal for Warranty 1.4

Use SAP Web Ap pli cation Server (SAP Web AS ) is the technological enhancement and further development of the hitherto SAP Basis Sy stem and includes Internet capabilities as well as the SAP impl ementation model. With SAP Web AS, Internet applic ations can be p rogrammed or installed quickly and easily. You can find further information in the SAP Help Portal under SAP Web App lication Server. Disc rete Industries Web Interface (DIWI) supp orts sales and after-sales p rocesses at the vehic le 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.

You can find further information in SAP Servic e Marketplace under service.sap.com/instguides ® SAP Web Application Server . · You have installed DIWI 3.0 .

Features The VMS Internet interface in D IWI offers you the following functions: · · · · · · ·

Disp lay of vehicles at importer’s site Dis play of own dealer vehicles Creation of a virtual v ehicle p ool of vehicles from the manufacturer’s stock or also of own dealer stock Combined vehicl e search according to status, models and configurations Vehicl e configuration with SAP Internet Prici ng and Configurator (SAP IPC) Creation of customer’s indiv idual orders in the importer’s or dealer’s sy stem Transfer between dealers if the desired vehi cle is to be found in another dealer’s s tock and this dealer has defined the vehic le as not viewable for the other dealers · Maintenance of end customer data and saving of desired configurations for later purchase orders or for evaluating cus tomers’ wishes

Connection to SAP EP with BP for Automotive Channel Management Use SAP Enterpris e Portal (SAP EP) is an Internet platform on which sp ecific SA P content is offered in the form of bus iness p ackages . The Busines s Package for Automotive Channel Management provides an Internet-based channel solution for manufacturers, wholesalers or importers in the automotive industry with which they can support all the inter-enterprise processes involving the entire dealer network. This business package contains Discrete Industries Web Interface (DIWI) for VMS, Warranty Processi ng and Spare Parts Process ing; the latter is enhanced b y marketing functions from SAP Customer Relationship Management (SAP CRM). All ap pli cations have b een integrated to form one user-friendly interface – they therefore do not have to be called v ia separate URLs. The user only needs to ensure that an Internet browser has been installed.

Apart from these components, there is also an Internet interface for CRM-based further development of VMS in the business package.


Page 61 of 65

Prerequisites · You have installed SAP EP 5.0 or higher.

You can find further information in SAP Servic e Marketplace under service.sap.com\instguides ® SAP Enterprise Portal . · You have installed SAP CRM 4.0 or higher. · You have installed the Busines s Package for Automotive Channel Management as part of the Busines s Package for CRM 4.0 EP 50.1.

Features The VMS Internet interface in SAP EP Busines s Pack age for Automotive Channel Management offers the same functions as the VMS Internet interface in SAP Web AS with DIWI. You can find further information in the iView Studio under Business Pac kage for Automotive Channel Management .

1.7 Transaction Codes for VMS Customizing for VMS

Transaction Code

Description

Number Ranges

OVELO2

Define number ranges for internal vehicle number

OVELO3

Define number ranges for action control determination

OVELO8

Define number ranges for determination of configuration change profile

Other

OVELO19

Define VMS roles

OVELO7

Assign own dialog messages

Vehicle Search

OVELO27

Define sharing levels

OVELO18

Define vehi cle search areas

OVELOVSRINIT

Initialize category maintenance

OVELO20

Define vehicle categories

OVELO21

Assign roles and vehicle categories

OVELOTREX

Define fields for TREX download

OVELO29

Define search views

SES_ADMIN

Search Engine Service: Administration

Control D ata

OVELO1

Define actions

OVELO12

Define vehicle status

OVELO5

Define external status

OVELO13

Determine availability

OVELOL

Define vehicle locations

OVELO14

Define vehicle usage

OVELO11

Define action controls and actions m atrices

OVELO00

Define global VMS parameters

OVELO30

Define calculation sheet profile

Message Determination

OVELOM04

Define field catalog for messages

OVELOM01

Maintain condition tables

OVELOM11

Define access sequences

OVELOM21

Define message types

OVELOM31

Define message determination schema/procedure

OVELOM41

Assign message determination schema/procedure to plant

Enhancements

OVELO6

Enter technical data for actions


Page 62 of 65

OVELO4

Define additional data for vehicle

Master Data

Transaction Code

Description

Material Master Record

MM01, MM02

Create and change material m aster records for vehicle m odels

Class ification System, Var iant Configuration

CT04

Create and change vehicle characteristics with characteristic values

CL04

Create, change classes

CU50 and CL30N

Group characteristics on interface

CU41, CU42

Create, change configuration profiles

CU01, CU02

Create, change relations hip and object dependencies

Pricing

VK11, VK12

Create and change variant conditions i n SD

MEK1, MEK2

Create and change variant conditions i n MM

Business P artner

XK01, XK02

Create, change vendor (creditor) centrally

XD01, XD02

Create, change customer (debtor) centrally

Vehicle Management System (VMS) To find 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 profile

VELOUM

Define used-vehicle models

VELOMNR

Models with user-defined number ranges

VELONR

Define number ranges for vehicle models

VELOCM

Configuration mapping

VELOMMAP

Assign vehicles to characteristics of used-vehicle configuration

Basic Data

VELORM

Assign vehicle models to VMS role

VELORO

Assign organizational data to VMS role

VELORU

Assign VMS roles to user

VELOS

Define action control determi nation

VELOC

Define sales campaigns

VELOP

Define configuration change profiles

VELOPR

Analyze configuration change profiles

VELOOBJC

Add object characteristics to a configuration

VELOK VELOBWC

Define message condition records Assign class characteristics to BW characteristics

Reports for Admin istrators

VELOV

Define variants for actions i n batch

VELOB

Perform actions i n 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)


Page 63 of 65

VELOP03

Log: action execution in Vehicle Manager (not in menu)

SLG2

Application log: delete expired logs (not in menu)

VELOARSL

Set/delete archivin g in dicator

VELOARDI

Display archived vehicles

Business Add-Ins (BAdIs) for VMS Business Add-In (BAdI)

Description

Layout

VMS_USER_INTERFACE

Influence Interface of Transaction VELO

VLC_DETAIL_CONFIG

Exchange Configuration Screen in Vehicle Detail

VLC_DETAIL_DEALER

Exchange Dealer Data Screen in Vehicle Detail

VLC_DETAIL_ENDCUST

Exchange End Customer Screen in Vehicle Detail

VLC_DETAIL_HISTORY

Exchange History Screen in Vehicle Detail

VLC_DETAIL_OVERVIEW

Exchange Vehicle Data Screen in Vehicle Detail

Vehicle Search

VLC_MODELLIST_NO_FIL

Adjust Model List (Without Filter)

VLC_VHVIN_PREPARE

Capitalization of VIN

VLC_SEARCH_INTERFACE

Adjust Search Interface

VLC_SEARCH_PROFILE

Search Profile for Vehicle Search

VLC_SEARCH_ADAPTION

Vehicle Search

VLC_EXTSE_SEARCH

Vehicle Search Via External Search Machine

VLC_SE_DELTA_LOAD

Delta Load into External Search Machine

VLC_PRESELECTION

Pre-selection of Vehicle Models

Vehicle Configuration

VLC_FILT_DISP_CONFIG

Filter for Display of Vehicle Configuration

VLC_CHECK_CONFIG

Configuration Check Before Save

VLC_CONFIG_SPLITTER

Split Configuration Data

VLC_SCE_PARAMETERS

Call IPC

VLC_DETERM_CHPROFILE

Determination of Configuration Change Profile

VLC_USED_VEHICLES

Used Vehicles

VLC_CALL_CONFIG

Connection to External Configurator

VLC_ IPC_SEL ECT

Select between IPC 4.0 and IPC 7.0

Actions

VLC_PREPARE_ACTION

Preparation of Actions

VLC_EXPAND_VLCDIAVEHI

Enhancement of Vehicle Data

VLC_EXPND_VLCDISP_SD

Enhancement of Sales Document Table

VLC_EXECUTE_ACTION

Execution of Actions

VLC_DETERMINE_CONTRL

Determination of Action Control

VLC_RESERVATION

Determination of Reservation Period

VLC_BATCH_ACTION

Execution of Actions in Batch

VLC_GET_VHCLE_NUMBER

Influence Internal Vehicle No. (VHCLE) When Creating Vehicles

VLC_EXECUTE_ASSIGNMT

Assignment of Vehicles to Sales Documents

VLC_CALCULATE_GPRICE

Calculation of Gross List Price

VLC_CTP_CHECK_DATA

Data Change Before Availability Check

VLC_HISTORY_CALL_TRA

Display Documents from Vehicle History

VLC_CUSTOMER_SERVICE

Service Processing for Vehicles

VLC_ORD1_EXECUTE

Execute Action ORD1 (Create Purchase Order)

VLC_MORD_EXECUTE

Execute Action MORD (Change Purchase Order)

VLC_CUOR_EXECUTE

Execute Action CUOR (Create Sales Order)

VLC_CHCO_EXECUTE

Execute Action CHCO (Change Sales Order)

VLC_DELI_EXECUTE

Execute Action DELI (Create Delivery)


Page 64 of 65

VMS.pdf

Recommend Documents