Seven pages, about 52 minutes in total.
- The Fiori 2025 Source Snapshot: Coverage, Gaps and What the Data Cannot Tell You — 5 min. What the export behind every catalogue page in this path can and cannot tell you, before you design a role on top of it.
- Deprecated and Successor Fiori Apps in S/4HANA 2025: What to Keep, Replace or Retire — 18 min. The apps flagged Deprecated or Available with Successor, each one needing an explicit keep, replace or retire decision before role design closes.
- SAP Utilities Fiori Apps in S/4HANA 2025: The 20 IS-U Apps by Process — 6 min. The IS-U tiles and role hints your launchpad and roles need to cover.
- FI-CA and Convergent Invoicing Fiori Apps in S/4HANA 2025: 72 Apps by Task — 12 min. The FI-CA and Convergent Invoicing tiles your launchpad and roles need to cover. No FI-CA description in this export names a business role template, so plan to build these roles from the task groups instead.
- Core ERP Fiori Apps a Utilities Project Still Needs in S/4HANA 2025 — 4 min. The cross-application apps a Utilities user’s role still needs outside the two catalogues above.
- Fiori Enrichment Record Template: Tracking What the SAP Export Does Not Supply — 4 min. How to record the role and security gaps you find in steps 1 to 5 without overwriting the source export.
- After Go-Live: Measuring Fiori Adoption and Retiring GUI Fallback Safely — 3 min. How to tell whether the roles and launchpad you built are actually being used before you remove GUI fallback access.
Utilities and FI-CA change what a launchpad and role design have to account for, and they do not behave the same way. Business role templates are named in IS-U app descriptions — 17 of the 20 IS-U records mention an SAP_BR_ template — while none of the 72 FI-CA records does, so the FI-CA side gives you no template to start from. Meter-to-cash exception apps sit under different owning roles than the billing and collections apps beneath them, and GUI fallback tends to persist longest in exactly these two areas because so few of the underlying transactions have a Fiori app at all. A security lead who treats Utilities and FI-CA like any other line of business will under-provision fallback access and over-promise tile coverage.
The pages in this path draw on the SAP export of September 2026 for product 2025 (Private Cloud): 20 app records sit in IS-U components and 72 in FI-CA components, and 17 of the 20 IS-U descriptions contain an SAP_BR_ business role template name while none of the 72 FI-CA descriptions does. 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: Fiori roles and launchpad conversion, clean core and technical debt, and per-app guides for the Utilities apps.
Related reading
- S/4HANA 2025 Conversion and Upgrade journey map — the full workstream and phase view behind this path.
Frequently asked questions
Why read the source snapshot page before any app catalogue?
Role design decisions get baked into authorization concepts that are expensive to unwind. Knowing what the export cannot tell you, before you build roles from it, means you design in a validation step for the gaps instead of discovering them in a security audit.
Why is a core ERP catalogue page in a Utilities and FI-CA focused path?
Because a Utilities project's users still need core finance, procurement and cross-application Fiori apps for the roles around meter-to-cash. A launchpad scoped only to IS-U and FI-CA apps leaves those users without a complete role.
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 →