From SAP GUI to Fiori: how the way Supply Chain teams work in SAP changed

Cover: from SAP GUI to Fiori, evolution of the SAP user experience
SAP ExplainedSAP GUI · Fiori · S/4HANA · MRP✓ Sources verified Nov 11, 2026
In 30 seconds
  • In R/3 and ECC, working in SAP meant memorizing transaction codes (MD04, MD07…) in the desktop SAP GUI.
  • In 2013 SAP launched Fiori: 25 simple web apps. Today S/4HANA offers more than 3,000 apps organized into more than 600 roles.
  • SAP GUI did not disappear: S/4HANA still complements Fiori with more than 10,000 classic screens.
  • The real shift: from “which transaction do I run?” to “which exception do I handle today?“, now with an AI assistant (Joule) on top.

If you have worked in SAP for years, your muscle memory probably looks like /nMD04, Enter, material number, plant. It works, but you have to know exactly what to look for. With S/4HANA, SAP changed the front door: planners no longer start from a transaction but from a role-based screen that shows what is wrong. Here is how that happened and what it means for your team. For the full S/4HANA context, see our article SAP S/4HANA explained.

The timeline: from transactions to apps

R/3 & ECC
SAP GUI is the only door: Easy Access menu, transaction codes and dense screens built for expert users.
May 2013
SAP unveils Fiori at Sapphire: 25 HTML5 apps for 4 user types (manager, sales rep, employee, purchasing agent) running on PC, tablet and phone.
2014–2015
The catalog grows fast: over 300 apps one year after launch and over 500 the year after.
2016
Fiori 2.0 is shown with S/4HANA and SAP declares it the design system for all its products.
2022
The Horizon visual theme becomes generally available (SAPUI5 1.102).
Jan 2023
SAP GUI for Windows 8.00: the first true 64-bit release. The GUI is alive and maintained.
Sep 2023
SAP announces Joule, its generative AI assistant, to be embedded across its applications, supply chain included.
Today
S/4HANA delivers more than 3,000 Fiori apps in more than 600 roles, with the launchpad as the entry point.
25
Fiori apps at launch in May 2013 (InfoWorld / SAP)
3,000+
Fiori apps in S/4HANA, grouped into 600+ business roles (SAP Community)
10,000+
classic screens S/4HANA keeps as a complement (SAP Community)

Before vs. now: a day in the life of an MRP planner

TaskBefore (SAP GUI in ECC)Now (Fiori in S/4HANA)
Entry pointEasy Access menu and transaction codes→ Fiori launchpad with role-based spaces and pages
Run MRPClassic MRP from the transaction→ MRP Live (MD01N) or the “Schedule MRP Runs” app
Find shortagesMD04 material by material, or MD07 as a collective list→ “Monitor Material Coverage”: every material in your area, filtered by issue
Fix the issueJump across several transactions→ “Manage Material Coverage”: see the issue and act from the same app
MRP lists (MD05/MD06)Static snapshot of the last run→ MRP Live does not generate them; you check the live situation
DevicePC with the client installed→ Browser on PC, tablet or phone

Note: the stock/requirements list (MD04) still exists and also opens from Fiori as “Monitor Stock/Requirements List”. The transaction doesn’t go away; it just stops being the starting point.

The building blocks of the Fiori experience

1 · Role
Business roles

Each user sees only the apps for their job (e.g. material planner). This is Fiori’s “role-based” principle.

2 · Entry
Fiori launchpad

The home page with apps, search and notifications. From S/4HANA 2021, SAP recommends organizing it with spaces and pages.

3 · Exception
Monitoring apps

They show what is wrong first (shortages, delays) so planners can manage by exception.

4 · Assistant
Joule

SAP’s AI assistant, designed to answer questions and suggest actions inside the applications.

A useful analogy: SAP GUI is a warehouse where everything has its place, but you must know the exact aisle and rack. Fiori is the DC supervisor’s board: it lights up in red what needs attention and takes you straight to fixing it.

What it means for your Supply Chain operation

The interface change is really a change in how people work.
  1. Design roles before screens. Define which apps each job needs (planner, buyer, warehouse clerk) and build the launchpad with spaces and pages for that role.
  2. Set up responsibility correctly. Coverage apps depend on each planner having their plants and MRP controllers assigned; get that wrong and they see noise or nothing.
  3. Don’t switch off the GUI overnight. Classic transactions remain available; run both and migrate by process, starting with those that generate the most exceptions.
  4. Train the “why”, not just the “where”. Users who looked up data in MD04 now need to learn to prioritize exceptions; that is where the time savings really come from.
Are your planners still using S/4HANA as if it were ECC?
We review at no cost how they use Fiori and SAP GUI today and tell you which apps and roles would save them the most time.
Book your assessment

This article is for information purposes. App availability, visual themes and AI features depend on your S/4HANA version, deployment model and licensing; always check SAP’s documentation for your release.

Related Posts