Skip to Content
Technical Articles
Author's profile photo Uladzislau Pralat

Keeping S/4HANA Fiori Overview Page System Resources Utilization Under Control

S/4HANA Fiori Overview Pages provide important analytical insights about transaction data, but they can not stand on the way of transaction data changes. In some cases Fiori Overview Page application might occupy multiple application server processes and put heavy load on HANA DB, causing system performance issues. In my blog I explain how to prevent that.

Typical Fiori Overview Page has a number of cards.

Usually one OData service populates all cards. HTTP requests for all these cards are batched into one request, but SAP Gateway, by default, process them in parallel at back-end. Parallel processing means consumption as many dialog process as there are Overview Page cards or available system dialog processes (the least of two).

If Overview Page is used often and simultaneously by number of user then system might run out application server processes and spike HANA DB utilization. To prevent that you might need to switch off Parallelization of Batch Requests.

To do that you need to need to open OData service in Maintain Service transaction /IWBEP/REG_SERVICE, then click Display

On next screen click on Configure button

And finally check Deactivate Parallelization of Batch Requests checkbox

After the change batched requests are executed sequentially occupying only one process .

VoilĂ 

 

See my book SAP S/4HANA Analytical Applications with Fiori Elements for more Fiori Elements tips and tricks

Assigned tags

      5 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Jelena Perfiljeva
      Jelena Perfiljeva

      Thanks for the post, Uladzislau!

      I'm a bit confused by this statement:

      Usually one OData service populates all cards.

      Are you sure this is actually a typical scenario? Even on the handbook example here the cards represent different data (e.g. contracts, orders, etc.). Wouldn't these be populated by different services? Or did you mean something else in this context?

      Author's profile photo Kemin Li
      Kemin Li

      Hey Uladzislau, Thank you for sharing. Can you try the dashboard with sap Fiori client or with IE? I changed parameter useBatch: false in manifest.json file to separate odata call for each card. But it seems it is not working in SAP fiori client with IE or in IE .

       

      Regards,

      Kemin

      Author's profile photo Uladzislau Pralat
      Uladzislau Pralat
      Blog Post Author

      Hi Kemin,

      SAP recommends to use Google Chrome.

      Regards, Uladzislau

      Author's profile photo Jocelyn Dart
      Jocelyn Dart

      If you are currently using IE you can also consider Microsoft Edge. Sunset of IE 11 support has already been announced.

      Author's profile photo Jocelyn Dart
      Jocelyn Dart

      Now added to the the SAP Fiori elements wiki https://wiki.scn.sap.com/wiki/display/Fiori/Fiori+elements

      Thanks for confirming the 40% delay in loading cards with this technique... that's one of the tradeoffs for this approach