SAP Fiori · Architecture & System Landscapes

A plain ABAP environment runs transactional Fiori apps fine on its current non-HANA database. The team wants to add fact sheet apps without changing the DB. Why won't that work?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Architecture & System Landscapes

An admin says SAP Smart Business content on HANA XS is independent of HANA Live, so HANA Live can be skipped in the install. Why is that wrong?

Name the five layers of a classic SAP Fiori system landscape, from the user's browser down to the data.

You must run analytical Fiori apps but the ABAP back end is on a non-HANA database. Integrated or side-by-side HANA XS — which does that force, and what cost does it impose?

Sizing a landscape that must eventually run all three classic Fiori app types: which database does that commit you to, which single app type would have left the choice open, and why can't you defer the decision?

A fact sheet app loads slowly and you want to trace the request path. Unlike transactional apps, what protocol does it use and which component does the request hit before HANA?

Of the three classic Fiori app types, exactly one requires SAP HANA XS. Which one, and what does XS do that makes it mandatory only there?

Start learning today

Free to start — download the app or use it in your browser.