Four pages, about 29 minutes in total.
- S/4HANA 2025 Cutover Validation for SAP Utilities and FI-CA: What to Test Separately — 3 min. What your test scripts need to cover separately for Utilities and FI-CA, the two areas most likely to be under-tested by a generic cutover plan.
- After Go-Live: Measuring Fiori Adoption and Retiring GUI Fallback Safely — 3 min. The metrics that tell you cutover actually succeeded, and when it is safe to retire GUI fallback access.
- Deprecated and Successor Fiori Apps in S/4HANA 2025: What to Keep, Replace or Retire — 18 min. Check this before locking the test plan, so scripts are not written against apps already on a deprecation or successor path.
- Transaction Code to Fiori App Lookup for SAP Utilities and FI-CA (S/4HANA 2025) — 5 min. Cross-check your test scripts’ transaction coverage against what the export associates with each app.
Utilities and FI-CA run on cycles a generic cutover plan does not naturally account for: billing and meter-reading periods, and FI-CA payment and dunning runs, both of which have their own freeze windows and mass-activity locks around go-live. A test and cutover manager who plans Utilities and FI-CA validation like any other module risks scheduling the freeze against the wrong calendar, or testing an exception path that only appears once a full billing cycle has run.
The pages in this path draw on the SAP export of September 2026 for product 2025 (Private Cloud): 726 of its 3,185 app records carry a supplied transaction code and 2,459 do not, and 144 records 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: testing, cutover and hypercare, the system conversion track, and the release upgrade track.
Related reading
- S/4HANA 2025 Conversion and Upgrade journey map — the full workstream and phase view behind this path.
Frequently asked questions
Why does a deprecated-apps catalogue belong on a cutover manager's path?
Because a test script written against an app that is on a deprecation or successor path is a script you will have to rewrite after go-live. Checking that page before the plan is locked avoids testing effort that does not survive the release.
Does this path cover mass-activity freeze windows during cutover?
Not directly. The cutover validation checklist in step 1 and the adoption and fallback page in step 2 are the two testing, cutover and hypercare pages published in this release, and neither one covers freeze-window or mass-activity sequencing 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 →