As member of the SAP S/4HANA Regional Implementation Group, I have the privilege of working with a lot of customers who are implementing SAP S/4HANA. My colleague Jocelyn already introduced performance benefits of inplace option for UX/ functional people, please check her blog post https://blogs.sap.com/2019/01/29/fiori-for-s4hana-calling-gui-web-dynpro-abap-without-opening-a-new-... in this blog post, I am going to provide more technical/performance related information, that in-place option will save time for all classic UIs.
“Why” it will save a time?
Because in-place approach does not need to rebuild the Fiori Launchpad shell in a new browser window, but let’s start at the very beginning.
With SAP S/4HANA 1809 and higher version additional performance improvements are available for the SAP Fiori Launchpad. To obtain these improvements, you have to make configuration settings on your frontend server.
Improved performance using in-place navigation for classic UIs
The default behavior for applications that make use of classic UI (Web Dynpro ABAP and SAP GUI for HTML) are opened in a new browser windows or tab. Changing the behavior for Web Dynpro ABAP and SAP GUI for HTML, so these apps are opened in-place (in the same browser windows and tab), you need to configure In-place navigation for classic UI2
- Logon to frontend sever
- In SAP Reference IMG (transaction SPRO), choose SAP NetWeaver > UI Technologies > SAP Fiori > Configuring SAP Fiori Launchpad > Client-Specific Settings (or transaction /UI2/FLP_CUS_CONF)
- Choose the sub-dialog FLP Configuration
- Click on the Change/Display icon to go into Change mode.
The title changes from Display View “FLP Configuration”: Overview to Change View “FLP Configuration”: Overview.
- Press New Entries (1) to add for the FLP Property ID (2) add the following parameters>
- NAVIGATION_GUI_INPLACE - Open SAP GUI for HTML applications in-place
- NAVIGATION_WDA_INPLACE - Open Web Dynpro applications in-place
- In the Property Value column, change from false to true (3); and SAVE your settings
The system will save changes to FLP setting - Client scope; table /UI2/FLPSETC, but they are not automatically recorded in transport request, anyway you can manually add them to customizing transport.
Testing in place configuration with apps “Create Sales Orders”
Logon to your Fiori launchpad home page, and select the relevant tile (my example „Create Sales Orders “) or link to launch the classic app.
- Click on Tile “Create Sales Orders”
The classical UIs are now opened in-place so there is not additional browser window/tab opened.
Performance benefits and benchmark information
All information is provided from Developers tools using Google Chrome.
Let’s use apps “Create Sales order” as our example.
Running apps in-place mode will send 15 requests and transfer 486 KB.
Now let’s change configuration to “false” and save settings.
Refresh/Reload your Web Browser and your changes are immediately applied.
Again, click to the tile “Create Sales Orders”
The new tab is opened.
From Google Chrome you will get information:
Running apps ex-place mode will send 51 requests and transfer 4.0 MB!
Again, in place it was only 15 requests and transfer 486 KB.
Back to the question why?
Because every ex-place navigation triggers reloading the entire FLP content plus SAPUI5 resources, but in-place approach does not need to rebuild the Fiori Launchpad shell in a new browser window.
In-place mode has significant performance benefit to save time for every WDA and WebGUI apps launched in browser.
From Headers information you can also see Request URL is based on Webgui call with mode sap-target-navmode=inplace for transaction VA01.
Becoming a SAP Fiori for SAP S/4HANA guru
You’ll find much more on our SAP Fiori for SAP S/4HANA wiki
Brought to you by the S/4HANA RIG
- SAP Managed Tags:
