top of page
  • Lawrence Matusek

My Favorite News in CPQ Updates: SAP CPQ 2102

CPQ 2102 Update

There is a lot of news in this quarterly update from SAP. Here are a few selected highlights:


A 2102 prelease was published in November. Prereleases inform customers of specific changes that may affect existing enhancements and require more time to test and resolve than the typical two-week period between sandbox and production updates. Key changes in the 2102 prelease are outlined below.

The names of database tables where pricing attributes and reference characteristics are retained will be changed in the 2102 release. If these tables are referenced in any custom Iron Python scripts, it is necessary to replace the old names with the new names in order for the scripts to remain operational.

GET Quotes API used for Quote 2.0

Custom Fields Format Change in GET Quotes API (scripts need to be updated)

The GET /api/v1/quotes/{quoteId} endpoint will retrieve the value code of custom fields with the type attribute, not their display value.

The End of the Road for Products 1.0

There will no longer be a Products (1.0) and Products 2.0 link under Product Catalog setup. Only the Products 2.0 functionality will be available, and it will be relabeled as ‘Products’. Don’t be confused:

Products 1.0 is labeled ‘Products’ in CPQ 2011

Products 1.0 is no longer available in CPQ 2102

Products 2.0 will be labeled ‘Products’ in CPQ 2102

There will no longer be a Products 2.0 link in CPQ 2102 (i.e., just use ‘Products’)

During the recent Power Hour, SAP explained that Products 1.0 can still be reactivated by SAP Support until the 2105 release in case some important, overlooked functionality of Products 1.0 has been lost with Products 2.0.

In general, I feel that the user experience in Products 2.0 is far superior to that of Products 1.0. The look, feel, and navigation options are much better. The Configuration Layout is drag and drop, and that really increases productivity. That said, there are few obscure Products 1.0 features that we use that are not yet available in Products 2.0. We will bring these to SAP’s attention in the hope that they can be included in the 2105 release.

Fresh New Look for Guided Selling Setup

In 2102, Guided Selling setup has a similar look and feel to Products 2.0 setup. In 2011, Guided Selling setup has a similar look and feel to Products 1.0 setup. This is a nice improvement (see preceding paragraph).

A powerful improvement is that the Guided Selling logic application parameter has been moved from General > Application Parameters to Product Catalog > Guided Selling and renamed to ‘Item Filter Criteria’. This provides more flexibility in creating new guided selling processes since each process can now have different item filtering logic.

Variant Configuration and Pricing Integration

These updates are always important to eLogic since most of our customers use this robust capability. You can now create mappings for pricing procedures from SAP ERP in CPQ setup. It is no longer necessary to create these mappings with Iron Python scripting or IFlows. These mappings are used when an order is placed from SAP CPQ to SAP ERP. In other words, this is now a data-driven task versus development.

Performance has also been improved for CPQ Products that are synchronized with ERP Materials by reducing the number of pricing requests sent by CPQ. Pricing is only requested when CPQ attributes that are synched from ERP characteristics (or otherwise used in pricing) are changed in CPQ configurations. This opens the door to enriching CPQ Products with certain resident CPQ attributes and rules. eLogic has researched which hybrid scenarios work (from a design time synchronization and runtime calculation perspective). Do not assume that all combinations that you can create will work or stay working after VC model updates.

Also noteworthy is that the Simple Product Administration API now supports the Variant Pricing mechanism, which is available for non-configurable products. In addition, the General Attribute Mappings setup has been improved for better usability.

Involved Parties

I bet we all want to be involved in parties these days, but I don’t think that it is what SAP has in mind for 2102 ;) The big news here is with integration scenarios to the SAP Commerce Cloud and Salesforce CRM that use the involved parties concept for recording business relationships on the quote and the relations to the transactions made in Quote 2.0.

Keyboard Support

All user interface elements for CPQ users can now be accessed via keystrokes. This makes it easier for users of assistive technologies to read and operate SAP CPQ. Rick Servello (an eLogician) will also be happy; he claims that using a mouse slows him down ;)

Other Noteworthy Updates

Here are a few miscellaneous updates that will make your life a little easier or a little more interesting.

You can integrate multiple SAP CPQ tenants with one SAP Cloud for Customer tenant.

Proposal links can be included in emails sent from SAP CPQ using the Quote 2.0 engine. This allows a customer to open the quote in CPQ (but you should restrict their permissions, of course).

User Certificates mapped to individual users then authenticated via API will enable powerful new integration designs.

Default User Settings for Self-Registered Users have been redesigned and improved.

Quotes API has been improved and extended to support more scenarios.

The Configuration Tree View responsive template is now available in Setup > UI Design under the Configurator page.

All these updates and more are described in detail in the SAP_CPQ_2102_Whats_New PDF document on the SAP CPQ main help page.

Each CPQ release has improved the experience and usability of SAP CPQ. We are looking forward to SAP completing the Quote 2.0 roadmap so there are no remaining gaps that preclude its use in our customer implementations. We also hope that the stateless pricing services become available later this year. These will be game changers.

bottom of page