Native quoting integration with Oracle CPQ
Oracle Commerce no longer requires Oracle Integration Cloud(OIC) to be implemented when using our standard quoting flows with Oracle CPQ. Merchants can natively map additional order/commerce item-level properties to CPQ transaction/transaction line-level properties. This feature is only available for our Commerce on CPQ customers.
Below are the key functions supported by this update:
- Request for Quote
- Generate Proposal
- Quote-to-Order Sync during Checkout
- Order Submission through CPQ
Add Self-Service quoting easily to an existing Oracle CPQ integration, and reduce the ownership cost for integrations when using Oracle Commerce and Oracle CPQ together.
Steps to Enable
To activate Native Quoting and Order Submission features:
- Enable the features:
API: PUT /ccadmin/v1/merchant/selfServiceConfiguration
Payload:
{
"requestQuoteToCPQ": true,
"orderSubmitToCPQ": true,
"cancelOrderOnFailure": true
}
- To configure additional property mappings between OCC and CPQ:
API: PUT /ccadmin/v1/merchant/selfServiceConfiguration
Payload:
{
"orderToTransactionMapping": {
"<occOrderAttr1": "<cpqTransactionAttr1>"
},
"commerceItemToTransactionLineMapping": {
"<occCommerceItemAttr1>": "<cpqTransactionLineAttr1>"
},
"shippingMethodsMapping": {
"<occShippingMethod1Id>": {
"_shipping_shippingServiceLevel_l": "<fusionShipMethodServiceLevelCode>",
"_shipping_shipModeOfTransport_l": "<fusionShipMethodModeOfTransport>",
"_shipping_shipCarrierName_l": "<fusionShipMethodCarrierName>"
}
}
}
e.g. Mapping Business Unit and Shipping Method
{
"orderToTransactionMapping": {
"x_businessUnit_Id": "businessUnitId_t"
},
"shippingMethodsMapping": {
"standardShippingMethod": {
"_shipping_shippingServiceLevel_l": "EXP",
"_shipping_shipModeOfTransport_l": "AIR",
"_shipping_shipCarrierName_l": "DHL"
}
}
}
Tips And Considerations
- This feature is only available for our Commerce on CPQ customers.
- For deeper customizations or orchestrations, merchants should use OIC to achieve the desired functionality.
- Field mappings assume the same data type for the mapped field in CPQ.
- Mapping Address, Payment and shopper input properties are out of scope.
- Only Invoice type payments are currently supported.
- Below are a few key mapping configured in the system by default. Please raise an SR with Oracle support to request for modifications to the mapping.
- '_start_step' : 'draftOrder'
- '_price_book_var_name' : '_default_price_book'
There are few other configurations available on Self Service CPQ settings on Administration Console->Settings->Oracle Integrations. e.g. Order Start Transaction Action is set to order_start. Update the settings to use a custom action for Order Start Transaction Action.