2/4/25, 10:36 AM about:blank
Performance Issue for Apps in Fiori Launchpad - Where to Improve checklist
Fiori Launchpad
and Apps
Performance
SAP Fiori and the
Fiori Launchpad
have thousands of
role-based apps for
different SAP
solutions, such as
SAP S/4 HANA,
SAP Simple
Finance, and the
SAP Business
Suites. The goal is
to apply the SAP
Fiori UX to provide
a personalized,
responsive and
simple user
experience.
With the goal
highlighted above,
there are known
performance tweaks
that one can do to
help improve the
runtime or display
of a Fiori app in the
Fiori Launchpad
(FLP).
The following
questions/guides
will help provide
the necessary
knowledge or steps
to help the user run
better with SAP.
Note: Additional contact information is under the Global Support Interaction Center (GSIC):
www.service.sap.com/supportcenters for web-form or telephone information. Please reference SAP note
560499 for more details.
Best Practices to Optimize Performance
about:blank 1/4
2/4/25, 10:36 AM about:blank
Fiori Application Specific Performance (ex: My Inbox, etc.)
Check SAP Landscape and Deployment Options
Browser/Server Certificates Performance Causes
User Roles on Performance
Kernel Upgrade and Relationship with Performance
Cache Buster Information (load updated information) or Cache issues
Customization Techniques FAQ and SAPUI5 library performance updates
Best Practices to Optimize Fiori Performance
SAP community of users,
development, services and consulting have
compiled a few best practices to help
improve the performance for SAP Fiori
application or Launchpad.
The following known options are provided
herein.
Typical startup performance of Fiori
Launchpad is affected by:
The amount of displayed tiles:
Show as few tiles as possible
on the Launchpad -> SAP
recommends using not more
than 100 tiles on the Fiori
Launchpad. Please refer to
SAP note 2421371
The amount of dynamic tiles:
Apply tile caching respectively
- increase the tiles' refresh
interval
The SAPUI5 resources
Use the latest patch level of
your SAPUI5 version
Use the Fiori Cache Buster as
described in the SAP Online
Documentation
about:blank 2/4
2/4/25, 10:36 AM about:blank
The browser of the respective device
used
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
The Network
Ensure minimum
3G: connectivity / bandwidth -
> please refer to SAP
note 2240690
Note: Additional quick techniques to measure performance:
2916959 - Fiori Performance Troubleshooting (checklist)
Known SAP Measurement Tools or Transaction code = /IWFND/STATS (Example)+
STATS_FE + STAD + /IWFND/TRACES + ST12 (2436955) + FESR (Front End Statistical
Report 2981366 )
FESR - This shows End to End Application ID + Name/Steps + Runtime Device, Session +
Performance End to End
STATS or STATS_FE - This shows the request entering the ABAP Stack (Memory usage or Top
10 Tables that is used by the offending query or service)
If a user identifies a table to be a bottleneck then an appropriate DB action or services
action may be done to reduce number of records (Ex: From 20 million business partners
down to 200K business partners)
A DB or DBA (Database Admin) action could be doing maintenance on the data
i.e. Ask yourself or your DBA when was the last time you/they did database
archiving on the company's data?
Ask the DBA if the hardware that runs the Database has enough assigned
virtual cache per hardware spec (i.e. If there is 100% memory/disk assign to a
backend then an option to assign a percentage of that could be allotted for
caching purposes. This may help with querying the backend on the same data.
Instead of querying the backend Data Disk for the same data (i.e. Read from
disk or hard disk), the database may offer what is already in the virtual cache
and this may speed up the backend processing (i.e. retrieve from available
cache data instead of asking the hardware to read from hard disk).
Ask your DBA for more details tied to hardware/software assigned
cache
A services action could be searching the name of the table or OData Services
(*_SRV) or method or class (CL_*) as presented by the STATS or STATS_FE report
or FESR or ST12 (i.e. which one has the most time used) if there is an available
SAP note on purging old data or clearing cache or performance updates on that
method/OData services/table available for your release or newer releases (i.e.
recommended the user/admin to search the SAP notes/KBA on the named offending
OData services or table or method or class)
about:blank 3/4
2/4/25, 10:36 AM about:blank
If an SAP note or KBA is found, apply the appropriate recommendation or
fixes
ST12 - To determine which OData queries are expensive or time consuming
-------Landscape Monitoring Tools----------
Front-End (FE) Backend (BE)
| |
|______REQUEST_______>|
|<_____RESPOND________|
FESR (Report)
AND
STATS/STATS_FE (Report)
-------END----------------------------------
Best Practice Goal: For Fiori consultant/USER/Admin/Basis - To identify the offending or
problematic method/table/class/services and find an SAP note or KBA for it.
- If a note or SAP KBA (Knowledge Base Article) is limited or not available to make sure that
the appropriate reports (ST12, STAD, FESR, STATS, etc.) are already saved or exported to be
shared with SAP for faster processing.
2506498 - Monitoring SAP Fiori Application Usage
See additional information on Troubleshooting Fiori Performance below (SAP Transaction codes) for other
techniques
about:blank 4/4
