SAP CPQ 2609: A Small Release With Real Migration Fixes

SAP CPQ 2609 went live on productive tenants on September 12, a week after the sandbox upgrade. The What’s New Viewer lists sixteen entries in total: three improvements, twelve resolved issues and one announcement about a hotfix. No new features. No breaking changes.

That is not a complaint. Small releases like this one tend to fix exactly the things that make teams nervous about Quote 2.0, and 2609 follows that pattern closely. Migration, Sales Area and variant pricing get most of the attention, which is where a lot of SAP landscapes are spending their energy right now.

Below is how I read the release, what I would mention to a leadership team, and what I would put on the admin backlog now that the bigger 2611 release is only a few weeks away.

What SAP CPQ 2609 actually contains

SAP runs two kinds of releases through the year. The larger ones, like 2605 and 2608, come with a pre-upgrade testing window and a long list of changes. The smaller ones in between, like 2603, 2606 and now 2609, skip that window and go straight to sandbox and production. If you track every version on our SAP CPQ release notes overview, you will see the rhythm clearly: big release, small release, big release.

According to SAP’s published schedule, the sandbox upgrade happened on September 5, 2026, and the productive upgrade followed on September 12. There was no pre-upgrade testing phase for this version. The viewer also lists hotfix 2609.0.1, valid as of September 12, with a note that it brings no documentation updates.

In practice, your production tenant is already on 2609. So the useful question now is what changed, and whether any of it touched your own setup.

Last month I pointed out that the 2608 release was mostly stability work rather than headline capability, and 2609 goes even further in that direction. Every entry is tagged Info only, so SAP is not asking you to do anything. That does not mean nothing matters. Several of the fixes touch areas where custom logic usually lives, and those are the areas worth a quick regression pass.

The full list, with area and user type for each row, sits in the SAP CPQ What’s New Viewer. Pick version 2609 and set the page size to 25, otherwise you will only see ten rows.

The three SAP CPQ 2609 improvements worth a leadership conversation

Improvements are rarely exciting on paper, but these three each remove a reason to delay a Quote 2.0 move or keep a workaround running.

Quote Migration Tool now handles variant configuration products

This is the entry I would put at the top of any summary. The Quote Migration Tool now supports products that use SAP Variant Configuration and Pricing (VCP). Until now, teams with VCP products in their catalogue had a gap in their Quote 1.0 to Quote 2.0 plan, and that gap usually turned into manual work or a postponed migration.

The same release also fixes a related bug. The tool used to fail when migrating product and item configurations for products with the System of Configurable Products display type. SAP says configurations now migrate correctly.

For a CEO, the short version: fewer exceptions in the migration plan, and fewer quotes that need to be rebuilt by hand. If your configuration logic still lives in S/4HANA, it is worth reading how configuration logic moves between LO-VC and SAP CPQ before you decide what to migrate and what to leave where it is.

Material Price Group for variant pricing

The second improvement is for administrators and pricing owners. SAP CPQ now exposes the Material Price Group through the CTX tag <*CTX(Product.MaterialPriceGroup)*> and through the MaterialPriceGroup property in the iProduct scripting interface. SAP describes the purpose as calculating prices retrieved from the SAP Variant Configuration and Pricing service more accurately.

Material price group is a familiar field for anyone who has worked with SD pricing, because condition records often depend on it. Having it available in CPQ tags and scripts means fewer custom lookups just to get a value that already exists in the ERP. It also fits the broader trend from 2608, where product hierarchy, sales text and material price group moved towards configuration instead of custom development. Teams that rely on attribute pricing and price books should check whether any existing script can now be simplified.

The third improvement is small but practical. When you import a multi-sheet Excel file in Quote 2.0, SAP CPQ now processes all valid sheets and skips the malformed ones. Before, one badly formatted sheet could make the whole import fail. Anyone who has watched a sales rep retry the same upload five times will appreciate this one.

Fixes that remove friction for sales and admins

Twelve of the sixteen entries are resolved issues. Most are narrow, but a few of them hit exactly the places where users lose trust in a system.

Sales Area and product aliases finally work together

This is the most detailed entry in the release. With Sales Area enabled, product aliases had several problems. Alias items were wrongly marked invalid when a quote’s sales area or effective date changed. Aliases could not resolve sales area fields such as division and statuses, because they have no sales area record of their own. And the visibility check in the Configurations V2 API did not recognise aliases at all.

SAP’s fix makes aliases inherit the parent product’s sales area record and respect the effective date. The result, in SAP’s own description, is that you can configure and add product aliases to a quote through the UI or the Configurations V2 API and have them processed correctly. If you parked aliases when you switched Sales Area on, this is the release to revisit that decision.

Two smaller Sales Area items sit next to it. Business Partner Permission conditions that use Sales Area relevant custom fields no longer throw an SQL generation error. And a new CTX tag, <CTX( Quote.SelectedMarket.CurrencyCode )>, returns the currency code of the quote’s market, which SAP notes you can combine with the market code tag in the Sales Area Migration Tool when your use case needs it.

Workflow, documents and pricing performance

Three fixes affect the daily experience of sales teams more than anything else in 2609.

Custom actions now display correctly after status transitions in Quote 2.0 workflows, including setups where pre-actions validate whether an action is available. Generated documents no longer go missing from the Document tab after a completed DocuSign signature on quotes that were reassigned to a new owner. And configurations with many dynamic part number attribute values now load pricebook prices through a bulk query instead of many individual searches, which SAP says significantly reduces slowdowns.

Each of these is the kind of issue that ends up as a support ticket titled “CPQ is broken again”. Because they touch workflows, documents and pricing, I would include them in a short regression testing routine for CPQ rather than assume they behave the same way in your specific setup.

API and configuration language

Configurations V2 API used to create a configuration in a default language and then load it again for every different Accept-Language value in later requests. Now you can create the configuration in the language you need from the start. Headless front ends serving several markets should see fewer redundant loads.

Quality of life for administrators

The Involved Parties tab no longer pushes the remove icon below long Business Partner names, and the stale error about invalid partners disappears once they are removed. The Workbench link in Global Script opens the current script in Script Workbench. Tooltips are back on the Script Performance and System Errors and Warnings graphs. And the Developer Console and Logs page no longer show misleading errors when a new revision is created. Those messages never affected revision creation, but they did cost admins time.

What to put on the admin backlog before 2611

2609 asks nothing of you, but the next release will. According to SAP’s schedule, 2611 has pre-upgrade testing from October 14 to 30, 2026, the sandbox upgrade on October 31, and the productive upgrade on November 14. Two announcements on SAP’s breaking changes page deserve attention now, while there is still time.

SAP CX AI integration ends with 2611

SAP will no longer support the SAP CPQ and SAP CX AI integration as of 2611, because SAP CX AI itself is being discontinued. The announcement dates back to March and was later moved to 2611. SAP lists limited functionality, no extensibility, outdated technology and incomplete interoperability as the reasons, and it says the change does not remove AI capabilities from SAP CPQ. SAP marks it as needing no action, but if any team still counts on that integration, now is the time to say so openly rather than discover it in November.

HttpWebClientProtocol is on its way out

This one needs real work. The IHttpWebClientProtocol interface, available as HttpWebClientProtocol in scripting, is deprecated and will be removed in 2702. SAP asks customers to move to the RestClient interface, which handles headers, JSON, authentication helpers and methods like PATCH and DELETE out of the box.

SAP’s published timeline puts runtime warnings in Q3 2026, across 2608 and 2611, and removal in Q1 2027. Any IronPython script that calls external services with the old interface will stop working after that. The fix is usually not hard, but finding every script is. This is exactly the kind of task that fits into ongoing SAP CPQ maintenance work instead of a rushed ticket in January. SAP’s deprecation notice for IHttpWebClientProtocol includes before and after code samples you can hand straight to your developers.

A simple plan for the next eight weeks

Run a search for HttpWebClientProtocol across all scripts this month. Confirm whether anyone uses the CX AI integration. Book time for the 2611 pre-upgrade testing window in October. Then use SAP CPQ 2609 as a calm quarter to test the migration and Sales Area fixes against your own data. If your team does not have the capacity, working with SAP CPQ experts who follow each release is usually less disruptive than an unplanned outage.

In short:

• SAP CPQ 2609 is already live in production, with three improvements, twelve fixes and no breaking changes.
• The most valuable changes are VCP support in the Quote Migration Tool, Material Price Group for variant pricing, and working product aliases under Sales Area.
• Use the quiet release to prepare for 2611 and to replace HttpWebClientProtocol before its removal in 2702.

If you want a second pair of eyes on your 2611 readiness, we are happy to walk through your scripts and Sales Area setup with you.