Software and Delivery Requirements

SAP HANA Activity Repository rapiddeployment solution V2.10 April 2015 English SAP HANA Activity Repository rapiddeployment solution: Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Copyright 2015 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 or an SAP affiliate company. 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 http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark 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. SAP SE Public Page 2 of 10

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. SAP SE Public Page 3 of 10

Table of Contents Contents 1 Purpose of the Document... 5 2 General Project Prerequisites... 5 3 Technical Requirements... 5 3.1 Software Product Versions... 6 3.2 SAP Notes... 7 3.3 SAP Solution Manager and SAP Solution Manager Content Add-On... 8 3.4 Connectivity... 9 3.5 Authorizations... 9 SAP SE Public Page 4 of 10

1 Purpose of the Document This document contains all information to: Validate that key prerequisites such as software products 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 lists 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 configuration guides. 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. SAPGUI, Netweaver Business Client or Portal Remote access is in place for SAP consultants and SAP Active Global Support Decision made whether pre-assembled delivery will be used Decision made whether SAP 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. SAP SE Public Page 5 of 10

3.1 Software Product Versions The following software products and versions are required: Product CAR RETAIL APPLICATIONS BUNDLE Product Version Components Comments CAR RETAIL APPL BUNDLE 1.0 SP01 RTLCAR 200 RTLCONS 100 RTLDDF 200 RTLPOSDM 300 RTLPROMO 810 RTLRAP 100 POSAFL_INST 100 UDFAFL_INST 100 SAP NetWeaver SAP NetWeaver Server 7.40 SP09 SAP NetWeaver Application ABAP SAP HANA SAP HANA platform Ed 1.0 SPS09 SAP HANA Enterprise Ed 1.0 SPS09 SAP HANA Server SAP HANA Client SAP HANA Studio SAP HANA ANALYTICS For ERP SAP HANA ANALYTICS FOR ERP 1.0 SP09 SLT: Check note 1605140 to get exact DMIS component version according to ERP version and SAP HANA version SAP Landscape Transformation SAP Landscape Transformation 2 SP08 DMIS 2011_1_731 Refer to the SAP HANA Enterprise 1.0 Installation Guide: Installing Trigger- Based Replication on the SAP Service Marketplace at http://service.sap.com/hana SAP ERP EHP6 SPS07 FOR SAP ERP 6.0 or higher ERP Application Server ABAP As the prerequisite SAP CRM EHP2 SPS07 FOR SAP CRM 7.0 or higher CRM Application Server ABAP As the prerequisite SAP Fiori for SAP CARAB SAP Fiori for SAP CARAB 1.0 UISCAR01 100 SAP Analytics Foundation SAP Analytics Foundation 1.0 SPS02 HANA CONTENT HBA AF CORE 100 HANA CONTENT HBA AF EXT 100 HANA CONTENT HBA AF CXO 100 HANA CONTENT SAP SE Public Page 6 of 10

HBA APF CORE 100 SAP LUMIRA SERVER SAP HANA Studio SAP HANA Client SAP LUMIRA SERVER 1 SAP HANA Studio 2 Revision 91 or higher SAP HANA Client 1.00 Revision 91 or higher SAP LUMIRA SERVER 1.21 or higher UNIVERSAL ANALYTICS AFL 1.300 or higher Software Client Software Client SAP Lumira SAP Lumira 1.22 Software Client 3.2 SAP Notes The following SAP Notes need to be considered: SAP Note No 2092380 Content Comments Relevance SAP HANA Activity Repository rapid-deployment solution v2.10 SV-RDS-CAR It s the solution note for SAP HANA Activity Repository rapid-deployment solution 2088924 RIN SAP Activity Repository retail applications bundle 1.0 2116084 Upgrade of SAP Activity Repository retail applications bundle 1.0 SPS01 2125672 SQL exception: Could not derive table type for variable UDF_FC_HORIZON 2114264 HANA Content corrections for SAP Activity Repository 2.0 2098632 UI Features/Corrections Sales Analytics Reuse Library 2099830 UI Features/Corrections Sales Analytics - Net Sales CA-RT CA-DDF-RT-UDF CA-DDF-RT-UDF General Info Upgrade Info SAP SE Public Page 7 of 10

2099672 UI Features/Corrections Sales Analytics - Gross Margin 2099675 UI Features/Corrections Sales Analytics Number of Transactions 2099911 UI Features/Corrections Sales Analytics - Average Transaction Value 2099912 UI Features/Corrections Sales Analytics - Items per Transaction 3.3 SAP Solution Manager and SAP Solution Manager Content Add-On For the implementation of the solution package, SAP Solution Manager is recommended. Product Product Version SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1 SP18 or higher Or SAP Solution Manager 7.1 SP01 or higher Or SAP Solution Manager 7.1 on HANA (ST 712) SP00 or higher Comments If using SAP Solution Manager 7.0 with SP below 24, see SAP Note 1579267. For SAP rapid-deployment solutions, implementation content is available in SAP Solution Manager templates. The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at service.sap.com/swdc. For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note 1726649 and SAP Note 1686668 respectively. In the ST-RDS 100 content add-on, access the template in the following way: SAP SE Public Page 8 of 10

If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below. If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package name(s) in the table below. Template ID and Template Name Solution Package Name(s) RDS_RTL_CAR_CAR10V2- SAP HANA Activity Repository RDS_V2 SAP HANA Activity Repository RDS_V2 3.4 Connectivity The following connectivity is required: Describe the connections between systems that are needed, if applicable. 3.5 Authorizations The following authorizations are required: Purpose User ID User Type Building Block Config. Guide Initial Password Authorization Profile Comment SAP SE Public Page 9 of 10

Purpose User ID User Type Building Block Config. Guide Initial Password Authorization Profile Comment Activation User User ID is defined by your system administrator Dialog (Type A) Creation described in Quick Guide Password is defined by your system administrator SAP_ALL For more details, see section above: Creating User for Activation of SAP Best Practices Content SAP HANA User User ID is defined by your system administrator System user Password is defined by your system administrator Authorization is defined by your system administrator You can check the users in transaction SU01 SAP SE Public Page 10 of 10