SAP Best Practices for SAP S/4HANA (on premise) (V3): Software and Delivery Requirements

Transcription

1 SAP Best Practices S4HANAX October 2016 English SAP Best (on premise) (V3): Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee Walldorf Germany

2 SAP Best 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. The information contained herein may be changed without prior notice. 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 and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see for additional trademark information and notices. SAP SE Public Page 2 of 13

3 SAP Best 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 13

4 SAP Best Table of Contents Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software product versions for 1610 FPS Software product versions for 1610 FPS Software product versions for 1610 FPS SAP Notes SAP Solution Manager Active Business Functions Required System Landscape Connectivity Authorizations SAP SE Public Page 4 of 13

5 SAP Best 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 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 please refer to the Administration Guide for OP Solution Implementation ( 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, SAP Fiori Remote access is in place for SAP consultants and SAP Active Global Support Decision made whether SAP Best Practices Solution Builder will be used to activate content (recommended). 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. 3.1 Software product versions for 1610 FPS00 The following software products and versions are required: SAP SE Public Page 5 of 13

6 SAP Best SAP NW FOR S4HANA ON- PREMISE NW FOR S4HANA ON- PREMISE SBOP ANALYSIS MS OFFICE Version 1610 FP stack 00 NW 7.51 FOR OP 1610 SPS00 NW 7.51 FOR OP 1610 SBOP ANALYSIS MS OFFICE 2.1 Version Instance SAP Server Application Server ABAP Adobe Document Services Analysis Office Client 2.1 Co mp one nts as test ed XL S Add on Solution Manager Logical Component S4HANAOP_Suite_Ser ver Comments Mandatory Relevance All scope items. None Mandatory All scope items. Mandatory All scope items. None Optional All ERP planning scope items (BEA, BEU, BEX) The SAP Fiori apps require an SAP Gateway System as a frontend system. This can be either the embedded Gateway System or the hub solution (the used Gateway system is a different system as the backend system). Recommendation The decision to choose the hub solution or use the embedded Gateway system depends on the use case on customer site. Find background information on pros and cons for each option on help.sap.com. In any case, this decision should be discussed for each customer individually with the assigned system architects. SAP FIORI FRONT- END SERVER SAP FIORI FOR SAP Version SAP FIORI FRONT-END SERVER 3.0 SAP FIORI FOR 1610 Version Instance SAP Frontend Server7.50 or SAP Frontend Server7.51 UI for SAP Compo nents as tested UIS4HO P1 200 UIAPFI Solution Manager Logical Compone nt Comments Relevance None Mandatory All scope items None Mandatory All scope items SAP SE Public Page 6 of 13

7 SAP Best SAP FIORI FOR SAP SAP FIORI FOR SAP SAP NETWEAV ER Version SAP FIORI FOR 1610 SAP FIORI FOR 1610 SAP NETWEAVER 7.5 Version Instance UI for Approve Requests Backend for Approve Requests SAP Web Dispatcher Compo nents as tested UIX01C A1 200 SAP IW PGW 100 Solution Manager Logical Compone nt Comments Relevance None Mandatory All scope items None Mandatory All scope items None Mandatory All scope items 3.2 Software product versions for 1610 FPS01 Detailed information will be provided before release date. 3.3 Software product versions for 1610 FPS02 Detailed information will be provided before release date. 3.4 SAP Notes The following SAP Notes need to be considered for specific countries: SAP Note No Content Comments Relevance SAP Best (Germany) (V3) SAP Best (U.S.A) (V3) SAP Best (Canada) (V3) SAP Best of SAP Best package Germany of SAP Best package USA of SAP Best package Canada of SAP Best package Australia SAP SE Public Page 7 of 13

8 SAP Best SAP Note No Content Comments Relevance (Australia) (V3) SAP Best (Great Britain) (V3) SAP Best (Netherlands) (V3) SAP Best (Hungary) (V3) SAP Best (Singapore) (V3) SAP Best (Belgium) (V3) SAP Best (China) (V3) SAP Best (Philippines) (V3) SAP Best (France) (V3) SAP Best of SAP Best package Great Britain of SAP Best package Netherlands of SAP Best package Hungary of SAP Best package Singapore of SAP Best package Belgium of SAP Best package China of SAP Best package Philippines of SAP Best package France of SAP Best SAP SE Public Page 8 of 13

9 SAP Best SAP Note No Content Comments Relevance (Switzerland) (V3) SAP Best (Japan) (V3) package Switzerland of SAP Best package Japan The following SAP Notes need to be considered for all countries: SAP Note No Content Comments Relevance , onpremise edition 1610 on the activation of Generic information collective note for content activation SAP Best Practices for content Setup Integrated Business Planning for Finance Configuration steps for Analytics Before you start the activation of the related SAP Best Practices scope, check the latest versions of this SAP Note and execute all steps as documented in this note. This note provides additional information about the configuration for Analytics in S/4 HANA On-Premise Edition. This note is only required if you want to use one of the following scope items BEA - Revenue Planning, BEX - General Cost Center Planning, BEU - Internal Order Planning. all FPSs 3.5 SAP Solution Manager For the implementation of the solution package, SAP Solution Manager is recommended. SAP Best Practices content is available for SAP Solution Manager 7.2. Follow the detailed instructions in SAP Solution Manager 7.2 on how to proceed. 3.6 Active Business Functions Required Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated: After installing ON-PREMISE, but before activating the SAP Best Practices for package, activate the following SAP Business Functions. The activation of Enterprise Extensions, Business Functions, and Business Function Sets changes your system and cannot be rolled back. For more SAP SE Public Page 9 of 13

10 SAP Best information about the impact, check the documentation of the related extension or business function. Ensure that you have activated all Business Functions as outlined below before you create the client in which the SAP Best (on premise) package shall be activated. Do NOT activate additional Enterprise Extensions or Business Functions (in addition to the required BF mentioned for SAP BP deployment) before content activation. This can result in errors during activation of SAP Best Practices content. Additional Business Functions can still be activated at any time after content activation of course this will then require regression testing of business process as it is usually part of any system maintenance activities. Business Function FIN_FSCM_CLM Configuration or Data required Relevance items J77, J78 (Building Blocks BFD, BFE, BFF, BFP). An additional license is necessary. all FPSs FIN_FSCM_BNK items J78 (Building Block J83, BF4). An additional license is necessary. all FPSs BSESH_HANA_SEARCH Required for BB MAA / all FPSs BSCBN_HANA_NAV Required for BB MAA / all FPSs FIN_REP_SIMPL_2 Required for BB MAL / all FPSs FIN_REP_SIMPL_3 Required for BB MAL / all FPSs FIN_REP_SIMPL_4 Required for BB MAL / all FPSs FIN_LOC_SRF item 1J2 (Building Block BRS). An additional license is necessary. all FPSs / 1J2 is only relevant for specific countries SAP SE Public Page 10 of 13

11 SAP Best Business Function LOG_EAM_SIMPLICITY Configuration or Data required Relevance items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_2 items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_3 items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_4 items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_5 items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_6 items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). 3.7 System Landscape The Front-End Server (SAP Gateway) connects to the ABAP Back-End Server (i.e. ) and other SAP Business Suite Server. The clients requests are routed via the SAP Web Dispatcher. Find more details on the architecture in the configuration guide SAP S4HANA Fiori Foundation Configuration (MAA). When creating Adobe Forms (e.g. PDF Documents) out of an SAP system, the rendering is done by Adobe Document Services. The system landscape diagram shows the relevant component. SAP SE Public Page 11 of 13

12 SAP Best 3.8 Connectivity This section gives an overview of the required RFC destinations that have been created and used for this package. RFC Destination Description Connection Type <system id >CLNT<Client> <system id >CLNT<Client> RFC Destination to SAP Server RFC Destination to SAP Gateway Server Created in Building Block 3 SAP S4HANA Fiori Foundation Configuration 3 SAP S4HANA Fiori Foundation Configuration Logon Data UserID UserID Comment For more details, see chapter Gateway System: Creating Trusted RFC in NetWeaver Gateway to SAP Business Suite For more details, see chapter Defining Trust between SAP Business Suite and SAP NetWeaver Gateway SAP SE Public Page 12 of 13

13 SAP Best RFC Destination Description Connection Type Created in Building Block Logon Data Comment <system id >CLNT<Client> RFC Destination to SAP Server H SAP S4HANA other app Types Deployment UserID Creating an HTTP RFC Destination to Back-End Server Note You can check the RFC destinations using transaction SM Authorizations For required authorizations please check the respective sections in the Administration Guide for SAP OP Solution Implementation ( SAP SE Public Page 13 of 13