Eight pages, about 49 minutes in total.
- How to Use the S/4HANA 2025 Conversion and Upgrade Knowledge Base — 4 min. Read this first: it explains the callouts and review status you will rely on for every scope decision below.
- Source and Verification Policy: How Facts, Field Notes and Review Status Work Here — 5 min. An architect signs off scope on these citations; know exactly what a
verifiedAtdate and a transaction-code association do and do not promise. - Before an S/4HANA 2025 Upgrade: 8 Fiori and Scope Decisions to Close First — 5 min. The scope decisions an architect is accountable for closing before the programme commits a plan.
- A Fiori Elements App Is Not a Clean Core: Separating UI Technology from Extensibility — 4 min. A recurring governance risk: stakeholders treat a modern UI as proof of clean-core compliance, and only an architect is positioned to correct that early.
- “SAP Fiori Elements for CoPilot” Is Not Joule: How to Verify AI Capability Claims — 4 min. The same governance pattern applies to AI claims in vendor and internal messaging; an architect needs the test before it reaches a steering committee.
- SAP Utilities Fiori Apps in S/4HANA 2025: The 20 IS-U Apps by Process — 6 min. The shape of the Utilities app catalogue, which sets what a Fiori-only launchpad can realistically promise for meter-to-cash.
- Deprecated and Successor Fiori Apps in S/4HANA 2025: What to Keep, Replace or Retire — 18 min. The longest page in the path and the one with the most scope risk: what an architect must decide to keep, replace or retire before build starts.
- S/4HANA 2025 Cutover Validation for SAP Utilities and FI-CA: What to Test Separately — 3 min. How the scope decisions above get proven, or disproven, before go-live.
Generic S/4HANA architecture guidance treats Fiori, clean core and AI adoption as cross-industry topics. On a Utilities and FI-CA programme they are not: the app catalogue is thin and exception-shaped, the clean-core surface includes convergent invoicing event and correspondence logic that has no equivalent elsewhere in the ERP, and an AI capability claim tied to a billing or dunning process carries regulatory weight a generic module does not. An architect who reads only generic material will scope the programme against the wrong shape.
The pages in this path draw on the SAP export of September 2026 for product 2025 (Private Cloud): 3,185 app records across 668 application components, of which 144 carry a lifecycle flag — 85 Deprecated and 59 Available with Successor. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library.
Coming next for this role
Still to come that will extend this path: Utilities transformation, FI-CA transformation, the system conversion track, and the release upgrade track. Reading paths are extended by hand as each release is published.
Related reading
- S/4HANA 2025 Conversion and Upgrade journey map — the full workstream and phase view behind this path.
Frequently asked questions
Why does an architect's path start with two guide pages instead of a technical topic?
Because every claim later in the path depends on knowing how it was sourced and what review status means. An architect signs off scope based on these pages; reading the source policy first means a citation is read for what it actually promises, not assumed to be more settled than it is.
Does this path replace a Utilities or FI-CA functional consultant's own reading path?
No. It covers the cross-cutting decisions an architect needs to govern a programme. The Utilities Functional Consultant and FI-CA Consultant reading paths go deeper into their respective app catalogues and process detail.
Further reading
Continue your trail
You now have the Migration context.
Save this guide, continue to the next concept or return to the Knowledge Library with your context intact.
Migration
22 resources in this area.
Practical SAP notes, structured for review, reuse and long-term maintenance.
Working on an FI-CA or IS-U implementation? I take on a limited number of advisory and architecture engagements.
Get in touch →