Implementing the SAP CRM rapid-deployment
Solution on Top of Existing SAP CRM
SAP CRM rapid-deployment solution V4.702
Document Version 1.0
© 2012 SAP AG. All rights reserved. 2
Implementing the SAP CRM Rapid-Deployment Solution
on Top of existing SAP CRM Business Processes
Introduction and Purpose of this Presentation
The SAP CRM rapid-deployment solution is typically deployed in a new SAP CRM system, i.e. no existing
business processes in the customer‟s system landscape have to be considered and integrated. However the
SAP CRM rapid-deployment solution can also be an option for existing SAP CRM customers. These
customers would typically have at least Account- & Contact-Management and Activity Management already
up and running on the same system landscape as the SAP CRM rapid-deployment solution is supposed to
Such deployments require very detailed knowledge about the already implemented business processes and
the business processes to be implemented by the package. This document provides guidance regarding
how to proceed and what to consider from an implementation perspective.
© 2012 SAP AG. All rights reserved. 3
The SAP CRM rapid-deployment solution V4.702 requires Enhancement Package 02 (EhP2) of SAP CRM
7.0. For further details, e.g. the Support Package (SP) level required, refer to the Software Requirements
Potentially necessary upgrades from earlier releases of SAP CRM (e.g. SAP CRM 2007, SAP CRM 7.0
EhP1) or even only lower SPs are considered a prerequisite, i.e. the actual upgrade to the target release is
considered out of scope.
© 2012 SAP AG. All rights reserved. 4
The implementation process consists of the following steps:
1. Qualification of implementation projects
2. Refinement of scope on business process level
3. Definition of implementation scope on building block level
4. Analysis of implementation scope on configuration task level
5. Automated conflict check based on installation data (optional)
6. Configuration of solution package scope
© 2012 SAP AG. All rights reserved. 5
1. Qualification of Implementation Projects
Deploying rapid deployment solutions on top of existing customer business processes affects feasibility
aspects, implementation effort (and related cost), implementation methodology and the deployment
procedure. Therefore it is crucial to qualify such implementation projects at a very early stage.
Use the accelerator Qualification Questionnaire (tab Qualification Questionnaire L1, Section 2 Existing
SAP CRM Solution) to check whether the scope of the solution package may cause conflicts with the
existing customer system landscape, customer-specific development and configuration (for example
master data or business processes).
Based on the answers of the Qualification Questionnaire the project can be qualified
– standard implementation approach is applicable
– approach for implementation on top of existing business processes has to be applied
– the SAP CRM rapid-deployment solution is not a fit for this customer
Customer implementation project is qualified against the solution package„ scope and methodology
© 2012 SAP AG. All rights reserved. 6
2. Refinement of Scope on Business Process Level
The planned scope of the rapid-deployment project of SAP CRM needs to be refined considering the
existing customer implementation on business process level.
To identify whether scope items are already implemented by the customer use the solution package„s
documentation like scope item descriptions and business process documentation.
After having identified this overlap on this rather high level verify your finding against the mapping matrix
available via the asset Qualification Questionnaire (tab L2 CRMRDS on top CRM Enterprise) to get a
first indicator of the feasibility.
This matrix provides an indicator for each scope item whether it can be deployed in case of already
implemented business content (divided into the categories “Possible combination”, “To be verified” and
In addition scope items may require existing configuration, e.g. business processes or master data,
because they are defined as functional enhancements or as preceding or following business processes.
In this case the feasibility of scope item deployment has to be checked by using integration prerequisites
described in the solution and scope item documentation (Scope Document, Scoping Questionnaire).
Describe the feasible scope items to be implemented in the customer specific Scope Document.
The scope of the solution package to be implemented has been finalized and documented.
Already implemented scope items have been identified.
© 2012 SAP AG. All rights reserved. 7
3. Definition of Implementation Scope on Building Block
The configuration content of a scope item is defined by the related Building Blocks which contain the
dedicated, detailed configuration (customizing) tasks.
In case of already implemented business processes the related Building Blocks have to classified
according to their potential conflicts with existing system configuration.
Use the accelerator Detailed Configuration Analysis (tab Analysis – Building Block Level) to determine
the Building Blocks to be examined before the deployment of the selected scope items.
– Note: this asset is currently only tailored for CRM Standalone scope, i.e. not specifically adressing aspects of
deployments with ERP integration.
Maintain the Deployment Status (Not in scope, In scope, Implemented) of the business processes.
The Deployment Status is automatically inherited from the assigned Building Blocks.
– Assumption: already implemented customer-specific business processes have a similar configuration as the business
processes which are part of the SAP CRM rapid-deployment solution
© 2012 SAP AG. All rights reserved. 8
3. Definition of Implementation Scope on Configuration
Building Block Level -2
Based on the Deployment Status the line Building Blocks to be analyzed indicates which Building Blocks
may cause conflicts or post-processing steps during configuration.
– Building Block is in scope and has been implemented (customer-specific)
Detailed analysis required regarding completeness and deviations from Building Block content
– Building Block is in scope and has not been implemented
Rough analysis required because Building Block content to be implemented can have
dependencies to other existing configuration
– Buildling Block is not in scope and has been implemented (customer-specific)
No analysis is required. Assumption: Customer-specific configuration will not be modified but only
– Building Block is not in scope and has not been implemented
No analysis is required
For all Building Blocks to be analyzed check and maintain the Implementation Status (Not relevant, To
be implemented, Implemented) and the Analysis Status (Not relevant, To be analyzed, Analysis
completed) on Building Block level on tab Analysis – Task Level.
Consider the Building Block Descriptions linked to the Building Blocks (line Building Blocks with Building
Block Descriptions) and navigate to the Building Block details on tab Analysis – Task level using line
Building Blocks with Link to Task Level Analysis.
The Building Blocks have been categorized regarding implementation status and relevance for detailed
© 2012 SAP AG. All rights reserved. 9
4. Analysis of Implementation Scope on Configuration
For all relevant Building Blocks a detailed analysis of configuration content conflicts and rework needs to be executed.
This analysis serves as preparation for the subsequent configuration.
In order to run the detailed analysis the existing customer-specific configuration has to be available for comparision, i.e.
system landscape containing the productive business processes and related documentation.
Use the accelerator Detailed Configuration Analysis (tab Analysis – Task Level).
Set the filter in column Critical Tasks to ‚X„ to get a working list of all tasks requiring a detailed analysis regarding conflict
and rework across all Building Blocks.
In addition the column Main Topics can be used as additional filter to focus on the most relevant configuration topics.
For all Building Blocks with Analysis Status To be analyzed check the Critical Tasks and follow the guidance provided in
the column Proposed Action.
– Depending on the task the range of actions can be e.g. a simple check whether a single configuration parameter value exists to complex
configuration checks, e.g. related to the organizational model.
In order to run the analysis on configuration task level consider the configuration guides of the related Building Blocks.
Maintain the result of the analysis on task level in columns Implementation Status and Action Result, e.g. required
adaptation of configuration settings to be implemented.
The configuration content has been analyzed on task level and prepared for implementation.
© 2012 SAP AG. All rights reserved. 10
5. Automated Conflict Check Based on Installation Data
The analysis of configuration conflicts as suggested by step 4 can be automated by using the SAP Best
Practices Solution Builder „procedure framework‟.
This is an optional step in case there is a project-based decision to use Solution Builder even when
implementing the SAP CRM rapid-deployment solution on top of existing SAP CRM business processes.
The Solution Builder and related configuration content (solution, installation data) has to be available in
the system landscape containing the customer-specific business processes. Refer to the Quick Guide for
In the Solution Builder run the procedure Find Conflicts.
Solution Builder – Solution Editor: Solutions -> Procedures
The procedure compares the configuration parameter values to be implemented (installation data) with
the existing values to identify key conflicts.
For all parameter value sets with identical keys in existing configuration and installation data differences
are reported on field level.
Solution Builder – Solution Editor: Goto -> Change Management -> Data Changes
This information can now be used as basis for conflict detection and resolution.
Maintain the results in the accelerator Detailed Configuration Analysis (tab Analysis – Task Level).
Conflicts for configuration parameter values have been identified.
© 2012 SAP AG. All rights reserved. 11
6. Configuration of Solution Package Scope
Based on the detailed analysis of configuration content on configuration task level configure the selected
scope of the SAP CRM rapid-deployment solution.
Use the accelerator Detailed Configuration Analysis (tab Analysis – Building Block Level).
For each of the business processes in scope identify the Building Blocks with Deployment Status In
For each of the relevant Building Blocks manually execute the task of the Building Block listed in
Detailed Configuration Analysis (tab Analysis – Task Level) by using the related configuration guide.
Activate tasks depending on implementation status and action result.
– Implemented: Skip
– To be implemented: Activate
– Conflict detected: Resolve conflict including all dependencies
– Post-processing: Skip and post process after initial implementation
The selected scope of the SAP CRM rapid-deployment solution has been implemented considering
existing business processes.
© 2012 SAP AG. All rights reserved. 12
© 2012 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, PowerPoint, Silverlight, and Visual Studio are
registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power
Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,
pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,
Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
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.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App
World are trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,
Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,
Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are
trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, 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.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of
Crossgate AG in Germany and other countries. Crossgate is an SAP company.
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.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.