S4HANAX
November 2015
English
SAP Best Practices
S/4HANA on premise
edition (USA) (USV1):
Software and Delivery
Requirements
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Rapid Deployment Solutions
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 11
SAP Rapid Deployment Solutions
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 11
SAP Rapid Deployment Solutions
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................................................................................................... 5
3.2
SAP Notes ........................................................................................................................... 5
3.3
SAP Solution Manager and SAP Solution Manager Content Add-On ................................ 8
3.4
Active Business Functions Required .................................................................................. 9
3.5
System Landscape <optional> ............................................ Error! Bookmark not defined.
3.6
Connectivity ......................................................................... Error! Bookmark not defined.
3.7
Authorizations ..................................................................... Error! Bookmark not defined.
© SAP SE
Public
Page 4 of 11
SAP Rapid Deployment Solutions
Software and Delivery Requirements
1 Purpose of the Document
This document contains all information to:
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/). You can also access this Guide
by calling the transaction /FTI/SET_IMPL_PHASE directly in your system
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
The following software products and versions are required:
Product
© SAP SE
Product
Product
Comp
Solution Manager
Public
Comments
Relevance
Page 5 of 11
SAP Rapid Deployment Solutions
Version
SAP
S/4HANA
ONPREMISE
SAP
NETWEAV
ER
SAP
BusinessO
bjects
Analysis,
edition for
Microsoft
Office
SAP S/4HANA
ON-PREMISE
1511
SPS 0
SAP
NETWEAVER
7.5
Version
Instanc
e
SAP
S/4HAN
A Server
Software and Delivery Requirements
onent
s as
tested
Applicati
on
Server
ABAP
SAP
BusinessObject
s Analysis,
edition for
Microsoft Office
2.1 SP2
XLS
Addon
Logical Component
S4HANAOP_Suite_Ser
ver
Mandatory
All scope items.
S4HANAOP_Suite_Ser
ver
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.
Product
NETWEAV
ER FOR
S4HANA
ONPREMI
SE
SAP FIORI
FRONTEND
SERVER
SAP FIORI
FOR SAP
S/4HANA
SAP FIORI
FOR SAP
S/4HANA
SAP FIORI
FOR SAP
© SAP SE
Product
Version
NW 7.5 FOR
S4HANA OP
1511
SAP FIORI
FRONT-END
SERVER 2.0
SAP FIORI FOR
SAP S/4HANA
1511
SAP FIORI FOR
SAP S/4HANA
1511
SAP FIORI FOR
SAP S/4HANA
1511
Product
Version
Instanc
e
Basis
Apps
Comp
onent
s as
tested
Solution Manager
Logical Component
Comments
Relevance
None
Mandatory
All scope items
frontend
server
cfg :
NW7.50
UI for
S4COR
E
None
Mandatory
All scope items
None
Mandatory
All scope items
UI for
Approve
Request
s
Backend
for
Approve
None
Mandatory
All scope items
None
Mandatory
All scope items
Public
Page 6 of 11
SAP Rapid Deployment Solutions
Product
Product
Version
S/4HANA
SAP FIORI
FOR SAP
S/4HANA
SAP FIORI
FOR SAP
S/4HANA
SAP FIORI
FOR SAP
ERP
SAP
ANALYTIC
S
FOUNDATI
ON
SAP
NETWEAV
ER
SAP FIORI FOR
SAP S/4HANA
1511
Product
Version
Instanc
e
Request
s
UI for
FIN
Software and Delivery Requirements
Comp
onent
s as
tested
Solution Manager
Logical Component
Comments
Relevance
None
Mandatory
All scope items
SAP FIORI FOR
SAP S/4HANA
1511
UI for
HCM
None
Mandatory
All scope items
UI FOR EHP7
FOR SAP ERP
6.0
UI for
Insuranc
e
NW740
Fronten
d
Analy.F
ND NW
7.4
None
Mandatory
All scope items
None
Mandatory
All scope items
SAP
Web
Dispatch
er
None
Mandatory
All scope items
SAP
ANALYTICS
FOUNDATION
1.0
SAP
NETWEAVER
7.5
3.2 SAP Notes
The following SAP Notes need to be considered:
SAP Note No
2226371
2231568
1972819
2219726
© SAP SE
Content
Comments
Relevance
SAP S/4HANA content
activation note
Generic information
on the activation of
SAP Best Practices
for S/4HANA content
Information on the
activation of SAP Best
Practices for
S/4HANA, on premise
edition Germany
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
For setting up the
system landscape to
All Scope Items
SAP Best Practices for
S/4HANA, on premise
edition (U.S.A) (USV1)
Setup Integrated
Business Planning for
Finance
General Information:
FIORI UI Infrastructure
Public
All Scope Items
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.
Page 7 of 11
SAP Rapid Deployment Solutions
SAP Note No
2219727
Software and Delivery Requirements
Content
Comments
Relevance
Components SAP
S/4HANA Enterprise
Management solution
Q4/2015
run SAP Fiori apps,
this notes states the
relevant prerequisites
and fixes User
Interface Technology
for SAP NetWeaver
7.5.
General Information:
FIORI SAP Gateway for
SAP S/4HANA
Enterprise Management
solution 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.
All Scope Items
3.3 SAP Solution Manager and SAP Solution Manager
Content Add-On
For the implementation of the solution package, SAP Solution Manager is recommended.
Product
SAP Solution Manager
Product Version
Comments
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 rapid-deployment 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:
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
© SAP SE
BP_OPEP_S4HANAX_USV1 - S/4HANA, On premise edition 1511 US V1
Public
Page 8 of 11
SAP Rapid Deployment Solutions
Software and Delivery Requirements
and Template
Name
Solution
Package
Name(s)
S/4HANA, On premise edition 1511 US V1
3.4 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 S/4HANA, on premise edition, 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 S/4HANA, on
premise edition shall be activated.
Do NOT activate additional Enterprise Extensions or Business Functions even if
you do not plan to use them. This can result in serious errors during activation of
SAP Best Practices. Activate ONLY the Business Functions listed below.
Product
S/4HANA
S/4HANA
S/4HANA
S/4HANA
S/4HANA
Business Function
Configuration or Data
required
Relevance
FIN_FSCM_CLM
Required for scope
items J77, J78, J60
(Building Blocks J73,
J74, J75, J76).
An additional license is
necessary.
FIN_FSCM_BNK
Required for scope
items J78, J60
(Building Blocks J83).
An additional license is
necessary.
FIN_REP_SIMPL_2
Required for BB MAL
FIN_REP_SIMPL_3
Required for BB MAL
FIN_REP_SIMPL_4
Required for BB MAL
3.5 System Landscape
The Front-End Server (SAP Gateway) connects to the ABAP Back-End Server (i.e. SAP S/4 HANA)
and other SAP Business Suite Server. The clients requests are routed via the SAP Web Dispatcher.
© SAP SE
Public
Page 9 of 11
SAP Rapid Deployment Solutions
Software and Delivery Requirements
Find more details on the architecture in the configuration guide ‘SAP S4HANA Fiori Foundation
Configuration (MAA)’.
3.6 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/4
HANA 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’
© SAP SE
Public
Page 10 of 11
SAP Rapid Deployment Solutions
Software and Delivery Requirements
RFC Destination
Description
Connection
Type
Created in
Building Block
Logon Data
Comment
<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’
<system id
>CLNT<Client>
RFC
Destination
to SAP S/4
HANA 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.7 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/). You can also access this Guide
by calling the transaction /FTI/SET_IMPL_PHASE directly in your system
© SAP SE
Public
Page 11 of 11
