Software and Delivery Requirements

SAP Best Practices for user experience in SAP S/4HANA
04 April 2016
EnglishEnglish
SAP Best Practices for user experience in SAP S/4HANA: APOSoftware and Delivery Requirements
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Document Revisions / Date
0 / 04-04-2016
1
2

SAP Best PracticesSoftware and Delivery Requirements

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 SEin Germany and other countries. Please see 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

Contents

1Purpose of the Document

2General Project Prerequisites

3Technical Requirements

3.1Software Product Versions

3.2Browser Requirements

3.3SAP Notes

3.4SAP Solution Manager and SAP Solution Manager Content Add-On

3.5Active Business Functions

3.6Software Landscape Diagram

3.7Connectivity

3.8Roles and Authorizations

1Purpose 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 (e.g. how to find the download area) please refer to the configuration guides.

2General Project Prerequisites

The following prerequisites need to be in place before an implementation project can start.

Prerequisite / Responsibility
Kick off and workshopdates, location and attendees agreed / Customer
Customer team allocated with correct skills and training in place / Customer
Project sponsors and stakeholder identified / Customer
Hardwarefully 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

3Technical Requirements

This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided.

3.1Software Product Versions

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.

The following software products and versions are required:

Note

A download link to the respective software component to SAP Software Download Center is provided in column ‘Product Version Instance/Link to Software Download Center’ in the table below.

When you install any of the following product versions, ensure that you apply the most up-to-date support pack.

Product / Product Version / Product Version Instance/Link to Software Download Center / Comments / Relevance
SAP FIORI FRONT-END SERVER / SAP FIORI FRONT-END SERVER 2.0 / front-end server: NW7.50:

SAP NW GATEWAY FOUNDATION 7.50
USER INTERFACE TECHNOLOGY 7.50

(Choose ‘Entry by Component’ in Software Download Center) / Mandatory / All Scope Items
SAP NETWEAVER / SAP NETWEAVER 7.5 / SAP Web Dispatcher / Mandatory / All Scope Items
SAP FIORI FOR SAP S/4HANA / SAP FIORI FOR SAP S/4HANA 1511 / UI for S4CORE (UIS4HOP1 100)
(Choose ‘Installation’ in Software Download Center) / Mandatory / All Scope Items
SAP FIORI FRONT-END SERVER / SAP FIORI FRONT-END SERVER 2.0 / front-end server: NW7.50:

SAPUIFT 100

(Choose ‘Entry by Component’ in Software Download Center) / Optional: required for the usage of the App Activation Tool / SAP S4HANA Fiori Apps Deployment (MDA)
SAP FIORI FOR SAP S/4HANA / SAP FIORI FOR SAP S/4HANA 1511 /

UIX01CA1 200
IW_PGW 100

(Choose ‘Installation’ in Software Download Center) / Optional: only required for generic workflow app ‘my Inbox’ / SAP S4HANA Fiori Apps Deployment (MDA)
SAP FIORI FOR SAP S/4HANA / SAP FIORI FOR SAP S/4HANA 1511 /

UIAPFI70 300

(Choose ‘Installation’ in Software Download Center) / Optional: Only for financial processes / SAP S4HANA Fiori Apps Deployment (MDA)
SAP Single Sign-On / SAP Single Sign-On 2.0 /

Secure Login Library 2.0
Secure Login Client 2.0
IDM Federation 7.2

(Choose ‘Comprised Software Component Versions’ in Software Download Center) / Single Sign-On with SAML2.0 requires the SAP Identity Federation. Federation software is needed to make the AS JAVA as the Identity Provider. / SAP S4HANA Fiori Advanced Security Setup (MDE)
- / - / SSO Extension Library 2.0
(Choose ‘Comprised Software Component Versions’ in Software Download Center) / This is a validation tool to verify if the SAP Logon Ticket is correctly produced. / SAP S4HANA Fiori Advanced Security Setup (MDE)
SAP CLOUD CONNECTOR / SAP CLOUD CONNECTOR
latest version / SAP Cloud Connector / The SAP Cloud Connector is required to connect your On Premise SAP Front End Server with the SAP HANA Cloud Platform. / SAP S4HANA Fiori App Extensibility and Customization (MDG)
Mobilizing SAP S4HANA Apps (MDM)
SAP SCREEN PERSONAS / SAP SCREEN PERSONAS 3.0 / Screen Personas for NW
(Choose ‘Installation’ in Software Download Center) / Needs to be installed on the S/4 HANA System / Using SAP Screen Personas in SAP S/4HANA (UP6)

The table above holds the most relevant UI Add-Ons as optional components. Depending on the scope of the project additional UI Add-Ons may be required. The following section explains how to find the required app specific software requirements.

Note

The following sections explain in detail how to find the required Software Components using the Fiori Apps Reference Library. The whole installation process can be eased up using the SAP Maintenance Planner. The Maintenance Planner helps you to plan your installation and easily generate and download a consolidated stack.xml. Find detailed information here: Simplified Installation of SAP Fiori Apps with Maintenance Planner.

You can derive the required Software Components using the SAP Fiori apps reference library.

The following 2 examples explain the usage of the SAP Fiori apps reference library:

Example 1:

Figure out which Software Component Versions need to be installed to deploy the app ILM Monitoring of Archiving Jobs:

Open the reference library using this link: SAP Fiori apps reference library
ChooseCategory 'All Apps'
Enter ILM Monitoring of Archiving,choose the magnifier glass and select the app in the result list

Note

Make sure in the drop down ‘SAP S/4HANA, on-premise edition’ is selected. In case you cannot choose ‘SAP S/4HANA, on-premise edition’ the selected is app is not available in the context of S/4 HANA on-premise.

Choose Implementation Information
Extract the Installation Section on the right detail pane
Derive the required Software Components:
Front End Server (SAP Gateway):
Product Version: SAP Fiori for SAP S/4HANA 1511
Software Component Version: UIILM001 100
Back End Server (S/4 HANA System):
Product Version: SAP S/4HANA ON-PREMISE 1511
Software Component Version: SAP_BASIS 750 SP01
Result:
Front End Server: Installation of UIILM001 100
Backend Server: Make sure the system is on SP01 for SAP_BASIS component.

Example 2

Figure out which Software Component Versions need to be installed to deploy the app My Leave Requests (Version 2):

Open the reference library using this link: SAP Fiori apps reference library
ChooseCategory 'All Apps'
Enter leave,choose the magnifier glass and select the app in the result list.

Note

Choose Implementation Information.
Extract the Installation Section on the right detail pane.
Derive the required Software Components:
Front End Server (SAP Gateway):
Product Version: SAP Fiori for SAP S/4HANA 1511
Software Component Version: UIHR001 100
Back End Server (S/4 HANA System):
Product Version: SAP S/4HANA ON-PREMISE 1511
Software Component Version: GBX01HR 600
Result:
Front End Server: Installation of UIHR001 100
Backend Server: Installation of GBX01HR 600

3.2Browser Requirements

This section is in continuous change due to the fast changes in browser business. Check SAP Note 1935915 for the current requirements. For a more detailed view on general or technical release information, see the Product Availability Matrix (

3.3SAP Notes

The following general SAP Notes need to be considered:

SAP Note No / Content / Comments / Relevance
2277636 / SAP Best Practices for UX in SAP S/4HANA V1 / Before you start the activation of the related SAP Best Practices, check the latest versions of this SAP Note. / All Scope Items
2219726 / General Information: FIORI UI Infrastructure Components for SAP S/4HANA, on-premise edition 1511 / All Scope Items
2219727 / General Information: FIORI SAP Gateway for for SAP S/4HANA, on-premise edition 1511 Q4/2015 / All Scope Items
2240690 / Front-end Network Bandwidth Sizing for SAP Fiori Apps / All Scope Items

The following notes need to be implemented in the system:

SAP Note No / Content / Comments / Relevance
2269272 / "Reference Lost" Error for FLP Tiles after applying new UI component version / Relevant after update to SP01 UIS4HOP1 / All Scope Items
2243529 / Corrections to back-end catalog replication for UI add-on 2.0 SP01 / Relevant after update to SP01 UIS4HOP1 / All Scope Items
2256680 / Replication of Backend Catalogs: System alias with suffix '_HTTP' / Relevant after update to SP01 UIS4HOP1 / All Scope Items
2266478 / Task list SAP_ESH_INITIAL_SETUP_000_CLIENT: Working clients are updated despite software components with errors / Fact Sheets configuration / SAP S4HANA Fiori Apps Deployment (MDA)
2250057 / Task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT: Consistence check of SW Comp. &1 was unsuccessful / Fact Sheets configuration / SAP S4HANA Fiori Apps Deployment (MDA)
2221810 / PLM search relation not deleted correctly / Fact Sheets configuration / SAP S4HANA Fiori Apps Deployment (MDA)
2221877 / Connector generation and virtual models / Fact Sheets configuration / SAP S4HANA Fiori Apps Deployment (MDA)
1885373 / Missing sap Annotations in Metadata Document / Analytical apps configuration / SAP S4HANA Fiori Apps Deployment (MDA)
2147950 / Apps missing in App Activation / Usage of ‘App Activation Tool’ SAPUIFT / SAP S4HANA Fiori Apps Deployment (MDA)
2146390 / App Activation shows app multiple times / Usage of ‘App Activation Tool’ SAPUIFT / SAP S4HANA Fiori Apps Deployment (MDA)
2260777 / Syntax error in program /UI2/CL_CATALOG_API======CP / Usage of ‘App Activation Tool’ SAPUIFT / SAP S4HANA Fiori Apps Deployment (MDA)
2197125 / App Descriptor support for 'App Activation' and PFCG administration for Fiori L / Usage of ‘App Activation Tool’ SAPUIFT / SAP S4HANA Fiori Apps Deployment (MDA)
2057775 / SAP Screen Personas rapid-deployment solution V2.30 / Central project note for SAP Screen Personas / Using SAP Screen Personas in SAP S/4HANA (UP6)
2050325 / SAP Screen Personas 3.0: Released Notes Information / SAP Screen Personas 3.0 Note with sub-notes.
This note provides information on all notes relevant for SAP Screen Personas in addition to the respective support pack. / Using SAP Screen Personas in SAP S/4HANA (UP6)
1888428 / Sizing for SAP GUI for HTML / Sizing CPU and memory in setting up the system / Using SAP Screen Personas in SAP S/4HANA (UP6)

3.4SAP 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 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 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 and Template Name / BP_S4H_UX_S4HANAXV1 - SAP Best Practices for user experience in SAP S/4HANA_V1
Solution Package Name(s) / SAP Best Practices for user experience in SAP S/4HANA_V1

3.5Active Business Functions

Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated:

Software Component / Business Function / Configuration or Data required / Relevance
S4CORE / BSESH_HANA_SEARCH / SAP S4HANA Fiori Apps Deployment (MDA)
S4CORE / BSCBN_HANA_NAV / SAP S4HANA Fiori Apps Deployment (MDA)

3.6Software Landscape Diagram

Find an overview of the Technical System Landscape in the configuration guide ‘SAP S4HANA Fiori Foundation Configuration (MAA)’ in chapter ‘Technical System Landscape’.

For SAP Screen Personas, an overview of the system landscape architecture in the configuration guide ‘SAP Screen Personas in SAP S/4HANA (UPI)’ in chapter ‘Technical System Landscape’.

3.7Connectivity

The following connectivity is required:

RFC Destination / Description / Connection Type / Created in Building Block / Comment
systemidCLNT<Client> / RFC Destination to SAP Server / 3 / SAP S4HANA Fiori Foundation Configuration / For more details, see chapter ‘Gateway System: Creating Trusted RFC in NetWeaver Gateway to SAP Business Suite’
systemidCLNT<Client> / RFC Destination to SAP NetWeaver Gateway Server / 3 / SAP S4HANA Fiori Foundation Configuration / For more details, see chapter ‘Defining Trust between SAP S/4 HANA and SAP NetWeaver Gateway’
<system id >CLNT<Client>_HTTP / RFC HTTP connection to S/4 HANA Server / H / SAP S/4 HANA other app Types Deployment (MAL) / For more details, see chapter ‘Creating an HTTP RFC Destination to Back-End Server’
Additional RFC Connections (Type 3 and H)depending on scope of the package required / 3/H / See SAP Note 2269272

3.8Roles and Authorizations

The following section provides a brief overview on the chapters dealing with roles and authorizations:

Purpose / Created in Building Block / Chapter
Administrator Role / SAP S4HANA Fiori Foundation Configuration (MAA) / SAP Gateway System: Assign role template for administrators
Access roles to Fiori Launchpad and Launchpad Designer / SAP S4HANA Fiori Foundation Configuration (MAA) / ConfiguringAuthorizationRoles
Usage of context-sensitive user assistance / SAP S4HANA Fiori Foundation Configuration (MAA) / SAP Gateway System: Create a role referencing the Catalog
Administration embedded search / SAP S4HANA Fiori Foundation Configuration (MAA) / Assign Roles for Embedded Search administration
Backend Authorization for Users / SAP S/4 HANA Fiori Apps Deployment (MAD) / Create and Assign the Backend Role for a User
Frontend Authorization for Users / SAP S/4 HANA Fiori Apps Deployment (MAD) / Assign a User to the SAP Fiori Launchpad
Overview on role management for Fiori / SAP S4HANA Fiori Launchpad Operation (MAG) / PFCG Rolesmanagement
Role for JAM Integation / SAP S4HANA Fiori Launchpad Operation (MAG) / Creating a Social Media Integration Role
Backend and Frontend Authorizations / SAP S/4 HANA other app Types Deployment (MAL) / Web Dynpro App Configuration