SAP architecture · Lesson

Presentation layer

Quick answer

Because presentation is decoupled from logic and data, SAP can evolve the UI (from GUI to Fiori) without rewriting the backend, and multiple front-ends can share one system.

Key takeaways

This tier is what the user sees and touches: the SAP GUI on the desktop, or the Fiori launchpad and apps in a browser.
The presentation layer should be thin: heavy logic belongs on the application server, not the client.
SAP GUI: classic desktop screens (Windows, Java, or Web GUI).
Watch out: Putting business logic in the UI, it belongs on the app server.

What the presentation layer is

This tier is what the user sees and touches: the SAP GUI on the desktop, or the Fiori launchpad and apps in a browser. It sends user actions to the application layer and displays the results, but it contains no business logic itself, that lives on the application tier.

Front-end options

SAP GUI: classic desktop screens (Windows, Java, or Web GUI).
SAP Fiori / UI5: modern, role-based web apps.
Third-party and custom UIs talking to the backend via APIs/OData.

Why separation matters

Because presentation is decoupled from logic and data, SAP can evolve the UI (from GUI to Fiori) without rewriting the backend, and multiple front-ends can share one system. This three-tier separation is a core architectural strength.

Performance considerations

The presentation layer should be thin: heavy logic belongs on the application server, not the client. Well-designed apps minimise round-trips to keep the experience responsive.

Common pitfalls

Putting business logic in the UI, it belongs on the app server.
Chatty apps with too many backend round-trips.
Confusing GUI and Fiori as if interchangeable.

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 Presentation layer?
- A. It sends user actions to the application layer and displays the results, but it contains no business logic…
- B. SAPUI5 (and its open-source core, OpenUI5) is the JavaScript framework Fiori apps are built with.
- C. SAP CO (Controlling) is the module for internal management accounting, tracking, planning and analysing costs…
Show answer
A. It sends user actions to the application layer and displays the results, but it contains no business logic…
Covered in the “What the presentation layer is” section of this lesson.
Which of these also applies to Presentation layer?
- A. No/weak credit checks, exposure to bad debt.
- B. Choosing greenfield vs brownfield without analysis.
- C. This three-tier separation is a core architectural strength.
Show answer
C. This three-tier separation is a core architectural strength.
Covered in the “Why separation matters” section of this lesson.
Which part of the Learn SAP curriculum covers Presentation layer?
- A. SAP examples
- B. Getting started
- C. SAP architecture
Show answer
C. SAP architecture
This lesson sits in the SAP architecture section of the Learn SAP course.

Frequently asked questions

What does the term Presentation layer refer to in SAP?

The presentation layer is the top tier of SAP’s architecture, the interface through which users interact with the system. It is deliberately separated from business logic and data so the same backend can be reached through different front-ends.

What is the Fiori angle on Presentation layer?

This tier is what the user sees and touches: the SAP GUI on the desktop, or the Fiori launchpad and apps in a browser.

What is another point to note about Presentation layer?

Because presentation is decoupled from logic and data, SAP can evolve the UI (from GUI to Fiori) without rewriting the backend, and multiple front-ends can share one system.

What tends to go wrong with Presentation layer?

Putting business logic in the UI, it belongs on the app server. Chatty apps with too many backend round-trips. Confusing GUI and Fiori as if interchangeable.