DBM 6.

0
August 2007
English

AG0: Vehicle Service and

Recalls
Building Block Configuration Guide

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Copyright

© Copyright 2007 SAP AG. 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 AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components
of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z,
System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5,
POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP
products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other product and
service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG 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 AG Page 2 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Icons

Icon Meaning
Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, Transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.

Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

© SAP AG Page 3 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Contents

1 Purpose................................................................................................................................... 5
2 Preparation.............................................................................................................................. 5
2.1 Prerequisites.................................................................................................................. 5
2.1.1 Building Blocks.......................................................................................................... 5
3 Configuration........................................................................................................................... 7
3.1 Sales and Distribution.................................................................................................... 7
3.1.1 Creating Customer Master Data................................................................................7
3.1.2 Changing Customer Credit Data...............................................................................7
3.2 Logistics......................................................................................................................... 8
3.2.1 Creating Material Master Data as Parts....................................................................8
3.2.2 Maintaining Sales Price for Spare Parts..................................................................10
3.2.3 Maintaining Supersession Chain.............................................................................10
3.2.4 Posting Goods Receipt for Initial Stocks..................................................................11
3.3 Catalog Numbers......................................................................................................... 11
3.3.1 Defining Defect Codes............................................................................................11
3.3.2 Defining Cause Codes............................................................................................12
3.3.3 Defining Symptom Codes........................................................................................13
3.4 DBM Package.............................................................................................................. 13
3.4.1 Manual Activity: Maintaining Number Ranges for Packages...................................13
3.4.2 Manual Activity: Maintaining Package.....................................................................14
3.5 HR Master Data........................................................................................................... 15
3.5.1 Creating Customer Adviser.....................................................................................15

© SAP AG Page 4 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Vehicle Service and Recalls: Configuration Guide

1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.
If you do not want to configure manually and prefer an automated installation process using BC
Sets and other tools, refer to the installation guide of this building block.

2 Preparation
2.1 Prerequisites
2.1.1 Building Blocks
Before you start installing this building block, the installation of the following building blocks must
have been completed:
Baseline Layer 0

Building Block Description

B32 Sap Best Practices Installation DE

J02 Organizational Structure (DE)

N69 External Financial Accounting Basics

N70 External Financial Accounting

N71 Central Cost Center Accounting

J05 Materials Management

J04 Sales and Distribution

Baseline Layer 1

Building Block Description

J18 Product Cost Planning

J17 Profitability Analysis

N72 Asset Management

Before you install DBM Building blocks, you need read and install the entire necessary
supplements as per DBM Quick Guide.
DBM Building Block

Building Block Description

AZ1 DBM Basic Settings

AZ2 Warranty and Recall Settings

© SAP AG Page 5 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

© SAP AG Page 6 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

3 Configuration
3.1 Sales and Distribution
3.1.1 Creating Customer Master Data
Use
The purpose of this activity is to create customer master data used by this scenario.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Sales and Distribution  Master Data  Business
Partner  Customer  Create  Complete
Transaction code XD01
2. On the Customer Create: Initial Screen, make the following entries:
Field name Description User action and values Note
Account Group KUNA
Customer G000
Company code BP01
Sales Organization BP01
Distribution channel 01
Division 01
3. Choose Save.

Refer to the following file for details of the master data required:
SMB64_SD_CUSTOMER_O001_AG0.TXT

3.1.2 Changing Customer Credit Data

Use
The purpose of this activity is to change customer credit data so that customer credit limit is
checked during order process.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Accounting  Financial Accounting  Customers  Credit
Management  Master data  Change
Transaction code FD32

© SAP AG Page 7 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

2. Change customer G000 in credit control area BP01

3. In the Central Data view, make the following entry:
Total amount Individual limit Currency
10000 10000 EUR
4. In the Status view, make the following entry:
Credit Limit
20

3.2 Logistics
3.2.1 Creating Material Master Data as Parts
Use
The DBM material is based on the standard system. Dealer Business Management (DBM) has
the following differences and enhancements to the standard system:
● Additional DBM data (generic data)
○ Part to be returned
(returned to manufacturer for further technical development)
○ Part that has to be kept (legal requirement)
○ Part that has to be disposed of (legal requirement)
○ Check multiple entry
● Simplified user interface
○ Default views
○ Aggregated display

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Logistics Execution  Dealer Business Management
 Master Data  Part  Create Material
Transaction code MM01
2. Create following materials AG0-1000, AG0-1001, AG0-1002, AG0-2000, AG0-3000, AG0-
4000 A90-5000 and AG0-6000.

The following information for DBM material data, in other words, part data, is
important:
Field Data Description
Material Type HAWA Trading goods
Properties copied from
HAWA
Industry Sector M
Material Group Customer and brand-specific
settings possible
General Item Category Group NORM Normal SAP

© SAP AG Page 8 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

standard item
Checking Group for Customer-specific setting
Availability Check
Procurement type F External:
supplied by manufacturer
Materials planning (MRP) Customer-specific settings for
manufacturer parts (MRP is
manufacturer-specific)
For inventory-managed
materials from other vendors,
such as tires (for example,
summer and winter tires) and
accessories, you can use
SAP MRP and materials
planning functions
Tax classification Customer-specific setting
(see SAP Note 109005 for
tax levied on used parts)
Transportation group 0001 Delivery functions are not
Loading group currently integrated into the
DBM order,
Since transport and loading
groups are required fields in
the material type HAWA, you
either have to define them
with default values or set the
field control for these fields in
Customizing appropriately.

Refer to the following 2 files for details of the master data required:
SMB64_MM01_ALL_VIEWS_O001_AG0.TXT and
SMB64_MATERIAL_MASTER_DBM_DM1_AZ1.TXT

3.2.2 Maintaining Sales Price for Spare Parts

Use
The purpose of this activity is to maintain the sales price for spare parts.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Logistics Execution  Dealer Business Management
 Master Data  Pricing Condition  Create Condition.
Transaction code VK11

© SAP AG Page 9 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

2. Enter QPRT in the field Condition Type and choose combination Material.
3. Enter Sales organization BP01 and distribution channel 01 and maintain the following
entries:
Material Amount
AG0-1000 15
AG0-1001 15.5
AG0-1002 16
AG0-2000 30
AG0-3000 0.7
AG0-4000 20
AG0-5000 15
AG0-6000 250
4. Choose Save.

3.2.3 Maintaining Supersession Chain

Use
The purpose of this activity is to maintain the spare parts substitution relationship as
supersession chain.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Materials Management  Purchasing  Master Data
 Interchangeability of Parts Maintain
Transaction code PIC01
2. Enter Material AG0-1000 and choose Supersession

3. Make the following entries:

Material Validity Date Replacement
AG0-1001 01.02.2007 I
AG0-1002 01.09.2007 I
4. Choose Save.

3.2.4 Posting Goods Receipt for Initial Stocks

Use
You need post initial stocks for spare parts before you can post goods issue.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Materials Management  Inventory Management 

© SAP AG Page 10 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Goods Movement  Goods Receipt  Other

Transaction code MB1C
2. Post initial stock with movement type 561 for material AG0-1000, AG0-1001, AG0-1002,
AG0-2000, AG0-4000, AG0-5000 and AG0-6000 with quantity 100 and material AG0-3000
with quantity 1000.

3.3 Catalog Numbers

3.3.1 Defining Defect Codes
Use
The purpose of this activity is to define defect codes.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Logistics Execution  Dealer Business Management 
Master Data  Warranty  Defect Code  Create
Transaction code /DBM/DEFECTCODE_CREA

2. On the Create Number In Catalog: Initial Screen, make the following entries:
Field name User action and values
Catalog WTY1
No. in catalog 1-00001

3. Choose Enter.
4. On the Create Number In Catalog: Detail Screen, make the following entries
Field name User action and values
Language EN
Catalog Text Navigation System Defect
5. Choose Save.

Result
The catalog number for WTY1 was defined.

3.3.2 Defining Cause Codes

Use
The purpose of this activity is to define cause codes.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Logistics Execution  Dealer Business Management 

© SAP AG Page 11 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Master Data  Warranty  Cause Code  Create

Transaction code /DBM/CAUSECODE_CREA

2. On the Create Number In Catalog: Initial Screen, make the following entries:
Field name User action and values
Catalog DBM2
No. in catalog 0000000001-01-01

3. Choose Enter.
4. On the Create Number In Catalog: Detail Screen, make the following entries:
Field name User action and values
Language EN
Catalog Text EPROM Module Error
5. Choose Save.

Result
The catalog number for DBM2 was defined.

3.3.3 Defining Symptom Codes

Use
The purpose of this activity is to define symptom codes.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Logistics Execution  Dealer Business Management 
Master Data  Warranty  Symptom Code  Create
Transaction code /DBM/SYMPTOMCODE_CRE

2. On the Create Number In Catalog: Initial Screen, make the following entries:
Field name User action and values
Catalog DBM1
No. in catalog 0000000001-01-01

3. Choose Enter.
4. On the Create Number In Catalog: Detail Screen, make the following entries:
Field name User action and values
Language EN
Catalog Text Navigation System Crash
5. Choose Save.

© SAP AG Page 12 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Result
The catalog number for DBM1 was defined.

3.4 DBM Package

3.4.1 Manual Activity: Maintaining Number Ranges for

Packages
Use
In this activity, you define the number ranges for packages.

Procedure
1. Access the activity using the following navigation option:
Transaction code /DBM/PACKAGE_NUMBER
2. On the DBM Package screen, choose from menu Group  Maintain.
3. On the Maintain Number Range Groups screen , choose from menu Group  Insert
4. On the Insert Group dialog box, make the following entries:
Text From number To number EXT
0000000000010000000 0000000000019999
DBM Package
0 9999
AAAAAAAAAAAAAAAA ZZZZZZZZZZZZZZZ
X
AAAA ZZZZZ
5. Choose Add.

6. On the Maintain Number Range Groups, choose Save.

7. Confirm with Enter the appearing information transport number range intervals.
8. Choose the package type 01 Price Package, 02 Chain package and 03 Parts Package add
them to the group DBM Package. To do this double click the 3 package types, select DBM
Package and choose Element/Group.
9. Choose Save.

3.4.2 Manual Activity: Maintaining Package

Use
A service package can consist of different items, for example, n labor values, n parts, and n texts.
The manufacturer usually supplies this information in the form of a catalog (local OEM system).
However, dealer can also create their own packages.
The package master is a DBM object.

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Logistics  Logistics Execution  Dealer Business Management
(DBM)  Master Data  Package  Edit Package
Transaction code /DBM/PACKAGE

© SAP AG Page 13 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

2. On the Change Package screen, choose Create New Package.

3. On the Create Package dialog box, make the following entries, and choose Continue.
Package Type Package ID External Key
02 Chain SR-001 EXT_SR-001
4. On the Display Package SR-001 (Changed) screen, make the following entries:
Package LV Description Plant Sales Distr. Division OEM Package
Status Main Org Channel Changeable
Type
02 01 20 TKM BP01 BP01 C3 SR SR_AUTO Select
Package
5. Choose Save, and confirm the information dialog box.
6. On the Item Detail sub-screen, choose Item Category P002 Part, and make the following
entries, then choose Enter.
Item Cat. Material Order Quantity
P002 Part AG0-1000 1
7. On the Item list sub-screen, choose Create and then repeat step 6 to assign the following
materials to the package.
Material Order Quantity
AG0-3000 10
AG0-4000 0,1
8. On the Item Detail sub-screen, choose Create New Item and choose the Item Category P001
labor value, make the following entries and then choose Enter.
Item Cat. LV Catalog ID Labor Value No.
P001 labor Value SR_LV 0000101
9. Repeat step 8 to enter the following Labor value keys:
Labor Value No.
0100202
0200301
10. Choose Save and ignore the information message
11. Choose Back.

Package SR-001 has been maintained.

3.5 HR Master Data

3.5.1 Creating Customer Adviser
Use
You create customer adviser as HR personnel master.

© SAP AG Page 14 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Procedure
1. Access the activity using one of the following navigation options:
SAP menu Human Resources  Personnel Management  Administration
 HR Master Data  Personnel Actions
Transaction code PA30
2. On the Personnel Actions screen, make the following entries:
Field name Description User action and values Comment
Personnel 1
No.
From The first day of current
month
3. Choose Action Type Hiring line, make the following entries :
Field name Description User action and values Comment
Personnel BP01
area
EE Group 1
EE Subgroup DU
4. On the Create Actions screen, choose Save.
5. On the Prompt for Customizing request screen, enter an existing customizing request or
create a new one.
6. After you assign the customizing request, on the Prompt for Customizing request screen,
choose Continue.
7. On the Create Personal Data screen, make the following entries:
Field name Description User action and values Comment
Title Ms.
Last name Bergmann
First name Lisa
Birthdate 01.01.1970
Nationality German
8. Choose Enter twice to ignore the error message PN001 – No entry in table T5D0P for key
BP01 and 0001.
9. Choose Save. Create or assign customizing change request to save the data.
10. On the Create Organizational Assignment screen, choose Assignment

11. On the Create Organizational Assignment dialog box, check No assignment and choose

Continue.
12. There is message Please enter a valid combination of personnel area and
subarea at the bottom of screen. To avoid the message, on the Create Organizational
Assignment screen, make the following entries:
Field name Description User action and values Comment

© SAP AG Page 15 of 16
SAP Best Practices AG0 - Vehicle Service and Recalls: Configuration Guide

Subarea 0001
13. Choose Save.
14. On the Create Addresses screen, make the following entry:
Field name Description User action and values Comment
City Frankfurt
15. Choose Save.
16. Choose to skip the screen for Create Planned Working Time

17. Choose to skip the screen for Create Basic Pay

18. Choose to skip the screen for Create Bank Details

19. Choose on the Error message dialog box from the Create Absence Quotas screen.

20. Choose to skip the screen for Create Absence Quotas

21. On the Exit current screen dialog box, choose yes.

© SAP AG Page 16 of 16