Lesson 5 of 5
Front ends: SAP GUI and SAP Fiori
9 min
Users reach SAP S/4HANA in two main ways: SAP GUI, the classic installed client with transaction codes, and the SAP Fiori launchpad in a browser, with role-based apps. Both end up in the same application server work processes, but they travel different paths to get there, and that matters for administration, security and test automation.
| Front end | How it connects | Typical users | What you see |
|---|---|---|---|
| SAP GUI for Windows | Installed client using SAP's own protocol to the dispatcher, often through the message server and a logon group | Power users, consultants, Basis | Transactions entered by code, such as VA01 |
| SAP GUI for HTML | Browser through ICM; classic transactions rendered as web pages | Users who need classic transactions without an installed client | Classic screens in a browser tab, often launched from a Fiori tile |
| SAP Fiori launchpad | Browser through HTTPS to ICM; apps read and write data through OData services | Most business users | Role-based tiles and apps, such as Manage Sales Orders |
The SAP GUI path
- SAP Logon entryPoints to a message server and logon group (or directly to one instance)
- Message serverChooses an application server instance in the group
- DispatcherReceives the request and assigns a dialog work process
- Work processRuns the transaction and returns the screen
The Fiori path
A Fiori app is a web application that runs in the browser. It loads its user interface files from the server and then calls OData services to read and change data. Requests travel over HTTPS, usually through a load balancer such as SAP Web Dispatcher, to the ICM of an application server instance, which passes them to a work process. The launchpad decides which tiles a user sees from their business roles, and the back-end authorizations decide what the services let them do.
- BrowserUser opens the launchpad URL
- Web dispatcherDistributes HTTPS requests across instances
- ICMReceives the request on the application server instance
- Front-end componentsLaunchpad content, app files and OData service handling
- Back-end logicABAP and CDS views read and write the data in SAP HANA
The front-end server: embedded or hub
The components that serve Fiori (launchpad content, UI files and the gateway for OData services) are known together as the SAP Fiori front-end server. It can be deployed embedded, inside the SAP S/4HANA system itself, or as a hub, a separate system in front of one or more back ends. SAP's guidance is that embedded deployment is the recommended setup for SAP S/4HANA: one system to administer, no remote calls between front end and back end, and roles and authorizations in one place. A hub can still make sense for specific needs, such as keeping back ends in a separate network zone.
What would you do?
After a release, Contoso's Fiori app Manage Sales Orders works for testers in CMQ but shows no tile for Maria's team in production CMP. SAP GUI transactions work for everyone. Where should Basis look first?
- SAP GUI connects to the dispatcher, usually via the message server and a logon group.
- Fiori runs in the browser and calls OData services over HTTPS through a web dispatcher and ICM.
- The Fiori front-end server can be embedded or a hub; SAP recommends embedded for SAP S/4HANA.
- Tiles depend on business roles and launchpad content; record SID, client and front end in evidence.
Check your understanding · not graded
Lesson check
1. Which front end loads role-based apps in a browser and calls OData services?
2. What is SAP's recommended Fiori front-end server deployment for SAP S/4HANA?
3. Which component receives Fiori HTTPS requests on the application server?
4. A tile is missing in production but the transaction works. What is the likely cause?