Generate Oracle CPQ Renewal Quotes from Subscription Renewals
This feature enables Subscription Management renewal processing to initiate renewal quote creation in Oracle CPQ. After the Subscription Auto Renewal ESS job creates renewal drafts, the renewal flow can evaluate renewal insights, create an opportunity when required, prepare a subscription renewal payload, send it to Business Messaging Framework (BMF) for mapping/transformation, and invoke CPQ quote creation.
The flow also introduces a callback mechanism so BMF and CPQ can report success or failure back to Subscription Management through "subscriptionCallbackEvents". These responses can be tracked in a Renewal Navigator with step-level status and retry options.
Benefits
| Benefit | Description |
|---|---|
| Faster renewal quote creation | Reduces manual handoff between Subscription Management and CPQ. |
| Better renewal orchestration | Supports Zero Touch, Low Touch, High Touch, and Manual renewal paths. |
| Improved visibility | Callback events show where the renewal quote process succeeded or failed. |
| Actionable recovery | Users can manually retry failed steps from Renewal Navigator. |
| Richer CPQ context | Payload can include subscription header, products, charges, adjustments, covered levels, and renewal insights. |
| Scalable integration | Uses direct JSON payload for normal cases and UCM document reference for large subscriptions. |
Steps to enable and configure
- Profile option Enable Integration Between CPQ and Subscription Management Cloud must be set to Y/Yes to use the Business Messaging Framework used in this feature and create a renewal quote for the subscription that is renewed.
- Profile option Integration Between Opportunity and Subscription Management Cloud Enabled must be set to Y/Yes to send the renewal subscription to be created as a renewal opportunity.
Tips and considerations
Tips and Considerations
| Area | Consideration |
|---|---|
| Payload approach | Use full synchronous payload to BMF as the primary option. If payload exceeds the supported limit, upload payload to UCM and send the document ID. |
| Payload size | Current noted limit is 20 MB, with BMF expected to support up to 100 MB. Large subscriptions need fallback handling. |
| Payload content | Include child entities such as products, charges, charge adjustments, covered levels, and insights. Covered levels may need profile-option control. |
| Attribute optimization | Until BMF confirms exactly which attributes are used in mappings, use configuration/profile options to control which entities are sent. |
| Retry handling | Implement retry at Renewal ESS/Renewal Agent, BMF callback, and CPQ quote creation stages. Failed steps should surface for manual retry. |
| Renewal Navigator | Needed to show current status, state transitions, callback history, errors, and retry actions. |
| Callback API | Common REST callback API should support BMF and CPQ responses, including success, warning, and error statuses. |
| Error model | Store callback events and callback event errors separately, including functional and technical errors. |
| Quote/draft sync | Clarify behavior when a renewal draft is deleted or changed after a CPQ quote has already been created. |
| Insights granularity | Product-line insights are planned; bundle-level or asset-level insight behavior needs clear use cases and design decisions. |