Relevant for S/4HANA 2022, 2021, 2020, 1909, 1809, 1709, 1610, 1511

In most of the S/4HANA implementations the RIG team has been able to support we face the question on how to improve performance for Web Dynpro ABAP and SAP GUI for HTML (WebGUI) based tiles. This is no simple task but following you will find some useful considerations.

1. Apply kernel patches (all versions)

Most of the corrections and performance improvements are delivered via kernel patches as the kernel is the core for the Web Dynpro ABAP and WebGUI engines. Instructions on how to apply patches are available in note 2221289

You can find an overview of the kernel dependent performance improvements for WebGUI in note 2558822

2. Apply NWBC ABAP runtime patches (all versions)

When you are using WebGUI applications through the Fiori Launchpad you will be using part of the NWBC for HTML engine, hence you want to make sure that it has the latest corrections. You can check the current version by going through any of the options listed in note 1864151 and find relevant notes by searching for the keywords “SAP NWBC ABAP Runtime Patch” in support portal search.

3. Ensure Unified Rendering Library compatibility (all versions)

In hub deployments, we have sometimes observed non-matching support package levels for certain components, especially with component SAP_UI which contains the Unified Rendering Libraries. It is important to try to maintain the same level on both the Frontend and Backend servers as non-matching versions may result in unpredictable behaviors. You can validate the current version of the Unified Rendering Libraries in your system by running report WDG_MAINTAIN_UR_MIMES. If in doubt raise a ticket to component BC-WD-UR showing the results of the report.

4. Enable compression (all versions)

Make sure compression is enabled for the following nodes in tx: SICF

• /sap/public/bc/ui5_ui5/

• /sap/bc/gui/sap/its/webgui/

5. Use In-Place Navigation (1709 or higher)

When users navigate to a Web Dynpro ABAP or WebGUI application, the target application is by default opened in a new browser window or tab depending on your SAP_UI component version as described in note 2403527. You can change this behavior using Fiori Launchpad configuration parameters:

• NAVIGATION_GUI_INPLACE
• NAVIGATION_WDA_INPLACE

6. Use Stateful Navigation for WebGUI (1809 or higher)

When users navigate between apps, the default behavior of the launchpad is to remove the so-called application container and create a new one for the new app. You can change this behavior by using the Launchpad configuration parameter:

• NAVIGATION_GUI_STATEFUL_CONTAINER

Once it is set to true, when users navigate from WebGUI to another app, the container for the original WebGUI will be kept-alive making subsequent navigation to WebGUI faster. In short, this means that the required runtime objects are only loaded once and will be persisted until the session ends or you close the browser tab.

Please note that this feature requires a minimum kernel version as described in note 2657777

About Fiori Launchpad configuration parameters:

You can find information on how to configure Fiori Launchpad configuration parameters in the following links:

We hope these tips can help you in your implementations!

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on our SAP Fiori for SAP S/4HANA wiki

Do you have any questions? Let us know in the comments section.

Thanks,

SAP S/4HANA RIG