.png)
Sales System Architecture
Global System Architecture
Valio Sales Systeme rchitecture is relying in 4 main systems
SAP C4C as the main company CRM
Zilliant Price Manager and Price IQ, for holding all valio Pricing Strategy and rules
SAP S/4 Hana : as the main ERP of the Company
Zilliant CPQ : as the main deals and agreements manager
The diagram below display a high level architecture and interaction betweend the diffrent components, the box in yellow highlights the technical coverage of the CPQ project scope.
Although SAP C4C, is planned to be implemented as the main CPQ in Valio, the integration with CPQ is not in the scope of the current project. However CRM design solution is taken into consideration for the solution
Any additional SAP integration between SAP and Price Manager resulting from the new architectural setup is not in the scope of the CPQ project
System Interface :
In this project, there are only two main interfaces to be defined to ensure a the expected seamless data flow across the sales Proces process.
Integration between CPQ and CRM : These interfaces ensure synchronisation between the SAP C4C and Zilliant CPQ. It enables sales users to initiate the quoting process directly from CRM opportunities or accounts, leveraging existing customer and opportunity data. Key objects typically exchanged include Accounts, Contacts, Opportunities, and Quotes. This integration facilitates a unified sales experience, reduces manual data entry, and ensures consistency across systems.
Integration between PM and CPQ : These integrations ensure the alignment of product, pricing, and any sales related data between Zilliant Price Manager system and the CPQ. PM acts as the master system for pricing logic and product attributes. Through this interface, relevant data such as product master, pricing rules are transmitted to CPQ. This ensures that the sales team always uses up-to-date and approved pricing logic within the CPQ engine, and it supports consistent and controlled pricing governance.
Both integrations are typically implemented through APIs or middleware platforms and require coordination of data models, field mapping, update frequency, and error handling mechanisms.
The implementation of CRM <--> CPQ interface is not in the current scope of the solution
CPQ ↔︎ CRM Interfaces
CRM to CPQ
Customer Integration: This integration focuses on enhancing customer data synchronization.
Opportunity Integration: This aims to streamline the flow of opportunity-related information.
Contact Integration: This facilitates the seamless sharing of contact details.
CPQ to CRM
Prospect Integration: This integration is designed to improve the management of prospect information.
PM ↔︎ CPQ Interfaces
Below is the list of objects that should be interfaced between CPQ and Price Manager
PM to CPQ
Product: product information will come from the Product Master Data table in PM and will be stored in the product catalog
Product Group: Product Group data must be synchronised between the table in PM and the catalog to create products. In addition, information related to Head Office and Discount will be stored in a Data Lookup.
Customer: Customer information will be retrieved from the Customer Master Data table and stored in the Account object. Note that only Parent Account information will be stored.
Pricing: Prices are processed and manipulated in Price Manager. They are called up when the user creates a quote, and the information from the Price Manager tables will then be synchronised with the appropriate fields in the quote line.
CPQ to PM
Agreement: Currently the only outgoing interface in the system, it will send agreement data to the corresponding table in Price Manager.
As Of The List of field for the Mapping of some of thes object are note festablished. please refer to the D-MIMO TDS.
Related Technical Document : Data Mapping In Mapping Out
The Data Mapping In Mapping out is structured as follow :