SAP FIORI RESOURCE HUB · 2026
SAP Fiori Apps Library: Complete Access Guide (2026)
The SAP Fiori Apps Library is SAP's official catalog for discovering Fiori applications across SAP products. Consultants, functiThe SAP Fiori Apps Library is SAP's official catalog for discovering Fiori applications across SAP products. Consultants, functional teams, Basis administrators, and project leads use it to answer a practical question: does SAP already provide a standard Fiori app for this business process, and is that app available for our SAP release? The library has also evolved, with SAP moving from the older catalog experience to a newer interface. That change matters if you are working from older bookmarks, documentation, or screenshots. This guide explains what the SAP Fiori Apps Library is, how to access and search it, how to interpret app information, and how to use it during S/4HANA planning. It also includes a module-by-module reference so you can quickly identify where relevant Fiori apps may exist. onal teams, Basis administrators, and project leads use it to answer a practical question: does SAP already provide a standard Fiori app for this business process, and is that app available for our SAP release? The library has also evolved, with SAP moving from the older catalog experience to a newer interface. That change matters if you are working from older bookmarks, documentation, or screenshots.
TABLE OF CONTENTS
- What Is the SAP Fiori Apps Library?
- History & Evolution of the Library
- Old Library vs New Library (2026)
- Why SAP Retired the Classic Library
- How to Access the Library
- How to Search and Filter Apps
- Detail View vs List View
- Understanding App Types
- App Recommendations Tool
- SAP Fiori Lighthouse Apps Explained
- Fiori Apps by Module — Quick Reference
- Best Practices for Using the Library in an S/4HANA Conversion
- Common Errors & Troubleshooting
- FAQs
- Related Resources
1. What Is the SAP Fiori Apps Library?
A research and planning tool for discovering Fiori applications — not the
environment where people use them.
The SAP Fiori Apps Library is a searchable catalog for discovering Fiori applications. It is a research and planning tool, not the runtime environment where users actually work with Fiori apps.
That distinction is important because the Apps Library and Fiori Launchpad are often confused. The Fiori Launchpad provides the user-facing entry point for accessing apps, while the Apps Library helps teams determine which apps are available and what is required to implement them.
App information can include the application name and ID, business role, supported SAP product or release, implementation information, and related documentation. Depending on the application, the library can also provide technical prerequisites and other information needed during evaluation.
2. History & Evolution of the Library
The Fiori Apps Library has changed as SAP’s Fiori portfolio has expanded. The
earlier library was hosted at fioriappslibrary.hana.ondemand.com and used a
more traditional, catalog-style interface. SAP later improved browsing and filtering,
followed by the newer experience associated with fal.cloud.sap
Current fal.cloud.sap
This matters for teams still using older documentation — a screenshot from an earlier
implementation project may look very different from today’s interface, even though
the underlying purpose hasn’t changed.
Before you link out
If an old bookmark or internal procedure points to the previous library, verify the destination before using it in a current project.
3. Old Library vs New Library (2026)
The newer experience modernizes how you browse and filter SAP’s
application catalog. If you’re unsure which one you’re on, check the URL
against SAP’s current documentation.
|
|
Classic Library
|
New library
|
|---|---|---|
|
URL
|
fioriappslibrary.hana.ondemand.com
|
fal.cloud.sap
|
|
Interface
|
Legacy catalog experience
|
Modernized interface
|
|
Search
|
Catalog-based browsing
|
Updated search and filtering
|
|
Filtering
|
More limited
|
Broader filtering capabilities
|
|
Best use
|
Older references
|
Current app discovery
|
SAP’s exact transition and retirement status for older URLs can change — confirm
current status against SAP’s documentation before citing a definitive retirement date.
4. Why SAP retired the classic library
The library needed to evolve as SAP’s Fiori portfolio expanded across S/4HANA, cloud products, industries, and deployment models. A modern catalog needs more than a long list of applications — consultants need to narrow results, compare candidates, and understand whether an app fits a particular landscape.
For users, the biggest practical change is familiarity: older screenshots, bookmarks, and instructions may no longer match the current interface. If your team has internal documentation for the Apps Library, review it as part of any S/4HANA or Fiori project rather than assuming the old workflow still applies.
4. How to Access the Library
Browser-based — no SAP GUI required to browse the catalog.
5. How to Search & Filter Apps
Open the library
Go to the current Fiori Apps Library address and open it in a supported modern browser.
Open the library
Some functions or SAP resources may require an SAP Universal ID or additional authentication. If basic catalog browsing is available without authentication, you can begin your research immediately.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Start with the business requirement, then narrow using filters relevant to
your SAP landscape
|
|
|
|---|---|
|
By role
|
Find applications intended for roles like accounts payable specialists, or warehouse users.
|
|
By product / version
|
Check whether an application applies to the SAP product and release you're running.
|
|
By deployment
|
Distinguish cloud vs. on-premise scenarios where filters support it.
|
|
By industry
|
Narrow results when industry-specific applications are relevant.
|
|
By keyword / process
|
Search by the task users need to perform, not just a transaction code.
|
Combining filters works best — e.g. narrow finance apps by business role and SAP product version before reviewing individual applications.
6. Detail View vs List View
Use list view to compare candidates; use detail view to evaluate one specific app.
Detail view shows what you need to investigate an individual app — ID, description, business role, technical requirements, implementation information, and related documentation.
List view is better for scanning several apps quickly and building a shortlist before reviewing each one in depth.
6. Explore SAP Fiori — Choose Your Path
Consectetur adipiscing elit, sed do eiusmodLorem ipsum dolor sit amet, consectetur adipiscing elie lorem ipsum dolor sit amet, consect adipiscing elit sed do eiusmod
Need to find or access a specific Fiori app?
Lorem ipsum dolor sit amet, consect adipiscing elit, sed do eiusmod
Need to find or access a specific Fiori app?
Lorem ipsum dolor sit amet, consect adipiscing elit, sed do eiusmod
Need to find or access a specific Fiori app?
Lorem ipsum dolor sit amet, consect adipiscing elit, sed do eiusmod
7. Understanding App Types
Fiori apps are commonly grouped by the kind of task they suppor
Transactional
Help users complete processes — creating, changing, or approving business documents.
Analytical
Help users monitor performance and decide, using KPIs, charts, and aggregated views.
Fact sheet
Show detailed information about an object — a customer, material, or document — and its related data.
The category gives an early read on intent: transactional apps complete a process, analytical apps focus on monitoring and decisions.
9. App recommendations tool
Identifies candidate Fiori apps from existing SAP usage rather than manual
search alone.
For transformation projects, this helps because the starting point comes from how
users already work — usage data from the current environment can surface
transactions and processes with a corresponding Fiori app.
Treat recommendations as a starting point, not a final decision. Teams still need to
validate business requirements, release compatibility, technical prerequisites, and
user experience before selecting an app.
10. SAP Fiori lighthouse apps explained
A curated set of apps SAP highlights as strong examples of UX and
business value — not the full catalog.
They’re useful for showing stakeholders what a modern Fiori experience looks like.
But if the goal is finding every standard app that fits a process, use the main Apps
Library search rather than limiting research to lighthouse apps.
11. Fiori apps by module
Coverage spans major SAP business areas, but exact availability depends
on product, release, deployment model, and scenario.
Licensing
Licensing depends on the SAP product, application, deployment model, and capabilities being used. Requirements can vary between applications and environments, so organizations should confirm the relevant licensing requirements during planning rather than assuming every Fiori experience follows the same licensing model.
Authorization and roles
Fiori applications rely on appropriate authorizations and Launchpad configuration. Roles, catalogs, spaces, pages, services, and authorization objects can all affect application access. If a user cannot find or launch an application, authorization settings and Launchpad configuration should be among the first areas to review.
Browser support
Modern Fiori environments are designed for current supported browsers, but exact compatibility depends on the SAP product, release, application, and frontend components. Organizations should verify SAP's browser support information for their specific environment instead of relying on a general browser compatibility list.
Mobile access
Many standard Fiori applications provide responsive experiences, but mobile suitability depends on the individual application and business scenario. Custom applications should be specifically designed and tested for target devices when mobile access is required. A Fiori application should not automatically be assumed to be mobile-ready.
Performance and network
Fiori applications use web-based interfaces, making browser performance, network latency, backend response time, frontend configuration, and application design important factors. For remote teams or locations with limited connectivity, these conditions should be evaluated and tested before a wider Fiori deployment is introduced.
Change management and training
Fiori can simplify navigation, but users familiar with traditional transaction codes may still need time to adapt. Role-specific walkthroughs, practical process-based training, and clear communication can help users transition smoothly. Preparing employees before changing the interface can make adoption easier and more effective.
Change management and training
Fiori can simplify navigation, but users familiar with traditional transaction codes may still need time to adapt. Role-specific walkthroughs, practical process-based training, and clear communication can help users transition smoothly. Preparing employees before changing the interface can make adoption easier and more effective.
Change management and training
Fiori can simplify navigation, but users familiar with traditional transaction codes may still need time to adapt. Role-specific walkthroughs, practical process-based training, and clear communication can help users transition smoothly. Preparing employees before changing the interface can make adoption easier and more effective.
These are representative categories, not a definitive list. Always confirm the exact app ID and availability for your SAP release.
12. Best practices for an S/4HANA conversion
Use the library early, validate findings throughout, and document gaps before development decisions are made.
- Start from real business usage instead of searching randomly through the catalog.
- SAP GUI is desktop-only; Fiori apps are responsive across devices.
- SAP GUI shows every field; Fiori scopes the screen to one task.
- Classic GUI still exists — most landscapes run both side by side.
13. Common errors & troubleshooting
Most issues trace back to outdated links, overly restrictive filters, or a
release mismatch.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Open the library
Go to the current Fiori Apps Library address in a supported modern browser.
Change one filter at a time when troubleshooting — it’s the fastest way to isolate what’s excluding an application.
14. Frequently Asked Questions
Is SAP Fiori free?
Fiori is not generally purchased as one standalone product. Many Fiori applications are delivered with the relevant SAP solution, but licensing can depend on the specific application, product, deployment model, and underlying capabilities. Verify the licensing position for your specific scenario.
What's the difference between SAP Fiori and the Fiori Launchpad?
Fiori is SAP’s broader user experience and design system, while the Fiori Launchpad is the role-based application shell and entry point through which users access applications and navigation. Fiori describes the broader experience; the Launchpad provides the environment through which that experience is accessed.
Is SAP Fiori the same as SAPUI5?
No. SAPUI5 is SAP’s web UI development framework used to build many Fiori applications. Fiori is the broader design and user experience system, while SAPUI5 is one of the core technologies used to implement that experience.
Do I need SAP Fiori for S/4HANA?
S/4HANA can support classic SAP GUI-based applications for certain functions, but Fiori is the primary modern user experience for many S/4HANA business processes and is the standard user experience in many S/4HANA Cloud scenarios. The exact application experience depends on the S/4HANA edition and release.
Can I customize SAP Fiori apps?
Yes. Depending on the application and SAP environment, organizations can use in-app extensibility, developer extensibility, or side-by-side extensibility to adapt or extend functionality. Custom applications can also be developed using technologies such as SAPUI5 and Fiori elements when standard applications do not meet the business requirement.
Does SAP Fiori replace SAP GUI completely?
Not entirely. Fiori provides modern application experiences for many business processes, but classic SAP GUI remains relevant for various back-office, technical, and configuration activities. SAP environments can therefore use Fiori and SAP GUI alongside each other.
How long does it take to roll out SAP Fiori?
There is no single timeline. A limited rollout using a small number of standard applications can be relatively straightforward, while an enterprise-wide deployment involving authorization design, Launchpad configuration, integrations, testing, custom applications, change management, and training can take considerably longer. The scope and complexity of the SAP landscape determine the actual timeline.
More Questions?
We’re always ready to help you out.
15. Related resources
SAP Fiori Launchpad TCode: Complete Reference List
SAP Fiori Launchpad TCode: Complete Reference List
SAP Fiori Launchpad TCode: Complete Reference List
Found a process the standard library doesn't cover?
Our SAP Fiori team can help evaluate the gap and determine whether extensibility or custom development is the right approach.