Skip to Content
Product Information
Author's profile photo Sally Redmond

Part 2: Best Practice for Performance: Setting up your S/4HC Homepage and Role Groupings – Updated 2002

In Part 1 of the earlier blog (Optimal Browser Settings for Performance in your S/4HC System), we explored how to get the best from your browser settings.

But how about beyond the browser settings….? In this part, we will cover several more important points for your toolkit to improve loading times and home page configuration so your end-users enjoy the best end-user experience in the cloud.

Also updated for 2002 – new settings in Manage Launchpad to improve performance by selecting APPS as the default search factor and so reducing overload of Enterprise Search launch from FLP.

1.Ensuring a Smooth Launch to the Landing Page

With the delivery of 1711, we introduced the concept of ‘Blind rendering” which renders only the visible tiles of FLP home page. With this setting, we still need to parse the entire PageSets which describe the FLP home page, so wisdom tells us that one option is to configure launchpad to ensure you select only one grouping at a time.

Why: this gives you the fastest loading time and you can still use the anchor tab at the top to quickly navigate between app groupings and the app finder/search bar


If you have apps with heavy animation activity, you can also try setting the animation to ‘Minimal’
in the Appearance settings.


2.The Key to Fast Launching of Apps and Searching for Business Objects 

As most users wish to launch Apps rather than search, you can take the following guidelines to have the best navigation experience.

    • FLP home page is designed to only host favorite Apps you use every day
    • The recommended way to find an App on your FLP home page is to use either “View Ports” or “Overflow” to jump directly to the required group, and then select the required App
    • Occasionally used Apps can be found by using either App Finder in FLP Me Area or by Searching in the area of Apps
    • To locate business objects (e.g. sales orders or material) using the search bar, SAP Enterprise Search must be integrated and set up in your environment; otherwise, the search returns apps that are located only in your home page and the catalog.
    • A general recommendation for using Enterprise Search: When possible please always try to restrict your search area by using the pull-down left to the search term field

The app searcher in the top right corner allows you to search for Apps entirely within the browser.

Alternatively, from the home page – the app finder also produces fast results searching for specific apps within the business catalog

2.1 New for CE2002 – Selectable Search Settings

1). Observationally, SAP finds that users are often using the Enterprise Search directly after the logon to FLP to search for an app. With the current default option “ALL” this searches in all search areas like SD, MM, etc. As a result. this is causing a maximum load to the system and makes the FLP logon and ESH for other users further slower.

2). When using Enterprise search, you should always restrict your search area when possible. This would result in better response time and less resource consumption on the server and database.

To optimize the system behaviour, the following configuration feature is delivered with CE2002. But the key user needs to decide for one of three options and need to make the necessary settings.

With the Administrator role ( e.g. Customers’ Key User) will be able to change / choose 3 Boolean settings in the App Manage Launchpad Settings:

The required role is SAP_BR_ADMINISTRATOR

  • Apps as default datasource
  • Remove All-datasource (Apps as default)
  • Disable BO search (only Apps-search)


–> Apps instead of All is the default datasource. However, manually switching to All is still possible.


–> All is completely removed, i.e. again Apps is the default datasource and single-datasource searches are still possible by manually switching to the respective datasources.

Apps-Search is executed locally in the Browser only, i.e. there’s no load produced on the search-backend.



Information: SAP Help and Fiori Launchpad Guide


3. Lower the Load: Reduce the Volume of Roles per User

Best practice for adding roles for users is that adding multiple roles should really be avoided as loading of all the tiles happens asynchronously in background to take advantage of UI2 technology as built-in UI2 caches to the DB server to cache FLP content.

By having disproportionate volume of roles and in turn tiles, this leads to a greater chance of UI2 cache invalidation.

    • In the most cases in the productive environment, the FLP content is loaded and parsed directly from the local browser cache.
    • For any reason when the browser cache is cleared or not yet filled, the FLP content is fetched from the server from the UI2 caches.
    • When your FLP content is changed due to changed role assignment, role content, personalization of FLP home page; then UI2 caches must be invalided.
    • In this case, the server needs to calculate FLP content from the scratch again at FLP logon time.
    • This could take up to a minute or more: depending on the size of your FLP content

SAP Recommendation: Provide users only the required roles as per their functional role in the company

Important to note: In first load or first use of Starter and Quality system environment, extended load time maybe seen but will improve with subsequent loading as the initialization phase involves the creation of many Javascript objects which usually results in high initial loading time.

Conclusion:  Performance Matters – Less means More

We can conclude that to take advantage of UI2 caching technology delivered with S/4HC and Fiori this best done with only the roles necessary and access to your essential apps.  Otherwise, the greater the data load, then the greater the impact on performance due to the data download and rendering effort.

In the next blog chapter, we will look at some of the developer tools that you can use and also used by SAP to analyse performance.

Part 3  – Capturing System Performance using HTTP Watch trace and Chrome Developer Tools. 


Related Notes:

2673924 – Performance Related Restrictions in 1808 

2647911 – Release Restriction Note in 1808 






Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.