S/4HANA 2025 Fiori Export Data Quality

In 30 seconds

What it is The September 2026 export covers 3,185 unique app records across 668 components with no exact duplicates: 3,041 Available, 85 Deprecated, 59 Available with Successor. It has real gaps — 97 blank descriptions, 68 blank Line of Business, 140 blank backend stacks, 2,459 blank transaction codes — and it never supplies six specific fields, including earliest release and Joule capability. Every number here traces to the workbook and to the published snapshot the App Explorer serves.

You use it when You need to state, precisely and with a source, what this export does and does not cover before someone treats a gap in the data as a fact about the SAP system.

Guide covers Migration / Reference and Templates

Why it matters

Every other page in this knowledge base that cites an app count, a lifecycle status or a UI technology value is drawing on one workbook: SAP Fiori AppList Sep 2026(1).xlsx. Before trusting any of those numbers on a live project, a consultant needs to see the coverage and the gaps in that source directly, in one place, traced against the machine-readable data file this site actually builds its pages from. This page is that trace.

Source coverage and quality

Measure	Result
Data rows	3185
Unique App IDs	3185
Exact duplicate data rows	0
Source columns	11
Distinct application components	668
Available	3041
Deprecated	85
Available with Successor	59
Release label	2025 (Private Cloud) — all 3,185 records

Missing source fields

Field	Blank cells
App Description	97
Application Component Description	16
Line Of Business	68
Product version (Backend) - SP Stack	140
Transaction Codes	2459

Backend stack values

Source value	Records
Initial Shipment Stack	3033
Not supplied	140
SP01 \| SP01	12

UI technology distribution

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

Fields the workbook does not provide

Requested field	Treatment in this revision
Earliest available release	Not supplied; the selected release label is retained instead
Joule capability	Not supplied; do not turn missing data into Yes or No
Exact activation prerequisites	No structured service, component-version, catalog, or SAP Note columns; retain any details present in descriptions
Successor app ID	No dedicated field; preserve any relationship explicitly stated in a description
Roadmap commitment	Not supplied; no planned applications added
Complete Private Edition application population	Not established by the export; it covers the supplied SAPUI5 selection

Source of record

Workbook: SAP Fiori AppList Sep 2026(1).xlsx
Worksheet: SAPUI5 Export
Header row: 1. Data rows: 2–3186.
Source SHA-256: 3081de9840f0930bc824aa7b881b646b118a5e26faf32f1deff50bbb625b03d8

Revision history

Version	Change
1.0	Earlier provisional research list; many application and release gaps
2.0	Original ten-column workbook incorporated; all 3,185 apps retained with source-row traceability
2.1	Updated eleven-column workbook incorporated; 726 supplied transaction mappings added to app records and indexes; reverse lookup added; original ten columns verified unchanged

Decide

Question	If yes	If no
Do you need the current state of the live SAP Fiori Apps Reference Library?	Query the live library directly. Neither this page nor the Fiori 2025 App Explorer can answer it: both serve the same frozen September 2026 snapshot.	This snapshot is adequate for planning against the September 2026 baseline.
Is the value you need one of the six fields this workbook never supplies?	Do not invent it. Record it as an open enrichment task with a source and a verification date.	Use the source column directly; it is the evidence for that field in this snapshot.
Does a record show a blank backend stack, description or transaction code?	Treat it as “not supplied,” never as “No,” “unavailable,” or “incompatible.”	Proceed with the supplied value as given.

Do this

Solution Architect — Freeze this exact workbook and its hash as the project’s baseline before quoting any count from it in a deliverable.
Fiori lead — Cross-check any count you quote against the published snapshot at /tools/fiori-2025-app-explorer/apps.json (its meta.counts, or a direct query over apps) rather than re-typing a number from memory.
Solution Architect — Where a page or deck needs one of the six fields this workbook does not supply, route it to the enrichment record template instead of guessing.

Utilities and FI-CA scope sits inside the same 140 blank backend-stack records and 2,459 blank transaction-code records as everything else in the export; there is no evidence in this snapshot that Utilities or FI-CA apps are disproportionately affected by either gap. Check each shortlisted app individually rather than assuming a component-wide pattern.

Initial Shipment Stack describes the backend stack selected for this export. It does not establish the app’s first historical release, and a blank stack value is not evidence of incompatibility with your target maintenance level. Both misreadings turn a data-collection artifact into a false statement about the SAP system.

Every table above is reproduced exactly from the SAP export of September 2026 for product 2025 (Private Cloud), cross-checked against the meta.counts block of the published snapshot at /tools/fiori-2025-app-explorer/apps.json and against a direct query of the UI technology and backend stack fields across all 3,185 records. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library.

Treat this page as the page to link back to whenever a number in another page of this knowledge base needs a source. It is easier to maintain one trace of coverage and gaps than to repeat the caveats on every page that cites a count.

Frequently asked questions

How many apps and application components does the September 2026 export cover?

3,185 unique App IDs with zero exact duplicate data rows, spread across 668 distinct application components. 3,041 records are Available, 85 are Deprecated and 59 are Available with Successor. All 3,185 records carry the same release label: 2025 (Private Cloud).

Does a blank field mean the corresponding thing does not exist in SAP?

No. A blank cell means the workbook did not supply a value for that field, nothing more. The export has 97 blank App Descriptions, 16 blank Application Component Descriptions, 68 blank Line of Business values, 140 blank backend-stack values and 2,459 blank transaction codes. None of these gaps establishes that the app, its component description, its LoB, its stack, or a transaction is unavailable in SAP.

What does this workbook never supply, no matter how the data is filtered?

Six fields: earliest available release, Joule capability, exact activation prerequisites, a dedicated successor app ID field, roadmap commitments, and confirmation of the complete Private Edition application population. Anything a page states about these six areas has to come from a separate, cited source, not from this export.