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. Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. © 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. Table of content PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 1 of 31 Table of content 1 Master Data 1.1 Vehicle Model 1.1.1 Assignment of VMS Roles 1.1.2 RFC Function Modules for Processing the Vehicle Model Master 1.1.3 Definition of Options for Models and Vehicles 1.2 Vehicle 1.2.1 Vehicle Search 1.2.1.1 Extended Vehicle Search 1.2.2 Vehicle Printing 1.2.3 Action Control During Vehicle Processing 1.2.3.1 Determination of Action Control 1.2.3.2 Execution of Vehicle Actions 1.2.3.3 Details for Vehicle Actions 1.2.3.3.1 Actions for Vehicle Procurement 1.2.3.3.2 Actions for Vehicle Sales and Service 1.2.3.3.3 Actions for Goods Movements 1.2.3.3.4 Other Vehicle Actions 1.2.3.3.5 Interlinked VMS Actions in DBM Vehicle Master 1.2.4 RFC Function Modules for Processing the Vehicle Master 1.2.5 RFC Function Modules for Processing Multiple Vehicle Masters 1.2.6 Vehicle Life Cycle Management 1.2.7 Vehicle Additional Costs 1.2.8 Calculation of Stock Age 1.3 Part 1.3.1 Parts Master 1.3.2 Creation of Material from Original Parts Master 1.4 Storage Goods Manager 1.5 HR Master Data for DBM 1.6 Labor Value 1.7 Package 1.7.1 Package Maintenance 1.7.2 Package Reporting 1.7.3 Change Package Report 1.8 Job ID 1.9 Pricing Conditions 1.10 Warranty Profile 1.11 Warranty Catalog PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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 Model Vehicle Part Storage good (see Storage Goods Manager) Employee (see HR Master Data for DBM) Labor Value Package Job ID Pricing Conditions Warranty 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 additional model 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 vehicle of this model. Vehicle Model as Copy Template for Vehicles When 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 already copied 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 vehicles of 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 are BEFORE_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. This means 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 the same 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 be changed in the vehicle master. To do this, you must change the UI of vehicle master as described in SAP Note 900850. Model Catalog In 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 is assigned 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 user generally 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 tab of the Maintain User Profile screen (transaction SU3). Model Data This 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. The Labor 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 Data . Vehicle General 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 Texts Model 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 model was created. The model descriptions corresponding to the reference material of the model catalog is not displayed in the model master. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 3 of 31 Model Prices The 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 sales quotation 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 vehicle’s business transaction type. For more information, see Customizing for Dealer Business Management (DBM) under Vehicle Vehicle Master Define Business Transaction Type . Material Data Each 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 to the 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 any material 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 similar Assign a class of type 300 to the material Provide sales organization data as well as purchasing data In 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 influenced by 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 material description 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 in the 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 field is 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. Features The 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 not check 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 model master 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 Classes In vehicle model master, there are several different features classes. The purposes and the usages within the application differ: A – Accessories Accessories are used for vehicle features which are typically handled by the dealer and not by the importer or manufacturer of the vehicle. Examples include car mats or a rear spoiler. These are relevant for stock keeping. Therefore the usage of materials of type HAWA is recommended. C – Color The exterior color of the vehicle. As the exterior color is part of the vehicle itself, materials of type NLAG are recommended. D – Outbound Delivery This 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 the manufacturing plant, and so on), as well as the cost for each type. For materials, use material type NLAG. I – Upholstery The upholstery of the vehicle. As the upholstery is part of the vehicle itself, materials of type NLAG are recommended. M – Other Feature class M does not have a purpose in the standard implementation. You can use it for your own features class. O – Optional Extras The 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 example different 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 the importer or manufacturer, use material type NLAG. S – Standard Features Similar to optional extras, the standard features are provided by the importer or manufacturer of the vehicle. Therefore the material type is NLAG. Unlike optional extras, the standard features are not selected by the user, but are always part of the vehicle. Standard features are for informative purposes only and usually do not have a price. U – Missing Handover Articles Missing handover items are relevant for the used vehicle procurement process only. On the model master level, you can define which handover articles are expected 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 vehicle trade-in process description. Feature Categories Feature categories can be used to further group different features within a feature class, for example to distinguish between metallic colors and non-metallic colors within the feature class Colors . If there is no requirement to use feature categories, just define one feature category for each feature class. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 4 of 31 Enhancement Concept You 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 APIs Control Vehicle Model Master UIs Note You can use various function modules to adapt the vehicle models and use functions for the vehicle models. For more information about function modules, see Customizing 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 that has been assigned to them explicitly on the basis of a role with vehicle models. Prerequisites In Customizing for Vehicle Management System (VMS), you have created each of the VMS roles with key and description by choosing Define VMS Roles . Features DBM differentiates between the following VMS roles: Vehicle Model Role This 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 assigned user. A vehicle model can be assigned to more than one vehicle model role using transaction VELORM. Organizational Role If you wish to use category management during the vehicle search, assign vehicle categories to the organizational role in Customizing for VMS under Vehicle Search Vehicle Search Areas Assign Roles and Vehicle Categories . You can find further information on the use of category management in Customizing under Logistics Execution Vehicle Management System (VMS) Vehicle Search Vehicle Search Areas . Activities Assign 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 Model Master 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 PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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 Note For 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 and vehicles. You can also use this table to import options from the OEM. Integration You 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 Modifying Quotations 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 Model and Vehicle Options transaction. Activities To define the options, on the SAP Easy Access screen choose Logistics Model Edit Model and Vehicle Options (transaction /DBM/VM_OPT). Logistics Execution Dealer Business Management Master Data Vehicle 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 dealer’s stock and available as unsold and without any assignment to a customer, or assigned 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 individual objects, 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 can use 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 the current vehicle status. For more information about vehicle actions that can be performed in DBM, see Details for Vehicle Actions. Note Using various function modules, you can adapt the DBM vehicles and use functions for the DBM vehicles. For more information about function modules, see Customizing for Dealer Business Management (DBM) under RFC Interfaces Function Modules RFC DBM Vehicle . Structure In Customizing for DBM under object Vehicle is displayed: Data Overview Vehicle Vehicle Master Navigation in Vehicle Master (SAP GUI) , you can define which of the following data for the 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 system automatically 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, PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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, and secondary status are documented here. The vehicle history shows which user performed which action, at what time, and which status change resulted. You can display the document that is created from an action (see Action Control During Vehicle Processing and Execution of Vehicle Actions). VMS General Data Important vehicle data, such as vehicle identification number (VIN), availability, vehicle location, 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, for example, the name of the forwarding agent. For more information about additional data, see Customizing for Logistics Execution under Vehicle Management System (IS-A-VMS) Additional Data for Vehicle . Model Data Enhancements Define Important vehicle model data is entered here such as the sales code and service code for the vehicle. The system copies the model data from the vehicle model. This data can be changed for the vehicle. Vehicle Data You can enter important additional vehicle data mainly for service such as the labor value main type and price group, for example. For a vehicle or service order, the system copies the price group from the vehicle data. Partners You can assign customers appropriate partner functions. When you assign a customer to the vehicle, the system assigns this customer as sold-to party. The system assigns further partner functions with standard partner determination functions that are triggered by the action Assign Customer. Furthermore, you can add or remove partners manually. When you create an order for a vehicle, the system copies the partner data defined for the vehicle as default values in the order. The Owner and Driver partner functions are relevant for the vehicle. The driver information is required if there is a different driver for the vehicle than the customer. You can use this function, for example, for fleet customers. The system determines the Owner 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 number and the mileage of the current entry to the order header. You can overwrite the mileage in the order. Warranty You can define warranty conditions for the vehicle. If you create a vehicle, the system copies 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 the vehicle. Options You can assign features to the vehicle, which you can group into features classes and features categories. The system copies the standard features from the vehicle model. You can add further features classes in the vehicle master record. To do this, you can use the input help that stems 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 and the 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 of the title of auto, and the number of the vehicle key. You can define the key types in Customizing for DBM under Data Planned Maintenance Intervals Define Key Type Vehicle General . 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 the maintenance and service intervals for the vehicle in the vehicle order, the standard system automatically updates the data in the appropriate vehicle master record. You can define the service types in Customizing for DBM under Vehicle General Data Recalls Define Service Type . 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 repair instructions). 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 value was. There are VMS change document functions for tables VLCVEHICLE ( VELO: Vehicle) and VLCADDDATA ( VELO: Qualifier Data for Vehicle) that are combined with 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 of Service Contracts in Vehicle Data). PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 7 of 31 Deferred Work You can see all the orders with order type Service Deferred Work (2201) that exist for a vehicle (see Order Processing for Additional Work and Deferred Work). You can also navigate directly to each order. Additional Cost Overview The system displays details of additional costs assigned to the vehicle (see Vehicle Additional Costs). Service History You can see a vehicle’s service history and navigate to each service order from the vehicle 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 it displays the material configuration of the VMS vehicle. For more information, see Enable VMS Vehicle for DBM. Financing/Leasing You can enter and update financing and leasing information. You must first make the appropriate 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 is Good as New or Poor . Additionally, you can see the latest vehicle damage report. If there is more than one vehicle damage report the system displays the latest one with its description text and item overview. Generic Options When you create a vehicle, the system determines the generic options based on the standard features. You select generic options to specify for example the color type or the gearbox type for the vehicle. 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. Note In 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 DBM Vehicle (/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 UIs Control Vehicle Master APIs Change and Filter of VMS Attachments in DBM Vehicle Control Vehicle Order Control Maintenance and Service Intervals for Vehicle Control Vehicle Master UIs Control Vehicle Model Master APIs Control Vehicle Model Master UIs Control Vehicle Model Master UI Defaults Control Reading of Control Values Control Vehicle Actions (VMS) Control Vehicle Warranties Control Replacement Vehicle Search Dependency Check for Multiple Vehicles Integration In 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 you create 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 the vehicle, 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 ) PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 8 of 31 Integration You 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 Order Acceptance tab and on the Order Search tab. Prerequisites You 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). Features The following search options are available: Full-text search The full-text search is available when you search for vehicles. You can choose between exact search and error-tolerant or fuzzy search. Attribute-based search If you are searching for vehicles, you can use the following search criteria, for example: Vehicle identification number License plate number Primary or secondary status Customer Division (Brand) In order processing, you can search for the following three attributes: Vehicle identification number License plate number Customer The 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-based searches. In an overview, the system displays all of the vehicles found together with vehicle data. From this overview, depending on which transaction you are currently using, 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 (order processing). 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 the vehicle search. You can define exactly which vehicles you want to be displayed for which dealers. For further information, see component Vehicle Management System (VMS) under Vehicle Search Vehicle Search Areas Define Vehicle Categories . Note You 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 variants Select a variant to enter into the search criteria fields on the vehicle search user interface Define 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. Prerequisites If 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 Define Generic Options with Groups . You have updated the vehicles. Before that, you have maintained the mapping table on the SAP Easy Access screen under Logistics Logistics Execution 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 every dependent vehicle. For example, if you created a new generic option Automatic Door Locking and assigned it to a vehicle model and the related vehicle features, this report will set the generic option for all vehicles those have the same model sales code. Features The extended vehicle search has three different parts: Vehicle attributes: You can use the following vehicle attributes to search for vehicles: Body Type PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 9 of 31 Vehicle Make Code Model Sales Code Model Year Engine Performance Number 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 or Automatic Transmission . OEM options You can choose a model sales code. You can choose a features category and a features key for the model sales code. The system stores features categories and features key in the vehicle model master. Activities To start the extended vehicle search, on the SAP Easy Access screen navigate to Logistics Vehicle Processing Vehicle Search , and choose the Extended Vehicle Search tab. Logistics Execution Dealer Business Management Note You 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 same time. 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. Integration Vehicle printing is integrated into the actions of the transaction Vehicle Master . Prerequisites For detailed information concerning system settings for vehicle printing, see SAP Note 1343359 and the attached cookbook in this SAP Note. Activities You create a new vehicle with transaction Vehicle Master (/DBM/VM) and run the action Issue Messages (MSSO). After you run the action, the system prints a 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 which changes to the status of the vehicle are involved in this. Example A vehicle that the dealer creates in the system has the vehicle status Vehicle Created. Once the dealer has ordered the vehicle, that is, performed the Order Vehicle action, the status of the vehicle changes automatically to Vehicle Ordered . Caution You can access an emergency report with transaction VELOE. DBM administrators can use this report to change the status of vehicles without action controls being checked. This is only recommended for resolving data inconsistencies. You should not use this report under normal DBM business circumstances. In other words, this report should be used with care. Prerequisites In Customizing for Vehicle Management System (VMS), you have defined actions and the vehicle status under Control Data . Features You can use the primary and secondary Action Control to map processes that are independent of each other, for example the Vehicle Procurement or Vehicle Sales 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 PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 10 of 31 vehicle model, for example. Activities In 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 your internal 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 action control can be determined individually and at the same time. Note You can use the Business Add-In BAdI: Determination of Action Control in the Vehicle Management System (VMS) to define your own logic for the determination of action control. Prerequisites You 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 action controls with which you want Dealer Business Management (DBM) to work for each vehicle model and, if necessary, for further organizational data. The following fields are key fields: Vehicle model Plant/Location Purchasing org. Supplier Sales org. Distr. 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 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. Process 1. 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. Note The primary or secondary action control is assigned when the primary or secondary action is performed, respectively. If necessary, the new assignment can be subsequently triggered using the implementation of the method DETERMINE_CONTROL —> FORCE_REDETERMINATION of the BAdI Determination 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 of Action 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, the system displays an error message. Result As 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 the system 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 Action Control (VELOS) appropriately. Example You want to perform a primary action with the following action data: vehicle model Sprinter, plant 7777. No primary action control has been assigned to the vehicle 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 PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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 vendor and 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 taken since 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. See SAP note 903914. You can execute vehicle actions in the following ways: Directly for the vehicle In 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 order Vehicle actions can be triggered by means of order control. Note In 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 or rejected 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. Integration Action 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 various documents 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. Recommendation Due 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 Action Matrices . 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 internal actions 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 . Prerequisites You have defined the following in Customizing for VMS under Control Data : Actions At least one action control Vehicle status One action grid for each action control Features You can control every action with authorizations (authorization object C_AUTO_VMS). This means, for example, that you can configure DBM in such a way that 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. The system 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 action influences 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 own actions. The standard actions can be assigned to the following business processes: Vehicle procurement Vehicle sales and service PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 12 of 31 Goods movements Other 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 EXECUTE modules for the actions to suit your own specific requirements. Caution The execution of interlinking actions in DBM is very critical. For this reason, it is not necessarily advisable to use these actions. Since the VMS itself executes 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). Note that not all Business APIs in the standard SAP system can be executed in an LUW. For example, a purchase order with goods receipt cannot be created in an LUW. For more information about the vehicle actions that can be executed in DBM, see Details for the Vehicle Actions. Example Vehicle History Action Primary Status Create vehicle with internal order Vehicle created Secondary Status Order vehicle Vehicle ordered Create goods receipt Vehicle received Assign customer Vehicle received Customer assigned Create vehicle order Vehicle received DBM order created Change 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) . The actions in the standard system begin with Q . For the purposes of this documentation, these actions have been grouped together with a short description and commentary. The actions can be assigned to the following business processes: Vehicle Procurement Vehicle Sales and Service Goods Movements Other 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 QORD Description Create Purchase Order (DBM) Prerequisites Scope of Functions of Action Note Vehicle to which you can assign Creates a purchase order for an This purchase order is not sent to values, vendor existing vehicle The purchase order is required for posting the goods receipt so that the vehicle vendor because it does not contain any information about the vehicle configuration (vehicle the system can post the vehicle to features). the car dealer's stock. The actual vehicle order is processed in a third-party system such as a dealer portal. QMOR Change Purchase Order (DBM) Purchase Order Goods issue should not have been posted Changes the delivery date of purchase order items Performs pricing again Deletes the item from the purchase order QDOR Delete Purchase Order (DBM) Purchase Order Goods issue should not have been posted QINV Create Incoming Invoice (DBM) Purchase Order Enters the incoming invoice The goods receipt must have been manually There can only be one purchase order without an incoming invoice posted for goods-receipt-based invoice verification The system takes currency and payment conditions from the purchase order or purchasing info for a vehicle. If there is more than one, the incoming invoice for the most recent purchase order is record posted automatically. You cannot create incoming invoices for one-time vendors with PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Deletes the entire purchase order 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 QCRE Create Vehicle with Internal Order (DBM) QCRV Create Vehicle QMOD Change Vehicle (DBM) Prerequisites Scope of Functions of Action Note Creates a vehicle You define the vehicle as used The internal order for the vehicle controls all following internal with business transaction USC: Used Vehicle. costs, such as refurbishments or revaluation. This interlinking action creates a vehicle (action QCRE) and an internal order group (action QIOG). Vehicle Changes the vehicle, for example, when you determine the price of the used vehicle QNTF Create Notification Vehicle Creates a notification for vehicle damage The system executes this action when you choose Notification in the vehicle master and select notification type D3 (Vehicle Damage Report). QCHN Create Vehicle Chain Used Vehicle Links the used vehicle to the new Usually when a dealer trades in a New Vehicle vehicle so that both vehicles are regarded as one business used vehicle during a sales process transaction with regard to purchase and sales The vehicles are linked by one internal order group. QORD Create Purchase Order (DBM) Creates a purchase order for the used vehicle QRPU Repurchase Used Vehicle For cases in which the vehicle already existed in the system, this action is executed. It contains the actions QTIP Prepare Repurchase , QIOG Group Internal Order , and QORD Create Purchase Order (DBM) see below. QTIP Prepare Repurchase QIOG Group Internal Order See Action QTIP: Prepare Repurchase of Vehicle. Creates an internal order group This action is part of vehicle into which the internal order of the creation. vehicle is placed. QORD Create Purchase Order (DBM) QGOR Create Goods Receipt (DBM) QINV Create Incoming Invoice (DBM) Creates a goods receipt for the used vehicle QRCR Change Vehicle into Replacement Car Creates an incoming invoice Vehicle master record The PO status changes to invoiced. Converts the vehicle to a replacement one that cannot be involved in a sales process until action QRCC is executed QRCC Turn Replacement Car into Normal Vehicle Vehicle master record Converts the replacement vehicle back into a normal one so that it can 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 to perform the following: Check whether the order action is allowed Change the vehicle status Update the vehicle history These vehicle actions are relevant for the following sales documents in vehicle sales and service: Vehicle quotation PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 14 of 31 Sales order Vehicle order Service quotation Service order Customer billing document Action QOFF Description Create Quotation (DBM) Prerequisites Scope of Functions of Action Note The vehicle is assigned to the customer (QACU). Is called if a vehicle quotation is created In Customizing for DBM order types, it is determined for the In the VMS document table, creates a link between the vehicle and vehicle quotation quotation that this action has to be performed when a quotation is created. Changes the vehicle status QDOF Delete Quotation (DBM) Quotation Is called if a vehicle quotation is deleted or rejected Updates the vehicle from the order QCSD Create Sales Order (DBM) Customer master record, vehicle order Is called if a sales order is created for the vehicle In the VMS document table, creates a link between the vehicle and sales order QDSD Cancel Sales Order (DBM) Sales order Is called if a sales order is deleted for the vehicle QCUO Create Vehicle Order (DBM) Vehicle master record The vehicle is assigned to the customer (QACU). Is called if a vehicle order is created In the VMS document table, creates a link between the vehicle and vehicle order QDCO Delete Vehicle Order (DBM) The vehicle order has not yet been Is called if a vehicle order is completed. deleted QFOR Complete Vehicle Order (DBM) The outgoing invoice is created. Is called if a vehicle order is completed The vehicle status must be QS60 ( Sales Order Completed ) to be able to execute this action. Updates the vehicle status from QS60 ( Sales Order Completed ) to QS50 ( Outgoing Invoice This action is the counterpart to/reversal of action QFOR. It is executed only when the vehicle Created ) Is executed in tandem with the order action order is completely closed, and subsequently reopened. QFOC Order Re-Open (Order Close Cancelled) ORD_CLOSE_CANC ( Cancel Close Order ) and is triggered by the event BILLING_CANCEL ( Cancel Last Billing Document ) QCSQ Create Service Quotation (DBM) Is called when a DBM service quotation is created. It updates the vehicle history and checks whether the status allows a service quotation to be created. QCSO Create Service Order (DBM) Vehicle master record Is called if a service order is created for the vehicle In the VMS document table, creates a link between the vehicle and service order QDSO QOIV Delete Service Order (DBM) Is called if a service order is deleted for the vehicle Create Customer Billing Document (DBM) Is called if a customer billing document is created for the vehicle order In the VMS document table, creates a link between the vehicle and customer billing document QOIR Cancel Customer Billing Document (DBM) Customer billing document Is called if a customer billing document is canceled for the vehicle In the VMS document table, creates a link between the vehicle and cancellation document The following table explains the actions that are relevant for internal service orders with revaluation: Action Description Prerequisites QCPO CO Prod. Create (DBM) QCPH CO Prod. Create Returns (DBM) CO production order PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Scope of Functions of Action Note Creates a CO production order The counterpart to this action is action QCPH (return). 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, The counterpart to this action is posts the primary costs from the action QCCH (return). vehicle internal order to the CO production order; and material consumption from the batch to the CO production order QCCH CO Prod. Cost Collection CO production order The counterpart to this action is Returns (DBM) QGRP action QCCP. CO Prod. Post Goods Receipt (DBM) QGRH Posts the goods receipt from the The counterpart to this action is CO production order to the batch action QGRH (return). CO Prod.Post Goods Receipt The counterpart to this action is Return (DBM) QSEP CO Prod. Create Settlement (DBM) QSEH CO Prod. Create Settlement Returns (DBM) QCLP CO Prod. Close (DBM) QCLH CO Prod. Close Returns (DBM) QCOS Check Balance of Internal Order QLIO Complete Internal Order action QGRP. Settles the CO production order against the batch The counterpart to this action is action QSEH (return). The counterpart to this action is action QSEP. Closes the CO production order and sets the deletion flag The counterpart to this action is action QCLH (return). The counterpart to this action is action QCLP. QSVC CO Prod. Stock Value Change (DBM) The counterpart to this action is action QSVH (return). QSVH CO Prod. Stock Value Change Returns (DBM) The counterpart to this action is action 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 QGOR Description Create Goods Receipt (DBM) Prerequisites Scope of Functions of Action Purchase order Creates a material document for There can only be one purchase the goods receipt with reference to order without goods receipt for a a purchase order Note vehicle. If there is more than one, the goods receipt for the most recent purchase order is posted automatically. It cannot be posted to the sales order stock. QGRE Cancel Goods Receipt (DBM) Goods receipt Creates a cancellation document for the goods receipt document QGIS Create Goods Issue (DBM) Vehicle master record, vehicle order Is called if a goods issue is created in the vehicle order in order to update the vehicle history and status, for example QGIR Cancel Goods Issue (DBM) Goods issue Is called if a goods issue is canceled in the vehicle order in order to update the vehicle history It can be used only for goods issues that have been created with the action QGIS. QGRP CO Prod. Post Goods Receipt CO production order, goods receipt Posts the goods receipt from the Used, for example, for internal CO production order to the batch service orders with revaluation and status, for example (DBM) QGRH CO Prod. Goods Receipt Return CO production order, goods receipt Reverses the posting of the goods (DBM) Used, for example, for internal receipt from the CO production order service orders with revaluation Prerequisites Scope of Functions of Action Note Vehicle sales order Creates a vehicle returns order Vehicle Vehicle returns order Creates a goods receipt for the vehicle return The table below explains the vehicle actions that are relevant for vehicle returns: Action QROR QRGR QRBD Description Create Return Order Goods Movement for Vehicle Return Create Invoice for Vehicle Return Creates an invoice for the vehicle return The following tables explain the vehicle actions that are relevant for vehicle transfer postings: Transfer Posting of Vehicle from Current Assets to Fixed Assets: PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 16 of 31 Action QCAS Description Create Fixed Asset for Vehicle (DBM) Prerequisites Scope of Functions of Action Vehicle Creates a fixed asset Note Asset class, for example, asset class 3100 for vehicles QVTA Post Vehicle to Fixed Assets (DBM) Posts the vehicle to the fixed assets QVTD Create Fixed Asset and Post Vehicle Creates a fixed asset and posts the You can combine actions QCAS vehicle Create Fixed Asset for Vehicle (DBM) and QVTA Post Vehicle to Fixed Assets (DBM) in the interlinking action QVTD Create Fixed Asset and Post Vehicle . QATV Post Vehicle to Current Assets Posts the vehicle to the current assets For more information, see Transfer Posting of Vehicle from Current Assets to Fixed Assets. Transfer Posting of Vehicle Between Plants: Action Description QPGM Cross-Plant Goods Movement QVTP Transfer Between Plants Prerequisites Scope of Functions of Action Note Vehicle Transfers a vehicle from one plant This interlinking action contains Quotation DBM sales order to another See: action QVTP the following actions: QCIO Create InternalOrder, QIOG Group Internal Order, QCOR Check Settlement Rules, QROC Transfer Costs, QCCV Batch and Valuation Check, QPGM Cross-Plant Goods Movement, QLIO Complete Internal Order. QCIO Create Internal Order Vehicle master record Creates an internal order for a Internal orders are used to plan, vehicle collect, monitor and settle the costs of specific operations and tasks performed within a company. QCOR Check Settlement Rules Vehicle master record QROC Transfer Costs Vehicle master record Checks whether settlement rules exist in the internal order Costs form the current internal order are posted to the new internal order; this takes place by line item reposting QCCV Batch and Valuation Check Vehicle master record Creates a batch and a valuation type for the vehicle if they do not QOIA DBM Order - All Billing Vehicle master record, customer Resets the vehicle to a pre-invoice master record status exist in the specified plant Documents Cancelled For more information, see Transfer Posting of Vehicle Between Plants. Transfer Posting Between Company Codes: Action Description Prerequisites Scope of Functions of Action QVTC Transfer Between Company Codes The vehicle to be transferred has already been sold from one Transfers a vehicle from one This interlinking action contains company code to another company the following actions: QCOS Note company code to the other by means of a DBM vehicle order. code Check 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 a vehicle transfer between company codes 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 MSSO Description Issue Messages Prerequisite Scope of Functions of Action Note Vehicle master record Prints detailed information about the vehicle For detailed information, see Vehicle Printing PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 17 of 31 QCRE Create Vehicle with Internal Order (DBM) Configurable material Creates vehicle master record with internal order and batch The system assigns the internal vehicle number. QMOD Change Vehicle (DBM) Vehicle master record Allows changes to vehicle You control the action in attributes and qualifiers Customizing for the VMS by Is executed in the following cases: selecting Enhancements If vehicle data in the vehicle Define Additional Data for Vehicle master record is changed, without a different action having been Assign Attributes to Actions chosen explicitly If vehicle data in the DBM order is changed, without one of the vehicle actions having been performed for vehicle sales and service QNTF Create Notification Called to update the vehicle history each time a notification is You can change the notification from the vehicle history created for a vehicle QVIN Change VIN (DBM) Vehicle master record Changes the vehicle identification You can assign each VIN only number (VIN) once and should not make subsequent changes unless this is absolutely necessary. You can make changes only if a VIN has already been saved for the vehicle. You can use this action to control authorization for changing the VIN separately. As a result, anyone who changes the VIN can be traced in the vehicle history. QSCR Scrap Vehicle (DBM) Vehicle master record Changes the vehicle status QACU Assign Customer (DBM) Vehicle master record, customer Assigns a vehicle a customer and You can assign a vehicle only one master record triggers the partner determination customer. To change the customer assignment, you first have to cancel the customer assignment (QDCU). QDCU Cancel Customer Assignment (DBM) Vehicle master record, customer Cancels the assignment of a master record customer 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. Integration Interlinked 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). Note You must not use VMS interlinked actions in the DBM order. Instead, you should use the options provided in Customizing for Dealer Business Management (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. Features VMS interlinked actions consist of more than one elementary action. When the system executes an interlinked action, it starts the elementary actions contained 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 Interface Framework 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 ( Create Purchase Order ; primary action) and CUOR ( Create Sales Order ; secondary action). It is not possible to interlink actions that are already interlinked. Example The interlinked action Execute Vehicle Procurement could consist of the following elementary actions: Create purchase order Create goods receipt PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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 Note For more information about the individual function modules, see transaction SE37 ( Function Builder ). 1.2.5 RFC Function Modules for Processing Multiple Vehicle Masters 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 Note For more information about the individual function modules, see transaction SE37 ( Function Builder ). 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 for vehicles. For more information, see Customizing for Dealer Business Management (DBM) under Vehicle Business Add-Ins BAdI: Dependency Check for 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 business transaction type. The business transaction type describes the vehicle with regard to the business process required and reflects the different vehicle sales scenarios and life cycle phases, such as new, owned by customer, used, or replacement car. During the vehicle's life cycle, the business transaction type might change, 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 vehicle USC ( Used Vehicle ) A vehicle owned or to be owned by the dealer which should be sold as a used vehicle CUS ( 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 the dealership 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 vehicle stock values to be posted to the same, or different, G/L accounts depending on the material type. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 19 of 31 Integration Certain 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 the system. 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. A life cycle act can be considered as an encapsulated business process step such as creating an internal order, changing valuation class, changing business transaction 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 life cycle. Prerequisites You have made the settings in the following Customizing activities: Logistics Control Logistics Logistics Logistics Execution Execution Execution Execution Dealer Business Management (DBM) Dealer Business Management (DBM) Dealer Business Management (DBM) Vehicle Management System (VMS) Vehicle Vehicle Master Vehicle Life Cycle Management Define Life Cycle Vehicle Vehicle Master Define Business Transaction Vehicle Vehicle Master Vehicle Control Define VMS Action Control Data Define Action Controls and Define Action Matrices Note For the upgrade from DBM 6.00 to DBM 7.00 see SAP Note 1337722 regarding business transaction types. Features In the following the most common changes of business transaction types and the relevant data changes in the system are explained. This reflects the standard settings. Creation of Vehicle If 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 Vehicle The 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 CUS New Vehicle to Used Vehicle After action QTIP ( Prepare Repurchase ) the system performs the following data changes: Change business transaction type from NEC to USC Change the vehicle options to not purchase order relevant Change the vehicle options to not sales order relevant Create new batch and valuation type if not available in trade-in plant Create new CO internal order Delete vendor/supplier Delete customer/debitor Delete sales organization Delete distribution channel Delete sales date Delete vehicle partners Customer Vehicle to Used Vehicle The business transaction type changes from customer vehicle to used vehicle, when a used vehicle is bought from a customer (before the purchase order is created). The system performs the following data changes: Change business transaction type from CUS to USC Create new batch and valuation type Create new CO internal order Delete vendor Delete debitor Delete sales organization Delete distribution channel Delete sales date Delete partner Delete margin taxation indicator Used Vehicle to Customer Vehicle The 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). The system performs the following data changes: Change business transaction type from USC to CUS PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 20 of 31 New Vehicle to Replacement Vehicle When 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 changes to replacement vehicle. The system performs the following data changes: Change business transaction type from NEC to RPL Replacement Vehicle to Used Vehicle When 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. The system performs the following data changes: Change business transaction type from RPL to USC Delete sales order relevance of options Activities In 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 this overview the system shows you which action took place in which business transaction type of the vehicle. Example During the vehicle life cycle the business transaction type can change as follows: 1. Initial -> NEC A vehicle is created and purchased as a new vehicle by the dealer. 2. NEC -> RPL After 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 transferred to asset management. 3. RPL -> USC After 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 -> CUS The vehicle was sold. When it is invoiced and handed over, its service life cycle has started. 5. CUS -> USC Some 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 overheads such 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 multiple vehicles at a time, but also cancel costs that have been posted already. Additionally, you can use the function to separately create purchase orders, goods receipts, and incoming invoices for the external services. In the vehicle sales process, this function helps in estimating the profitability of each vehicle being sold. Note You can post or cancel additional vehicle costs only using the Mass Vehicle Processing transaction. Standard SAP ERP transactions (such as those used for purchase orders, goods receipts, and invoices) do not support posting or cancellation of additional vehicle costs. Prerequisites The 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 Logistics Execution Dealer Business Management Master Data Additional Costs Assign Material to Additional Cost Category . Note that you can assign only non-stockable service materials to external service types. Features When 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 its internal 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 a sequential manner. Alternatively, you can generate the purchase orders, goods receipts, and incoming invoices separately. Activities Posting Additional Costs 1. In the SAP Easy Access menu, go to Logistics Logistics Execution Processing (or transaction /DBM/MASSACTIONS). Dealer Business Management Vehicle Processing Mass Vehicle 2. Search for the vehicles by entering the search criteria and choosing Vehicle Search . PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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 the distributed 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 is assigned 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 Costs To cancel additional costs that have been posted earlier, search for and select the vehicles as explained above, and choose Additional Cost . The system cancels the purchase orders, goods receipts, and incoming invoices sequentially. Possible Actions Cancel Creating Separate Purchase Orders, Goods Receipts, or Incoming Invoices 1. In the SAP Easy Access menu, go to Logistics Logistics Execution Processing (or transaction /DBM/MASSACTIONS). Dealer Business Management Vehicle Processing Mass Vehicle 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 . Note You 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 the distributed amounts here, if required. Note If you have implemented the Business Add-In (BAdI) /DBM/BADI_VMASS_DISTRIBUTE_ADC, the system distributes the amount based upon the BAdI 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 is assigned entirely to it. To cancel the documents, select the vehicles as explained above, and choose button, depending on the document you are cancelling). Possible Actions Cancel Pur. Order for External Service (or other similar Note Only 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 that vehicle 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 receipt and 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 of vehicles 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 a particular 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 each vehicle has been in stock. You can also define personalized selection variants to run the calculation on a regular basis. Prerequisites Goods receipt has been performed for the selected vehicles. That is to say, the selected vehicles are currently in stock. Features You can calculate the stock age of one or more vehicles using any of the following ways: From the Mass Vehicle Processing function Running the report /DBM/VEHI_STOCK_AGEING as a background job Running the Stock Ageing report (or /DBM/STOCKAGEING transaction) Activities To 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 PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. 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 Stock Ageing . Alternatively, run transaction /DBM/STOCKAGEING. 2. Select the appropriate selection variant, as created in Mass Vehicle Processing . Note You 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 choose Execute . 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 the difference 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. Note You 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 spool in 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 master and 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 material group. You can do this by assigning valid material groups in Customizing for Dealer Business Management (DBM), in accordance with the OEM and item category. The search help function can also be used to find entries in the original parts master. Note Using various function modules, you can adapt the parts and use functions for the parts. For more information about function modules, see Customizing for Dealer Business Management (DBM) under RFC Interfaces Function Modules RFC Original Part . Structure DBM-Specific Transactions Apart 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 obligation Subject to disposal Check for multiple entry of parts items in the order Exchange parts process You can assign a used part to an exchange part. For more information, see Exchange Parts. Simplified user interface Default views Aggregated display Transaction Create Material from Original Parts Master (/DBM/MMXX) You can search for parts in the original parts master. If you require a part in service and parts sales, you can create a complete material master record in your dealer parts master. By doing this, you avoid having superfluous material master records for parts in the system and ensure that you only have the material master records that you really require. Note PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 23 of 31 You can add manufacturer-specific fields according to the enhancement concept. Manufacturer Part Number In DBM, you can use the 40-character manufacturer part number that processes more than 18 characters. The uniqueness of a part results from the combination of the material number and manufacturer. This ensure the multi-brand capabilities of DBM. To do so, you must enter the vendor number of the manufacturer in the material master. The prerequisite for using the manufacturer part number is that the conversion exit in Customizing is active. Example 18-character manufacturer part number Material number (external): A062115561 Manufacturer part number and manufacturer: do not enter 40-character manufacturer part number Material number (external): A062115561 Manufacturer: RAAG The manufacturer part number is displayed in the interface as follows: A062115561:RAAG Supersession DBM supports the following types of linear supersession, depending on the manufacturer: 1. Supersession takes place automatically in the background. When you create a new parts item, you receive the message that material X has been replaced with material Y . 2. When you create a new parts item, you can choose one of the two materials displayed in a dialog box. Supersession takes place based on the quantity, in other words, the order quantity is used. 3. When you create a new parts item, you can choose one or both of the materials displayed in a dialog box. By double-clicking on a line, the user can adjust the quantity as required. 1.3.1 Parts Master The information about the materials that a company procures or produces, stores, and sells. The parts master is the company's central source for retrieving parts-specific data. This information is stored in individual parts master records. Dealer business management uses the DBM-specific parts master transactions /DBM/MM01, /DBM/MM02, and /DBM/MM03. These DBM parts master transactions provide the same functionality as the standard MM transactions. The only differences are: The user interface is optimized for automotive dealer businesses. Fields relevant for purchase, inventory, and accounting are grouped within one screen for each area. Indicators for specific automotive dealer business requirements: Return Part Identifies the part as one that must be returned to the OEM (required for warranty claim processing). Retention Obligation Indicates that the part should be retained, according to OEM guidelines. Usually, you keep the part in a separate bin, in the event that the OEM requests the part. Check Multiple Entry If you set this indicator, the system checks whether the part is already used in the order. Subject to Disposal Indicates that this material should be disposed. You can assign a used part to an exchange part, indicating that this part is relevant for the exchange process. For more information, see Exchange Parts. Integration The parts master is used by all components in the DBM and SAP Logistics System. The integration of all parts data in a single database object eliminates redundant data storage. In the SAP Logistics System, the data contained in the parts master is required, for example, for the following functions: In In In In In Purchasing for replenishment Inventory Management for goods movement postings and physical inventory Invoice Verification for posting invoices Sales and Distribution for DBM part sales processing Production Planning and Control for parts requirements planning, scheduling, and work scheduling In Customizing for Logistics – General under requirements. Material Master Configuring the Material Master , you can configure the master to suit your specific For more information about the material master, see Material Master (LO-MD-MM). 1.3.2 Creation of Material from Original Parts Master You can use this function to create a material master from the original parts master by using a reference material. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 24 of 31 Prerequisites Data for the material masters to be created must be available in tables /DBM/OMARA and /DBM/OMAKT. You must have created a suitable reference material. Activities 1. Open Create Material from Original Part Master (transaction /DBM/MMXX). 2. The system displays a selection screen with the following subscreens: 1. Original Parts Master Enter the material number from/to, and an OEM. The system uses this data to create a selection list of materials that can be created. 2. Reference Material: Enter a material number. The system uses this material as a reference material. It has to have been created for the organizational levels for which you want to create the new material. 3. Organizational Levels: The organizational levels for which the system creates the material include plant, storage location, sales organization and purchasing organization. 3. When you choose Execute , the system creates the material master, purchasing info record, purchasing price and sales price. Note You can also create a material from the original parts master when you create a DBM order. In this case, you have to maintain the reference material by choosing Environment Reference Materials . 1.4 Storage Goods Manager This function enables you to handle goods that are placed into storage by dealerships for their customers. These storage goods include, for example, wheel sets, snow chains, hardtops; in other words, goods that are used in vehicles depending on the season. When these goods are not being used, they are stored on the property of the branch concerned. Integration The Storage Goods Manager is integrated into DBM order processing (transaction code /DBM/ORDER, /DBM/ORDER01, /DBM/ORDER02, /DBM/ORDER03). It is displayed in the memo pad ( Environment Memo Pad ) and also in a separate subscreen on the Header tab page. You can access the Storage Goods Manager by choosing Storage Goods in the vehicle master. The system then displays the storage goods assigned to this vehicle. In the vehicle-related data of the vehicle master ( Goto Vehicle ), there is also a separate subscreen for storage goods. Furthermore, you can access the Storage Goods Manager by choosing Storage Goods in the customer master . The system then displays the storage goods assigned to this customer. Prerequisites If you wish to use the Storage Goods Manager , you should have made the appropriate settings in Customizing for Dealer Business Management(DBM) under Storage Goods Manager . If you wish to use printing functions in the Storage Goods Manager, you have made appropriate settings in Customizing for Dealer Business Management(DBM) under Storage Goods Manager Message Determination . Message determination in DBM is similar to the standard procedure used in Sales and Distribution (SD). For more information on the standard message determination procedure, see the standard documentation Output Determination. Features The Storage Goods Manager provides various features, such as: Storage for the following storage good types: tire sets, summer wheels, winter wheels, roof racks, hard tops, rim sets, ski rack, snow chains. Note The above-mentioned storage types are delivered in the system. You cannot add or handle other storage types. Functions for creating, searching, displaying, deleting and maintaining storage goods and for assigning the storage good to a specific customer and/or vehicle. To access these functions, from the SAP Easy Access menu choose Logistics Logistics Execution Dealer Business Management Storage Goods Manager (transaction codes /DBM/STG_CREATE ( Create Storage Good ) and /DBM/STG_SEARCH ( Storage Goods Search ). Printing of storage goods; to access the printing functions, from the SAP Easy Access menu choose Logistics Logistics Execution Dealer Business Management Storage Goods Manager Output Condition /DBM/SGM08 - Create Output: DBM Order or /DBM/SGM09 - Change Output: DBM Order or /DBM/SGM10 - Display Output: DBM Order . In the Storage Goods Manager, there are two different options for calling message determination: Explicitly in dialog mode Choose the print function in the order processing transaction. Automatically by an action When executing an action, message determination is called. When, depending on the given status and action, a message can be found the storage goods are printed. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 25 of 31 There are the following actions: EXP List Overview REM Reminder SCP Confirm Putaway in Storage SCR Confirm Removal from Storage SDL Delete Storage Goods SEP Putaway in Storage SER Removal from Storage SES Extend Time in Storage SPP Prepare Putaway in Storage SPR Prepare Removal from Storage SSP Scrap Storage Goods There are the following statuses: CREA Created DELE Deleted FRMV For Removal FSTR For Storage RMVD Removed SCRP Scrapped STRD Stored Note The above-mentioned actions and statuses are delivered in the system. You cannot define your own actions or statuses. You must, however, define an action matrix; here you enter the start status of the storage good (old status), the action, the status of the storage good after you have executed the action (new status) and thus define how the status of a storage good changes when a specific action is executed. 1.5 HR Master Data for DBM You use this function to create employee information for different processes. For example, in the new and used vehicle sales process, you require sales representative data to determine sales commission information (ICM integration). For the service process, service advisor information is required for time recording. Therefore, you create HR master records. Depending on the processes you use (for example time recording or ICM integration), you provide information for the following HR master record views: Infotype 0001: Organizational assignments Infotype 0002: Employee data (name, address) Infotype 0007: Target working times Infotype 0050: Time recording data (terminal assignment) Infotype 0315: Default values into CATS (activity type, cost center assignment) Integration When a service advisor or sales representative creates a DBM order, they enter either the employee number manually, or the system enters the appropriate user by default. This allows employees to search for DBM orders they are responsible for, and to determine the daily workload. When workshops use time recording functionality, the service technician working on a service order records the time spent working on that order. The service technician selects their employee number, and records the time spent on the order. Based on HR master data, the system determines the appropriate cost center and activity type to calculate the correct internal costs for the working time. Prerequisites You must define HR master data infotypes (transaction PM01). More Information For more information about HR master data, see on the SAP Help Portal at http://help.sap.com/ SAP ERP the SAP Library for ERP Central Component SAP ERP Central Component Human Resources Personnel Management (PA) Personnel Administration (PA-PA) Maintaining HR Master Data . 1.6 Labor Value A measurement of work that can be defined, among other things, by the following values: Labor value number Description Target time for labor value Pricing reference material Labor value main type You can combine labor values in Labor Value Catalogs according to different criteria. A dealer can assign more than one labor catalog to each OEM. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 26 of 31 Note In Customizing for Logistics Execution under Dealer Business Management can assign more than one catalog ID to an OEM. Service Labor Value Catalog Determination Assign Criteria , you You can assign the division representing the vehicle brand in the SAP System to an external manufacturer, by selecting Dealer Business Management Company Structure in Customizing for Logistics Execution . You can use the manufacturer, for example, to control the interface or determine the labor value catalog. In order processing for a service order, you can enter labor values as items in the order. For the item category in the order, the system distinguishes between labor values entered in the material master and manual labor values not entered in the material master that are used for a specific order only. You can use manual labor values, for example, for dealer promotions or sales of used vehicles. Note Using various function modules, you can adapt the labor values and use functions for the labor values. For more information about function modules, see Customizing for Dealer Business Management (DBM) under RFC Interfaces Function Modules RFC Labor Values . You can use the Business Add-In (BAdI) /DBM/BADI_LV_SEARCH (see Customizing for Dealer Business Management (DBM) under Value Business Add-Ins (BAdIs) BAdI: Labor Value Search ), to influence and enhance the labor value search. Service Labor Structure The labor value is defined by an alphanumeric key. This key is model and OEM-specific and is provided by the OEM in the form of subsystems. These systems support the search for labor values and contain a series of additional graphical information that supports the work carried out on the vehicle. The systems are connected to DBM by an interface. The following data is stored in the master record of a labor value: Pricing reference material When a DBM order is created, the system transfers this material to the order. Labor value main type The OEM usually delivers the labor value main types. For manual labor values, you can define labor value main types yourself. Labor value group You can use the labor value group to subdivide the labor values according to categories that you choose, for example, electrics and electronics, mechanics, and body work. Matchcode The matchcode simplifies the determination of labor values in the DBM order. Target time for labor value The value in the system is proposed as a quantity for the labor value and a target time in the DBM order. You can organize labor values in a hierarchy. You define the hierarchy level in Customizing for Dealer Business Management (DBM) under Value Define Hierarchy Level and maintain the labor value hierarchy nodes in transaction /DBM/LBROPGRP. Service Labor Example If the hierarchy level has two characters, the following labor values could belong to the hierarchy node 17 Engine Lubrication : 17030100 Check oil pressure 17051900 Remove and install oil pressure switch 17071900 Remove and install oil temperature sensor More Information For more information about labor values, see the DBM Configuration Guide on SAP Service Marketplace at Solutions Industry Solution Guides SAP for Automotive . http://service.sap.com/instguides Industry 1.7 Package A group of items, for example, parts, labor values, and external services that are required for a specific task. In vehicle service, you use this business object mainly for recurring standard tasks such as inspections or the exhaust emission test, or for special dealer sales actions, for example a winter check. OEMs provide preconfigured packages by means of an interface. But you can also define your own packages. You can search for packages by using a wildcard. Note Using various function modules, you can adapt the packages and use functions for the packages. For more information about function modules, see the Customizing for Dealer Business Management (DBM) under Interface Framework Function Modules RFC Packages . Structure A package consists of the following parts: Package data: PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 27 of 31 The package data contains header details, price relevant data, a list of package variants and variant data, and a list of items and item details. Some of the package header data (organizational data) is used as search criteria for the DBM order package search. Administration data: The administration data contains data such as creation/change date and the user for the header, the package variants, and the items. Pricing data: The pricing data contains pricing data for the header, the package variant, the header items, and the variant items. Not all packages have pricing data. Texts: Here you can find a descriptive text for the main package and the package variant. There are main packages and package variants. A package contains labor values and parts. A parts package, however, only contains parts and can be used in parts orders. When you add a package to an order, the system automatically copies the individual package items. You cannot include a package in the same job more than once. You can use the labor value main type to make the assignments to the model-specific labor values. You can use customized vehicle criteria to assign the package, for example, to the vehicle model for which the package should be valid. When you save a package item, you can decide whether the item should be valid for all vehicles, in other words on header level, or whether you wish to restrict the item on version level to specific vehicles (or vehicle criteria, such as the model code). Package Types The following package types are available in the standard version of the Customizing for Dealer Business Management (DBM) : 01: Price package 02: Chain package 03. Parts package You can use the package type to define which organizational data should be used for the package. In Customizing for Dealer Business Management (DBM) under Service Package Define Package Type , you can assign different organizational data to each package type to define brand, OEM, dealer, or workshop packages, for example. Here, you can also assign a pricing procedure. The system uses this pricing procedure material in price packages. In chain or parts packages, the system uses the pricing procedure to find a condition record value for a condition that has been predefined under Define Condition Type for Package . If the system determines a value, it is displayed in the Net Price field of the package; you cannot change this price. Furthermore, in Customizing for Dealer Business Management (DBM) under assign the package type to a number range for the package ID. Service Package Define Number Range for DBM Package , you can Package Categories The system uses different package categories: Chain When creating a package, the system includes all items with the categories that have been defined in Customizing for the package type. You cannot change the prices in the package yourself, but you can add and change additional items as you wish. By selecting a package during order maintenance, an order job is created and for each package item, an order job item. The item price is the same as for the individually entered items. Price As with the chain package category, the system adds all the order items. A fixed price is defined for the entire package or package variant. The system automatically copies the package condition values to the order condition values per item. By defining the condition type for the package in Customizing, you determine whether the condition is a discount or a fixed price condition. The pricing procedure defines whether the package price is the final value, or whether additional discounts are possible. Parts The package is assigned to one material master and can include only parts items (similar to a bill of material). The parts package can be used in service and parts orders. The system does not create a job if you select the package in the order. You can assign a part item to the package and automatically replace the part in the order with the package items. Note You can use the Business Add-in BAdI: Package Search to make any enhancements and restrictions you may require for the package search. 1.7.1 Package Maintenance The functions in the transaction Edit Package (/DBM/PACKAGE) enable you to process packages, main packages, and package variants. Integration The package search and transfer are integrated into the DBM order. Features Package functions enable you to do the following: Search for and list packages fulfilling specific search criteria Create, change, and display packages with validity periods Create, change, display, and delete package variants with validity periods Create packages by copying existing packages Note Packages with package type 01 cannot be used for creating packages with package type 02 or 03 . PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 28 of 31 For price packages, set package prices, package variant prices, and package item prices Use the business object (BUS2440) for packages and assigned workflow events Select packages in the DBM order using predefined criteria Transfer package data, items, and prices to the DBM order (with and without job creation) For specific fields, make mass changes to packages and package items Import packages from an external, OEM system using RFC Track changes to packages with change documents Use different authorizations for packages (authorization object /DBM/PACK) Some users (for example, service supervisors) can create and change packages while other users (for example, service technicians) are only allowed to display packages Define order job printing options in the package For parts packages without job creation, use the package as an entry aid for parts orders For parts packages, assign the package to the material master for material substitution Define the user interface (interface control) for the package transaction (layout of the tabstrips) Define the customer influence on package data and the process flow by using Business Add-Ins (BAdIs) You can append customer-specific fields to the package database tables. You require enhancements to integrate your own data into the package transaction. The package transaction provides the required enhancement calls. Furthermore, there are enhancement options for the transfer of data from the package to the order and also in the package search help. Activities You can make settings for the package functions in Customizing for Dealer Business Management (DBM) under Service Package . You can adapt the package functions to suit your own requirements by using the Business Add-Ins (BAdIs) in Customizing for Dealer Business Management (DBM) under Service Package Business Add-Ins (BADIs) . You can find a list containing details of RFC functions in Customizing for Dealer Business Management (DBM) under RFC Package . RFC Interfaces Function Modules 1.7.2 Package Reporting You use this function to search for packages. The system returns a list of packages based on your search criteria. You can search for DBM packages by using standard DBM package information, or customer-specific package information. The search criteria includes: Header data Organizational data Pricing data Package variants In addition, you can search for DBM package using customer-specific package information, for example additional package fields at header, variant, and item level. Integration The package reporting functionality is also used in the Change Package report. This report supports the mass-change procedure for packages. Features You can use the package list to navigate to the package details. 1.7.3 Change Package Report You use this report (transaction /dbm/package_list2) to search for a list of packages, and change all selected packages in one step. For example, you can use this report to: Replace a material with a new version Change the target time for a specific labor value Change the individual price of a labor value or a part The Change Package report supports the mass-change procedure for packages. Typically, this report involves the following steps: Entering search criteria for the packages you want to change Entering the changes you want to make (for example price, or quantity) Starting a test run Selecting packages you want to change Executing the mass-change procedure for selected packages Features The package administrator who is responsible for creating and maintaining packages ensures that the packages used in the service process provide the correct parts, labors, quantities, and prices. Price changes for parts and labors are requested periodically. These price changes must also be updated in the packages that reference these parts and labors. The Change Package report allows you to select and update these packages. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 29 of 31 The Change Package report contains the following: 1. Fields for which you can change values. These include Part (material) Labor target time Package ID (item, not header) Package price Variant price Item price (discount, surcharge) 2. Search criteria for the packages you want to change, including: Header data such as labor value, external package ID, and package status Organizational data such as plant, sales organization, and division Pricing data such as tax and condition group Standard variant data Item selection data such as labor value, target time, and item category 3. Options for a background run. You can start the Change Package report as a background job. The package administrator can specify whether: The package price needs to be adjusted in case of a low margin The package is updated when the package is included in another package A test run is required Example Packages include items with parts or labors. If a part number is replaced by a new part number (follow-up material), the part number must be replaced in all current and valid packages. If the price of a part changes, all relevant packages must be updated with the new price information. The package administrator checks whether the fixed price for the package must also be adjusted. The package administrator enters relevant search criteria, such as package type, organizational information, and the new price for the relevant part. The system determines relevant packages to be changed. The package administrator checks all packages, navigates to the package details and decides whether to update the package or not. 1.8 Job ID A job ID is a request frequently made by customers for a service from the workshop, such as an inspection or seasonal tire change. Job IDs are defined in a job catalog with a description and an estimated time, among other data. Job IDs are used in appointment scheduling. When you schedule an appointment, you can create jobs in the service order by selecting job IDs from a job catalog. Structure Job IDs are defined using an alphanumeric key. The following data is stored in the master record of a job ID: Labor Value Group You can use the labor value group to group job IDs into categories, such as electrical work, mechanical work, or body work. Matchcode The matchcode makes it easier to find job IDs in the DBM order. Default Package ID You can assign service packages (see Package) to each job ID in the job catalog. If a service advisor schedules an appointment using the job ID the package is assigned to, the system will add all the items maintained in the package to the service order. Estimated Time from Package In the job catalog, you can specify for each job ID if the system should calculate the estimated time during appointment scheduling based on the sum of the target times of all the package items. Job Type You can categorize the job IDs by job type. This categorization is primarily used in the service history (see Vehicle Service History). Estimated Time You enter the estimated time based on the labor value main type. In the service order, the system searches for a job ID using the labor value main type. The estimated time entered in the job catalog is used in the service order, but can be overwritten. Tools For each job ID, you can define which tools are required for the service (see Tool Demands in DBM Orders and in MRS). You enter tools based on the labor value main type, since the tools required for a service can vary depending on the vehicle model. You can group job IDs according to labor values (see Labor Value). The hierarchy level of a job ID is defined in Customizing and is reflected in the key. Integration To use job catalogs and job IDs, you make the settings in Customizing for Dealer Business Management (DBM) under Service Workshop Scheduling Job Catalog . You create job IDs in a job catalog. To do so, on the SAP Easy Access screen, choose Logistics Logistics Execution Dealer Business Management Master Data Workshop Scheduling Job Catalogs Maintain Job Catalog . 1.9 Pricing Conditions You use this function to determine valid sales prices during order processing. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 30 of 31 Integration The system uses pricing conditions in order and package pricing. Prerequisites You have added the pricing conditions to the relevant pricing procedure in Customizing for Sales and Distribution under Control Define and Assign Pricing Procedures (choose Maintain Pricing Procedures ). Basic Functions Pricing Pricing Features For more information about condition technique elements, such as condition types, condition tables, and access sequences, see the Sales and Distribution (SD) component under Pricing and Conditions. We deliver predefined pricing conditions. These usually begin with Qxxx (for example QPRT - a relevant condition for the sales price of parts). 1.10 Warranty Profile You can use this function to define the type of warranty that is assigned to a particular vehicle. Warranty categories represent different warranty types. A warranty profile consists of multiple warranty categories and can therefore include warranties from OEM, legal and compulsory warranties, as well as an extended warranty. Integration The warranty profile includes the warranty terms (maximum milage or time period). Prerequisites You have defined a warranty profile in the SAP Easy Access screen under Edit Warranty Master Data (transaction /DBM/WTY1). Logistics Logistics Execution Dealer Business Management Master Data You can assign a warranty profiles individually for each model sales code, or generically for an entire brand (division). When you create vehicles, the system copies the entire warranty profile to the vehicles by default. You can exclude individual warranty categories assigned to a profile from copying. Features Once you assign a warranty profile to a specific model sales code, the system assigns the entire warranty profile (including all warranty categories) to each new vehicle record. In the vehicle master, each warranty category is inactive until you enter the start date. The system uses the warranty category start date to calculate the end date, and determine whether a warranty is inactive, active, or expired. During service order processing the system displays the warranty categories and the according status ( Inactive , Active , and Expired ) in the memo pad. You can select active warranty categories for further service order follow-up processes. Example You want to assign a standard warranty for each vehicle of a particular model. You assign a warranty profile that includes the standard warranty. You then offer the customer the option to purchase an extended warranty. You can include the extended warranty in the profile, but set the default value Not to be Copied . When a customer buys the extended warranty, the additional category can be selected in the vehicle master. 1.11 Warranty Catalog You use this function to specify data for a warranty claim. Service performed under warranty cannot be invoiced to the customer. You create a warranty claim to request reimbursement from the OEM. For the warranty claim, the OEM requires additional information such as the main defect code, and the cause code. The OEM uses this data for warranty claim validation and approval. The OEM provides a predefined warranty catalog and code structure that you can use when creating a warranty claim. For more information about how to create warranty claims, see Order Processing for a Warranty Case. Integration Warranty catalogs are integrated into the warranty claim, which is triggered from the DBM service order. The service advisor enters the main defect code, the cause code and the symptom code. PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved. Page 31 of 31