We’re running the Fiori requirement collection app in SAP PLM 2022, and it’s taking 25-35 seconds to load when users have access to large product portfolios (500+ products with 2,000+ requirements). The initial data load seems to be the issue.
I’ve looked at the OData service tracing and see that we’re pulling all requirements upfront rather than using server-side paging. The underlying CDS views also seem inefficient - they’re joining multiple tables without proper filtering. Our users are complaining about the wait time, especially on mobile devices.
What’s the best approach to optimize this? Should we focus on CDS view optimization, implement proper paging, or both?
Check the SAP Gateway cache configuration. In transaction /IWFND/MAINT_SERVICE, you can enable caching for your OData service. For relatively static requirement data, a 15-30 minute cache can dramatically improve perceived performance. Just ensure you have proper cache invalidation when requirements are updated.
On the client side, make sure you’re using the growing list pattern in UI5 rather than loading all items at once. Set the growing threshold to 50-100 items and enable scroll-to-load. This provides a much better user experience even if the backend is slow. Also check if you’re using two-way data binding unnecessarily - one-way binding is much faster for read-only requirement lists.
Use transaction /IWFND/ERROR_LOG to trace the actual OData service execution. You’ll see exactly where time is spent - often it’s in authorization checks if you have complex authorization objects. Consider implementing authorization buffering or simplifying your authorization model for read operations on requirements.