We’ve Dynamics 365. In Dynamics 365 there are many business apps, like Sales, Operations, Flow, Office, Field Services. The Quote to Order processes touches many application. If we take a typical Quote-to-Cash process it probably starts in the Sales app and then moves in the Operations app and maybe finally moves into the Field Services App.
One data model and configuration for multiple Business Apps (Quote-to-Order and Quote-to-Cash)
e-Con CPQ is of course connected to all of those different Business Apps in your Dynamics 365 App Suite. The challenge is then, how we could use our e-Con CPQ in an efficient and easy way in all the apps involved in your quote to cash process. For that we’ve been introducing our so called ‘context driven’ concept. A second pillar here is also our meta data based integration. Meta data means that from these business apps we expose the data model to our CPQ studio – in other words our e-Con Studio is aware of all the data entities of these different apps. The new functionality, so called contexts are introduced for those different business apps – each business app can be associated to a so called context. Context can be designed and set up flexible so I can introduce in my e-Con CPQ the context Sales which is of course linked to our Sales App, I could also introduce the context operations which is connect to Operations, etc. When I use e-Con CPQ throughout the Quote-to-Order while configuring custom products or services it works as you can see in this movie:
Context Driven Modeling Approach
When I set up the e-Con configuration templates in the e-Con Studio, first thing I need to do is the map my e-Con CPQ template on entities relevant for e.g. sales (a typical quote to cash process starts in Sales), typically Quote and Quote detail entities. However next step in the quote to cash process is to submit my quote to an order. Orders typically lives in Dynamics 365 for Operations app and has of course their own entities in operations for storing the data… The trick now is that within the Studio I’ve the possibility to switch the context from Sales to Operations, allowing me to do a second mapping on my CPQ template with the for Operations relevant entities, like the Sales Order, Sales Order Line, Products, Bill of Materials and Routing. And of course I can do this for more contexts, I could introduce to Project contexts, maybe my business is more project oriented meaning moving from sales to operations the quote needs to land in a Project, with budget lines. So one e-Con CPQ template can literally be mapped on different Business Apps, allowing me to have one single e-Con configuration template mapped on multiple Dynamics 365 applications.
e-Con CPQ is the one and only CPQ tool allowing and following this metadata and context driven concept. In general it delivers you optimal speed, flexibility and low costs of maintenance.