sap best practices for sap s/4hana (on premise) (v2 ...sapidp/... · premise) (v2): software and...

SAP Best Practices

S4HANAX

May 2016

English

SAP Best Practices for SAP S/4HANA (on premise) (V2): 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

© SAP SE Public of 15

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/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.



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.



Table of Contents 1 Purpose of the Document ......................................................................................................... 5

2 General Project Prerequisites ................................................................................................... 5

3 Technical Requirements ........................................................................................................... 5

3.1 Software product versions for 1511 FPS01 (released on 03.02.16) ................................. 5

3.2 Software product versions for 1511 FPS02 (released on 12.05.16) ................................. 7

3.3 Software product versions for 1511 FPS03 (release planned on 09.11.16) ...................... 9

3.4 Software product versions for 1511 FPS04 (release planned on xx.xx.xx) ....................... 9

3.5 SAP Notes.................................................................................................................... 10

3.6 SAP Solution Manager and SAP Solution Manager Content Add-On ............................ 11

3.7 Active Business Functions Required ............................................................................. 12

3.8 System Landscape ....................................................................................................... 13

3.9 Connectivity .................................................................................................................. 14

3.10 Authorizations............................................................................................................... 15



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 1511 FPS01 (released on 03.02.16)

The following software products and versions are required:

http://service.sap.com/~sapidp/012002523100012419282015E/



Product Product Version

Product Version Instance

Components as tested

Solution Manager Logical Component

Comments Relevance

SAP S/4HANA ON-PREMISE

SAP S/4HANA ON-PREMISE 1511 SPS 01 (02/2016)

SAP S/4HANA Server

S4HANAOP_Suite_Server

Mandatory All scope items.

NW FOR S4HANA ONPREMISE

NW 7.5 FOR S4HANA OP 1511

Application Server ABAP

None Mandatory All scope items.



Adobe Document Server

Mandatory All Scope Item

SBOP ANALYSIS MS OFFICE

SBOP ANALYSIS MS OFFICE 2.1

Analysis Office Client 2.1

XLS Addon

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.





Comments Relevance

SAP FIORI FRONT-END SERVER

SAP FIORI FRONT-END SERVER 2.0

front-end server cfg : NW7.50

None Mandatory All scope items

SAP FIORI FOR SAP S/4HANA

SAP FIORI FOR SAP S/4HANA 1511

UI for S4CORE




UI for Approve Requests


http://help.sap.com/saphelp_gateway20sp09/helpdata/en/62/91ad98b19b4a91bca737fbe442273f/content.htm







Comments Relevance



Backend for Approve Requests




UI for FIN


SAP NETWEAVER

SAP NETWEAVER 7.5

SAP Web Dispatcher


If you use analytic scope items, you need BI Platform installed and configure the integration between S/4HANA and BI Platform server. Find the details in the analytical scope items (BHA, BHF, BHI). The usage of BI Platform requires the following additional and optional components.





Comments Relevance

SBOP DESIGN STUDIO

SBOP DESIGN STUDIO 1.6 SP01

Design Studio BIP Add-On

None Optional All Analytic scope items (BHA, BHF, BHI)

SBOP DESIGN STUDIO


Design Studio Client


SBOP BI PLATFORM (ENTERPRISE)

SBOP BI PLATFORM 4.2

Enterprise Servers (SMP)


3.2 Software product versions for 1511 FPS02 (released on 12.05.16)

The following software products and versions are required:







Comments Relevance

SAP S/4HANA ON-PREMISE

SAP S/4HANA ON-PREMISE 1511 SPS 02 (02/2016)

SAP S/4HANA Server

S4HANAOP_Suite_Server

Mandatory All scope items.


NW 7.5 FOR S4HANA OP 1511 SPS 02 (02/2016)

Application Server ABAP

None Mandatory All scope items.



Adobe Document Server

Mandatory All Scope Item

SBOP ANALYSIS MS OFFICE

SBOP ANALYSIS MS OFFICE 2.1

Analysis Office Client 2.1

XLS Addon

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.





Comments Relevance

SAP FIORI FRONT-END SERVER

SAP FIORI FRONT-END SERVER 2.0

front-end server cfg : NW7.50




UI for S4CORE




UI for Approve Requests


http://help.sap.com/saphelp_gateway20sp09/helpdata/en/62/91ad98b19b4a91bca737fbe442273f/content.htm







Comments Relevance



Backend for Approve Requests




UI for FIN


SAP NETWEAVER

SAP NETWEAVER 7.5

SAP Web Dispatcher


If you use analytic scope items, you need BI Platform installed and configure the integration between S/4HANA and BI Platform server. Find the details in the analytical scope items (BHA, BHF, BHI). The usage of BI Platform requires the following additional and optional components.





Comments Relevance

SBOP DESIGN STUDIO


Design Studio BIP Add-On


SBOP DESIGN STUDIO


Design Studio Client


SBOP BI PLATFORM (ENTERPRISE)

SBOP BI PLATFORM 4.2

Enterprise Servers (SMP)


3.3 Software product versions for 1511 FPS03 (release planned on 09.11.16)

Detailed information will be provided before release date.

3.4 Software product versions for 1511 FPS04 (release planned on xx.xx.xx)

Detailed information will be provided before release date.



3.5 SAP Notes The following SAP Notes need to be considered for specific countries:

SAP Note No Content Comments Relevance

2244659 SAP Best Practices for SAP S/4HANA (on premise) (Germany) (DEV2)

Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package Germany

All Scope Items / all FPSs

2247743 Information on the installation of SAP Best Practices for SAP S/4HANA (on premise) (USA) (USV2)

Information on the activation of SAP Best Practices for SAP S/4HANA (on premise) package USA


The following SAP Notes need to be considered for all countries:


2226371 SAP S/4HANA content activation note

Generic information on the activation of SAP Best Practices for S/4HANA content


1972819 Setup Integrated Business Planning for Finance

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 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

2219726 General Information: FIORI UI Infrastructure Components for SAP S/4HANA, on-premise edition 1511

For setting up the system landscape to run SAP Fiori apps, this notes states the relevant prerequisites and fixes User Interface Technology for SAP NetWeaver 7.5.


2219727 General Information: FIORI SAP Gateway for for SAP S/4HANA, on-premise edition 1511 Q4/2015

For setting up the system landscape to run SAP Fiori apps on S/4HANA Enterprise Management solution, this note states the relevant prerequisites and fixes for





SAP Gateway on the Fiori Frontend Server 7.50.

2289865 Configuration steps for S/4 HANA Analytics

This note provides additional information about the configuration for Analytics in S/4 HANA (On-Premise). The described configuration steps are necessary to enable the usage of the Analytic Engine in S/4 as well as the usage of tools like Query Designer, Query Browser, Design Studio Template (used as preview tool in Query Browser, Query Designer).

This note is only required if you want to use one of the following scope items

BHA - Analytical Content for S/4HANA: Core Finance

BHI - Analytical Content for S/4HANA: Order-to-Cash

BHF - Analytical Content for S/4HANA: Procure-to-Pay

3.6 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 Comments

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

If using SAP Solution Manager 7.0 with SP below 24, see SAP Note 1579267.

For SAP Best Practices 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 https://support.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:

http://service.sap.com/sap/support/notes/1579267


https://support.sap.com/swdc






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

DE: BP_OPEP_S4HANAX_DEV2 - SAP Best Practices for SAP S/4HANA, on-premise edition DE V2

US: BP_OPEP_S4HANAX_USV2 - SAP Best Practices for SAP S/4HANA, on-premise edition US V2

Solution Package Name(s)

DE: SAP Best Practices for SAP S/4HANA, on-premise edition DE V2

US: SAP Best Practices for SAP S/4HANA, on-premise edition US V2

Please note that the Solution Manager Content is based on the Best Practices Content delivered with FPS01.

3.7 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 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 Business Function Configuration or Data

required Relevance

S/4HANA FIN_FSCM_CLM Required for scope

items J77, J78, J60 (Building Blocks BFD, BFE, J75, J76). An additional license is necessary. all FPSs



Product Business Function Configuration or Data

required Relevance

S/4HANA FIN_FSCM_BNK Required for scope

items J78, J60 (Building Blocks J83). An additional license is necessary. all FPSs

S4CORE BSESH_HANA_SEARCH Required for BB MAA /

all FPSs

S4CORE BSCBN_HANA_NAV Required for BB MAA /

all FPSs

S/4HANA FIN_REP_SIMPL_2 Required for BB MAL /

all FPSs


all FPSs


all FPSs

S/4HANA BSESH_HANA_SEARCH Required for BB MAA /

all FPSs

S/4HANA BSCBN_HANA_NAV Required for BB MAA /

all FPSs

3.8 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)’.

If you use analytic scope items (optional), you need Business Intelligence Platform installed. Find the details in the analytical scope items (BHA, BHF, BHI).

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.



3.9 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’


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’


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.10 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/).

http://service.sap.com/~sapidp/012002523100012419282015E/