SAP HANA Customer Engagement Intelligence rapid-deployment solution: Software and Delivery Requirements

Transcription

1 1.1, powered by HANA November 2014 English HANA rapid-deployment solution: Software and Delivery Requirements SE Dietmar-Hopp-Allee Walldorf Germany

2 Copyright 2014 SE or an 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 SE or an affiliate company. and other products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SE (or an affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SE or an affiliate company for informational purposes only, without representation or warranty of any kind, and SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SE or 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, 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 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 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. SE Public Page 2 of 13

3 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 EXAMPLE TEXT Example text Emphasized words or phrases in body text, titles of graphics and tables. 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. 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 <Example text> Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SE Public Page 3 of 13

4 Table of Contents Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software product versions Mandatory Software Product Versions Optional Software Product Versions Notes Required Content System Landscape Connectivity Authorizations SE Public Page 4 of 13

5 1 Purpose of the Document This document contains all information to: Validate that key prerequisites such as software components and versions match the customer situation Check that all prerequisites for a customer implementation are in place Check that correct content, tools and skills are in place before the project starts The document will list different kinds of requirements on package level if they are valid for all Scope Items included in the package. For requirements valid for certain scope items only, these scope items are mentioned. The document contains pre-requisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the Quick Guide. 2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start. Prerequisite Kick off and workshop dates, location and attendees agreed team allocated with correct skills and training in place Project sponsors and stakeholder identified Hardware fully commissioned Software licenses in place Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports User interfaces agreed e.g. GUI, NetWeaver Business Client or Portal Remote access is in place for consultants and Active Global Support Decision made whether pre-assembled delivery will be used Decision made whether Best Practices Solution Builder will be used to activate content. Decision made whether Solution Manager will be used. Solution Manager set up with any relevant templates. Tool for project repository and collaboration agreed Test management tool agreed Responsibility 3 Technical Requirements This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided. SE Public Page 5 of 13

6 Regarding deployment options of, refer to the installation guide that you can find here: Installation and Upgrade Information Installation Guide. 3.1 Software product versions The following software products and versions are required to implement HANA rapid-deployment solution Mandatory Software Product Versions Product Product Version Components as tested Comments Relevance (Scope Item) CUSTOMER ENGAG INTELL 1.1 (SP04) _CUAN 110 SP04 _BS_FND 747 SP05 IW_FNDGC 100 SP01 MDG_FND 747 SP03 WEBCUIF 747 SP05 _UI 740 SP09 To be installed on NetWeaver 7.40 SP07; can be installed in existing BW client or in separate client. All Scope Items NetWeaver NETWEAVE R 7.4 (SP07) _BASIS 740 SP07 _ABA 740 SP07 _GWFND 740 SP07 _BASIS: Web Dispatcher is required for scope item CM1. All Scope Items HANA Enterprise HANA Enterprise 1.0 SPS08 You must install HANA CLIENT and HANA STUDIO. All Scope Items Refer to the product availability matrix for more details, for example on operating system: ( search for HANA Platform) Landscape Transformation Replication Server 2.0 LT REPLICATI ON SERVER 2.0 DMIS 2011_1_731 SP07 LT is used to replicate data from the ERP and CRM back-end systems. It is optional if you use the Hub- Deployment with Shared All Scope Items SE Public Page 6 of 13

7 HANA System options. ERP SD (Sales and Distribution) For data replication via LT: EHP1 FOR ERP 6.0 (or higher) For hubdeployment with shared HANA system: EHP6 for ERP 6.0 on HANA (or higher) Relevant ERP objects are sales orders, sales quotations, sales contracts, billing documents, financials accounts receivables. Optionally, ERP CO-PA line items can be used to enrich the data used in Value Margin Decomposition. Mandatory back-end system for Value ; optional back-end system for the other scope items. CRM For data replication via LT: EHP1 FOR CRM 7.0 (or higher) For hubdeployment with shared HANA system: EHP2 for CRM 7.0 on HANA (or higher) Relevant CRM objects are: Activities, leads, opportunities, CRM sales orders. Mandatory back-end system for the Integration into Sales and Marketing scope item; optional back-end system for the other scope items. For deployment on same AS ABAP: EHP3 FOR CRM 7.0 SP04 (or higher) Fiori for Fiori for 1.0 SP02 UICUAN 100 SP02 This component should be installed in the Fiori frontend Gateway system. Fiori Apps for and SE Public Page 7 of 13

8 Marketing HANA Rules Framework HANA rules framework 1.0 HANA RULES FRAMEWORK 1.0 Predictive Segmentatio n (CE5) Solution Manager Solution Manager 7.0 Enhanceme nt Package 1 For Solution Manager 7.0: If the SP is below 24, see Note All Scope Items SP18 or higher or Solution Manager 7.1 SP01 or higher or Solution Manager 7.1 on HANA (ST 712) SP00 or higher Optional Software Product Versions In addition to the standard application content, the rapid-deployment solution provides: BusinessObjects reports and dashboards, built using queries of the application. A sample Lumira report build based on an existing HANA view. These reports are an optional component of the rapid-deployment solution, which can be used to enrich the Value ( BusinessObjects content) and the Social Contact ( Lumira content) solutions. Product Product Version Components as tested Comments Relevance (Scope Item) BusinessObj ects Business SBOP BI PLATFORM 4.1 SP3 Web Analysis edition for OLAP Translation Management Tool Both server and client installation are mandatory. Value SE Public Page 8 of 13

9 platform BusinessObj ects Dashboards SBOP DASHBOARD S 4.1 SP3 Not applicable Mandatory for 360 dashboard configuration. Value Adobe Flash Player Adobe Flash Player 10.1 or higher Not applicable Mandatory. If the BusinessObjects reports cannot be displayed with the Flash Player version you have installed, upgrade to the most recent version. Value Lumira LUMIRA 1.0 SP17 Not applicable Mandatory for display and configuration of sample report Contact Analysis. Social Contact 3.2 Notes The following Notes need to be considered: Note No Content Comments Relevance Rapid deployment of HANA Release Information Note (RIN) Release Information Note (RIN) Fiori for Installation/Upgrade SLT - DMIS 2011 SP7 This Note contains critical information for implementing the HANA rapid-deployment solution. Implement all Notes listed in this RIN. Implement all Notes listed in this RIN if you want to implement Fiori for Relevant if you use Landscape Transformation All Scope Items All Scope Items Fiori Apps for (CEF); Marketing (CM1) All Scope Items SE Public Page 9 of 13

10 Replication Server How many work processes should be configured? Audience Discovery and Targeting (CE2) 3.3 Required Content If you want to make use of the additional dashboards and reports delivered for the HANA rapid-deployment solution, the following content is required: Product Product Version Comments Relevance Rapid- Deployment Solution BIP Content RDS BIP CONTE NT V2 The _HANA_CEI_RDS.lcmbiar included in the RDS BIP Content contains the additional dashboards and reports. Value Lumira report RDS BIP CONTE NT V2 The Contact Analysis.lums file included in the RDS BIP Content contains a sample Lumira report. Social Contact 3.4 System Landscape There are several deployment options for. Before installing the product, decide for the deployment option best suited to your requirements. You can find a detailed overview of available deployment options in the installation guide that you can find here: Installation and Upgrade Information Installation Guide. The following diagram displays a system landscape for the case that is deployed on a separate HANA database and connects to ERP and/or CRM via Landscape Transformation Replication Server: SE Public Page 10 of 13

11 3.5 Connectivity Source Systems This rapid-deployment solution uses ERP and/or CRM as source system(s). You can deploy on a separate HANA database (refer to figure 1) or on the same HANA database as an existing CRM or ERP system (refer to figure 2). Loading source system data that is not from an source requires additional setup. For more information, refer to the rapid data load HANA applications solution. Staging and Data Layer To access the ERP and CRM data, you have two options: a) You replicate the relevant ERP data and/or CRM data via Landscape Transformation Replication Server into the HANA database. b) If you share the same HANA database with either CRM or ERP, the data from the respective system does not need to be replicated to via LT. Only if you want to access data from both CRM and ERP, you would have to replicate the data from that system which does not share the same HANA database via LT. is installed on an NetWeaver 7.40 system with an HANA database. Semantic Layer (Optional) SE Public Page 11 of 13

12 Additional predefined BusinessObjects content delivered via the HANA rapid-deployment solution requires that BusinessObjects Business platform and BusinessObjects Explorer are implemented and configured for these additional, optional dashboards. To make use of the sample Lumira report that is delivered as part of the rapid-deployment solution, Lumira has to be installed first. 3.6 Authorizations The following authorizations are required for the business user (as described in the Basic Settings for (CEB) building block): _CEI_BI_AUTH _CEI_HOME _CEI_TG_INI _CEI_CVI _CEI_ADT _CEI_SCI _CEI_PBA _CEI_KUA _CUSTOMER_ANALYTICS_ADMIN _BC_WEBSERVICE_ADMIN_TEC _CEI_CUAN_MK_TG_REL_APP _CEI_MED _CEI_MEM _CEI_ADT_FLP _CEI_CVI_FLP _CEI_SCI_FLP _CEI_TG_INI_FLP _CEI_KUA_FLP _CEI_PBA_FLP _CEI_B2C_RECO_FLP _UI2_ADMIN_700 _ UI2_USER_700 _CEI_TCR_T _CEI_BCR_MARKETINGMANAGER _CEI_BCR_MARKETINGEXPERT _CEI_BCR_MARKETINGEXECUTIVE The following authorizations are required for the installation user (as described in the HANA Content Activation for (CEB) building block): _BC_BASIS_ADMIN _BC_DB_ADMIN _BC_SIW_DEV SE Public Page 12 of 13

13 _BC_CTS_ADMIN _BC_CUS_ADMIN _BC_DWB_ABAPDEVELOPER _BC_STC_USER _BC_WEBSERVICE_DEBUGGER _BC_WEBSERVICE_ADMIN_TEC _ESH_CR_ADMIN _BC_BGRFC_SUPERVISOR SE Public Page 13 of 13