SAP Presentation layer
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.
The SAP presentation layer is what the user sees: SAP GUI on the desktop as Windows, Java or Web GUI, the Fiori launchpad in a browser, or a custom UI calling the backend over OData. It sends actions to the application layer and displays results, holding no business logic, so the UI could move to Fiori without a backend rewrite.
- 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.