SAP Fiori Elements Is Not Clean Core

In 30 seconds

What it is SAP Fiori elements is the most common UI technology in the September 2026 export, covering 1,547 of 3,185 apps, but it is a rendering framework label, not evidence of clean-core readiness. Keep the clean-core assessment separate from UI technology and inventory the actual FQEVENTS implementations, user exits, modifications and integration dependencies before choosing a refactoring design.

You use it when Someone on the project is treating a high count of SAP Fiori elements apps as evidence that clean-core extensibility work is smaller than expected, and you need this site's catalogue analysis on record before scoping the technical debt workstream.

Guide covers Migration / Clean Core and Technical Debt

Why it matters

A clean-core business case built on the app catalogue’s UI-technology column looks encouraging at first glance: 1,547 of 3,185 apps in the export, roughly half, carry SAP Fiori elements as their UI technology label. It is tempting to read that as “half our landscape is already clean core.” This site’s catalogue analysis blocks that reading directly: a Fiori elements record establishes how the screen is rendered, not whether the underlying app exposes a released API or extension point for customer code. The technical debt that actually blocks a clean-core transition sits in FQEVENTS implementations, user exits, modifications and integration dependencies, none of which this column describes.

UI technology distribution across the 3,185-app export

Exact UI technology	Records
SAP Fiori elements	1547
SAP Fiori (SAPUI5)	883
SAP Fiori: Generic Job Scheduling Framework	271
SAP Fiori: SAP Smart Business generic drill down app	151
SAP Fiori app variant	123
SAP Fiori elements: Overview Page	66
SAP Fiori: Generic Application Log Framework	43
SAP Fiori: Manage Workflow	35
SAP Fiori: My Inbox	27
SAP Fiori: Analysis Path Framework (APF)	26
SAP Fiori elements for CoPilot	11
SAP Fiori: SAP Smart Business tile & custom drill down app	2

Decide

Evidence type	Establishes clean-core readiness?	What to check instead
UI technology value (for example “SAP Fiori elements” or “SAP Fiori (SAPUI5)”)	No	The app’s released API and extension-point documentation for your target release
Lifecycle status (Available, Deprecated, Available with Successor)	No	Whether the app itself, or its successor, actually exposes a supported extension point
Backend stack value	No	The real FQEVENTS implementations, user exits, modifications and integration dependencies present in your system
A documented, released API or extension point for the specific app or process	Yes	Confirm the extension point covers your actual customization, not only the generic process it was built for

Do this

Discover · ABAP lead — Inventory the actual FQEVENTS implementations in your FI-CA landscape: which events are implemented, why, and whether the same outcome is achievable through a released extension point.
Discover · ABAP lead — Inventory user exits and modifications across the technical landscape as a whole; do not assume a Fiori-elements-heavy app population reduces this work.
Prepare · Solution Architect — Inventory integration dependencies — interfaces, custom RFCs, custom reports — that any refactoring design would need to preserve or replace.
Explore · ABAP lead — Choose a refactoring design only after the first three steps are complete, and only where a released extension point actually exists for the customization in question.

For a utility, technical debt concentrates in FI-CA events (FQEVENTS) and IS-U enhancements, not in the Fiori layer. A billing or invoicing process that looks fully modernized because its overview and exception apps use SAP Fiori elements can still depend on a heavily customized FQEVENTS implementation underneath. See SAP FI-CA basic functions for the fundamentals of the events concept this inventory has to cover.

Do not read the 1,547 SAP Fiori elements apps, or any other row in the table above, as apps that are ready for clean extensibility. The count describes a rendering framework choice made by SAP for the app’s UI. It says nothing about whether that app, or the process behind it, has a released extension point for your customization.

The UI technology distribution above — 12 exact values across 3,185 records, led by SAP Fiori elements at 1,547 and SAP Fiori (SAPUI5) at 883 — comes from the SAP export of September 2026 for product 2025 (Private Cloud). The export has no column for extension points, released APIs or customer code, and 140 of its records carry no backend-stack value at all. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library.

Editorial position from this site’s catalogue analysis: before you choose a refactoring design, inventory the actual FQEVENTS implementations, exits, modifications and integration dependencies in your own landscape. That inventory, not a UI-technology count, is what tells you where the clean-core work sits. This page establishes the boundary only: do not let the distribution above stand in for that assessment.

SAP FI-CA basic functions — the events concept and process fundamentals behind FQEVENTS.
The Fiori 2025 Source Snapshot: Coverage, Gaps and What the Data Cannot Tell You
Fiori 2025 App Explorer

Frequently asked questions

If most apps use SAP Fiori elements, does that mean most of them are already clean-core ready?

No. SAP Fiori elements is a UI-rendering framework label describing how the screen is built. It does not establish that the underlying app exposes a released API or extension point for customer code. Clean-core readiness has to be verified per app, per extension requirement, against the target release's own extensibility documentation.

What should we inventory before choosing a refactoring design for a legacy customization?

The actual FQEVENTS implementations, user exits, modifications and integration dependencies in your landscape, not the UI technology distribution of the app catalogue. The export tells you how apps render; it does not tell you what your custom code actually does or whether a released extension point can replace it.

Where does a utility's clean-core exposure typically concentrate?

In FI-CA events (FQEVENTS) and IS-U enhancements, on the editorial reading in this site's catalogue analysis. A utility's custom logic tends to sit inside these event implementations, not inside the Fiori layer, which is exactly what a UI-technology count cannot see.