5Steps2FIORI
Gain hands-on experience on Fiori configuration
Markus Andres
Alessandro Sabidussi
Jorge “Javier” Baltazar
Step by step approach organized in phases
30
WP 1
WP 2
Step by step approach
organized
in phases
WP 3
WP 4
WP 5
Date
Day 1
Day 2
Day 3
Day 4
Day 5
Objective
Gateway Configuration
Basic FIORI
Configuration
FIORI Configuration
Special Launchpad
features
Build Custom Theme
Troubleshooting &
Performance Analysis
Extensibility and
Development
Content / Tasks
•
•
•
•
•
•
•
•
•
•
•
•
Configuration of SAP
Front-end Server
Activation and
configuration of
FIORI Launchpad
Activation of
Enterprise Search
•
•
Activation and
configuration of
FIORI applications
Application selection
Build roles &
catalogues
SAP Theme Designer
Notification area
App Finder
System description
•
•
•
Fiori App
Troubleshooting
Caches
Webdynpro & Web
GUI integration
Optimizing
Performance
ABAP in Eclipse
CDS Views
Develop a new FIORI
application
Duration roll-out
session
60 mins
45 mins
1 hour
1 hour 30 min.
1 hour 15 min.
Partner additional effort
3 - 4 hours
2 - 3 hours
2 - 3 hours
3 - 4 hours
3 - 4 hours
Partner Resources
required
Tech / Basis Consultant
Tech / Basis Consultant
Application Consultant
(validation & testing)
Tech / Basis Consultant
Application Consultant
(validation & testing)
Tech / Basis Consultant
Developer
Customer
2
Content:
➢
Connect to your system
➢
Basic Fiori and Front-end Configuration
➢ Fiori Architecture, Strategy and Versions
➢ Configuration – Getting Started
➢ Fiori Configuration Steps
➢
Call to action
Customer
3
Connect
to your system
System Landscape per partner
S/4HANA 1909
Terminal Server
2
Application Server
Browser
1
SAP GUI
SAP HANA 2.0 SP04
SAP ADT
in Eclipse
Communication
Customer
5
Connection guide
Customer
6
Access to infrastructure (Cheat sheet)
•
Two user ID per team (2 PDF documents)
•
Cheat sheets will be sent to Team lead
Customer
7
Basic Fiori and
Front-end Server Configuration
Agenda
Fiori Architecture, Strategy and Versions
Configuration – Getting Started
Fiori Configuration Steps
9
Fiori Architecture, Strategy and Versions
SAP Fiori deployment options for S/4HANA
RECOMMENDED
NOT RECOMMENDED !
SAP Fiori FES*
embedded
SAP Fiori FES*
as standalone system
SAP Fiori FES* as hub for
multiple S/4HANA systems
FLP content
FLP content
FLP content
Fiori UIs
Fiori UIs
Fiori UIs
SAP S/4HANA
back-end
SAP S/4HANA
back-end
* SAP Fiori Front-end Server
SAP S/4HANA
back-end
SAP S/4HANA
back-end
Details: SAP Fiori deployment options and system landscape recommendations, SAP Note 2590653
Migration from Standalone to Embedded: Moving from Standalone to Embedded Deployment in SAP Fiori for SAP S/4HANA
11
Deployment Options for Fiori Frontend Server
Note 2590653 - SAP Fiori front-end server deployment for SAP S/4HANA
https://launchpad.support.sap.com/#/notes/2590653
https://www.sap.com/documents/2018/02/f0148939-f27c-0010-82c7-eda71af511fa.html
https://wiki.scn.sap.com/wiki/display/Fiori/SAP+Fiori+Front-end+Server
12
SAP Fiori Architecture Options – Considering the SAP Fiori Roadmap
Fiori FES
Option 0*
Not recommended
possible
due to
to release
release
dependencies
dependencies
between
between S/4HANA
S/4
and Fiori FES
and Fiori FES
S/4HANA
Region 1
Option 1*
S/4HANA
Region 3
S/4HANA
Region 3
Central Fiori Launchpad
S/4HANA
cFIN
S/4HANA
MDG
**
Recommended
Fiori FES
S/4HANA
Region 1
Option 2*
Not recommended
Fiori FES
S/4HANA
Region 2
Fiori FES
S/4HANA
Region 3
Central Fiori Launchpad
Fiori FES
Fiori FES
Fiori FES
S/4HANA
Region 1
S/4HANA
Region 2
S/4HANA
Region 3
Fiori FES
S/4HANA
cFIN
Fiori FES
S/4HANA
MDG
A decision must be taken on how to
deploy SAP Fiori throughout the
customer’s landscape.
Depending on customer’s hosting
provider you may need to involve
different teams (e.g. HEC
infrastructure)
**
Fiori FES
S/4HANA
cFIN
S/4HANA
MDG
*Sample Landscape
Not Shown:
• Web Dispatcher/Reverse Proxy
• Firewall/s
**Central Fiori Launchpad
Planned Solution
13
Planned
innovations
Single Entry Point in multi-system landscapes
SAP Fiori Cloud
SAP Cloud Platform
Central Entry Point
SAP Cloud
Solutions
FLP content
apps
CDM content
apps
Business
Suite
back-end
S/4HANA
back-end
back-end
CDM* / DCM**
SAP FES
SAP S/4HANA
SAP S/4HANA
CDM content
FLP content
apps
apps
Business Suite
back-end
non SAP
Business Suite
back-end
This is the current state of planning and may be changed by SAP at any time without notice.
FLP content
FLP content
apps
apps
back-end
back-end
back-end
Legend
FLP: SAP Fiori launchpad
CDM: Common Data Model
14
Embedded Migration – Overview
FIORI
400
400
300
TRANSFORM
300
400
300
FES
FIORI
BES
BES+FES
Main steps are:
1. Identify active content in Frontend
Fiori system
2. Identify custom content in Frontend
Fiori system
3. Install SAP Fiori Frontend
components in Backend S/4HANA
system
4. Transport custom content into
Embedded Fiori system
5. Activate Fiori content in Embedded
Fiori system
6. Update SAP Web Dispatcher
configuration
7. Perform UAT
S/4HANA
Fiori for S/4HANA Moving from Standalone to
Embedded Deployment in Fiori for SAP S/4HANA
15
Fiori Strategy and Versions – Handling complex landscapes
URL Link
FES
Launchpad 1
BES
S4H
User ID:JOE
Launchpad 2
Launchpad 3
Fiori Add-on
Fiori Add-on
CAR
User ID:JOE
CFIN
User ID:JOE
S4CORE
1909
S/4
Analytics
UIS4HOP
1909
CAR
Analytics
CFIN
Analytics
*Architecture is simplified for display purposes
16
SAP Fiori Architecture Recommendations
Additional considerations:
1.
2.
3.
Define SAP Fiori adoption strategy:
❑
Full SAP Fiori
❑
Phased adoption
Define Internet-facing scenarios:
❑
Internal access
Favor SAPUI5, Web Dynpro
ABAP, SAP GUI for HTML
❑
External access
Favor SAPUI5
Consider SAP Fiori launchpad
technology integration options:
❑
Web Dynpro ABAP
❑
SAP GUI for HTML
❑
SAP Business Client
❑
SAP or 3rd Party Cloud Solutions
17
Configuration – Getting started
Configuration – Getting started
As a general recommendation, when planning a Fiori for S/4HANA Project you should start by
reading through the available documentation. Once you decide on doing so, you will find that there
are various documents and may find it difficult to determine where to start.
More Information: Fiori for S/4HANA – Getting started
19
How to implement for 1909?
Changing the Implementation Experience of SAP Fiori
Activation of individual apps leads to high upfront investment to experience SAP Fiori
Select relevant
SAP Fiori apps
Implement selected SAP Fiori scope
Experience
SAP Fiori
New approach: Experience SAP Fiori “out of the box” along business roles
Select relevant
business roles
Rapid SAP
Fiori
activation
Experience
SAP Fiori
Adjust
FLP content
and business
roles
FLP=SAP Fiori launchpad
21
Quickstart to experience SAP Fiori
Experience SAP Fiori “out of the box” along template business roles
Initial scoping
Select relevant
business roles
Sandbox
Rapid
SAP Fiori
activation
Fit / Gap analysis
Implementation
Experience SAP Fiori
Adjust
FLP content and
business roles
* FLP = SAP Fiori launchpad
22
Tools supporting the implementation of SAP Fiori for SAP S/4HANA
Initial scoping
Identify business roles
SAP Fiori apps reference library
SAP Readiness Check 2.0
SAP Fiori apps recommendations
SAP Fiori lighthouse scenarios
Rapid activation of SAP Fiori
for selected business roles
Task Lists for rapid SAP Fiori activation
• SAP Fiori foundation
• SAP Fiori content activation
Adjust SAP Fiori launchpad
content according to fit/gap analysis
SAP Fiori launchpad content manager
• Search SAP Fiori launchpad content
• Identify matching tiles/target mappings
• Copy & adjust catalogs
• Mass assignments of tiles/target mappings
• Catalog assignments to roles
• App activation status
23
New approach to activate and implement Fiori for SAP S/4HANA
Copy & adjust to customer specifics
Rapid SAP Fiori activation
Task list
SAP Fiori
foundation
Basic configuration
Generate generic
Administrator and
End User roles
Task list
SAP Fiori
content
activation
Activate apps for
selected business roles
Roles
ready
for test
Launchpad
content
manager
Create custom catalogs
based on SAP’s
business catalogs
Activate content for
custom roles
Generate
custom roles
Generate PFCG
authorization roles based on
SAP Fiori launchpad content
(front-end and back-end)
Find out more via this blog:
https://blogs.sap.com/2020/03/16/fiori-for-s4hana-new-rapid-content-activation-on-s4hana-1809-1709-part-1-overview/
Rapid activation available via SAP Notes:
S/4HANA 1709 FPS01 or higher: https://launchpad.support.sap.com/#/notes/2695653
S/4HANA 1809:
https://launchpad.support.sap.com/#/notes/2704570
S/4HANA 1809 FPS01 or higher: https://launchpad.support.sap.com/#/notes/2777142
S/4HANA 1909:
https://launchpad.support.sap.com/#/notes/2834415
FLP = SAP Fiori launchpad
PFCG = Profile Content Generator
24
ABAP design time tools
Technical catalogs (back-end)
App descriptor mass maintenance
(SUI_MM_TM_APP)
• Technical catalogs for GUI transactions and
WebDynpro
Catalogs (front-end)
Mass operations for
business catalogs (front-end)
SAP Fiori launchpad designer (FLPD)
SAP Fiori launchpad content manager
•
•
•
Maintenance of tiles and target
mappings in technical catalogs
Maintenance of groups
•
•
•
•
Supplements FLPD
Maintain business catalogs
Searching SAP Fiori launchpad content
Identify matching tiles/target mappings
Assign (mass) tiles/target mappings
25
The “New” Approach – Easily finding Fiori Roles for your project
How to easily select Fiori Roles?
❑
Filter apps in the Fiori Apps Library
and use “Aggregate” function to
collect your apps.
❑
Download an excel file containing
the required Roles for your app
selection
SAP Fiori Apps Library
26
Known Limitations of the “New” Approach
As a result of this new activation approach, approximately 90% of
apps / content works out of the box, however, there are known
limitations:
▪ Some Dynamic Tiles might not fully work.
▪ Apps based on the Generic Configuration
Framework (sakp.cross.genericui) might not fully work.
▪ Apps based on the Smart Business Framework (SSB) might not
fully work.
▪ Apps based on the Analysis Path Framework (APF) might not
fully work.
▪ Apps based on the Workflow Framework might not fully work.
▪ Apps based on the Application Logs & Jobs Framework might
not fully work.
▪ Apps based on the Design Studio Framework might not fully
work.
▪ Special Apps like My Inbox might require additional customizing.
See 2676990 & 2424054
▪ Hub Deployment not supported.
Follow-up activities and known activation errors are listed in
the note
If you find errors not listed in the note, send an email to
jorge.baltazar@sap.com
27
Fiori Configuration Steps
Exercise Overview
Fiori Configuration Steps
Required for Embedded Deployments
Configuration of SAP Fiori Infrastructure
SAP Fiori Embedded Analytics
Run the configuration steps described in notes 2303900, 2289865 and 2636754
29
Fiori Configuration Steps
Required for Embedded Deployments
Configuration of SAP Fiori Infrastructure
SAP Fiori Search
1.
2.
3.
4.
Issue transaction STC01 and execute task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT
Manually confirm preconditions
Setup DB connection
Select Software component
Ensure content activation
Note: If your system was copied you will need to run task list SAP_ESH_RESET prior to running SAP_ESH_INITIAL_SETUP_WRK_CLIENT
30
Fiori Configuration Steps
Required for Embedded Deployments
Setup of SAP Fiori System Landscape
Execute Basic Configuration of Fiori
and Gateway
Issue transaction STC01 and execute task list SAP_GW_FIORI_ERP_ONE_CLNT_SETUP
31
Fiori Configuration Steps
Required for Embedded Deployments
Setup of SAP Fiori Foundation
Execute Fiori Foundation Configuration
1.
2.
3.
4.
Issue transaction STC01 and execute task list SAP_FIORI_FOUNDATION_S4
Assign Workbench Request
Define RFC connection names
and settings
Generate Foundation Roles
(Admin/User)
The running task list
automatically executes
Backend Catalog replication,
Cache Cleanup, Activation of
basic Gateway OData services
32
Exercise Tips & Tricks
The exercises described in this Work Package are the
foundation of Fiori activation:
❑
Missing any step can generate fatal consequences
on exercises of the following Work Package.
❑
There are tight dependencies, specially between
Embedded Analytics and Enterprise Search that
when not sorted out correctly will affect your Fiori
implementation.
❑
These configurations are the most time consuming,
depending largely on hardware resources and
system utilization.
33
Exercise Tips & Tricks
❑
You will need to implement several notes to ensure
correct execution of the task lists.
❑ Note implementation hints are provided in the
documents
❑
We recommend trying to run task lists in parallel as
this will help you optimize execution times
34
Closure
and call to action
System Landscape per partner
S/4HANA 1909
Terminal Server
2
Application Server
Browser
1
SAP GUI
SAP HANA 2.0 SP04
SAP ADT
in Eclipse
Communication
Customer
36
Call to action
•
•
•
Review this presentation (published in JAM group)
Execute the activity documents for
• Basic Fiori and Gateway Configuration (WP1)
Collaborate using JAM in case of issues or doubts
Customer
37
Q&A
Ask your questions
Use Jam to post your
questions
Customer
38
Thank you.
Contact information:
SAP 5Steps2FIORI Team
sap5steps2fiori@sap.com
5Steps2FIORI <YOUR EDITION>