Dealer Business Management (IS-A-DBM)

Dealer Business Management (IS-A-DBM)
PDF download from SAP Help Portal:

http://help.sap.com/saphelp_dbm600/helpdata/en/6F/9FC1FA5E8F44B2858B845A3AD1249E/frameset.htm
Created on November 02, 2014
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.
© 2014 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 Page 1 of 77
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
Table of content
1 Dealer Business Management (IS-A-DBM)
1.1 Customer
1.1.1 Customer Data Management
1.1.1.1 Notification
1.1.1.2 Fact Sheet
1.1.1.3 Memo Pad
1.2 Vehicle
1.2.1 Vehicle Search
1.2.2 Action Control During Vehicle Processing
1.2.2.1 Determination of Action Control
1.2.2.2 Execution of Vehicle Actions
1.2.2.3 Details for Vehicle Actions
1.2.2.3.1 Actions for Vehicle Procurement
1.2.2.3.2 Actions for Vehicle Sales and Service
1.2.2.3.3 Actions for Goods Movements
1.2.2.3.4 Other Vehicle Actions
1.2.2.3.5 Interlinked VMS Actions in DBM Vehicle Master
1.2.3 Vehicle Transfer Posting
1.2.3.1 Transfer Posting of Vehicle From Current Assets to Fixed Assets
1.2.3.2 Transfer Posting of Vehicle Between Plants
1.2.3.3 Transfer Posting of Vehicle Between Company Codes
1.2.4 Used-Vehicle Purchasing
1.2.4.1 Example: Handling of Missing Handover Articles
1.2.4.2 Example: Handling of Damages
1.2.4.3 Example: Pricing in Used-Vehicle Purchasing
1.2.4.4 Action QTIP: Prepare Repurchase of Vehicle
1.2.5 Vehicle Chain Business
1.2.6 Vehicle Returns
1.2.7 RFC Function Modules for Processing the Vehicle Master
1.3 Vehicle Model
1.3.1 Assignment of VMS Roles
1.3.2 RFC Function Modules for Processing the Vehicle Model Master
1.4 Part
1.4.1 Creation of Material from Original Parts Master
1.4.2 Stock Information
1.5 Labor Value
1.6 Package
1.6.1 Package Maintenance
1.7 Recall
1.7.1 Recall Processing
1.8 Standard Text
1.8.1 Text Control
1.9 DBM Order
1.10 Order Item
1.11 Order Processing
1.11.1 Order search
1.11.2 Creation of a Vehicle Quotation
1.11.3 Order Processing in Vehicle Sales
1.11.4 Order Processing for the Service Order
1.11.4.1 Creation of Internal Service Orders with Revaluation
1.11.5 Order Processing in Parts Sales
1.11.6 Order Processing for a Warranty Case
1.11.6.1 Processing of Warranty Master Data
1.11.7 Order Control
1.11.8 Procurement
1.11.9 Creation of Credit Memos
1.11.10 Execution of Returns from the Customer
1.11.11 Job Management
1.11.12 Task Management
1.11.13 Order Split
PUBLIC Page 2 of 77
1.11.14 Pricing
1.11.15 Down Payment List
1.11.16 Start Collective Billing
1.11.17 Cancellation of Billing Documents in a DBM Order
1.11.18 Value Flows for Service Orders
1.11.19 Cash Desk Processing
1.12 Storage Goods Manager
1.13 Time Management
1.13.1 Recording of Time Events
1.13.2 Time Events Error Log
1.13.3 Automatic Clock-Off
1.13.4 Target/Actual Comparison in DBM Order
1.14 Incentive and Commission Management
1.15 Methods of Taxation
1.15.1 Standard and Margin Taxation
1.16 Archiving in DBM
1.16.1 Data Archiving
1.16.2 Pre-settings
1.16.3 Checks
1.16.4 Customizing
1.16.5 Dependencies
1.16.6 Residence Time
1.16.7 Initial Run Log
1.16.8 Archiving Log
1.16.9 Deletion Log
1.17 Transaction Codes in Dealer Business Management
PUBLIC Page 3 of 77
Dealer Business Management (IS-A-DBM)
Purpose
As a dealer management system, this component supports the industry-specific sales and services processes of dealers and dealer organizations, as well as
vehicle importers, authorized dealers, and OEM vendors. This includes handling of new and used vehicles sales, vehicle service, and parts
management.
The component is distinguished by its multi-brand capability as well as its ability to manage different locations. Customer-specific settings with regard to language
and country, such as currency and taxes, mean that it can be deployed worldwide.
The component supports the integration of processes between the dealer and the Original Equipment Manufacturer (OEM) within a vehicle order (vertical
integration). Furthermore, it also supports horizontal integration between dealers. For example, members of dealer organizations can obtain an overview of the parts
and vehicles in stock for the entire dealer organization.
As a dealer, you can manage an order from its creation, through its completion, and right down to its billing phase. Order control enables processes to be modeled
flexibly. In this way, you can meet different requirements that arise from the OEM or due to the size of a company. To ensure that country-dependent OEM
requirements are met, SAP provides relevant techniques such as Business Add-Ins (BAdIs) and the condition technique.
For reasons of simplicity, the term dealer is used in the following documentation; this term could, however, be referring to the car dealer or dealer
organizations, vehicle importers, authorized dealers, or OEM-dedicated vendors.
Integration
Dealer Business Management (IS-A-DBM) is fully integrated in the following SAP application components:
● Materials Management (MM)
● Sales and Distribution (SD)
● Financial Accounting (FI)
● Controlling (CO)
● Logistics – General (LO)
You can save warranty claims directly in the order. For this purpose, the component is integrated in Warranty Claim Processing (LO-WTY).
Since the Vehicle Management System (VMS) is the technical basis of the DBM vehicle object and the vehicle action control, you have to
define settings in Customizing for VMS because they apply to vehicles in DBM .
Note that in the documentation for VMS-specific settings, the terms vehicle model and material or material master are used as synonyms. In
DBM , however, a material is only part of a vehicle model.
You can assign the division representing the vehicle brand in the SAP System to an external manufacturer, by selecting Dealer Business
Management (DBM) ® Company Structure in Customizing for Logistics Execution . You can use the manufacturer, for example, to control the
interface or determine the labor value catalog.
Features
The component offers the following functions:
● For the customer
○ Customer data management
○ Processing of actions, for example, a mailing campaign
○ Processing of contacts, for example, sales calls, letters, telephone calls
○ Cross-matching
○ Customer credit limit check
● For the vehicle
○ Vehicle model management in the vehicle model master
○ Vehicle management in the vehicle master
○ Vehicle search
● For material and labor value
○ Material data management
○ Availability check for parts
○ Labor value management
○ Service package management
● For order processing
○ Creation and processing of DBM orders
○ Pricing
○ Processing of confirmations
○ Handling of goods movements and invoice receipts
○ Billing
○ Order Split
○ Printing of documents
○ Processing of returns and credit memos
○ Cash desk functions for sales of parts
PUBLIC Page 4 of 77
● For warranty processing
○ Creation and monitoring of warranty claims from the DBM order
○ Status check for parts to be returned
○ Recall check
1.1 Customer
Definition
A business partner with whom a business relationship exists, involving the issue of goods or services.
Use
You use this object to manage customer data. You can access the following information directly from the customer master record:
Vehicles Here, the system displays all vehicles assigned to the customer. You can branch directly
to the vehicle master record.
Order History Here, the system displays all DBM orders assigned to the customer.
You can branch directly to the order.
Sales Activities You can carry out the following actions here:
● Store and manage customer contacts (for example, letters, phone calls,
visits) with a reference to the employee (for example, service advisor,
salesman)
● Define partner functions (for example, a bill-to party, a ship-to party.
● Create texts for customers (for example, reports, notes)
● View customer fact sheet (information on, for example, classification, key
figures, agreements on shipping, delivery, billing, open items)
Fact Sheet Here, the system displays concise and clear information on customers (for example,
customer vehicles, DBM orders, open items).
Credit Info Here, the system displays the credit limit and the total open items for each company
code.
Activities and Complaints Here, the system displays the activities and complaints logged for the customer.
Storage Goods Here, the system displays the customers' storage goods (for example, tires).
You can manage one-time customers, such as passers-by, by using a one-time account in the customer master.
Structure
You can call important data for the customer in a condensed from in the DBM-specific transaction Customer Management (/DBM/VDXX). To create a customer
or change data, use the transactions Create Customer (VD01) and Change Customer (VD02) as standard. You can branch to these transactions directly from
the Customer Management .
You can enter the following data for the customer:
General Data For example, address, control data, payment transactions, marketing activities, contact
persons.
General data is of relevance to sales and accounting. They apply to all organizational
units within a client.
Company Code Data For example, accounting information, payment transactions, correspondence.
Company code data is of relevance to accounting and applies to the corresponding
company code. The creation of accounting data is the precondition for creating a DBM
order.
Sales Area Data For example: Sales and shipping data, billing documents, partner functions.
Sales area data is of relevance to sales and the creation of DBM orders, and apply to the
relevant sales area as a combination of sales organization, distribution chain and
division.
ETM Data Basic and settlement data for Equipment and Tools Management (ETM)
PUBLIC Page 5 of 77
You can use the Business Add-In BAdI: Enhance Customer Master to include own customer screens.
1.1.1 Customer Data Management
Use
Customer Data Management enables you to make use of several functions for maintaining and improving customer relationships. Effective customer management
can influence customer relationships from the initial contact, throughout the service cycle, up to the reconsideration of purchasing the next vehicle; it also ensures
customer loyalty and potential for growth.
Integration
Customer Data Management is integrated into DBM order processing via transaction Order Processing ( /DBM/ORDER) . You can call up the customer data
management from the order via Environment ® Customer Management . Use transaction /DBM/VDXX to call up this function directly.
Customer data management makes use of notifications. DBM notifications are based on the SAP standard notification.
You can use DBM notifications, for example, to process complaints, process maintenance requirements, and document malfunctions, exceptional circumstances,
or alerts. There are three notification types in DBM:
● D1 S Sales Activity
● D2 C Complaint
● D3 D Vehicle Damage Report
You can link the notification to the DBM vehicle master, DBM customer master, and the DBM order list.
If you create a notification for a vehicle, the system generates a record in the vehicle history.
You can define your own notification types for DBM in Customizing for Dealer Business Management (DBM) under Customer Data Management
® Notification ® Define Notification Types for DBM.
Prerequisites
● If you wish to use the notification functions in Customer Data Management, you should make the appropriate settings in Customizing for Dealer Business
Management under Customer Data Management ® Notification.
● You have entered enhancements and BAdI implementations for the standard notification in Dealer Business Management (DBM) and made settings to
enable the notification types Sales Activity - D1 , Complaint - D2, and Vehicle Damage Report - D3 . For further information, see Customizing for Dealer
Business Management (DBM) under Customer Data Management ® Notification ® Business Add-Ins (BAdIs) ® Notification Documentation.
● You have defined the style and layout of the fact sheet in Customizing for Dealer Business Management (DBM) under Customer Data Management ®
Dynamic Sheet.
● For the memo pad, memo texts are required. Each of the memo texts is implemented by using a specific content object. You can implement further content
objects with BAdI /DBM/BADI_CU_SHEET_CONTENT (BAdI: Content Object for Dynamic Sheet).
Features
Customer data management provides various features, such as:
● Customizable customer and vehicle fact sheet providing an overview of master data and documents
● Customizable memo pad with the option of maintaining informative customer and vehicle long texts
● Integration with other standard business objects (notification)
For each DBM notification type, you can define the possible outcome types and outcome codes and then assign these outcome types and codes to the
notification tasks. You can do this in Customizing for Dealer Business Management (DBM) under Customer Data Management ® Notification ® Define
Outcome Type and Outcome Code and Assign Outcome Type to Task Code.
● Functions for managing customer data and maintaining customer contacts.
From the SAP Easy Access screen, select Dealer Business Management ® Customer Management ® Customer Management (/DBM/VDXX).
● Functions for creating, changing, displaying, and deleting sales activities, customer complaints and maintenance requirements (by using notifications).
To access this function, select one of the following transactions from Dealer Business Management ® Customer Management ® Sales Activities and
Complaints on the SAP Easy Access screen.
○ Create Notification (IQS1)
○ Change Notification (IQS2)
○ Display Notification (IQS3)
If you wish to link your notification to the DBM order, you can also create and change DBM-type notifications from the transactions Create Order
(/DBM/ORDER01) and Change Order (/DBM/ORDER02).
You can also create notifications in the vehicle master via transaction Vehicle (/DBM/VM) and Goto ® Notification .
● Functions for documenting malfunctions, exceptional circumstances, and alerts (by using notifications)
● Functions for generating notification and task worklists.
To generate these worklists, select Dealer Business Management ® Customer Management ® Worklists from the SAP Easy Access menu (IQS8 for
notifications and IQS9 for tasks).
● Updating the DBM order document flow and the vehicle history with the DBM notification data
● The following five actions (task codes) that are linked to the notification tasks:
○ Internal Note
○ Send letter
PUBLIC Page 6 of 77
○ Send brochure
○ Log telephone call
○ Send e-mail
You can define your own actions (task codes) in Customizing for Cross-Application Components under Notification ® Notification Creation ® Notification
Content ® Maintain Catalogs ® Edit Catalogs. DBM uses catalog 2 Tasks and code group DBM Dealer Business Management.
● Functions for branching to the DBM order, memo pad, fact sheet, customer master, and vehicle master from the notification.
1.1.1.1 Notification
Definition
An object that allows you to record, process, and manage different types of information. This information, for example, may consist of simple inquiries to complex,
specialized problems.
Use
You can use notifications to process all types of information or problems that might be encountered in the business processes of your company. Among other
things, you can use notifications to carry out the following activities:
● Process complaints
● Process maintenance requirements
● Document malfunctions or exceptional situations in your company
● Process inquiries or problems in the IT area (for example, when using the SAP System)
● Process inquiries by or needs of individual employees over the Intranet
DBM notifications are based on the SAP standard notification.
You can create notifications from the transactions Create Order (/DBM/ORDER01) and Change Order (/DBM/ORDER02) . The notifications are assigned to
the DBM order.
You can create notifications from the vehicle master, the customer master, and transaction Order Processing (/DBM/ORDER). In these cases, the notification is
not assigned to a DBM order.
In Dealer Business Management (DBM), there are three notification types:
● D1 S Sales Activity
● D2 C Complaint
● D3 D Vehicle Damage Report
You can create your own notification types for DBM in Customizing for Dealer Business Management (DBM) under Customer Data Management
® Notification ® Define Notification Types for DBM .
Structure
A notification consists of the following:
● Subject
Here you can enter a long text, start and end dates and organizational data for the notification
● Notification history
Here you can see the historical overview of the notification regarding available activities, tasks and items
● Reference objects
Here you can enter information on the affected vehicle, for example.
● Tasks
You can enter tasks to be completed either in the notification header or with reference to an item.
● Actions
The following five actions are linked to the notification tasks:
○ Internal note
○ Send letter
○ Send brochure
○ Log telephone call
○ Send e-mail
In Customizing, you can specify your own tasks. You also have the option of setting follow-up tasks for a specific task type; the system creates these follow-up
tasks automatically when this type of task is created. You can add further details to a task by defining outcome types that can be selected for the specified task
type.
The action box is linked to the tasks: by clicking on an item in the action box, a task of the same type is either created under Tasks or changed if there was
already one in an incomplete status.
Integration
From the notification, you can branch to the following objects:
● DBM Order
● Memo Pad
PUBLIC Page 7 of 77
● Fact Sheet
● Customer Master
● Vehicle Master
1.1.1.2 Fact Sheet
Definition
An object that provides a quick overview on customer-related information, such as:
● Contact persons
● Basic data
● Vehicles
● Partner functions
● Marketing attributes
● Warranties
● Open recalls
● Credit information
● Vehicle orders
● Service orders
● Parts orders
● Notifications
● Invoices
Integration
You can display the fact sheet in the vehicle master by choosing Goto ® Fact Sheet, or from the DBM order by choosing Environment ® Fact Sheet.
1.1.1.3 Memo Pad
Definition
An object that deals with texts and especially with long text objects.
Use
The handling of long text objects is based on the SAP standard text framework in basis package STXD: the long text objects are saved in the basis tables STXH
(text header) and STXL (text lines).
The system displays the memo pad when you create a new DBM order. The memo pad displays vehicle-related information, such as:
● General customer data
● Open recalls
● Warranties
● Jobs within last service order
● Storage goods
● Customer text
● Vehicle text
The memo pad allows you to copy open recalls to the order, set the recall status to Done by 3rd Party, and copy warranties.
Integration
You can display the memo pad from the DBM order by choosing Environment ® Memo Pad.
You can customize the content, layout, and text attributes.
1.2 Vehicle
Definition
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 further information on 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.
PUBLIC Page 8 of 77
Use
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 further information on vehicle actions that can be performed in DBM, see Details for Vehicle Actions.
Using various function modules, you can adapt the DBM vehicles and use functions for the DBM vehicles. For further information on function
modules, see the Customizing for Dealer Business Management (DBM) under Interface Framework ® Function Modules ® RFC DBM
Vehicle .
Structure
In Customizing for DBM under Vehicle ® Navigation Vehicle Master , you can define which of the following data for the object Vehicle is displayed:
Data overview Here you can display all the important vehicle data in summarized form.
When you enter the mileage for the vehicle in the vehicle order, the 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,
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 further information on additional data, see Customizing for Logistics Execution
under Vehicle Management System (IS-A-VMS) ® Enhancements ® Define
Additional Data for Vehicle .
Model data 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.
Partner 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 by means of 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.
Approval Here you can enter registration data such as the type and date of vehicle registration, for
example. The mileage is updated.
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 Vehicle ® Vehicle
Master ® D efine Key Types .
Planned Maintenance Intervals You can define maintenance and service intervals, for example, for M.O.T. tests,
exhaust emission tests and general inspections.
PUBLIC Page 9 of 77
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 ® Vehicle
Master ® D efine Service Types .
Recalls The recall contains information about the technical fault and how to repair it (for example,
what tasks the mechanic has to perform, which parts are required, and 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.
You can use individual objects to enhance the vehicle master with additional vehicle data, in other words, with new screens and new fields.
You can store any documents in the Document Management System (DMS) directly from the master data for any vehicle.
The following Business Add-Ins (BAdIs) are available for the vehicle in Customizing for DBM under Vehicle ® Business Add-Ins (BAdIs) :
● Manage Vehicle Search UIs
● Control Vehicle Master APIs
● Manage Vehicle Order
● Manage Maintenance and Service Intervals for Vehicle
● Manage Vehicle Master UIs
● Manage Vehicle Master APIs
● Manage Vehicle Master UIs
● Control UI Standard Values for Vehicle Master
● Manage Reading of Control Values
● Control Vehicle Actions (VMS)
● Manage Vehicle Warranties
● Control Replacement Vehicle Search
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
Use
This function enables you to search your vehicle master for vehicles that fulfill specific criteria. Use transaction Vehicle Search (/DBM/VSEARCH) to start the
vehicle search in DBM. You can also find vehicles for processing an order, as this function is integrated into transaction Order Processing (/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)
Integration
You can use this search function in the vehicle master as well as in order processing. In the order processing, the vehicle search is available on the Order
Acceptance tab (search criteria on left) and on the Order Search tab.
PUBLIC Page 10 of 77
Prerequisites
You have been assigned to a role with vehicle models as a minimum, and you have stored vehicle master records in transaction Vehicle Master (/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
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 .
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
Action Control During Vehicle Processing
Use
This function enables you 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.
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 .
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 to be recommended only if you want to sort out 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 the 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 fine-tune the primary and secondary processes even more with different action controls. This means that processes can differ depending on the sales
organization or vehicle model, for example.
Activities
In Customizing for VMS, define the following by choosing Control Data ® Define Action Controls and Define Action Matrices :
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.2.1 Determination of Action Control
Purpose
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.
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 by using the SAP Easy Access screen via 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 Flow
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.
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:
a. Does the table contain an entry that matches the transaction Set Determination of Action Control (VELOS)? If so, the system uses this entry.
b. 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
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.2.2 Execution of Vehicle Actions
Use
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.
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 V ehicle 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.
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 always choose only 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 V MS 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
¡ 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.
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 Secondary Status
Create vehicle with internal order Vehicle created
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.2.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.2.3.1 Actions for Vehicle Procurement

The table below explains the vehicle actions that are relevant for the purchase order and incoming invoice:
Action Description Prerequisites Scope of Functions of Action Note
QORD Create Purchase Order (DBM) Vehicle to which you can assign Creates a purchase order for an This purchase order is not sent to
values, vendor existing vehicle the vehicle vendor because it does
The purchase order is required for not contain any information about
posting the goods receipt so that 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
processed in a third-party system
such as a dealer portal.
QMOR Change Purchase Order (DBM) Purchase Order Changes the delivery date of
Goods issue should not have purchase order items
been posted Performs pricing again
Deletes the item from the
purchase order
QDOR Delete Purchase Order (DBM) Purchase Order Deletes the entire purchase order
Goods issue should not have
been posted
QINV Create Incoming Invoice (DBM) Purchase Order Enters the incoming invoice There can only be one purchase
The goods receipt must have been manually order without an incoming invoice
posted for goods-receipt-based The system takes currency and for a vehicle. If there is more than
invoice verification payment conditions from the one, the incoming invoice for the
purchase order or purchasing info most recent purchase order is
record posted automatically.
You cannot create incoming
invoices for one-time vendors with
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:
QCRE Create Vehicle with Internal Creates a vehicle The internal order for the vehicle
Order (DBM) You define the vehicle as used controls all following internal
with business transaction USC: costs, such as refurbishments or
Used Vehicle. revaluation.
QCRV Create Vehicle This interlinking action creates a

vehicle (action QCRE) and an
internal order group (action
QIOG).
QMOD Change Vehicle (DBM) 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 used vehicle during a sales
regarded as one business 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 See: Action QTIP: Prepare

Repurchase of Vehicle.
QIOG Group Internal Order 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) Creates a goods receipt for the
used vehicle
QINV Create Incoming Invoice (DBM) Creates an incoming invoice The PO status changes to
invoiced.
QRCR Change Vehicle into Vehicle master record Converts the vehicle to a
Replacement Car replacement one that cannot be
involved in a sales process until
action QRCC is executed
QRCC Turn Replacement Car into Vehicle master record Converts the replacement vehicle
Normal Vehicle back into a normal one so that it
can be involved in a sales process
For more information, see Used-Vehicle Purchasing.
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
● Sales order
● Vehicle order
● Service quotation
● Service order
● Customer billing document
QOFF Create Quotation (DBM) The vehicle is assigned to the Is called if a vehicle quotation is In Customizing for DBM order
customer (QACU). created types, it is determined for the
In the VMS document table, quotation that this action has to be
creates a link between the vehicle performed when a quotation is
and vehicle quotation 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 Is called if a sales order is created
order 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 Is called if a vehicle order is
The vehicle is assigned to the created
customer (QACU). In the VMS document table,
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
QFOC Order Re-Open (Order Close The vehicle status must be Updates the vehicle status from This action is the counterpart
Cancelled) QS60( Sales Order Completed ) QS60( Sales Order Completed ) to/reversal of action QFOR. It is
to be able to execute this action. to QS50( Outgoing Invoice executed only when the vehicle
Created ) order is completely closed, and
Is executed in tandem with the subsequently reopened.
order action
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
and service order
QDSO Delete Service Order (DBM) Is called if a service order is

deleted for the vehicle
QOIV Create Customer Billing Is called if a customer billing
Document (DBM) document is created for the vehicle
order
and customer billing document
QOIR Cancel Customer Billing Customer billing document Is called if a customer billing
Document (DBM) document is canceled for the
vehicle
and cancellation document
The following table explains the actions that are relevant for internal service orders with revaluation:
QCPO CO Prod. Create (DBM) Creates a CO production order The counterpart to this action is
action QCPH (return).
QCPH CO Prod. Create Returns CO production order The counterpart to this action is
(DBM) action QCPO.
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) action QCCP.
QGRP CO Prod. Post Goods Receipt Posts the goods receipt from the The counterpart to this action is
(DBM) CO production order to the batch action QGRH (return).
QGRH CO Prod.Post Goods Receipt The counterpart to this action is

Return (DBM) action QGRP.
QSEP CO Prod. Create Settlement Settles the CO production order The counterpart to this action is
(DBM) against the batch action QSEH (return).
QSEH CO Prod. Create Settlement The counterpart to this action is

Returns (DBM) action QSEP.
QCLP CO Prod. Close (DBM) Closes the CO production order The counterpart to this action is
and sets the deletion flag action QCLH (return).
QCLH CO Prod. Close Returns (DBM) The counterpart to this action is

action QCLP.
QCOS Check Soldo of Internal Order
QLIO Complete Internal Order
QSVC CO Prod. Stock Value Change The counterpart to this action is

(DBM) action QSVH (return).
QSVH CO Prod. Stock Value Change The counterpart to this action is

Returns (DBM) action QSVC.
For more information, see Creation of Internal Service Orders with Revaluation.
1.2.2.3.3 Actions for Goods Movements

The table below explains the vehicle actions that are relevant for goods receipt and goods issue:
QGOR Create Goods Receipt (DBM) 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 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 Is called if a goods issue is created
order 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 It can be used only for goods
canceled in the vehicle order in issues that have been created with
order to update the vehicle history the action QGIS.
and status, for example
QGRP CO Prod. Post Goods Receipt CO production order, goods receipt Posts the goods receipt from the Used, for example, for internal
(DBM) CO production order to the batch service orders with revaluation
QGRH CO Prod. Goods Receipt Return CO production order, goods receipt Reverses the posting of the goods Used, for example, for internal
(DBM) receipt from the CO production service orders with revaluation
order
The table below explains the vehicle actions that are relevant for vehicle returns:
QROR Create Return Order Vehicle sales order Creates a vehicle returns order
QRGR Goods Movement for Vehicle Vehicle Creates a goods receipt for the
Return Vehicle returns order vehicle return
QRBD 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:
QCAS Create Fixed Asset for Vehicle Vehicle Creates a fixed asset
(DBM) Asset class, for example, asset
class 3100 for vehicles
QVTA Post Vehicle to Fixed Assets Posts the vehicle to the fixed
(DBM) assets
QVTD Create Fixed Asset and Post Creates a fixed asset and posts the You can combine actions QCAS
Vehicle 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:
QPGM Cross-Plant Goods Movement See: action QVTP
QVTP Transfer Between Plants Vehicle Transfers a vehicle from one plant This interlinking action contains
Quotation to another the following actions: QCIO
DBM sales order Create Internal Order, 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 Checks whether settlement rules
exist in the internal order
QROC Transfer Costs Vehicle master record 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
exist in the specified plant
QOIA DBM Order – All Billing Vehicle master record, customer Resets the vehicle to a pre-invoice
Documents Cancelled master record status
For more information, see: Transfer Posting of Vehicle Between Plants.
Transfer Posting Between Company Codes:
QVTC Transfer Between Company The vehicle to be transferred has Transfers a vehicle from one This interlinking action contains
Codes already been sold from one company code to another company the following actions: QCOS
company code to the other by code Check Saldo of Internal Order,
means of a DBM vehicle 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.2.3.4 Other Vehicle Actions

The table below explains the vehicle actions that are relevant for direct changes to vehicle data or customer assignment to the vehicle:
Action Description Prerequisite Scope of Functions of Action Note
QCRE Create Vehicle with Internal Configurable material Creates vehicle master record with
Order (DBM) 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
master record is changed, without Vehicle ® Assign Attributes to
a different action having been 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 You can change the notification
history each time a notification is 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 Vehicle master record, customer Cancels the assignment of a
(DBM) master record customer to a vehicle
Interlinked VMS Actions in DBM Vehicle Master
Use
You can use this function to trigger a sequence of multiple elementary actions, to avoid the need of 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).
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
● Receive incoming invoice
Vehicle Transfer Posting

There are various processes for making vehicle transfer postings in DBM. These are:
● Transfer Posting of Vehicle from Current Assets to Fixed Assets
● Transfer Posting of Vehicle Between Plants
● Transfer Posting of Vehicle Between Company Codes
Transfer Posting of Vehicle From Current Assets to Fixed Assets
Purpose
You can use this process to post vehicles from current assets to fixed assets and back again. You may wish to do this for the following reason:
If vehicles are used internally at a dealer as demonstration cars in the vehicle showroom, they should not be in the current assets. For depreciation reasons, they
should be transferred to the fixed assets. When the vehicles are no longer used as showroom cars, they have to be transferred back to the current assets, and a
valuation of the net book value takes place.
Prerequisites
You have checked that the following Customizing settings have been made:
In Customizing for the Vehicle Management System under Control Data :
● Define Actions (Overview) – you have maintained action QCAS (Create Asset for Vehicle (DBM))
● Define Actions (Overview) – you have maintained action QVTA (Post Vehicle to Asset (DBM))
● Define Actions (Overview) – you have maintained action QATV (Transfer Vehicle to Current Assets)
● Define Actions (Overview) – if you wish to create the asset and post the vehicle in one go, you have maintained action QVTD (Create Asset and Post
Vehicle) as an interlinking action
● Define Actions -> Interlinking Actions – if you wish to create the asset and post the vehicle in one go as stated above, you have entered actions QCAS
(Create Asset for Vehicle) and QVTA (Post Vehicle to Asset) as elementary actions for the interlinking action QVTD (Create Asset and Post Vehicle).
● Define Actions (Details) – you have defined actions QCAS, QVTA and QATV as secondary actions. Action QVTD is defined as a secondary action,
and if you wish to create the vehicle as an asset and post it in one go, also as an interlinking action. In this case, action QCAS must be set as an internal
action. The reason for this is that the user can start only the interklinked action and not the elementary one. However, if for some reason the interlinked action
breaks, the user still can continue by calling the rest of the elementary action from the interlinking set.
● Define Vehicle Status – you have maintained status QT05 (Asset Created), QT10 (Posted to Fixed Assets), and QT20 (Posted from Fixed Assets).
● Define Action Controls and Define Action Matrices – for action control (DBM), you have made the following settings for the action matrix:
Old Status Action New Status
Initial QCAS QT05
QT05
QT20 QCAS
Initial QVTD QT10
QT20 QVTD QT10
QT05 QVTA QT10
QT10 QVTA QT10
QT10 QATV QT20
QT20 QACU QS20
● If you want to be able to change the valuation class, you have ensured that you can do so by changing message number MM 326 to a warning message.
You can use transaction code OMT4 System Messages: Overview to do this.
Process Flow
1. You create a fixed asset for the vehicle by entering the business transaction (BT), cost center, asset class, and posting date.
To create a fixed asset in the system, you require an asset class. For vehicles, this asset class is 3100 in the standard system.
The system executes action QCAS Create Fixed Asset for Vehicle (DBM) and stores the asset number in the vehicle history.
The secondary vehicle status changes from Initial (Vehicle Received) to QT05 (Asset Created).
2. You post the vehicle to the fixed assets.
You do this by creating a goods movement to make a transfer posting for the vehicle to the fixed assets. Movement type 241 is used for this.
The system executes action QVTA Post Vehicle to Fixed Assets (DBM).
The vehicle status changes from QT05 (Asset Created) to QT10 (Posted to Fixed Assets).
1 and 2 above may be combined in the interlinking action QVTD Create Fixed Asset and Post Vehicle.
In this case, the secondary vehicle status changes directly from Initial (Vehicle Received) to QT10 Posted to Fixed Assets .
3. You transfer the vehicle from the fixed assets to the current assets.
The system executes action QATV Post Vehicle to Current Assets.
The secondary vehicle status changes from QT10 (Posted to Fixed Assets) to QT20 (Posted From Fixed Assets).
You can use BAdI /DBM/QCAS_EXECUTE to influence asset data.
You can use an implementation of BAdI VLC_CPGM_EXECUTE to make amendments to the valuation class of a vehicle, in other words, to
determine the valuation class when a vehicle is created and whenever a new valuation type is created for a vehicle, for example, when a vehicle
is changed from new to used.
Result
To display the asset movements, you can navigate to the asset master from the vehicle history.
Transfer Posting of Vehicle Between Plants
Purpose
You can use this process to post a vehicle in stock from one plant, or dealer’s branch, to another plant when the plants are in the same company code. You may
wish to do this, for example, if a customer at plant B wishes to purchase a vehicle that is currently situated at plant A. The following graphic illustrates this case:
Prerequisites
● The vehicle must be in stock before you can execute a transfer posting.
● No open DBM service orders exist for the vehicle.
● The sending plant and the receiving plant are in the same company code.
● There is no settlement rule in the internal order.
Process Flow
1. A customer decides on the required vehicle.
2. Salesperson A discovers that the vehicles assigned to plant A do not coincide with the customer’s wishes. However, another vehicle in plant B fulfills the
customer’s requirements.
3. Salesperson A telephones salesperson B to request permission to create a quotation and sell the vehicle.
4. Salesperson A assigns the customer to the vehicle.
The system uses the VMS action QACU (Assign Customer DBM) to do this.
5. Salesperson A creates a quotation and shows it to the customer.
The system uses the VMS action OFFE (Create Quotation) to do this.
6. The customer accepts the quotation.
7. Salesperson A creates a sales order.
The system uses the VMS action QCSD (Create Sales Order DBM) to do this.
8. So that the goods movement can take place and a goods issue can be created , interlinking action QVTP (Transfer Between Plants) has to be executed.
This action contains the following primary/elementary actions:
○ QCIO Create Internal Order
○ 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
You can only make changes to closed internal orders manually; there is no function to support this or to make cancellations within DBM.
Result
The vehicle has been transferred from plant A to plant B and sold to the customer from plant B.
You can check that the transfer posting has taken place by:
Displaying the vehicle master to check that the storage location and plant have changed automatically
Viewing the vehicle history to check that a material document, internal order and follow-on documents have been created.
Transfer Posting of Vehicle Between Company Codes
Purpose
You can use this process to post a vehicle in stock form one plant, or dealer’s branch, to another plant when the plants are in different company codes. You may
wish to do this, for example, if a customer at plant B, company code B wishes to purchase a vehicle that is currently situated at plant A, company code A. The
following graphic illustrates this case:
Prerequisites
● The vehicle must be in stock before you can execute a transfer posting.
● There are no open DBM orders for the vehicle.
● The vehicle has been sold with a DBM vehicle order to the other company code.
● The balance on the internal order is zero.
Process Flow
This scenario is based on the following assumptions:
○ the customer quotation and the sale of the vehicle to the customer take place in an external system.
○ the DBM sales process is used for the transfer between company codes, not standard transfer posting functions. In other words, the vehicle must be sold
from one company code to the other by means of a DBM vehicle order. This is for reasons of flexibility in pricing By using the DBM sales process, the
dealers can decide on the sales price themselves
○ before the salespersons telephone each other, the sale between the company codes has already taken place. In other words, the vehicle cannot be sold
to the customer before it has been transferred between company codes.
1. A customer decides on the required vehicle.
2. Salesperson B discovers that the vehicles assigned to plant B and company code B do not coincide with the customer’s wishes. However, another vehicle in
plant A and company code A fulfills the customer’s requirements.
3. Salesperson B telephones salesperson A to make a deal.
Settling of the balance of the internal order in company code A is carried out manually by using transaction codes KO02 (Change Internal Order) and KO08
(Data Transfer for Order Master Data).
4. Salesperson A, company code A sells the vehicle to salesperson B, company code B by means of a DBM vehicle order.
The system executes VMS interlinking action QVTC (Transfer Between Company Codes), which contains the following elementary/primary actions:
QCOS Check Saldo of Internal Order
QCIO Create Internal Order
QIOG Group Internal Order
QISV Initialize Vehicle Status
5. Salesperson A creates a sales order and thus also the ensuing billing documents.
On the receiving plant side, you execute the VMS actions for creating a purchase order and creating/posting a goods receipt separately after the
vehicle has been transferred between the company codes.
The creation of a quotation is an optional step since the customer has already bought the vehicle.
If transport costs are involved, they can be billed by including them as an order item in the vehicle sales order.
The sales action between company codes cannot be cancelled. You would have to execute another transfer posting in the reverse direction if you
wanted to undo the transfer.
Result
The vehicle has been transferred from plant A, company code A to plant B, company code B and can then sold to the customer from plant B, company code B.
You can check that the transfer posting has taken place by:
■ Checking that the company-specific data has changed
■ Viewing the vehicle history to check that a new internal order has been created, in other words, that a vehicle posting has taken place.
1.2.4 Used-Vehicle Purchasing
Purpose
You can use this process to handle the purchasing of used vehicles. Used-vehicle purchasing consists of two main scenarios:
● The (re-)purchase of rental cars, company cars, and leasing cars by the OEM, National Sales Company (NSC), or the dealer, or free purchasing of used
vehicles by dealers (independent of new vehicle sales)
● the purchase of used vehicles: for profitability reasons, a dealer may wish to buy a customer’s old vehicle as part payment for a new vehicle bought at the
dealership
Prerequisites
● You have assigned users to a VMS role.
● You have created a vehicle model.
● You have followed the steps listed in the DBM Configuration Guide.
● To enable the use of notifications for damage recording in the used-vehicle scenario, you made the appropriate standard settings in Customizing for Cross-
Application Components under Notification .
● You have checked the settings in Customizing for Logistics Execution under Vehicle Management System ® Control Data .
Process Flow
1. Either the vehicle already exists in the system as it was sold in the past, or you create a new vehicle in the system and identify it as a used vehicle (action
QCRE: Create Vehicle with Internal Order (DBM)), vehicle business transaction USC: Used Vehicle) .
You maintain the vehicle configuration data. The internal order for the vehicle controls all following internal costs, for example refurbishments or revaluation.
2. You valuate the vehicle and determine the price of the used vehicle (action QMOD: Change Vehicle (DBM) ).
The actual determination is performed externally; in DBM you note the results returned from the external source. You can do this in the vehicle master under
Vehicle Prices.
3. If no vendor record exists yet, you create one. This means that you create a vendor master for the customer from whom you shall purchase the used vehicle.
This is necessary in order to represent the associated purchasing processes and their documents in the system.
4. You record any vehicle reductions. There may be reductions to the price of the vehicle due to:
○ Missing handover articles, such as a service booklet or vehicle keys (action QMOD: Change Vehicle (DBM) ).
The system stores information on missing handover articles in the vehicle master and then copies it to the purchase order. For further information, see
Example: Handling of Missing Handover Articles.
○ Damages to the vehicle (action QNTF, Create Notification ). The system executes this action when you choose Notification in the vehicle master and
then select notification type D3 (Vehicle Damage Report).
The system stores information on damages in a notification and then copies it to the purchase order. If you have entered a short text for the notification
item, the system also copies this text to the PO. For further information, see Example: Handling of Damages.
5. If the purchase of the used vehicle is part payment for a new vehicle, you link the entries you have made to the new vehicle (action QCHN: Create Vehicle
Chain ).
When this action is executed, the dealer costs incurred by the used vehicle are added to the cost of the new vehicle sale. For further information, see:
Example: Pricing in Used-Vehicle Purchasing.
6. If you created a used vehicle in step 1, you create a purchase order for the used vehicle (action QORD: Create Purchase Order (DBM) ).
If the vehicle already existed, you execute action QRPU (Repurchase Used Vehicle) . This action contains actions QTIP (Prepare Repurchase), QIOG
(Group Internal Order) and QORD (Cre ate Purchase Order (DBM)).
7. You create a goods receipt for the used vehicle (action QGOR: Create Goods Receipt (DBM) ) and post it.
When the vehicle arrives at the dealer’s location, it can be inspected and checked for missing handover articles or damage again. This data is then recorded
(by updating the missing handover articles in the vehicle master and/or by either updating the damages in the notification or creating a new notification of type
D3 ) and the purchase order is updated accordingly (action QMOD: Change Vehicle (DBM) ).
8. You create an incoming invoice (action QINV: Create Incoming Invoice (DBM) ).
The PO status changes to invoiced.
You can implement various Business Add-Ins (BAdIs) to make amendments to the valuation class of a vehicle. This means to determine the valuation class you
want to use whenever you create a vehicle and a new valuation type, for example when changing a vehicle from new to used .
Result
You can now calculate the gross profit margin incurred by the purchase of the used vehicle by calling transaction code /DBM/VM_GPA Gross Profit Analysis
and entering the appropriate criteria in the selection screen of the report.
Example: Handling of Missing Handover Articles
You deal with handover articles in the system by using options/features in the model and vehicle master.
The following example clarifies how missing handover articles are handled during the purchase of used vehicles:
1. Model Master (as template):

Model: XYZ
missing door key € -100,-
missing service booklet € -150,-
missing radio key € - 80,-
The model master contains the model XYZ. For this vehicle model, there is a list of expected handover articles, including the price reductions if the articles are
missing.
Provided the option (article) has been defined as relevant to copying, the system copies this data from the model master to the vehicle master when you create a
used vehicle (vehicle business transaction USC : Used Vehicle ). If a vehicle already exists in the system, you must add the missing handover articles
manually.
2. Vehicle Master(containing the data copied from the model master or added manually):
Vehicle VIN 4077
missing door key € -100,-
missing radio key € - 80,-
You make manual adjustments according to which articles are missing or not.
3. Vehicle Master(changed by user):

Vehicle VIN 4077 € 6000,-
missing door key € -100,- x
The €6000 represents the trade-in price, provided the vehicle comes complete with all articles.
A door key is missing, but you have set the Not PO Relevant flag for it because this is deemed to be irrelevant to the purchase order. The price of the vehicle is
therefore not reduced by the cost of the key.
The service booklet is missing, and relevant. The price of the vehicle is therefore reduced by the cost of the service booklet.
You have removed the radio key from the list as it is not missing.
Provided you have set the indicator defining the articles as relevant to the purchase order, the system copies this data to the purchase order when the latter is
created.
4. Purchase Order(created on the basis of the vehicle master):

Vehicle VIN 4077 € 6000,-
The final price contained in the purchase order would be €6000,- minus € -150,- = €5850.
1.2.4.2 Example: Handling of Damages
The following example clarifies how damages are handled during the purchase of used vehicles.
The purchase order that is created reflects the fact that the used vehicle has damages:
Notification D3, July 10th, 2006 / 80.573 km
Location Type Number Markdown
left front door scratches 4 €100,-
right back fender rust 2 €250,-
left front seat holes 1 €80,-
A little while later, the vehicle acquires more damages and the purchase order is changed to reflect this. You can do this by creating a new notification or by
updating the existing one:
Notification D3: August 16th, 2006 / 81.974 km
Location Type Number Markdown
left front door scratches 6 €150,-
right back fender rust 2 €250,-
left front seat holes 2 €160,-
When the used-vehicle purchase order is created, the system only takes the most recent notification (type D3 Vehicle Damage Report ) into
account. It ignores all previous D3 notifications on the assumption that the most recent damage report provides the most accurate description of
the vehicle damages.
Example: Pricing in Used-Vehicle Purchasing
The following example clarifies how pricing in used-vehicle purchasing is handled.
Vehicle Master:
(Set type DBM_V_IPRICES)
Purchasing Price Estimated: €22 000 15.08.06
Purchasing Price Aimed: €20 500
Sales Price Estimated: €24 000 15.08.06
Sales Price Aimed: €24 500
Missing Handover Articles:

(Set type DBM_V_IOPTIONS)
Missing Car Key €100
Missing Service Booklet €150
Missing Warning Triangle €20 (Not relevant to PO)
Service Notification D3:

Scratches Left Front Door €800
Rust Right Back Fender €650
Holes Left Front Seat €200
Purchasing Price Estimated -> Preliminary PO Price
Purchasing price (estimated) €22.000,00
- Damage €800,00
- Damage €650,00
- Damage €200,00
- Missing car key €100,00
- Missing service booklet €150,00
Preliminary PO price €20.100,00
Purchasing price (aimed) €20.500,00
- Preliminary PO price €20.100,00
Dealer Cost €400,00
Purchasing Price Estimated -> Aimed PO Price
Purchasing price (estimated) €22.000,00
- Damage €800,00
- Damage €650,00
- Damage €200,00
- Missing car key €100,00
- Missing service booklet €150,00
+ Dealer Cost €400,00
PO price (aimed PO price) €20.500,00
Additional items are created in the purchase order for missing handover articles. Vehicle damages are handled as conditions on vehicle item
level. This means that whilst missing handover articles only reduce the vehicle purchase price, damages not only reduce the purchase price but
also the value of the vehicle in stock (vehicle valuation type).
Action QTIP: Prepare Repurchase of Vehicle

Below is a description of how action QTIP (Prepare Repurchase) changes and/or deletes vehicle data. There are two cases.
A)
A vehicle that is repurchased might already exist in the system as it might have been sold as new vehicle some time back. In this case, you do not have to
create a new vehicle record. Instead, action QTIP converts the existing new vehicle into a used vehicle.
This action deletes and changes the vehicle data as follows:
● Changes the vehicle business transaction type from new (NEC) to used (USC) in the vehicle master table.
● Deletes organizational vehicle sales data (sales organization, distribution channel) from table VLCVEHICLE (VELO: Vehicle). This data is reassigned when
the vehicle is assigned to a customer again by using the vehicle action QACU Assign Customer (DBM).
● Deletes the vehicle customer number and the vehicle partner data. This data is also reassigned by action QACU Assign Customer (DBM).
● Changes the valuation class of the vehicle from new to used.
● Does not automatically change or delete the vehicle registration number or any existing vehicle registration history records. You should create a new
registration history record of registration type 02 (deregistration) when the vehicle is repurchased.
● Does not clear the Vehicle Usage field in the data overview of the vehicle master. The field is automatically filled by a VMS action in accordance with your
Customizing settings.
● Allows you to change the Margin Taxation field.
● Clears the vendor as the last vendor (importer or manufacturer in the case of a new vehicle).
● Clears the Sales Date field.
● Vehicle options with prices might have been used in the original new vehicle purchase order sent to the OEM. As the vehicle options are not relevant for
used- vehicle purchase pricing, the flag indicating non-relevance to the purchase order is set for such options. Similarly, the new vehicle options and prices
are also irrelevant for the sales order. Therefore, sales-order-relevancy flags are also set accordingly.
B)
A vehicle that is repurchased as a used vehicle may already exist as a used vehicle in the system. Even if the vehicle is already used, some additional steps
are still required to prepare it for repurchase. Some of the steps required in the new to used transformation are not necessary. The list below mentions the
differences and/or similarities:
● Business transaction type remains USC
● Organizational data is deleted
● Partner data is deleted
● The valuation class remains the same because the vehicle is already a used
vehicle.
● Vehicle registration data: as above
● Vehicle usage: as above
● Margin taxation: as above
● Vendor: as above
● Sales date: as above
● Relevancy of options to the purchase order: as above
As the vehicle is already a used one, the data is most likely to be correct already.
In both cases A and B above, a new internal order is usually created. Batch and valuation class need to be handled. There are two cases for this:
● The vehicle is repurchased by the plant that last sold it
In this case, the batch and valuation type can remain as they are. The only required change is the valuation class assigned to the valuation type. The
valuation class is used to differentiate used vehicles from new vehicles in Financial Accounting and/or Controlling. You can only change the valuation class
for a valuation type as long as the vehicle is not in stock.
● The vehicle is repurchased by a different plant
In this case, the valuation class is set to Used . Furthermore, the batch and valuation type for the vehicle may not yet exist in the plant, unless, for example, a
plant transfer was carried out at some time in the past. If this information is not yet available, it is created for the vehicle in this plant.
1.2.5 Vehicle Chain Business
Use
You can use a chain to link two vehicles that are otherwise handled independently but are not considered as individual transactions with respect to purchase and
sales. In practice, this occurs, for example, when a customer sells a used vehicle to a dealer as a part of payment for a new vehicle. The vehicles are linked by
one internal order group.
Prerequisites
If you want to use the report for analyzing the gross profit (transaction /DBM/VM_GPA), the sale process must be complete.
Features
● Create vehicle chain
The chain is generally created between the new and used vehicle, but it could be between two used vehicles or two new vehicles (action QCHN Create
Vehicle Chain). You can execute this action for the new vehicle and create the chain to the used vehicle, or you can execute the action on the used vehicle
and create the chain to new vehicle. In both cases, there is only one internal order group for both vehicles.
A chain can be open, in which case only one vehicle in the chain has been sold, or closed, in which case both vehicles in the chain have been sold.
There can be no more than two vehicles in the chain.
The system does not store the internal order group of the vehicle in the vehicle data.
● Report for gross profit analysis
Provided the sales process is complete, The report displays the following data:
○ Purchase price including tax (from the associated MM-incoming invoice or credit memo)
○ Tax at the time of purchase (from the associated MM-incoming invoice or credit memo)
○ Additional costs (from the associated CO internal order - only the relevant cost elements)
○ Stock value (purchase price plus additional costs minus tax at the time of purchase, stock value from the MM document)
○ Sales price including value-added tax (from the associated SD sales document)
○ Tax (7,6% or marginal tax from the SD sales document)
○ Revenue (sales price minus tax minus items that do not affect the revenue).
○ These items can be determined by using the condition type.
○ Net income (revenue minus stock value and possibly minus additional costs)
○ Gross profit (net income divided by revenue, percentage value)
Activities
Create vehicle chain
In change mode of the vehicle master, choose Actions, then Create Vehicle Chain.
If a chain already exists to this vehicle, the system displays a dialog box in which you can chose whether to delete the existing chain or not.
In the Int. Veh. No. field, enter the internal number of the vehicle to which you wish to create the chain.
Save your entries.
Report for gross profit analysis
If you wish to run the report for analyzing gross profit, enter transaction /DBM/VM_GPA ( Gross Profit Analysis ) and the required data on the selection screen.
You can choose whether you wish to display data for vehicles in an open or a closed chain.
1.2.6 Vehicle Returns
Purpose
You can use this process to return a vehicle, including its accessories, after it has been sold. The customer may wish to return the vehicle to the dealer, for
example, if the vehicle has a defect.
Prerequisites
● The vehicle has been sold.
In other words, a vehicle sales order exists; the vehicle returns order has to be created with reference to this vehicle sales order.
● In Customizing for Dealer Business Management under Order ® Order Type ® Define Order Type , you have checked that the DBM document category
H is set for the vehicle returns order (order type 3100 ).
Process Flow
1. The service manager or service advisor creates a returns order in one of the following ways:
○ By calling up transaction Copy Order (/DBM/ORDER05) for the reference vehicle sales order for which the returns order is being created
○ By calling up transaction Vehicle Search (/DBM/VSEARCH) and using the function Order and then Copy in the vehicle master
○ By calling up transaction Order Processing (/DBM/ORDER) on the overview screen for the DBM order by using the function Copy
The system executes the VMS action QROR (Create Return Orde r ) .
Status QR10 (Return Order Created ) is assigned to the vehicle.
The document flow of the vehicle returns order shows the vehicle sales order as a reference document in the DBM order via Goto ® Document Flow .
2. The service manager or service advisor creates a goods receipt for the vehicle.
The system checks whether this goods movement is allowed for the vehicle return. If the return is not allowed, the system displays an error message. If the
return is allowed, the system executes the VMS action QRGR (Goods Movement for Vehicle Return) .
The vehicle has the status QR15 (Goods Receipt Done) .
3. The service manager or service advisor creates a billing document.
The system checks whether the creation of a billing document is allowed. If it is not allowed, the action returns an error and thus prevents further processing. If
it is allowed, the system executes the VMS action QRBD (Create Invoice for Vehicle Return) .
Status QS20 (Customer Assigned ) is assigned to the vehicle.
Result
The vehicle returns order has been processed, the VMS status of the vehicle returns to QS20 Customer Assigned and you can create a new vehicle sales order.
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
For more information about the individual function modules, see transaction SE37 Function Builder .
1.3 Vehicle Model
Definition
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.
Use
You can use this object as a basis for creating vehicles. In the vehicle model master for a vehicle model, you enter information about which features classes are
possible for the model, for example.
The system copies the standard features possible from the vehicle model to the vehicle data. Using the input help, you can choose additional data such as
optional extras, colors, and accessories. The system copies the values for the input help from the model data. You can also enter values for the vehicle that do not
exist in the vehicle model master.
Sales and distribution processing for a vehicle model is controlled by the sales code. The sales code provides the integration to documents, such as quotations
and orders. Service processing for a vehicle model is controlled by the service code.
Using various function modules, you can 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 Interface Framework ® Function Modules ® RFC Vehicle Model.
Structure
The model catalog is the central element in processing of vehicle model masters. You process all vehicle models and their features within a model catalog.
Using the criteria technique, the system determines the model catalog that is valid. The default values offered for the vehicle models and their respective features
come from this model catalog.
In the standard system, the model catalog is assigned the combination of division and country, and is determined accordingly.
You can enter and display the following data for the object:
Model data You enter the sales code and the service code and can enter other information that has no
controlling effect.
You can set the model and the other vehicle features to inactive so that they can no
longer be used actively in the order process.
Texts You can enter text for the vehicle model.
Prices You can define purchase prices and sales prices for the vehicle model.
Material data You enter the material master record that belongs to the vehicle model.
Features You can specify the vehicle features possible for a vehicle model. In the vehicle master
record, only the features belonging to the appropriate vehicle model can then be chosen.
The following Business Add-Ins (BAdIs) are available:

● Control Vehicle Model Master APIs
● Control Vehicle Model Master UIs
Integration
Vehicle Model Data Creation With Creation Of A New Material

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.
On the model master screen, you can display the model texts 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.
For more information about the use of material master records in the vehicle model, see SAP Note 1258776.
1.3.1 Assignment of VMS Roles
Use
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 him or her explicitly on the basis of a role with vehicle models.
Prerequisites
In Customizing for the 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.
Both of a dealer's sellers are to sell different vehicle models: one seller only model A, and the other only model B. The dealer assigns the two
sellers different vehicle model roles.
· 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
the Customizing under Logistics Execution ® Vehicle Management System (V MS) ® Vehicle Search ® Vehicle Search Areas.
Activities
1. Assign the vehicle model roles to vehicle models (transaction: VELORM - Assign Vehicle Model ).
2. Assign one or more vehicle model roles to each user and, if you wish, also an organizational role (transaction VELORU - Assign User Roles ).
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
/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
For more information about the individual function modules, see transaction SE37 Function Builder .
1.4 Part
Definition
A material that can be installed in a vehicle.
Use
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.
Using various function modules, you can adapt the parts and use functions for the parts. For further information about function modules, see
Customizing for Dealer Business Management (DBM) under Interface Framework ® 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 (Indicator)
○ Return part (part to be returned)
○ Retention obligation
○ Subject to disposal
○ Check for multiple entry of parts items in the order
● 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.
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 form 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.
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.
Creation of Material from Original Parts Master
Use
You can use this function to create a material master from the original parts master by using a reference material.
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. To access the function for creating a material from the original parts master, enter the transaction code /DBM/MMXX.
2. The system displays a selection screen with the following subscreens:
a. 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.
b. 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.
c. 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.
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.2 Stock Information
Use
You can use this function to check stock and display a stock overview for the current plant, a nearby plant, or an external system.
Integration
You can display this stock information on the Procurement subscreen of the Parts tab page of the DBM order.
Prerequisites
In Customizing for Dealer Business Management (DBM) under Part ® Stock Information you have:
● defined search keys and their descriptions for the stock inquiry.
You can then use these search keys for the purpose of creating a relationship between plants (see next prerequisite) and thus restrict the stock inquiry for a
part in the DBM order to the plants that you choose.
● assigned search keys and nearby plants.
The relationship between plants that you define restricts the stock inquiry for a part in the DBM order. If you do not make any settings here, the system calls
transaction code MMBE without any restrictions.
If you wish to check stock in an external system, you must implement BAdI /DBM/BADI_STOCKQUERY BAdI: Stock Information from External
System.
Features
You can use this function to:
● Check stock in your own plant
The system checks the stock in the current system.
● Check stock in nearby plants
The system checks the stock in the plants you have defined as being nearby in the Customizing activity Assign Search Key and Nearby Plants.
● Check stock in all plants
The system checks the stock in all the plants that have been entered in the system.
● Check stock in an external system
By means of BAdI /DBM/BADI_STOCKQUERY BAdI: Stock Information from External System, the system checks the stock in an external system.
The Stock Information function does not perform an availability check.
1.5 Labor Value
Definition
A measurement of work that can be defined, amongst other things, by the following values:
● Labor value number
● Description
● Target time for labor value
● Pricing reference material
● Labor value main type
Use
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.
In Customizing for Logistics Execution under Dealer Business Management (DBM) ® Service ® Labor Value ® Catalog Determination ®
Assign Criteria , you can assign more than one catalog ID to an OEM.
You can assign the division representing the vehicle brand in the SAP System to an external manufacturer, by selecting Dealer Business
Management (DBM) ® 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.
Using various function modules, you can adapt the labor values and use functions for the labor values. For more information about function
modules, see the Customizing for Dealer Business Management (DBM) under Interface Framework ® Function Modules ® RFC Labor
Values .
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 of a labor value in Customizing and is represented by its ID code.
If the hierarchy level has two characters, the following labor values could belong to the labor value group 17 Engine Lubrication:
■ 17030100 Check oil pressure
■ 17051900 Remove and install oil pressure switch
■ 17071900 Remove and install oil temperature sensor
For further information on labor values, see the DBM Configuration Guide on the SAP Support Portal under Release and Upgrade Info ® Installation and
Upgrade Guides ® Industry Solutions ® Industry Solution Guides ® SAP for Automotive.
1.6 Package
Definition
A group of items, for example, parts, labor values, and external services that are required for a specific task.
Use
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 often 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.
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:
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.
Normally, 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 Service ® Package ® Define Number Range for DBM Package, you can
assign the package type to a number range for the package ID.
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.
You can use the Business Add-in BAdI: Package Search to make any enhancements and restrictions you may require for the package search.
1.6.1 Package Maintenance
Use
The functions in 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
● 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 whilst 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
To make settings for the package functions, select Service ® Package in Customizing for Dealer Business Management (DBM).
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 Interface Framework ® Function Modules
® RFC Package.
1.7 Recall
Definition
A document that the OEM sends to dealers to inform them about technical faults that need rectifying in vehicles that have either already been shipped (and are
located on the dealer’s premises) or have already been sold to the end customer.
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).
Use
The OEM sends a recall to the dealers affected to inform them about which vehicles are concerned and what has to be done; the recall is saved in the local dealer
system and created as a recall object in the Automotive Warranty solution.
The OEM triggers the creation of a recall containing header data and the object list (list of vehicles affected) by an interface; the OEM may also
send repair instructions, for example, by email. An internal employee at the dealer’s processes this recall manually, by entering the required
labor values and parts, for example, by hand.
Structure
A recall consists of the following parts:
● General information on recalls:
○ Recall number
There is an internal recall number that is assigned by the DBM system and an external recall number that originates from the OEM. This external recall
number is important for communication between OEM and dealer and also to be able to identify the recall for the tasks to be performed in the workshop.
This number can be found on the repair instructions for the mechanic, for example.
○ Valid-from and valid-to dates
○ Who created and last changed the recall
○ Information text
● Recall header data:

○ Partner, OEM
○ Defect code
○ Recall priority: high, standard, low
In the case of high priority recalls (for example, recalls relating to safety), the owners of the vehicles receive a letter from the dealer that they should bring their
vehicles for repair. Less serious faults are often repaired on the side when the customer brings the vehicle for inspection or for other reasons.
If repair instructions are sent as an accompanying document, you can attach them to the recall by selecting Business Document Navigator.
● Item overview:
You can list parts items and labor value items that are required for the repair. The system also supports text items.
● Item detail
You can enter detailed information on the items in the recall. Pricing data is not supported. For more information, see SAP Note 996655.
● Objects
Recall objects can be of type VELO (vehicle), object ID type DBMVI.
You can use a list of individual VINs, but no intervals.
For further information on the object ID type, see SAP Note 996566.
Integration
You can create a recall in one of the following ways:
● Manually, using the SAP Easy Access screen via Dealer Business Management ® Warranty ® Recalls ® Edit Recalls (WTYRCL)
● by triggering the creation of the recall in the SAP system by use of an interface to the dealer’s system where the recall is stored. You can do this by using the
Business Application Programming Interface (BAPI) function module BAPI_WARRANTYCLAIM_CREATE.
For current recalls (status Open ), you can copy the recall data to the service order.
When you create a new service order for a specific vehicle, the system checks whether relevant recalls exist. If so, the memo pad displays a list of these recalls,
from where you can branch to each specific recall object to get more detailed information.
You can display previous recalls (status Closed ) and also current recalls in the vehicle master (transaction /DBM/VSEARCH).
You can branch to functions provided by the Document Management System (DMS) by choosing Business Document Navigator in the recall.
1.7.1 Recall Processing
Purpose
You can perform the following activities with this process:
● Create recalls
● Edit recalls
● Check recalls in the order transaction
● Set recalls to status Recall Done by Third Party
● Copy recalls to the service order
● Cancel recalls from the service order
● Close recalls.
You use a recall to inform dealers about technical faults in vehicles that have already been shipped. You can also include information on how to repair the fault in
the recall.
Prerequisites
● In Customizing for Logistics Execution under Dealer Business Management (DBM) ® Service ® Recall ® Define Order Type and Warranty Category
for Recalls , you have defined, for each OEM, the DBM order type and warranty category for which you wish to use the recall functions. When you copy a
recall to an order, the system uses this information as input for the automatically-triggered order split.
● On the SAP Easy Access screen under Dealer Business Management ® Warranty ® Recalls ® Assign Item Type and Item Category to OEM
(/DBM/WTYRCLITEM), you assigned the recall item type (part: MATC, labor value: FRC, text: TEXT) to the DBM item category for the manufacturer.
● At any one time, irrespective of the recall status, the number of vehicles with a recall in the database does not exceed 99 999 (table WTY_RCLOBJ can
store a maximum of 99 999 objects).
Process Flow
1. You create a recall of type CDBM (DBM Recall).
You can create a recall manually by using transaction Edit Recall (WTYRCL) or, more usually, the recall is triggered via the interface. If the latter is the
case, you can edit the recall manually later on the basis of repair instructions. Enter the following data:
○ General information and header data:
External recall number, valid-from and valid-to dates, information text, recall priority, partner (OEM), and defect code.
The system automatically assigns an internal number to the recall.
○ Item Data:
Item type (labor value: FRC or material/part: MATC), material number, key (material number or labor value key with labor value catalog), amount with the
appropriate unit, and the flag for part causing damage.
The item type, key, material number, and amount fields are required-entry fields.
○ Details for the items
○ Objects:
Here you can enter the vehicle identification number (VIN), for example.
You must list vehicles with their individual vehicle identification numbers (VINs). You cannot use intervals. For more information, see SAP Note
932947.
○ Documents:
You can attach further documents, for example repair manuals, by using functions provided by the Document Management System (DMS). Select
Business Document Navigator to do this.
Save your entries.
The recall has the status 1 Open.
You can check the recall in the vehicle master. When you choose the Recalls view, you should be able to display the recall with the status Open.
At this point in time, the recall is read and displayed dynamically; it has not yet been stored in the vehicle database.
2. You check the recall.
When you create a new service order for a specific vehicle, the system checks whether open recalls relevant to this vehicle already exist. If so, the memo
pad displays a list of these recalls; from this list, you can branch to the recall data and to attachments for the recall, for example, repair instructions.
The recall dialog box contains a column displaying the sum of the labor values; this is important information for employees scheduling the servicing
appointments. This information provides an indication as to whether the recall tasks can be performed as required.
3. If the recall work has already been performed, you can set the recall to Recall Done by Third Party.
Dealer A and dealer B both receive a recall for a specific vehicle model. The customer takes his vehicle to workshop A, the work is performed
and the recall status is set appropriately. Later, for another reason, the customer takes the vehicle to workshop B, where the recall is still open.
Workshop B can set the recall status to Recall Done by Third Party.
4. You copy the recall to service order.
If a recall already exists, you can (automatically) copy the recall data to the DBM order. You can do this either by choosing the recalls you wish to copy from
the memo pad, or you can choose the recalls you wish to transfer to the order after you have entered the order in the recall subscreen. Copy the recall to
service order from the order processing transaction, Copy Recall . When you trigger this transfer, the recall data is copied to a new job (with all recall items)
and the job is then split 100% to the OEM. The system generates and saves a warranty record together with a reference to the recall. This, together with the
status information In Process, is saved in the corresponding vehicle master when the DBM order is saved.
The system uses the split order type and the warranty category that you have assigned in transaction Assign Item Type and Item Category to OEM
(/DBM/WTYRCLITEM), and the DBM order item categories from the customizing settings for Dealer Business Management (DBM) under Service ®
Recall ® Define Order Type and Warranty Category for Recalls .
The recall has the status 3 ( In Process ).
The mechanics or service technicians read the repair instructions, work on the recall, and add or delete labor values or parts items as required. They may
also discover that the recall fault has already been corrected, in which case, they would cancel the recall and then set the recall to Recall Done by Third
Party .
5. You cancel the recall.
In some cases, you may have to remove the recall from the service order. You may wish to do this, for example, if some parts are not yet available and the
recall is therefore going to be handled at a later date with a separate order, or if the fault has already been rectified. In this case, you have to delete the
warranty record manually from the order. You can do this by deleting the warranty data in the order processing transaction. The system deletes the link
between the recall and the service order (action WTYD_ORDER_DELE, Delete Warranty Data ). The system deletes the recall reference in the vehicle
master.
The recall has the status 1 Open again.
Further processing takes place as a normal service order warranty process.
You still have to delete the split, job and items manually from the warranty data view of the service order even after the link between the recall and the order
has been deleted (cancelled).
6. You close the recall.
If the recall has not been cancelled, the mechanic completes and releases the job and set the technical status for the job (you can find this at the Job tab,
action RECALL_CLOSE, Complete Recall ). For the same vehicle, you cannot copy closed recalls to future service orders; however, a recall can be
complete for one vehicle, but still open and in process for another vehicle.
The recall has the status 4 Closed and is not displayed in future service orders.
Result
You can display recalls (recall number, status, and corresponding DBM order number) and gain an overview of all related recalls, old recalls, and new recalls in
the recall view of the vehicle master.
1.8 Standard Text
Definition
A reusable text that can be assigned to and printed out with documents.
Use
In order processing, you use this object to link a text to documents. Standard texts serve as advertising texts or order texts for customer-specific notes and
information on documents. You can access the standard text directly from the area menu or from within a DBM order.
Structure
You can create, change and delete standard (long) texts centrally. In an order, you can use standard (long) texts at header, job, item and split level, or save a
standard (long) text so that you can print it as a document attachment.
You can assign standard (long) texts to text catalogs. The standard system finds the valid text catalogs for the order by using the plant and the order type. You can
change this assignment in Customizing for Logistics Execution ® Dealer Business Management (DBM ® Text Control .
1.8.1 Text Control
Use
You can use this function to handle texts.
In order processing, for example, you use a standard text to link a long text to documents. Long texts serve as advertising texts or order texts for customer-specific
notes and information on documents.
Integration
You can use standard text functions in order processing, the model master, vehicle master, labor value master, package master, Storage Goods Manager and in
the memo pad.
You can access the long text directly from the area menu or from within a DBM order.
Prerequisites
You have made the appropriate settings in Customizing for Dealer Business Management (DBM) under T ext Control .
Features
● You can define how you wish to control the DBM order texts (on header, split header, job, task and item level).
● In Customizing for Dealer Business Management (DBM) under Text Control, you can create different text determination procedures, define how they are
determined and define text access sequences to copy texts to the several levels of the DBM order. You can copy long texts from the vehicle master/options,
vehicle model/options, package master (main or variant package), labor value master, material master (central texts, sales-dependent texts), material
customer info., and customer master to the DBM order. You can also copy texts from the text pool to the DBM order.
● The long text of DBM order items of category P002 (Part) and P010 (External Service with Purchase Order) is copied to the purchase requisition item long
text.
● For the model master, you can define how you wish to control model texts and model option texts. You can create different text determination procedures and
maintain how they are determined.
● For the vehicle master, you can define how you wish to control vehicle texts and vehicle option texts.
You can create different text determination procedures, define how they are determined and define text access sequences to copy texts to the vehicle master.
You can maintain long texts on vehicle level in a separate text view. You can maintain long texts referring to features by using a separate function in the
features view.
You can copy vehicle and option long texts (with reference or without) from the model master when you are creating the model or an option.
● For the labor value master, you can define how you wish to control labor value texts. You can create different text determination procedures and maintain how
they are determined.
● For the package master, you can define how you wish to control main package and variant package texts. You can create different text determination
procedures and define how they are determined. You can maintain long texts on main package level or on variant package level on a separate tab page.
● For the memo pad, you can define how you wish to control customer information and vehicle information texts. You can create different text determination
procedures and define how they are determined. You can define text access sequences for transferring texts to the memo pad. Long texts can be found in the
vehicle master, model master and in the customer master. The texts that are found are displayed in the memo pad. The found/displayed customer and
vehicle information texts should be controlled logically by the constellation determined in Customizing for Text Control and the maintained texts in the vehicle,
model and customer master data.
● For the Storage Goods Manager, you can define how you wish to control storage goods texts. You can create different text determination procedures and define
how they are determined.
Example
Using long texts in DBM Order

You customize using long texts in DBM Order with Customizing for DBM ( Logistics Execution ® Dealer Business Management (DBM) ® Text Control ®
Control DBM Order . Here you choose the text object (this can be the order header, item, job, splitheader and task), and set the text types for these objects. The
text types can be assigned at the detailed text determination procedures.
For text objects, you must set text determination procedures, an ID and a description.
For text determination procedures, you must assign text types on the detail of Text Determination Procedure screen. Here you can choose from the text types
(which you have set for the text object), set the sequence number (this determines the sequence that is applied when displaying the text types in user
transactions), the reference flag and the text access sequence.
Access sequences can be created after choosing Access Sequence , then specifying an ID and a description. On the detail screen of the access sequences
you can set the partner function, the text object, the text type, text name, access sequence rule key, text determination rule key and the append flag. Then you
append the text determination procedures to the order types for all order objects (header, split, job, task and item).
You can check confirm the results using the Create DBM Order or Open DBM Order (via transaction /DBM/ORDER). On the header tab, click Header Text
where the appropiate text elements for the text determination procedure and the order type appear. You can edit, format and delete them.
The same method can be used for the model master, vehicle master, labor value master, package master, memo pad and the storage goods using different text
elements
DBM Order
Definition
A generic term for orders of all order types in Dealer Business Management (DBM), such as:
● Vehicle order
● Service Order
● Parts order
Use
You use this business object in order processing to document services and activities.
When creating a DBM order, you specify the order type and the organizational unit, and thereby control how the system processes the data.
Using the following function modules, you can adapt the DBM order and use functions for the DBM order.
/DBM/ORD_RFC_ADDITEM - creates item for DBM order
/DBM/ORD_RFC_ADDJOB - creates job for DBM order
/DBM/ORD_RFC_CREATE - creates DBM order
/DBM/ORD_RFC_EXISTS - checks existence of an DBM order
/DBM/ORD_RFC_GETDETAIL - gets all DBM order data
/DBM/ORD_RFC_GETLIST - selects lists of DBM orders
For further information, see the Customizing for Dealer Business Management (DBM) under Interface Framework ® Function Modules ® RFC 1.9 DBM
Order .
Structure
The DBM order consists of tab pages on which you can display or hide subscreens. In the following documentation, the data on the tab pages and subscreens is
described as it appears in the standard system. You can adjust the display of tabs and subscreens in Customizing, and show or hide the relevant tabs according
to the order type.
You can use the Customizing for Dealer Business Management (DBM) under Order ® Business Add-Ins ® BAdI: Enhancement for Order
Transaction to control the processing logic of the order transaction screens and include your own subscreens by using BAdI: Order Transaction
Enhancement: Customer Subscreens.
Header Tab
In the order header, the system displays the following subscreens in accordance with the order type:
● The Order Data subscreen includes the following information:
○ Order Type
○ Organizational Data
○ Customer data
○ Pricing conditions on header level
○ Information on vehicle, such as mileage and number plate (for service and vehicle order)
From this subscreen, you can call and edit the header and footer texts and also the pricing conditions overview for the order header. You can also enter the
external purchase order (PO) number.
● You can create and display partner roles in the Partner subscreen. You can find further information in the component Partner Determination in Sales and
Distribution (SD-BF-PD).
● Important vehicle data is displayed in the vehicle subscreen of the DBM order, for example, the vehicle identification number (VIN), registration data, and
maintenance and service intervals. From here, you can branch directly into the Vehicle Master display via the Display Vehicle pushbutton.
● In orders for the vehicle, the warranty master data subscreen displays all the vehicle warranties that are stored in the vehicle master record. Furthermore, the
warranty category for the order is displayed in the warranty order.
● The recall subscreen displays all the warranty claims, with reference to a recall, that belong to the vehicle from the order.
● The Storage Goods subscreen displays all the storage goods that belong to the vehicle from the order. If there are no storage goods, the list is empty. With
forward navigation, it is possible to branch to the Storage Goods Manager by clicking on the Storage Goods Detail button.
Job Tab
On the Job tab, the system lists all the jobs with the assigned order items and all the open (not assigned) order items. You can assign fixed prices for jobs and
record print settings on the jobs level. You can also assign and sort order items via drag and drop.
You can set the following indicators for the job:
● Print Job
● Print Job: 0 %
● Job Update
● Synchr. Job/Task
The system only displays this indicator when the Task Manager is active. When this indicator is set, the system automatically generates a task for each
new job and changes in the job description are copied to the task. You can only set this indicator if there is only one single task for the job. Otherwise, more
than one task would have to be changed when the job description is updated.
For more information, see Job Management.
Position Tab
Select one of the item types stored in Customizing, for example Labor Value or Part . You can use the Key field to choose the order item and copy it to the
item list.
In accordance with the authorization object and authorization check, you can create, change, display, and delete a purchase requisition for one of the following
items:
● A parts item (item category P002) from the DBM parts or service order
● An external service item with procurement/purchase order (item category P010) from the DBM service order.
To create a purchase requisition, choose Procurement from the order. The system executes the event PROCUREMENT.
Use BAdI /DBM/BADI_PREQ (BAdI for Enhancements for Purchase Requisition) if you wish to add additional data and adapt the purchase requisition data to
suit your requirements.
To create a purchase requisition, you have to change the settings in Customizing for Dealer Business Management (DBM) at the following IMG activities:
● Order ® Interface Control ® Subscreen ® Define Subscreen
● Order ® Item Category ® Define Item Category for Order
● Order ® Order Control ® Enhancements ® Define Action
● Order ® Order Control ® Define Events
● Order ® Order Control ® Define Action Control
Parts Tab
This tab contains an Item Details subscreen and a Procurement subscreen with an Item List - Quick Entry . For more information, see Procurement.
You can call stock information for the parts items, such as warehouse stock and availability. You can display stock information in the following:
● Current plant
● Local plant
● All plants
● External system
There is an authorization check for the cross-plant stock inquiry. To enable the display of stock in other plants, you should make the appropriate settings in
Customizing for Dealer Business Management (DBM) under Part ® Stock Information ® Define Search Key for Stock Inquiry and Assign Search Key and
Nearby Plants.
Once you have implemented the BAdI Stock Information from External System in Customizing for Dealer Business Management (DBM) under Part ® Stock
Information ® Business Add-Ins (BAdIs) , you can display availability of stock across systems.
Split Tab
You can display details and an overview for the order split and execute further splits.
You can move an item from a job that has been split to another job if the job is split over a percentage. If the job is split over a fixed amount, you cannot assign
the item to another job before you have deleted the splits.
Warranty Tab
This tab shows the details of the warranty claim and of the associated order items. You can generate warranty claims form the DBM order and monitor the status of
the warranty claim processing (LO-WTY).
Date Planning Tab
You can display the following details:
● Appointment header
● Appointment job/Task/Task schedule line
● Workshop
● Replacement vehicles
● Consultants
Item Quick Entry Tab
For service and parts orders, you can use this tab to add multiple items to the order at once.
Target/Actual Comparison Tab
You can check whether the actual times recorded deviate from the target working times for the order. For further information, see: Target/Actual Comparison in
DBM Order.
Task Tab
You can display an overview and details for the task. Otherwise known as the Task Manager, this view exists in parallel to the job view of the order. Whilst jobs
display and external customer view of the order, tasks show an internal view of the order.
Service advisors usually enter the jobs to be completed, to which items can be assigned, when the customer telephones or brings in a vehicle for servicing or
repair. Customers often wish to see these jobs listed on the bill so they can check whether the jobs have been performed as agreed.
Internally, you may find it more helpful to use the Task Manager, as different workshop departments and resources may be involved by performing different tasks
within the same job. The example scenario below describes a situation in which we would advise you to assign work to be performed in the Task Manager view.
Repair of accident damage:

A customer brings a damaged vehicle to the workshop and requests that the damage be repaired. Since an inspection is also due, this should be
performed at the same time.
The service advisor enters two jobs: “repair accident damage” and “inspection”.
The customer wishes to see these two jobs in the form of items on the bill.
The workshop dealing with this request is very large and has several departments: there is a department for bodywork repair, one for electrical
maintenance, and one for paintwork. The department for bodywork repair also deals with general servicing and repair work.
In this case, entries on job level would not be helpful, since the work to be performed could not be assigned correctly; you would therefore use the
Task Manager.
The Task Manager allows you to assign an order internally as required. This means that tasks such as beating out dents or replacing damaged body parts can be
assigned to the department for bodywork repair, whilst electrical damage can be dealt with by the electrical maintenance department, and scratches removed by
the paintwork department.
Since the department for bodywork repair also deals with general issues, such as the inspection requested by the customer, you can assign the items from this
job to the task that the bodywork repair department is dealing with.
When the task does not fit into the actual date capacity, you can use task schedule lines to divide one large task into several smaller tasks/task schedule
lines with different start dates and times, but for the same department.
For more information, see Task Management.
Integration
● The DBM order contains a tool called the Order Engine Simulator that allows you to simulate events. This tool provides details as to why an Event may occur
or not, by providing information on the status checks that pass or fail for the current status of the order.
To access the Order Engine Simulator, open a DBM order and select Order ® Order Analyzer (Expert).
● In the DBM order, you can branch to the following functions via Goto :
○ Change document : Enabled you to display changes to the DBM order. The system displays a list of change documents.
○ Action log : This takes you to the list of messages and their details from the DBM application log, that were generated for this order (for example error
messages for action execution).
○ Status Overview : An overview of the status of the individual process steps. You can scroll through these with the action-controlled order engine for the
order. This enables you to see, whether certain events were completed or still remain open (for example, confirmation from workshop).
○ Document Flow : Displays the document flow for the DBM order. The system lists all documents for the order and enables you to branch directly to the
relevant document.
○ Cost Analysis : Displays the report for the cost types of the DBM order.
● In the standard system, you can create a pro forma invoice from the DBM order for sales orders, customer orders or parts orders, before the actual invoice.
Document flow is updated. Possible reasons for such pro forma invoices may include the following:
○ Prior to creation of the real invoice, you wish to provide the customer with a preliminary invoice listing the amount that will most likely have to be paid.
○ In some cases, no actual billing document is created in DBM, for example if the vehicle sale is conducted from the vehicle owner or importer directly to
the customer, with the dealer acting as a sales agent.
To enable the creation of pro forma invoices, you defined the billing type you want to use for pro forma invoices in Customizing for Dealer Business
Management (DBM) under Order ® Order Type ® Define Order Type in the Pro Forma Billing field.
Order Item
Definition
An item in a DBM order that is classified according to item categories.
Use
You can use this object to store materials and services, such as, parts, labor values, and packages, that are required for a DBM order. Order control defines
which item categories are available for which order type in the input help. When you create an order item, you use the item category to define how the system
processes the data.
Structure
In Dealer Business Management (DBM), an item category is assigned to a technical item category that controls the program logic.
There are the following item categories in the standard system:
Text
Labor value
Part
Vehicle
· Vehicle features
· Vehicle extras/accessories
· Manual labor value
· Manual part
· External service with purchase order
· External service without purchase order
Package
1.11 Order Processing
Use
This function enables you to create and process DBM orders.
In the central transaction Order Processing (transaction code /DBM/ORDER ) you can identify existing orders according to customer, vehicle, and order
data using the order search function, and then call up and change the order. You can also create and call up all vehicle orders from the vehicle master record.
You can also create print messages in the order.
Features
When you create an order, you control the order process based on order type. By choosing an order type, you determine the type of settlement and thereby cover
the following business processes:
Vehicle quotations
Vehicle sales
Vehicle service
Cash sales of parts
Returns and credit memos
Warranty cases for vehicles and parts
Once you have saved the order, you can no longer change the order type. You can delete a created order only before you carry out goods movements or send
confirmation.
If you want to bill individual jobs rather than the entire order, perform an order split.
You can use the Copy function to select data of an existing source order and copy it to a new target order.
From both the Order Processing transaction and the order itself, you can branch to the following order-related displays:
· Vehicle master record
· Customer master record (DBM-specific transaction)
· Cost analysis
· Document flow
· Status overview
· Action log
· Printing
Choose Goto ® Print Preview to view print messages for the order or billing document.
If you want to create print messages for the order or billing document, you have two options:
¡ From the order, choose Goto ® Messages (Print Expert Screen)
¡ In the order, choose Print (Print Easy Screen)
The abbreviations RD and V3 originate from message control; RD stands for DBM Automotive and V3 for Billing.
To change settings for output determination in Customizing for Dealer Business Management (DBM) , choose Order ® Output Determination.
On the SAP Easy Access screen, you can maintain output determination in the application by choosing Logistics ® Logistics Execution ® Dealer
Business Management ® Master Data ® Output Condition.
You can maintain output determination for billing in the SAP standard transaction code NACE.
For more information on message determination in general, see the standard documentation on the SAP Help Portal ( help.sap.com ) under
Documentation ® mySAP ERP ® SAP ERP Central Component ® SAP ERP Central Component ® Logistics ® Sales and Distribution
(SD) ® Output Determination (SD-BF-OC).
· Order blocking
You can block the creation of sales documents for a customer and order type. To block the creation of sales documents, choose in Customizing Sales and
Distribution ® Sales ® Sales Documents ® Define and Assign Reason for Blocking ® Define Blocking Reasons . You then define which
order types you wish to do this for under …Allocate Blocking Reasons to Sales Document Types. To be able to use the order block in DBM, you must
assign the standard SD order type (assigned to the DBM order type in Customizing for DBM) to every order block reason that you wish to use.
1.11.1 Order search
Use
You can use this function to create and search for orders. There are two search options for orders – basic search and enhanced search:
● Basic search
In Order Processing , you can execute a basic search in a single screen by using standard search criteria based on customer, vehicle, and order in the
Find/Create Orders group box.
You can also create new orders with this search option. This search option does not make use of TREX.
● Enhanced search (TREX search)
You can execute an enhanced search in two ways:
○ Create a customer-specific variant and set as the default
○ Create multiple variants and, in a two-step procedure, execute a search by first selecting a variant and then clicking Find in the Find/Create Orders
group box. The enhanced search is a TREX-based search that supports attribute and a free text searches.
You cannot use this search option to create new orders.
Integration
From the order search, you can branch to the customer master, vehicle master, notification and fact sheet.
Prerequisites
You have made the appropriate Customizing settings for the order search in Dealer Business Management (DBM) under Order ® Order Search .
Features
The order search function allows you to do the following:
● Create a new order by entering customer data, vehicle data and order type (basic search)
● Search for an existing order (basic and enhanced search)
● Start the enhanced search with an initial search (enhanced search)
● Load a default selection variant (enhanced search)
● Select a view with additional search criteria (enhanced search)
● Load and modify a selection variant (enhanced search)
● Create, save, and delete a personal, that is, user-specific selection variant (enhanced search)
● Add new attributes to the search (enhanced search)
● Set the Error-Tolerant Search indicator.
By doing this, you can execute a fuzzy search. Note, however, that this indicator refers to text only, and not to attributes.
The descriptive texts for the selection variants are language-dependent. For example, variants that you create in German are available to you in
another user logon language, but they do not then have a text.
Activities
To search for an order, select Logistics Execution ® Dealer Business Management (DBM) ® Order Processing ® Order Processing (/DBM/ORDER) on
the SAP Easy Access screen, and enter the appropriate organizational data.
● Basic search
By selecting the Order Acceptance tab, you can access the basic search and create new orders or search for existing orders by entering the appropriate
customer, vehicle or order data.
● Advanced Search
By choosing the Order Search tab page, you can access the enhanced search.
The enhanced search is displayed on a separate tab page in the same transaction. It is separated into two areas: the search criteria area and the result list.
By default, there is a standard search screen with some of the most useful criteria for an order search, but you can also implement your own views/customer
screens. On these customer screens, you can implement new attributes, provided that they are part of one of the following five basic DBM tables:
○ Header (VBAK_DB)
○ Item (VBAP)
○ Job (JOB)
○ Split (SPLHDR_DB)
○ Partners (VBPA).
Every field that is part of one of these tables can be defined as an attribute field. Furthermore, you can append further fields to these tables.
Generally speaking, you can declare all fields of these five main order tables as attributes, also customer fields that have been appended to the
tables. You cannot include other tables in the search. If a new field is included in the search, TREX has to be indexed again manually; only after
you have done this are the fields available as attributes in the search.
For further information, see Customizing for Dealer Business Management (DBM) .
You can use selection variants in the enhanced search, not in the basic search. Selection variants are user-specific and can only be used by the user who
created them. They contain all the criteria on all the screens of the enhanced search; in other words, also when you create your own views. All the criteria are
used for the search, not just the criteria for the screen that is currently active.
1.11.2 Creation of a Vehicle Quotation
Purpose
With this process, you can create a quotation for the sale of a new or used vehicle for a potential customer in the system.
By entering a validity period, you can define time interval (from to) for determining how long the quotation is valid.
A VMS status change ensures the reservation of the sale of the vehicle to the potential customer named in the quotation, thus preventing the sale to a third party.
When you create a quotation for a vehicle, the vehicle status is changed so that no-one else can purchase this vehicle.
Prerequisites
● You have created the necessary master data.
You can choose to use a one-time customer and then have to enter the required data manually.
● You have assigned the vehicle a customer.
● In Customizing, you have checked the action control settings for the vehicle as well as the order control settings and tailored these to your business
processes.
Process Flow
Depending on the settings you make in Customizing, the process flow may be as follows:
1. After you have selected and assigned the vehicle to the customer using the transactions Vehicle Search (/DBM/VSEARCH) and Vehicle Master
(/DBM/VM), click Order to create a quotation with the Vehicle Quotation order type from order processing for the vehicle master. The system performs the
following:
○ It transfers the customer data from the customer master record (provided that you do not use a one-time customer) and the vehicle data from the vehicle
master record to the order header.
○ It checks the customer’s credit limit.
2. Enter the valid-to date of the vehicle quotation, and additional order data. In addition, you can enter header and footer texts, and edit partner data.
The system enters the current date as the validity start date automatically.
3. The system transfers the vehicle and the vehicle features and accessories that are stored in the vehicle master record to the vehicle quotation as order items.
4. You can add vehicle accessories and text as additional order items, and group the items into jobs.
For each vehicle quotation, you can include only one vehicle with vehicle features, since the quotation is linked with the associated vehicle
master record.
5. You can define prices, discounts, and surcharges and perform pricing.
6. If you want to split the quotation among several potential bill-to parties, perform an order split for the job in question.
7. You print the vehicle quotation.
Result
Once you have created the vehicle quotation, you have the following options:
● If the potential customer accepts the quotation, you can convert it to a vehicle order. To do so, use the Copy function to copy the vehicle quotation data with a
new order type to a vehicle order.
The system transfers the information from the vehicle quotation, and not from the vehicle master record, since vehicle accessories, for example,
have been added to the vehicle in the quotation.
● If the potential customer rejects the quotation, you can cancel it by specifying a reason.
The system flags the quotation items for deletion and cancels the vehicle registration for this customer by triggering a vehicle action that sets the defined target
status. This is the same status as before the reservation.
1.11.3 Order Processing in Vehicle Sales
Purpose
With this process, you can create, post, and bill a DBM order for the sale of new and used cars. The system updates the order-dependent data in the vehicle
master record, such as the vehicle history and the primary and secondary status of the vehicle, automatically.
Prerequisites
● You have created the required master data, such as vehicle master and vendor master.
● In the vehicle master, you have assigned a customer to the vehicle via action QACU.
processes.
For vehicle sales, we recommend the use of the following material categories:
■ Vehicle VEHI
■ Option NLAG (not relevant for goods movements)
■ Accessories HAWA
Process Flow
Create a Vehicle Order
1. You use the vehicle search function to find the customer’s vehicle and open the vehicle master record.
If you have created a quotation for the vehicle, you can use the Copy function to copy the vehicle quotation data directly to a vehicle order.
2. You create a vehicle order.
The system performs the following:
○ It transfers the customer data from the customer master record and the vehicle data from the vehicle master record to the order header.
It checks the customer’s credit limit.
○ It creates an internal order with the vehicle order.
3. You enter additional order data, can add a header text and footer and edit partner data.
4. The system transfers the vehicle and the vehicle features and accessories that are stored in the vehicle master record to the vehicle order as order items.
Note the following:
○ The system only copies those vehicle master options into the sales order item, for which you did NOT set the Not Relevant for Sales Orders indicator in
the vehicle master.
○ New vehicle price: The system gets the sales price for the vehicle model from the Model Data view in the vehicle master. New vehicle price: The
system gets the sales price for the vehicle model from the Model Data view in the vehicle master.
○ The system gets the price for a used vehicle from the Vehicle Prices view.
○ You can copy accessories and additional features in items with prices and standard features in items without prices.
○ When you store the sales order, the system updates the vehicle master (action QCUO is executed).
5. You can add vehicle accessories and text as additional order items and group the items into jobs.
For each vehicle order, you can include only one vehicle with vehicle features, since the order is linked with the associated vehicle master
record.
Post and Bill the Vehicle Order
Preconditions:
● To issue the vehicle, you have to execute vehicle purchase actions, for example creating a purchase order in the vehicle master (standard action QORD)
and creating a goods receipt (action in standard QGRE).
● The settings in Customizing for the action grid of the vehicle determine when goods issue or billing are possible.
1. As soon as you post the goods movement for the vehicle and parts, the system carries out an availability check.
2. If you want to split the order among several bill-to parties, perform an Order Split for the job in question.
3. You bill the order.
If the sales order has multiple splits, the system updates the vehicle (action QOIV) for each created billing document. As soon as you have created the last
billing document, the corresponding vehicle action sets the sales order status to "Complete".
4. You print one or more invoices for the bill-to party or parties.
Order Processing for the Service Order
Purpose
With this process, you can create, post, and bill a DBM order for vehicle services. The system updates the order-dependent data in the vehicle master record,
such as the vehicle history and the primary and secondary status of the vehicle, automatically.
Prerequisites
You can choose to use a one-time customer and one-time vehicle, and then to enter the required data manually.
● You have assigned the vehicle a customer.
processes.
Process Flow
Create a Service Order
1. You create a service order.
○ It copies the header data from the customer master record and the vehicle data from the vehicle master record to the order header (provided that you do
not use a one-time customer and a one-time vehicle).
○ It creates an internal order with the service order.
3. You enter the order items.
For this purpose, you can use the following item categories:
○ Labor value
○ Part
○ Package
○ Manual part and manual labor value
○ External service with and without purchase order
○ Text
As soon as you include a part in the order as an item, the system checks the part replacement for this part.
4. You can group order items into jobs.
6. You can trigger a procurement process (purchase requisition/stock transport order) for a parts item or for an external service with purchase order (see
Procurement).
Release, Post, and the Bill Service Order
1. You release individual jobs or the entire order.
On release of the jobs or order, the system automatically prints the work instructions for the mechanic.
2. As soon as you post the goods movement for the parts, the system carries out an availability check.
3. You post the costs for the labor values by means of a confirmation.
The confirmation is required before the order can be billed.
4. Once individual jobs or the entire order has been executed, you confirm the jobs or order as technically complete.
5. If you want to split the order among several bill-to parties, perform an Order Split for the job in question.
7. You print one or more invoices for the bill-to party or parties.
Creation of Internal Service Orders with Revaluation
Use
This function enables you to upgrade vehicles, thus making them more attractive to potential customers. Dealers can therefore then potentially sell more vehicles
more quickly.
Prerequisites
You made the appropriate settings for order type 4100 and 4101 in Customizing for Dealer Business Management (DBM) under Order ® Account
Assignment :
● Internal Order for Bill-To Party ® Define Internal Order Type for Bill-to Party
● Internal Order Accounting Assignment ® Define Account Assignment Categories for Internal Order
● Internal Order Accounting Assignment ® Assign Account Assignment Object for Internal Order
● Internal Order Revaluation ® Define Order Type for Revaluation
For further information, see Customizing for Dealer Business Management (DBM) .
Features
You can use the following order types to revaluate the vehicle on stock:
● Order type 4100 (internal service order with increase in value)
You use this order type when value-increasing measure are performed on a vehicle that is in the workshop stock.
● Order type 4101 (internal service order with increase in value – return)
You use this order type if you have to cancel the revaluation steps you have made with order type 4100.
Activities
When you bill an internal service order with revaluation, the following VMS actions are triggered in the background and revaluate the vehicle stock automatically:
1. Creation of the CO production order (VMS action QCPO/QCPH)
2. For the internal service performed, primary costs transfer posting from the vehicle internal order to the CO production order; posting of material consumption
from the batch to the CO production order (VMS action QCCP/QCCH)
3. Posting of the goods receipt from the CO production order to the batch (VMS action QGRP/QGRH)
4. Settling of the CO production order against the batch (VMS action QSEP/QSEH)
5. Closing of the CO production order and setting of the deletion flag (VMS action QCLP/QCLH).
The letter H in the name of the action indicates a value increase with return, the absence of the letter H indicates a value-increasing measure.
The following figure illustrates the steps involved in the creation of an internal service order with revaluation:
Creation of an Internal Service Order with Revaluation
1.11.5 Order Processing in Parts Sales
Purpose
With this process, you create a DBM order in order to sell vehicle parts. You can proceed as follows, for example:
● You can create a parts order in the order processing and process the cash sales using the cash desk.
● You can create a parts order from the cash desk and branch back to the cash desk to process the cash sales.
Prerequisites
You can choose to use a one-time customer and then have to enter the required data manually.
● In Customizing, you have checked the order control and tailored it to your business processes.
● You have made the required settings for the cash desk.
Process Flow
1. You create a parts order.
○ It transfers the customer data from the customer master record (provided that you do not use a one-time customer).
3. You enter the order items.
For this purpose, you can use the following item categories:
○ Part
○ Manual part
○ Text
As soon as you include a part in the order as an item, the system checks the part replacement for this part.
5. You can trigger a procurement process (purchase requisition/stock transport order) for a parts item. For more information, see Procurement.
6. As soon as you post the goods movement for the parts, the system carries out an availability check.
8. You print the invoice for the bill-to party.
Result
In the Cash Desk transaction (/DBM/CASHDESK), you process the cash sales for the invoice generated.
Order Processing for a Warranty Case
Purpose
With this process, you can process warranty cases in the service order from order processing for Dealer Business Management (DBM) and generate warranty
claims. You can monitor the status of warranty claim processing using the relevant DBM order.
The warranty claims are further processed in Warranty Claim Processing (LO-WTY).
Prerequisites
● For the vehicle and the part, you have defined possible warranties in Customizing for DBM under Service ® Warranty , as well as in the Processing of
Warranty Master Data transaction, using the Criteria Technique.
● For the vehicle, you have assigned the vehicle warranties in the vehicle master record and defined a start date.
● To copy DBM-specific data to warranty claims, you have made the changes described in Customizing for DBM under Service ® Warranty ® Business
Add-Ins (BAdIs) ® Warranty Documentation.
Process Flow
1. You create a DBM order with one of the following order types:
○ Service Workshop (workshop order)
○ Service Workshop (Warranty) (warranty order)
Note (Standard Icon):

To execute warranties for parts orders, use the order type Service Workshop 2000 without vehicle and split, or the order type Service Workshop
(Warranty) 2001 without vehicle.
The system finds the possible warranties that have been defined in the system.
2. Depending on the order type, proceed as follows:
○ Workshop order
In a dialog box, you select the warranty that is to be used for this order, or do not transfer any warranties.
○ Warranty order
In a dialog box, you select the warranty that is to be used for this order.
The warranty is thereby defined at header level on the basis of the warranty category. On the tab page for the split, you can change the warranty
category for each split order.
3. At header, job, and item level, enter the required data.
4. If you have created a workshop or parts order, split the total amount or a partial amount between one or more guarantors as the bill-to parties by means of an
Order Split. For this purpose, choose the order type Service Workshop (Warranty) .
On the basis of the warranty category, the system automatically finds the relevant car manufacturer as the bill-to party of the split order.
5. On the tab page for the warranty, enter the data relevant for the warranty. In the subscreen for the warranty item data, you can define items as damage-
causing, as secondary defective parts, or as parts to be returned to the reimburser. These settings are copied to the warranty claim. In accordance with the
Customizing settings, the action Change Item (Warranty) (ITEM_WTY_CHANGE) checks that not too many items are selected as causing damage.
6. Once you have released the order, you can generate a warranty claim.
The system transfers the warranty claim to Warranty Claim Processing (LO-WTY) .
Before you release the order, you can simulate a warranty claim to check whether all data that is relevant for the warranty is available in the
system. You can find the result of the simulation in the action log.
Result
In Warranty Claim Processing (LO-WTY) , continue to process the warranty claim until it is complete. In the associated DBM order, you can monitor the status of
warranty claim processing.
1.11.6.1 Processing of Warranty Master Data
Use
This function enables you to store default values for the vehicle and parts warranty, such as warranty conditions, in the system. You can also define warranty
categories, which you can use to control Warranty Claim Processing (LO-WTY) .
In the case of parts, the system finds the data required for a warranty claim, such as the bill-to party (car manufacturer) and warranty claim type, using the criteria
technique in the service order.
In the vehicle master record, you can assign the vehicle warranty categories, which are proposed on the basis of the criteria technique, and define warranty
conditions. If you create a service order for the vehicle, the system displays the possible warranties for the vehicle in a dialog box.
Prerequisites
In Customizing for Dealer Business Management (DBM), you have made the following settings under Service ® Warranty :
● Definition of one or more criteria tables and access sequences for warranty determination
● Assignment of item categories in the DBM order for item types in the warranty claim
Features
In variable key fields (criteria), the system finds one or more warranty profiles. The warranty profile specifies which warranty conditions (such as validity in
kilometers and warranty period) apply for the vehicle or part, and at which manufacturer the warranty is validated. On the basis of the warranty categories, which
are also assigned to the warranty profile, the system finds the type of warranty (for example, manufacturer warranty or implied warranty) as well as the relevant
warranty claim type.
The following applies for the vehicle warranty: The system transfers all warranty categories of the warranty profile found as a default setting to the vehicle
master record. The warranty is active as soon as you enter the warranty start in the vehicle master record or DBM order.
In accordance with the default implementation of the Business Add-In BAdI: Warranty Check in Order, the validity of the vehicle warranty
depends on the following entries:
■ Warranty period, that is, the warranty start and duration
■ Mileage/kms interval
■ Sales date of the vehicle
■ Mileage/kms on the vehicle
You can use a separate implementation to influence which warranties the system displays as valid when a DBM order is created.
You can use BAdI /DBM/VEHICLE_IWTY BAdI Control Vehicle Warranties to influence, for example, the validity periods of warranties; color
coding in the warranty indicates which warranties are valid and which not.
The following applies for the parts warranty: By entering the invoice date of the DBM order relevant for the parts warranty in the parts order, you can define
the start date of the parts warranty. The warranty check then checks the validity of the parts warranty.
Example
Vehicle Warranty
Parts Warranty
1.11.7 Order Control
Use
In DBM orders, this function enables you to control the execution of events and order actions using the criteria technique. The control can be executed at the
following levels:
● Header
● Job
● Split
● Item
Integration
The action control settings for the V ehicle Management System (VMS) and the order control settings for Dealer Business Management (DBM) must be
coordinated. For more information, see the “Integration” section in Performance of Vehicle Actions.
By making settings in Customizing for Dealer Business Management (DBM) under Order ® Order Control ® Order Control VMS Extensions, you can define
tables of criteria and access sequences for the execution of VMS actions and order control actions.
Prerequisites
You do not have to make any settings in order to use the processes shipped by SAP. If you want to implement additional processes or adapt predefined
processes, define your own events and order actions. For more information, see SAP Note 889566.
Features
If you trigger an event, the system performs the assigned order actions in the sequence defined in Customizing for DBM. An order action describes a self-
contained business transaction. At the end of an order action, the system can perform the following actions:
● Trigger an update
● Set the status
● Include the new document in the document flow
System actions play a particularly important role. They are required in order to create, change, or save an order, and must not be deleted or changed. However,
they can be enhanced.
Do not make any changes to system actions and events, since this can have unforeseen effects. Instead, define your own actions and events.
In Customizing for DBM, you can define whether a particular event is linked with a dependent subsequent event. On the basis of this link, data is created by
event actions. The system requires this data for the actions of the subsequent event.
In the order, you can call up the following information via Goto :
● The action log displays the order actions that have already been performed, together with an appropriate message.
● The status overview displays the status of the order actions that have been performed.
The system sets the relevant indicator.
In Customizing for DBM, you can define the statuses that the system should display in the status overview for the relevant order action, and for additional
actions whose status is influenced by this action.
To define the statuses, select Order ® Order Control ® Define Actions . The following statuses are possible:
○ Not Relevant
○ Not Edited
○ Partially Processed
○ Completely Processed
If you want to create your own order actions, create separate action modules. You can customize events and assign them to a separate pushbutton or the Events
pushbutton.
Order Control Versions:
You can check your Customizing settings and manage different versions of Customizing settings for order control. You may wish to do this to help you keep track of
changes made to Customizing settings during an implementation or test phase.
You can also compare Customizing settings for order control between different clients or you can compare the customer’s current Customizing settings with the
standard Customizing settings.
You can generate different versions of the Customizing settings. You may wish to do this for future reference; for example, you could generate a version at the
beginning and at the end of certain phases of a project.
You can also, for the purpose of working in the DBM order, activate a previous Customizing version without having to make any changes to the current
Customizing settings.
To generate different customizing versions, and to compare and check customizing settings for the order control, use the following functions provided in
Customizing for Dealer Business Management (DBM) under Order ® Order Control ® Order Control Tools :
● Order Engine Version Generator
● Order Engine Version Analysis
● Order Control Customizing Checks
Example
You have created a vehicle order in which a vehicle with features and vehicle accessories were transferred as order items. As soon as you trigger the Execute
Goods Movement event, the system performs the following order actions consecutively, in accordance with settings in Customizing:
1. Depending on the control code ( vehicle order ):
a. Vehicle action: Check goods issue
b. Change Item (if order item data has been changed)
c. Select All Items
2. Depending on the sales document category ( order ):
a. For technical item category Vehicle :
i. Availability check before goods issue
ii. Execute goods movement
b. For technical item category Vehicle Features :
Post LV/External Service Costs (for cost transfer posting for vehicle features)
c. For technical item category Vehicle Features :
i. Availability check before goods issue
ii. Execute goods movement
3. Vehicle action: Report goods issue
When the vehicle action is performed, VMS action control updates the vehicle history and status in the associated vehicle master record.
1.11.8 Procurement
Use
You can use this function to trigger a procurement process from a DBM order.
The system generates a standard purchase requisition in the background.
Integration
You can access this function from the DBM order by choosing the Parts tab page and then expanding the subscreen Procurement.
Prerequisites
The event Procurement has triggered the procurement process.
Features
This function allows you to do the following:
● Change data, such as quantity, supplying (issuing) plant, or purchase price.
● Trigger the procurement process by using the event Procurement.
● Create, change and delete a purchase requisition for parts
● Create, change and delete a purchase requisition for external service with purchase order
● Create and change a standard stock transfer order and trigger a standard stock transfer by entering the supplying (issuing) plant
● Use a Business Add-In (BAdI), enhancement spot /DBM/ORDER with BAdI definition /DBM/BADI_PREQ ( BAdI: Enhancement for Purchase
Requisition) to adapt this function to your own requirements.
You can find this BAdI in Customizing for Dealer Business Management (DBM) under Order ® Business Add-Ins (BAdIs).
Activities
You can create a purchase requisition for a wholly or partially unavailable parts item from a DBM service order or DBM parts order, or for an external service item
from a DBM service order. You can select the item, enter data such as quantity, delivery date, vendor (optional), purchase price (optional), and then select
Procurement .
In the background, the system uses DBM function modules to gather the data and perform all the checks required for creating the purchase requisition.
If data input is incorrect, the system displays an appropriate message and you can change the data accordingly.
Updates you make to the DBM order may have an influence on the related purchase requisition. Provided that the purchase order has not yet been created
and/or the completion flag in the purchase requisition has not yet been set, you can update the purchase requisition. You can trigger the update by choosing
Procurement. If the purchase order has already been created, you cannot update the purchase requisition and the system displays a warning message.
If you wish to increase the order quantity, a new purchase requisition is created with the remaining unconfirmed quantity.
You can display the purchase requisition by using the function for document flow and then double-clicking on the purchase requisition document.
There are two options for deleting the purchase requisition:
● Delete the purchase requisition without deletion of the item
● Delete the purchase requisition whilst also deleting the item/order
When a purchase order and/or goods receipt is created, the system updates the status and document flow of the DBM order item/DBM order when the former
reference to a purchase requisition created from a DBM order.
A purchase order can be created in one of two ways:

- Manually using transaction ME21N
- Automatically in the background
You can create a goods receipt for the purchase order by using transaction MIGO.
You can also create a vendor invoice verification by using transaction MIRO.
1.11.9 Creation of Credit Memos
Use
This function enables you to create a DBM order in order to create a value-based credit memo for parts and labor values. You can create a credit memo in the
following cases, for example:
· You have billed the customer at high prices.
· The part returned by the customer is not accepted.
Activities
1. You copy the source order and create a new order with order type Service Credit Memo with the required order data.
The system continues with the document flow for the source order.
2. The system posts the invoice with negative amounts.
3. You print the credit memo.
Execution of Returns from the Customer
Use
This function enables you to create a DBM order in order to post the goods return for parts and cancel the confirmation for labor values. In the following cases, you
can return items, for example:
· A part has been damaged or is not required
· A labor value has not been provided but has been billed
Activities
1. You copy the source order and create a new order with order type Service Returns or Parts Returns with the original order data.
The system continues with the document flow for the source order.
2. For parts, post the goods return, and for labor values, cancel the confirmation.
3. You create a credit memo for the returns.
1.11.11 Job Management
Use
This function enables you to group order items in the DBM order into jobs. This enables, for example, all order items in a job that are assigned to a particular
vehicle activity to be structured clearly. At job level, you can also define fixed prices.
Integration
If you want to split an order item, you need to have assigned this item to a job. For more information, see Order Split.
Features
You can access the Job Management via the Job tab in the DBM order. For each job, you assign a separate number (external number assignment) or the
system assigns the next available number (internal number assignment). The system automatically calculates the costs for each job as well as the total cost for
all jobs and displays these costs.
Furthermore, job management also provides you with an overview of the status of the individual jobs. Icons display whether the job has been split, whether it has
been confirmed as technically complete and if so, when and by whom.
In Job Management, you can define a fixed price in the following way:
● For each job
● For all labor values of a job
● For all parts of a job
You can specify whether and how the system prints a job. This means that you can, for example, use an indicator in Job Management to control that a job also
appears on the sold-to party's invoice if 100% of the costs are transferred from a different payer.
In the standard system, you can use the following functions for the job, provided that the job has not yet been billed:
● Explode Job
The system deletes only the job and keeps the order items without assignment.
● Delete Job
The system deletes the entire job, including assigned order items.
● Set technical status
You can confirm a job or the entire order as technically complete.
● Reset technical status
Once you have confirmed a job or an entire order, you can reset the status.
● Explode package
Provided the package has been classified as changeable, it can be broken down into its individual items. The price that was calculated for the entire
package expires.
In the Job Management, you can distribute and sort the DBM order items into individual jobs via drag and drop.
Example
A customer comes into the workshop to have the tires changed on his or her vehicle. The vehicle is also losing oil. The workshop employee creates a workshop
order with the following jobs:
● Job 1
The employee assigns all labor values and parts required for the tire change to this job.
● Job 2
The employee enters the customer's statement about the oil loss in Job 2 as a text item, as it is not yet clear, which labor values and parts will be required.
While examining the vehicle, the employee establishes that the oil pan needs replacing. The employee includes the relevant order items for replacing the oil
pan in Job 2.
1.11.12 Task Management
Use
This function enables you to group order items in the DBM order into tasks. This allows you, for example, to clearly structure all order items in a task that are
assigned to a particular vehicle activity. Tasks represent an internal view of the order, and jobs an external one. You can group items in jobs and as well in tasks.
In other words, a task collects all the work that has to be performed by a specific department, for example, by the electrical department or the body work
department. In the task view, you can group all items in the task assigned to a specific department. They are also assigned to a job that can be displayed as the
external view.
Integration
Tasks represent the internal view of the order. They are used to group the items internally in way that varies to the external view (job). Tasks can be related to
jobs, but they need not.
Features
You can access the Task Management via the Task tab in the DBM order. For each task, you assign a separate number (external number assignment) or the
system assigns the next available number (internal number assignment). You can also assign a reference job, but all items of the task have to be assigned to
that job. If there is any item that is assigned to another job, the reference is no longer unique and is deleted.
You can specify whether and how the system prints a task.
In the standard system, you can use the following functions for tasks:
● Delete task
The system deletes the entire task, but the items are still in the order.
● Create new task
Example
Repair of accident damage:
A customer brings a damaged vehicle to the workshop and requests that the damage be repaired. Since an inspection is also due, this should be performed at
the same time.
The service advisor enters two jobs: Repair accident damage and Inspection .
The customer wishes to see these two jobs in the form of items on the bill.
The workshop dealing with this request is very large and has several departments: There is a department for bodywork repair, one for electrical maintenance, and
one for paintwork. The department for bodywork repair also deals with general servicing and repair work.
In this case, entries on job level would not be helpful, since the work to be performed could not be assigned correctly and precisely; you therefore use the Task
Manager.
Task 1: electrical maintenance
· All items belonging to this department are collected here, irrespective of whether they are part of the repair-job or the inspection job.
Task 2: bodywork repair
· All items belonging to this department are collected here, irrespective of whether they are part of the repair-job or the inspection job.
1.11.13 Order Split
Use
This function enables you to split jobs in a DBM order among multiple bill-to parties on the basis of a percentage or fixed amount.
You can perform this function in the following situations, for example:
· If only part of the repairs was carried out
· If more than one bill-to party exists
· If part of the invoice is settled by goodwill or warranty
Integration
If you create a warranty order, the system automatically transfers the warranty category that is valid for this order to the order split and thereby also defines the
associated original equipment manufacturer (OEM).
If you split a service order among different bill-to parties, the system considers this split when it allocates the costs and revenues from the header internal order to
the bill-to party internal orders.
Prerequisites
Before you split an order item, you have assigned the order item to a job.
Features
For each bill-to party, the system generates a split order with its own pricing, that is, also for the sold-to party from the order header. A split number is assigned for
each split order. A split order consists of a split header and split items.
In the split header details, you can, among other things, specify an order type for this split order as well as the allocation of the following services to the bill-to
party:
· Labor values
· Parts
· Other services
Each split header displays the total amount and the split amount according to service. During pricing, the system takes into account pricing conditions of the bill-to
party, such as discount or surcharge, that are stored in the master data.
The split items represent all order items of a specified job. The following data is displayed for each bill-to party:
· Base amount of the order item
· Split amount as a fixed amount
· Split amount in percent
As soon as a split order has been billed, the system locks the associated split amounts. If more than two split orders exist, you can change the split amounts of
the split orders that have not yet been billed; the system continues to take the locked split amounts into account during costing.
Status of the Sold-To Party and Additional Bill-To Parties

The sold-to party from the order header has a particular status in the order split:
· He or she is always displayed as the first split header, that it, with split number 1 .
· The first split header cannot be deleted.
· Provided that no additional bill-to party is added, the sold-to party is always assigned 100% of all services.
· For the sold-to party, the system calculates the differences in the sold-to party’s split order on the basis of the entries for the additional bill-to parties.
· The system considers manual prices, discounts, and surcharges for the sold-to party’s split order only.
If you want to specify different prices for an additional bill-to party, you have to define a fixed amount for this split order.
You can specify various internal and external bill-to parties as additional bill-to parties. You can also create additional split orders for the sold-to party from the
order header.
Splitting Options
You can split amounts as follows:
· For each job
If you specify a fixed amount or percentage rate in the split header details, the system calculates this amount or percentage rate for all labor values, parts, or
other services in the entire job.
· For each order item in the job
If you specify a fixed amount or percentage rate in the split items, the system calculates this amount or percentage rate for the relevant job items. In doing so,
the system adjusts the split amount in the split header details accordingly.
You can add manual texts or standard texts to orders to explain the job; when the order is split, these texts are then displayed on the invoice for each split order.
Activities
To split an order, enter the job number on the Split tab page and copy the data to the split header. You can double-click the split header to copy the data to the
split header details and process it. To add an additional bill-to party, create a new split header.
Example
The dealership Flitzer Repairs and Sales sells vehicles manufactured by the OEM Flitzer and receives a service order for the inspection of a three-year old
vehicle with 35,000 km on the odometer. During the inspection, it is noted that the exhaust pipe has to be replaced and the wiring of a loudspeaker, which was
built in as an extra in the workshop two years ago, has to be replaced.
The three jobs are split as follows:
· Job 1 Inspection: This is charged to the customer.
· Job 2 Replace Exhaust Pipe: This is split according to amounts. Due to that fact that only 35,000 km are on the clock, OEM Flitzer agrees to pay for the
parts (€ 300) and the customer pays for the labor (€ 400).
· Job 3 Wiring of Loudspeakers : This is split according to percentage rate. Since the faulty wiring was due to bad workmanship in the workshop, and the
customer was also partly to blame, since he or she used the loudspeakers incorrectly, the workshop and customer agree to share the costs equally.
First of all, the system assigns 100% of the services in the appropriate jobs to the customer as the bill-to party; the same order type as for the order itself, in other
words, the order type Service Workshop , is used here.
For job 2, choose the order type Service Workshop (Warranty) and enter the OEM Flitzer as the external bill-to party. You then allocate € 300 for the costs of
the parts to the OEM. The system automatically allocates the difference, in other words, the rest of the costs, to the customer.
For job 3, choose the order type Internal Order and enter the workshop as the internal bill-to party. You then allocate 50% of the costs for all services to the
workshop. The system automatically allocates the difference, in other words, the remaining 50%, to the customer.
1.11.14 Pricing
Use
This function enables you to determine the price for DBM orders at header and item level and for jobs and order splits. Furthermore, you can determine the price
for packages. The system takes the appropriate taxes into account and calculates the cost and the profit margin. You can process prices directly in the order at
header or item level, or display and change price data in the pricing conditions overview.
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.
Features
Pricing at header level
The system displays the total sum of the sales prices of all the order items at header level. Here, you can define a fixed price for the order, and discounts and
surcharges separately for parts and labor values. The system splits the fixed price among the relevant items.
Pricing at item level
The system determines the order item prices of the following item categories:
● Part
● Labor value
● Vehicle
● Vehicle features
● Vehicle extras/accessories
For manual parts and labor values, enter a manual price. You can define discounts and surcharges at item level.
Pricing at job level
The system displays the total sum of the sales prices of all the order items in a job at job level. Here, you can define a fixed price for the job, the part items, and
the labor value items. The system splits the fixed price proportionately among all items.
Pricing for packages
The system determines the price for packages without a fixed price in the same way as pricing in the order. You can copy fixed price packages only to jobs to
which no order item has yet been assigned. After you have chosen a fixed price package in the job, the system breaks the package down into its individual order
items. The fixed price is displayed at job level.
Pricing for the order split
During the split, the system creates a split order with its own pricing for each bill-to party.
A service order is split between bill-to party A and bill-to party B. The system creates an appropriate pricing object for each of the following
orders:
■ Service Order
■ Split order for bill-to party A
■ Split order for bill-to party B
Tax determination
In Dealer Business Management (DBM), the system determines value-added tax (VAT) in the same way as the standard system. For Germany, the tax on
used parts applies. For more information about how to proceed when dealing with tax levied on used parts, see SAP Note 109005.
Fast entry of conditions
In Customizing for Dealer Business Management (DBM) under Order ® Order Type ® Define Order Type, in the subscreen Pricing, field Fast Entry
Schema, you can enter a fast entry check schema that groups together different DBM order types (for example, service order and service returns order) with the
same behavior as regards pricing fast entry.
In Customizing for Dealer Business Management (DBM) under Order ® Item Category ® Define Item Category for Order, there is a similar field ( Fast Entry -
Item Category ) that defines an item category as a reference for the pricing fast entry fields (see Customizing for Dealer Business Management (DBM) ® Order
® Pricing ® Define Fast Entry of Conditions ).
If you do not make entries in these two fields, the system uses the order type and the item category as the relevant value for fast condition entry. If you entered an
order type schema in the field Fast Entry Schema , and an item category in the field Fast Entry - Item Category , the system uses these two entries. The
following table shows the effects of the values in these two fields on the corresponding value for the fast condition entry.
Fast Entry Schema - Order Type Fast Entry - Item Category Order Type - Use Item Category - Use
No No Order Type Item Category
Yes Yes Fast Entry Schema - Order Type Fast Entry - Item Category
No Yes Order Type Fast Entry - Item Category
Yes No Fast Entry Schema - Order Type Item Category
You can use the Business Add-In BadI: Enhancement for Pricing to change fields in the communication structures for pricing.
For more information, see SAP Note 1017729.
1.11.15 Down Payment List
Use
You can use this function to create a down payment request in the DBM order, and post and clear the down payment.
Integration
The system assigns the down payment request to the split header level of the order.
Prerequisites
You have defined a number range in Customizing for Dealer Business Management (DBM) under Order ® Specific Processes ® Define External Number
Range for Down Payment Request.
Features
● Creation of a down payment request
● Payment of a down payment request
● Posting and clearing of a down payment
Activities
Create Down Payment Request in the DBM Order:
1. You can create a down payment request from the DBM order by choosing Down Payment List. The system displays a dialog box, where you can display
existing down payments, and create a new one. When you save your entries, the down payment request appears in the down payment list.
Instead of from the DBM order, you can also create the down payment request from the SAP Easy Access screen via Accounting ® Financial Accounting ®
Accounts Receivable ® Document Entry ® Down Payment ® Request (F-37).
2. The system stores the down payment request as a noted item.
You can call up a list of these items from the SAP Easy Access screen via Accounting -> Financial Accounting -> Accounts Receivable ->
Account -> Display/Change Item (FBL5N).
3. The system displays the down payment request as an open item in the cash desk.
Create Down Payment in the Cash Desk:
You handle payment of the down payment request in the transaction Cash Desk (/DBM/CASHDESK). Here you can display a list of the open items still to be
paid. You can copy the down payment amount to the Total Amount field by double-clicking on the item.
The system generates a billing document.
Post and Clear Down Payment:
You can check that the down payment has been posted and cleared by displaying the clearing document via transaction Display/Change Item (FBL5N).
The system deducts the down payment amount from the invoice amount during settlement.
Example
Creation of Down Payment Request in DBM Order
a. Document no. b. Date c. Amount d. Status
e. 1400000154 f. 27.10.2006 g. 500,00 € h. Red (not assigned)
Creation of Down Payment in Cash Desk
i. Document no. j. Date k. Amount l. Status
m. 1400000155 n. 27.10.2006 o. 500,00 € p. Red (not assigned)
q. 1400000154 r. 27.10.2006 s. 500,00 € t. Green (processed)
Creation of Billing Document
u. Document no. v. Date w. Amount x. Status
y. 1600000032 z. 27.10.2006 aa. 500,00 € bb. Red (not assigned)
cc. 1400000155 dd. 27.10.2006 ee. 500,00 € ff. Processed
gg. 1600000032 hh. 27.10.2006 ii. 500,00 € jj. Processed
kk. 1400000154 ll. 27.10.2006 mm. 500,00 € nn. Processed
Posting of Outstanding Payment
oo. Document no. pp. Date qq. Amount rr. Status
ss. 1400000154 tt. 27.10.2006 uu. 500,00 € vv. Processed
ww. 1600000032 xx. 27.10.2006 yy. 500,00 € zz. Processed
aaa. 1400000155 bbb. 27.10.2006 ccc. 500,00 € ddd. Processed
eee. 1600000032 fff. 27.10.2006 ggg. 500,00 € hhh. Processed
The statuses are indicated by traffic lights in the system:

Red = Not assigned
Yellow = Assigned
Green = Processed
1.11.16 Start Collective Billing
Purpose
This process enables you to select all open orders that are due for billing, and collect them in one billing document. This is useful for customers who prefer to
receive an invoice containing all open (not yet billed) orders at regular intervals.
Prerequisites
● You have generally entered no copy requirements for DBM billing types in Dealer Business Management (not especially for Collective Billing) in
Customizing for Sales under Billing ® Billing Documents ® Maintain Copy Control for Billing Documents ® C opy Control: Sales Document to
Billing Document . Ensure that the billing quantity for the order quantity is set to C . Although the DBM order can be split, the invoice always considers the
full amount. Ensure that the pricing type is set to G .
● In Customizing for Dealer Business Management (DBM) under Order ® Specific Processes ® Define Collective Billing Indicator, you have defined the
order types (control codes) for which collective billing is valid.
● In transaction Change Customer (VD02), you have selected one of the values All Orders , Service Orders or Parts Orders via the pushbutton DBM
Sales Areas in the field Collective Billing . By doing this, you define customers as relevant to the collective billing process. The system copies the entry
from this field into the order header data as default value.
Process Flow
1. If the orders do not yet exist, you can create them (for example, service, parts, or vehicle orders).
A Collective Billing indicator exists in each split header. Check that the Collective Billing indicator is set in the order. You can also see this in the customer
data. If required, you can change the Collective Billing indicator in the order manually, irrespectively of the settings in the customer master.
The Collective Billing indicator in the order takes priority over the indicator in the customer data, in other words, it has a controlling nature for the
process (whereas the indicator in the customer master does not).
If the indicator is not set in the order, and partial billing has taken place for the sold-to party, you cannot set the Collective Billing indicator
anymore.
2. You post the goods issue or confirm the labor values.
If you split the order, you should also set the Collective Billing indicator to split level.
3. On the SAP Easy Access screen, select Logistics ® Logistics Execution ® Dealer Business Management ® Order Processing ® Collective Billing
(/DBM/COOL_BILLING).
4. On the selection screen Start Collective Billing screen, enter the organizational data, customer data, DBM orders, and order type. You can also set the date
when the system should create the billing document. Now select Execute. If you want the system to execute a collective billing overnight, you can schedule a
batch job.
5. The system selects the orders that meet the following requirements:
○ Orders that meet the criteria that you entered
○ Orders in whose order header data you have set the Collective Billing indicator
○ Orders that are relevant for billing with regard to their status
It is sufficient if a single job in the order has a status that is relevant for billing.
6. The system shows you an ALV list of the DBM orders you have selected. It contains customers (sold-to party and payer), the invoice type (invoice or credit
memo), and other relevant data.
The system only selects the DBM orders that have the Collective Billing indicator set and have the correct Order Engine status (confirmation of
labor values, goods movements of parts). If the system finds an order that is incomplete or has missing data, it skips the order during collective
billing, akin to the standard collective billing process.
You can view the system messages that the system generates during collective billings in a log. To do so, select Environment ® Display
Collective Billing Logs from the Start Collective Billing screen.
7. You can branch to the DBM order and the customer master directly from the DBM Collective Billing screen. There is also a standard ABC analysis that
allows you to analyze the net values of invoices. Report /DBM/COLL_BILLING_REORG allows you to redetermine the collective billing index in a certain
number range of orders. To avoid problems during processing and to prevent performance problems, no orders in the value range should be open when you
execute the report. Do not execute this report during normal office hours.
8. Select the required DBM orders from the list and start the collective billing via Process ® Start DBM Collective Processing . The system generates one
billing document.
9. You can leave the DBM order and access the Document Flow via Goto ® Document Flow . The system displays the billing document.
10. You can print the document directly or by using the print function in the DBM order.
You can use collective billing functions for returns. In this case, you would have to select all the DBM orders involved, create credit memo, and
execute collective billing on this.
You cannot use collective billing for internal orders or orders with revaluation. In addition, you cannot reverse billing documents that you created via
the collective billing function.
Result
You have created one invoice for more than one order. The system has updated the order statuses.
Cancellation of Billing Documents in a DBM Order
Use
You can use this function to cancel steps you have executed in either a partially or completely invoiced DBM order. You can cancel billing documents, change
vehicles, and execute billing again. You may wish to do this for the following reasons, for example:
● if the address of a customer is incorrectly maintained in the master data
● if items are missing in the DBM order
● if prices are incorrect
In other words, you can use this process to cancel one or more individual billing documents within the order, irrespective of whether the DBM billing process is
complete or not.
Integration
You cannot use this function for the following:
● internal service orders with revaluation
● service orders workshop warranty
● collective billing documents
● cross-company code transfer postings for vehicle
Prerequisites
No SD orders exist.
Features
● A Cancel Billing functionality in the DBM order.
In the case of a partially or totally invoiced order, the Cancel Billing function appears in the DBM order after the first billing document has been created. If
there are several billing documents for a DBM order and you wish to cancel them individually, you always have to cancel the most recent one first.
Alternatively, you can cancel them all in one step.
Five billing documents belong to one DBM order. You want to cancel the third one. You have two options:
● You cancel only the most recent billing document (billing document number 5), then you repeat this cancellation step twice, thus canceling billing document 4
and then 3. To do this, choose Cancel Billing in the order.
The system executes event BILLING_CANCEL (Cancel Last Billing Document).
● You cancel all the billing documents in the DBM order in one step. To do this, choose Event in the order, and then choose the event BILLING_ALL_CANC
(Cancel All Billing Documents).
Activities
1. You reopen the DBM order and choose either Cancel Billing or Event and Cancel All Billing Document s.
2. The system cancels the settlements that have been created in CO-PA from the internal orders for the bill-to parties.
3. The system resets the internal order on the first level and cancels the transfer posting from this internal order to the internal orders for the bill-to parties.
4. The system sets the deletion flag for the internal order for the bill-to party.
5. The system cancels the billing, accounting, and controlling documents.
6. The system updates the document flow and the status of the vehicle.
1.11.18 Value Flows for Service Orders
Purpose
With this process, you can collect the costs and revenues according to different information and use these to analyze the contribution margin. Depending on the
level at which you want to map the value flow for service orders, the following contribution margin analyses are possible:
● For each service order (level 1)
● In accordance with compatible selection criteria from the internal order, such as vehicle or customer (level 1)
● For each bill-to party (level 2)
● In accordance with any criteria and their values known in the service order (level 3)
You can also use collective internal orders to represent a short-term breakeven analysis and use and create Profitability Analysis reports.
Process Flow
The following graphic shows the posting transactions for costs and revenues, from the service order through the profitability analysis:
1. As soon as you create a service order, the system generates a header internal order for the service order in Controlling. This enables you to examine the
contribution margin on the basis of individual orders and on the basis of summarizing selection criteria (such as vehicle) within Overhead Cost Controlling.
At the same time, the system generates the settlement rules that you require for the profitability analysis automatically on the basis of order control.
2. During billing, the system splits the costs and revenues among the individual bill-to parties for the service order. If only one bill-to party exists, the system
only reposts one bill-to party internal order.
Depending on the customizing settings, you have the following options within this step:
○ You use only the header internal order. In this case, contribution margin calculations per bill-to party and transferring the values is not possible.
○ You use collective internal orders to collect all costs and revenues of the same type, such as the same defect code, same vehicle, or same vehicle
category. This enables you to display a short-term breakeven analysis for specific warranty cases (Level 1), for example.
○ For each bill-to party, the system automatically generates a bill-to party internal order (Level 2) for the service order from the order control.
This enables you to consider the bill-to party, such as customer, vehicle, or warranty, during the contribution margin analysis.
There are two options for service orders during settlement of bill-to party internal orders:
○ The system accounts bill-to party internal orders in the profitability analysis. This requires the creation of an internal billing document during the posting of
the header internal order in Step 1.
○ If no internal billing document was created, the system only collects the costs in the bill-to party internal orders, and then bills these to the cost object.
The system does not bill to the profitability analysis.
The system establishes the relationship between cost object and bill-to party internal order in the following way:
a. The system checks whether it should create an internal billing document, and whether it should bill revenues from the cost object to the bill-to party
internal order. If this is the case, the system creates an internal billing document and posts the revenue from the cost object to the header internal order. If
no internal billing document is required, the system posts no revenue.
b. The system creates one bill-to party internal order each for all bill-to party internal orders entered in the service order.
c. The system creates the settlement rule for the bill-to party internal orders. If the system did not create an internal billing document during Step 1, it bills
the revenues and costs of the bill-to party internal orders directly to the cost object. If an internal billing document exists, the system configures the
settlement rule in such a way that the costs and revenues of the bill-to party internal orders are billed to the profitability analysis.
d. The system reposts all revenues and costs of the header internal order to the bill-to party internal orders.
The system created the settlement rules for the bill-to party internal orders and distributed the values to the bill-to parties.
3. If you want to use a profitability analysis, you can transfer the values to the profitability analysis by creating internal billing documents during the posting of
the header internal order. The system provides the characteristics of the profitability analysis via the settlement rule or the standard derivation based on it.
This enables you to examine the contribution margin in accordance with any information in the service order, that is, characteristics and their values. You can
use the profitability analysis reports and create your own reports based on drilldown reports.
You can transfer all customer, vehicle, and workshop-specific information known in the service order, or that can be derived from the service order, to the
characteristics defined in the profitability analysis, and, to a limited extent, different material groups. To distinguish different material groups, you have to use
different cost elements for different material groups.
1.11.19 Cash Desk Processing
Use
This function enables you to post incoming and outgoing payments during daily business activities. The system guides you through business activities that define
the following information, among other things:
● Operational account assignment
● Tax code
● Posting text
In cases where an error occurs during the FI posting, you can post the cash document again, either directly from cash desk or in a separate transaction.
Integration
The system transfers and posts the data to Accounting (FI) automatically. You can also branch directly from the cash journal to Accounting .
From this function, you can then navigate directly to cash sales of parts in order processing to post payments for parts.
Prerequisites
● A cash desk work center with a till drawer and a printer for receipts is set up on your PC.
● You have defined the business transactions and settings for the cash desk work center in Customizing for Dealer Business Management (DBM) under
Cash Desk.
Features
General Options
● Create a cash document for incoming and outgoing payments (for customer and vendor)
● Select open items and display totals or difference amounts
● Enter a document header text for cash documents
● Carry out posting with or without printing a receipt
● Cancel a cash document
● Check the current amount in the cash desk
● Open a cash desk with a void receipt without posting
● Display the cash journal and a list of postings for each cash desk for a specific period
● Repost items, for which previous FI postings have failed, either directly using the Cash Desk transaction ( /DBM/CASHDESK ) or by using the Cash Desk
Reposting transaction ( /DBM/CASHDESK_RP ).
Incoming Payment - Customer
You can call up and clear open invoices and credit memos from customers using the customer number, matchcode, or directly from the document number.
You can choose one or more invoices for the payment. The system also takes into account the current terms of payment. If, for example, the customer is entitled to
a cash discount, the system automatically calculates the amount of the cash discount as well as the total amount minus the cash discount amount.
The payment is cleared in Financial Accounting as soon as you post the payment. You can choose whether you want to print a receipt at the same time as you
post the payment.
Outgoing Payment - Vendor
You can call up credit memos for customers and post payments using the customer number, matchcode, or directly from the document number. The posting
reduces the cash desk amount and, at the same time, clears the credit memo in Financial Accounting.
Outgoing Payment - Customer
You can call up open invoices and credit memos for vendors and post payments using the customer number, matchcode, or directly from the document number.
You cannot post a payment that is greater than your current cash desk amount.
Incoming Payment – G/L Account
You can make an incoming payment to a G/L account to post a cash transfer, for example. To do so, you select a suitable business transaction with a cost center
and tax code for the incoming payment.
Outgoing Payment – G/L Account
You can create postings using predefined business transactions.
Cancellation
You can cancel documents only within an active session before the cash desk is closed. To cancel a document, you have to enter a descriptive text.
Cash Journal
The system displays an overview of the active sessions and closed sessions. You are shown information, for example, about the cash desk work center and the
opening and closing amounts.
You can call up an overview of the postings for a session. The system displays the following data, for example:
● All incoming and outgoing payment postings including amounts
● Cash document cancellations
● Document header texts entered
● The user who performed the action in the session
● Postings carried out correctly and postings with errors
● Total cash documents entered
You can also navigate directly to the document display.
Cash Sales
A cash sale is equivalent to a parts order in that open items are cleared, and you can create receipts directly. You can use this function to call up and clear parts
orders and delivery notes that have already been created, in the same way as in parts order processing. You can switch between OEMs during processing.
Reposting
You can repost cash documents for which errors occurred by using the reposting function. You can access this function in one of the following ways:
● Directly using the transaction Cash Desk (/DBM/CASHDESK)
Display the cash journal, select the cash desk document for which you wish to repeat the posting, and choose Repost.
● By choosing the transaction Cash Desk Reposting (/DBM/CASHDESK_RP), entering the company code and cash desk work center ( CDWC ) and
choosing Execute
The system displays a list of erroneous cash documents. Select the cash document you wish to repost and choose Repost.
During reposting, the system locates the cash desk document and relevant data that have already been generated. Since the cash document already exists, it
does not have to be recreated. The system only updates the data.
The system then checks whether the FI document has been created or not. If not, the posting date is filled with the current date. If an FI document exists, the
posting date remains the same.
You can check the result of reposting in the cash journal.
To adapt the cash desk function, you can use the Business Add-In (BAdI) BAdI: Enhancement for Cash Desk .
Activities
For transactions Cash Desk and Cash Desk Reposting , go to the SAP Easy Access screen Logistics ® Logistics Execution ® Dealer Business
Management ® Cash Desk Processing ® Cash Desk (/DBM/CASHDESK) and ® Cash Desk Reposting (/DBM/CASHDESK_RP).
To perform actions in the cash desk, open a session when you start the cash desk. Several users can make postings within a session. The system assigns the
next free session number automatically. To close the cash desk, exit the session. More than one user cannot work in the same cash desk simultaneously.
1.12 Storage Goods Manager
Use
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 on the SAP Help Portal
(help.sap.com) under Documentation ® mySAP ERP ® SAP ERP Central Component ® SAP ERP Central Component ® Logistics ®
Sales and Distribution (SD) ® Output Determination (SD-BF-OC).
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.
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.
● There are the following actions:
EXP List Overview
REM Reminder
SCP Confirm Putaway in S torage
SCR Confirm Removal from S torage
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
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.13 Time Management
Purpose
You use this component to enter the working time of an employee on order and cost-center-related activities using a terminal, and transfer it to the Cross-
Application Time Sheet (CATS). Time management includes postings such as Clock On and Clock Off , confirmation of completed work, and an error log of the
time events that could not be posted to CATS.
Integration
The data recorded within time management is required for cost accounting (CO) and Human Resources (HR). Time management provides standard components
with data for CATS time recording and further processing. A restricted master record in personnel administration for each employee (mini-master record) is
sufficient for time management in DBM.
For information on how to set up the system to handle Time Management, see the Customizing for Dealer Business Management (DBM) under Service ®
Time Management .
You can find general information on CATS under Cross-Application Time Sheet (CATS) and on the SAP Help Portal under http://help.sap.com ® SAP ERP
® SAP ERP Central Component ® SAP ERP Central Component ® Cross-Application Components ® Cross-Application Time Sheet (CATS) .
Features
Time management comprises the following functions:
● Recording of Time Events
● Time Events Error Log and branching to CATS
● Automatic Clock Off of Open Orders
● Target/Actual Comparison in DBM Order
There are three levels for booking of time on the DBM Order: Order header level, Task level, and Item level. For more information, see Determination of Criteria for
Use of Time Management in Customizing for Dealer Business Management (DBM) .
Constraints
You cannot correct time events in DBM; you must branch from the error log to the appropriate CATS records.
1.13.1 Recording of Time Events
Use
Employees can use this function to record their personnel and working time data at their respective terminals. The system transfers the data directly to CATS.
You can find the customizing tables for assigning internal orders to a time event in Customizing for Dealer Business Management (DBM) by
choosing Service Time Management ® Determination of Internal Order .
Integration
To use the terminal to post time events to CATS, the system requires specific personal data from personnel administration on each employee. This application
also includes the time event catalog from the Human Resources standard system. The following system events are initially defined and can be used to define your
own time events types in Customizing for Dealer Business Management (DBM) under Service ® Time Management ® Definition of Time Event Types ®
Define Customer-Specific Time Event Types:
● Coming
● Leaving
● Coming and Start of Work
● Start of Work
● End of Work
● Break
● Confirmation
Prerequisites
● In the HR master record, you have used transaction PA30 to maintain the infotypes 0000 ( Personnel Action ), 0001 ( Organizational Assignment ), 0002
( Name ), 0050 ( PIN ) and 0315 ( Sending Cost Center ) for each employee.
● To be able to record times, employees (terminal owners) must be authorized to access terminals. You must have assigned them implicitly or explicitly as
time recorders to the terminal.
The explicit assignment overrides an existing implicit assignment and is particularly useful if you want to allow individual employees that you want
to use as stand-in staff to log on to different terminal groups.
○ In implicit assignment you have done the following in Customizing for Dealer Business Management (DBM) ® Service ® Time Management ®
Definition of Terminals:
■ allowed particular employee groups to generally record times at terminals under Define Admission to Terminal on Basis of Personnel Structure.
■ assigned a terminal group to the personnel subgroup that the employee is assigned to under Define Admission to Terminal on Basis of
Organizational Structure .
The combination of employees based on personnel structure and employees based on organizational structure provides the number of employees
for a terminal group.
To program alternatives for implicit assignment, you can use BAdI /DBM/BADI_TM_VT_DATA Correction of Employee Assignment to Terminal .
○ In explicit assignment, you have assigned an employee to a terminal group and as a stand-in for other terminal groups directly in the HR master record
by way of transaction PA30.
● In Customizing for Dealer Business Management (DBM), you have grouped, by choosing Service ® Time Management ® Grouping Time Event
Types and Cost Centers, and defined terminals and terminal groups under Definition of Terminals.
Features
Recording of Time Events

Employees can record their times by using the transaction Create Time Stamp (/DBM/TM_VT) or by choosing Logistics ® Logistics Execution ® Dealer
Business Management ® Time Management ® Create Time Stamp from the SAP Easy Access screen. You can activate/deactivate the PIN for recording
in Customizing for Dealer Business Management (DBM) by choosing Service ® Time Management ® Definition of Terminals ® Define Terminal Group .
The Create Time Stamp screen consists of the following parts:
● Screen with the following fields:
○ Personnel number
○ Cust Event Type
○ PIN
○ Procurement
○ Job
○ Cost Center
○ Internal order
○ Item number
○ Status ID
○ an indicator for setting a final confirmation
● DBM Order tab page
● Internal Order tab page
Recording Time Events for Stand-Ins

Stand-ins are employees that can work at different work centers and therefore post time events to different terminals. To use employees as stand-ins, assign them
to different terminal groups directly in the HR master record. To do this, you must maintain the customer personnel infotypes. You can define this info type yourself.
For more information on defining info types, see the DBM Customizing.In Customizing for Dealer Business Management (DBM) under Service ® Time
Management ® General Settings ® General Settings for use of Time Recording, you enter the info type that you have created in the field Infotype expl.
ass. (info. type for explicit assignment employee – terminal). Stand-ins log on to the terminal and record their times in the same way as employees that are only
assigned to one terminal group.
Activities
1. As an employee, you use your personnel number and, optionally, PIN code for authorization purposes when you want to record your times. You can enter the
personnel number directly, or select it from the employee list.
2. If you want to change the default time event type, select the appropriate time event type from the input help or enter it directly. Depending on the time event
type, after selecting the event, you must specify further details, such as the order number of a released order.
3. The system sets the date and time of time events (the time stamp) and validates the entered data. The system checks that:
○ whether the employee is approved for the terminal
○ whether the order is released for recording
You can use BAdI: Check and Adjustment of DBM Order Number /DBM/BADI_TM_ORD_CHECK to specify the release criteria for a DBM
order and to swap the DBM order number for a different number.
4. The system groups two time events that follow each other in pair formation and saves the time data in CATS. The system can transfer the working times
generated in this way in CATS to cost accounting, together with the account assignment attributes.
You can use BAdI Event Processing /DBM/BADI_TM_EVENT_PROC to revise the CATS records again before saving to the database, and to
implement the follow-up activities after saving to the database.
1.13.2 Time Events Error Log
Use
You can use the error log to display the time events that could not be posted to CATS.
Integration
You can branch from the DBM error log directly to CATS and make corrections there.
Prerequisites
● Filter the list of errors according to areas of responsibility: In Customizing for Dealer Business Management (DBM), you have specified areas of
responsibility by choosing Service ® Time Management ® Global Settings ® Define Areas of Responsibility for Display of Error Log .
Features
If a time event pair cannot be posted to CATS, the system displays a warning message on the terminal at the time of the most recent time event. To get an
overview of errors, access the time events error log by entering transaction code /DBM/TM_ERRORS Error Processing) or by choosing Logistics ® Logistics
Execution ® Dealer Business Management ® Time Management ® Error Processing from the SAP Easy Access screen . The non-posted time
events are red in the error log and warnings are yellow. In addition, the system displays other time events that are related to the non-posted time event. For details
on the relevant non-posted time event, choose Details .
To make corrections at a later point easier, if possible, the system generates a placeholder data record in CATS for non-posted time events. This is not possible if,
for example, the affected personnel number is being processed in CATS.
Activities
1. To see the incorrect CATS records for a particular employee, double-click on the employee’s name to select the employee.
To correct time recording data in CATS, double-click on the entries displayed in red.
Note that the error display relates to the time event pair's CATS record. The selected time event for the CATS record provided the ending time. All
other data in this CATS record originates from the previous time event.
2. When you have corrected the error in CATS, set the CATS Entry Controlled indicator in the time events error log. This only helps you to see the records that
you have already processed.
3. You can refresh the display by choosing Refresh Error List.
1.13.3 Automatic Clock-Off
Use
You can use this function to ensure that no orders or time stamps are left open at the end of a working day. The system automatically clocks off at a certain time.
Schedule the report that performs the automatic clock off for after the clock-off time, but before the date changes.
Prerequisites
In Customizing for Dealer Business Management (DBM), by choosing Service ® Time Management ® General Settings for Use of Time Recording , you
have made the appropriate settings and entered a value in the Aut. Time field. This value is the time at which the system performs an automatic clock off. You
can specify this time for individual terminal groups under Define Terminal Group by choosing Time Management ® Definition of Terminals ® Define
Terminal Group .
Features
From the SAP Easy Access screen, you can access a report for automatic clock-on and clock-off by choosing Logistics ® Logistics Execution ® Dealer
Business Management ® Time Management ® Automatic Clocking On and Clocking Off (transaction code: /DBM/TM_AUTO_PUNCH).
Activities
1. On the DBM Time Recording: Automatic Punching Out screen, enter the following parameters:
a. Terminal
b. Terminal Group
c. Day of Finish Time Stamp
2. Choose Execute.
Target/Actual Comparison in DBM Order
Use
You can access the target/actual comparison in the DBM order to check whether the actual times recorded deviate from the target working times for the order. This
enables you to, for example, determine whether an invoice can be logically created and avoid miscalculations due to incorrectly recorded working times.
Integration
The target/actual comparison is integrated into the DBM order.
You can use the BAdI Calculations for Target – Actual Comparison /DBM/BADI_TM_TARGET_ACTUAL for programming, to:
· change the target/actual output data to, for example, enable the time to be specified in industry minutes
· calculate the actual data and prices for the order
Prerequisites
· In Customizing for Dealer Business Management (DBM) under Order ® Interface Control ® Layout ® Assign Criteria , the order type of the order is
assigned a layout that includes the target/actual comparison.
· In Customizing for Dealer Business Management (DBM) under Service ® Time Management ® Global Settings ® Define Variance Tolerances for
Target/Actual Comparison , you have determined at which deviation percentage the traffic light is displayed red, yellow or green.
Features
When you access the Target/Actual Comp. tab page in a workshop order, the system creates a current target/actual comparison of the working times.
The system displays:
· Actual-Target Overview: a view with the total target and actual time for the entire order, the deviation in hours and a traffic light that displays the status of the
order. Depending on the deviation tolerances determined in Customizing, the traffic light for the current order is red, yellow, or green.
· Cumulated Amount per Employee: a view with the following details:
¡ Employee's name
¡ Personnel number
¡ Total recorded times for each employee
¡ Total target times for each employee. The proportionate target times for each employee are calculated using the following formula:
¡ Target time (employee) = target time (total) * [actual time (employee) / actual time (total)]
¡ Unit of measure
¡ Currency
¡ Trade price: actual times multiplied by the cost rate of the appropriate mechanic. The cost rate depends on the data stored in the HR master record in the
Plant , Master Service Type and Sending Cost Center fields of infotype 315 for the mechanics.
¡ Sales price: cumulated value of all work positions multiplied by the respective allocation value.
¡ Times and prices for each employee as well as a total row with the total target and actual times and the sales and purchase prices for the total order.
· Single Time Stamps: a view with the individual stamps from CATS and the employees that have clocked on an order, but have not yet completed it. These
are displayed as red.
Updating the Target/Actual Comparison

Choose Refresh Times to update the details in the views.
Incentive and Commission Management
Use
This function provided by the standard 1.14 Incentive and Commission Management (ICM) solution enables you to calculate and settle commission. It
supports the design of incentive compensation plans, organizational management and the remuneration calculation for commissions, bonuses and target
agreements. In ICM there are commission contracts (legally independent contracts between a company and a commission contract partner that may contain a
general commission contract agreement, a remuneration agreement or a payment agreement) and commission cases that identify business transactions relevant
to commission.
Integration
ICM in vehicle sales provides the following:
· in the DBM order and the DBM quotation, a function allowing commission simulation, in other words, the system calculates how much commission a sales
representative earns when he completes a deal
· DBM-ICM interface: When calculating commission, for example, this interface allows the system to transfer the DBM order and vehicle data to ICM. ICM then
calculates the commission and returns the calculated commission to the DBM order.
Prerequisites
You have made the appropriate settings in Customizing for Dealer Business Management (DBM) under Order ® Incentive and Commission Management.
Features
ICM allows you to do the following:
· simulate commission in the DBM order and DBM quotation. The system automatically triggers the creation of a commission’s case when a billing document is
created. The system then displays the commission amount in the pricing condition, and the commission document in the document flow.
· trigger the creation of a commissions case in the DBM order when you create the DBM billing document. The commission’s case is displayed in the document
flow of the DBM order.
· trigger the cancellation of the ICM commission’s case when you cancel the DBM order
· track remuneration documents (displayed in the document flow of the DBM order)
· calculate and settle target agreements in ICM
1.15 Methods of Taxation

Taxation laws differ from country to country. To be able to calculate the tax incurred and also the subsequent billing correctly, you have to be able to represent the
former by different taxation methods in the system. Below you can find some information on margin taxation (taxation of the margin). This method of taxation can be
used during the purchase and sales of used vehicles in Switzerland, for example.
Margin Taxation in Switzerland

The method of margin taxation is a regulation set by the Swiss Value-Added Tax (VAT) Fiscal Code that can be used on the purchase and sales of moveable
goods, in this case motor vehicles. The law in its present form has been valid since the introduction of the revised VAT law of 1st January 2001.
Currently, there are two methods of taxation for the purchase and resale of used vehicles:
1. Standard taxation (input tax deduction on purchase, VAT levied on the entire sales price)
2. Margin taxation (without input tax deduction, for example when a private customer purchases the vehicle; VAT is only levied on the difference, or margin,
between the original purchase price and the sales price)
As soon as a dealer acquires a used vehicle, whether by purchasing it or taking it as a trade-in, the taxation method required for this vehicle takes effect. In some
cases, the taxation method can be different and has to be adapted to the vehicle. If the vehicle is sold later, this note regarding determination of the correct tax
amount with respect to the vehicle item has to be taken into consideration both on the invoice and in any dealings with the tax authority.
For further information on margin taxation, see Standard and Margin Taxation.
In some places in the system and documentation, you may find the term “differential taxation” being used as a synonym for “margin taxation”.
1.15.1 Standard and Margin Taxation
Purpose
You can use this process to define the method of taxation that is used during the purchase and sale of used vehicles, and also to determine the correct amount of
value-added tax (VAT) depending on whether you are using standard or margin taxation.
It allows you to do the following:
· enter and store the required basic data for vehicles
· change the taxation method by using specific actions before the resale of vehicles
· determine the correct basis for the calculation of VAT during the billing process
Margin taxation is not relevant to every country; this method of taxation is used, for example, in Switzerland.
Prerequisites
· A suitably-trained employee has determined the method of taxation to be used (standard or margin taxation) and entered it manually in the vehicle data. In the
case of margin taxation, the original purchase price must also have been entered in the system.
· The decision to use margin taxation must take place before the goods receipt is posted.
If the indicator for margin taxation has not been set, posting takes place using the standard taxation method. You cannot change the taxation
method from standard to margin without first canceling the goods receipt.
If you wish to use margin taxation:
· Create new vehicle (transaction /DBM/VM). Select Create Vehicle ensuring that Vehicle Business Transaction USC is selected.
· In the vehicle master, you have selected the Margin Taxation indicator.
You can only set this indicator if you are dealing with a vehicle of category USC, in other words a used vehicle, or after you have executed action
QCDT ( Differential/Margin Taxation (DBM) ). You can then find this indicator in the data overview and in the vehicle data of the vehicle master.
You can display the details for this indicator later in the VMS vehicle history.
· You have set the indicators for input tax and output tax.
· You have made the appropriate Customizing settings. You can find further information on which settings to make in the attachment to Note 1009665 .
Process Flow
The different taxation methods influence the amount that is taken as a basis for determining the value-added tax (VAT). Whilst in the standard taxation method the
entire sales price forms the basis for calculating the tax, the margin taxation method uses the difference between the sales price and the original purchase price.
If the vehicle is sold using the margin taxation method, the original purchase price does not change even if the dealer services the vehicle or installs additional
parts in the vehicle before selling it on. These activities simply increase the stock value of the vehicle and only influence the sales price (indirectly).
If a vehicle that already exists in the system (for example, it has been sold as a new vehicle before) is purchased back, you should use interlinked action QRPU
(Repurchase Used Vehicle) . By using this action, the margin taxation flag can also be set. For more information on elementary action QTIP (part of QRPU ),
see Action QTIP: Prepare Repurchase of Vehicle.
If during a vehicle acquisition the vehicle is transferred within the same company or group of affiliated companies (both parties being registered under the same
number for tax purposes), for example between dealers, this has no effect on the original purchase price.
Dealer A purchases a used vehicle for 8 000 € and later transfers it to dealer B for 6 000€ (no billing takes place within the same tax object).
Dealer B then sells the vehicle to a customer for 10 000 €. The basis for determining the tax to be paid is still 2 000€, since the original
purchase price stays fixed at 8 000€.
If the margin taxation method is used for the resale of a specific vehicle, the primary factors for determining the VAT are the original purchase price and the final
sales price. Factors such as the costs incurred by the dealer for maintaining the vehicle are irrelevant. If the vehicle is sold at a loss, the VAT related to this
vehicle is zero. If other accessories and parts are sold together with the vehicle in the same DBM order, such as new winter tires or a roof rack, the VAT is
calculated for these items separately from the vehicle. The flat rate for delivery is an exception. This is added to the vehicle sales price and then compared with
the original purchase price.
If the sales price (plus delivery flat rate) is less than the original purchase price, the tax payable on the vehicle is zero and not negative.
As soon as the standard taxation method is used on a specific used vehicle, this method remains valid for the vehicle until it is sold. In other
words, if standard taxation has been defined for the vehicle, either at the time of the original purchase or as a result of later activities on the
vehicle, the standard taxation method must be retained until the vehicle is billed when it is resold.
This does not apply to the margin taxation method. After the purchase and acquisition of the vehicle, the dealer can make certain changes to it
that, from a legal point of view, require a transfer form margin to standard taxation.
Examples
Example 1: Margin Taxation

A dealer accepts 10 000 € as a trade-in for a used vehicle; and cannot assert a claim to any input tax for this business transaction.
Later the dealer sells the vehicle at a price of 12 000€; the VAT is already included in this price.
The dealer is obliged to pay tax to the authorities of currently 7.6%, not on the entire 12 000€, but on the difference between the final sales price and the original
purchase price: 12 000€ - 10 000€ = 2 000€.
In this case, the dealer pay tax on only 2 000€: 2 000€ x 7.6% / 107.6 % = 141,26€ is paid to the tax authorities.
Example 2: Standard Taxation
If the dealer had been able to deduct the input tax form the purchase price during the trade-in, the vehicle would have to be sold later using the standard taxation
method, for which the basis for calculating tax is the total sales price of the vehicle.
If we use the same values as in the first example, the tax authority would receive the same amount of VAT at the time of sale of the vehicle.
The dealer demands the following amount of input tax from the original purchase price of 10 000€ (VAT included) of the vehicle: 10 000 € x 7.6% / 107.6% =
706,32 €.
After the sale of the vehicle for 12 000 €, the dealer pays VAT on 12 000 € x 7.6% / 107.6% = 847,58 €.
The difference between the input tax and the VAT is 847,58 € – 706,32 € = 141,26 €. This is the same as the amount calculated for the margin method of
taxation.
Example 3: Margin Taxation

The following table shows the calculation of VAT based on the margin method of taxation for four alternatives. The invoice amount as basis for the VAT with respect
to the entire DBM order is the same, larger, or smaller than zero. The influence of accessories, for which the standard taxation method takes effect, is displayed.
Alternative 1: Alternative 2: Alternative 3: Alternative 4:

Vehicle (margin) Vehicle (margin) Vehicle (margin) < 0 Vehicle (margin) > 0
Business (margin) Business (margin) > 0 Business (margin) < 0 Business (margin) > 0
Original purchase price 23,250.00 23,250.00 23,250.00 23,250.00
Sales price 23,000.00 23,000.00 22,000.00 24,500.00
Flat rate for delivery 1) 250.00 250.00 250.00 250.00
Accessories 2) 0.00 500.00 500.00 500.00
Amount relevant for VAT 0.00 500.00 500.00 2000.00

purposes
VAT incl.
VAT (basis 100) 0.00 35.32 35.32 141.26
Sales incl. VAT 23,250.00 23,750.00 22,750.00 25,250.00
Net sales 23,250.00 23,714.68 22,714.68 25,108.74
The flat rate for delivery is added to the sales price as basis for determining the margin with respect to the original purchase price.
In accordance with VAT laws and regulations, accessories are regarded, as also goods and services, independently of the vehicle and therefore are not always
subject to VAT.
1.16 Archiving in DBM
Use
This function enables you to archive the following data:
· DBM order data
· DBM package data
Integration
Archiving of DBM data uses the standard archiving functions (transaction code SARA) and the following standard and DBM-specific archiving objects:
· /DBM/ORDER - archiving object for DBM order
· /DBM/PACK - archiving object for package
· VEHICLE – achiving object for vehicle
· PRODUCT_MD – achiving object for Iobject
· NM_QMEL – achiving object for notification
Archiving of DBM data uses and the following DBM archiving programs:
· Order
¡ /DBM/ORD_ARC_PRE: sets the deletion flag for DBM orders.
¡ /DBM/ORD_ARC_WRI: creates archiving objects in an archive.
¡ /DBM/ORD_ARC_DEL: physical deletion of the database entries for the archiving objects created by /DBM/ORD_ARC_WRI; /DBM/ORD_ARC_DEL
should always run after /DBM/ORD_ARC_WRI; this is ensured by transaction code SARA.
· Package:
¡ /DBM/PACK_ARC_PRE: sets the deletion flag for DBM packages.
¡ /DBM/PACK_ARC_WRI: creates archiving objects in an archive.
¡ /DBM/PACK_ARC_DEL: physical deletion of the database entries for the archiving objects created by /DBM/PACK_ARC_WRI;
/DBM/PACK_ARC_DEL should always run after /DBM/PACK_ARC_WRI; this is ensured by transaction code SARA.
· Vehicle
¡ RVLC_ARCHIVE_WRITE – Archive write program
¡ RVLC_ARCHIVE_DELETE – Archive delete program
· IObject
¡ COM_PRODUCT_SELECTIONS – Preprocessing program
¡ COM_PRODUCT_ARC_WRITE – Write program
¡ COM_PRODUCT_ARC_CHECKBACK – Delete program
¡ COM_PRODUCT_ARC_DELETE – Preprocessing program
· Notification
¡ RQARCNMV – Preprocessing program
¡ RQARCNMA – Write program
¡ RQARCNMD – Delete program
There are the following info structures for archiving in DBM:
· DBM/ORDER_01 - Info structure for archive object /DBM/ORDER
· /DBM/PACK_01 - Info structure for archive object /DBM/PACK
There are the following field catalogs for archiving in DBM:
· /DBM/ORDER_01 - Field catalog for archiving object /DBM/ORDER
· /DBM/PACK_01 - Field catalog for archiving object /DBM/PACK
· /DBM/VEHICLE_01 – Info structure for archive object VEHICLE
· SAP_PRODUCT_AIS – Info structure for archive object PRODUCT_MD
· SAP_NM_QMEL1 – Info structure for archive object NM_QMEL
In order to display the archive data, these information structures must be active. You can activate the information structures manually with the transaction SARI. If
you had archived some data before you activated the corresponding information structure, you must fill the structure with the transaction SARI. Choose
Enviroment ® Fill Structure .
There are the following field catalogs for archiving in DBM:
· /DBM/ORDER_01 – Field catalog for archiving object /DBM/ORDER
· /DBM/PACK_01 – Field catalog for archiving object /DBM/PACK
For more information on archiving in general, see Data Archiving (CA-ARC) , Introduction to Data Archiving (CA-ARC) and, for example,
Archiving Maintenance Notifications.
Prerequisites
· You have made the appropriate settings in Customizing for DBM under Dealer Business Management (DBM) ® Archiving.
· Prerequisites for the DBM order:
The preprocessing program has set the deletion flag (/DBM/VBAK_DB-LOEVM) when the DBM order has the status closed (for example, after billing) and
the residence time has been reached.
· Prerequisites for the DBM package:
The preprocessing program has set the deletion flag for the package with the status 'SHOULD_BE_ARCHIVED' if the package is not included in any open
order and any other non-archived package.
· Prerequisites for the Vehicle:
The action ‘Set archive Indicator’ can be processed if the curretn vehicle is not included in any DBM order in which the status is not equal with ‘CLOSED’.
· Prerequisites for the Notification:
Notification can be archived if it is not included in any DBM order which is not marked to be archived.
Features
· You can carry out archiving either manually or in a background job.
· The archiving report for DBM orders archives a DBM order only if it has the status Closed .
· The system deletes the data indexes from the TREX search after archiving.
· Customer and material data can be archived, provided that the data of the corresponding DBM order data has already been archived.
Activities
Archiving of DBM data takes place in the following stages:
1. Preprocessing: The system or archiving administrator, controller or auditor selects the data that needs to be archived. An Archive Development Kit (ADK)
preprocessing program carries out a check to determine which of these objects can be archived and sets the appropriate status (for example, can be
archived) for these objects.
2. Archiving: an ADK write program writes the data with this status to the archive file.
3. Deletion: an ADK deletion program system deletes the archived data from the database tables.
If you wish to read archived data, use the standard transaction code SARI or:
– For DBM Order, you can use transaction /DBM/ORDER03
– For Vehicle, you can use the vehicle search functionality
The system archives the following tables:
DBM Order:
· /DBM/VBAK_DB: Database Table - Order Header
· /DBM/VBAP: Main Sales Document: Item Data
· /DBM/SPLHDR_DB: Database Table for Split Header Data
· /DBM/SPLIT: Main Sales Document: Split Data
· /DBM/ JOB : Job Administration
· /DBM/VBEP: Main Sales Document: Schedule Line Data
· /DBM/VBPA: Order-Related Partner Functions
· /DBM/TASK: Task Administration
· /DBM/OE_VBAKST: Status Table for Order Header
· /DBM/OE_VBAPST: Status Table for Item
· /DBM/OE_VBEPST: Status Table for Schedule Line
· /DBM/OE_SPLITST: Status Table for Split Item
· /DBM/OE_SPLHDRST: Status Table for Splits
· /DBM/OE_JOBST: Status Table for Jobs
· /DBM/OE_TASKST: Status Table for Tasks
· /DBM/WTYD_ORDER: Warranty-Relevant Data in DBM Order
· NAST: Message Status
· KONV: Conditions (Transaction Data)
DBM Package:
· /DBM/PACK_H: Package Header Database T able
· /DBM/PACK_H_TXT
· /DBM/PACK_I: Package Item Database Table
· /DBM/ PACK _I_ TXT
· /DBM/PACK_V: Package Variant Database T able
· /DBM/ PACK _V_ TXT
· KONV: Conditions (Transaction Data)
1.16.1 Data Archiving
Use
You can archive DBM order and package data that you no longer need to access directly in the system by using archiving programs accessed via transaction
SARA. The system copies the data into archive files. If the procedure was successful, the system subsequently deletes the data.
Features
Archiving Programs and Objects

You can archive and delete this data using the following archiving programs:
● /DBM/ORD_ARC_PRE
Sets the deletion flag for DBM orders
● /DBM/ORD_ARC_WRI
Creates archiving objects in an archive
● /DBM/ORD_ARC_DEL
Physical deletion of the database entries for the archiving objects created by /DBM/ORD_ARC_WRI; /DBM/ORD_ARC_DEL should always be run after
/DBM/ORD_ARC_WRI; this is ensured by transaction SARA.
● /DBM/PACK_ARC_PRE
Sets the deletion flag for DBM packages
● /DBM/PACK_ARC_WRI
Creates archiving objects in an archive
● /DBM/PACK_ARC_DEL
Physical deletion of the database entries for the archiving objects created by /DBM/PACK_ARC_WRI; /DBM/PACK_ARC_DEL should always be run after
/DBM/PACK_ARC_WRI; this is ensured by transaction SARA.
And the following archiving objects:
● /DBM/ORDER for DBM orders
● /DBM/PACK for DBM packages
Initial Run (Preprocessing)

The initial run programs /DBM/ORD_ARC_PRE and /DBM/PACK_ARC_PRE prepare the data in the database for archiving. The deletion flags, with which you
flagged the objects you want to archive, are also assigned the system status MARC (Flagged for archiving) .
The initial run generates a log.
Archiving (Writing)
The archiving programs /DBM/ORD_ARC_WRI and /DBM/PACK_ARC_WRI write the database tables of the data to be archived to the archive.
The archiving program generates a log.
Deleting
The deletion programs /DBM/ORD_ARC_DEL and /DBM/PACK_ARC_DEL delete all database records for the DBM data that was successfully archived.
The system automatically calls the delete program after successful completion of the Archiving activity. You may have to wait briefly until archiving is complete.
You can process an entire archiving session with all the archive files created or you can select individual archive files for processing.
To avoid problems caused by data inconsistency, you should run the deletion program as near as possible to the archiving program.
The deletion program generates a log
Display
You can display statistical data for the archive file. To do this, choose Display Statistics in the Archive Administration: Initial Screen for archiving DBM data.
1.16.2 Pre-settings
The status Deletion flag must be set in the DBM data before archiving can be performed.
You have the following options for setting the deletion flag:
● You can manually flag the DBM data for deletion.
● You can flag DBM data for deletion using the report /DBM_ORD_ARC_PRE for orders or /DBM/PACK_ARC_PRE for packages.
If you execute the report in Test Mode , you can determine which DBM data has already been completed, and for which data the residence time has been
reached.
If you execute the report in Production Mode , the system sets the status DFLAG (Deletion Flag) for the data found.
1.16.3 Checks
Use
Before archiving, the system checks whether the DBM data is still being used. For this purpose, usage checksare performed on the data.
You can display a verification list of the DBM data that is still in use in the system and that is flagged for deletion using the initial run
(preprocessing). To do this, execute the initial run in Test Mode .
1.16.4 Customizing
Use
You have to make the following Customizing settings for archiving in DBM:
Cross-Archiving Object Customizing:
· Technical Settings
· Check and Delete
Archiving Object-Specific Customizing:
· Technical Settings
· Archive Routing
Basis Customizing:
· Cross-Client File Names/Paths
· Client-Specific File Names
Application-Specific Customizing:
· Archiving Control for DBM Order (Residence Time Check for DBM Order)
Customizing View for the Archiving Object

Using the transaction SARA, you can set the log file, the size of the archive file, the variants for the deletion program, and whether archiving is to be started
automatically or not.
1.16.5 Dependencies
When archiving DBM data, you must consider dependencies between archiving objects. Generally, you cannot archive data until dependent objects have been
archived.
As soon as DBM data can be archived, the status DLT (Deletion indicator, to be archived) can be set.
Prerequisites fort he DBM Order:

The preprocessing program sets the deletion flag (/DBM/VBAK_DB-LOEVM) when the DBM order has the status C losed (for example, after a billing document
has been created) and the residence time has been reached.
Prerequisites fort he DBM Package:

The preprocessing program sets the deletion flag when the package has the status SHOULD_BE_ARCHIVED and it is not included in any open order and any
other non-archived package.
1.16.6 Residence Time
Definition
The length of time that data must reside in the system, even if it is no longer being used (for example, for legal reasons). This data cannot be archived until it has
been in the system for at least this length of time.
In other words, the residence time determines the time interval (in calendar days) that must elapse between the time of closing the DBM order (the date when
order receives the status Closed) and the setting of the deletion indicator by the preprocessing program.
Use
You can control this residence time for DBM data by making the appropriate Customizing settings.
If the DBM data meets the requirements for archiving, the system can archive the data immediately.
Activities
You can make settings to define the residence time in Customizing for Dealer Business Management (DBM) under Archiving ® Archiving Control for DBM
Order.
1.16.7 Initial Run Log
Definition
A list in log form that the system creates when you perform the initial run program for archiving DBM data in a background job.
Structure
The initial run log contains the following information in detail:
· DBM data processed
¡ With the confirmation message, "Archiving Flag can be set"
¡ Exception messages
For example, if you executed the program in test mode, the where-used list for the DBM data can be listed.
· Statistics regarding DBM data processed
1.16.8 Archiving Log
Definition
A log in list form that the system creates when you run the archiving program as a background job.
Structure
The log contains the following data:
● Each processed service notification with exception messages if necessary
For example, if you executed the program in test mode, the where-used lists for the DBM data is listed.
● Statistics for archived objects
● Number of archive files generated
● All administrative data
● Associated tables
● Number of table entries processed
1.16.9 Deletion Log
Definition
A list that the system creates when the deletion program /DBM/ORD_ARC_DEL or DBM/PACK_ARC_DEL is executed automatically in a further step after the
initial run and the archiving log.
Structure
This log contains statistics for the objects processed for each archiving session.
Transaction Codes in Dealer Business Management
The DBM-specific transactions begin with /DBM/. Further transactions that are used in Dealer Business Management (DBM) come either from the standard
SAP system or from Vehicle Management System (VMS) (VELO*).
Master Data
Transaction Code Short Description
Customer
/DBM/VDXX Customer management
XD01, XD02, XD03 Create, change and display customer
IQS1 Create notification
IQS2 Change notification
IQS3 Display notification
IQS8 Worklist: notifications
IQS9 Worklist: tasks
Vehicle Model
/DBM/VMODEL Edit vehicle model master
/DBM/VFUEL_TYPE Edit fuel type
/DBM/VBODY Edit body types
/DBM/VCLASS Edit vehicle type
/DBM/VOPTYPE Edit features category
Part
/DBM/MM01 Create material – DBM
/DBM/MM02 Change material – DBM
/DBM/MM03 Display material – DBM
/DBM/MMXX Create material form the original parts master.
MM01, MM02, MM03 Create, change and display material
MM06 Flag for deletion
Labor Value
/DBM/LBROPGRP Edit labor value group
/DBM/LBROP Edit labor value
Package
/DBM/PACKAGE Edit package
Pricing Condition
VK11, VK12, VK13 Create, change and display condition
Account Assignment
/DBM/CO_INT_ORD Assign collective internal order
/DBM/CO_PCA Assign profit center
/DBM/CO_ACC Define account assignment object for internal order
Output Conditions and Control
/DBM/BOC01 Create condition tables
/DBM/BOC02 Change condition tables
/DBM/BOC03 Display condition tables
/DBM/BOC04 Define field catalog
/DBM/BOC05 Define access sequences
/DBM/BOC06 Define output types
/DBM/BOC07 Define pricing procedures
/DBM/BOC08 Create output: DBM order
/DBM/BOC09 Change output: DBM order
/DBM/BOC10 Display output: DBM order
VV31 Create output: billing document
VV32 Change output: billing document
VV33 Display output: billing document
Text
/DBM/ORDER_TEXT Edit text
/DBM/ORDER_TEXT_CAT Define text catalog
/DBM/ORDER_TEXT_COND Find text catalog
Warranty
/DBM/WTY1 Edit warranty master data
Warranty -> Defect Code
/DBM/DEFECTCODE_CREA Create
/DBM/DEFECTCODE_CHAN Change
/DBM/DEFECTCODE_DISP Display
Warranty -> Cause Code
/DBM/CAUSECODE_CREA Create
/DBM/CAUSECODE_CHAN Change
/DBM/CAUSECODE_DISP Display
Warranty -> Symptom Code
/DBM/SYMPTOMCODE_CRE Create
/DBM/SYMPTOMCODE_CHA Change
/DBM/SYMPTOMCODE_DIS Display
Workshop Scheduling
/DBM/SCH_DEPT Define workshop department
/DBM/SCH_OMAP Assign workshop department to organizational unit
/DBM/SCH_RMAP Assign resource to organizational unit
/DBM/SCH_EQUIM Define parameters for item creation
/DBM/SCH_DEF_PAR Define default parameters for scheduling
Vehicle Processing
/DBM/VSEARCH Vehicle search
/DBM/VM Vehicle master
VELORM Assign vehicle models to VMS roles
VELORU Assign users to VMS roles
/DBM/VM_GPA Gross profit analysis
Order Processing
/DBM/ORDER Order Processing
/DBM/ORDER01 Create order
/DBM/ORDER02 Change order
/DBM/ORDER03 Display order
/DBM/ORDER05 Copy order
/DBM/COOL_BILLING Collective billing
Warranty
WTY Process warranty claim
/DBM/S_WTY_LIST Warranty claims overview
/DBM/RS_WTY_CAUSP Status for parts to be returned
WTYRCL Edit recall
/DBM/WTYRCLITEM Assign item type and item category to OEM/Mapping: Recall item types for DBM item
categories
Workshop Scheduling
/DBM/SCH_DEPT Define workshop department
/DBM/SCH_OMAP Assign workshop department to organizational unit
/DBM/SCH_RMAP Assign resource to organizational unit
/DBM/SCH_VEHMA Define vehicle mapping for creation of scheduling item
/DBM/SCH_TSLOTS_COND Timeslot determination
/DBM/SCH_ETIME_C Estimated time catalog
/DBM/SCH_RES Minimum time slots for replacement vehicles
Cash Desk Processing
/DBM/CASHDESK Cash desk
/DBM/CASHDESK_RP Cash desk reposting
Marketing Activities
VC01N_M Edit actions/Create direct mailing
VC06 Change address list
VC10 Assign selection reports
SO10 Standard texts
VC15 Crossmatching
Storage Goods Manager
/DBM/STG_CREATE Create storage good
/DBM/STG_SEARCH Storage goods search
/DBM/SGM08 Create output: DBM order
/DBM/SGM09 Change output: DBM order
/DBM/SGM10 Display output: DBM order
Time Management
/DBM/TM_VT Create time stamp
/DBM/TM_AUTO_PUNCH Automatic clocking on and clocking off
/DBM/TM_ERRORS Error processing
Incentive and Commission Management
/DBM/ICM02 Select commissions from pending contracts

Dealer Business Management (IS-A-DBM)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dealer Business Management (IS-A-DBM)

Uploaded by

Copyright:

Available Formats

Dealer Business Management (IS-A-DBM)

PDF download from SAP Help Portal:

Created on November 02, 2014

1.1.1 Customer Data Management

1.1.1.2 Fact Sheet

1.1.1.3 Memo Pad

1.2.1 Vehicle Search

Action Control During Vehicle Processing

1.2.2.1 Determination of Action Control

1.2.2.2 Execution of Vehicle Actions

Action Primary Status Secondary Status

Create vehicle with internal order Vehicle created

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.2.3 Details for Vehicle Actions

The actions can be assigned to the following business processes:

1.2.2.3.1 Actions for Vehicle Procurement

Action Description Prerequisites Scope of Functions of Action Note

Action Description Prerequisites Scope of Functions of Action Note

QCRV Create Vehicle This interlinking action creates a

QNTF Create Notification Vehicle Creates a notification for vehicle

QRPU Repurchase Used Vehicle For cases in which the vehicle

QTIP Prepare Repurchase See: Action QTIP: Prepare

QORD Create Purchase Order (DBM)

For more information, see Used-Vehicle Purchasing.

Actions for Vehicle Sales and Service

Action Description Prerequisites Scope of Functions of Action Note

QDOF Delete Quotation (DBM) Quotation Is called if a vehicle quotation is

QCSQ Create Service Quotation (DBM) Is called when a DBM service

QDSO Delete Service Order (DBM) Is called if a service order is

Action Description Prerequisites Scope of Functions of Action Note

QGRH CO Prod.Post Goods Receipt The counterpart to this action is

QSEH CO Prod. Create Settlement The counterpart to this action is

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

QCOS Check Soldo of Internal Order

QLIO Complete Internal Order

QSVC CO Prod. Stock Value Change The counterpart to this action is

QSVH CO Prod. Stock Value Change The counterpart to this action is

1.2.2.3.3 Actions for Goods Movements

Action Description Prerequisites Scope of Functions of Action Note

Action Description Prerequisites Scope of Functions of Action Note

Action Description Prerequisites Scope of Functions of Action Note

Action Description Prerequisites Scope of Functions of Action Note

QPGM Cross-Plant Goods Movement See: action QVTP

Action Description Prerequisites Scope of Functions of Action Note

1.2.2.3.4 Other Vehicle Actions

Action Description Prerequisite Scope of Functions of Action Note

Interlinked VMS Actions in DBM Vehicle Master

Vehicle Transfer Posting

Transfer Posting of Vehicle From Current Assets to Fixed Assets

Old Status Action New Status

Initial QCAS QT05

QT20 QVTD QT10

QT05 QVTA QT10

QT10 QVTA QT10

QT10 QATV QT20

QT20 QACU QS20

You can use BAdI /DBM/QCAS_EXECUTE to influence asset data.

Transfer Posting of Vehicle Between Plants

Transfer Posting of Vehicle Between Company Codes