SAP CPQ 2605 Release Notes: What Changed in Quote 2.0, Sales Area, APIs, Scripting, and Administration

Posted by

Milos

April 29, 2026

On April 29, 2026

SAP CPQ 2605 is a broad and practical release. It does not focus on one isolated area of the product. Instead, it strengthens several parts of the SAP CPQ landscape at the same time: Quote 2.0, Sales Area handling, product and business partner data extensibility, integration scalability, scripting, administration, deployment, document generation, security, and everyday user experience.

Based on the SAP CPQ 2605 release notes, valid as of May 2, 2026, this release includes 59 entries in total:

10 new features
16 improvements
33 resolved issues
51 entries touching Quote 2.0
26 administrator-focused entries
33 general user-focused entries
1 recommended action, related to SHA-1 certificate generation

The overall direction is clear: SAP is continuing to mature Quote 2.0 as the strategic quote engine, while also reducing friction in enterprise scenarios that depend on complex product data, Sales Area logic, integrations, scripting automation, multi-user collaboration, and controlled transport between environments.

This article provides a detailed analysis of what changed in SAP CPQ 2605, why the changes matter, and what SAP CPQ administrators, architects, developers, and business teams should review before and after the upgrade.

Executive summary: the main themes in SAP CPQ 2605

SAP CPQ 2605 is best understood through six major themes.

First, Quote 2.0 becomes more extensible. Product Custom Fields, business partner custom fields with Sales Area dimension, and new scripting capabilities make it easier to adapt SAP CPQ to complex business models without relying as heavily on custom workarounds.

Second, Sales Area support becomes more complete. The release improves translations, quote comparison, pricing context, quote reconfiguration triggers, business partner fields, and Incoterms handling in Sales Area-enabled environments.

Third, integration scenarios become more scalable. The new QuoteItemBulkUpdate REST API, self-service enablement for SAP Variant Configuration and Pricing, and performance improvements around effective date changes are important for customers with large quotes, Sales BOM structures, external systems, or advanced pricing integrations.

Fourth, administration and deployment are safer and more manageable. SAP CPQ 2605 improves event subscription management, quote table action permission deployment, approval branch deployment, workflow deployment validation, document template delegation, and error/warning visibility.

Fifth, developer experience improves. Administrators and developers can launch Visual Studio Code directly from SAP CPQ when working with global scripts, use more workflow actions from scripts, trigger repricing programmatically, and monitor frequent errors more easily.

Sixth, many resolved issues focus on operational reliability. Fixes across approvals, reassignment, layouts, filters, generated documents, business partner replication, autocomplete behavior, date conversion, and custom templates all contribute to a more stable daily experience.

1. Product Custom Fields: a major extension point for Quote 2.0

One of the most important new features in SAP CPQ 2605 is Product Custom Fields for Quote 2.0.

SAP CPQ now supports custom fields for products, allowing administrators to extend the product data model through configuration. These fields can be defined at the product header level and at the Sales Area level. They are also available through CTX tags, scripting, and product integration REST APIs.

This matters because product-related customization is one of the most common sources of complexity in CPQ implementations. Many companies need additional product metadata for pricing, eligibility, quoting logic, document generation, approvals, reporting, or integration with backend systems such as SAP S/4HANA.

Before this enhancement, some teams had to rely on custom tables, additional replication flows, or implementation-specific extensions to represent product attributes that were not part of the standard product model. With Product Custom Fields, more of that logic can now be modeled directly in SAP CPQ configuration.

Why Product Custom Fields matter

Product Custom Fields can reduce unnecessary customization in several ways.

They make product extensions easier to govern because the custom data becomes part of the CPQ product model rather than a separate workaround. They can also simplify integrations because product-related custom values can be accessed through supported APIs rather than through custom replication mechanisms. For Sales Area-specific product behavior, they provide a cleaner way to define values that differ by sales organization, distribution channel, division, or other Sales Area dimensions.

For enterprise SAP CPQ landscapes, this is especially relevant because product data rarely exists in isolation. It often has to remain aligned with backend master data, pricing logic, configuration rules, sales documents, templates, and approval processes.

What teams should review

Teams should review existing product-related custom tables and identify whether some of them can eventually be replaced or simplified using Product Custom Fields. They should also decide which fields belong at the product header level and which fields need Sales Area-specific behavior.

It is also important to test how these fields behave in CTX tags, scripting, document generation, product integration APIs, and downstream processes. Product Custom Fields are not just a data-model feature; they can affect the logic layer and integration layer as well.

2. Sales Area becomes a stronger first-class dimension

SAP CPQ 2605 includes several changes that make Sales Area handling more complete and practical for enterprise quoting scenarios.

The Sales Area-related changes include:

translation support for Sales Area fields
Quote Comparison support with Sales Area entities
quote reconfiguration triggers based on Sales Office and Sales Group changes
pricing context configuration for SAP Variant Configuration and Pricing
business partner custom fields with Sales Area dimension
Incoterms Location as a standard Quote field when Sales Area is enabled

Together, these updates show that SAP is continuing to make Sales Area a more deeply integrated concept in Quote 2.0.

Translation support for Sales Area fields

Sales representatives can now view Sales Area entity names in their target language. Translation support applies to sales organizations, distribution channels, divisions, payment terms, shipping conditions, and Incoterms.

This is important for multinational sales organizations where the same SAP CPQ tenant may support users across multiple countries or regions. Without proper translation support, Sales Area data can become difficult for end users to interpret, especially when codes or backend-oriented labels are exposed directly in the quote interface.

Quote Comparison with Sales Area entities

SAP CPQ 2605 also improves Quote Comparison when Sales Area is enabled. Sales organizations, distribution channels, and divisions are now presented with both codes and names.

This is useful because Quote Comparison is only reliable when users can clearly understand what is being compared. In Sales Area-enabled environments, two quotes may differ not only by products and prices but also by organizational context. Showing both codes and names helps reduce ambiguity.

Sales Office and Sales Group can trigger reconfiguration

Changes in Sales Office and Sales Group can now be used as triggers for quote reconfiguration. Administrators can configure these events on the Sales Area Parameters page.

This is a meaningful improvement because Sales Office and Sales Group can influence eligibility, pricing, responsibilities, approval logic, routing, and business rules. If a quote changes organizational context, the configuration may need to be recalculated to remain valid.

Pricing context for SAP Variant Configuration and Pricing

Administrators can now configure which partner functions should be used to determine pricing context for integration with SAP Variant Configuration and Pricing. Specifically, they can configure partner function mappings for Exchange Rate Type and Customer Pricing Procedure.

This is important because pricing in SAP landscapes often depends on more than the product and quantity. Customer context, partner roles, exchange rate types, and pricing procedures can all influence the final result. Better control over pricing context helps ensure that CPQ pricing behavior remains aligned with backend pricing expectations.

Business Partner Custom Fields with Sales Area dimension

SAP CPQ 2605 also introduces Sales Area dimension support for business partner custom fields. Previously, business partner custom fields could be defined at the business partner level. With this release, they can also be defined as Sales Area elements.

This is especially relevant when the same business partner has different attributes depending on sales organization, distribution channel, or division. For example, payment terms, account classifications, partner-specific flags, or commercial attributes may vary across Sales Areas.

Incoterms Location as a standard Quote field

SAP CPQ 2605 adds the Incoterms Location field to the list of standard Quote fields when Sales Area is enabled.

For companies that quote across borders, regions, or shipping responsibilities, Incoterms-related data can be commercially and legally important. Making Incoterms Location available as a standard field reduces the need to model this information manually.

3. Quote 2.0 automation: scripting can do more in workflow context

SAP CPQ 2605 expands what can be automated through scripting in Quote 2.0.

The release introduces the ability to trigger standard approval actions from scripts in workflow context. Supported actions include:

Submit for Approval
Retract Approval Process
Approve
Reject

These actions remain governed by workflow permissions, and configured pre-actions, post-actions, and notifications are triggered as expected. This is important because scripted automation should not bypass workflow governance. Instead, it should execute standard workflow behavior in a controlled way.

Why scripted approval actions matter

Approval workflows are often one of the most implementation-specific areas of SAP CPQ. Companies may need to automate approval submission after a quote reaches a certain status, retract approval under defined conditions, or trigger approval-related behavior as part of a larger scripted process.

By exposing approval actions in scripting, SAP CPQ gives implementation teams more flexibility while preserving standard workflow logic.

However, this feature should be used carefully. Any scripted approval process should be tested against workflow permissions, user roles, notification behavior, audit requirements, and edge cases such as reassigned quotes or multi-level approval flows.

Reprice action through scripting

SAP CPQ 2605 also allows the Reprice action to be triggered directly from scripts in Quote 2.0 using the WorkflowExecutor object.

This is useful when pricing needs to be recalculated as part of a controlled automation sequence. For example, a script may update fields, adjust quote structure, or respond to workflow events before triggering repricing.

The key implementation consideration is sequencing. Repricing should happen after all required data changes are complete, and teams should verify that pricing results remain consistent with expected quote and backend pricing logic.

RemoveItemFromSection method

SAP CPQ 2605 introduces the RemoveItemFromSection method, which can be called from scripting.

This addresses scenarios where users or scripts need to remove items from quote sections programmatically, especially in Solution Design contexts with dynamic section content. For advanced implementations, this gives teams more control over quote structure and section management.

4. API and integration improvements: fewer calls, better scalability

SAP CPQ 2605 includes several integration-related improvements, with the new QuoteItemBulkUpdate REST API standing out as one of the most important.

QuoteItemBulkUpdate API

The new QuoteItemBulkUpdate API allows external systems and integrations to update multiple quote items and item-level fields in a single request.

Previously, integrations often had to update quote items individually. That approach can create performance problems, especially for large quotes, configurable products, complex Sales BOM structures, or automated quote maintenance scenarios.

With QuoteItemBulkUpdate, multiple item columns across multiple quote items can be updated at the same time. Pricing recalculation is automatically triggered, and the update is processed as a single operation that follows existing quote and pricing logic.

Why QuoteItemBulkUpdate matters

Bulk item updates are common in real CPQ scenarios. External systems may need to update quantities, dates, discounts, attributes, classifications, or integration-specific fields across many quote lines.

If each item update requires a separate API call, performance can degrade and the risk of mid-process changes increases. A bulk operation reduces API overhead and supports more reliable integration patterns.

For teams maintaining SAP CPQ integrations, this is a strong candidate for technical review. Existing item-by-item update logic may be simplified or optimized using the new API.

Self-service enablement for SAP Variant Configuration and Pricing

Administrators can now enable SAP Variant Configuration and Pricing integration independently, without contacting SAP Support.

This is an important administrative improvement because it reduces dependency on external enablement steps. The integration can be activated with recommended default settings, while advanced configuration parameters are exposed in the administration interface.

For new customers, this can accelerate setup. For existing customers, it provides more control over when and how optimized settings are adopted.

Effective date change performance optimization

SAP CPQ 2605 introduces a performance optimization for effective date change calls during integration with the SAP Variant Configuration and Pricing service.

A consolidated API call now handles effective date changes across many quote items, reducing system overhead and improving response times. This is particularly useful for quotes with many line items.

This functionality is available for early adopters only and requires a request to SAP Support.

Business partner integration improvements

The release also improves several business partner-related scenarios.

Business Partner Quick Search on the Involved Party tab is now faster because it retrieves only the information needed to display results. SAP CPQ also adds clearer Event Log messages when Business Partner replication fails, including the failed entity, reason, externalID, partnerID, and systemID.

Another resolved issue ensures that business partner replication preserves customizations made in post-exit processes, especially for Sales Area data modifications.

These changes are important because business partner data is central to quote accuracy, pricing, approval, and downstream integration.

5. Developer experience: better tooling and better visibility

SAP CPQ 2605 includes several changes that improve the developer and administrator experience.

Launching Visual Studio Code from SAP CPQ

Administrators can now launch Visual Studio Code directly from the Global Scripts page in SAP CPQ Setup. When the SAP CPQ Scripts Plugin is installed, Visual Studio Code supports script editing capabilities such as creating and modifying global scripts, validating scripts, attaching events, and pushing changes back to SAP CPQ.

This is a practical improvement for teams that maintain a significant amount of SAP CPQ scripting. It reduces context switching and makes the scripting workflow more familiar for developers who already work in modern IDEs.

Most Frequent Errors and Warnings page

SAP CPQ 2605 adds a comprehensive table showing system errors and warnings with monthly history. This is available through Developer Tools under Most Frequent Errors and Warnings.

The Setup Home page also displays the top five errors and warnings from the previous day.

This is valuable because many SAP CPQ issues are not immediately visible to business users. They may appear as intermittent behavior, slow troubleshooting cycles, or unexplained failures in specific scenarios. Better visibility into frequent errors helps administrators identify patterns earlier.

Quote Item Custom Fields page rewritten to Angular

The Quote Item Custom Fields page in Quote 1.0 has been modernized with an Angular-based design and usability improvements.

Although this is not a functional change on the same level as Product Custom Fields or QuoteItemBulkUpdate, it contributes to a more consistent administration experience.

6. Collaboration and multi-tab quoting

SAP CPQ 2605 introduces and stabilizes several collaboration-related capabilities.

Parallel Quoting

Parallel Quoting, also referred to as Multi-Tab Quoting, allows users to work on multiple quotes simultaneously in separate browser tabs. This means users can reference other quotes without losing their current work.

This functionality is available for early adopters only and requires a request to SAP Support.

Parallel Quoting is a significant usability improvement for sales teams, solution designers, and quote specialists who often compare quotes, copy logic, validate configurations, or work across several customer scenarios at the same time.

However, it also introduces implementation considerations. Teams should test how multi-tab behavior interacts with quote locking, pricing recalculation, scripting, configuration context, approval actions, and user permissions.

Public parameters for Multi-User Quote Collaboration

Two application parameters controlling Multi-User Quote Collaboration are now publicly available in General Application Parameters under Shopping Cart and Quotes.

Administrators can now enable or adjust collaboration behavior without backend assistance. The available parameters control real-time collaboration indicators and quote collaboration notifications.

This gives administrators more direct control over collaboration behavior in Quote 2.0.

Multi-tab resolved issues

SAP CPQ 2605 also resolves several issues related to multi-tab usage.

Error handling has been improved for quotes with multiple revisions when some revisions are not visible to the user. Editing quotes in multiple tabs using scripts now retains configuration context properly when scripts are called from product events. An issue with launching the Configurator from a quote with custom visibility permissions and Multi-Tab enabled has also been resolved.

Together, these changes suggest that SAP is not only introducing multi-tab functionality but also hardening the surrounding technical behavior.

7. Administration, deployment, and document management improvements

SAP CPQ 2605 contains several improvements that are especially relevant for administrators and platform owners.

Activating and deactivating event subscriptions

Administrators can now deactivate event subscriptions instead of permanently deleting them.

This is useful for testing, troubleshooting, phased rollouts, and temporary process changes. Instead of removing a subscription and later rebuilding it, administrators can turn it off while preserving its configuration.

Enhanced deployment handling for Quote Table action permissions

SAP CPQ 2605 improves deployment handling for Quote Table action permissions to prevent foreign key conflicts.

The updated package format includes both permission list IDs and permission system IDs. If a package includes system IDs, they are used to correctly identify and insert associated permissions. Older packages without system IDs continue to rely on permission IDs.

This improves compatibility and reduces deployment failures between environments.

Approval Branch copied via Send and Deploy

When approval rules are copied between tenants using Send and Deploy, the associated approval branch is now automatically included in the deployment package. If the approval branch does not exist in the target tenant, it is created and linked to the approval rule.

This reduces manual configuration after deployment, especially in tenants with many approval rules.

Workflow deployment status validation

SAP CPQ 2605 resolves an issue where workflow package deployment could fail with a fatal error if the destination environment did not contain a status referenced in the source workflow.

The system now validates the status before deployment. If the status does not exist, deployment stops safely and logs an informative error message explaining which status is missing.

This is a small but important improvement for release management because it turns a fatal deployment failure into a controlled validation error.

Delegated access rights for document templates

The release introduces delegated access rights for document templates. Administrators can grant local users specialized permissions to manage specific document templates independently.

This supports decentralized template ownership while maintaining governance. In large organizations, document templates may be owned by different regions, product teams, legal teams, or business units. Delegated access helps reduce administrative bottlenecks.

PDF generated document compression

Administrators can now enable PDF image compression on the Document Generation Templates page and configure compression settings. This helps when generated documents contain images and need to be sent by email.

For companies with image-heavy proposals, product sheets, or quote attachments, this can reduce document size and improve deliverability.

Automatic synchronization with SAP Build Work Zone

SAP CPQ now supports automatic synchronization of its content in SAP Build Work Zone. After SAP CPQ is registered as a content provider, new tiles or features are automatically reflected in the customer’s SAP Build Work Zone tenant.

This removes the need to manually refresh or re-sync the content channel.

8. Security update: SHA-1 certificate generation discontinued

The only item marked as Recommended in the SAP CPQ 2605 release notes is the security update related to SHA-1 certificates.

SAP CPQ no longer supports generating new SHA-1 system certificates. New system certificates are generated only as SHA-256 certificates from Certificate Management under System Certificates.

Existing SHA-1 certificates still work, but SAP recommends replacing them as soon as possible to prevent security vulnerabilities.

Why this deserves attention

This is the clearest action item in the release. It may not break existing integrations immediately, but it should be treated as a security and technical debt item.

SAP CPQ administrators should inventory existing SHA-1 certificates, identify integrations or authentication flows that depend on them, generate SHA-256 replacements, test connected systems, and plan a controlled cutover.

A practical checklist would include:

Review all system certificates in SAP CPQ.
Identify any active SHA-1 certificates.
Map each certificate to the integration, authentication, or connected system using it.
Generate SHA-256 replacements.
Test the replacement certificates in a non-production environment.
Coordinate certificate updates with external systems or middleware.
Monitor integrations after production cutover.

Because certificate changes can affect authentication and integrations, this should be handled carefully rather than left until an urgent security review.

9. Resolved issues: what changed and what should be regression-tested

SAP CPQ 2605 includes 33 resolved issues. Many of them may look small individually, but together they improve reliability across approvals, quote reassignment, layout behavior, generated documents, business partner replication, deployment, scripting, and configuration.

The resolved issues can be grouped into several practical areas.

Approval and workflow fixes

SAP CPQ 2605 resolves an issue where approval workflows in Quote 2.0 did not function correctly after a quote was reassigned to a different owner. Reassigned quotes can now be opened and reviewed by the new owner and approvers, and Approve and Reject actions work as expected.

The release also fixes a multi-level approval issue where approvers from a previous approval level were incorrectly removed after a later approver rejected the quote. All eligible approvers are now correctly displayed when the approval process restarts.

Delegated approvers, such as managing parents, approving parents, and ordering parents, can now submit quotes for approval from the Waiting for Approval tab.

Another workflow-related fix ensures that pre-actions and post-actions for Add Asset to Quote Items execute in the correct order. Pre-actions now run before items are added, while post-actions run after completion.

These fixes are important because approval workflows are often business-critical. Even small inconsistencies can delay quotes, create audit concerns, or confuse approvers.

Quote reassignment and data retention

SAP CPQ 2605 fixes an issue where the Reassign action unintentionally cleared Opportunity ID and Sales Order ID. These values are now retained on the new quote.

This matters for CRM and ERP-connected processes where opportunity and sales order references are essential for traceability.

The Quote Reassign dialog also now includes autocomplete search, making it easier to find users in large user lists. The search supports contains matching rather than only starts-with filtering.

Layout, permissions, and UI state fixes

Several resolved issues improve the Quote 2.0 user interface and layout behavior.

Layout permission groups now re-evaluate when a quote is loaded. Previously, quote layouts such as item columns were not always refreshed when opening an existing quote, which could cause incorrect column visibility.

SAP CPQ also fixes item order changes in the Solution Design tab, filter modal settings being overwritten by saved filters, filter search focus jumping in Solution Design, line item display preferences not persisting between sessions, and totals/footer labels appearing incorrectly in read-only configuration view.

These fixes improve usability, but they also reduce the risk of user mistakes caused by misleading or inconsistent UI behavior.

Product configuration and custom field fixes

SAP CPQ 2605 fixes an issue where configuration options were not displayed in the Configurator after creating a new product version through knowledge base sync under certain conditions.

The release also resolves an autocomplete issue where a quote item custom field sourced from a custom table displayed values incorrectly across line items because the preselection filter was not evaluated independently per item.

Another fix ensures that AttributeValueCode is correctly resolved from the original display value rather than the translated value.

These changes are particularly relevant for environments with complex product configuration, translated attributes, custom tables, and quote item custom fields.

Integration and data correctness fixes

SAP CPQ 2605 resolves several integration and data integrity issues.

The DocuSign callback now executes with the correct user context. Previously, when an end customer signed a document through DocuSign, the audit trail could log the action under the quote owner rather than the guest user. The audit trail now records the action correctly.

The Price API import has also been fixed. When the parameter to show effective dates for price book entries is enabled, multiple entries with the same PartNumber-PriceCode combination can now be added through UpsertPricebook API if ValidFrom and ValidUntil differ.

A date format conversion issue has been resolved for custom table entries. Previously, dates in formats such as dd.mm.yyyy and mm.dd.yyyy could be saved with swapped day and month values when both values were between 1 and 12.

Business Partner replication now preserves customizations made in post-exit processes, particularly for Sales Area data.

These fixes should be included in regression testing for integrated SAP CPQ environments.

Document generation and template fixes

Users can now successfully download generated documents created from templates owned by other users without system failures.

SAP CPQ also now pre-compiles responsive templates, including custom templates marked as default, after code deployments. This prevents delays when users access SAP CPQ for the first time after deployment.

Another fix adjusts behavior around Additional Content files. When a formula returns no result, the system displays a user-friendly message instead of triggering unnecessary invalid filename validation and event log entries.

These changes improve reliability around generated documents, custom templates, and post-deployment performance.

Deployment and transport fixes

SAP CPQ 2605 resolves multiple deployment-related issues.

Workflow deployment now validates missing statuses before deployment fails. Autocomplete attribute search placeholders sourced from custom tables are now properly saved in the destination environment during deployment. Approval branches are included when approval rules are copied through Send and Deploy. Quote Table action permission deployment has also been improved.

These changes help administrators move configurations between tenants with fewer manual corrections.

10. SAP CPQ 2605 upgrade readiness checklist

For SAP CPQ teams preparing for release 2605, the following checklist can help structure the review.

Data model and configuration

Review existing product-related custom tables and custom replication flows. Identify whether Product Custom Fields can simplify the current model. Decide which product fields should be global and which should be Sales Area-specific.
Review business partner custom fields and determine whether any should be modeled with Sales Area dimension.
Check whether Incoterms Location should be added to quote layouts, templates, approval logic, or integrations.

Sales Area

Review Sales Area translations for sales organizations, distribution channels, divisions, payment terms, shipping conditions, and Incoterms.
Test Quote Comparison with Sales Area-enabled quotes.
Review whether Sales Office and Sales Group changes should trigger quote reconfiguration.
Validate partner function mappings for Exchange Rate Type and Customer Pricing Procedure if using SAP Variant Configuration and Pricing.

APIs and integrations

Evaluate whether existing item-by-item update integrations can use QuoteItemBulkUpdate.
Test pricing recalculation behavior after bulk updates.
Review integrations using Price API, Business Partner replication, DocuSign, and custom table date fields.
If relevant, assess early adopter availability for effective date change performance optimization.

Scripting and workflow

Review scripts that interact with approvals, repricing, quote sections, and product events.
Test scripted approval actions with workflow permissions, pre-actions, post-actions, and notifications.
Test multi-tab scripting scenarios if Parallel Quoting or Multi-Tab functionality is enabled.

Administration and deployment

Review event subscriptions and decide where deactivation is preferable to deletion.
Test Send and Deploy packages involving approval rules, approval branches, workflows, statuses, quote table action permissions, and autocomplete placeholders.
Review delegated access rights for document templates.
Consider enabling PDF compression for image-heavy generated documents.

Security

Inventory SHA-1 system certificates.
Generate SHA-256 replacements.
Test affected integrations and authentication flows before production cutover.
Prioritize this item because it is the only release note marked as Recommended.

User experience and regression testing

Test quote reassignment, approval flows, Solution Design behavior, Quote Comparison, generated document download, layout permission visibility, filter persistence, line item display settings, and custom responsive templates after deployment.
If using Sales Area, test end-to-end quote creation, reconfiguration, pricing, involved parties, document generation, and downstream integration.

Final takeaway

SAP CPQ 2605 is not just a maintenance release. It is a release that continues to move SAP CPQ toward a more configurable, integration-friendly, and enterprise-ready Quote 2.0 architecture.

The most important functional change is Product Custom Fields, especially for teams that previously relied on custom tables or custom replication flows to extend product data. The Sales Area enhancements are also significant because they make Sales Area more usable across localization, quote comparison, reconfiguration, pricing context, business partner data, and Incoterms.

On the technical side, QuoteItemBulkUpdate, self-service enablement for SAP Variant Configuration and Pricing, scripting enhancements, Visual Studio Code integration, improved error visibility, and deployment fixes all make the platform easier to build, maintain, and troubleshoot.

The most important action item is the SHA-1 certificate update. Existing SHA-1 certificates still work, but administrators should plan replacement with SHA-256 certificates as part of their security maintenance.

For SAP CPQ teams, the best way to approach release 2605 is not to treat it as a simple list of features. It should be reviewed as an upgrade readiness backlog: which changes simplify the current implementation, which integrations can be optimized, which scripts need testing, which Sales Area scenarios become easier, and which resolved issues reduce risk in daily quote operations.

Blog