- 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
Before vs. now: a day in the life of an MRP planner
| Task | Before (SAP GUI in ECC) | Now (Fiori in S/4HANA) |
|---|---|---|
| Entry point | Easy Access menu and transaction codes | → Fiori launchpad with role-based spaces and pages |
| Run MRP | Classic MRP from the transaction | → MRP Live (MD01N) or the “Schedule MRP Runs” app |
| Find shortages | MD04 material by material, or MD07 as a collective list | → “Monitor Material Coverage”: every material in your area, filtered by issue |
| Fix the issue | Jump 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 |
| Device | PC 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
Each user sees only the apps for their job (e.g. material planner). This is Fiori’s “role-based” principle.
The home page with apps, search and notifications. From S/4HANA 2021, SAP recommends organizing it with spaces and pages.
They show what is wrong first (shortages, delays) so planners can manage by exception.
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
- 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.
- 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.
- 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.
- 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.
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.
- SAP Community – SAP Fiori: how it started and where it’s going
- InfoWorld – SAP unveils consumer-friendly Fiori app suite (2013)
- SAP Community – SAP Fiori for SAP S/4HANA
- SAP Community – SAP Fiori evolution: Horizon now generally available
- SAP Community – SAP GUI for Windows 8.00 is coming on 27th of January 2023
- SAP News – SAP announces new generative AI assistant Joule
- SAP Learning – Planning Using MRP Live
- SAP PRESS – How to evaluate MRP results with SAP S/4HANA









