Documente Academic
Documente Profesional
Documente Cultură
Configuration
Applies to:
Best practice as general and specific to Baseline for GCC.
Summary
This document describes about the plan and implementation for Best practice in general.
Author Bio
The author is a consultant in the Tech Practice with over 13 years of experience of which 9 years of
SAP Technology Platform. He is involved in large Implementation in multiple SAP Solution area
.This document is the result of author’s experience in SAP Implementation using Best practice.
Table of Contents
1. Introduction:........................................................................................................................................... 3
2. What is Best Practice?........................................................................................................................... 3
2.1 SAP Best practice Into a Live system..................................................................................................... 4
3. Pre-requisites for a Best practice Installation......................................................................................... 5
3.1 Best practice Tools................................................................................................................................. 6
4. Best practice Implementation................................................................................................................. 7
Implementation Phase:..................................................................................................................................... 7
5 Best practice FAQ’s.................................................................................................................................. 11
6. Reference:........................................................................................................................................... 12
Copyright........................................................................................................................................................ 13
1. Introduction:
This document is intended for consultants and system administrators to familiarize the SAP
Best practice solutions and the various Best practice types available. The document also
explains the Best Practice pre-requisites and the functionality as of BP- ERP05 v7. Best
practice base line for GCC (AE 603V7) is considered as the base for the document.
The Best practice functionalities are made based on business need of customers and partners
based on their experience. By using best practice there are significant benefit in saving cost as well
as time.
Training material
b. Pre-configuration:
Pre-configuration settings
Sample master data
Configuration documentation
Automation tool
User roles
There are around 75 Best practice package solutions available, these are scattered
across different core areas. The core areas are broadly classified as
a. Country Baseline version (e.g.:- India, Australia, GCC, US ..)
b. Industries (e.g.:- Automotive, Chemicals, Retail, Utilities...)
c. Cross Industries (e.g.:- Baseline Package, CRM, HCM...)
d. Components specific (e.g.:- SAP ERP, SAP CRM, SAP Netweaver...)
Other key benefit is that transfer and generation of master data is accelerated and
facilitated by the use of automated procedure known as eCATT, this allows to modify and import
the customer specific master data in SAP system.
Before Implementing Best practice in to a live system always go through the key topics
into consideration.
1. Whether the Scope is identified?
2. Whether the scenarios for activating are identified?
3. Have the training team got identified?
4. Whether the Business flow clearly understood?
Once topics are clearly understood and which is fitting for the customer environment
an appropriate package can be identified for the Project.
Building block concept in Best practice: In Best practice a tool called Building blocks is used.
The benefit of building block is such that which are re-usable businesses processes oriented pre-
configured units which simply have to assemble to obtain the desired configuration. The building
blocks will vary in size and content typically some building blocks cover a small range of very
specific scenarios where as for instance building block for financial accounting contains complex
scenarios which fall in layer zero of the configuration.
The major pre-requisite for a Best practice installation and configuration are a set of
Key documentations this documents explain the step by step scenario for the installation.
The documents can be categorized as
The Installation DVD/CD carries all these documents. The consultant has to carefully
through these guides before starting activation.
There are different tools or techniques used for the Best practice installation and
configuration.
Installation Assistant: Using the best practice installation assistant we can install the
Best practice base line package easily. There are options for selecting and
implementing selected Best practice scenarios.
eCATT procedure: which is an automated testing tool that allows to create automated
functional test cases for majority of the applications, it works by
making a recording of an application which we can modify if required with different
set of values.
eCATT procedure enables us to create and execute functional tests of business
process within Best practice. The test produces a log which can be analyzed in detail
if required.
Maintaining Master data: With eCATT we can maintain master data in the client,
before maintaining the master data the project has to decide whether to
maintain/create the master date for the specific project or master data delivered by
Best practice.
Before activating BC set always compare the values existing in Customizing tables,
It is also required to activate the language that are to be used when we activate the BC
sets in Best practice implementation process.
The activation of BC sets for language can be done using transaction “SCPR20”.
Implementation Phase:
a. Plan
b. Pre-requisites and Development system setup
c. Implementation and activation of Best practice
a. Plan:
The plan consists of, preparing the plan ,understanding the scenario to be
implemented and arranging the Best practice package to be implemented.
Prepare the software (Download the Baseline for BP GCC from Service market place
and BP text files from the link www.service.sap.com/bestpractices ) extract the text
files for GCC the content name for Text file same as that of Media name in SWDC to a
common folder.
SAP Best Practices solution scope file (*.xml file): For the installation of the SAP
Best Practices Baseline Package using the SAP Best Practices Solution Builder, you
need the scope file. This scope file is attached to the note 1366041
(510*****_SCOPE_BL_GCC_V1603_603V*.zip).
Download this file, unzip it and use the extracted file as outlined in the SAP Best
Practices Baseline Package Quick Guide.
Typical Space requirement for the complete activation for Base line Package for
GCC consists approximately (BP GCC only requires 50-60 GB). Also ensure
configuration is (complete /partial)
Also certain profile parameters also has to activated before starting the activation of
Solution Builder, the key parameters are
1. login/accept_ss02_ticket > 1
2. login/crate_ss02_ticket > 2.
The best practice generally ships with the user specific roles which comes separately
In the form of sap notes (as attachment) , this user roles needs to be imported and
uploaded to the system
The pre-requisite notes as mentioned in best practice installation guide also has to
be implemented.
The transaction “/n/smb/bbi” is used for activating the Best practice scenario. Import
the solution builder xml file using this transaction. Once the xml file got uploaded the
Best practice can get activated. We can adapt different activation
approach based on our requirement. The approach can be,
The important activities which has to be taken into consideration during the activation
are the delta modifications which is happening along with Best practice activation.
The delta modifications get recorded in the form of a customizing request and
workbench request. This request holds important role in the Implementation project
since this records the key modifications/ functionalities which has to be available in the
Integration and Production landscapes.
The recommended way of using the SAP Best practices is to first install the scenarios
in a prototype environment and decide which scenarios suit your requirements. Then
the selected scenarios are installed in development environment. Before installing the
SAP Best Practice scenarios in the development environment, you can personalize the
organization structures (e.g. Company code, Plants, sales organizations etc.). While
installing in the development client, you can capture the configuration changes in
transports. These transports can be released to your Test and Production system. From
this point onwards it is a normal SAP implementation wherein you can modify or add
more configurations to meet your business requirements.
Therefore, the SAP Best practices ADD-ON is required on the prototype and
development environment. However, there is no harm in installing the SAP Best
practices ADD-ON on any system as it contains the technical objects like BC sets and
eCATTS (cross-client). They will not change the configuration tables till they are
activated in the SAP Best practices Solution Builder.
Yes multiple Best practice solutions can be installed on one client; this can be a
combination of either one base line package and one industry package.
Ref: Message no: 0120061532 0002129487 2008 and 0120050409 0000021025 2009
Best practice is purely Client Dependent the functionality available in one client won’t
be available in another client
SAP Best Practices Content for Solution Manager is no longer supported except the
few Best Practices please refer SAP note 1229397
No, Best practice is free of cost and which can be freely download from service market
place using the provided S-user id.
Yes best practice can be imported using client copy tools, however ensure with best
practice support team regarding functioning of complete functionality.
6. Reference:
1. www.service.sap.com/bestprcactices
2. CSS Support > Primary Support messages.
(SAP message : 0020079747 0000362826 2008 )
Copyright
© 2008 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, 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, 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.
These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the
implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that
may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for
errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.