SAP CPQ Release Notes: What Changed and What to Do About It
We follow every SAP CPQ release, read the breaking changes before they reach your tenant, and turn each new version into a short list of things your administrators actually need to check.
Release Notes Are Easy to Find. Knowing What They Mean Is Harder.
SAP CPQ release notes are the official record of what SAP changed in each version of SAP CPQ. SAP publishes them on the SAP Help Portal through the What's New Viewer for SAP CPQ. Every release carries a four digit number in which the first two digits are the year and the last two are the month, so release 2608 is the August 2026 release and 2602 is the February 2026 release.
Finding that page is the easy part. The harder part is working out which of the listed entries touch your tenant. Something that reads like a small documentation improvement can mean a reworked field, a changed API response, or a script that quietly stops behaving the way your team expects. We read each release with your configuration in front of us, which is a different exercise from reading it in general.
Which engine you run changes what you should read. SAP maintains separate administration guides for the Quote 1.0 and Quote 2.0 engines, so an entry can apply to one and not the other. Teams still on Quote 1.0 regularly spend time reading about features they cannot use yet. Our walkthrough of the 2605 release and the Quote 2.0 changes goes through that split in more detail.
Every SAP CPQ release we have covered
A small release with no new features and no breaking changes. The value sits in Quote 2.0 migration, Sales Area and variant pricing fixes, and it is the last quiet window before 2611.
What to watch in 2609
- The Quote Migration Tool now supports SAP Variant Configuration and Pricing products, so revisit any Quote 2.0 migration plan that excluded them.
- Material Price Group is available through a CTX tag and the iProduct scripting interface. Check whether custom lookups for variant pricing can be simplified.
- Product aliases now work with Sales Area enabled, in the UI and the Configurations V2 API. Retest alias scenarios if you parked them.
- Workflow custom action visibility, DocuSign document retention on reassigned quotes and pricebook loading for dynamic part numbers were fixed. Include them in regression tests.
- Plan ahead: the SAP CX AI integration is no longer supported as of 2611, and HttpWebClientProtocol is removed in 2702, so scripts should move to RestClient.
A readiness release rather than a feature release. Most of the work sits in what is being removed or changed, not in what is being added.
What to watch in 2608
- The Customers concept in Quote 2.0 is being sunset, so anything that still reads or writes customers through the old model needs to move to business partner handling.
- Add Row endpoints change behaviour, which affects every integration or script that adds quote items programmatically.
- Specific properties are removed from Approvals UI customizations, so custom approval screens need a pass before the upgrade.
- Quote replication to SAP S/4HANA and Deploy or Send Changes setups belong in the impact review, not in post-upgrade firefighting.
- Quote List API consumers should be checked against the current response, and CX AI usage confirmed before assuming it is dormant.
- With 45 fixes in the release, Parallel Quoting and Sales Area deserve regression tests because that is where custom logic tends to live.
A small, administrator focused release: one new feature, two improvements and six resolved issues, with the useful part in the fixes.
What to watch in 2606
- Built-In Support is the new feature. Decide where it appears, which administrators can use it, and how it fits the support process you already run.
- Audit trail logging now records actual business partner custom field changes, so verify the logs after API updates and replication events.
- The ApprovalRule.IsViolated CTX formula fix changes how workflow conditions evaluate. Every approval rule using it needs a retest.
- Opportunity ID is preserved during quote reassignment, which is worth confirming against your own reassignment scenarios.
- Configuration preview with quote context is removed from Quote 1.0 setup because it only applies to the new engine.
The largest release of the year so far, weighted heavily towards Quote 2.0, Sales Area and the API surface, plus one entry SAP marks as recommended.
What to watch in 2605
- SHA-1 certificate generation is discontinued. This is the only entry in the release marked as recommended: inventory SHA-1 certificates, generate SHA-256 replacements, and test the affected integrations before production cutover.
- Product Custom Fields arrive as a real extension point for Quote 2.0 and can replace some custom tables and replication flows you built to work around their absence.
- Sales Area becomes a first class dimension: field translations, Quote Comparison support, reconfiguration triggered by Sales Office and Sales Group, and Incoterms Location as a standard quote field.
- QuoteItemBulkUpdate replaces item by item update calls. Worth evaluating for existing integrations, and worth testing how pricing recalculates after a bulk update.
- Scripting reaches further into workflow context, including approval actions and a reprice action, so scripts touching approvals and repricing need a review.
- Event subscriptions can be deactivated instead of deleted, and Send and Deploy packages now carry approval branches, so deployment routines change too.
A mixed release with real breaking changes underneath the sales facing improvements, mostly around authentication, scripting and identity.
What to watch in 2602
- Custom Tables API authentication changes. Integrations and middleware need updating, then a smoke test that reads and writes the expected records.
- IronPython eval() is deprecated. Inventory the scripts that rely on it, refactor them, and retest pricing, configuration and document generation paths that depend on those scripts.
- The federation route migration is announced. Review the federation setup, confirm routing matches the new approach, and check what it means for SSO and user onboarding.
- The licensing and access model shifts to support external users, which is a commercial question as much as a technical one.
Where SAP publishes release information
Four places, and they are not interchangeable. All of them sit in the SAP CPQ documentation on the SAP Help Portal.
- Latest Breaking Changes and Announcements. Read this one first. It is where SAP flags removals, deprecations and behaviour that will differ after the upgrade.
- What's New Viewer for SAP CPQ. New and changed features for the current release.
- What's New Viewer History. The same entries for earlier releases, which is what you need when catching up after a skipped upgrade window.
- Release Schedule and Dates. When the upgrade actually reaches your test and productive tenants.
SAP CPQ Release Questions We Get Asked
The list above links every breakdown we have published. These are the questions teams ask us most often when a new SAP CPQ release is on the way.
Where are the official SAP CPQ release notes?
On the SAP Help Portal, in the SAP CPQ documentation. The What's New Viewer for SAP CPQ covers the current release and the What's New Viewer History covers earlier ones. Latest Breaking Changes and Announcements sits next to them and is the section to read first.
What does a release number like 2608 mean?
The first two digits are the year and the last two are the month. Release 2608 is the August 2026 release and release 2602 is the February 2026 release. SAP publishes the calendar for upcoming releases in the Release Schedule and Dates list on the SAP Help Portal.
Do we have to do anything before an SAP CPQ upgrade?
Usually yes, and usually not much. The work is reading the breaking changes and announcements for that release, checking whether any of them touch your scripts, integrations, or configuration, and testing the affected flows in a non productive tenant before the productive upgrade date. Where that turns into a recurring burden, it belongs in an ongoing SAP CPQ maintenance arrangement rather than in a scramble every few months.
What usually breaks after an SAP CPQ release?
Custom IronPython scripts and integrations, more often than standard functionality. Both depend on behaviour that SAP can change between versions, and both sit outside the standard product, so nothing warns you automatically.
Does every release note entry apply to our tenant?
No. Entries can be specific to the Quote 1.0 or Quote 2.0 engine, to functionality you have not switched on, or to areas you do not use. Checking the entry against the administration guide for your engine is the quickest way to tell whether it is relevant.
Can our own administrators handle release checks?
Most teams can, once the routine is written down. We set the checklist up with your administrators, run the first few releases alongside them, and stay available for the entries that need a judgement call. Our training for internal SAP CPQ administrators covers the same ground.
Want a Second Pair of Eyes on the Next SAP CPQ Release?
We go through the release notes with your configuration in front of us, tell you what needs attention, and help your administrators handle the rest. If your tenant has drifted across several releases, an SAP CPQ health check is usually the better place to start.
Recent testimonials from our clients
Isidora and Milos are real CPQ experts in all aspects. They know the all the ins and outs of CPQ and can translate their in-depth technical knowledge to business use cases. They have a good mix of sticking to the standards and being flexible to implement the required system in budget and time.
Isidora and Milos played crucial roles in designing and developing the SAP CPQ sales quote solution for my company. I was very fortunate to benefit from their SAP CPQ skills and knowledge and they brought the added benefit of being outstanding colleagues to collaborate with as people. It was a very productive and enjoyable experience.
What truly stands out about Isidora & Milos, is their ability to navigate the entire development lifecycle: from requirements, designing architectures to building intuitive front-end interfaces. They approached every challenge with a meticulous and innovative mindset, and showed terrific leadership and mentoring of the team.
Isidora is an exceptional professional. During our time working together, she demonstrated deep expertise in even the most obscure aspects of the SAP CPQ product. Her outstanding problem-solving abilities enabled us to resolve highly complex issues with speed & efficiency.
Reliability is the word describing Sovetect’s work. All chalenges thrown at them were met with engineer’s curiosity and professional’s commitment, always resulting with job well done. Any project having them as implementators, no matter the technology or business chalenges, will thrive.