2022-09-15 2916959

2916959 - Fiori Performance Troubleshooting

SAP Knowledge Base
Version 9 Type
Article
Master
Language English English
Language
Release
Released to Customer Category How To
Status
XX-SER-MCC (Mission Control Center - Knowledge
Component Released On 05.04.2022
Management)

Please find the original document at https://launchpad.support.sap.com/#/notes/2916959

Environment

You are looking for guidance on troubleshooting performance issues for Fiori.

Important! The recommendations in this article are based on practical project experience and should be
verified by the project team during the planning, testing and execution of the project.

The content of this note may be updated at anytime.

Resolution

Performance troubleshooting is an iterative process, therefore, recommendations on different layers or

aspects may apply to reach the desired performance. The recommendation when troubleshooting
performance issues is to narrow down which layer the performance issue is in a process of elimination.

This article is organized into the following sections to allow better navigation:

• General system aspects

• Network
• Distance from end user to Frontend Server
• Browser of the respective device used
• SAPUI5 resource
• SAP GUI for HTML & WebDynpro performance
• Limitations of SAP GUI for HTML
• Fiori Layer
• Fiori Launchpad startup performance
• Fiori Launchpad Search performance
• Single Fiori App Peformance

General system aspects

Even if there are peformance issues in Fiori, the root cause could be in general system aspects. Indicators
coulld be to have as well performance issues in SAP GUI for Windows, WebDynpro, etc. which are not Fiori
related.

Recommendation:

• Check the general SAP system recommendations (Documentation, Quicksizer, etc.)

• Check the Software Versions (FES, NW, Backend, Web Dispatcher, etc.)
• Check the Workload and Performance Statistics (ST03N)

© 2022 SAP SE or an SAP affiliate company. All rights reserved 1 of 6

2022-09-15 2916959

• Check Available Dialog Work Process and Dialog Queue length(/SDF/MON or /SDF/SMON)
• Check the Operating System (Dumps in ST22, Syslog-Errors in SM21, etc.)
• Check the Hardware Capacity (ST06)
• Check the ABAP Parameters (Memory Management, Buffer, Work Processes, Communication, ICM,
etc.)
• Check the Database (Statistics and parameter in DBACOCKPIT)
• Check the Web Dispatcher (Configuration for routing, workload, SSL, etc.)

Network

Slow network performance can be caused by following aspects:

• Browser of the respective device used

• Distance from end user (browser) to Frontend Server
• General network conditions

Recommendations:

• Ensure minimum 3G connectivity / bandwidth → Refer to SAP Note 2240690.

• Many Fiori Apps are SAP GUI based which will be exposed as SAP GUI for HTML in the Fiori
Launchpad running in Browser. SAP GUI for HTML feels slower than SAP GUI for Windows and
furthermore has limitations → Refer to the section Limitations of SAP GUI for HTML.
• Check for cache issues - reference the KBA 2626394 - Troubleshooting Fiori Apps Cache issue - how
to information

Distance from end user to Frontend Server

• One of the main reasons for slow performance is the fact that the SAP UI5 libraries are located in the
ABAP Front-end Server (FES), when the Fiori web page is rendered it needs to make a call to the
ABAP FES to load the JavaScript libraries.
• In high-latency networks this results in high rendering time lapses which affects end-user performance
• One way to overcome this situation is to load UI5 libraries from a Content Delivery Network (CDN,
Akamai) which enables users to load the UI5 libraries from a network server closest to their location
Please note that use of SAP's Content Delivery Network is only permissible for SAP cloud products
and development purposes. For more information, please see SAP Note 2943781 - Is the usage of
SAP's Content Delivery Network for onPremise systems permitted?

Browser of the respective device used

Browser-related recommendations are not Fiori or even not SAP related recommendations, instead general
Web standard recommendations. The most important aspect is activating the browser cache to cache all
static Fiori resources, e.g. SAPUI5 library, Application resources, etc.

Recommendation:

• Use the latest browser versions or the SAP Fiori Client for handheld devices
• Do not run the Fiori Launchpad in Private mode
• Select a sufficient browser cache size limit
• Do not clear cache history automatically when the browser closes
• Enable Browser caching
• Do not disable the browser cache in the browser developer tools
• Enable HTTP compression
• Check for cache issues - reference the KBA 2626394 - Troubleshooting Fiori Apps Cache issue - how
to information

© 2022 SAP SE or an SAP affiliate company. All rights reserved 2 of 6

2022-09-15 2916959

• Check the browser settings - reference the Note 2447857 - Fiori Launchpad: How to check browser
settings for better performance

SAPUI5 resource

Recommendation:

• Use the latest patch level of your SAPUI5 version

• Use the Fiori Cache Buster as described in the SAP Online Documentation

SAP GUI for HTML & WebDynpro performance

Recommendation:

• Check Kernel version and try to update as this is required by the new unified rendering concept →
Refer to SAP Note 2374840.
• Apply NWBC ABAP runtime patches (all versions) → Refer to SAP KBA 1864151.
• Force WebGUI/WebDynpro apps to open in same window when launching from Fiori Launchpad →
Refer to SAP KBA 2403527.

Limitations of SAP GUI for HTML

The SAP Note 314568 provides guidance on the limitations of SAP GUI for HTML.

Fiori Layer

Very often the root cause of performance issues are on the conceptional aspect of Fiori. For example
performance issues are raised with an test user with too many catalogs, search connectors and Fiori apps
assigned. This is not reflecting the reality, instead an end-user with tailored catalogs, search connectors and
Fiori apps should be considered. Still the technical side of Fiori should be considered as well.

Technical aspects

• General system aspects

• SAPUI5 resource
• Metadata Cache

Conceptional aspects

• Performance issues of Fiori Launchpad startup

• Performance issues in Fiori Launchpad Search
• Performance issues within a single Fiori App

Fiori Launchpad startup performance

• The more tiles you have on your FLP, the longer it will take to load.
• KPI (Key Performance Index) and dynamic tiles (i.e. display data changes all the time) have a bigger
impact on bandwidth, as they are in constant communication with the back-end servers to update
• Static tiles do not change; once they are loaded onto the FLP, they are not making any additional
"calls" to update
• KPI tiles may cause expensive analytical queries to be executed in SAP HANA. While with SAP HANA
incredible on-the-fly calculations are possible, there are still some boundaries in the amount of data
that can be processed in a reasonable time

Recommendation:

© 2022 SAP SE or an SAP affiliate company. All rights reserved 3 of 6

2022-09-15 2916959

• Show as few tiles as possible on the Launchpad. SAP recommends using not more than 100 tiles on
the Fiori Launchpad → Refer to SAP KBA 2421371.
• Apply tile caching respectively - increase the tiles' refresh interval.
• For KPI and dynamic tiles try to define a refresh interval or cache duration suitable to your end user
needs and SAP landscape capabilities.
• Implement the Fiori Launchpad (FLP) Tab Bar option → Refer to SAP KBA 2576059.

Fiori Launchpad Search performance

The default configuration of the Fiori Launchpad Search "All" is using the search string to search for objects
(e.g. Sales Order), defined with search conncetors, through the whole system. This search functionality is a
very powerful funcionality, but causes on on the other side a very high load on the system. A typical end-user
might not need all search connectors, instead only the relevant objects should be selected.

Recommendation:

• Reduce the number of search connectors for the end user.

• SAP recommends not more than 10 search connectors, 6-7 connectors is a good number of
connectors.

Single Fiori App Peformance

Fiori apps are based on several UI technologies and frameworks, even if all Fiori apps have the same look &
feel, the technical base and application architecture are very different. This is the reason why different skills
and expertises are needed.

• SAP GUI
• SAP GUI for HTML (Fiori running in a browser) → Refer to section SAP GUI for HTML &
WebDynpro performance
• SAP GUI for Windows (Fiori running in Business Client)
• WebDynpro → Refer to section SAP GUI for HTML & WebDynpro performance
• SAP Fiori (SAPUI5)
• SAP Fiori elements
• Analytical (SAP Fiori elements)
• Analytical (SAP Fiori elements: Overview Page)
• Analytical (SAP Fiori: SAP Smart Business generic drill down app)
• Analytical, BW Query used (SAP Fiori: Design Studio)
• Web Client UI

Recommendation:

• Check the technology or framework is used for the Fiori App. This information can be checked in the
Fiori App Library using the filter/property "Application Type".
• Refer to SAP KBA 2881803 for single Fiori app related information.
• Do note that some individual Fiori apps may show higher than expected response times, depending on
the S/4HANA release, check the following notes:

2837072 - SAP S/4HANA 1909: Performance Restrictions

2967834 - SAP S/4HANA 2020FSP0 Performance Restrictions
3013761 - SAP S/4HANA 2020FPS1: Performance Restrictions
3090070 - SAP S/4HANA 2021 FPS0: Performance Restrictions

Keywords

© 2022 SAP SE or an SAP affiliate company. All rights reserved 4 of 6

2022-09-15 2916959

Fiori, S/4HANA, S/4, S4, HANA, S/4 HANA, Performance, Launchpad

Products

SAP Fiori all versions

Other Components

Component Description

CA-FLP-ABA SAP Fiori Launchpad ABAP Services

This document refers to

SAP Note/KBA Title

2881803

2626394 Troubleshooting Fiori Apps Cache issue - how to information

2576059 How to enable Tab Bar navigation mode in Fiori Launchpad

2421371 Understanding Launchpad performance Issues

2403527 Force WebGUI/WebDynpro apps to open in same window when launching from Fiori Launchpad

1864151 How to determine the version and Patch Level of NWBC Runtime Environment

314568 SAP GUI for HTML functionality / Limitations / Sp. Behaviour

3090070 SAP S/4HANA 2021 FPS0: Performance Restrictions

3013761 SAP S/4HANA 2020FPS1: Performance Restrictions

2967834 SAP S/4HANA 2020FSP0 Performance Restrictions

2943781 Is the usage of SAP's Content Delivery Network for onPremise systems permitted?

2837072 SAP S/4HANA 1909: Performance Restrictions

2447857 Fiori Launchpad: How to check browser settings for better performance

2374840 New Unified Rendering version

2240690 Front-end Network Bandwidth Sizing for SAP Fiori Apps and SAP S/4HANA

© 2022 SAP SE or an SAP affiliate company. All rights reserved 5 of 6

2022-09-15 2916959
Fiori Apps Library

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2022 SAP SE or an SAP affiliate company. All rights reserved 6 of 6