EHP3 for SAP CRM 7.0
April 2014
EnglishEnglish
Document Version 1.2
APOSoftware Requirements
SAP CRM rapid-deployment solution (V6.703)
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany

© SAP SEPage 1 of 21

SAP CRM rapid-deployment solution (V6.703)Software Requirements

Copyright

© 2014 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Icons

Icon / Meaning
/ Caution
/ Example
/ Note
/ Recommendation
/ Syntax
/ External Process
/ Business Process Alternative/Decision Choice

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.

Content

1Purpose

2Required Product Versions and Software Components

2.1Important Release and Support Package Level Information

2.2General Software Requirements

2.3Software Requirements specific to Desktop Connection for SAP CRM

2.4Software Requirements specific to SAP HANA

2.5SAP Solution Manager and SAP Solution Manager Content Add-on

3Integration Points

4Required Business Functions

5More Information

5.1Figure of System Landscape

5.2Hardware Sizing

1Purpose

This document lists all software required to implement and run the solution.

If the SAP CRM rapid-deployment solution V6.703 is implemented following the pre-assembled deployment approach, this document rather serves as a reference (as opposed to a requirements) document, listing the software which is already part of the pre-assembled system.

Refer to SAP Note 1992121 for current information on availability of SAP CRM software appliances (pre-assembled rapid-deployment solutions) and more details.

2Required Product Versions and Software Components

2.1Important Release and Support Package Level Information

The deliverables of SAP Best Practices packages are developed and tested in a system landscape with specific release and support package stack (SPS) level, as documented below. SAP recommends to meet this SPS as minimal SPS level.

If you need a higher SPS level in your system, for example, because of additional functionality, ideally first import and activate the SAP Best Practices package on the mentioned SPS level, then update your system to the target SPS level. If SAP Best Practices content is activated directly on a higher SPS level (for example, if the recommended SPS level is not available anymore),some automated activation steps might fail, however still can be processed manually following the related configuration guide. Also note that some of the SAP Notes which are considered relevant for the scope of the solution package might be obsolete due to a higher SPS level, and additional SAP Notes could exist.

For delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog or download from the SAP Software Download Center (SWDC) on SAP Service Marketplace (SMP). You can only order unrestricted SAP software.

2.2General Software Requirements

The following table lists the software required to implement and run the solution:

SAP Product / Product Version / Component / Part of Pre-assembled System / Logical Component in SAP Solution Manager* / Comments
SAP CRM / EHP3 FOR SAP CRM 7.0 (SP03) / NW 7.40 (SP05) / BBPCRM / Yes / CRM70_EHP3_APPL_SERV_ABAP / Mandatory.
SAP GUI for Microsoft Windows / For information about supported SAP GUI releases, see SAP Note 147519. / n.a. / Yes / None / Required for system administration functions and maintaining application customizing.
SAP Best Practices Solution Builder / BP-SOLBLD 70Vx
Always use the latest available version as outlined in SAP Note 1301301. / BP-SOLBLD / Yes / None / Add-on for the implementation tool(only necessary to be implemented in a system where content activation shall be done using the Solution Builder (i.e. Sandbox or Development System).
SAP Best Practices Configuration Content
(for SAP CRM and SAP NetWeaver) / BP-CRM 713Vx
BP-CANW 740Vx
Always use the latest available versions as outlined in SAP Note 1301301. / BP-CRM
BP-CANW / Yes / None / Add-ons containing configuration content
(only necessary to be implemented in the system which is used for the initial content activation (i.e. Sandbox or Development System).
SAP ERP** / EHP7 FOR SAP ERP 6.0 (SP03) - central applications / SAP_APPL / No / ERP60_EHP7_CENTRAL_APPLICATION / Optional, that is, not required for CRM standalone deployment.

*The logical component in SAP Solution Manager is an identifier provided by SAP for the combination of the product and product version. When selecting the SAP Solution Manager template later on, the logical component provided by SAP will automatically be mapped with the logical component in the customer system landscape with the same combination of product and product version to set up access from SAP Solution Managerto the correct customer system.

** As part of implementing the SAP CRM rapid-deployment solution, the SAP CRM system can be integrated with the customer’s existing SAP ERP system. However, it is also possible to deploy the SAP CRM rapid-deployment solution in a CRM standalone manner. In this case, the SAP ERP client is not required.

Also in case of pre-assembled deployment the ERP system is not part of the pre-assembled system, but the customer’s existing SAP ERP system needs to be integrated during the implementation project.

End users access SAP CRM via their local Web browsers. Exception: the Interaction Center Manager must access SAP GUI to generate and assign call lists for the Interaction Center Marketing(C81)scenario.

For the latest information about supported web browsers, refer to SAP’s Product Availability Matrix, which bundles technical information on SAP components for quick reference ( enter EHP3 FOR SAP CRM 7.0) and SAP Note 1876371.

If SAP Best Practices scope item CRM Interactive Reporting (CR2) is in scope: As of SAP Enhancement Package 3 for SAP CRM 7.0 CRM the user interface (UI) to display reporting data is based on HTML5, replacing the previous UI based on Adobe Flash.

Note that this technology is only supported as of the following browser versions:

  • Microsoft Internet Explorer, as of Version 9
  • Mozilla Firefox, as of version 17
  • Safari, as of version 5
  • Google Chrome

If you want to use a browser version that is not supported, do not activate business function CRM_ANA_UI5: Interactive Reporting Using UI Development Toolkit for HTML5 so that you can use the Interactive Reporting UI based on Adobe Flash. However also note that some CRM Interactive Reporting features also depend on that technology, such as embedding Interactive Reports on Home, overview and work center pages (related to business function CRM_EMBED_IR_ANA_UI: Embedded Interactive Reporting and SAP HANA Live Reporting Analytics). For details refer to the release information, e.g. via transaction /sfw5 (Switch Framework Customizing).

For scenarios in which survey and questionnaire functionality is used (such as Activity Management, Lead Management, and Opportunity Management), you have to activate the Virtual Machine Container (VMC).For more information about activating the VMC, see SAP Note 854170.In the pre-assembled system the Virtual Machine Container is activated.

The Adobe Flash plugin needs to be installed on the user’s local browser forusing the graphical segmentation modeler (scope itemLean Campaign Management). For detailed information, see SAP Note 1334838). It is also required forusing the graphical buying center feature (within scope items Account and Contact Management and Opportunity Management) and the dashboard feature in the context of the Accelerated Agent Inbox based on SAP HANA.

The Java Runtime Environment (JRE)is required for using the Interactive Scripting Editor within the business processes Interaction Center Marketing and Interaction Center Sales. JRE allows end-users to run Java applications andneeds to be installed on the user’s local PC. Use any version of Java™ Plug-In higher than 1.6.For details see SAP Note 717921.

HTTPSis prerequisite for:

  • scope item Activity Management using Desktop Connection for SAP CRM
  • dashboard functionality (Inbox Work Distribution Dashboard) within scope item Interaction Center Service Request Management(in the context of the Accelerated Agent Inbox based on SAP HANA)

The Master Guide for SAP Customer Relationship Management provides the central starting point for the technical implementation of SAP CRM. Use the Master Guide to obtain an overview of SAP CRM, its software units, and scenarios from a technical perspective. The Master Guide helps you design your SAP CRM system landscape.


The Master Guide is available via SAP Business Suite Applications SAP CRMSAP enhancement package 3 for SAP CRM 7.0Plan.

2.3Software Requirements specific to Desktop Connection for SAP CRM

Desktop Connection for SAP CRM enables you to synchronize appointments, employees, contacts, and accounts between Microsoft Outlook and SAP CRM so that you can access all relevant data that has been created in SAP CRM from Microsoft Outlook.In order to implement and run SAP Best Practices for CRM scope item Activity Management Using Desktop Connection for SAP CRM the following software components are required in addition:

SAP Product / Product Version / Component / Part of Pre-assembled System / Logical Component in SAP Solution Manager* / Comments
SAP Netweaver Gateway Foundation / SAP NW GATEWAY FOUNDATION 7.40(SP05) / SAP_GWFND / Yes / CRM70_EHP3_APPL_SERV_ABAP / As of SAP NetWeaver 7.40 (SP02) this component is part of SAP NetWeaver itself. So landscape set-up could be either way: using the Gateway component which is anyway part of SAP CRM’s NetWeaver stack or running it on a separate server. This finally also depends on performance considerations, and e.g. if customers in parallel run other scenarios that require the Gateway component as well, such as SAP JAM integration scenarios or SAP FIORI related scenarios.
SAP CRM DESKTOP INT / CRM DESKTOP CONNECTION 2.0(SP01) / CRM DESKTOP INT / Yes
(CRMGWS and CRMGWCUS; not CRMGWCON) / CRM70_EHP3_APPL_SERV_ABAP / Consists of components:
-CRMGWS (ABAB add-on to SAP CRM system
-CRMGWCUS (customization package, will be configured during implementation project)
-CRMGWCON (MS Outlook Connector; client component for Win32 and Windows on x64 64bit; required on user’s local PC).

For details refer to theAdministrator's Guideas the single and leading source of information for the implementation of the Desktop Connection for SAP CRM.This guide also documents required and supported operating systems and versions (on client), Microsoft Outlook versions (on client), Microsoft Exchange Server versions, Microsoft .NET Framework version, and Microsoft Visual C++ version.

Also note that HTTPS is prerequisite for using Desktop Connection for SAP CRM.

The most recent version of this document is available on SAP Service Marketplace at SAP Business suite Application SAP CRM Add-OnsDesktop Connection for SAP CRM.

To send e-mails from SAP CRM and receive e-mails in SAP CRM, a connection to an e-mail server is required. The mailserver needs to be connected to the SAP CRM system and all installation-related activities need to be completed prior to implementing the SAP CRM rapid-deployment solution. Setup of this mail server and the connection to the SAP CRM system is not part of the service delivery.

Also in case of implementing based on a pre-assembled system, an e-mail server on customer side is required. If the pre-assembled system resides in the Cloud a VPN-tunnel is required between the Cloud and the e-mail server.

For additional information refer to SAP Notes 1436692and 455140.

With Microsoft Office Outlook 2007, the Microsoft ‘Collaboration Data Objects’ (CDO) Library is no longer contained in the supply scope of the Microsoft Outlook installation routine, so it must be installed separately. Refer to article 171440 from the Microsoft support web site ( The CDO’s can be downloaded from the Microsoft web site, for example from here:

Starting with Microsoft Outlook 2010 the CDO‘s are no longer required.

In addition users’ browser settings must comply to the documentation in the 'Prerequisites' section for the E-Mail function in:

For details refer to SAP Note 963408.

2.4Software Requirements specific to SAP HANA

The SAP CRM rapid-deployment solution V6.703 can be deployed in a non-HANA as well as in an SAP HANA context.

Scope of the solution package which is specifically dependent on SAP HANA is of course not available in a non-HANA deployment:

•Duplicate Check / Fuzzy Search (within ‚ Account and Contact Management‘)

•Accelerated Agent Inbox (within Interaction Center business processes)

•CRM Interactive Reporting based on SAP HANA

The related configuration tasks as well as the related process implications are clearly indicated in the respective configuration guides respectively business process documentation (test scripts).

The following table lists SAP HANA related software required to take advantage of SAP HANA specific scope within the SAP CRM rapid-deployment solution:

SAP Product / Product Version / Component / Part of Pre-Assembled System / Logical Component in SAP Solution Manager / Comments
SAP HANA PLATFORM EDITION / SAP HANA, platform edit. 1.0 (SP07,latest revision) / SAP NEWDB / Yes / None / Optional.
SAP HANA ANALYTICS FOR CRM / SAP HANA ANALYTICS FOR CRM 1.0(SP05) / HCO_HBA_CRM
(HANA CONTENT HBA SAP CRM 100) / Yes / None / Optional.
SAP HANA content required for scope item CRM Interactive ReportingonSAP HANA.
SAP HANA CRM IC INBOX ACC / SAP HANA CRM IC INBOX ACC 1.0 (SP01) / HCO_CRM_IC_AUI2
(HANA CONT CRM IC INB2 100) / Yes / None / Optional.
SAP HANA content for the ‘accelerated agent inbox’ feature in SAP CRM; related to scope item Interaction Center Service Request Management.
Also refer to SAP note 1810530.
SAP HANA content for the ‘duplicate check’ feature
[content available via SAP Note, not as software component] / Yes / None / Optional.
Related to scope item Account and Contact Management.
Refer to SAP note 1858106.

For supported hardware platforms for SAP HANA refer to SAP’s product availability matrix (PAM) via and search for ‘SAP HANA’. Via the result list navigate to the PDF document “SAP Hana Enterprise-Platform 1.0 PAM”.

Installing SAP HANA Studio

SAP HANA Studio enables technical users to manage the SAP HANA database, to create and manage user authorizations, and to create new or modify existing models of data in the SAP HANA database. It is a client tool, which is used to access local or remote SAP HANA databases.

  1. Download SAP HANA Studio Installer (SAR file) from the SAP Software Download Center (SWDC) at to your local machine.
  2. Open the downloaded folder and run the HDBSETUP executable file (SAP HANA Database Installation Manager) to install and update the SAP HANA Studio.
  3. When prompted, use option Install new SAP HANA Studio to proceed with the installation.
  4. Open the SAP HANA Studio from the Microsoft Windows Start menu: Start  All Programs  SAP HANA  SAP HANA Studio.


To work in the SAP HANA database, you need to have a database user who has the privileges (SQL, Analytics) granted directly or indirectly (through roles). The available standard roles are MODELING and MONITORING for performing the basic operations on database objects and to allow read access to data.