2026-11-20
SAP Fiori – Simply Explained

Show notes
SAP Fiori shows up in almost every SAP meeting, and almost nobody stops to explain it. It is a design system, a launchpad and a set of tools, all at once. In this episode of Simply Explained you will learn:
- What SAP Fiori really is: a design system, a launchpad and a set of developer tools
- Why SAP needed a new face and how Fiori grew from 25 apps in 2013
- The five ideas behind every Fiori screen: role-based, responsive, simple, coherent and delightful
- How the launchpad works and why it is where your SAP day starts
- Where Microsoft fits in, from Entra ID single sign-on to what sign-in does not solve
- The honest limits and common mistakes in Fiori rollouts
Simply Explained by M365.FM breaks down Microsoft 365, Azure and modern IT topics in clear, jargon-free language. Hosted by Mirko Peters. Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support. This episode includes AI-generated content.
Apple Podcasts · YouTube · Deezer
Host: Mirko Peters
Guests
Guests in this episode:
Transcript
Read the full transcript
Speaker 1: Sippy Fury gets said in almost every SAP meeting, and almost nobody stops to define it. You have probably seen the colorful tiles without knowing what runs them. Fury is the way SAP apps are designed, the launchpad that pulls them together, and the tools developers use to build them. By the end, you will know how people use it every day, where Microsoft fits in, and where it honestly falls short. So let's take it one plain step at a time. Fury is not a single program you download or one screen you log into. It is a design system, a shared set of rules for how SAP apps should look and behave on any device. When a company says it is doing Fiori, it usually means three things at once. That means a new look for its screens, a new homepage that gathers them, and a new set of tools for building them. That is the part people miss. The tiles are only the surface. Under them sits a whole approach that shapes what you see and what happens when you click. Once you know that, the rest of Fiori stops feeling mysterious. Fiori also has a version story that confuses newcomers, so here is the short form. It began in 2013 as a small set of 25 apps. It grew through design generations that SAP calls Fiori 2.0 and Fiori 3. Today it is simply the standard phase of SAP's main product, S slash 4Herna. When people argue about Fiori versions, they are usually arguing about a look, not about three separate products. Before, Fiori using SAP usually meant staring at a gray screen full of transaction codes. A transaction code is a short command, almost like a secret handshake, that opens one specific corner of the system. You either memorize the codes or kept a cheat sheet nearby, and even simple tasks could take a string of extra clicks. Imagine you only need to check one customer order. The old way you log in and type a code. Then you land in a dense table, filter it, and hunt for the single line you care about. None of that was built with a phone in mind, so if you stepped away from your desk, the work simply waited until you got back. That gap is exactly what Fiori was built to close. SAP looked at the clean, simple apps people already used on their phones and decided that business software should feel that calm too. SAP never wanted to bolt on more features. It wanted to get the tool out of the way so the real work could come forward. The change sounds small until you watch it in practice. A task that used to take five screens and a memorized code can become one tile, one tab, and one clear form. For a company, that adds up quickly because people spend less time learning the software and more time doing the job it exists to support. There is a practical reason this matters beyond comfort. Every extra click and every confusing screen is a chance to enter the wrong number or skip a step. When the interface is built around the task, the process itself gets keener, and that is the argument SAP makes for moving to Fiori. When SAP designed Fiori, it settled on five ideas that every Fiori app is supposed to follow. They are worth knowing because they explain why Fiori looks the way it does. They also give you a simple test to hold any app against. First, Fiori apps are role-based, which means each one centers on a job rather than the entire system. An accounts payable clerk and a warehouse manager open the same launchpad. Each of them sees only the apps their role needs. That one idea drives a lot of what comes later because it separates a tool that hands you your work from one that makes you hunt for it. Second, Fiori apps are responsive, so the same screen rearranges itself to fit a desktop, a tablet, or a phone. Third, they are simple and each app does one narrow job well instead of trying to do everything at once. Fourth, they are coherent, so once you learn how one app works, the next one already feels familiar. You spend your attention on the work rather than on the buttons. The fifth idea is the one people smile at, because SAP says fury apps should be delightful. That is SAP's way of saying the software should come across as calm and clear rather than heavy. Treat all five as a quick test, because when an app feels clumsy or crowded, it is usually breaking one of them. If those five sound familiar, that is because they echo how good consumer software is built. SAP did not invent the idea of a clean, role-based app. It borrowed the idea and applied it to payroll runs, purchase orders, and inventory counts, which is a much harder place to keep things simple. One caution here matters. The five ideas describe intent, not a guarantee, and not every app in the Fiori family lives up to them. Some older apps were moved onto a launchpad without being redesigned. That is worth remembering when a colleague calls an app Fiori and it still looks like it came from another decade. Now, the place where everything comes together is the launchpad. Think of it as your personal homepage for SAP, a page of tiles where each tile opens one app or one task. You sign in once and the launchpad shows the tiles your role has been given, so you are not scrolling past things you will never touch. The Launchpad includes a search that reaches across connected SAP systems? That matters more than it sounds, because in a large company, the thing you need often sits in a system you did not expect. You can personalize the page, too, moving tiles around so your most used tasks sit where your eyes land first. For years, Launchpads grouped those tiles into simple buckets called groups. SAP has since moved to a cleaner model called spaces and pages, where tiles are organized into areas and subpages that match how people really work. The older group's layout is now deprecated, which means it is on the way out, and the classic homepage will be removed in a future version. One more thing about the Launchpad is easy to miss. It does not only hold modern Fiori apps, because it can also hold older SAP screens, older web applications, and custom apps a company built for itself. People often call anything they reach from the Launchpad a Fiori app, even when it technically is not one. A cloud chapter fits here too, and it takes one sentence. SAP's newer cloud service, SAP Build Work Zone, is positioned as the successor to the classic launchpad, pulling SAP apps and third-party tools into a single workspace. If your company runs SAP in the cloud, the launchpad you use may already be that newer service and the idea stays the same even when the name changes. So the launchpad works less like a single product and more like a front desk. It sets out what you see when you arrive and it lets you search the whole building. It hands you the right tools for your role without making you memorize a single code. So it is worth knowing what makes those tiles work, and you do not need to be a developer to follow it. Three pieces sit behind almost every Fiori app. Once you can name them, the jargon around Fiori gets a lot less intimidating. The first is SAPUI5, the JavaScript framework behind most Fiori apps. In plain terms, it is the toolkit SAP uses to build web screens that behave the same way everywhere, on any browser and any device. Part of their toolkit is open source under the name OpenUI5, which means anyone can read the code and build with it. The second is SAP Fiori Elements. This is a low-code approach where developers describe what an app needs and the framework builds the screens from ready-made templates called floor plans. It cuts down on hand coding and it keeps apps consistent because they all start from the same proven patterns instead of a blank page. A developer still decides what data matters and how the app should behave, but the look and the layout come almost for free. The third piece is OData, the common language a Fiori app uses to ask the SAP backend for data. When you open a list of sales orders, the app sends an OData request, the SAP system answers, and the screen fills in with real numbers. OData is worth remembering because when a Fiori app loads slowly or shows nothing at all, The problem usually lives in the service behind the screen. Developers build and test these apps in a cloud workspace called SAP Business Application Studio, which comes with the templates and tools already set up. Put the pieces together, and the picture gets clearer, because SAPUI5 and Fiori elements build what you see, and OData feeds it with live data. The launchpad hands it to you at the right moment, and the colorful tiles are just the friendly face on a fairly ordinary set of moving parts. There's one more layer you will hear about, and it is the one nobody notices. In many setups, a Fiori front-end server sits between the apps and the SAP business system, handling the launchpad, the logins, and the routing of those OData calls. You rarely think about it when it works. You hear about it constantly when it does not because it decides whether the whole experience feels fast or slow. None of those names need to live in your head forever, and the useful takeaway is simpler. A Fiori app is a web app that talks to SAP through a standard data service and it is built from reusable parts rather than from scratch. Hold on to that and the acronym stock being scary. Some Fiori apps are transactional and in those you do something like approve a purchase order or submit a leave request. Others are analytical and in those you read numbers like a dashboard tracking this quarter's spend against budget. A third kind, the fact sheet, is read-only and it shows the details of one thing such as a customer, a supplier, or a piece of equipment. Picture a buyer starting her morning. She opens the launchpad, taps an analytical tile, and sees that one supplier is running late on three deliveries. She opens that supplier's fact sheet to check the contact name, then jumps into a transactional app to push the delayed orders along. In one short loop, she saw the number, understood the detail, and took the action, which is the whole idea of Fiori in a single story. The pattern repeats across roles. A plant supervisor uses analytical tiles to watch output, then transactional tiles to confirm a production step. A finance analyst checks a customer's fact sheet before releasing a credit block. The apps change from person to person, but the rhythm stays the same. And that sameness is what makes Fiori easier to learn than the old screens. It also changes how fast a task fields, because the app opens on the exact list you need, and the detail you want is one tap away. You stop navigating and start deciding, and that tends to be the moment someone finally says they understand why the company bothered with Fiori at all. One honest note on this part. The three flavors describe how apps behave, not how good they are. and one of those action apps can still be slow. An analytical dashboard is no better than the data feeding it. Fiori gives the work a better shape, and the quality of what happens inside that shape still depends on the system behind it. Now here is where the Microsoft side enters the picture, and the cleanest place to see it is at sign-in. In many companies, people already carry a Microsoft account for email, Teams, and documents, and that same account can be the one that opens Fiori. Microsoft EntraID, Microsoft's cloud identity service, can act as the identity provider for SAP Fiori using a standard called SAML for single sign-on. Setting it up is a two-sided job. On the Microsoft side, EntraID holds the certificate and the claims that describe who the user is. On the SAP side, the system is configured to trust EntraID and the two sides trade the details through metadata files. The payoff is simple and it matters. A user signs in once with their Microsoft account and lands in Fiori without typing a second password. Fewer passwords means fewer support tickets and people spend their energy on the job instead of the login screen. The security side gains as well because one place decides who gets access and that access can be reviewed or taken away in one spot. One limit is worth stating clearly and it trips up a lot of teams. Signing in is not the same as being allowed to do everything. Microsoft proves who you are and SAP still decides what each person can see and do once they are inside. Both sides matter and treating them as one thing is a common and costly mistake. This sign-in link is usually the first place a company connects its Microsoft world to its SAP world. That is why it shows up so often in mixed projects. It is a small concrete win and it tends to open the door to bigger conversations about identity and data. If you take one thing from this section, Let it be this. The Microsoft connection you will meet first is identity, not data. Now let's be honest about the parts that trip people up because the clear picture beats a sales pitch every time. The first mistake is treating Fiori like a single app or a small project. Fiori spans a design system, a launchpad, and a build toolkit, and a real rollout touches roles, permissions, layout, and the backend services that feed the apps. When a team budgets for a redesign and ends up rebuilding half the access model, that is usually this mistake showing up late. The same mistake is expecting Fiori to wipe out the old screens everywhere. It does not. SAP GUI still runs technical transactions and system administration, and some older processes have no Fiori equivalent yet, so for a while the two live side by side. That is normal, and planning for it beats pretending it will not happen. The third mistake is assuming that Microsoft sign-in replaces SAP roles. It replaces the password prompt and nothing more, because EntraID proves your identity and SAP still decides what you are allowed to touch. Getting that wrong leads to a security review nobody enjoys. There are moving parts to watch as well. The launchpad layout has shifted from groups to spaces and pages and the Fiori version labels overlap in practice. What you actually get depends on your S Flash 4 HANA release and whether you run it in the cloud or on your own servers. Nothing there should stop you from adopting Fiori, but all of it should make you check the details before promising a date. One more limit surprises people. An app is only as good as the service that feeds it, and if that service is slow or incomplete, the app looks polished and still feels wrong. So when a project stalls, look behind the tiles before you blame the design. The simplest way to stay out of trouble is to treat Fiori as a way of working rather than a product you install. Once you do that, the questions get better, you stop asking whether Fiori is done, and you start asking which roles, which apps, and which services are ready to move. So let me pull the whole thing together for you. SAP Fiori is not one app, it is a shared design approach, a launchpad that gathers your apps onto one page and a set of tools that build modern screens on top of SAP. It gives SAP a cleaner role-based face and it started small in 2013 before growing into the standard look of SS4 HANA. For a lot of companies, your Microsoft account is the key that opens the door. The reason this matters is fairly simple. A tool that people actually want to use gets used properly and a tool they fight gets worked around. I'm furious SAP's attempt to win that fight and knowing it's three parts is what lets you tell a strong rollout from a shallow one. None of this is magic, and it is not finished either, but it is a practical direction. The question I want to leave you with is this. If your team started a Fiori rollout tomorrow, which of those three pieces would give you the most trouble first, the look, the launchpad, or the tools? If this made the topic feel less intimidating, subscribe to M365FM to master the tools and the mindset shaping the future of work.