Receive a renewal quote from Oracle Subscription Management

Redwood Platform

Seamlessly transform potential subscriptions in Oracle Subscription Management into renewal quotes in Oracle Configure, Price, Quote (CPQ).

Use the new predefined Oracle OSS message definition Oracle-1-0-A2A-OSS-Renewal-Quote-In to receive renewal subscriptions from Oracle Subscription Management and seamlessly transform them into the appropriate payload format required by Oracle CPQ for create quotes.

You can now send status update notifications about the processing of the Oracle-1-0-A2A-OSS-Renewal-Quote-In message automatically to the initiating user in OSS by leveraging the outbound application response message, Oracle-1-0-A2A-OSS-Application-Response-Out.

Here are some of the benefits of this feature:

• Seamless Transformation: Convert eligible subscription renewals into CPQ quotes, accelerating the renewal process, simplifying cross-application workflows, and reducing integration effort.
• Automated Notifications: Success and error notifications are automatically handled and communicated back to Oracle Subscription Management so that the users are kept informed in real-time.

Steps to enable and configure

After you have enabled the feature Simplify Configuration and Processing for B2B Messaging, you'll need to perform the following high-level tasks to complete the setup:

1. Select Connections from the in-app navigation bar.
   • Select the Providers tab and search for Oracle OSS to see the service provider details.

Oracle OSS provider

1. • Select the Delivery Methods tab to access the predefined delivery method ORA_OSS_REST_WebService.

Oracle OSS delivery method

1. • Select the Connections tab and filter by the provider Oracle OSS to see all seeded connections.

Oracle OSS connections

2. Select Documents from the in-app navigation bar.
   • Select the B2B Message Processing Result - Outbound document and set the Enabled field to Yes. You don’t need to assign a connection to this outbound document.

B2B message processing result - outbound

1. • Filter by Inbound documents. Select the Renewal Quote - Inbound document and set the Enabled field to Yes.

Renewal quote - inbound

3. You can also search for Oracle OSS message definitions by provider in B2B Message Definitions
   • Select Definitions from the in-app navigation bar.
   • Select Oracle OSS in the Provider filter.

Oracle OSS message definitions

4. You can include additional attributes in your messages:
   • Select Definitions from the in-app navigation bar.
   • Select the predefined message definition you intend to customize, that is, Oracle-1-0-A2A-OSS-Renewal-Quote-In or Oracle-1-0-A2A-OSS-Application-Response-Out and select Export Transformation Package. The transformation package has two folders, mappingFile and mappingFunctionFile.
   • Edit the mapping file to include the additional attributes.
   • Edit the mapping function file to edit or create business functions used by the mapping file.
   • Select the predefined message definition you customized the mappings for, such as Oracle-1-0-A2A-OSS-Renewal-Quote-In, and select Duplicate. Enter a name and upload your modified file. 

Duplicate message definition

5. You can replace the predefined message definition Oracle-1-0-A2A-OSS-Renewal-Quote-In or Oracle-1-0-A2A-OSS-Application-Response-Out with the newly duplicated one.
   • Select Connections from the in-app navigation bar.
   • Select the Connections tab and filter by the provider Oracle OSS to see the connections for all Oracle OSS messages.
   • Select the predefined ORA_OSS_Oracle-1-0-A2A-Renewal-Quote-In connection. The duplicated message will appear in the Message Definition drop-down list.

Replace message definition

6. Transactions for both Renewal Quote-Inbound and B2B Message Processing Result - Outbound can be reviewed using the Messaging History page and by selecting the applicable document.
   • Select History from the in-app navigation bar.
   • Filter the messages by Document, Provider, and Status Date.

Messaging history

Tips and considerations

• The Application Provider Type which defines the Oracle OSS provider is any internal Oracle application that you exchange messages with.
• Since the OSS delivery method (ORA_OSS_REST_WebService) facilitates communication between two Oracle applications, REST service details are not displayed on the page.
• Transformation mode displays options to specify whether the document will be transformed using an XSLT style sheet or a mapping file. For Oracle-1-0-A2A-OSS-Renewal-Quote-In and Oracle-1-0-A2A-OSS-Application-Response-Out messages, the transformation is performed using JSON instead of XSLT, so the transformation mode is set to mapping file.
• The mapping file contains the attribute mappings and may utilize functions defined in the JavaScript file when necessary.
• The mapping function file contains all the functions used by the mapping file. It encapsulates the business logic necessary to perform the mapping operations.
• Even if only one file is modified, both the mapping file and the mapping function file must be uploaded when duplicating a message.
• There's no need to configure Customer B2B Properties for the Oracle-1-0-A2A-OSS-Renewal-Quote-In message.
• The B2B Message Processing Result - Outbound document is automatically generated in response to the processing of the Renewal Quote-Inbound (Oracle-1-0-A2A-OSS-Renewal-Quote-In) document. There's no need to assign connections to it.
• All error information from the application will be available in the payload with the specific error message being extracted and displayed separately.
• The event correlation ID sent by Oracle OSS in the payload header will be propagated to Oracle CPQ.
• Documents associated with either Oracle-1-0-A2A-OSS-Renewal-Quote-In or Oracle-1-0-A2A-OSS-Application-Response-Out messages can't be reprocessed or resubmitted from the History page.

Access requirements

If you're using custom job roles, then you need to add privileges identified as new in this update as well as validate that you have the previously delivered privileges listed.

Privilege status	Privilege name and code
Existing	Invoke Collaboration Message Inbound Service CMK_INVOKE_INBOUND_COLLAB_DOC_SERVICE_PRIV