How to Use This S/4HANA 2025 Knowledge Base

In 30 seconds

What it is This knowledge base supports two S/4HANA 2025 journeys, conversion from SAP ERP with IS-U and upgrade from an earlier S/4HANA release, over a shared set of workstreams. Every page follows the same shape and the same four callouts, and every page starts life marked In review.

You use it when You have just landed on this knowledge base, or you are onboarding a consultant onto an S/4HANA 2025 project, and need to know where to start and how a page is meant to be read.

Guide covers Migration / Start Here

Who this is for

This knowledge base is written for SAP consultants working S/4HANA 2025 projects, with the deepest coverage in SAP Utilities (IS-U) and FI-CA — Contract Accounts Receivable and Payable, of which Convergent Invoicing is one branch. It assumes you already know the functional area you work in and are looking for what changes in S/4HANA 2025, not an introduction to Utilities or FI-CA as a discipline.

Two tracks, one shared backbone

The knowledge base serves two journeys over the same set of workstreams:

System conversion — moving from SAP ERP with IS-U straight to S/4HANA 2025.
Release upgrade — moving from an earlier S/4HANA release to S/4HANA 2025.

Both journeys share the same workstreams: Strategy and Business Case, Utilities Transformation, FI-CA Transformation, Fiori Apps, Roles and Launchpad, Clean Core and Technical Debt, AI and Joule, Testing, Cutover and Hypercare, and Reference and Templates. System Conversion and Release Upgrade are the two workstreams that hold what is specific to each journey. The journey map lays workstreams out as rows and project phases as columns, so you can find your page from where you are, not just from what topic it covers.

How to read a page

Every page follows the same shape:

In 30 seconds — the summary shown near the top tells you in two or three sentences what the page covers and what it lets you decide.
Decide — a table of options, when to choose each one, and the effort and risk involved. It is a comparison, not a recommendation for your specific instance.
Do this — a numbered checklist, each step tagged with a project phase and an owner role, so you can hand it to the right person.
Four callouts, always in the same visual language:

IS-U lens — what is different for SAP Utilities and FI-CA specifically. Every page in this knowledge base carries one of these, including pages that read as generic Fiori or clean-core guidance elsewhere, because meter-to-cash and convergent invoicing rarely follow the generic answer.

Watch out — a pitfall or a false assumption, stated plainly. On this knowledge base, the most common one worth watching for across every page: a supplied transaction code next to a Fiori app is an association SAP shipped with the export, never a statement that the app replaces that transaction.

Source fact — what a cited SAP source, or the September 2026 SAP Fiori Apps Reference Library export, actually supplies, with no interpretation added. Here is this page’s own, so you can see the shape: the September 2026 export for product 2025 (Private Cloud) carries 3,185 app records across 668 application components, of which 20 sit in IS-U components and 72 in FI-CA components. The snapshot has not been revalidated against the live SAP Fiori Apps Reference Library. Every source fact on every export-backed page carries that last sentence.

Field note — editorial guidance or project experience, kept visibly separate from the source fact above it. This page is itself an example: recommending that you read the source and verification policy page before any playbook page is a field note, not a fact from an SAP source.

Related reading — links out instead of repeating fundamentals already covered elsewhere on this site.

What “In review” and “Verified” mean

Every page in this knowledge base is published with reviewStatus: needs-technical-review. On the journey map, that status shows as “In review” until the site owner reviews a page against live project experience and sets reviewStatus: approved; the map then shows “Verified” and the page itself carries a “Technically reviewed” label. Nothing on this knowledge base is marked Verified by default, and no page sets its own review status.

What this knowledge base deliberately does not repeat

This knowledge base does not re-explain SAP Utilities or FI-CA process fundamentals. For those, go to the existing SAP Utilities knowledge area and the FI-CA knowledge area. This knowledge base covers what changes for S/4HANA 2025, what to decide, and what to test, and links back to those areas for how a process works in the first place.

How it is kept current

Facts sourced from SAP are dated with a verifiedAt value and re-checked on a six-month cycle; the full rule is on the source and verification policy page. New pages are added as plain markdown files with a subArea and phase, and the journey map updates automatically to place them. Reading paths are curated by hand and are extended with each release, not generated from the map.

Source and Verification Policy — how facts, field notes and review status work here.
S/4HANA 2025 Conversion and Upgrade journey map — find your page by phase and workstream.
Fiori 2025 App Explorer — search all 3,185 apps in the September 2026 export.

Frequently asked questions

Do I have to read this knowledge base in order?

No. Read the journey map for your project phase, or open the reading path built for your role. This page and the source policy page are worth reading first regardless: the Solution Architect reading path opens with both, and every other path assumes you already know what the callouts and review status mean.

Is this knowledge base a replacement for SAP's own documentation?

No. It is a decision layer on top of SAP's documentation, focused on SAP Utilities and FI-CA scope for S/4HANA 2025. It links out to SAP's sources and to this site's existing process guides instead of repeating them, and it states plainly where a fact is still awaiting sign-off.

What does the 'In review' label on a page mean?

It means the page has cited sources and has been researched and drafted, but has not yet been checked against project experience and approved by the site owner. See the source and verification policy page for the full rule.