1 Master Data11

Master DataPDF download from SAP Help Portal:http://help.sap.com/saphelp_dbm800/helpdata/en/c3/bbfee1bc46472899fb204272c41c35/content.htm

Created on June 29, 2015

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

NoteThis 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 purposewithout the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SEand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable 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 expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 31

Table of content1 Master Data1.1 Vehicle Model1.1.1 Assignment of VMS Roles1.1.2 RFC Function Modules for Processing the Vehicle Model Master1.1.3 Definition of Options for Models and Vehicles1.2 Vehicle1.2.1 Vehicle Search1.2.1.1 Extended Vehicle Search1.2.2 Vehicle Printing1.2.3 Action Control During Vehicle Processing1.2.3.1 Determination of Action Control1.2.3.2 Execution of Vehicle Actions1.2.3.3 Details for Vehicle Actions1.2.3.3.1 Actions for Vehicle Procurement1.2.3.3.2 Actions for Vehicle Sales and Service1.2.3.3.3 Actions for Goods Movements1.2.3.3.4 Other Vehicle Actions1.2.3.3.5 Interlinked VMS Actions in DBM Vehicle Master1.2.4 RFC Function Modules for Processing the Vehicle Master1.2.5 RFC Function Modules for Processing Multiple Vehicle Masters1.2.6 Vehicle Life Cycle Management1.2.7 Vehicle Additional Costs1.2.8 Calculation of Stock Age1.3 Part1.3.1 Parts Master1.3.2 Creation of Material from Original Parts Master1.4 Storage Goods Manager1.5 HR Master Data for DBM1.6 Labor Value1.7 Package1.7.1 Package Maintenance1.7.2 Package Reporting1.7.3 Change Package Report1.8 Job ID1.9 Pricing Conditions1.10 Warranty Profile1.11 Warranty Catalog


Page 2 of 31

1 Master Data Master Data contains information that is stored on a long-term basis in the SAP system and can be incorporated into individual transactions. You use the following master data as the basis for the different business processes in Dealer Business Management, for example:

Vehicle ModelVehiclePartStorage good (see Storage Goods Manager)Employee (see HR Master Data for DBM)Labor ValuePackageJob IDPricing ConditionsWarranty Profile

You are required to create master data before you execute a transaction.

1.1 Vehicle Model The basic type of a vehicle of which there can be several variations. Vehicle models are defined in the SAP system as configurable materials with additionalmodel data. You can use the same material master record for several different vehicle models. You can use this object as a basis for creating vehicles. In the vehicle model master for a vehicle model, you enter information which is relevant for each vehicleof this model.

Vehicle Model as Copy Template for VehiclesWhen you create a vehicle, the system copies data from the vehicle model to the vehicle. If you change a vehicle model, the changes do not affect data alreadycopied from the vehicle model to a vehicle.There are optional fields, for example regarding fuel consumption, engine performance, and the number of doors. If this information is not the same for all vehiclesof a certain vehicle model, do not populate these fields. These fields are then empty when you create a vehicle based on this vehicle model.You can use the Business Add-In /DBM/BADI_VEHICLE_API to determine how data is copied from the vehicle model to a vehicle. The relevant methods areBEFORE_VEHICLE_SET and BEFORE_VEHICLE_SAVE.As vehicle model data is simply copied from the vehicle model to the vehicle, you can change the information copied in the vehicle master afterwards. Thismeans that values defined in the model master are proposed values.The fact that you can change values in the vehicle master, including those copied from model master can mean that the values in the vehicle master are not thesame as those in the model master. If you do not want to allow this situation, you can ensure that the values copied from model master to vehicle master cannot bechanged in the vehicle master. To do this, you must change the UI of vehicle master as described in SAP Note 900850.

Model CatalogIn DBM, vehicle models are grouped in model catalogs. You can, for example, define a model catalog for each vehicle brand.In Customizing, you can define model catalogs and also specify how the system determines model catalogs. In the standard system, the model catalog isassigned the combination of division and country, and is determined accordingly.When working in the vehicle model (transaction /DBM/VMODEL), usually the first step is to select the model catalog that you want to work with. If a certain usergenerally works on models of one model catalog, you can assign this model catalog to the user by using parameter ID /DBM/MCATALOG in the Parameters tabof the Maintain User Profile screen (transaction SU3).

Model DataThis section of the vehicle model contains the general data that describes the vehicle model.In DBM, the Model Sales Code is the key for a vehicle model. You use the model sales code when you enter a vehicle model somewhere in the application. TheLabor Value Main Type is used to determine the correct labor value target time for labor values.

The Pricing Group can be used for vehicle-related pricing.You can define some values, for example Body Type and Fuel Type in Customizing for Dealer Business Management (DBM) under Vehicle GeneralData .Most of the data entered in this section does not influence the business process but serves information purposes only.If a model is not required any more or is not needed yet, you can set it to Inactive by using the corresponding flag in vehicle model master.In the standard setup, the Model Service Code is used for package determination.

Model TextsModel texts are language dependent texts and long texts that describe the vehicle model.To switch languages, enter another language in the Language field. You can then edit the model texts in the language selected.On the model master screen, in Edit Vehicle Model Master (transaction /DBM/VMODEL), you can display the model texts that were entered when the modelwas created. The model descriptions corresponding to the reference material of the model catalog is not displayed in the model master.


Page 3 of 31

Model PricesThe model purchase price and the model sales price are the base prices for the vehicle model. When you create a vehicle sales order or a vehicle salesquotation for a vehicle of pricing type 1, the system copies these prices from the vehicle master to the vehicle item within the DBM order document.The model prices do not contain the prices for additional vehicle features. The feature prices can be maintained separately for each feature key.The model prices are only relevant when price type 1 (New Vehicles) applies for the vehicles business transaction type. For more information, see Customizingfor Dealer Business Management (DBM) under Vehicle Vehicle Master Define Business Transaction Type .

Material DataEach vehicle model must be assigned to a material master record. The material master must be a configurable material.When creating a vehicle model, you can assign an existing material master record to the vehicle model.Alternatively, you can create a new material master record for the vehicle model. This only works if an appropriate material master record is already assigned tothe model catalog to which the vehicle model will belong to as vehicle reference material. The reason for this is that in the vehicle model master, hardly anymaterial master data can be provided so that for a new material master, most data is copied from the vehicle reference material assigned to the model catalog.The material master used for vehicle models needs to fulfill certain prerequisites. The most important are:

Use material type VEHI, or similarAssign a class of type 300 to the materialProvide sales organization data as well as purchasing dataIn the accounting 1 view, use valuation category X

The material assigned to the vehicle model is used to determine the vehicle action control in transaction VELOS. Therefore the lifecycle of the vehicle is influencedby the material it is assigned to.When you enter texts in the model master in the Model Text 1 field and descriptions for the template material for the selected model catalog, the materialdescription of the newly created material in the material master is affected as follows:

If you do not enter any text in a given language, the text in the language of the vehicle reference material is used for the descriptions of the new material inthe material master.When the selected language you use for the model text is not present in the description of the reference material, the text entered into the Model Text 1 fieldis added to the description of the new material in the material master.When the selected language you use for the model text is present in the description of the reference material, and you enter a text in the Model Text 1 field,the newly entered text is used for the description of the new material in material master.

For more information about the use of material master records in the vehicle model, see SAP Note 1258776.

FeaturesThe features, also called options, are mainly used to describe vehicles in more detail. In DBM, this functionality replaces the variant configuration.The features defined in model master are the features which are made available in vehicle master when you use the input help. The vehicle master does notcheck if the values you enter are contained in the list of predefined features in vehicle model master. This is based on the assumption that the vehicle modelmaster data cannot always be kept up to date so that vehicles with other features than those predefined in vehicle model master need to be created.The materials assigned to features are used for the creation of items in DBM vehicle orders and vehicle quotations.

Feature ClassesIn vehicle model master, there are several different features classes. The purposes and the usages within the application differ:

A AccessoriesAccessories are used for vehicle features which are typically handled by the dealer and not by the importer or manufacturer of the vehicle. Examplesinclude car mats or a rear spoiler. These are relevant for stock keeping. Therefore the usage of materials of type HAWA is recommended.C ColorThe exterior color of the vehicle. As the exterior color is part of the vehicle itself, materials of type NLAG are recommended.D Outbound DeliveryThis feature class can be used to define the different types of vehicle delivery to the end customer (for example collect at the dealership, collect at themanufacturing plant, and so on), as well as the cost for each type. For materials, use material type NLAG.I UpholsteryThe upholstery of the vehicle. As the upholstery is part of the vehicle itself, materials of type NLAG are recommended.M OtherFeature class M does not have a purpose in the standard implementation. You can use it for your own features class.O Optional ExtrasThe set of optional extras that can be ordered with a vehicle of a particular model. There can be optional extras which are mutually exclusive, for exampledifferent radio systems, but also optional extras which can be combined such as a sun roof and front fog lights. As optional extras are provided by theimporter or manufacturer, use material type NLAG.S Standard FeaturesSimilar to optional extras, the standard features are provided by the importer or manufacturer of the vehicle. Therefore the material type is NLAG. Unlikeoptional extras, the standard features are not selected by the user, but are always part of the vehicle. Standard features are for informative purposes onlyand usually do not have a price.U Missing Handover ArticlesMissing handover items are relevant for the used vehicle procurement process only. On the model master level, you can define which handover articles areexpected when a vehicle of a certain model is traded in, for example the warning triangle or the spare wheel. Details are described in the used vehicletrade-in process description.

Feature CategoriesFeature categories can be used to further group different features within a feature class, for example to distinguish between metallic colors and non-metallic colorswithin the feature class Colors .If there is no requirement to use feature categories, just define one feature category for each feature class.


Page 4 of 31

Enhancement ConceptYou can enhance the vehicle model master with additional fields. For more information, see SAP Note 929089.The following Business Add-Ins (BAdIs) are available:

Control Vehicle Model Master APIsControl Vehicle Model Master UIs

NoteYou can use various function modules to adapt the vehicle models and use functions for the vehicle models. For more information about function modules, seeCustomizing for Dealer Business Management (DBM) under RFC Interfaces Function Modules RFC Vehicle Model .

1.1.1 Assignment of VMS Roles This function enables you to define, on the basis of a role concept, that each user in Dealer Business Management (DBM) can edit only the vehicle model thathas been assigned to them explicitly on the basis of a role with vehicle models.

PrerequisitesIn Customizing for Vehicle Management System (VMS), you have created each of the VMS roles with key and description by choosing Define VMS Roles .

FeaturesDBM differentiates between the following VMS roles:Vehicle Model RoleThis role is assigned vehicle models, that is, the vehicle model role specifies which vehicle models the system displays in the vehicle model list for the assigneduser. A vehicle model can be assigned to more than one vehicle model role using transaction VELORM.Organizational RoleIf you wish to use category management during the vehicle search, assign vehicle categories to the organizational role in Customizing for VMS under VehicleSearch Vehicle Search Areas Assign Roles and Vehicle Categories . You can find further information on the use of category management in Customizingunder Logistics Execution Vehicle Management System (VMS) Vehicle Search Vehicle Search Areas .

ActivitiesAssign the vehicle model roles to vehicle models (transaction VELORM - Assign Vehicle Model).Assign one or more vehicle model roles to each user and, if you wish, also an organizational role (transaction VELORU - Assign User Roles).

1.1.2 RFC Function Modules for Processing the Vehicle ModelMaster The following table contains an overview of the function modules that exist in the system for processing the vehicle model master:

RFC Function Module Short Description/DBM/VM21_RFC_ADDMODLT Creates long text for vehicle model/DBM/VM21_RFC_ADDOPTION Creates optional features for vehicle model/DBM/VM21_RFC_ADDOPTLT Creates long text for model optional features/DBM/VM21_RFC_ADDOPTTEXT Creates text for model optional features/DBM/VM21_RFC_ADDTEXT Creates text for vehicle model/DBM/VM21_RFC_CHANGE Updates all vehicle model data/DBM/VM21_RFC_CHECK Checks all vehicle model data/DBM/VM21_RFC_CREATE Creates all data for vehicle model/DBM/VM21_RFC_DELETE Deletes all vehicle model data/DBM/VM21_RFC_DELMODLT Deletes long text for vehicle model/DBM/VM21_RFC_DELOPTION Deletes optional features for vehicle model/DBM/VM21_RFC_DELOPTLT Deletes long text for model optional features/DBM/VM21_RFC_DELOPTTEXT Deletes text for model optional features/DBM/VM21_RFC_DELTEXT Deletes text for vehicle model/DBM/VM21_RFC_EXISTS Checks whether vehicle model exists/DBM/VM21_RFC_GETCAT Gets data for model catalog


Page 5 of 31

/DBM/VM21_RFC_GETCATTEXT Gets text for model catalog/DBM/VM21_RFC_GETDETAIL Gets all vehicle model data/DBM/VM21_RFC_GETLCID Determines model catalog ID/DBM/VM21_RFC_GETLIST Gets list of vehicle models/DBM/VM21_RFC_GETMODLT Gets long text for vehicle model/DBM/VM21_RFC_GETOPTION Gets optional features for vehicle model/DBM/VM21_RFC_GETOPTLT Gets long text for model optional features/DBM/VM21_RFC_GETOPTTEXT Gets text for model optional features/DBM/VM21_RFC_GETTEXT Gets text for vehicle model/DBM/VM21_RFC_UPDMODLT Updates long text for vehicle model/DBM/VM21_RFC_UPDOPTION Updates optional features for vehicle model/DBM/VM21_RFC_UPDOPTLT Updates long text for model optional features/DBM/VM21_RFC_UPDOPTTEXT Updates text for model optional features/DBM/VM21_RFC_UPDTEXT Updates text for vehicle model

NoteFor more information about the individual function modules, see transaction SE37 ( Function Builder ).

1.1.3 Definition of Options for Models and Vehicles You can use this function to define options for vehicles and models in a central table and provide them as input help in the master data of the models andvehicles. You can also use this table to import options from the OEM.

IntegrationYou can use this function in the Vehicle Sales Assistant (VSA) when adding a dealer fitted accessory to a quotation or an order (see Creating or ModifyingQuotations Within the Deal and Processing Orders in the Deal). To enable this, you flag the relevant options as dealer fitted accessories (DFAs) in the Edit Modeland Vehicle Options transaction.

ActivitiesTo define the options, on the SAP Easy Access screen choose Logistics Logistics Execution Dealer Business Management Master Data VehicleModel Edit Model and Vehicle Options (transaction /DBM/VM_OPT).

1.2 Vehicle An object in the SAP system that represents an individual vehicle. Technically, a DBM vehicle consists of the VMS vehicle object and the individual object.In Dealer Business Management (DBM), the vehicle can be either in the dealers stock and available as unsold and without any assignment to a customer, orassigned to a business partner or customer.For more information about the VMS vehicle, see component Vehicle Management System (IS-A-VMS) under Vehicle . For more information about individualobjects, see SAP Customer Relationship Management (CRM) under Individual Objects. You enter this object and its data in the vehicle master and use it for handling business processes in service and warranty as well as for vehicle sales. You canuse the vehicle search to help you do this.You can execute actions for a vehicle, such as Change Vehicle and Create Goods Receipt. The system always displays the actions that are possible for thecurrent vehicle status. For more information about vehicle actions that can be performed in DBM, see Details for Vehicle Actions.

NoteUsing various function modules, you can adapt the DBM vehicles and use functions for the DBM vehicles. For more information about function modules, seeCustomizing for Dealer Business Management (DBM) under RFC Interfaces Function Modules RFC DBM Vehicle .

StructureIn Customizing for DBM under Vehicle Vehicle Master Navigation in Vehicle Master (SAP GUI) , you can define which of the following data for theobject Vehicle is displayed:

Data Overview Here you can display all the important vehicle data in summarized form.When you enter the mileage for the vehicle in the vehicle order, the systemautomatically updates the data in the appropriate vehicle master record.

SAP Internal Technical Data The underlying technical DBM vehicle data for the VMS vehicle, the individual object,


Page 6 of 31

and the vehicle model are displayed here.This data helps SAP support find errors more easily.

VMS Vehicle History The actions carried out for the vehicle including date, time, primary status, andsecondary status are documented here. The vehicle history shows which user performedwhich action, at what time, and which status change resulted. You can display thedocument that is created from an action (see Action Control During Vehicle Processingand Execution of Vehicle Actions).

VMS General Data Important vehicle data, such as vehicle identification number (VIN), availability, vehiclelocation, and primary and secondary status, is displayed here.

VMS Qualifier You can store additional data that is neither checked nor subject to any particular logic, forexample, the name of the forwarding agent.For more information about additional data, see Customizing for Logistics Executionunder Vehicle Management System (IS-A-VMS) Enhancements DefineAdditional Data for Vehicle .

Model Data Important vehicle model data is entered here such as the sales code and service code forthe vehicle. The system copies the model data from the vehicle model. This data can bechanged for the vehicle.

Vehicle Data You can enter important additional vehicle data mainly for service such as the labor valuemain type and price group, for example. For a vehicle or service order, the system copiesthe price group from the vehicle data.

Partners You can assign customers appropriate partner functions. When you assign a customer tothe vehicle, the system assigns this customer as sold-to party. The system assignsfurther partner functions with standard partner determination functions that are triggeredby the action Assign Customer. Furthermore, you can add or remove partnersmanually.When you create an order for a vehicle, the system copies the partner data defined for thevehicle as default values in the order.The Owner and Driver partner functions are relevant for the vehicle. The driverinformation is required if there is a different driver for the vehicle than the customer. Youcan use this function, for example, for fleet customers. The system determines theOwner information based on the billing document. The owner is the legal owner of the

vehicle.Registration Here you can enter registration data such as the type and date of vehicle registration, for

example. The system updates the mileage and the owner.When you create an order for the vehicle, the system copies the license plate numberand the mileage of the current entry to the order header. You can overwrite the mileage inthe order.

Warranty You can define warranty conditions for the vehicle. If you create a vehicle, the systemcopies the valid warranty conditions according to country, division, and vehicle model,which you can later change. The system displays the warranty data in the order for thevehicle.

Options You can assign features to the vehicle, which you can group into features classes andfeatures categories.The system copies the standard features from the vehicle model. You can add furtherfeatures classes in the vehicle master record. To do this, you can use the input help thatstems from the entries made in the vehicle model, or enter other features keys.When you create a vehicle quotation or a vehicle order, the system copies the vehicle andthe features with the appropriate prices as items to the order.

Keys You can enter additional keys for the vehicle, for example the radio code, the number ofthe title of auto, and the number of the vehicle key.You can define the key types in Customizing for DBM under Vehicle GeneralData Define Key Type .

Planned Maintenance Intervals You can define maintenance and service intervals, for example, for M.O.T. tests,exhaust emission tests and general inspections.The system displays this data in the order for the vehicle. When you enter or change themaintenance and service intervals for the vehicle in the vehicle order, the standardsystem automatically updates the data in the appropriate vehicle master record.You can define the service types in Customizing for DBM under Vehicle GeneralData Define Service Type .

Recalls The recall contains information about the technical fault and how to repair it (for example,what tasks the mechanic has to perform, which parts are required, and repairinstructions).

Texts Descriptive texts that can be assigned to and printed out with documents.Vehicle Change Document There is a standard functionality that allows you to track changes made on vehicle tables,

for example, who changed the value in the table, when, and what the previous valuewas. There are VMS change document functions for tables VLCVEHICLE ( VELO:Vehicle) and VLCADDDATA ( VELO: Qualifier Data for Vehicle) that are combinedwith the history data for the individual object.

Vehicle Prices Here you can enter the estimated and aimed purchasing and sales prices.Storage Goods Represents parts located in a warehouse, such as summer or winter tires.Service Contracts You can see all the service contracts and service items that are assigned to a vehicle. You

can also navigate directly to the service contracts created for this vehicle (see Display ofService Contracts in Vehicle Data).


Page 7 of 31

Deferred Work You can see all the orders with order type Service Deferred Work (2201) that exist for avehicle (see Order Processing for Additional Work and Deferred Work). You can alsonavigate directly to each order.

Additional Cost Overview The system displays details of additional costs assigned to the vehicle (see VehicleAdditional Costs).

Service History You can see a vehicles service history and navigate to each service order from thevehicle service history (see Vehicle Service History).

VMS Configuration You can see this view only if you enabled it by the VMS-DBM integration. In this case itdisplays the material configuration of the VMS vehicle. For more information, see EnableVMS Vehicle for DBM.

Financing/Leasing You can enter and update financing and leasing information. You must first make theappropriate settings in Customizing for Dealer Business Management under Vehicle General Data Define Financing and Leasing .

Condition You can specify data that describes the condition of the vehicle, for example if the paint isGood as New or Poor .

Additionally, you can see the latest vehicle damage report. If there is more than onevehicle damage report the system displays the latest one with its description text anditem overview.

Generic Options When you create a vehicle, the system determines the generic options based on thestandard features.You select generic options to specify for example the color type or the gearbox type for thevehicle. You can use the generic options in the extended vehicle search.First you have to make the appropriate settings on the SAP Easy Access screen under

Logistics Logistics Execution Dealer Business Management Master Data Vehicle Model Edit Generic Options for Features .

You can use individual objects to enhance the vehicle master with additional vehicle data, in other words, with new screens and new fields.

NoteIn the vehicle, you can use the Documents pushbutton to store documents Document Management System (DMS). In addition, you can see documents,which have been attached to the vehicle in the Vehicle Management System (VMS). In Customizing for DBM under Vehicle Business Add-Ins (BAdI)

you can change and filter VMS attachments in DBM with the Business Add-In BAdI: Change and Filter of VMS Attachments in DBMVehicle (/DBM/BADI_VEHICLE_ATTACHMENTS).For more information, see Enable VMS Vehicle for DBM.

The following Business Add-Ins (BAdIs) are available for the vehicle in Customizing for DBM under Vehicle Business Add-Ins (BAdIs) :Control Vehicle Search UIsControl Vehicle Master APIsChange and Filter of VMS Attachments in DBM VehicleControl Vehicle OrderControl Maintenance and Service Intervals for VehicleControl Vehicle Master UIsControl Vehicle Model Master APIsControl Vehicle Model Master UIsControl Vehicle Model Master UI DefaultsControl Reading of Control ValuesControl Vehicle Actions (VMS)Control Vehicle WarrantiesControl Replacement Vehicle SearchDependency Check for Multiple Vehicles

IntegrationIn order to create a vehicle in the standard system, you first have to create a vehicle model.You can use BAdI: Control Vehicle Master APIs (BAdI /DBM/VEHICLE_API) to copy default data from the vehicle model master to the vehicle master when youcreate a new vehicle. If you do not wish to use the default implementation of the BAdI, you can create a customer implementation.You can also create a vehicle without a vehicle model. If you want to do this, there must be a material in the material master for this purpose. When you create thevehicle, you have to enter the material instead of the model, or you can implement your own logic for material determination in BAdI: Control Vehicle Master APIs .If you create an order from the vehicle master, the vehicle data is copied to this order. To do this, implement BAdI: Control Vehicle Order(/DBM/VEHICLE_SALES).

1.2.1 Vehicle Search This function enables you to search your vehicle master for vehicles that fulfill specific criteria. To start the vehicle search in DBM, open Vehicle Search(transaction /DBM/VSEARCH). You can also find vehicles for processing an order, as this function is integrated into Order Processing (transaction/DBM/ORDER). Depending on the transaction, you can then do the following:

Display and change the vehicle data ( vehicle search )Display and change the orders created for the vehicle ( order processing )Create new orders for the vehicle ( order processing )


Page 8 of 31

IntegrationYou can use this search function in the vehicle master as well as in order processing. In order processing, the vehicle search is available on the OrderAcceptance tab and on the Order Search tab.

PrerequisitesYou have been assigned to a role with vehicle models as a minimum, and you have stored vehicle master records in the Vehicle Master (transaction/DBM/VM).

FeaturesThe following search options are available:

Full-text searchThe full-text search is available when you search for vehicles.You can choose between exact search and error-tolerant or fuzzy search.Attribute-based searchIf you are searching for vehicles, you can use the following search criteria, for example:

Vehicle identification numberLicense plate numberPrimary or secondary statusCustomerDivision (Brand)In order processing, you can search for the following three attributes:Vehicle identification numberLicense plate numberCustomerThe search for the internal vehicle number can also be performed without TREX.

If you enter multiple criteria, the vehicles must fulfill all of the criteria specified (AND operation); if both are available, you can combine full-text and attribute-basedsearches.In an overview, the system displays all of the vehicles found together with vehicle data. From this overview, depending on which transaction you are currentlyusing, you can either branch to the vehicle master record for the vehicle selected (vehicle search), or process an existing order or create a new order (orderprocessing). If the system finds only one vehicle when searching for vehicles, the relevant vehicle master record is displayed automatically.In category management, you can form categories, that is, groups of vehicles whose similarities are defined by certain rules. These rules are evaluated during thevehicle search. You can define exactly which vehicles you want to be displayed for which dealers. For further information, see component Vehicle ManagementSystem (VMS) under Vehicle Search Vehicle Search Areas Define Vehicle Categories .

NoteYou can use the Business Add-In BAdI: Control Vehicle Search UIs to adjust the user interface for the vehicle search.

In addition, you have the following options:Define, store, and delete selection variantsSelect a variant to enter into the search criteria fields on the vehicle search user interfaceDefine a selection variant as default

1.2.1.1 Extended Vehicle Search You can use this function for an advanced search. You can use vehicle attributes to search for a vehicle. If you do not know the features key for a vehicle model,you can use generic options such as color type. You can also use a model sales code to search for vehicles.

PrerequisitesIf you want to use the generic options in this function, you have executed the following settings:

You defined generic options in Customizing for Dealer Business Management (DBM) under Vehicle Vehicle Master Vehicle Search DefineGeneric Options with Groups .You have updated the vehicles. Before that, you have maintained the mapping table on the SAP Easy Access screen under Logistics LogisticsExecution Dealer Business Management Master Data Vehicle Model Edit Generic Options for Features . The report/DBM/R_UPD_VEH_OPTIONS automatically updates the vehicles according to the mapping table. The report updates the generic options data in everydependent vehicle. For example, if you created a new generic option Automatic Door Locking and assigned it to a vehicle model and the related vehiclefeatures, this report will set the generic option for all vehicles those have the same model sales code.

FeaturesThe extended vehicle search has three different parts:

Vehicle attributes:You can use the following vehicle attributes to search for vehicles:

Body Type


Page 9 of 31

Vehicle Make CodeModel Sales CodeModel YearEngine PerformanceNumber of Doors

Generic options:You can choose a generic option group, for example Color Type or Gearbox Type , and select the relevant generic options, for example Metallic orAutomatic Transmission .

OEM optionsYou can choose a model sales code. You can choose a features category and a features key for the model sales code. The system stores featurescategories and features key in the vehicle model master.

ActivitiesTo start the extended vehicle search, on the SAP Easy Access screen navigate to Logistics Logistics Execution Dealer Business Management Vehicle Processing Vehicle Search , and choose the Extended Vehicle Search tab.

NoteYou can use all three parts in the extended vehicle search simultaneously. You can also use the vehicle search and the extended vehicle search at the sametime. When you start the search, the system uses the search criteria from both tabs.

1.2.2 Vehicle Printing You can use this funtion to print for any vehicle, in any status, a data sheet that displays all information about the vehicle. The action Issue Messages (MSSO)uses SAP Smart Forms to print detailed information about the vehicle.

IntegrationVehicle printing is integrated into the actions of the transaction Vehicle Master .

PrerequisitesFor detailed information concerning system settings for vehicle printing, see SAP Note 1343359 and the attached cookbook in this SAP Note.

ActivitiesYou create a new vehicle with transaction Vehicle Master (/DBM/VM) and run the action Issue Messages (MSSO). After you run the action, the system printsa data sheet with the vehicle data.

1.2.3 Action Control During Vehicle Processing You can use this function to map your business processes. You define which vehicle actions can follow one after the other during vehicle processing and whichchanges to the status of the vehicle are involved in this.

ExampleA vehicle that the dealer creates in the system has the vehicle status Vehicle Created. Once the dealer has ordered the vehicle, that is, performed theOrder Vehicle action, the status of the vehicle changes automatically to Vehicle Ordered .

CautionYou can access an emergency report with transaction VELOE. DBM administrators can use this report to change the status of vehicles without action controlsbeing checked. This is only recommended for resolving data inconsistencies. You should not use this report under normal DBM business circumstances. Inother words, this report should be used with care.

PrerequisitesIn Customizing for Vehicle Management System (VMS), you have defined actions and the vehicle status under Control Data .

FeaturesYou can use the primary and secondary Action Control to map processes that are independent of each other, for example the Vehicle Procurement or VehicleSales processes.You can enhance the primary and secondary processes with different action controls. This means that processes can differ depending on the sales organization or


Page 10 of 31

vehicle model, for example.

ActivitiesIn Customizing for VMS , under Control Data Define Action Controls and Define Action Matrices , define the following:

1. Action controls that you require for your business processes during vehicle processing.2. An action grid, or matrix, for each action control

In this grid, you define which action is allowed for which vehicle status and to which status the action converts the vehicle. This enables you to map yourinternal business process, and ensures that users can only execute those actions for a vehicle that are permitted at the relevant vehicle status.

1.2.3.1 Determination of Action Control This process runs automatically in the system (according to the logic explained below) as soon as you perform a vehicle action. Primary and secondary actioncontrol can be determined individually and at the same time.

NoteYou can use the Business Add-In BAdI: Determination of Action Control in the Vehicle Management System (VMS) to define your own logic for thedetermination of action control.

PrerequisitesYou defined the action control settings in Customizing for VMS under Control .You stored the information required by the system for determining the action control in the application from the SAP Easy Access screen under Logistics Execution Vehicle Management System Basic Data Set Determination of Action Control (VELOS). You have entered the actioncontrols with which you want Dealer Business Management (DBM) to work for each vehicle model and, if necessary, for further organizational data. Thefollowing fields are key fields:

Vehicle modelPlant/LocationPurchasing org.SupplierSales org.Distr. channelDivisionCustomer

You can define different action controls for any combination of these fields. Mostly, however, it suffices to define an action control for each combinationof vehicle model and plant for primary action controls and for each sales organization for secondary action controls.You do not need to fill all of the key fields. A key field that is empty means that the entry is valid for all values that are possible for this field.

Process1. In Customizing, the system checks whether the action that you want to perform is a primary action, a secondary action, or both.2. The system checks whether the appropriate action controls have already been assigned to the vehicle. If this is the case, the system uses these.

NoteThe primary or secondary action control is assigned when the primary or secondary action is performed, respectively. If necessary, the new assignmentcan be subsequently triggered using the implementation of the method DETERMINE_CONTROL > FORCE_REDETERMINATION of the BAdIDetermination of Action Control .

3. If this is not the case, the system triggers determination of the action control and evaluates the entries in the table for the transaction Set Determination ofAction Control (VELOS). This takes place on the basis of the action data and existing vehicle data. The system carries out checks in the following order:

1. Does the table contain an entry that matches the transaction Set Determination of Action Control (VELOS)? If so, the system uses this entry.2. If no: Is there a generic entry that matches, that is, an entry for which fields are empty and therefore all existing values can be taken? If so, the

system uses this entry. If there is no generic entry or more than one entry that matches, and if the action controls in the entries are not identical, thesystem displays an error message.

ResultAs soon as the system has found a suitable action control, determination is ended. The system performs the desired action and sets the status that is stored in thesystem as the new status for this action in the action control.If the system does not find a suitable action control, it displays an error message and you have to correct the entries in the transaction Set Determination of ActionControl (VELOS) appropriately.

ExampleYou want to perform a primary action with the following action data: vehicle model Sprinter, plant 7777.No primary action control has been assigned to the vehicle model. This usually means that the vehicle model has just been created.The table does not contain any entries that exactly match transaction VELOS, in other words, it does not contain an entry for which only the fields Vehicle Model


Page 11 of 31

Sprinter and Plant 7777 are filled.However, there is an entry for vehicle model Sprinter, plant 7777, and vendor Opel . But this entry cannot be not found, since it includes a very specific vendorand the user has not entered a vendor.There is another entry for the vehicle model Sprinter for which only the vehicle model has been entered and no other fields have been filled. This entry is takensince the missing entry in the Plant field means that the entry is valid for all existing plants.The system always uses the most fitting entry from the table for transaction VELOS that matches the data specified.

1.2.3.2 Execution of Vehicle Actions This function enables you to control the business processes during vehicle processing. The execution of vehicle actions is defined on the basis of the action grids,or matrices, in which it is defined which action is linked with which vehicle status change. You can always execute actions for a selected vehicle.You can also create additional vehicle actions that meet branding, country-specific process requirements, or both by enhancing the basis of the matrices. SeeSAP note 903914.You can execute vehicle actions in the following ways:

Directly for the vehicleIn the vehicle master record, you can select one of the actions offered. Otherwise, an action is executed using the RFC module.Implicitly on the basis of the DBM orderVehicle actions can be triggered by means of order control.

NoteIn Customizing for DBM , you can define which action the system has to execute when an order of a certain order type is created and deleted orrejected by choosing Order Order Control Order Control VMS Extension Define Table of Criteria for Order Control - VMS Action Determination .

For example, the standard system executes action QCUO when a vehicle order (order type 3000 ) is created and action QDCO when it is deleted.

IntegrationAction Control for the Vehicle Management System (VMS) , which controls the actions for the DBM vehicle, and order control for Dealer Business Management(DBM) interact in the standard system as follows:As soon as a vehicle is used in a DBM order, the order control takes over control of the next step such as goods issue or invoice creation.At the same time, the order control also triggers vehicle actions, which ensure that the system updates the vehicle history accordingly and that the links to variousdocuments generated in the background are saved.You can change the Customizing settings in such a way that VMS action control influences and also controls the order process.

RecommendationDue to the complex process modeling, you are advised to do this only if your business processes urgently require so.

So that the vehicle actions can be executed, the following settings must be made:The vehicle actions must be permitted in the action grid in Customizing for VMS by choosing Control Data Define Action Controls and Define ActionMatrices .Vehicle actions that do not appear as actions in the vehicle master and that should be executable only using the DBM order are identified as internalactions in Customizing for VMS under Control Data Define Actions .The vehicle actions must be made known to DBM by means of control values in Customizing for DBM under Vehicle Enter Control Value .

PrerequisitesYou have defined the following in Customizing for VMS under Control Data :

ActionsAt least one action controlVehicle statusOne action grid for each action control

FeaturesYou can control every action with authorizations (authorization object C_AUTO_VMS). This means, for example, that you can configure DBM in such a waythat you, as management, are authorized to perform all actions, but your employees only specific actions.In the vehicle master record, you can only choose those actions that are possible for the current vehicle status in accordance with the action grid. Thesystem does not display the other actions.If the system executes an action, this can result in a change in the status of the vehicle, depending on the definition in Customizing. A primary actioninfluences the primary status, a secondary action the secondary status.In the vehicle master record under VMS Vehicle History , you can track the actions that have already been executed with primary and secondary statuses.A whole host of actions are delivered with the standard system. In Customizing, however, you can change these actions or define and program your ownactions.The standard actions can be assigned to the following business processes:

Vehicle procurementVehicle sales and service


Page 12 of 31

Goods movementsOther vehicle actions

Business Add-Ins (BAdIs) are available for the most important actions in the standard SAP system. You can use these BAdIs to adapt the EXECUTEmodules for the actions to suit your own specific requirements.

CautionThe execution of interlinking actions in DBM is very critical. For this reason, it is not necessarily advisable to use these actions. Since the VMS itselfexecutes a COMMIT for interlinked actions, the DBM order control no longer controls the COMMIT.Instead of using interlinking actions, you can write an action whose EXECUTE module performs two actions in one logical processing unit (LUW). Notethat not all Business APIs in the standard SAP system can be executed in an LUW. For example, a purchase order with goods receipt cannot becreated in an LUW.

For more information about the vehicle actions that can be executed in DBM, see Details for the Vehicle Actions.

ExampleVehicle History

Action Primary Status Secondary StatusCreate vehicle with internal order Vehicle createdOrder vehicle Vehicle orderedCreate goods receipt Vehicle receivedAssign customer Vehicle received Customer assignedCreate vehicle order Vehicle received DBM order createdChange vehicle Vehicle received DBM order created

1.2.3.3 Details for Vehicle Actions The vehicle actions that can be performed for Dealer Business Management (DBM) are defined in Customizing for the Vehicle Management System (VMS) . Theactions in the standard system begin with Q . For the purposes of this documentation, these actions have been grouped together with a short description andcommentary.The actions can be assigned to the following business processes:

Vehicle ProcurementVehicle Sales and ServiceGoods MovementsOther Vehicle Actions

For further information on vehicle actions, see SAP Note 1038943 Vehicle Action Matrix Delivery Customizing Overview .

1.2.3.3.1 Actions for Vehicle Procurement The table below explains the vehicle actions that are relevant for the purchase order and incoming invoice:

Action Description Prerequisites Scope of Functions of Action NoteQORD Create Purchase Order (DBM) Vehicle to which you can assign

values, vendorCreates a purchase order for anexisting vehicleThe purchase order is required forposting the goods receipt so thatthe system can post the vehicle tothe car dealer's stock.

This purchase order is not sent tothe vehicle vendor because it doesnot contain any information aboutthe vehicle configuration (vehiclefeatures).The actual vehicle order isprocessed in a third-party systemsuch as a dealer portal.

QMOR Change Purchase Order (DBM) Purchase OrderGoods issue should not havebeen posted

Changes the delivery date ofpurchase order itemsPerforms pricing againDeletes the item from thepurchase order

QDOR Delete Purchase Order (DBM) Purchase OrderGoods issue should not havebeen posted

Deletes the entire purchase order

QINV Create Incoming Invoice (DBM) Purchase OrderThe goods receipt must have beenposted for goods-receipt-basedinvoice verification

Enters the incoming invoicemanuallyThe system takes currency andpayment conditions from thepurchase order or purchasing inforecord

There can only be one purchaseorder without an incoming invoicefor a vehicle. If there is more thanone, the incoming invoice for themost recent purchase order isposted automatically.You cannot create incominginvoices for one-time vendors with


Page 13 of 31

this action.QIIR Cancel Incoming Invoice (DBM) Incoming invoice Creates a cancellation document

for the incoming invoice

The table below explains the vehicle actions that are relevant for used-vehicle purchasing:

Action Description Prerequisites Scope of Functions of Action NoteQCRE Create Vehicle with Internal

Order (DBM)Creates a vehicleYou define the vehicle as usedwith business transaction USC:Used Vehicle.

The internal order for the vehiclecontrols all following internalcosts, such as refurbishments orrevaluation.

QCRV Create Vehicle This interlinking action creates avehicle (action QCRE) and aninternal order group (actionQIOG).

QMOD Change Vehicle (DBM) Vehicle Changes the vehicle, for example,when you determine the price ofthe used vehicle

QNTF Create Notification Vehicle Creates a notification for vehicledamageThe system executes this actionwhen you choose Notification inthe vehicle master and selectnotification type D3 (VehicleDamage Report).

QCHN Create Vehicle Chain Used VehicleNew Vehicle

Links the used vehicle to the newvehicle so that both vehicles areregarded as one businesstransaction with regard topurchase and salesThe vehicles are linked by oneinternal order group.

Usually when a dealer trades in aused vehicle during a salesprocess

QORD Create Purchase Order (DBM) Creates a purchase order for theused vehicle

QRPU Repurchase Used Vehicle For cases in which the vehiclealready existed in the system, thisaction is executed. It contains theactions QTIP PrepareRepurchase , QIOG GroupInternal Order , and QORDCreate Purchase Order (DBM) -

see below.QTIP Prepare Repurchase See Action QTIP: Prepare

Repurchase of Vehicle.QIOG Group Internal Order Creates an internal order group

into which the internal order of thevehicle is placed.

This action is part of vehiclecreation.

QORD Create Purchase Order (DBM)QGOR Create Goods Receipt (DBM) Creates a goods receipt for the

used vehicleQINV Create Incoming Invoice (DBM) Creates an incoming invoice The PO status changes to

invoiced.QRCR Change Vehicle into

Replacement CarVehicle master record Converts the vehicle to a

replacement one that cannot beinvolved in a sales process untilaction QRCC is executed

QRCC Turn Replacement Car intoNormal Vehicle

Vehicle master record Converts the replacement vehicleback into a normal one so that itcan be involved in a sales process

For more information, see Used-Vehicle Purchasing.

1.2.3.3.2 Actions for Vehicle Sales and Service The table below explains the vehicle actions that order control triggers as internal actions in a DBM vehicle order. The vehicle action can then cause the system toperform the following:

Check whether the order action is allowedChange the vehicle statusUpdate the vehicle history

These vehicle actions are relevant for the following sales documents in vehicle sales and service:Vehicle quotation


Page 14 of 31

Sales orderVehicle orderService quotationService orderCustomer billing document

Action Description Prerequisites Scope of Functions of Action NoteQOFF Create Quotation (DBM) The vehicle is assigned to the

customer (QACU).Is called if a vehicle quotation iscreatedIn the VMS document table,creates a link between the vehicleand vehicle quotationChanges the vehicle status

In Customizing for DBM ordertypes, it is determined for thequotation that this action has to beperformed when a quotation iscreated.

QDOF Delete Quotation (DBM) Quotation Is called if a vehicle quotation isdeleted or rejectedUpdates the vehicle from the order

QCSD Create Sales Order (DBM) Customer master record, vehicleorder

Is called if a sales order is createdfor the vehicleIn the VMS document table,creates a link between the vehicleand sales order

QDSD Cancel Sales Order (DBM) Sales order Is called if a sales order is deletedfor the vehicle

QCUO Create Vehicle Order (DBM) Vehicle master recordThe vehicle is assigned to thecustomer (QACU).

Is called if a vehicle order iscreatedIn the VMS document table,creates a link between the vehicleand vehicle order

QDCO Delete Vehicle Order (DBM) The vehicle order has not yet beencompleted.

Is called if a vehicle order isdeleted

QFOR Complete Vehicle Order (DBM) The outgoing invoice is created. Is called if a vehicle order iscompleted

QFOC Order Re-Open (Order CloseCancelled)

The vehicle status must be QS60( Sales Order Completed ) to beable to execute this action.

Updates the vehicle status fromQS60 ( Sales Order Completed )to QS50 ( Outgoing InvoiceCreated )Is executed in tandem with theorder actionORD_CLOSE_CANC ( CancelClose Order ) and is triggered bythe event BILLING_CANCEL( Cancel Last Billing Document )

This action is the counterpartto/reversal of action QFOR. It isexecuted only when the vehicleorder is completely closed, andsubsequently reopened.

QCSQ Create Service Quotation (DBM) Is called when a DBM servicequotation is created. It updates thevehicle history and checkswhether the status allows aservice quotation to be created.

QCSO Create Service Order (DBM) Vehicle master record Is called if a service order iscreated for the vehicleIn the VMS document table,creates a link between the vehicleand service order

QDSO Delete Service Order (DBM) Is called if a service order isdeleted for the vehicle

QOIV Create Customer BillingDocument (DBM)

Is called if a customer billingdocument is created for the vehicleorderIn the VMS document table,creates a link between the vehicleand customer billing document

QOIR Cancel Customer BillingDocument (DBM)

Customer billing document Is called if a customer billingdocument is canceled for thevehicleIn the VMS document table,creates a link between the vehicleand cancellation document

The following table explains the actions that are relevant for internal service orders with revaluation:

Action Description Prerequisites Scope of Functions of Action NoteQCPO CO Prod. Create (DBM) Creates a CO production order The counterpart to this action is

action QCPH (return).QCPH CO Prod. Create Returns (DBM) CO production order The counterpart to this action is

action QCPO.


Page 15 of 31

QCCP CO Prod. Cost Collection (DBM) CO production order For the internal service performed,posts the primary costs from thevehicle internal order to the COproduction order; and materialconsumption from the batch to theCO production order

The counterpart to this action isaction QCCH (return).

QCCH CO Prod. Cost CollectionReturns (DBM)

CO production order The counterpart to this action isaction QCCP.

QGRP CO Prod. Post Goods Receipt(DBM)

Posts the goods receipt from theCO production order to the batch

The counterpart to this action isaction QGRH (return).

QGRH CO Prod.Post Goods ReceiptReturn (DBM)

The counterpart to this action isaction QGRP.

QSEP CO Prod. Create Settlement(DBM)

Settles the CO production orderagainst the batch

The counterpart to this action isaction QSEH (return).

QSEH CO Prod. Create SettlementReturns (DBM)

The counterpart to this action isaction QSEP.

QCLP CO Prod. Close (DBM) Closes the CO production orderand sets the deletion flag

The counterpart to this action isaction QCLH (return).

QCLH CO Prod. Close Returns (DBM) The counterpart to this action isaction QCLP.

QCOS Check Balance of Internal OrderQLIO Complete Internal OrderQSVC CO Prod. Stock Value Change

(DBM)The counterpart to this action isaction QSVH (return).

QSVH CO Prod. Stock Value ChangeReturns (DBM)

The counterpart to this action isaction QSVC.

For more information, see Internal Service Value Increase.

1.2.3.3.3 Actions for Goods Movements The table below explains the vehicle actions that are relevant for goods receipt and goods issue:

Action Description Prerequisites Scope of Functions of Action NoteQGOR Create Goods Receipt (DBM) Purchase order Creates a material document for

the goods receipt with reference toa purchase order

There can only be one purchaseorder without goods receipt for avehicle. If there is more than one,the goods receipt for the mostrecent purchase order is postedautomatically.It cannot be posted to the salesorder stock.

QGRE Cancel Goods Receipt (DBM) Goods receipt Creates a cancellation documentfor the goods receipt document

QGIS Create Goods Issue (DBM) Vehicle master record, vehicleorder

Is called if a goods issue is createdin the vehicle order in order toupdate the vehicle history andstatus, for example

QGIR Cancel Goods Issue (DBM) Goods issue Is called if a goods issue iscanceled in the vehicle order inorder to update the vehicle historyand status, for example

It can be used only for goodsissues that have been created withthe action QGIS.

QGRP CO Prod. Post Goods Receipt(DBM)

CO production order, goods receipt Posts the goods receipt from theCO production order to the batch

Used, for example, for internalservice orders with revaluation

QGRH CO Prod. Goods Receipt Return(DBM)

CO production order, goods receipt Reverses the posting of the goodsreceipt from the CO productionorder

Used, for example, for internalservice orders with revaluation

The table below explains the vehicle actions that are relevant for vehicle returns:

Action Description Prerequisites Scope of Functions of Action NoteQROR Create Return Order Vehicle sales order Creates a vehicle returns orderQRGR Goods Movement for Vehicle

ReturnVehicleVehicle returns order

Creates a goods receipt for thevehicle return

QRBD Create Invoice for Vehicle Return Creates an invoice for the vehiclereturn

The following tables explain the vehicle actions that are relevant for vehicle transfer postings:Transfer Posting of Vehicle from Current Assets to Fixed Assets:


Page 16 of 31

Action Description Prerequisites Scope of Functions of Action NoteQCAS Create Fixed Asset for Vehicle

(DBM)VehicleAsset class, for example, assetclass 3100 for vehicles

Creates a fixed asset

QVTA Post Vehicle to Fixed Assets(DBM)

Posts the vehicle to the fixedassets

QVTD Create Fixed Asset and PostVehicle

Creates a fixed asset and posts thevehicle

You can combine actions QCASCreate Fixed Asset for Vehicle

(DBM) and QVTA Post Vehicleto Fixed Assets (DBM) in theinterlinking action QVTD CreateFixed Asset and Post Vehicle .

QATV Post Vehicle to Current Assets Posts the vehicle to the currentassets

For more information, see Transfer Posting of Vehicle from Current Assets to Fixed Assets.Transfer Posting of Vehicle Between Plants:

Action Description Prerequisites Scope of Functions of Action NoteQPGM Cross-Plant Goods Movement See: action QVTPQVTP Transfer Between Plants Vehicle

QuotationDBM sales order

Transfers a vehicle from one plantto another

This interlinking action containsthe following actions: QCIOCreate InternalOrder, QIOGGroup Internal Order, QCORCheck Settlement Rules,QROC Transfer Costs, QCCVBatch and Valuation Check,

QPGM Cross-Plant GoodsMovement, QLIO CompleteInternal Order.

QCIO Create Internal Order Vehicle master record Creates an internal order for avehicle

Internal orders are used to plan,collect, monitor and settle thecosts of specific operations andtasks performed within acompany.

QCOR Check Settlement Rules Vehicle master record Checks whether settlement rulesexist in the internal order

QROC Transfer Costs Vehicle master record Costs form the current internalorder are posted to the newinternal order; this takes place byline item reposting

QCCV Batch and Valuation Check Vehicle master record Creates a batch and a valuationtype for the vehicle if they do notexist in the specified plant

QOIA DBM Order - All BillingDocuments Cancelled

Vehicle master record, customermaster record

Resets the vehicle to a pre-invoicestatus

For more information, see Transfer Posting of Vehicle Between Plants.Transfer Posting Between Company Codes:

Action Description Prerequisites Scope of Functions of Action NoteQVTC Transfer Between Company

CodesThe vehicle to be transferred hasalready been sold from onecompany code to the other bymeans of a DBM vehicle order.

Transfers a vehicle from onecompany code to another companycode

This interlinking action containsthe following actions: QCOSCheck Balance of Internal Order,

QCIO Create Internal Order,QIOG Group Internal Order,QISV Initialize Vehicle Status

QISV Initialize Vehicle Status Vehicle master record Initializes the vehicle status after avehicle transfer between companycodes

For more information, see Transfer Posting of Vehicle Between Company Codes.

1.2.3.3.4 Other Vehicle Actions The table below explains the vehicle actions that are relevant for direct changes to vehicle data or customer assignment to the vehicle:

Action Description Prerequisite Scope of Functions of Action NoteMSSO Issue Messages Vehicle master record Prints detailed information about

the vehicleFor detailed information, seeVehicle Printing


Page 17 of 31

QCRE Create Vehicle with InternalOrder (DBM)

Configurable material Creates vehicle master record withinternal order and batchThe system assigns the internalvehicle number.

QMOD Change Vehicle (DBM) Vehicle master record Allows changes to vehicleattributes and qualifiersIs executed in the following cases:If vehicle data in the vehiclemaster record is changed, withouta different action having beenchosen explicitlyIf vehicle data in the DBM order ischanged, without one of thevehicle actions having beenperformed for vehicle sales andservice

You control the action inCustomizing for the VMS byselecting Enhancements Define Additional Data for Vehicle Assign Attributes to Actions

QNTF Create Notification Called to update the vehiclehistory each time a notification iscreated for a vehicle

You can change the notificationfrom the vehicle history

QVIN Change VIN (DBM) Vehicle master record Changes the vehicle identificationnumber (VIN)

You can assign each VIN onlyonce and should not makesubsequent changes unless thisis absolutely necessary. You canmake changes only if a VIN hasalready been saved for the vehicle.You can use this action to controlauthorization for changing the VINseparately. As a result, anyonewho changes the VIN can betraced in the vehicle history.

QSCR Scrap Vehicle (DBM) Vehicle master record Changes the vehicle statusQACU Assign Customer (DBM) Vehicle master record, customer

master recordAssigns a vehicle a customer andtriggers the partner determination

You can assign a vehicle only onecustomer. To change the customerassignment, you first have tocancel the customer assignment(QDCU).

QDCU Cancel Customer Assignment(DBM)

Vehicle master record, customermaster record

Cancels the assignment of acustomer to a vehicle

1.2.3.3.5 Interlinked VMS Actions in DBM Vehicle Master You can use this function to trigger a sequence of multiple elementary actions, to avoid executing each elementary action manually.

IntegrationInterlinked actions in DBM use the same functions as the Vehicle Management System (VMS), Warranty Processing (WTY) and Just-in-Time Processing(JIT).VMS interlinked actions are available in the transaction Vehicle Master (/DBM/VM).

NoteYou must not use VMS interlinked actions in the DBM order. Instead, you should use the options provided in Customizing for Dealer BusinessManagement (DBM) under Order Order Control . In other words, do not use interlinked VMS actions in these Customizing settings.

VMS interlinked actions are integrated in the DBM vehicle APIs, and thus also in the corresponding vehicle RFC functions.

FeaturesVMS interlinked actions consist of more than one elementary action. When the system executes an interlinked action, it starts the elementary actionscontained in the interlinked action one after the other in exactly the same sequence that is defined in the interlinked action.You can update the individual object data of a DBM vehicle from a VMS action.You can execute VMS interlinked actions from the DBM vehicle RFC functions in Customizing for Dealer Business Management (DBM) under InterfaceFramework Function Modules RFC DBM Vehicle .You can interlink elementary actions independently of whether they are primary or secondary actions. For example, you can interlink ORD1 ( CreatePurchase Order ; primary action) and CUOR ( Create Sales Order ; secondary action). It is not possible to interlink actions that are already interlinked.

ExampleThe interlinked action Execute Vehicle Procurement could consist of the following elementary actions:

Create purchase orderCreate goods receipt


Page 18 of 31

Receive incoming invoice

1.2.4 RFC Function Modules for Processing the Vehicle Master The following table contains an overview of the function modules that exist in the system for processing the vehicle master:

RFC Function Module Short Description/DBM/VM20_RFC_CHANGE Updates DBM vehicle data/DBM/VM20_RFC_CREATE Creates DBM vehicle/DBM/VM20_RFC_GETDETAIL Gets all DBM vehicle data/DBM/VM20_RFC_GETLIST Selects a list of DBM vehicles/DBM/VM20_RFC_DOACTION Executes action for DBM vehicle/DBM/VM20_RFC_REFRESH Initializes internal vehicle buffer


1.2.5 RFC Function Modules for Processing Multiple VehicleMasters You can use several function modules if you need to process a lot of vehicles in one step. This might be necessary in the following cases:

If you start new projects, you may need to migrate a lot of vehicle data from your old system to the DBM system.If you upgrade to a new release, and need to migrate a lot of vehicle data from your previous release to the new release.If you need to create a lot of vehicles in the system for your daily work.

The following table contains the function modules that exist in the system for processing multiple vehicle masters:

RFC Function Module Short Description/DBM/VM20_RFC_MULTI_CHANGE Change Multiple Vehicles/DBM/VM20_RFC_MULTI_CREATE Create Multiple Vehicles/DBM/VM20_RFC_MULTI_DOACTION Vehicle Actions for Multiple Vehicles/DBM/VM20_RFC_MULTI_GETDETAIL Get Vehicle Details for Multiple Vehicles


The following vehicle actions can handle multiple vehicles:QCRV (Create Vehicle)QMOD (Change Vehicle)

You can use Business Add-In BAdI: Dependency Check for Multiple Vehicles (/DBM/BADI_VEH_DEPEND_CHK) to implement a dependency check forvehicles. For more information, see Customizing for Dealer Business Management (DBM) under Vehicle Business Add-Ins BAdI: Dependency Checkfor Multiple Vehicles .

1.2.6 Vehicle Life Cycle Management You use this function to influence how the life cycle of a vehicle changes when you execute an action. When you create a vehicle, you specify a businesstransaction type. The business transaction type describes the vehicle with regard to the business process required and reflects the different vehicle salesscenarios and life cycle phases, such as new, owned by customer, used, or replacement car. During the vehicle's life cycle, the business transaction type mightchange, for example from New Vehicle to Used Vehicle .You can use the following business transaction types to cover phases of a vehicle life cycle:

NEC ( New Vehicle )A vehicle owned or to be owned by the dealer which should be sold as a new vehicleUSC ( Used Vehicle )A vehicle owned or to be owned by the dealer which should be sold as a used vehicleCUS ( Customer Vehicle )A vehicle that belongs to a customer. This can be either a vehicle which was never owned by the dealership and is only in the system because thedealership services the vehicle, or it is a vehicle that the dealership sold to a customer.RPL ( Replacement Vehicle )A vehicle that is used in the service process as replacement vehicle.

In Customizing for Dealer Business Management you can define additional business transaction types.Business transaction types are usually assigned to different valuation classes. You can specify how valuation data is handled for vehicles. This allows vehiclestock values to be posted to the same, or different, G/L accounts depending on the material type.


Page 19 of 31

IntegrationCertain business process steps for vehicle actions have been moved into the life cycle management so that you can control the behavior of these actions in thesystem. You see the vehicle actions in the Customizing for Logistics Execution under Dealer Business Management (DBM) Vehicle Vehicle Master Vehicle Life Cycle Management Define Life Cycle Control , where you link the vehicle actions to so-called vehicle life cycle acts.A vehicle life cycle act is not a complete or standalone vehicle action but part of a vehicle action. It can precede or follow the vehicle action to which it is linked. Alife cycle act can be considered as an encapsulated business process step such as creating an internal order, changing valuation class, changing businesstransaction type or even deleting sales organization data.The vehicle life cycle acts are never executed for their own sake. They are always assigned to a certain action and therefore to a certain step in the vehicle lifecycle.

PrerequisitesYou have made the settings in the following Customizing activities:

Logistics Execution Dealer Business Management (DBM) Vehicle Vehicle Master Vehicle Life Cycle Management Define Life CycleControl

Logistics Execution Dealer Business Management (DBM) Vehicle Vehicle Master Define Business Transaction Logistics Execution Dealer Business Management (DBM) Vehicle Vehicle Master Vehicle Control Define VMS Action Logistics Execution Vehicle Management System (VMS) Control Data Define Action Controls and Define Action Matrices

NoteFor the upgrade from DBM 6.00 to DBM 7.00 see SAP Note 1337722 regarding business transaction types.

FeaturesIn the following the most common changes of business transaction types and the relevant data changes in the system are explained. This reflects the standardsettings.Creation of VehicleIf you create a vehicle, you can only use one of the following business transaction types:

NEC ( New Vehicle )USC ( Used Vehicle )CUS ( Customer Vehicle ) (created in services)

You cannot create a replacement vehicle initially.New Vehicle to Customer VehicleThe business transaction type changes from new vehicle to customer vehicle at the end of the sales process (for example at outbound delivery creation time).And from now on the vehicle is in its service life cycle. The system performs the following data changes:

Change business transaction type from NEC to CUSNew Vehicle to Used VehicleAfter action QTIP ( Prepare Repurchase ) the system performs the following data changes:

Change business transaction type from NEC to USCChange the vehicle options to not purchase order relevantChange the vehicle options to not sales order relevantCreate new batch and valuation type if not available in trade-in plantCreate new CO internal orderDelete vendor/supplierDelete customer/debitorDelete sales organizationDelete distribution channelDelete sales dateDelete vehicle partners

Customer Vehicle to Used VehicleThe business transaction type changes from customer vehicle to used vehicle, when a used vehicle is bought from a customer (before the purchase order iscreated). The system performs the following data changes:

Change business transaction type from CUS to USCCreate new batch and valuation typeCreate new CO internal orderDelete vendorDelete debitorDelete sales organizationDelete distribution channelDelete sales dateDelete partnerDelete margin taxation indicator

Used Vehicle to Customer VehicleThe business transaction type changes from used vehicle to customer vehicle, when a used vehicle is sold to a customer (for example at goods issue time). Thesystem performs the following data changes:

Change business transaction type from USC to CUS


Page 20 of 31

New Vehicle to Replacement VehicleWhen a dealer is purchasing a new vehicle and is using it as replacement vehicle (the vehicle is not primarily for sales) the business transaction type changesto replacement vehicle. The system performs the following data changes:

Change business transaction type from NEC to RPLReplacement Vehicle to Used VehicleWhen a dealer stops the usage of a vehicle as replacement vehicle, for example because the vehicle is for sale now, the vehicle changes to a used vehicle. Thesystem performs the following data changes:

Change business transaction type from RPL to USCDelete sales order relevance of options

ActivitiesIn the VMS Vehicle History view of the vehicle you can see the different phases in the vehicle life cycle grouped via the business transaction type. In thisoverview the system shows you which action took place in which business transaction type of the vehicle.

ExampleDuring the vehicle life cycle the business transaction type can change as follows:

1. Initial -> NECA vehicle is created and purchased as a new vehicle by the dealer.

2. NEC -> RPLAfter the vehicle has arrived, the dealer decides to use the vehicle as a replacement car. It is not planned to sell the vehicle yet. The vehicle is transferredto asset management.

3. RPL -> USCAfter some time the vehicle should be sold. As the vehicle was used as a replacement car for some time, it is now a used vehicle.

4. USC -> CUSThe vehicle was sold. When it is invoiced and handed over, its service life cycle has started.

5. CUS -> USCSome years later, the vehicle is traded-in as a used vehicle again. It is prepared for sale again.

1.2.7 Vehicle Additional Costs You can use this function to monitor additional costs incurred on a vehicle by way of various external services availed. External services can include overheadssuch as warehousing, maintenance and cleaning, intra-plant vehicle transfers, and so on.This function allows the distribution of the additionally incurred costs among the internal orders of a set of vehicles. You can not only post additional costs to multiplevehicles at a time, but also cancel costs that have been posted already. Additionally, you can use the function to separately create purchase orders, goodsreceipts, and incoming invoices for the external services.In the vehicle sales process, this function helps in estimating the profitability of each vehicle being sold.

NoteYou can post or cancel additional vehicle costs only using the Mass Vehicle Processing transaction. Standard SAP ERP transactions (such as those usedfor purchase orders, goods receipts, and invoices) do not support posting or cancellation of additional vehicle costs.

PrerequisitesThe vehicles for which additional costs need to be posted are available in the system.You have defined the external service types for additional costs in Customizing under Logistics Execution Dealer Business Management (DBM) Vehicle General Data Define Categories for Additional Costs .

You can assign materials to various external service types in the master data, from the SAP Easy Access menu under Logistics LogisticsExecution Dealer Business Management Master Data Additional Costs Assign Material to Additional Cost Category . Note that you can assignonly non-stockable service materials to external service types.

FeaturesWhen each vehicle is created in the system, an internal order is also created for it automatically. Any additional costs incurred on the vehicle are assigned to itsinternal order.When you post additional costs against one or more vehicles, the system triggers the creation of purchase orders, goods receipts, and incoming invoices in asequential manner. Alternatively, you can generate the purchase orders, goods receipts, and incoming invoices separately.

ActivitiesPosting Additional Costs

1. In the SAP Easy Access menu, go to Logistics Logistics Execution Dealer Business Management Vehicle Processing Mass VehicleProcessing (or transaction /DBM/MASSACTIONS).

2. Search for the vehicles by entering the search criteria and choosing Vehicle Search .


Page 21 of 31

3. In the search results table, select one or more vehicles among which you want an additional cost to be distributed.4. Choose Possible Actions Post Additional Costs .5. In the dialog box that opens, enter the appropriate parameters, especially the service vendor, net amount, and tax amount. Choose Distribute .

The entered amount is distributed equally among the selected vehicles, which are displayed within the dialog box itself. You can manually change thedistributed amounts here, if required.You can additionally influence the distribution proportion by implementing the Business Add-In (BAdI) /DBM/BADI_VMASS_DISTRIBUTE_ADC.

6. Choose Post Additional Costs .The function distributes the entered cost among the selected vehicles as defined by you. If you had selected only one vehicle, the entered amount isassigned entirely to it.

7. At this point the system creates purchase orders, goods receipts, and incoming invoices sequentially for external services availed on the selected vehicles.Cancelling Additional CostsTo cancel additional costs that have been posted earlier, search for and select the vehicles as explained above, and choose Possible Actions CancelAdditional Cost . The system cancels the purchase orders, goods receipts, and incoming invoices sequentially.Creating Separate Purchase Orders, Goods Receipts, or Incoming Invoices

1. In the SAP Easy Access menu, go to Logistics Logistics Execution Dealer Business Management Vehicle Processing Mass VehicleProcessing (or transaction /DBM/MASSACTIONS).

2. Search for the required vehicles by entering the search criteria and choosing Vehicle Search .3. In the search results table, select one or more vehicles.4. Choose Possible Actions Create Pur. Order for External Service .

NoteYou can use the corresponding actions to create goods receipts or incoming invoices, as required.

5. In the dialog box that opens, enter the appropriate parameters. Choose Distribute .The entered amount is distributed equally among the selected vehicles, which are displayed within the dialog box itself. You can manually change thedistributed amounts here, if required.

NoteIf you have implemented the Business Add-In (BAdI) /DBM/BADI_VMASS_DISTRIBUTE_ADC, the system distributes the amount based upon theBAdI logic.

6. Choose Create Pur. Order for External Service (or other similar button, depending on the document you are creating).The system creates the documents for external services availed on the selected vehicles. If you had selected only one vehicle, the entered amount isassigned entirely to it.

To cancel the documents, select the vehicles as explained above, and choose Possible Actions Cancel Pur. Order for External Service (or other similarbutton, depending on the document you are cancelling).

NoteOnly one document (purchase order, goods receipt, or incoming invoice) can be cancelled at a time.If a purchase order, goods receipt, or incoming invoice is being separately created for a vehicle, you cannot post any more additional costs to thatvehicle until all three documents have been created; a similar constraint is applicable in the case of cancellation of additional costs.For example, if you have created only a purchase order for a vehicle, you cannot post any new additional costs to that vehicle until the goods receiptand incoming invoice too are created.

1.2.8 Calculation of Stock Age Stock age refers to the number of days that a vehicle has been part of stock at a plant. In the vehicle sales process, it is important to know the stock age ofvehicles so that appropriate steps can be taken regarding the stock situation. For example, knowing the stock age helps you plan until what date you can sell aparticular vehicle, whether it needs to be promoted with any special offers, or beyond what date it may be advisable to return it.These functions enable you to carry out stock age calculation for multiple vehicles simultaneously. These calculate and display the number of days that eachvehicle has been in stock. You can also define personalized selection variants to run the calculation on a regular basis.

PrerequisitesGoods receipt has been performed for the selected vehicles. That is to say, the selected vehicles are currently in stock.

FeaturesYou can calculate the stock age of one or more vehicles using any of the following ways:

From the Mass Vehicle Processing functionRunning the report /DBM/VEHI_STOCK_AGEING as a background jobRunning the Stock Ageing report (or /DBM/STOCKAGEING transaction)

ActivitiesTo calculate stock age from the Mass Vehicle Processing function, follow the steps below:

1. In the SAP Easy Access menu, choose Logistics Logistics Execution Dealer Business Management Vehicle Processing Mass


Page 22 of 31

Vehicle Processing . Alternatively, run transaction /DBM/MASSACTIONS.2. Search for vehicles that are currently in stock, that is to say, those for which goods receipt has been done.

You can save your selection criteria for future use by choosing the Selection Variant button.3. Choose Vehicle Search to run the search.4. In the search results, select one or more vehicles, and choose Possible Actions Determine Age of Vehicle .5. In the Report Up To field, enter the date up to which the stock age must be calculated; the current date is selected by default. Then choose

Determine Age of the Vehicle .6. The function calculates and displays the stock age in number of days. This figure, displayed in the Stock Age column for the selected vehicles, is

the difference in days between the goods receipt date and the date entered.To calculate stock age using the Stock Ageing report, follow the steps below:

1. In the SAP Easy Access menu, choose Logistics Logistics Execution Dealer Business Management Vehicle Processing StockAgeing . Alternatively, run transaction /DBM/STOCKAGEING.

2. Select the appropriate selection variant, as created in Mass Vehicle Processing .

NoteYou can create selection variants in the Mass Vehicle Processing function as described above.

In the Report Up To field, enter the date up to which the stock age must be calculated; the current date is selected by default. Then chooseExecute .

3. The report displays the stock age for vehicles selected in the variant. This figure, displayed in the Stock Age column for the selected vehicles, is thedifference in days between the goods receipt date and the date entered.

To calculate stock age by scheduling a batch job, run transaction SM36, then execute the report /DBM/VEHI_STOCK_AGEING in the background.

NoteYou cannot select a date here; the report automatically calculates the stock age up to the current system date.The selection variant created in Mass Vehicle Processing and the output list variant of the Stock Ageing report are used to generate the spoolin the batch job.

1.3 Part A material that can be installed in a vehicle. You create this object as a material master record. For order processing of services and parts, you can enter parts as order items in the order.For the item category in the order, the system distinguishes between the part entered in the material master and the manual part not entered in the material masterand that is used for a specific order only.You can use the search help to display existing parts. If you wish to restrict your search to deliver the most useful results, you can filter by using the materialgroup. You can do this by assigning valid material groups in Customizing for Dealer Business Management (DBM), in accordance with the OEM and itemcategory. The search help function can also be used to find entries in the original parts master.

NoteUsing various function modules, you can adapt the parts and use functions for the parts. For more information about function modules, see Customizing forDealer Business Management (DBM) under RFC Interfaces Function Modules RFC Original Part .

Structure

DBM-Specific TransactionsApart from the standard transactions for the material, DBM provides the following transactions to support your industry-specific tasks:

Create Material (/DBM/MM01)Change Material (/DBM/MM02)Display Material (/DBM/MM03)

You can use the following changes to the standard in the DBM-specific transactions:Additional data

Return part (part to be returned)Retention obligationSubject to disposalCheck for multiple entry of parts items in the order

Exchange parts processYou can assign a used p