Fiori 2025 App List Corrections | S/4HANA Upgrade Scope

In 30 seconds

What it is Fourteen records in the September 2026 export are easy to misread: a status label that looks decorative, a name that invites shortening, two similar apps that look like one. Each note below pairs the exact supplied name and status with what the record does and does not establish for Utilities, FI-CA or core-ERP scope. Nine of the 14 touch Utilities or FI-CA directly.

You use it when You inherited an earlier Fiori app list or scope document for this programme and need to know which entries were wrong or incomplete, and why.

Guide covers Migration / Fiori Apps, Roles and Launchpad

Why it matters

A shortlist built by hand from a large export loses things: a status label dropped, a name shortened, two similar apps merged into one. Each loss looks minor in isolation and compounds into wrong upgrade scope decisions — a missing BPEM app, an assumed transaction replacement, a successor treated as already live. The 14 notes below are interpretation notes from this site’s catalogue analysis, each one placed where that misreading is most likely, so your own scope document does not inherit it.

The 14 interpretation notes

App ID	Exact source name	Source status	Interpretation
F4494	Reverse Document	Available	The description explicitly supports reversal of FI-CA documents and archived FI-CA documents. Treat it as an FP08 replacement candidate to test, not proven full equivalence — and the export supplies no transaction code for it.
F2709	Periodic Billing Overview	Available	Included at Initial Shipment Stack in this export. Do not label it as introduced later merely because documentation was found elsewhere.
F3135	Periodic Invoicing Overview	Available	Confirmed as a Utilities invoicing overview under IS-U-IN.
F7255	BPEM Clarification Case Overview	Available	Add the Utilities BPEM overview to exception-management scope.
F7256	Manage BPEM Clarification Cases	Available	Add Utilities BPEM case processing. Keep this separate from Convergent Invoicing clarification cases (F2349).
F2349	Manage Clarification Cases	Available	The description restricts its clarification-case context to Convergent Invoicing; do not map it to all FI-CA payment clarifications.
F3978	Search Payments in Lots	Available	Add dedicated payment-in-lot search. Search does not establish payment-lot creation or posting replacement.
F4531	Manage Reconciliation Key	Available	Add reconciliation-key management to FI-CA upgrade scope.
F4866	Reconcile SD Billing Documents	Available	Add SD billing reconciliation to the SD–FI-CA integration assessment.
F0717	Manage Journal Entries	Available with Successor	Preserve Available with Successor status; do not treat this as identical to the new version.
F0717A	Manage Journal Entries - New Version	Available	Preserve the exact name Manage Journal Entries - New Version as a separate record from F0717.
F1511	Request Maintenance	Available with Successor	Preserve Available with Successor status in the maintenance selection.
F1443A	Manage Cost Centers (Version 2)	Available	Use the exact source name, including (Version 2).
F0251	Manage Material Coverage	Available with Successor	Description names F0251A as an alternative and explicitly notes incomplete feature coverage. A successor is not automatic feature parity.

Every row above was checked by App ID against the September 2026 export at the time of writing, and the name and status columns are the supplied values.

Do this

Prepare · Fiori lead — If you are carrying forward a scope document written against an older app list, re-check every App ID it references against the current export, not just the 14 listed here.
Prepare · Fiori lead — Copy exact app names and statuses from the export into your own documents. Do not paraphrase a status label — “Available with Successor” and “Available” are materially different facts.
Prepare · Fiori lead — Never shorten a suffixed App ID for readability. Keep the suffix every time the ID appears.

Nine of the 14 notes touch Utilities or FI-CA directly: F4494, F2709, F3135, F7255, F7256, F2349, F3978, F4531 and F4866. Two of those — F7255/F7256 (Utilities BPEM) and F2349 (Convergent Invoicing clarification cases) — look similar by name but sit in different components and different processes. Keep them as separate scope items in your workbook; merging them into a single “clarification cases” line loses the distinction the export itself preserves.

App-ID suffixes are significant. F2596A, F2600A, F0717A, F0251A and every other suffixed ID in this knowledge base must never be shortened to what looks like the “base” ID — the suffixed record is a separate record, not a formatting artifact. The export supplies no release date, so the suffix tells you the records differ; it does not tell you which came first.

The App IDs, exact names and lifecycle statuses in the table above are reproduced exactly as the SAP export of September 2026 for product 2025 (Private Cloud) supplies them: 11 of the 14 records carry the status Available and 3 carry Available with Successor. The Interpretation column is this site’s catalogue analysis, not an export field. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library.

Treat this page as a living log. When a later pass through the export surfaces another record that is easy to misread, add it here with the same evidence format — App ID, exact source name, source status, interpretation — rather than folding the point into whichever page happens to need it and losing the shared note.

Fiori 2025 App Explorer — verify any App ID against the current export directly.
SAP Utilities Fiori apps in S/4HANA 2025
FI-CA and Convergent Invoicing Fiori apps in S/4HANA 2025

Frequently asked questions

Why does this page exist if the export is already accurate?

The export is accurate and this page does not dispute a single supplied value. What it addresses is reading: building a shortlist from 3,185 rows means grouping, abbreviating and summarising, and these 14 records are the ones where that process most often loses a fact that changes scope. Each note says what the record establishes and what it does not.

Can an App ID suffix like the A in F2596A be dropped for readability?

No. F2596A and F2600A are distinct records from any unsuffixed ID that might exist elsewhere in the export. Shortening a suffixed App ID risks pointing a reader at the wrong app entirely.

Are all 14 notes about Utilities and FI-CA?

No. Nine touch Utilities or FI-CA directly (F4494, F2709, F3135, F7255, F7256, F2349, F3978, F4531, F4866). The remaining five (F0717, F0717A, F1511, F1443A, F0251) are core-ERP apps whose status label needed preserving exactly.