What Is Planned For The 2611 Release Of SAP Variant Configuration And Pricing?

The 2611 release of SAP Variant Configuration and Pricing is planned to be deployed to BTP customer tenants on October 21, 2026:

Administration UI and Administration service:

Release	Test/Non-Productive & Productive Upgrades
2611	October 21, 2026

Variant Configuration service & Pricing service:

Release	Test/Non-productive Upgrade	Productive Upgrade
2611	October 21, 2026	November 11, 2026

This blog covers the following planned innovations:

Pricing service – Price Agreement Data in Stateless Pricing Response
Pricing service – Alternate Product Units Accessible in Pricing Extension Interface
Pricing service – Parent Item Access in Pricing Extension Interface
Pricing service – Application Filter and Language Filter on Condition Type GET Endpoint
Pricing service – Application Filter and Language Filter on Access Sequence GET Endpoint
Variant Configuration service – New AVC-Aligned Mode (General Availability)
Variant Configuration service – Configuration Engine Trace – Enhanced Header Information
Administration – Load Changed Variant Tables Only
Administration – Browser Title Added to Administrative UI Pages
Administration – Table Settings Enabled Including Persistency

It also includes a call to act regarding the following changes:

Administration – Load Changed Variant Tables Only

Please check the updated roadmap and release notes after the release date to see which of these features were delivered as planned.

Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to develop or release any functionality mentioned therein.

This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP's intentional or gross negligence.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Pricing service – Price Agreement Data in Stateless Pricing Response

A new value items-priceAgreement for the optional query parameter $select has been introduced for the stateless pricing endpoint. This enhancement enables callers to retrieve price agreement details alongside the pricing results.

Usage: POST /api/v1/statelesspricing?$select=items-priceAgreement

When multiple price agreements with different validities exist for the same condition type, the pricing engine selects one at runtime for calculation. Previously, the stateless response did not include price agreement data, making it impossible for callers to identify which agreement was applied.

Only when items-priceAgreement is requested, the response includes the price agreement details used during calculation for each item. This provides full transparency into which price agreement was selected and applied, enabling consuming applications to display accurate pricing information to end users.

More information will be published with the November release in the API Definition and the Development Guide (Pre-Production).

Pricing service – Alternate Product Units Accessible in Pricing Extension Interface

The pricing extension input interface has been enhanced to receive alternate product units from the pricing input payload, enabling custom routines to perform high-precision unit conversions during pricing calculation.

During quantity conversion, rounding errors may occur because the condition base is limited to 3 decimal places. When the sales unit and condition unit differ, the resulting condition base is truncated to 3 decimal places – causing discrepancies between the expected and actual calculated values.

SAP Note 22963 describes a formula-based workaround to perform the conversion at full precision using the numerator and denominator from the unit of measure conversion table (MARM in the back-end). Since MARM is not replicated, the only viable source for these values at runtime is the pricing input payload itself.

Previously, alternate product units present in the pricing input payload were not passed through to the extension interface, making it impossible for custom formulas to implement this workaround.

With this enhancement, alternate product units supplied in the pricing input payload under productDetails.alternateProductUnits are now accessible within the pricing extension interface at runtime. Custom local routines can read the numerator and denominator values directly during formula execution to perform the full-precision conversion without intermediate rounding.

More information will be published with the November release in the Extension Guide (Pre-Production).

Pricing service – Parent Item Access in Pricing Extension Interface

The pricing extension input interface has been enhanced to receive the parent item- and root item context, enabling custom formulas to implement cross-item pricing logic based on higher-level line item data.

When a pricing formula was executed for a condition of a child item, the extension interface only provided access to the current item's context. There was no way to navigate to the parent item from within the formula – making it impossible to implement pricing patterns where a child item's value depends on a condition of its higher-level item.

Example:

A main item has a condition value of 10,000.00 USD calculated at the document level
A child item has a percentage-based condition with a rate of 7.5%
Expected: child item base = condition value of parent item -> child item value = 10,000.00 x 7.5% = 750.00 USD

The pricing formula interface now exposes access to the parent item and root item from within a child item formula execution. Custom formulas can:

Navigate to the parent item or root item from the current item context
Read item-level data of the parent item
Use parent condition values as the base for child item calculations

More information will be published with the November release in the Extension Guide (Pre-Production).

Pricing service – Application Filter and Language Filter on Condition Type GET Endpoint

The GET endpoint for condition types has been enhanced with an optional application query parameter and a new $select=names parameter to retrieve all language-dependent descriptions.

Application Filter Parameter

The endpoint now accepts the optional query parameter application, enabling callers to retrieve a condition type scoped to a specific application:

GET /api/v1/customizing/conditiontypes/{conditionTypeId}?application={application}

– When application is provided, the condition type is returned for that specific application

– When application is omitted, it defaults to the service's configured application context, for example V (Sales)

All Language Descriptions ($select=names)

A new parameter $select=names has been introduced. When passed, the response includes an additional names array containing descriptions in all available languages.

GET /api/v1/customizing/conditiontypes/{conditionTypeId}?$select=names

An optional parameter $filter can be combined with $select=names to restrict which language variants are included in the names array. If no $filter is passed, all available language descriptions are returned.

Supported syntax: $filter=language IN (‘en','de','fr')

GET /api/v1/customizing/conditiontypes/{conditionTypeId}?$select=names&$filter=language IN (‘en','de','fr')

More information will be published with the November release in the API Definition and the Development Guide (Pre-Production).

Pricing service – Application Filter and Language Filter on Access Sequence GET Endpoint

The GET endpoint for access sequences has been enhanced with an optional application query parameter and a new $select=names parameter to retrieve all language-dependent descriptions.

Application Filter Parameter

The endpoint now accepts the optional query parameter application, enabling callers to retrieve an access sequence scoped to a specific application.

GET /api/v1/customizing/accesssequences/{accessSequenceId}?application={application}

– When application is provided, the access sequence is returned for that specific application

– When application is omitted, it defaults to the service's configured application context, for example V (Sales)

All Language Descriptions ($select=names)

A new parameter $select=names has been introduced. When passed, the response includes an additional names array containing descriptions in all available languages.

GET /api/v1/customizing/accesssequences/{accessSequenceId}?$select=names

An optional parameter $filter can be combined with $select=names to restrict which language variants are included in the names array. If no $filter is passed, all available language descriptions are returned.

Supported syntax: $filter=language IN (‘en','de','fr')

GET /api/v1/customizing/accesssequences/{accessSequenceId}?$select=names&$filter=language IN (‘en','de','fr')

More information will be published with the November release in the API Definition and the Development Guide (Pre-Production).

Variant Configuration service – New AVC-Aligned Mode (General Availability)

The AVC-Aligned Mode is now available to all customers. Building on the beta version released in 2608, this release significantly extends the supported AVC syntax and closes key behavioral gaps to SAP S/4HANA for advanced variant configuration (AVC).

New syntax functions (2608 + 2611 combined):

Numeric: round, nroot, log2, mod
String: length, substring, prefix, suffix, to_string, to_int, to_float
EXIT / EXIT IF for explicit conditional procedure termination

Behavioral alignment with AVC:

Set semantics for multi-valued characteristics
Automatic inferences in constraints (INFERENCES section no longer required)
Symbolic value exclusion via inequality (<>)
Negated table inferences (NOT TABLE / FALSE IF TABLE)
Sticky static defaults: CT04 defaults always restored when no value is assigned
Negative values allowed flag aligned with AVC
Preconditions for values of multi-valued restrictable characteristics
Procedure termination aligned with AVC (non-terminating on unassigned value)
Processing of all dependency types: constraints, procedures, selection conditions, and preconditions

Compilation visibility:

Compilation errors for unsupported syntax displayed in KB response and at configuration session creation, now persisted in the database
Per-dependency compilation status in GET /knowledgebases/{kbId}?$select=dependencies

More information will be published with the November release in the AVC-Aligned Mode – Customer Guide (Pre-Production).

Variant Configuration service – Configuration Engine Trace – Enhanced Header Information

Downloaded engine trace files now include a structured preamble with the HTTP request context. This enhancement provides:

Configuration ID
Correlation ID
Request URL
KBID (Knowledge Base ID)
AVC-Forwarding flag
The characteristic value changes (set/delete) applied in the request

This makes trace files self-contained for support analysis without needing to correlate them against application logs. When troubleshooting configuration issues, support teams can now immediately understand the context of a trace file without requiring additional information from the customer.

More information will be published with the November release in the API Definition and the Development Guide (Pre-Production).

Administration – Load Changed Variant Tables Only

The data replication will load only the changed variant tables on updates to knowledge bases when SAP Note 3754609 is applied to the source system. This will reduce the time a knowledge base is locked during the update process.

Previously, all variant tables were reloaded during knowledge base updates, even if only a subset had changed. This could result in extended lock times, particularly for knowledge bases with many large variant tables.

With this enhancement, the replication process identifies which variant tables have been modified since the last replication and only transfers those tables. This optimization significantly reduces:

Knowledge base lock duration
Network traffic during replication
Overall replication time for incremental updates

Action: To benefit from this optimization, ensure that SAP Note 3754609 is applied to your source SAP S/4HANA- or SAP ERP system when using classical knowledge-base generation.

More information will be published in the Administration Guide (Pre-Production) with the November release.

Administration – Browser Title Added to Administrative UI Pages

A browser title has been added to each page of the administrative UI. This helps you identifying where you are from the browser tab title.

When working with multiple browser tabs or windows open to different pages of the administration UI, it was previously difficult to identify which tab contained which page without switching to it. The browser tabs all displayed the same generic title.

With this enhancement, each page now sets a descriptive browser title that reflects the current location within the administration UI. This improves usability when:

Working with multiple administration UI tabs simultaneously
Switching between browser windows
Using browser history to navigate back to specific pages

More information will be published in the Administration Guide (Pre-Production) with the November release.

Administration – Table Settings Enabled Including Persistency

The settings of a table like visible columns and width are enabled. The information is also persisted and re-used on the next logon.

Previously, any customizations made to table displays in the administration UI – such as showing or hiding columns, adjusting column widths, or changing column order – were lost when you navigated away from the page or logged out. Users had to repeatedly configure their preferred table views.

With this enhancement, your table settings are automatically saved and restored:

Column visibility preferences are remembered
Column width adjustments are persisted
Column order customizations are retained
Settings are restored automatically on your next logon

This provides a more personalized and efficient user experience, especially for administrators who regularly work with specific subsets of data and prefer customized table layouts.

Table Personalization

Column Filter

More information will be published in the Administration Guide (Pre-Production) with the November release.

With that, you have a good overview of what innovations are planned for the November release. Please check the updated roadmap and release notes after the release date to see which of these features were delivered as planned.

Source link