Financial Management Blogs by SAP
Get financial management insights from blog posts by SAP experts. Find and share tips on how to increase efficiency, reduce risk, and optimize working capital.
cancel
Showing results for 
Search instead for 
Did you mean: 
LukaPilipovic
Product and Topic Expert
Product and Topic Expert
1,861

It’s been a while since Quote2.0 is available for customers but we are still hearing questions here and there. What is the difference? Is Quote 2.0 that good? Is it ready? What is new, what is different?


Let's reflect on couple of most important aspects of SAP CPQ



Performance


Quote 2.0 engine was developed as a part of the initiative to make SAP CPQ the state-of-the-art software that allows users to create large quotes more quickly than in Quote 1.0.



New quoting engine can without any doubt support thousands of line items per quote. Working with not so huge quotes is also more convenient as we adopted new approach on how standard events are to be leveraged in implementations.

 

Event driven mindset. Optimized and reinvented


Experience from over a decade of implementations with previous quote engine taught us that having full power of customization via scripting does not always lead to optimal results. With Quote 2.0 we rely on having scripting being executed on discrete events rather than on every user click. Here are few key technical points:





  • Events and execution pipeline cleaned and simplified





             Quote 1.0 events                                             Quote 2.0 events




 


  • Quote 2.0 is stateless while Quote 1.0 works with entire quote being loaded into user memory.




  • Quote 2.0 works with deltas which significantly decreases network traffic and as quote is not in user memory but actually every change gets sent to cloud we are entering new era of quoting.




  • Quote 2.0 works on field level and not on item level as Quote1.0 which contributes to performance gains




  • As consequence of described above multiple users can work on same quote in parallel.




  • We really wanted to start with only important functionalities to maximize our ability to move fast. As a result of that some unused features have been obsoleted and some got completely redesigned. Full list of Quote 1.0 vs Quote 2.0 features 





 

Powerful. Designed for future integrations


We understand modern enterprise architecture. Therefore we heavily invest into building new robust API endpoints. In Quote 2.0 we released brand new endpoint to get full list of quotes based on specific criteria.



GET /api/v1/quotes


Please take some time to get familiar with REST APIs specific to quote 2.0

 

Business partners


In Quote 2.0 we adopted Business Partners concept from S/4HANA as default functionality for managing customers and other involved parties. Admins can predefine business partner but they also can be added during quoting process. In CPQ 2305 release highlights | SAP Blogs I already described newly introduced mass import function.



Solution Design


The Solution Design feature enables users to organize items into sections and subsections in a separate tab on quotes. It brings additional view of the items that are already in the quote. Calculations are upgraded to cover sections as well. This feature is supported only with SAP CPQ Quote 2.0 engine.


Solution Design feature is useful when sales representatives work on large deals which consist of different logical areas like multiple data centers or furnishing multiple buildings.





Quote teams


While working on large quotes quite often different teams are engaged. Therefore only in Quote 2.0 it is possible to define solution teams that can be assigned only to a section of solution design. Additionally CPQ admins can predefine administrator teams for users that can create, edit and delete sections within every quote.


Still haven’t found answers to your questions? Please check out frequently asked questions section in SAP Help portal.


Share in comments yout impressions and experience with SAP CPQ Quote 2.0 engine!

1 Comment