Master Guide For-SAP DBM-800
Master Guide For-SAP DBM-800
Master Guide For-SAP DBM-800
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 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
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.
Performance http://service.sap.com/performance
2013-11- PUBL 7/
1 Getting
1.3 Important SAP Notes
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
2013-11- PUBL 9/
2 Upgrade
2.5 Overall Upgrade Sequence
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.
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
The following figure provides an overview of a possible system landscape for SAP DBM Vehicle
Sales and Administration:
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
Further Information
The vehicle service scenario covers all business process processes for managing repairs and
inspections for vehicles in your workshop. These business processes include:
■ 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
The following figure provides an overview of a possible system landscape for SAP DBM Vehicle
Service:
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
Upgrade Sequence
Further Information
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
The following figure provides an overview of a possible system landscape for SAP DBM Parts
Management:
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
Further Information
4 References
A Reference
Cross-Phase Documentation
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
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
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:
● 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)
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
Disclaimer
Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.