You are on page 1of 29

Upgrade Master Guide

SAP Dealer Business


Management
Using SAP DBM 8.0
Target Audience
Consultants
Administrators
Others

PUBLIC
Document version: 1.0 – 2013-11-
29
Document History

CAUTION
Before you start the implementation, make sure you have the latest version of this
document. You can find the latest version at the following location:
http://service.sap.com/ instguides.

The following table provides an overview of the most important document changes.
VersionDate Description
1.02013-11-29 Initial Version

2/ PUBL 2013-11-
Table of Contents

Chapter 1 Getting Started.......................................................................................5


1.1 About this Document.........................................................................5
1.2 Related Information..................................................................................6
1.2.1 Planning Information................................................................................6
1.2.2 Further Useful Links.................................................................................7
1.3 Important SAP Notes................................................................................7

Chapter 2 Upgrade Overview..................................................................................9


2.1 Upgrade at a Glance......................................................................................9
2.2 Upgrade Paths...............................................................................................9
2.3 Upgrade of Involved Software Components............................................9
2.4 Minimal System Landscape.....................................................................9
2.5 Overall Upgrade Sequence....................................................................10

Chapter 3 Business Scenarios of SAtf Dealer Business Management..................13


3.1 Vehicle Sales and Administration...........................................................13
3.2 Vehicle Service.............................................................................................14
3.3 Parts Management.......................................................................................16

Chapter 4 References..................................................................................................19
4.1 List of Documents...................................................................................19
4.2 List of SAP Notes.........................................................................................19

Chapter A Reference..............................................................................................21
A.1 The Main SAP Documentation Types..........................................................21

2013-11- PUBL 3/
This page is left blank for
that are printed on both sides.
1 Getting
1.1 About this Document

1 Getting Started

1.1 About this Document


Purpose

This Upgrade Master Guide provides a central starting point for the technical upgrade of SAP
Dealer Business Management. You can find cross-scenario upgrade information as well as
scenario-specific information in this guide.

NOTE
The central starting point for the technical implementation of your SAP
application/solution is the Master Guide, which you can find on SAP Service Marketplace
at http://service.sap.com/ instguides.

Use the Upgrade Master Guide to get an overview of the upgrade paths, the upgrade of the
involved software units and scenarios from a technical perspective. The Upgrade Master Guide is a
planning tool that helps you to decide what software units you have to upgrade taking into account
the dependencies between the software units. It refers you to the required detailed
documentation, mainly:
■ Upgrade guides for single software units
■ SAP Notes
■ Configuration documentation
■ SAP Library documentation
For a general overview of available SAP documentation, see section The Main SAP Documentation
Types.

NOTE
You can find the most current information about the technical upgrade of SAP Dealer
Business Management and the latest upgrade, installation and configuration guides on
SAP Service Marketplace at http://service.sap.com/instguides.
We strongly recommend that you use the documents available here. The guides are
regularly updated.

Constraints

■ The business scenarios that are presented here serve as examples of how you can use SAP
software in your company. The business scenarios are only intended as models and do not
necessarily run the way they are described here in your customer-specific system landscape.
Ensure to check your requirements and systems to determine whether these scenarios can be

2013-11- PUBL 5/
1 Getting
used productively at your

6/ PUBL 2013-11-
1 Getting
1.2 Related Information

site. Furthermore, we recommend that you test these scenarios thoroughly in your test
systems to ensure they are complete and free of errors before going live.
■ This Upgrade Master Guide primarily discusses the overall technical upgrade of SAP Dealer
Business Management, rather than its subordinate components. This means, that
additional software
dependencies may exist without being mentioned explicitly in this document. You can find
more information about component-specific software dependencies in the corresponding
upgrade guides.

1.2 Related Information


1.2.1 Planning Information
For more information about planning topics not covered in this guide, see the following
content on SAP Service Marketplace.
Content Location on SAP Service Marketplace
Latest versions of installation and http://service.sap.com/instguides
upgrade guides
SAP Upgrade Info Center - http://service.sap.com/upgrade
general information about
upgrade topics and application-
specific upgrade information
General information about SAP http://help.sap.com/saphelp_dbm800/helpdata/en
Dealer Business Management
SAP Business Maps - http://service.sap.com/businessmaps
information about applications
and business scenarios
Sizing, calculation of hardware http://service.sap.com/sizing
requirements - such as CPU, SAP Note 1244700
disk and memory resource
Released platforms and http://service.sap.com/platforms
technology-related topics such as To access the Platform Availability Matrix directly, enter
maintenance strategies and http:// service.sap.com/pam.
language support
Network security http://service.sap.com/securityguide

High Availability http://www.sdn.sap.com/irj/sdn/ha

Performance http://service.sap.com/performance

Information about Support http://service.sap.com/sp-stacks


Package Stacks, latest software
versions and patch level
requirements
Information about Unicode http://www.sdn.sap.com/irj/sdn/i18n
technology

2013-11- PUBL 7/
1 Getting
1.3 Important SAP Notes

1.2.2 Further Useful Links


The following table lists further useful links on SAP Service Marketplace:
Content Location on SAP Service Marketplace
Information about creating error messages http://service.sap.com/messages

SAP Notes search http://service.sap.com/notes

SAP Software Distribution Center (software download and ordering of http://service.sap.com/swdc


software)
SAP Online Knowledge Products (OKPs) – role-specific Learning http://service.sap.com/rkt
Maps

1.3 Important SAP Notes


You must read the following SAP Notes before you start the upgrade. These SAP Notes
contain the most recent information about the upgrade, as well as corrections to the upgrade
documentation. Make sure that you have the up-to-date version of each SAP Note, which you
can find on SAP Service Marketplace at http://service.sap.com/notes.
SAP Note Number Title Description
1876924 Installation and Upgrade Note for Dealer Business General information about technical upgrade
Management 8.0

6/ PUBL 2013-11-
2
2
that
Upgrade
are printed on both sides.
Overview

2013-11- PUBL 9/
2 Upgrade
Overview
2

2 Upgrade Overview

2.1 Upgrade at a Glance


With the upgrade to DBM 800, new business processes are added to the business scenarios
Vehicle Sales and Administration, Vehicle Service, and Parts Management. The new processes are
listed below.
■ Vehicle Sales and Administration
● Processing Additional Vehicle Costs
■ Vehicle Service
● Processing for Additional Work and Deferred Work
● Creating Service Contracts
● Creating Advanced Payment
● Processing Payments
● Monitoring Credit Limits
● Processing Service Credit Memo
■ Parts Management
● Creating Advanced Payment

2.2 Upgrade Paths


There are direct upgrade paths from DBM 600 and DBM 700 to DBM 800 without intermediate
upgrade steps. There is no upgrade path from DBM 500 to DBM 800 available.

2.3 Upgrade of Involved Software Components


SAP Note Number Title Description
1876924 Installation and Upgrade Note for Dealer Business General information about technical upgrade
Management 8.0

2.4 Minimal System Landscape


The following figure shows an overview of the minimal technical system landscape for SAP
Dealer Business Management 800.

2013-11- PUBL 9/
2 Upgrade
2.5 Overall Upgrade Sequence

Figure 1: Minimal System Landscape

NOTE
Automotive Solutions use PP, LE, MM, SD and ECC DIMP which includes Dealer Portal, Vehicle
Management System (VMS), and so on.

At a minimum, you need to install SAP ECC with the SAP ECC DIMP 604, SAP DBM add-
ons, and TREX.

CAUTION
We strongly recommend that you use a minimal system landscape for test and demo
purposes only. For performance, scalability, high availability, and security reasons, do
not use a minimal system landscape as your production landscape.

2.5 Overall Upgrade Sequence


The following tables describe the overall upgrade sequence for SAP Dealer Business Management
for upgrades from DBM 600 or DBM 700 to DBM 800. These tables contain all available
software units.
However, to run a specific scenario, you only need a subset of available software units. Some are only
required for special processes. For information about which software is required to run a specific
scenario, see the specific business scenarios in this document.

Upgrade Sequence DBM 600 to DBM 800


Step Action Remarks/Subsequent Steps
1 Object control framework XPRA report /DBM/XPRA_GLOBAL_EVENTS runs automatically
events during upgrade and migrates old DBM order events to the new
global event customizing table.

10/ PUBL 2013-11-


2 Upgrade Overview
2 Overall Upgrade

Step Action Remarks/Subsequent Steps


2 DBM order: ATP status XPRA report /DBM/XPRA_ATP_STATUS runs automatically during
upgrade and calculates the ATP status based on the quantities and
updates the DBM order status.
3 Business partner Check the business partner configuration guide in SAP Solution
Manager for details about the setup of master data
synchronization (transaction MDS_LOAD_COCKPIT) and
upgrade of old DBM orders with business partner data.
4 Vehicle Sales (optional step) If you want to use the new owner functionality within the
vehicle, run report /DBM/UPDATE_VEHICLE_OWNER to update
vehicles with this new partner role.
5 Vehicle Sales (optional step) Execute report /DBM/R_UPD_VEH_OPTIONS to enable
selected vehicles for the new vehicle search via generic
options.
6 Order status (no action Order status: New delivered statuses are getting initialized
required) during accessing the order in change mode.
7 Pricing date on item level Pricing date on split item level is a new field in DBM 800
(no action required (/DBM/SPLIT- PRSDT). It is copied from the pricing date on
appropriate split header (/DBM/SPLHDR_DB-PRSDT) when
accessing the order in change mode.
8 Job fields: Job catalog and Job Id Fields Job Catalog (/DBM/JOB-CATID) and Job ID (/DBM/JOB-LABVAL)
(no action required) are filled from the tasks assigned to the job when accessing the
order in change mode.
9 Appointment scheduling dates The dates for vehicle pick-up (/DBM/VBAK_COM-
(no action required) VISIT_END_DATE and /DBM/VBAK_COM-VISIT_END_TIME) are
set to the same values as the dates for repair end
(/DBM/VBAK_COM- BASE_END_DATE and /DBM/VBAK_COM-
BASE_END_TIME).

Upgrade Sequence DBM 700 to DBM 800


Step Action Remarks/Subsequent Steps
1 Order status (no Order Status: New delivered statuses are getting initialized
action required) during accessing the order in change mode.
2 Pricing date on item level Pricing date on split item level is a new field in DBM 800
(no action required) (/DBM/SPLIT- PRSDT). It is copied from the pricing date on
appropriate split header (/ DBM/SPLHDR_DB-PRSDT) when
accessing the order in change mode.
3 Job fields: Job catalog and Job Fields Job Catalog (/DBM/JOB-CATID) and Job ID (/DBM/JOB-
Id (no action required) LABVAL) are filled from the tasks assigned to the job when accessing
the order in change mode.
4 Appointment scheduling dates The dates for vehicle pick-up (/DBM/VBAK_COM-VISIT_END_DATE
(no action required) and /DBM/VBAK_COM-VISIT_END_TIME) are set to the same
values as the dates for repair end (/DBM/VBAK_COM-
BASE_END_DATE and / DBM/VBAK_COM-BASE_END_TIME)

2013-11- PUBL 11/


This page is left blank for
that are printed on both sides.
3 Business Scenarios of SAP Dealer Business
3.1 Vehicle Sales and Administration

3 Business Scenarios of SAP Dealer


Business Management

3.1 Vehicle Sales and Administration


Overview

Vehicle sales and administration covers all business processes for managing the sales process for
new and used vehicles. These business processes include:
■ Processing Customers
■ Processing Activities
■ Purchasing New Vehicles
■ Purchasing Used Vehicles
■ Creating Vehicle Quotations without Vehicle Selling
■ Selling New Vehicles
■ Selling Used Vehicles
■ Splitting Orders
■ Creating Down Payments
■ Processing Vehicle Handover
■ Billing
■ Processing Complaints
■ Processing Vehicle Additional Costs
■ Processing Returns
■ Integration of VMS and DBM

Technical System Landscape

The following figure provides an overview of a possible system landscape for SAP DBM Vehicle
Sales and Administration:

2013-11- PUBL 13/


3 Business Scenarios of SAP Dealer Business
Management
3

Figure 2: Technical System Landscape

Software Units

The following software components are either mandatory or optional, as indicated below,
for the technical implementation of this business scenario:
Component Mandatory Optional
SAP DBM 8.0 x
SAP EHP 6 for SAP ERP 6.0 SPS 6 – SAP ECC Server with business function set x
Discrete Industries and Mill Products (DIMP_SDUD)
SAP NetWeaver 7.3 EHP 1 SPS 6 x
SAP NetWeaver 7.3 EHP 1 SPS 6 – TREX x
SAP NetWeaver 7.3 EHP 1 SPS 6 – BI x
SAP NetWeaver 7.3 EHP 1 SPS 6 – EP x

Upgrade Sequence

See section Overall Upgrade Sequence

Further Information

The following documents provide more information:


Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
Security Guide For more information, see SAP Service Marketplace at http://
service.sap.com/securityguide.

3.2 Vehicle Service


Overview

The vehicle service scenario covers all business process processes for managing repairs and
inspections for vehicles in your workshop. These business processes include:

14/ PUBL 2013-11-


3 Business Scenarios of SAP Dealer Business
3.2 Vehicle Service

■ Processing Customers
■ Creating Service Contracts
■ Creating Service Order Quotations
■ Processing Service Orders
■ Processing Internal Service Orders
■ Processing Suborders
■ Confirming Services
■ Splitting Orders
■ Creating Down Payments
■ Creating Advance Payments
■ Billing
■ Processing Payments
■ Monitoring Credit Limits
■ Processing Service Credit Memo
■ Processing Returns
■ Processing Activities
■ Processing Complaints

Technical System Landscape

The following figure provides an overview of a possible system landscape for SAP DBM Vehicle
Service:

Figure 3: Technical System Landscape

Software Units

The following software components are either mandatory or optional, as indicated below,
for the technical implementation of this business scenario:
Component Mandatory Optional
SAP DBM 8.0 x

2013-11- PUBL 15/


3 Business Scenarios of SAP Dealer Business
Management
3

Component Mandatory Optional


SAP EHP 6 for SAP ERP 6.0 SPS 6 – SAP ECC Server with business function set x
Discrete Industries and Mill Products (DIMP_SDUD)
SAP NetWeaver 7.3 EHP 1 SPS 6 x
SAP NetWeaver 7.3 EHP 1 SPS 6 – TREX x
SAP NetWeaver 7.3 EHP 1 SPS 6 – BI x
SAP NetWeaver 7.3 EHP 1 SPS 6 – EP x

Upgrade Sequence

See section Overall Upgrade Sequence

Further Information

The following documents provide more information:


Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
Security Guide For more information, see SAP Service Marketplace at http://
service.sap.com/securityguide.

3.3 Parts Management


Overview

The Parts Management scenario covers all business process processes for managing parts. These business
processes include:
■ Processing Customers
■ Processing Parts Orders
■ Purchasing Parts
■ Processing Backorders
■ Creating Down Payments
■ Creating Advance Payments
■ Billing
■ Processing Payments
■ Processing Returns

Technical System Landscape

The following figure provides an overview of a possible system landscape for SAP DBM Parts
Management:

16/ PUBL 2013-11-


3 Business Scenarios of SAP Dealer Business
Management
3

Figure 4: Technical System Landscape

Software Units

The following software components are either mandatory or optional, as indicated below,
for the technical implementation of this business scenario:
Component Mandatory Optional
SAP DBM 8.0 x
SAP EHP 6 for SAP ERP 6.0 SPS 6 – SAP ECC Server with business function set x
Discrete Industries and Mill Products (DIMP_SDUD)
SAP NetWeaver 7.3 EHP 1 SPS 6 x
SAP NetWeaver 7.3 EHP 1 SPS 6 – TREX x
SAP NetWeaver 7.3 EHP 1 SPS 6 – BI x
SAP NetWeaver 7.3 EHP 1 SPS 6 – EP x

Upgrade Sequence

See section Overall Upgrade Sequence

Further Information

The following documents provide more information:


Content Location
Scenario Description See the documentation in SAP Solution Manager.
Configuration Documentation See the documentation in SAP Solution Manager.
Security Guide For more information, see SAP Service Marketplace at http://
service.sap.com/securityguide.

2013-11- PUBL 17/


This page is left blank for
documents
4 References
4 List of

4 References

4.1 List of Documents


The following table lists documents mentioned in this Upgrade Master Guide.
Content Location
DBM Configuration Guide with business SAP Solution Manager
partner configuration section
(Configuration Documentation)
DBM Scenario Description SAP Solution Manager
DBM Security Guide SAP Service Marketplace at http://service.sap.com/
securityguide

4.2 List of SAP Notes


The following table lists all SAP Notes mentioned in this Upgrade Master Guide.
SAP Note Number Title Description
1876924 Installation and Upgrade Note for Dealer Business General information about technical upgrade
Management 8.0

2013-11- PUBL 19/


This page is left blank for
documents
A Referen
A.1 The Main SAP Documentation Types

A Reference

A.1 The Main SAP Documentation Types


The following is an overview of the most important documentation types that you need in the
various phases in the life cycle of SAP software.

Cross-Phase Documentation

SAtfterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30


languages, as well as many glossary entries in English and German.
■ Target group:
● Relevant for all target groups
■ Current version:
● On SAP Help Portal at http://help.sap.com Glossary
● In the SAP system in transaction STERM
SAtf Library is a collection of documentation for SAP software covering functions and
processes.
■ Target group:
● Consultants
● System administrators
● Project teams for implementations or upgrades
■ Current version:
● On SAP Help Portal at http://help.sap.com (also available as documentation DVD)
The security guide describes the settings for a medium security level and offers suggestions for
raising security levels. A collective security guide is available for SAP NetWeaver. This
document contains general guidelines and suggestions. SAP applications have a security
guide of their own.
■ Target group:
● System administrators
● Technology consultants
● Solution consultants
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required
installable units for each business or IT scenario. It provides scenario-specific descriptions of
preparation,
2013-11- PUBL 21/
A Referen
A.1 The Main SAP Documentation Types

execution, and follow-up of an implementation. It also provides references to other documents,


such as installation guides, the technical infrastructure guide and SAP Notes.
■ Target group:
● Technology consultants
● Project teams for implementations
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/instguides
The installation guide describes the technical implementation of an installable unit, taking
into account the combinations of operating systems and databases. It does not describe any
business-related configuration.
■ Target group:
● Technology consultants
● Project teams for implementations
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/instguides
Configuration Documentation in SAtf Solution Manager – SAP Solution Manager is a life-
cycle platform. One of its main functions is the configuration of business scenarios, business
processes, and implementable steps. It contains Customizing activities, transactions, and
so on, as well as documentation.
■ Target group:
● Technology consultants
● Solution consultants
● Project teams for implementations
■ Current version:
● In SAP Solution Manager
The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP
system. The Customizing activities and their documentation are structured from a functional
perspective. (In order to configure a whole system landscape from a process-oriented perspective,
SAP Solution Manager, which refers to the relevant Customizing activities in the individual
SAP systems, is used.)
■ Target group:
● Solution consultants
● Project teams for implementations or upgrades
■ Current version:
● In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on
SAP NetWeaver, and precedes the application operations guides of SAP Business Suite. The
manual refers

22/ PUBL 2013-11-


A Referen
A.1 The Main SAP Documentation Types

users to the tools and documentation that are needed to carry out various tasks, such as
monitoring, backup/restore, master data maintenance, transports, and tests.
■ Target group:
● System administrators
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/instguides
The application operations guide is used for operating an SAP application once all tasks in
the technical operations manual have been completed. It refers users to the tools and
documentation that are needed to carry out the various operations-related tasks.
■ Target group:
● System administrators
● Technology consultants
● Solution consultants
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/instguides

Upgrade

The upgrade master guide is the starting point for upgrading the business scenarios and
processes of an SAP solution. It provides scenario-specific descriptions of preparation, execution,
and follow-up of an upgrade. It also refers to other documents, such as upgrade guides and
SAP Notes.
■ Target group:
● Technology consultants
● Project teams for upgrades
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/instguides
The upgrade guide describes the technical upgrade of an installable unit, taking into
account the combinations of operating systems and databases. It does not describe any
business-related configuration.
■ Target group:
● Technology consultants
● Project teams for upgrades
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/instguides
Release notes are documents that contain short descriptions of new features in a particular release
or changes to existing features since the previous release. Release notes about ABAP
developments are the technical prerequisite for generating delta and upgrade Customizing in
the Implementation Guide (IMG).
■ Target group:

2013-11- PUBL 23/


A Referen
A.1 The Main SAP Documentation Types

● Consultants
● Project teams for upgrades
■ Current version:
● On SAP Service Marketplace at http://service.sap.com/releasenotes
● In the SAP menu of the SAP system under Help Release Notes (only ABAP
developments)

24/ PUBL 2013-11-


Typographic Conventions

Example Description
<Example> Angle brackets indicate that you replace these words or characters with
appropriate entries to make entries in the system, for example, “Enter your
<User Name>”.
Example Arrows separating the parts of a navigation path, for example, menu options
Example
Example Emphasized words or expressions
Example Words or characters that you enter in the system exactly as they appear
in the documentation
http://www.sap.com Textual cross-references to an internet address
/example Quicklinks added to the internet address of a homepage to enable quick access to
specific content on the Web
123456 Hyperlink to an SAP Note, for example, SAP Note 123456
Example ■ Words or characters quoted from the screen. These include field labels, screen
titles, pushbutton labels, menu names, and menu options.
■ Cross-references to other documentation or published works
Example ■ Output on the screen following a user action, for example, messages
■ Source code or syntax quoted directly from a program
■ File and directory names and their paths, names of variables and parameters,
and names of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program
names, transaction codes, database table names, and key concepts of a
programming language when they are surrounded by body text, for example,
SELECT and INCLUDE
EXAMPLE Keys on the keyboard

2013-11- PUBL 25/


SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2013 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.
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. National product specifications may vary.
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 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 other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.

Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

Documentation in the SAP Service Marketplace


You can find this document at the following address: http://service.sap.com

26/ PUBL 2013-11-


SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com

© Copyright 2013 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.

You might also like