SAP Best Practices S4HANAX October 2016 English SAP Best Practices for SAP S/4HANA (on premise) (V3): Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee 16 69190 Walldorf Germany SAP Best Practices for SAP S/4HANA (on premise) Software and Delivery Requirements 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 http://www.sap.com/corporateen/legal/copyright/index.epx#trademark for additional trademark information and notices. © SAP SE Public Page 2 of 13 SAP Best Practices for SAP S/4HANA (on premise) Software and Delivery Requirements 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 SE Public Page 3 of 13 SAP Best Practices for SAP S/4HANA (on premise) Software and Delivery Requirements Table of Contents Contents 1 Purpose of the Document.............................................................................................................. 5 2 General Project Prerequisites ....................................................................................................... 5 3 Technical Requirements................................................................................................................ 5 3.1 Software product versions for 1610 FPS00 ........................................................................ 5 3.2 Software product versions for 1610 FPS01 ........................................................................ 7 3.3 Software product versions for 1610 FPS02 ........................................................................ 7 3.4 SAP Notes ........................................................................................................................... 7 3.5 SAP Solution Manager ........................................................................................................ 9 3.6 Active Business Functions Required .................................................................................. 9 3.7 System Landscape............................................................................................................ 11 3.8 Connectivity ....................................................................................................................... 12 3.9 Authorizations ................................................................................................................... 13 © SAP SE Public Page 4 of 13 SAP Best Practices for SAP S/4HANA (on premise) Software and Delivery Requirements 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 SAP S/4HANA OP Solution Implementation (http://service.sap.com/~sapidp/012002523100012419282015E/). 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, SAP Fiori Customer Remote access is in place for SAP consultants and SAP Active Global Support Customer Decision made whether SAP Best Practices Solution Builder will be used to activate content (recommended). 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. 3.1 Software product versions for 1610 FPS00 The following software products and versions are required: © SAP SE Public Page 5 of 13 SAP Best Practices for SAP S/4HANA (on premise) Product SAP S/4HANA NW FOR S4HANA ONPREMISE NW FOR S4HANA ONPREMISE SBOP ANALYSIS MS OFFICE Product Version Product Version Instance SAP S/4HANA 1610 FP stack 00 NW 7.51 FOR S/4HANA OP 1610 SPS00 SAP S/4HANA Server Application Server ABAP NW 7.51 FOR S/4HANA OP 1610 Adobe Document Services SBOP ANALYSIS MS OFFICE 2.1 Analysis Office Client 2.1 Software and Delivery Requirements Co mp one nts as test ed XL S Add on Solution Manager Logical Component Comments Relevance S4HANAOP_Suite_Ser ver Mandatory All scope items. None Mandatory All scope items. Mandatory All scope items. Optional All ERP planning scope items (BEA, BEU, BEX) None 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. Product SAP FIORI FRONTEND SERVER SAP FIORI FOR SAP S/4HANA © SAP SE Product Version Product Version Instance SAP FIORI FRONT-END SERVER 3.0 SAP Frontend Server7.50 SAP FIORI FOR SAP S/4HANA 1610 or SAP Frontend Server7.51 UI for SAP S/4HANA Compo nents as tested UIS4HO P1 200 Solution Manager Logical Compone nt None Comments Relevance Mandatory All scope items None Mandatory All scope items UIAPFI7 0 400 Public Page 6 of 13 SAP Best Practices for SAP S/4HANA (on premise) Product SAP FIORI FOR SAP S/4HANA SAP FIORI FOR SAP S/4HANA SAP NETWEAV ER Software and Delivery Requirements Product Version Product Version Instance Compo nents as tested SAP FIORI FOR SAP S/4HANA 1610 UI for Approve Requests UIX01C A1 200 SAP FIORI FOR SAP S/4HANA 1610 Backend for Approve Requests SAP IW PGW 100 SAP NETWEAVER 7.5 SAP Web Dispatcher Solution Manager Logical Compone nt None Comments Relevance 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 2315744 2330455 Content Comments Relevance SAP Best Practices for SAP S/4HANA (on premise) (Germany) (V3) SAP Best Practices for SAP S/4HANA (on premise) (U.S.A) (V3) Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Germany All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package USA All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Canada All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Australia All Scope Items / all FPSs 2342316 SAP Best Practices for SAP S/4HANA (on premise) (Canada) (V3) 2342305 SAP Best Practices for SAP S/4HANA © SAP SE Public Page 7 of 13 SAP Best Practices for SAP S/4HANA (on premise) SAP Note No Content Software and Delivery Requirements Comments Relevance Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Great Britain All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Netherlands All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Hungary All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Singapore All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Belgium All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package China All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Philippines All Scope Items / all FPSs Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package France All Scope Items / all FPSs Information on the activation of SAP Best Practices for All Scope Items / all FPSs (on premise) (Australia) (V3) 2342286 SAP Best Practices for SAP S/4HANA (on premise) (Great Britain) (V3) 2342277 SAP Best Practices for SAP S/4HANA (on premise) (Netherlands) (V3) 2342278 SAP Best Practices for SAP S/4HANA (on premise) (Hungary) (V3) 2342296 SAP Best Practices for SAP S/4HANA (on premise) (Singapore) (V3) 2342298 SAP Best Practices for SAP S/4HANA (on premise) (Belgium) (V3) 2342299 SAP Best Practices for SAP S/4HANA (on premise) (China) (V3) 2342300 SAP Best Practices for SAP S/4HANA (on premise) (Philippines) (V3) 2342330 SAP Best Practices for SAP S/4HANA (on premise) (France) (V3) 2342362 SAP Best Practices for SAP S/4HANA © SAP SE Public Page 8 of 13 SAP Best Practices for SAP S/4HANA (on premise) SAP Note No 2342364 Software and Delivery Requirements Content Comments (on premise) (Switzerland) (V3) SAP S/4HANA (on premise) package Switzerland SAP Best Practices for SAP S/4HANA (on premise) (Japan) (V3) Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Japan Relevance All Scope Items / all FPSs The following SAP Notes need to be considered for all countries: SAP Note No 2328518 1972819 2289865 Content Comments Relevance SAP S/4HANA, onpremise edition 1610 collective note for content activation Setup Integrated Business Planning for Finance Generic information on the activation of SAP Best Practices for S/4HANA content 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. All Scope Items / all FPSs Configuration steps for S/4HANA Analytics 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 This note provides additional information about the configuration for Analytics in S/4 HANA On-Premise Edition. 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 SAP S/4HANA ON-PREMISE, but before activating the SAP Best Practices for SAP S/4HANA (on premise) 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 SAP Best Practices for SAP S/4HANA (on premise) Software and Delivery Requirements 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 Practices for SAP S/4HANA (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”. Product S4CORE S4CORE S4CORE S4CORE S4CORE S4CORE S4CORE S4CORE © SAP SE Business Function Configuration or Data required Relevance FIN_FSCM_CLM Required for scope items J77, J78 (Building Blocks BFD, BFE, BFF, BFP). An additional license is necessary. all FPSs FIN_FSCM_BNK Required for scope 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 Required for scope item 1J2 (Building Block BRS). An additional license is necessary. all FPSs / 1J2 is only relevant for specific countries Public Page 10 of 13 SAP Best Practices for SAP S/4HANA (on premise) Product S4CORE S4CORE S4CORE S4CORE S4CORE S4CORE Software and Delivery Requirements Business Function Configuration or Data required Relevance LOG_EAM_SIMPLICITY Required for scope items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_2 Required for scope items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_3 Required for scope items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_4 Required for scope items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_5 Required for scope items BH1, BH2, BJ2 (Building Blocks BFI, BFJ, BFM, BFN). LOG_EAM_SIMPLICITY_6 Required for scope 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. SAP S/4HANA) 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 SAP Best Practices for SAP S/4HANA (on premise) Software and Delivery Requirements 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 Created in Building Block Logon Data Comment <system id >CLNT<Client> RFC Destination to SAP S/4HANA Server 3 SAP S4HANA Fiori Foundation Configuration UserID For more details, see chapter ‘Gateway System: Creating Trusted RFC in NetWeaver Gateway to SAP Business Suite’ <system id >CLNT<Client> RFC Destination to SAP Gateway Server 3 SAP S4HANA Fiori Foundation Configuration UserID For more details, see chapter ‘Defining Trust between SAP Business Suite and SAP NetWeaver Gateway’ © SAP SE Public Page 12 of 13 SAP Best Practices for SAP S/4HANA (on premise) Software and Delivery Requirements RFC Destination Description Connection Type Created in Building Block Logon Data Comment <system id >CLNT<Client> RFC Destination to SAP S/4HANA 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 SM59. 3.9 Authorizations For required authorizations please check the respective sections in the Administration Guide for SAP S/4HANA OP Solution Implementation (http://service.sap.com/~sapidp/012002523100012419282015E/). © SAP SE Public Page 13 of 13