S/4 Hana FIORI performance and Accessing Data
Hey all
New here but working on a sap S/4 Hana implementation.
Hoping we could get some clarity on an important subject: FIORI performance and accessing data in SAP.
In ECC we typically accessed data via GUI, whether it be SE16 or other GUI ALV reports.
Most of the time we want to analyze and export line item reports for external statutory reporting requirements or for our auditors to upload into their external systems.
As we move to S/4, we’re being told to move away from GUI and use FIORI.
When we look at FIORI, SAP supplies Analytical Query reports in a Multi-Dimensional WebDynPro report format and also other reports in a classic FIORI Elements Analytical List format.
The data we specifically want to analyze and/or extract comes from ACDOCA so as you can imagine the data volume can be quite high.
SAP standard apps like the Journal Entry Analyzer or Line Items in General Ledger can be quite slow when you deal with a lot of fields and a lot of data.
We’ve asked SAP support about this and they’ve simply told us that we’re accessing too many fields and that FIORI is not good for exporting to excel and that we should either give users (eg auditors) access to the system or use other external tools to export the data.
This is confusing to us. Our implementation only uses SAP S/4 Hana. You would think that you would be able to export directly from the system without issue.
We’re not talking a lot of fields here. We can get the Journal Entry Analyzer app to time out with 40-60 fields in FIORI but it takes a second to load the underlying data from the CDS View using SE16N.
We’re also not talking a lot of data either (our dev environment has very limited data and we are hitting performance issues accessing it in FIORI).
SAP support tells us that our use case is unique to us. That no other customer requires this ability to access that many fields and export it.
We find this really difficult to accept because this is a pretty universal practice of wanting to analyze and extract data.
If we can’t do this from FIORI, moving forward how can we ever expect new tools like Joule to be able to analyze the data in real time? Joule won’t be in GUI.
Is anyone else encountering performance issues with FIORI? How are you dealing with that?
We’ve been able to replicate these issues in SAP’s public test demo systems as well to rule out our system configuration being the issue.
You would think that SAP would want their products to be as performant as possible as it would make their products even more attractive and users would complain less about the noticeable performance degradation they see migrating from GUI to FIORI (SAP support has also confirmed this last point about GUI being much faster than FIORI).
We would love to hear the communities thoughts on this.
Is this really an ‘us’ (you’re using the system wrong) problem or an issue that others are also experiencing with SAP S/4 and FIORI?
Note: we have already engaged with multiple SAP resources on this issue over the course of many months and still cannot get a clear answer on how the system should perform and also how it can meet these data extraction requirements.
Thanks in advance!