SAP Fiori · Lesson

Performance

Quick answer

Prefer Fiori Elements (well-optimised patterns), fetch minimally, page large lists, and keep CDS views efficient.

Key takeaways

Apps that request too much data (no filtering/paging), CDS views that compute expensively without pushdown, and dynamic tiles that…
Use browser developer tools to see OData call timing and payload size, and backend traces (ST05/SAT, HANA plan analysis) for the…
OData efficiency: use $select/$filter/$top so apps fetch minimal data.
Watch out: Over-fetching data without $filter/$top.

Where performance is won

OData efficiency: use $select/$filter/$top so apps fetch minimal data.
Backend/CDS: efficient CDS views and pushed-down aggregation on HANA.
UI5: lazy loading, growing lists, avoiding huge client-side data.
Caching: UI5 app resources cached; use the ABAP/UI5 cache buster correctly.

Common causes of slow apps

Apps that request too much data (no filtering/paging), CDS views that compute expensively without pushdown, and dynamic tiles that fire heavy queries are the usual culprits. On HANA the backend is fast, so needless round-trips and over-fetching dominate.

Measuring

Use browser developer tools to see OData call timing and payload size, and backend traces (ST05/SAT, HANA plan analysis) for the service/CDS. Measure the actual slow request rather than guessing, then fix the specific layer.

Design for performance

Prefer Fiori Elements (well-optimised patterns), fetch minimally, page large lists, and keep CDS views efficient. Small design choices in OData and CDS have large effects on the user-perceived speed of Fiori apps.

Common pitfalls

Over-fetching data without $filter/$top.
Expensive CDS views without pushdown.
Too many/heavy dynamic tiles.

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the course Ask a question

Check your understanding

Which statement is true of Performance?
- A. RFC (Remote Function Call) is SAP’s core mechanism for calling function modules across systems, SAP-to-SAP or…
- B. Apps that request too much data (no filtering/paging), CDS views that compute expensively without pushdown…
- C. BKPF is a key SAP table in FI (Finance).
Show answer
B. Apps that request too much data (no filtering/paging), CDS views that compute expensively without pushdown…
Covered in the “Common causes of slow apps” section of this lesson.
Which of these also applies to Performance?
- A. Learning features, not the end-to-end process.
- B. Missing/wrong condition records, incorrect PO price.
- C. On HANA the backend is fast, so needless round-trips and over-fetching dominate.
Show answer
C. On HANA the backend is fast, so needless round-trips and over-fetching dominate.
Covered in the “Common causes of slow apps” section of this lesson.
Which part of the Learn SAP curriculum covers Performance?
- A. SAP performance tuning
- B. SAP Fiori
- C. SAP glossary
Show answer
B. SAP Fiori
This lesson sits in the SAP Fiori section of the Learn SAP course.

Frequently asked questions

What does Performance mean in SAP Fiori?

Fiori performance depends on the whole stack, the UI5 app, the OData service, and the backend/CDS, plus network and caching. Good performance is designed; poor Fiori performance usually traces to over-fetching or heavy backend queries.

Which transaction codes come up with Performance in SAP Fiori?

Use browser developer tools to see OData call timing and payload size, and backend traces (ST05/SAT, HANA plan analysis) for the service/CDS.

Where does Performance sit in the Fiori stack?

OData efficiency: use $select/$filter/$top so apps fetch minimal data. Backend/CDS: efficient CDS views and pushed-down aggregation on HANA. UI5: lazy loading, growing lists, avoiding huge client-side data.

What tends to go wrong with Performance in SAP Fiori?

Over-fetching data without $filter/$top. Expensive CDS views without pushdown. Too many/heavy dynamic tiles.