Cloud ERP updates arrive on SAP’s schedule, not yours. We review each release against your processes, test it with automated regression and switch on the new features that help you. For SuccessFactors we manage the 1H and 2H release cycles; for SAP Cloud ERP we manage each upgrade and its adoption.
Every release
reviewed against your own processes
Automated
regression testing with Tosca
1H and 2H
SuccessFactors release cycles managed
Adopt, not just survive
new features switched on when they help you
In the cloud, SAP decides when the release comes. You decide whether it is a surprise or an opportunity.
Your SAP release calendar
Each SAP product changes on a different rhythm. Choose a product to see how it updates, what can go wrong and what we do.
SAP Cloud ERP, public edition
How it updates: Two upgrades a year, named by year and month (for example 2602 and 2608), plus regular hotfix collections.
What SAP changes
- SAP upgrades every customer on its own schedule
- Your test system is upgraded before production
- New scope items and features arrive with each release
What can go wrong
- A process stops working and nobody notices until month-end
- Key users find changed screens on Monday morning
- Useful new features stay switched off
What we do
- Impact analysis of the release notes against your scope items
- Automated regression in the upgraded test system
- A shortlist of new features worth switching on
S/4HANA private edition and on-premise
How it updates: A new release every two years, with feature pack stacks in between and 7 years of mainstream maintenance from the 2023 release.
What SAP changes
- You choose when to upgrade
- Each upgrade is a project, not a weekend task
- Custom code and add-ons must be checked
What can go wrong
- Upgrades postponed until maintenance runs out
- Custom code that breaks on the new release
- Long, manual test cycles
What we do
- An upgrade roadmap that fits your business calendar
- Custom code checks and fixes through our Development Factory
- Automated regression so each test cycle is shorter
SAP SuccessFactors
How it updates: Two releases a year, 1H and 2H. Each arrives in your preview instance first, then in production.
What SAP changes
- Some features switch on for everyone
- Others wait for an administrator to enable them
- Deprecated features are retired on a set date
What can go wrong
- HR teams surprised by changes in forms and workflows
- Integrations to payroll or third parties break
- Features you are paying for never get used
What we do
- Release review in the preview instance
- Testing of your configuration and integrations
- A plan for which opt-in features to enable, and when
SAP BTP and integrations
How it updates: Services, adapters and APIs are updated continuously, with deprecations announced in advance.
What SAP changes
- APIs and adapters change version
- Old interfaces are deprecated
- Extensions run on updated runtimes
What can go wrong
- An interface fails silently after an update
- Extensions built on deprecated services
- Nobody owns the deprecation list
What we do
- Monitoring of deprecation notices for your landscape
- Interface and extension tests with every release
- Clean-core extensions that upgrade without rework
Six steps, repeated with every release
Scan
We read the release notes and what’s-new information for the products you run.
You get: A short list of changes that affect you
Assess
We map each change to your processes, custom code, extensions and interfaces.
You get: An impact report with owners and actions
Test
We run automated regression with Tosca, plus targeted tests for the changed areas.
You get: Evidence that your key processes still work
Fix
Custom code and extensions that need changing go to our Development Factory.
You get: Fixes ready before production is upgraded
Adopt
We recommend the new features worth switching on and configure the ones you approve.
You get: Value from each release, not just stability
Enable
We brief key users on what changed on their screens and in their processes.
You get: Users who are ready on day one
The cycle then starts again. Clean-core extensions make each turn faster, because custom logic sits beside SAP instead of inside it.
How release-ready are you?
Tick the statements that are true for your organisation today. Anything you leave unticked becomes part of your request.
What’s included
Release impact analysis
Every relevant change mapped to your processes, with an owner and an action.
Automated regression testing
Tosca test packs for your key processes, run with every release.
Feature adoption recommendations
New features that could help you, explained in business terms.
Custom code and extension fixes
Changes handled by our Development Factory before production is upgraded.
Interface and integration checks
Interfaces to and from SAP tested against each release.
Key-user briefings
Short notes and sessions on what changed for each team.
Before and after
Release day without a plan
- Release notes too long for anyone to read
- Testing done by hand, by busy key users
- Problems found in production
- New features never switched on
Release day with INK
- A short impact report for your processes
- Automated regression in the test system
- Fixes in place before production is upgraded
- A shortlist of features that add value
Products we manage releases for
- SAP Cloud ERP, public edition
- SAP S/4HANA private edition
- SAP S/4HANA on-premise
- SAP SuccessFactors
- SAP BTP
- SAP Integration Suite
- SAP Analytics Cloud
Related: iCare AMS · Development Factory · Quality Engineering & Test Automation · SAP Development & Clean Core
Make your next SAP release a non-event
Tell us which SAP products you run. We’ll show you what the next release changes for you and how we would test it.
Frequently asked questions
Can we skip an SAP Cloud ERP public edition upgrade?
No. SAP upgrades every public edition customer on its own schedule, so each release needs to be reviewed and tested before it reaches production.
How do you test each release?
We run automated regression testing with Tosca for your key processes, plus targeted tests for the areas the release changes.
Do you manage SuccessFactors releases?
Yes. We review each 1H and 2H release in your preview instance, test your configuration and integrations, and plan which opt-in features to enable.
What happens if a release breaks our custom code?
Custom code and extensions that need changing go to our Development Factory, so fixes are ready before production is upgraded.