Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table
All guides

Guide · SAP S/4HANA

S/4HANA 2025 FPS02 Update: What to Regression Test

How to scope regression for an S/4HANA 2025 FPS01-to-FPS02 update: read What's New, check deprecations, build a delta pack and get sign-off.

Matt Angerer
November 17, 2026 · 8 min read · 8 sources

If you are moving an on-premise S/4HANA 2025 system from FPS01 to FPS02, you are running an update, not a release upgrade. Build the regression scope from three inputs: the FPS02 What's New content filtered to your scope items, the deprecations that land in that stack, and the custom code and Fiori apps your business actually uses. Sign off a delta pack with evidence, not a full re-run of the suite out of habit.

FPS02 became generally available in October 2026, so most programs running 2025 are now deciding this. The steps below are what I would want documented before a test manager signs.

Update or upgrade: settle the label first

SAP treats a move to a higher feature package stack within the same release as an update. A move from a lower release to a higher one, such as 2023 to 2025, is an upgrade. The SAP S/4HANA 2025 Getting Started guide sets out that distinction, and it is version-dated October 7, 2026 for FPS02.

SAP describes an FPS as usually larger in scope, possibly with new features, but typically without objects or features taken away. It also carries software corrections and legal changes, and SAP says it is minimally disruptive, needing far less preparation, testing and training than an upgrade to an initial shipment stack. That is the point to keep in mind if your ECC instincts say every stack change is a project.

Read "minimally disruptive" as a statement about the effort SAP expects, not as a reason to skip regression. Your scope follows what changed in your processes. The Private Edition 2025 FPS02 count is a useful reminder: the Release Navigator post for FPS02 lists 28 deprecations among 996 innovations. That is a Private Edition count, so check the on-premise What's New for your own list.

Step 1: Baseline the stack on every tier

Write down the exact FPS on sandbox, QA, pre-production and production before you touch the scope. Stack drift between tiers is the most common reason a regression pack passes in QA and fails in the first production test. Record the target stack too, and the date you expect it.

Dates for FPS01 vary by source. SAP's own 2025 guide is version-dated February 25, 2026 for FPS01, while a later SAP community post puts it at about April 2026. For FPS02, the same community series says it is generally available as of October 2026. Use the SAP Help Portal date and the release note for your tenant or system as the record, not a blog.

Step 2: Filter What's New to your scope items

Open the What's New content for FPS02 through the What's New Viewer for SAP S/4HANA, not a summary. Filter it by the scope items, business functions, Fiori apps and interfaces in your test scope matrix. Then map each change to a business process and a test case, or mark it as not applicable with a reason.

Behavior changes matter more than new screens. One example from the FPS02 Core Logistics notes: post goods issue is now blocked while a Product Compliance check is still pending. That changes outbound delivery testing even though nobody asked for it. Any process that ends in a goods issue belongs in the delta pack, including the interfaces that trigger it.

Step 3: Treat deprecations as their own test list

Deprecations are where update regression usually breaks. A community post on repair processes reports that SAP introduced In-House Service 2.0 in FPS02 and deprecated the older repair-specific transaction types. The same post lists the document type changes, for example repair requests moving from REPA to IHRP and repair orders from REPO to SRVO.

Verify that against the FPS02 What's New before you rely on it. The practical test is the same whatever the list says: for each deprecated object, find every place your custom reports, output forms, interfaces and integration mappings reference it, and test that the replacement path still produces the same result. Missing a deprecated document type in a report is a silent defect, not a crash, so the test must check numbers, not just that the screen opens.

Fiori is the other place to check. New or changed apps need the right catalogs and roles, and an app that opens for the admin may still be missing for a business user. Our guide on testing Fiori catalog authorizations in S/4HANA roles covers how to test that part.

Step 4: Run the checks and decide what they change

The Simplification Item Check is where the technical findings come from. SAP's Upgrade Guide for 2025 describes it as mandatory for upgrades, triggered by the Software Update Manager, and says it needs the stack file from the Maintenance Planner first.

Sources disagree on whether it applies to an FPS update. The 2025 on-premise Upgrade Guide (version 3.0, October 2026) describes one optional but recommended tool as relevant for release upgrades and not for FPS-to-FPS updates. A SAP Community post, by contrast, says the check can be run for an FPS or SPS update by selecting the target version. My advice: run it against the FPS02 target anyway, since it costs little to read the list, and document which findings you dispositioned and why. The SAP guide also says most simplification items are not relevant to a given system, so the job is filtering, not fixing everything. Our guides on the SAP Readiness Check for S/4HANA and on simplification item check return codes cover the mechanics.

Feed custom code findings into scope as well. Our guide on ATC clean core results shows how to turn those results into regression scope.

Step 5: Build the delta regression pack

  1. BaselineRecord the FPS on every tier and the target date
  2. Scope the changeFilter What's New to your scope items and processes
  3. Add deprecationsList replaced objects, document types and interfaces
  4. Add check resultsSimplification item and ATC findings, each dispositioned
  5. Tier the testsSmoke, critical path, then the delta regression set
  6. Execute and sign offEvidence per test, defects triaged, go or no-go recorded
Figure 1. The FPS update delta pack, from baseline to sign-off

Structure the pack in three tiers. Smoke covers log-on, Fiori launchpad, and a few transactions in each core area. Critical path covers the end-to-end flows the business cannot lose: order to cash, procure to pay, record to report and the period close. The delta set is the change-driven tests from steps 2 to 4. That tiering is the usual approach for keeping a stack update inside a window.

Keep the delta set small and explicit. An SAP community post on test strategy for private cloud makes the same split between smoke, critical path and regression suites, and recommends tiered planning for FPS, SPS, custom code and base releases. Scope per release should follow what changed, not what the last team tested.

Step 6: Evidence and sign-off on RISE

If you are on RISE with SAP, be clear about who owns the test. The same community test-strategy post notes that customers on private cloud can request one upgrade per year from SAP, and that QA teams must plan and own upgrade testing. SAP does the technical work; you own the proof that your business still works.

The sign-off pack should show what changed, which tests covered each change, the deprecation dispositions, the check results with decisions, the defects found and closed, and the go or no-go with named owners. Our guide on life after go-live and the S/4HANA upgrade cadence covers how to keep this running every six months. For the wider sequence of test levels around a release, the N+1 landscape testing guide shows where a stack update fits.

To go deeper, the free SAP Academy course Testing SAP S/4HANA Upgrades and Feature Pack Stacks walks through the same ground in more detail.

Frequently asked questions

Is an FPS update the same as an S/4HANA upgrade for testing?

No. SAP defines a move to a higher FPS within the same release as an update, and a move from a lower release to a higher one as an upgrade. An FPS usually adds features and corrections without removing objects, so the scope is normally narrower. Deprecations still need their own test list.

Do I have to run the full regression suite for an FPS update?

Not by default. Run a small smoke and critical path set on every tier, then a delta set driven by the What's New content for your scope, your deprecations and your check findings. Document the scope decision so an auditor or reviewer can see why a test was left out.

Does the Simplification Item Check apply to an FPS update?

SAP's sources do not agree. The 2025 on-premise Upgrade Guide describes one optional tool as not relevant for FPS-to-FPS updates, while a SAP Community post says the check can be run for an FPS or SPS update by choosing the target version. Run it against the target stack and record how you handled each finding.

Where do I find what changed in FPS02?

Use the What's New Viewer for SAP S/4HANA and filter by your scope items. Cross-check against the release information note and the upgrade guide version for your stack. Don't rely on a blog summary for a test scope you will sign.

Sources

  1. Getting Started with SAP S/4HANA 2025 (on-premise), version 3.0, SAP Help Portal, October 7, 2026
  2. Upgrade Guide for SAP S/4HANA 2025, version 3.0, SAP Help Portal, October 7, 2026
  3. Release Navigator for SAP Cloud ERP Private - What's New in 2025 FPS02, SAP Community, October 2026
  4. SAP S/4HANA Service: In-House Repair 2023 vs 2025 FPS02 key changes, SAP Community member blog, October 2026
  5. SAP Core Logistics for SAP S/4HANA Cloud, Private Edition, 2025 FPS02, SAP Community, October 2026
  6. SAP S/4HANA Simplification Item Check: How to do it right, SAP Community, SAP blog
  7. Understanding Test Strategy for SAP S/4HANA Private Cloud, SAP Community member blog
  8. Release Navigator for SAP Cloud ERP Private - What's New in 2025 FPS01, SAP Community, early 2026

More on SAP S/4HANA

How this guide is made: researched with AI-assisted search across SAP documentation and practitioner sources, with every fact linked to its source. Found an error or have field experience to add? Tell us.