software and delivery requirements - sap service …sapidp/... · s/4hana: software and delivery...
TRANSCRIPT
SAP Best Practices for analytics with SAP S/4HANA
March 2016
English
SAP Best Practices for Analytics with SAP S/4HANA: Software and Delivery Requirements
SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany
Document Revisions Date
0
1
2
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 2 of 12
Copyright
© 2016 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 Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 3 of 12
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.
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 4 of 12
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 ........................................................................................................................... 6
3.3 Software Landscape Diagram ............................................................................................. 6
3.3.1 BGH: Embedded Analytics with SAP S/4HANA ............................................................. 7
3.3.2 BGA: Integration Between SAP S/4HANA and SAP BI .................................................. 8
3.3.3 BGB: Integration Between SAP S/4HANA and SAP BW ............................................... 8
3.4 Connectivity ....................................................................................................................... 12
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 5 of 12
1 Purpose of the Document This document contains 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 (Example: 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 Responsibility
Kick off and workshop dates, location and attendees agreed Customer
Customer team allocated with correct skills and training in place Customer
Project sponsors and stakeholder identified Customer
Hardware fully commissioned Customer
Software licenses in place Customer
Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports
Customer
User interfaces agreed e.g. SAPGUI, Netweaver Business Client or Portal
Customer
Remote access is in place for SAP consultants and SAP Active Global Support
Customer
Decision made whether pre-assembled delivery will be used Customer
Decision made whether SAP Best Practices Solution Builder will be used to activate content.
Customer
Decision made whether Solution Manager will be used. Solution Manager set up with any relevant templates.
Customer
Tool for project repository and collaboration agreed Customer
Test management tool agreed Customer
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 Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 6 of 12
3.1 Software Product Versions The following software products and versions are required:
Product Product Version Components Comments Relevance
SAP S/4HANA ON-PREMISE 1511 SP1
SAP S/4HANA ON-PREMISE 1511 SP1
Mandatory. All Scope Items
SAP BusinessObjects BI Platform
SBOP BI PLATFORM 4.2
Web Intelligence
Mandatory BGA
SAP Design Studio
SBOP DESIGN STUDIO 1.6
Mandatory BGA
SAP Crystal Reports for Enterprise
SBOP BI PLATFORM 4.2 CLIENT TOOLS
Mandatory BGA
SAP NETWEAVER
SAP NETWEAVER 7.4, SP13 or above
SAP_ABA 740 SP 13 SAP_BW 740 SP 13 BI_CONT 757 SP 08 or above BP-BW 740V2 or above
Mandatory BGB
SAP HANA PLATFORM EDITION
SAP HANA, platform
edit. 1.0 (latest SP,
latest revision)
Optional BGB
SAP HANA Live for SAP ERP
SAP HANA Live for SAP ERP 1.0, latest support package
Optional BGB
3.2 SAP Notes The following SAP Notes need to be considered:
SAP Note No
Content Comments Relevance
2271853
This SAP Note contains critical information for implementing the SAP Best Practices for analytics with SAP S/4HANA.
Before you start the implement of the related SAP Best Practices scope, check the latest versions of this SAP Note.
All Scope Items
3.3 Software Landscape Diagram For each scope item, system landscape diagram are provided accordingly.
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 7 of 12
3.3.1 BGH: Embedded Analytics with SAP S/4HANA Below chart describes the embedded analytics in S/4 HANA:
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 8 of 12
3.3.2 BGA: Integration Between SAP S/4HANA and SAP BI This diagram is an abstract view of the system landscape for Scope Item BGA, to explain where work is done in an implementation project. It is not a specification that describes all the technical details of a real system landscape.
3.3.3 BGB: Integration Between SAP S/4HANA and SAP BW For integration between SAP S/4 HANA and SAP BW, there are different scenarios. Below 5 scenarios are also covered in detail in configuration guide BGD.
1. Integration of S/4HANA and BW when S/4HANA and BW in different DBs
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 9 of 12
2. Integration of S/4HANA in BW when BW embedded in S/4HANA
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 10 of 12
3. BW and S/4 HANA and HANA Live deployed across different HANA instances
4. HANA Live and BW in the same HANA DB
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 11 of 12
5. S/4HANA and BW in the same HDB with separate standalone BW
SAP Rapid Deployment Solutions Software and Delivery Requirements
© SAP SE Public Page 12 of 12
3.4 Connectivity The following connectivity is required:
1. Connection from SAP BOBJ BI Platform to SAP S/4 HANA On-Premise system.
The connections from SAP BOBJ BI Platform to SAP S/4 HANA system need to be updated after deployment of the reports. Please refer to corresponding configuration guide for more information. Please refer to http://service.sap.com/analyticswiths4h
2. Connection from SAP BW to SAP S/4 HANA On-Premise system.
The connections from SAP BW to SAP S/4 HANA system are needed, please check Configuration Guide BGD for details. Please refer to http://service.sap.com/analyticswiths4h as well.