Some companies wrongly assume that the native integration between ERP and CPQ means that CPQ replicates all ERP configuration, pricing, and quoting functionality. Few companies realize how much functionality that truly is. Especially when you consider cross functional capabilities like available to promise, costing, and industry solutions. And advanced functionality in configuration and pricing.
The core set of CPQ configuration, pricing, and quoting functionality meets the main needs of most companies who want to run CPQ. So, SAP decided to support that functionality first in CPQ and its native ERP integration. For now, everything beyond that is custom functionality and/or integration. SAP has a product roadmap for CPQ and its ERP integration that is expected to continually introduce new capabilities over time. But do not expect that CPQ will ever support everything that ERP can do.
CPQ is not meant to replace ERP, and many specialized supply chain functions will continue to take place in ERP only. Think of CPQ and ERP as working together with each system playing to its strengths. In general, use CPQ to do “the selling” and ERP to do “the fulfilling”. And see my blog on The Complete Offer Process for why to do it this way.
In some cases, the interaction between CPQ and ERP is far more complex than the preceding generality. Companies sometimes need these applications to work in concert with ERP info needed in CPQ and vice versa (beyond what is natively provided or advertised). In such cases, proper solutioning (and awareness of the SAP product roadmap) are the keys to your success.
In the rest of this blog, I will touch on various topics that often come up in our CPQ implementations. Some of these require routine enhancements (where SAP provides documented guidance) while others require customizations that eLogic has developed. The detailed information in this blog sets eLogic apart, so we ask that you register below to gain access to the full blog.
Request Access: