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

Lesson 4 of 6

Cadence alignment

12 min

A TCoE runs on a calendar. Some dates are set by SAP (release and upgrade windows), some by the business (period-end close, peak season, audits), and some by IT (change freezes, other system upgrades). The TCoE's job is to lay these on one annual calendar and plan regression, data refreshes and people around them, so that testing is ready when the window opens instead of starting when it does.

SAP-driven dates

DeploymentWhat SAP publishesPlanning implication
Private Edition / on-premiseBase releases every two years, feature pack stacks between them, support pack stacks for older releases; under RISE, customers can request an upgrade from SAPYou choose when to upgrade within maintenance rules; plan one or two regression-heavy upgrade projects a year
Public EditionTwo major releases a year; test system upgraded before production on a published schedule; regular hotfix deliveriesRegression windows are fixed and short; the pack must be ready before the test system is upgraded
SAP Cloud ALM and other SAP cloud servicesFrequent updatesWatch for changes to test tools and integrations themselves

SAP cadence by deployment. Always confirm exact dates in SAP's current schedules and release notes.

For Public Edition, SAP's learning material describes customers being notified ahead of an upgrade and the test system being upgraded first, giving a window to run regression on existing processes, especially customized ones. SAP also offers Post-Upgrade Tests for standard processes, run with customer consent after each upgrade, and the embedded Test Automation Tool for customer-maintained automates. A TCoE serving Public Edition should treat those windows as fixed appointments.

Business and IT dates

  • Financial close: month-end, quarter-end and year-end; avoid production changes and key-user testing in close weeks.
  • Peak seasons: for Contoso, the spring fleet-ordering peak strains order to cash and the plants.
  • Audits: external audit fieldwork often needs evidence packs and access to key users.
  • Change freezes: IT freezes around close or peak periods.
  • Other system upgrades: connected systems such as warehouse, bank or carrier platforms.
  1. JanYear-end close freezeNo production change; regression pack maintenance and automation work.
  2. Feb–MarSupport pack stack updateRelease assessment, data refresh, targeted regression; key users after close.
  3. Apr–MayFleet ordering peakOrder-to-cash change freeze; TCoE runs roll-out testing for plant 3.
  4. Jun–JulFeature pack upgrade projectFull regression in QAS client 100; UAT with business test network.
  5. Sep–OctEnhancement releaseFunctional plus targeted regression; automation coverage extended.
  6. Nov–DecAudit and planningEvidence packs for audit; next year's calendar and budget.
Contoso's TCoE calendar for a Private Edition landscape. Months are illustrative.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-401

Building the calendar

  1. Collect fixed datesSAP schedules, close calendar, peaks, freezes, audits
  2. Place SAP-driven eventsUpgrades and support packages with their regression windows
  3. Place internal releasesEnhancement bundles in the remaining windows
  4. Back-schedule preparationRelease assessment, data refresh, environment readiness, tester booking
  5. Check capacityTCoE, business test network and partner capacity per month
  6. Publish and reviewShare with IT and business; review quarterly
Building the annual TCoE calendar.
The Sign-Off Table · thesignofftable.com/academy/sap-tst-401

Release assessment: from calendar to scope

The calendar tells you when to test; the release assessment tells you what. For each SAP update, compare what SAP changed with what Contoso actually uses. SAP points customers to the in-system What's New information and the What's New Viewer on the SAP Help Portal to identify changes, and notes that customers must know which features are active in their own system to judge impact. Map the changes onto the regression pack: processes touched by the release get full regression, neighbors get a targeted set, and untouched processes get the smoke-level checks. The output is a test scope that is as small as is safe, with the reasoning written down.

What would you do?

Contoso runs Public Edition for a newly acquired subsidiary. The next release upgrade of its test system falls in the subsidiary's quarter-end close week. What should the TCoE do?

Key points
  • Build one annual calendar from SAP release dates, business events and IT freezes.
  • Public Edition gives fixed upgrade windows; Private Edition lets you choose upgrade timing within maintenance rules.
  • Back-schedule assessment, data, environments and tester bookings from each window.
  • Key-user time is the scarcest resource; book it a quarter ahead around close and peaks.

Check your understanding · not graded

Lesson check

  1. 1. Why align the TCoE calendar to SAP's release cadence?

  2. 2. In Public Edition, which system is upgraded first?

  3. 3. What are SAP's Post-Upgrade Tests in Public Edition?

  4. 4. Which internal event most often constrains key-user availability?