BP DBM6.0 QuickGuide EN DE

SAP ECC 6.
00
August 2007
English
Quick Guide to Installing

the SAP Best Practices
for Dealer Business
Management V1.600
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices Quick Guide to Installing the SAP Best Practices for DBM
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 3 of 32
Icons
Icon Meaning
Caution
Example
Note
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.
Contents
1 Purpose............................................................................................................................. 6
2 System Preparation........................................................................................................... 7
2.1 Best Practices Add-On and Transport.....................................................................7
2.2 System Status of Client Roles.................................................................................7
2.3 Release and Support Package Level.......................................................................7
2.4 SAP Notes and Messages.......................................................................................9
2.5 Printer Settings...................................................................................................... 13
2.6 SAPGUI Version.................................................................................................... 13
3 Installation Preparation.................................................................................................... 14
3.1 Option 1: Creating Installation Folder manually without using the SAP Best
Practices Personalization Assistant.....................................................................................14
3.2 Option 2: Creating Installation Folder for the SAP Best Practices Installation Files
using SAP Best Practices Personalization Assistant...........................................................15
3.3 Creating Transfer Requests and Modifying DXX File............................................16
3.4 User Specific Settings for Installation....................................................................17
3.4.1 Maintaining Profile Parameters - SAP Scripting................................................17
3.4.2 Allowing GUI Scripting.......................................................................................18
3.4.3 Setting Decimal Notation and Date Format.......................................................18
3.4.4 User Settings for Installing Scenarios that Use Variant Configuration...............19
3.5 Switching Off - Enable Dialog Box for Dynpro Size Check...................................19
3.6 Using “SAP Best Practices Installation Assistant”.................................................20
3.6.1 Installation of the Best Practices Installation Assistant......................................20
3.6.2 Running the Installation Assistant.....................................................................20
3.6.3 Interface............................................................................................................ 20
3.6.4 SAP Best Practices Installation Assistant User Guide.......................................20
3.7 Upload the scope file for SAP BP for DBM to the Installation Assistant.................21
3.7.1 Selecting Scenario Projects in a Scope.............................................................21
3.7.2 Preparation: Setting Up Document Path............................................................22
3.7.3 Displaying a Project Document.........................................................................23
4 Installation Execution....................................................................................................... 23
4.1 Installation Sequence for DBM..............................................................................23
4.1.1 Installation Step 1 - Installing Baseline Germany, Layer 0 and Layer 1 Building
Blocks 23
4.1.2 Installation Step 2 - Activating BC Sets for Dealer Business Management (DBM)
25
4.1.3 Installation Step 3 - Installing BP DBM General Building Blocks.......................25
4.1.4 Installation Step 4 - Installing BP DBM Scenarios.............................................26
4.1.5 Install BP DBM Smart Forms (Optional)............................................................26
4.1.6 Installation Map................................................................................................. 27
4.2 Error Handling....................................................................................................... 27

4.2.1 Processing General Errors during Installation...................................................27
4.2.2 Processing of Specific Errors............................................................................29
5 Appendix.......................................................................................................................... 30
5.1 Layer Concept....................................................................................................... 30
Quick Guide to Installing the SAP Best Practices

for Dealer Business Management
1 Purpose
This quick guide provides the information you need to install the complete SAP Best Practices
for Dealer Business Management using automated configuration tools, such as BC Sets. It
also explains how to proceed if you want to install individual scenarios instead.
This document is intended for consultants and system administrators who

already have a sound knowledge of SAP Best Practices, including the tools
and documentation. If you are not familiar with these, refer first to the
document SAP Best Practices Tools (J00).
How to install SAP Best Practices for Dealer Business

Management
The information in this document is a supplement to the J00 – SAP Best Practices Tools and
provides you with additional information relevant for the SAP Best Practices for Dealer
Business Management setup before you start with the installation of the Baseline Building
Blocks and DBM Building Blocks and Scenarios.
The installation of SAP Best Practices for Dealer Business Management comprises two basic
parts:
- the installation of baseline building blocks for DBM
- the installation of Dealer Business Management building blocks and scenarios.
2 System Preparation
Please follow the steps in this chapter sequentially to perform the preparation for the SAP
Best Practices DBM system.
2.1 Best Practices Add-On and Transport

The Best Practices Add-on and special transport with additional objects have to be imported
into the system. For more details, see the document Importing Best Practices Add-Ons
(ADDONINS.PDF) on the configuration DVD.
2.2 System Status of Client Roles

The system must not comprise any client that is set to status productive client role. If the
system contained a productive client, extension sets cannot be activated as required and the
automatic installation of SAP Best Practices content using the SAP Best Practices Installation
Assistant is not possible due to the impossibility to activate BC sets in the system. You can
use the transaction SCC4 to check the client roles in your system.
2.3 Release and Support Package Level

The deliverables of SAP Best Practices for Dealer Business Management were developed
and tested in a system landscape with specific support package levels. If the support package
levels in your system are different, there could be errors during the installation. You may be
able to perform the installation activities manually using the configuration guides, but errors
may also occur.
For cases when the support package levels do not match the SAP Best Practices
requirements, especially when HIGHER support package levels are implemented,
only LIMITED SUPPORT can be granted.
If you need a higher support package level in your system, for example because
of additional functionality, FIRST install SAP Best Practices on the system SP
levels as mentioned above, and then upgrade your system to the latest support
package level.
The basic support package levels relevant for SAP Best Practices for Dealer Business
Management V1.600 are as follows:
Software Release Support Highest Support Short Description of Software
Component Package Package Component
SAP_ABA 700 0011 SAPKA70011 Cross-Application Component
SAP_BASIS 700 0011 SAPKB70011 SAP Basis Component
ST-PI 2005_1_700 0003 SAPKITLQI3 SAP Solution Tools Plug-In
PI_BASIS 2005_1_700 0011 SAPKIPYJ7B PI_BASIS 2005_1_700
SAP_BW 700 0012 SAPKW70012 SAP NetWeaver BI 7.0
SAP_AP 700 0008 SAPKNA7008 SAP Application Platform
0004 LC Applications (LCAPPS)
LCAPPS 2005_700 SAPKIBHD04 2005_700
SAP_HR 600 0013 SAPKE60013 Human Resources
SAP_APPL 600 0008 SAPKH60008 Logistics and Accounting
EA-IPPE 400 0008 SAPKGPID08 SAP iPPE

EA-APPL 600 0008 SAPKGPAD08 SAP Enterprise Extension PLM,
SCM, Financials
EA-DFPS 600 0008 SAPKGPDD08 SAP Enterprise Extension Defense
Forces & Public Security
EA-FINSERV 600 0008 SAPKGPFD08 SAP Enterprise Extension Financial
Services
EA-GLTRADE 600 0008 SAPKGPGD08 SAP Enterprise Extension Global
Trade
EA-HR 600 0013 SAPKGPHD13 SAP Enterprise Extension HR
EA-PS 600 0008 SAPKGPPD08 SAP Enterprise Extension Public
Services
EA-RETAIL 600 0008 SAPKGPRD08 SAP Enterprise Extension Retail
FINBASIS 600 0008 SAPK- Fin. Basis
60008INFINBASI
S
IS-OIL 600 0008 SAPK- IS-OIL
60008INISOIL
IS-M 600 0008 SAPK- SAP MEDIA
60008INISM
IS-H 600 0008 SAPK- SAP Healthcare
60008INISH
IS-CWM 600 0008 SAPK- Industry Solution Catch Weight
60008INISCWM Management
INSURANCE 600 0008 SAPK- SAP Insurance
60008ININSURA
NC
FI-CAX 600 0008 SAPK- FI-CA Extended
60008INFICAX
FI-CA 600 0008 SAPK- FI-CA
60008INFICA
ERECRUIT 600 0008 SAPK- E-Recruiting
60008INERECR
UIT
ECC-DIMP 600 0008 SAPK- DIMP
60008INECCDIM
P
DBM 600 0001 SAPK- DBM 600 : Add-On Installation
60001INDBM
IS-PS-CA 600 0008 SAPK- IS-PUBLIC SECTOR CONTRACT
60008INISPSCA ACCOUNTING
IS-UT 600 0008 SAPK- SAP Utilities/Telecommunication
60008INISUT
WFMCORE 200 0008 SAPK- WFMCORE 200 Installation: Meta-
20008INWFMCO Commandfile
RE
LSOFE 600 0008 SAPK- SAP Learning Solution Front-End

60008INLSOFE
SEM-BW 600 0008 SAPKGS6008 SEM-BW: Strategic Enterprise
Management
MRSS 600 0002 SAPK- Multi Resource Service Scheduling
60002INMRSS
BP-INSTASS Refer to the Best Practices Installation Assistant
comments below based on SAP_BASIS 700
BP-ERP05 Refer to the SAP Best Practices All-in-One
comments below based on ERP 2005 (ECC 600)
For more details of the support packages in question, see the document Importing Best
Practices Add-Ons (ADDONINS.PDF) on the configuration DVD.
The release of the software components BP-ERP05 and BP-INSTASS depend on

the SAP Best Practices configuration DVD you use for your installation. The
appropriate release information is listed in the document Importing SAP Best
Practices Add-Ons (ADDONINS.PDF) on the configuration DVD.
Besides the above components, please ensure that you also install TREX,
2.4 SAP Notes and Messages

In addition to the system status described above the following SAP Notes must be
implemented:
SAP Notes regarding Installation Assistant
SAP Note # Description Component

846028 Additional information for BP-INSTASS 500V1 SV-SMB-AIO-BP
SAP Notes regarding Best Practice for DBM
SAP Note # Description Component Remark

1020107 Note Assistant: Message type " " is unknown
1018338 BAdI sorter sorts incorrectly after import/upgrade
731958 AbrV: No automatic generation with reference or
1029666 NOTE/BAdI Impl.:Wrong filter value after you
1033675 Short dump meanwhile searching for LBRO.
All fields getting doubled in customer
975279 enhancement
VMAS: Inconsistency in function group
1035747 /DBM/VM24
Search help not working for Defect Code in
1036763 WTYRCL
1037826 Lock object /DBM/TM_TEVENT was not delivered

952945 Use of HR persons with MRSS 600
1037271 Missing delivery customizing workshop planning
1035030 MRS dump occurs
1040042 MRS:Appointment scheduling, Error while saving
1040346 App.Scheduling: Error while saving
1039977 Job/tasks vanishes + later a dump
1040279 MRS:Appointment scheduling, Error while saving
1038795 App.Sched.:'Delete Task'-Problems
1039636 P020 quantity not related on slots
1041893 Book of Replacement car is disappearing temp.
1041833 DBM print report only works with SAP ArchiveLink
1041157 DBM Time Recording: update of item quantity
Orders can not be displayed, if item or order is
1042229 billed
DBM Time Recording: Time Sheet entries with
1042634 zero
1042661 Error comes out at recall copy.
1040312 Fields to be removed from the recall ALV
Deletion of DBM-docflow entries did not work
1045977 correct
1045405 Not possible to execute vehicle transfer
1037471 Status ID TECH_CONF should not be a default
VMAS: Error when transfering vehicle between
1047888 company
SR: Strategy to profitability segment creates rule
1053947 with '08'
1055080 Using the new G/L and DBM: Down payments
1038860 K0105: "Group ... does not exist"
Account assignment category deletes RE partner
1050837 role
1046974 Vehicle Order executes Vehicle Actions in display
1038828 Order status is not updated after warranty action
1053622 Several part items cannot be reposted
Runtime error when you search for CO
1059046 documents
1058812 Very low performance of DBM collective billing
1061320 Internal Error while rejecting a DBM Quotation
1061180 No reposting during billing for goods receipt
Notifications and invoices are not ordered

1059636 descending by the date in the Fact Sheet
1020542 Runtime error in the cost analysis
1002078 Deleted links remain in the buffer
1010837 Document Flow objects are not saved after
Print Order: Wrong screen at defining message
1047592 schema
1047372 Wrong commit control at printing of DBM Order
1047373 Customizing settings for action PRINT_WI
Changing an Item causes short dump
1041513 MESSAGE_TYPE_X
DBM Order: Runtime error
1058441 DYNPRO_NOT_FOUND
replacement car's price independent of time slot
1042023 length
MRS: problem in rendering the cust advisor time
1051861 slots
Wrong tool tip of the Button "NEW" and
1053202 "DELETE"
Time data for Customer advisor not transferred to
1053932 Appointm
1038963 Not all pricing fast entry fields are accessible
1038985 DBM Order Screen enhancement - data transfer
1034114 Fast Entry of Items: Item Search after ENTER
Currency changes does not get poppulated to the
1040320 item level
1041344 Fast entry of items: dump at using of F4-help
1041642 Screen Flow - Logical Order of Tab Chain
Screen Flow - Logical Order of Tab Chain is
1042280 wrong
1017773 Copy tool doesn't support copying of tasks
1045155 Order User Interface - Call of Change Events
Delete global variables, tables, and so on in the
1047224 job
1047367 Deletion of global variables not correctly executed
The tree container of job and task contains old
1052514 data
1054304 Sold-to party address data is displayed incorrectly
Wrong output conversion for unit of measure in
1054763 scheduling
In /dbm/order01, BACK the workshop overview is
1055592 not refresh
1056420 Workshop Overview, date changes effects

1055834 editing replacement car time slot in DBM order
1060460 Static code separation
Action SPLHDR_CHANGE is called
1051503 unnecessarily
SAP BP:Not possible to create role categories
1051894 with
Distr. Chnl / Division changed on TCODE
1041958 /DBM/ORDER
ACC:Abbreviation Error on Criteria Button of
1044471 Order
1048940 DBM Order: Job and Task handling
Fast-Entry of Items: Item quantity is note
1048113 overtaken
1042021 Deleted second schedule line not saved
1041892 Strange time calcul.in the WS Overview
1044349 No simulation after order reload
App.Sched.: Task Sch. Lines - different UoM
1041195 possible
Display the customized item category on PREQ
1041591 Screen
1046414 Task number determined incorrectly
Creating a task w/o a reference job number is
1048426 possible
Inappropriate message after cancelling the item
1050708 search
TaskManager not active, but P020 still has task
1042297 no
Event PROCUREMENT aborts with error
1052577 message
Accessibility enhancement in the Memo Pad and
1040508 Fact Sheet
Fact Sheet: not proper printing for multiple
1044539 columns
Accessibility enhancement in the Memo Pad and
1040508 Fact Sheet
Warranties, which will be invalid soon sould be
1053101 selected.
Display of Warranties and Recalls in Fact Sheet
1054143 not possible
Event item change is called from UI even in
1054068 display mode
1047672 Badi Implementations of Badi
/DBM/BADI_ORDER_UI_MAIN
1076221 F4-Help: Dump CONVT_NO_NUMBER
Before you start the building block installation process, check the latest
version of the SAP Notes below to obtain updates and corrections for problems
that do not become apparent until after shipment.
SAP Note # Description Component

SAP Best Practices for Baseline
847698 SV-SMB-AIO-BP-DE
Germany
SAP Note #
BP for Dealer Business Description Component
Management
SAP Best Practices for Dealer
1069193 SV-SMB-AIO-BP-DBM
Business Management
If you do not find a solution for the problem this way, open a customer message specifying
the component SV-SMB-AIO-BP-DBM.
2.4.1.1 Note Corrections and Downloads for DBM

Download the latest documents and files attached to the note 1069193 mentioned above.
Read this note carefully. Extract the zip files as described and use the latest version of these
files/documents for your installation.
2.5 Printer Settings

For installation of SAP Best Practices, the standard default printer LP01 is used that is
generated during the SAP standard system set up.
For actual printing (generating output) after you have finalized the SAP Best Practices
installation, this printer LP01 can NOT be used (for details, see SAP note 573309). Instead,
an existing printer at your side has to be selected for generating output.
Your printer needs to be linked to a device type for which the HELVE font family is
defined (for example to the device type SAPWIN) to ensure that the forms printout is
correct.
In case of a personalized installation: During the personalization step 1, Preparation

 Installation Parameters  Printer and Development Class, a default printer has to
be maintained. The default printer LP01 can only be replaced by a printer already
existing in your system. If no printer exists, the value LP01 has to be kept to avoid
errors during the following installation.
2.6 SAPGUI Version

Ensure the SAPGUI version is 6.40 and patch level is above 14.
3 Installation Preparation
Before you install the SAP BP for DBM solution, you must perform some preliminary tasks.
You have two options for installation. You can perform a default installation using SAP-
delivered organizational parameters. To do this, read and follow the Default Installation
instructions under option 1.
Alternately, you can perform a personalized installation. This allows you to personalize certain
organizational parameters. To do this, read and follow the Personalized Installation
instructions under option 2.
3.1 Option 1: Creating Installation Folder manually

without using the SAP Best Practices
Personalization Assistant
1. Create a folder on a server that can be accessed from within the SAP system where you
want to install the SAP Best Practices DBM Package. Ensure that the persons who will
install SAP Best Practices have the necessary user rights to access this folder.
2. The installation files (variant files) are attached to the collective note for DBM (note:
1069193). Please make sure that you download the installation files (ZIP-Files) that
correspond to the material number of the configuration DVD or the number of the
download object in the software distribution center (SWDC) or the SAP Best Practices
Add-On Version.
Number Config DVD: 5XXXXXXXX

or
Number/File of Download Object in the SWDC 5XXXXXXXX.ZIP
or
SAP Best Practices Add-On Version: BP-ERP05 600VX
 ZIP file with variant files (installation files) for DBM attached to note:
5XXXXXXX_DBM_FIL_BP_ERP05_600VX.ZIP
 How do I determine the number of the Config DVD?

The material number of the configuration DVD (not the documentation DVD) can be
found on the DVD.
 How do I determine the number of the download object?
The number of the download object can be found in the software distribution center
(SWDC) in the download area for the download object Config: Best Practices All-in-
One. This number and the file name of the download ZIP file is identical to the
material number of the configuration DVD.
 How do I determine the Add-On version?
You can determine the Add-On Version as follows:
SAP Easy Access menu: System  Status  Component information
Picture: How to determine Add-On version

Prerequisite: The Add-On has been installed in the ERP system.
3. Download and extract the installation file package (ZIP file) attached to the note in a new
folder. This folder will be used as installation folder later.
3.2 Option 2: Creating Installation Folder for the SAP

Best Practices Installation Files using SAP Best
Practices Personalization Assistant
1. Follow the guided installation procedure as outlined in the respective section Installation
on the documentation DVD.
2. During the environment generation you have direct access to the attachment area of the
collective note. Follow the guided procedure to create the required installation folders and
other settings required for personalization.
3. The installation files (variant files) are attached to the collective note for DBM (note:
1069193). Make sure that you download the installation files (ZIP files) that correspond to
the material number of the configuration DVD or the number of the download object in the
software distribution center (SWDC) or the SAP Best Practices Add-On Version.
Number Config DVD: 5XXXXXXXX

or
Number/File of Download Object in the SWDC 5XXXXXXXX.ZIP
or
SAP Best Practices Add-On Version: BP-ERP05 600VX
 ZIP file attached to note: 5XXXXXXX_DBM_FIL_BP_ERP05_600VX.ZIP
 How do I determine the number of the Config DVD?

The material number of the configuration DVD (not the documentation DVD) can be
found on the DVD.
 How do I determine the number of the download object?
The number of the download object can be found in the software distribution center
(SWDC) in the download area for the download object Config: Best Practices All-in-
One. This number and the file name of the download ZIP file is identical to the
material number of the configuration DVD.
 How do I determine the Add-On version?
You can determine the Add-On Version as follows:
SAP Easy Access menu: System  Status  Component information
Prerequisite: The Add-On has been installed in the ERP system
4. Now you know which installation file package (ZIP file) you have to download during the
set up of the installation / personalization environment.
5. Start the environment setup. When you are processing the step Variant Source you have
to download and extract the installation file package in a folder you want to use as the
source folder.
We recommend using the SAP Best Practices Personalization Assistant for

downloading the installation files and creating the installation folders even
if you do not want to personalize.
3.3 Creating Transfer Requests and Modifying DXX

File
Procedure
1. Create one workbench transfer request and one customizing transfer request by
transaction code SE01.
2. Assign your user to the two transfer requests by transaction code SE01.
3. Change the Test Data Container file in the variant folder (that you have created in step
3.1 or 3.2 ) for Dealer Business Management:
SMB99_ACTIVATION_PARM_DXX_J01.TXT
a. Assign the workbench transfer request number to the field I_TRKORR_W, and the
customizing transfer request number to the field I_TRKORR_C.
3.4 User Specific Settings for Installation

3.4.1 Maintaining Profile Parameters - SAP Scripting
Use
You have to allow eCATT processing in the system: the profile parameter
sapgui/user_scripting has to be set. The value for Enable or disable user scripting on the
front-end has to be set true.
Only those installation users have to perform this activity that does not install the
building block B32 (for example, someone else installed Layer 0 including BB B32
and you want to install the BB AZ1).
Procedure
1. Run the following activity:
SAP System menu Preparation  Maintain Profile Parameters – SAP Scripting
Transaction code RZ11
2. On the Maintain Profile Parameters screen, make the following entries
Field name Description User action and values Note
PARANAME Profile parameter sapgui/user_scripting
name
Display
3. On the Display Profile Parameters Attributes screen, choose Change values.
4. On the Change Parameter Value screen, make the following entries.
Field name Description User action and values Note
New Value TRUE Enable SAP
Scripting
5. Choose Save.
When you save the change, the window closes and the current value of the
parameter changes to TRUE. This change only becomes effective when you log
onto the system again.
If the parameter is set in rz11, you lose the change when you restart the server.
3.4.2 Allowing GUI Scripting
Use
Perform this activity so that eCATTs GUI Scripts can by executed with your GUI.
Only those installation users, who haven’t installed building block B32, have to
perform this activity. (For example, someone else installed Layer 0 including BB
B32 and you want to install the BB AZ1).
Procedure
1. Choose the first button from the right side of the Standard Tool Bar Customizing of Local
Layout or type ALT + F12.
2. Choose the menu item Options.
3. Choose the tab strip Scripting.
4. Select the checkbox enable scripting.
5. Deselect the checkboxes Notify When a Script Attaches to a Running GUI and Notify
When a Script opens a Connection.
6. Choose OK at the bottom.
3.4.3 Setting Decimal Notation and Date Format
Use
Perform this activity to set up the installation user ID.
Only those installation users, who haven’t installed building block B32, have to
perform this activity. (for example, someone else installed Layer 0 including BB
B32 and you want to install the BB AZ1).
Procedure
1. Access the activity using the following navigation option:
Transaction code SU3
2. Choose the tab strip Defaults.
3. Make sure Decimal Notation is set up as 1.234.567, 89.
4. Make sure Date Format is set up as DD.MM.YYYY.

5. Save your settings.
5. Log off and log on the system again.
Result
The installation procedure can now be run without errors resulting from the decimal notation
or date format.
3.4.4 User Settings for Installing Scenarios that Use Variant

Configuration
Use
Before you can install those business scenarios that use variant configuration, you need to
assign a specific parameter to your user profile.
Parameters
Check the user data in transaction SU3. Ensure that you set the following parameters in your
user master record:
Parameter Value
CUQ 001
Make sure that your logon language is English.
3.5 Switching Off - Enable Dialog Box for Dynpro Size

Check
Use
Perform this activity so that the dynpro size check is disabled. This activity is not done in
building block B32.
Procedure
1. Choose the first button from the right side of the Standard Tool Bar Customizing of Local
Layout or type ALT + F12.
2. Select the menu item Options.
3. Choose the tab strip Options.
4. Deselect the checkbox Enable Dialog Box for Dynpro Size Check.
5. Choose the OK button at the bottom.
3.6 Using “SAP Best Practices Installation Assistant”

3.6.1 Installation of the Best Practices Installation Assistant
Use
SAP delivers the SAP Best Practices Installation Assistant program as a separate add-on
(BP-INSTASS) on the SAP Best Practices solution configuration DVD. Your system
administrator will handle installation of the SAP Best Practices Installation Assistant.
3.6.2 Running the Installation Assistant
Use
This activity runs the SAP Best Practices Installation Assistant.
Procedure
Access the activity using the following option:
Transaction code /n/SMB/BBI
3.6.3 Interface
Use
The SAP Best Practices Installation Assistant consists of two main screens:
 Building Block Installer
 Building Block Builder
The Building Block Installer screen is the first screen you see when you run the transaction;
this is the relevant screen for the installation of the SAP Best Practices Baseline Package.
The Building Block Builder screen is where you create or building blocks for use in the
projects in the Building Block Installer screen.
3.6.4 SAP Best Practices Installation Assistant User Guide
Use
This document describes all the functionalities of the SAP Best Practices Installation
Assistant. It explains how to import the SAP Best Practices Baseline Package scope and
activate building blocks.
The user guide can be found on the documentation DVD in the area Installation.
Do NOT delete Installation Assistant projects ONCE they have been activated. If
you delete projects, the activation history and the respective logs are lost and it is
not possible to find possible error reasons with tenable efforts.
In such cases NO SAP SUPPORT CAN BE PROVIDED.
3.7 Upload the scope file for SAP BP for DBM to the
Installation Assistant
To install one (or more or all) scenarios, upload the DBM scope file as follows:
1. Start the Installation Assistant, and on the Best practices Installation Assistant - Project
View screen, choose Goto  Scope Editor.
2. Choose Import, and open the file SAP_BP_DBM_DE_V1600_SCOPE.bps.
How to get the Scope file

The Scope file (.bps file) can be found as attachment to the SAP Best Practices
DBM Package support note (1069193), extract the file
SAP_BP_DBM_DE_V1600_SCOPE.zip.
3. You need to wait for a few minutes while the building blocks and projects are uploaded to
the Installation. On the Report dialog box, choose Continue.
4. The entire scope displays in the Scopes column.
Result
The entire SAP Best Practices for DBM installation scope is loaded into the Installation
Assistant.
3.7.1 Selecting Scenario Projects in a Scope
Use
This activity shows you how to select an entire scope or personalize the scope to activate
selected scenarios.
Procedure: Entire Scope

1. To activate the entire scope, select the top node (SAP BEST PRACTICES FOR DBM DE)
and choose the Set Scope to Favorite button. The system displays an asterisk document
graphic to the left of the scope name.
2. Choose the Display Favorite Scope button. The system displays the Best Practices
Installation Assistant – Scope View screen with all building block projects in the scope
listed.
Procedure: Personalize the Scope

1. If you want to activate only certain scenarios, in the Scope Editor, choose the Change.
2. On the Change scope dialog box, deselect the checkboxes for the building block projects
you do not want to activate. Choose Continue when you are done.
To determine which building blocks you require, see the Installation Map in step
4.1.6.
3. The Scope Editor displays the selected building block projects that will be available for
activation. Choose the Set Scope to Favorite button. . The system displays an asterisk
document graphic to the left of the scope name.
4. Choose the Display Favorite Scope button. The system displays the Best Practices
Installation Assistant – Scope View screen with the selected building block projects in the
scope listed.
3.7.2 Preparation: Setting Up Document Path
Use
To access the descriptions for manual activities in SAP Best Practices for DBM DE, you must
define the path for the offline documents.
Procedure
1. Download the BPIA manual zip file, copy and unzip to a local folder for example C:\BP
How to get the BPIA Manual Files

The BPIA manual files can be found as attachment to the SAP Best Practices
DBM Package support note (1069193). File name BPIA_MANUAL_STEPS.zip
2. On the Best Practices Installation Assistant – Project View screen, from the menu,
choose Goto  Parameter Maint.
3. On the Define Parameter dialog box, choose the Display <> Change to enter change
mode.
4. Choose the Insert Row button.
5. In the Parameter field, enter %docfolder%
6. In the Value field, enter the folder you copied the BPIA manual step files to for example
C:\BP\
Ensure that you enter the trailing slash. Otherwise, your documents will not
display.
7. Choose Continue.
3.7.3 Displaying a Project Document
Use
This activity is only required if you want to see detailed descriptions on manual activities
outside of the installation activity.
Documents will display automatically during installation.
Procedure
1. On the Best Practices Installation Assistant – Project View screen, double-click the
document icon next to a task, folder, or building block.
You may need to expand the scope and project nodes to view items with
documents.
2. A dialog box displays the attached document. Choose the Close.
As an example, expand the B32 building block and double-click the document
icon for step SCC4.
4 Installation Execution
When considering installation of Best Practice for Dealer Business Management, you can
install the complete package or only certain scenarios of your choice. You can see details of
the individual scenarios on the documentation DVD.
4.1 Installation Sequence for DBM

Installation of SAP Best Practices for DBM contains 4 major steps:
1. Installation of Baseline Germany for DBM (Layer 0 and Layer 1 BB's)
2. Activation of BC Sets for Dealer Business Management (DBM)
3. Installation of DBM DE Building Blocks and Scenarios.
4. Installation of DBM Smartforms (Optional)
4.1.1 Installation Step 1 - Installing Baseline Germany,

Layer 0 and Layer 1 Building Blocks
The building blocks packed into "Baseline BB for DBM" are modified; therefore,
please always use the latest BPIA scope and the external files attached to the
note 1069193.
Layer 0 Building Blocks

Building Block ID Name
B32 Settings for Best Practices Installation

J02 Organizational Structure
N69 External Financial Accounting Basics
N70 External Financial Accounting
N71 Central Cost Center Accounting
J05 Materials Management
J04 Sales and Distribution

Building Name Remarks
Block ID
J18 Product Cost Planning
You do not need to install part for

COUNTRY-SPECIFIC TEXTS.
J17 Profitability Analysis In step DEFINE RULE VALUES

FOR DERIVATION RULES
(transaction code KEDR).You do
not need to install the step 6 -
Maintain Rule Values button for
the line Customer  Inter-
company Indicator
The following sections only need

to be applied. Organizational
N72 Asset management Structure, Integration with the
General Ledger, Valuation,
Depreciation, Information
System, Preparing for production
start-up, Fiscal Year Change
Procedure
1. Activate the project BASELINE DE (DBM).
Refer to the "User Guide - SAP Best Practices Installation Assistant" for the
detailed procedure.
Result
The Baseline DE for DBM is activated in the relevant client
4.1.2 Installation Step 2 - Activating BC Sets for Dealer

Business Management (DBM)
4.1.2.1 Activating DBM BC Set /DBM/DBM600ERP
Use
A distinction is made between the following areas for configuring DBM:
● DBM configuration, in other words, entries in /DBM/* Customizing tables
● ERP and environment configuration, in other words, Financials, Controlling, Sales and
Distribution, and so on
The configuration data in this BC Set is based on the Customizing settings shipped with ERP
2005, that is, company code 0001 (chart of accounts INT, currency EUR).
The objective here is to mode a simple service process right through to the billing stage.
Procedure
1. Access the transaction choosing one of the following navigation options:
SAP menu Tools  Customizing  Business Configuration Sets 
Activation of BC Sets.
Transaction code SCPR20
You need accept the default value proposed by system and choose expert mode
to activate DBM BC Set.
2. Choose the activation options for overwriting all data and expert mode.
3. Activate the data in the following sequence:
 /DBM/DBM600ERP
Result
The BC Set /DBM/DBM600ERP is activated in the relevant client
4.1.3 Installation Step 3 - Installing BP DBM General

Building Blocks
Building Block ID Name
AZ1 DBM Basic Settings
AZ2 Warranty and Recall Settings
AZ3 Appointment Schedule and Time Recording Settings
AZ4 Notification Settings
Procedure
1. Activate the building blocks in the sequence specified in the installation map below
It is mandatory that all prerequisite building blocks are first installed in the system.
If you try to install a building block where some prerequisite building blocks have
not been installed, you will meet errors.
Result
The DBM general building blocks are activated in the relevant client.
4.1.4 Installation Step 4 - Installing BP DBM Scenarios

Scenario ID Name
AA0 Appointment Scheduling and Workshop Planning
AB0 Time Recording
AC1 Parts Purchasing
AC2 Parts Stock Transferring
AC3 External Service Procurement
AD0 Customer Management
AE0 Used Vehicle Purchasing
AF1 New Vehicle Sales with Down payment
AF2 New Vehicle Sales with Cross Plant Stock Transfer (1CC)
AF3 New Vehicle Sales with Cross Company Stock Transfer (2CC)
AF4 Vehicle Sales from Showroom
AG0 Vehicle Service and Recalls
AH0 Parts Cash Sales and Returns
AI0 Order Cancellation with Fast Order Entry
Procedure
1. Activate the scenarios you wish to install in the system.
It is mandatory that all prerequisite building blocks are first installed in the system.
If you try to install a scenario where some prerequisite building blocks have not
been installed, you will meet errors.
Result
The DBM Scenarios are activated in the relevant client
4.1.5 Install BP DBM Smart Forms (Optional)

If you wish to install the Smart forms for DBM in your system, you should follow the guided
installation process as outlines in the customizing guide DBM_SF_CUSTOMIZING_GUIDE.doc.
Please refer to the section Smart Forms on the Documentation DVD for a link to the
documentation for Smart Forms.
SAP Note 1069194 provides you with more detailed information regarding the Smart forms in
the SAP Best Practices for Dealer Business Management solution.
4.1.6 Installation Map

The building blocks in SAP Best Practices for DBM needs to be installed following the
sequence listed in the installation map below.
BP DBM 6.0 - Installation Map

Start
here
Baseline DE B32 J02 N69 N70 N71 J05 J04

Baseline DE J18 J17 N72

DBM DE Industry
Building Blocks AZ1 DBM Basic Settings
DBM DE Industry
AZ3: Apt. Sched. AZ2 Warranty and AZ4
Building Blocks and Time Rec. Recalls Notification
DBM DE
Scenarios AA0 AB0 AG0 AD0 AE0
AC1 AC2 AC3 AF1 AF2
AF3 AF4 AH0 AI0
Installation Sequence
 SAP AG 2007, SAP BP DBM
4.2 Error Handling

The following information helps you to solve problems that might occur during the installation
process.
4.2.1 Processing General Errors during Installation
Use
When an activation of an automated task runs into errors, the activation stops at the point of
the error. No further implementation can be done until the error is resolved.
Procedure
1. On the Building Block Installer screen, select a task that has a red light in the Current
status column.
2. Expand the task and choose the log that is assigned to this task.
Detailed information about the error is displayed in the Error List pane.
3. In the Error List pane choose Display Detailed Log. The detailed log information about an
eCATT or BC set activation is displayed.
4. In this log information check entries with a red light to identify the reason for the error.
5. In case the error can be solved based on the log information choose run the eCATT or
BC set again.
See the document SAP Best Practices Tools for details about the manual
activation of eCATTs and BC sets. The document can be found on the
documentation DVD in the area Technical Information  Tools and Concept.
6. In case the log information is not sufficient to solve the problem you can proceed as
follows:
a. Execute the task manually: use the description of the related section in the
configuration guide for executing the task,
or
b. Open a customer message for this problem specifying the component SV-
SMB-AIO-BP-DBM.
Do NOT delete Installation Assistant projects ONCE they have been activated. If
you delete projects, the activation history and the respective logs are lost and it is
not possible to find possible error reasons with tenable efforts.
7. When you have solved the problem (either executed the task manually or a solution has
been provided via customer message), choose the Change button that is displayed in the
Old Status column to the right of the task.
Do NOT proceed with installation if the problem has not been solved. If you
continue without solving the problem, severe errors might result in the
subsequent installation steps that cause incalculable efforts to fix.
8. Choose the Change button that is displayed in the Old Status column to the right of the
task.
9. On the Confirmation dialog box, choose OK to manually change the status to successful.
10. On the Information dialog box, enter a reason for changing the status.
11. Choose Continue.
The information is saved in a log. To view details for a changed task, choose the
red light in the Original Status column for that task. A dialog box displays the user
who performed the change, the date of the change, and the reason for the
change. Choose Continue to close the dialog box.
12. Choose Activate to continue with the installation of the Building Block.
4.2.2 Processing of Specific Errors

4.2.2.1 Baseline DE Building Blocks
Please refer to the Baseline DE Quick Guide in case that you encounter problems during the
baseline installation.
4.2.2.2 Warnings in the BC-Set Logs

If an eCATT runs on status red (error), check the eCATT log with regard to the BC Sets that
have been activated by this eCATT. If the eCATT log ran on error because the BC Sets have
been activated with warnings (use the BC Set log to check this), the eCATT error can be
ignored. Set the installation status manually on green, if the BC Set has been activated
successfully.
4.2.2.3 eCATT Error Variable xyz does not exist….

If an eCATT runs on status red (error), check the eCATT log with regard to the BC-sets that
have been activated by this eCATT. If the error message is variable xyz does not exist…. the
error can be ignored if the BC Sets have been activated successfully (use the BC Set log
to confirm this). Set the installation status manually on green, if the BC Set has been
activated successfully.
Example for this error:
4.2.2.4 Window appears during installation a script is

trying to attach to the GUI
If such a window appears during the installation process with the Installation Assistant,
choose OK.
4.2.2.5 Issue with SAP GUI

If you get the error message Installed scripting engine is older than engine of eCATT script.
Do you want to continue anyway? (see screenshot below) you need to update your SAP GUI
to solve this issue.
4.2.2.6 Manual Steps in Installation Process

In the SAP Best Practices Installation Assistant, SAP documented all the manual installation
steps that are necessary during the installation process of a specific building block. These
descriptions are directly attached to the installation activity in the SAP Best Practices
Installation Assistant projects in the system. However, if a description should be missing in
the Installation Assistant you can refer to the description in the configuration guide of the
respective building block.
4.2.2.7 Error Message: Execute report

COM_PRODUCT_UPGRADE
If you meet the error message Error Message: Execute report COM_PRODUCT_UPGRADE
go to transaction SE38, and execute the report.
5 Appendix
5.1 Layer Concept
The Baseline Package consists of mandatory layer 0 building blocks and optional layer 1
building blocks. The layer 0 building blocks provide fundamental preconfiguration, whereas
the layer 1 building blocks provide preconfiguration that is required for either one specific
scenario or for several scenarios. These building blocks can be put together and also
supplemented with additional industry-specific configuration to achieve a vertical industry
solution, as depicted below. For Best Practices for Dealer Business Management you
need the layer 0 Baseline Package building blocks and certain layer 1 building blocks. Which
are listed in the table above in chapter 4.2 (Install Baseline Germany, Layer 0 and Layer 1
Building Blocks).
Baseline Package as Foundation

BP DBM6.0 QuickGuide EN DE

Uploaded by

Copyright:

Available Formats

BP DBM6.0 QuickGuide EN DE

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

BP DBM6.0 QuickGuide EN DE

Uploaded by

Copyright:

Available Formats

SAP ECC 6.

Quick Guide to Installing

© Copyright 2007 SAP AG. All rights reserved.

Oracle is a registered trademark of Oracle Corporation.

Java is a registered trademark of Sun Microsystems, Inc.

MaxDB is a trademark of MySQL AB, Sweden.

Type Style Description

4.2 Error Handling....................................................................................................... 27

Quick Guide to Installing the SAP Best Practices

This document is intended for consultants and system administrators who

How to install SAP Best Practices for Dealer Business

2.1 Best Practices Add-On and Transport

2.2 System Status of Client Roles

2.3 Release and Support Package Level

EA-IPPE 400 0008 SAPKGPID08 SAP iPPE

LSOFE 600 0008 SAPK- SAP Learning Solution Front-End

The release of the software components BP-ERP05 and BP-INSTASS depend on

2.4 SAP Notes and Messages

SAP Notes regarding Installation Assistant

SAP Note # Description Component

SAP Notes regarding Best Practice for DBM

SAP Note # Description Component Remark

1037826 Lock object /DBM/TM_TEVENT was not delivered

Notifications and invoices are not ordered

1056420 Workshop Overview, date changes effects

SAP Note # Description Component

2.4.1.1 Note Corrections and Downloads for DBM

2.5 Printer Settings

In case of a personalized installation: During the personalization step 1, Preparation

2.6 SAPGUI Version

3.1 Option 1: Creating Installation Folder manually

Number Config DVD: 5XXXXXXXX

 How do I determine the number of the Config DVD?

Picture: How to determine Add-On version

3.2 Option 2: Creating Installation Folder for the SAP

Number Config DVD: 5XXXXXXXX

 ZIP file attached to note: 5XXXXXXX_DBM_FIL_BP_ERP05_600VX.ZIP

 How do I determine the number of the Config DVD?

We recommend using the SAP Best Practices Personalization Assistant for

3.3 Creating Transfer Requests and Modifying DXX

3.4 User Specific Settings for Installation

3.4.2 Allowing GUI Scripting

3.4.3 Setting Decimal Notation and Date Format

4. Make sure Date Format is set up as DD.MM.YYYY.

3.4.4 User Settings for Installing Scenarios that Use Variant

3.5 Switching Off - Enable Dialog Box for Dynpro Size

3.6 Using “SAP Best Practices Installation Assistant”

3.6.2 Running the Installation Assistant

3.6.4 SAP Best Practices Installation Assistant User Guide

In such cases NO SAP SUPPORT CAN BE PROVIDED.

How to get the Scope file

3.7.1 Selecting Scenario Projects in a Scope

Procedure: Entire Scope

Procedure: Personalize the Scope

3.7.2 Preparation: Setting Up Document Path

How to get the BPIA Manual Files

4. Choose the Insert Row button.

5. In the Parameter field, enter %docfolder%

3.7.3 Displaying a Project Document