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

Lesson 4 of 5

Roadmap alignment

10 min

Listen to this lesson

0:00 / 6:45

Architecture decisions in SAP programs are made inside SAP's own timeline: maintenance end dates, release cycles, product investments and retirements. A decision that ignores that timeline can be technically sound and still wrong, because the platform it depends on is ending, or because it lands the program in an upgrade it has no capacity to test. Roadmap alignment means checking every major decision against SAP's published plans and your own release calendar.

The dates that frame SAP transformations

  1. End of 2027SAP Business Suite 7 mainstream maintenance endsPer SAP's 2020 announcement, for core applications
  2. 2028–2030Optional extended maintenanceAt a premium of two percentage points; decision required by end of 2027
  3. Before end of 2030SAP ERP, private edition transition option deadlineSystems must move to the private edition on SAP HANA before end of 2030 to use the option
  4. 2031 onwardTransition option periodAnnounced for 2031 to 2033; SAP's October 13, 2026 update lets subscriptions run to December 31, 2035, with further prerequisites — check current terms
  5. End of 2040SAP S/4HANA maintenance commitmentPer SAP's 2020 announcement
Key SAP maintenance dates as published by SAP News. Terms change; check the latest announcements before relying on them.
The Sign-Off Table · thesignofftable.com/academy/sap-arc-401

These dates matter differently by situation. For Contoso, already converted to S/4HANA, ECC dates mainly affect the legacy systems ED1, EQ1 and EP1 and the support team that runs ChaRM on SAP Solution Manager 7.2 for them. For a program still on ECC, they set the deadline for the transition path decision itself.

The S/4HANA release rhythm

SAP's learning material for S/4HANA Cloud Private Edition describes the cycle after the 2023 release: one base release every two years, Feature Pack Stacks about every six months in between, and mainstream maintenance of seven years per base release. Under RISE with SAP, customers must install at least one upgrade within seven years to stay in mainstream maintenance and may request one upgrade per year; SAP executes the technical upgrade, while planning, preparation and testing stay with the customer or partner. Contoso is going live on SAP S/4HANA 2025, so its next base release decision falls around 2027, alongside Feature Pack Stacks in between.

  1. Go-live on 2025Q3: Contoso converts to SAP S/4HANA 2025 Private Edition
  2. Wave 2Alternadores load into company code 1910 on the same release
  3. Feature packsDecide per Feature Pack Stack whether to apply, based on value and test capacity
  4. Next base releasePlan the upgrade to the next base release; regression sized by the extension choices made now
  5. RebuildsSchedule clean core rebuilds, such as return agreements, before the upgrade to cut regression
Aligning Contoso's architecture decisions with the S/4HANA release rhythm.
The Sign-Off Table · thesignofftable.com/academy/sap-arc-401

Using SAP's roadmap information

  • SAP Road Map Explorer shows planned innovations by product; SAP's learning material lists it with the What's New Viewer on the SAP Help Portal and the Customer Influence site as resources for tracking change.
  • Simplification and readiness information shows what changes or disappears when moving to a release.
  • Clean core guidance shows which extension techniques SAP expects to stay stable.
  • Product announcements on SAP News record maintenance commitments and transition offers, with dates.

Treat roadmap items as plans, not commitments. Record in the decision record which roadmap item the decision depends on and when it was checked. If a decision relies on a capability SAP has planned but not delivered, say so and name the fallback.

A decision that leans on SAP's roadmap records the item, the date it was checked and a fallback.
The Sign-Off Table · thesignofftable.com/academy/sap-arc-401

Not only the ERP

The same discipline applies to everything around S/4HANA. SAP BTP services, SAP Cloud ALM and integration content follow their own release cycles, often faster than the ERP's, and services are occasionally renamed, merged or retired: at SAP Sapphire 2026 SAP began rebranding SAP BTP itself as SAP Business AI Platform, and the ABAP environment took the name SAP Business AI Platform, ABAP environment in September 2026, while the Neo environment reaches end of life on December 31, 2028. A side-by-side extension strategy therefore commits the program to tracking more than one roadmap. Record which services each decision depends on, and add those services to the roadmap review so a planned change on the platform side does not arrive as a surprise in production.

A side-by-side strategy means tracking several roadmaps, not just the ERP's.
The Sign-Off Table · thesignofftable.com/academy/sap-arc-401

Aligning with your own roadmap

Alignment is two-sided. SAP's timeline sets windows; the business calendar sets blackouts: year-end close, peak season, acquisitions. Contoso's Q3 go-live, Wave 2 shortly after and the first base release upgrade around 2027 all compete for the same test team. An architecture roadmap shows decisions, rebuilds and upgrades on one timeline with the test capacity each needs.

What would you do?

An architect proposes building a large new extension using an SAP BTP capability listed in a roadmap as "planned" for next year, with no fallback. What should the board require?

Key points
  • Check major decisions against SAP maintenance dates and transition terms; they change, so date your checks.
  • S/4HANA Private Edition: base release every two years, feature packs about every six months, seven years of mainstream maintenance.
  • Use SAP Road Map Explorer and announcements; treat roadmap items as plans with fallbacks.
  • Put decisions, rebuilds, upgrades and test capacity on one timeline.

Check your understanding · not graded

Lesson check

  1. 1. Until when has SAP committed maintenance for SAP S/4HANA, per its 2020 announcement?

  2. 2. How often does S/4HANA Private Edition get a new base release after 2023, per SAP's learning material?

  3. 3. Under RISE with SAP, who tests after SAP executes a technical upgrade?

  4. 4. How should a roadmap item that a design depends on be treated?