SAP Business Intelligence Adoption V6.41: Software and Delivery Requirements. SAP Business Intelligence Adoption February 2015 English

Transcription

1 Business Intelligence Adoption February 2015 English Business Intelligence Adoption V6.41: Software and Delivery Requirements AG Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date 0 11/11/14 1 2

2 Copyright 2015 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 15

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 15

4 Table of Contents Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software Product Versions Software Product Versions for ERP Core via Business Warehouse, Track Analytics Data, ERP Operational Data Provisioning Software Product Versions for CRM Analytics Software Product Versions for Trade Promotion Effectiveness Notes System Landscape Solution for ERP Core via Business Warehouse, Track Analytics Data, ERP Operational Data Provisioning Solution for BW (without HANA) Solution for BW (BW and HANA mixed) Solution for BW on HANA Solution for BI within CRM Analytics Solution for BI within Trade Promotion Effectiveness Analytics How to scope your software Requirement SE Public Page 4 of 15

5 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. 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 15

6 3.1 Software Product Versions The following software products and versions are required: The table lists all software required to implement the whole scope of this solution. should adopt the applicable software according to their actual landscape and business scope. This rapid deployment solution delivered the following scope items: Business Intelligence Analytics for ERP Core via Business Warehouse (Purchasing, Manufacturing, Sales, Finance, HCM, Executive Analytics) B05 B07 B49 B53 B55 D02 CEO Executive Analytics Sales Analytics Financial Analytics Purchasing Analytics Manufacturing Analytics Human Capital Management Analytics Track Analytics Data in Business Warehouse BY4 BY5 BY6 Data Reconciliation for BW Data Availability for BW Data Lineage for BW Business Intelligence Analytics with ERP Operational Data Provisioning BY7 BY8 BY9 Finance Operational Analytics with ODP Sales Operational Analytics with ODP Purchasing Operational Analytics with ODP Business Intelligence Analytics for CRM CR3 CR4 CR5 CR6 VB6 CRM Marketing Analysis CRM ERP Integrated Sales Analysis CRM Standalone Sales Analysis CRM Service Analysis CRM Sales Analysis for BI Platform Business Intelligence Analytics for Trade Promotion Effectiveness (Industry specific) EA7 Account Pre/Post Evaluation EA8 EA9 Promotion Pre/Post Evaluation Funds Analysis Very Important: Don t use solution manager to implement this RDS. Solution manager is not required to implement this RDS Although this RDS also released solution manager content as well, please don t use solution manager template for implementation. In our solution manager template, we just define the reference link to each configuration guide word document. We didn't deliver any automatically deployment content in solution manager template. To implement this RDS, Please refer to note and follow all the manual configuration steps SE Public Page 6 of 15

7 3.1.1 Software Product Versions for ERP Core via Business Warehouse, Track Analytics Data, ERP Operational Data Provisioning Product Product Version Components Comments Necessary in Scope Item ERP EHP6 FOR ERP 6.0 ERP 6.06 Application Server ABAP _APPL 606 SP11 _BW 731 BI CONT 747 SP10 If you use ERP Operational Reporting on ODP scenario, you have to use EHP6. If you don t use BI reporting on ODP, it is not necessary to upgrade into EHP6, the following components are not necessary as well: _BW 731 SP11 Required by B05 B07 B49 B53 B55 D02 BY4 BY5 BY6 BY7 BY8 BY9 BI CONT 747 SP10 NETWEAVER EHP1 For NETWEAVER 7.3, _BASIS 731 _ABA 731 PI_BASIS 731 _BW 731 BI_CONT 747 SP10 NETWEAVER 7.4, SP05 is also supported: _BASIS 740 SP08 _ABA 740 SP08 PI_BASIS 740 SP08 _BW 740 SP08 BI_CONT 747 SP08 or above BP-BW 731V7 Required by B05 B07 B49 B53 B55 D02 BY4 BY5 BY6 BP-BW 731V7 Trigger-Based Replication Using LT LT Replication Server Not applicable Check note to get exact DMIS component version according to ERP version and HANA version Only necessary for some reports built upon BW on HANA or HANA in B05,B07,B49,B53 Refer to the HANA Enterprise 1.0 Installation Guide: Installing Trigger- Based Replication on the Service Marketplace at HANA EDITION HANA EDITION 1.0 SPS09 or above HANA DATABASE Only necessary for some reports built upon BW on HANA or HANA in B05,B07,B49,B53, B55 SBOP BI SBOP BI 4.1 SP05 or above Required by B05 B07 B49 B53 B55 D02 BY4 BY5 BY6 BY7 BY8 BY9 SBOP EXPLORER SBOP EXPLORER Required by B49 B07 SE Public Page 7 of 15

8 4.1 SP05 Client Reporting Tools: Product Product Version Component Comments SBOP DESIGN STUDIO SBOP DESIGN STUDIO 1.4 or later DESIGN STUDIO BIP ADD ON 1.4 or later DESIGN STUDIO CLIENT 1.4 or later DESIGN STUDIO BIP ADD ON is installed with SBOP BI SBOP DASHBOARDS SBOP DASHBOARDS 4.1 SP05 Not applicable Crystal Reports for Enterprise Crystal Reports for Enterprise 4.1SP05 Not applicable LUMIRA LUMIRA 1.0 SP19 or higher Not applicable Please choose the client tools according to your selected report scope Optional Software: (You need to install in case of mobile support for BI reports) Product Product Version Component Comments IOS (Optional) 5.0 or above Not applicable BusinessObjects Mobile for ipad (Optional) BusinessObjects Experience for iphone/ipad (Optional) or above Not applicable or above Not applicable Software Product Versions for CRM Analytics Product Product Version Components Comments Necessary in Scope Item ERP EHP6 FOR ERP 6.0 SP11 ERP 6.06 Application Server ABAP Required by CR4 CR6 _APPL 606 SP11 _BW 731 SP11 BI CONT 747 SP08 SE Public Page 8 of 15

9 NETWEAVER EHP1 For NETWEAVER 7.3, _BASIS 731 _ABA 731 PI_BASIS 731 _BW 731 BI_CONT 747 SP10 BP-BW 731V7 NETWEAVER 7.4, SP05 is also supported: _BASIS 740 SP08 _ABA 740 SP08 PI_BASIS 740 SP08 _BW 740 SP08 BI_CONT 747 SP08 or above BP-BW 731V7 Required by CR3 CR4 CR5 CR6 VB6 SBOP BI SBOP BI 4.1 SP05 VB6 CRM EHP1 FOR CRM 7.0 or above CRM Application Server ABAP CR3 CR4 CR5 CR6 VB6 NETWEAVER EHP1 For NETWEAVER 7.3, BI Java CR3 CR4 CR5 CR6 Client Reporting Tools: Product Product Version Component Comments SBOP DASHBOARDS SBOP DASHBOARDS 4.1 SP05 Not applicable Software Product Versions for Trade Promotion Effectiveness Product Product Version Components Comments CRM EHP1 for CRM 7.0 SP07 or above CRM Application Server ABAP/CRM Application Server Java/WebClient UI Trade Promotion Management functionality must be implemented TRADE PROMOTION PLNG TRADE PROMOTION PLNG 2.0 or above CRM Add-on This is an optional product for this solution. NETWEAVER EHP1 For NETWEAVER 7.3, _BASIS 731 _ABA 731 SE Public Page 9 of 15

10 HANA EDITION ERP SBOP BI SBOP DESIGN STUDIO HANA EDITION 1.0 SPS09 or above EHP5 for ERP 6.0 SP08 or above SBOP BI 4.1 SP05 SBOP DESIGN STUDIO 1.4 or later PI_BASIS 731 _BW 731 BI_CONT 747 SP10 BP-BW 731V7 HANA DATABASE ERP ABAP Server: Central Application/ABAP Technology for ERP EHP5/Financial Services (COPA) /Sales (SD) Central Management Console Lifecycle management console 3.2 Notes The following Notes need to be considered: Note No Content Comments Relevance This Note contains critical information for implementing Business Intelligence Adoption Rapid Deployment Solution, which are the basis for the system preconfiguration related to Business Intelligence Adoption Rapid Deployment Solution The texts of variables are not displayed in Variable Screen during query execution. The technical names of the variables are presented. The texts of structure members (formulas) are Before you start the activation of the related Best Practices scope, check the latest versions of this Note. If you are using BW 7.31 SP06 or SP07 All Scope Items All Scope Items SE Public Page 10 of 15

11 not displayed in query results When you execute a query and call the varaible screen the currency results are displayed as '*'. This happens in 730 and 731 When you execute a query on an InfoCube, an exception occurs due to the use of a key figure that cannot be aggregated (aggregation type = "no aggregation"). The query can be executed in a similar way using a BW query, the RSDRI read interface or using transaction LISTCUBE. In all three cases, the error may occur. If you are using BW on HANA. All Scope Items All Scope Items 4 System Landscape 4.1 Solution for ERP Core via Business Warehouse, Track Analytics Data, ERP Operational Data Provisioning To deploy BI on BW of this package, the applicable scope depends on customer s landscape. As for those s who installed BW already, here is the transition road map to BW on HANA: SE Public Page 11 of 15

12 4.1.1 Solution for BW (without HANA) (Applicable for B05 B07 B49 B53 B55 D02 BY4 BY5 BY6 BY7 BY8 BY9 VB6. VB6 requires CRM source system to replace above ERP ) SE Public Page 12 of 15

13 4.1.2 Solution for BW (BW and HANA mixed) (Applicable for B05 B07 B49 B53 B55 D02 BY4 BY5 BY6 BY7 BY8 BY9 VB6 with more reports. VB6 requires CRM source system to replace above ERP) Solution for BW on HANA SE Public Page 13 of 15

14 (Applicable for B05 B07 B49 B53 B55 D02 BY4 BY5 BY6 BY7 BY8 BY9 VB6 with more reports. VB6 requires CRM source system to replace above ERP) 4.2 Solution for BI within CRM Analytics (Applicable for CR3 CR4 CR5 CR6. ERP is not necessary for CR3 CR5) SE Public Page 14 of 15

15 4.3 Solution for BI within Trade Promotion Effectiveness Analytics 4.4 How to scope your software Requirement should adopt the applicable scope according to their actual landscape and business scope. (1) To pick up applicable Server product and software components, please refer to customer s Landscape according to BW Migration (none HANA/ Partial Migration / BW on HANA) (2) To pick up client reporting tools, please do the scoping with the file RDS \ RDS_BIA_BOA41V6_Technical_Object_Mapping_EN_XX.xls a. Filter the Landscape according to BW Migration (none HANA/ Partial Migration / BW on HANA) b. Filter the Scope items (3) Mobile support is optional. In case it is necessary to run BI report on Mobile, please install the Mobile software products SE Public Page 15 of 15