Update 23D

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Module	Feature	Notes
29 SEP 2023			Created initial document.

Overview

Oracle Configure, Price, and Quote (CPQ) enables companies to streamline the entire opportunity-to-quote to-order process, including product selection, configuration, pricing, quoting, ordering, and approval workflows. Oracle CPQ provides a flexible, scalable, enterprise-ready solution ideal for companies of all sizes that sell products and services across direct, indirect, and e-commerce sales channels.

This guide outlines the information you need to know about new or improved functionality in Oracle CPQ 23D.

Security and New Features

We would like to remind you that if your system has modified security structures, you may need to advise your security administrator of new features you would like to implement

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at cpqcloud_documentation_us_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Feature Summary

Configure, Price, Quote

Pricing

In Oracle CPQ 23C and 23D, CPQ introduces a number of new business objects to allow you to price your products in a more flexible way to support subscriptions and consumption-based pricing.

The new pricing business objects include the following:

• Charges (Oracle CPQ 23C)
• Charge Attributes (Oracle CPQ 23C)
• Lookups (Oracle CPQ 23C)
• Price Model Items (Oracle CPQ 23D)
• Rate Plans (Oracle CPQ 23D)
• Rate Cards (Oracle CPQ 23D)
• Rate Card Templates (Oracle CPQ 23D)
• Charge Definitions (Oracle CPQ 23D)

Starting with Oracle CPQ 23C, Charges provide a means for customers to define multiple prices for a single product in addition to the legacy Product Prices that continue to display on quote lines and in the configuration BOM item panel. In Oracle CPQ 23D we’ve added Rate Plans, Rate Cards, Charge Definitions, and automated integration to further support subscription and consumption pricing with a complete end-to-end quote pricing and usage rating solution in combination with Oracle Subscription Management and Fusion Pricing.

While most of the new business objects in Oracle CPQ 23D are additive to our previous features, the introduction of the Price Model Item object modifies the behavior of several REST APIs and our pricing bulk upload behavior. For more information, refer to Pricing Setup REST APIs and Modifications to Known Functionality. The new Price Model Item object breaks out the product information (part and/or BOM Item) from the child prices for those products.

The following roles are referenced for pricing tasks within this document:

• Pricing Administrator refers to the Oracle CPQ user that is accessing CPQ Pricing Portal.
• Product Manager refers to an Oracle CX Sales user that is accessing the CPQ Product Workbench (formerly known as Product Launch).

The following Pricing features are available in Oracle CPQ 23D.

Rate Plan Business Object in CPQ Pricing

Oracle CPQ 23D provides support for the Rate Plan business object to define groups of charges that can be optionally applied to the pricing for a subscription product (e.g. Monthly vs. Quarterly Subscription Plan). Rate Plans provide an alternative to non-Rate Plan charges and product prices. Rate Plans can be defined using either the Pricing Portal or Product Workbench. A Rate Plan is a collection of charges for a product that is added as Price Model Items within a CPQ Pricing Engine Price Model. A Price Model Item can have zero to many Rate Plans, or zero to one product price and zero to many non-Rate Plan stand-alone charges. A Rate Plan can also have zero to one product price and zero to many charges. If a product has more than one Rate Plan, one of the Rate Plans is designated as the default Rate Plan.

Oracle CPQ 23D also provides Pricing Engine UI updates to support the Rate Plan object and to enhance navigation and list pages. These updates improve usability of the pricing UIs, display of multi-column tables, and translations. Similar to non-Rate Plan stand-alone charges, the Rate Plans will reside in the Pricing Data section of the applicable Price Model. The new default structured view for the Price Model Pricing Data provides easy access to manage product Price Model Items. Pricing administrators can perform the following tasks within the structured view:

• Click on the table view icon to view.
• Enter search criteria to filter the products for which prices have been defined.
• Manage columns and add new product Price Model Items.
• Edit or delete existing Price Model Items.
• Quickly access related product prices, charges, or Rate Plans.

When a pricing administrator edits a new subscription type product, they can add a product price, add charges (i.e. non-Rate Plan stand-alone charges), or add a Rate Plan.

After creating a Rate Plan, pricing administrators can perform the following:

• Add Rate Plans, Expand or Collapse All Rate Plans.
• Reorder Rate Plans to define the default Plan to apply (the first) and the sequence in which the Plans will display in a drop-down menu.
• Edit or Delete existing product prices or charges.
• Edit Rate Plan Details, Add a Product Price or Add Charges to an existing Rate Plan, or Delete Rate Plan.

Rate Plans are also available in the Product Workbench (aka Product Launch) for Oracle CX Sales integrated customers. Product managers can now define, select, and apply Rate Plans for subscription-based products that are linked to CPQ Pricing Engine Price Models.

When pricing is invoked, CPQ Pricing will calculate prices using the requested Rate Plan. When no Rate Plan is requested by a sales user, pricing applies the default Rate Plan if defined, or any stand-alone non-Rate Plan charges and product prices.

The pricing output will include the applied Rate Plan and other available Rate Plans, if applicable.

Rate Plans can be used to group charges, applied to subscription-based products, and integrated with sales, pricing, order management, and subscription applications.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Rate Plans are only available for subscription type products (i.e. Parts with Sales Product Type = SUBSCRIPTION).

• When Rate Plans are used for a product you cannot have non-Rate Plan charges or product prices. The use of a Rate Plan for a product is mutually exclusive to non-Rate Plan pricing.

Rate Card Business Object in CPQ Pricing

Oracle CPQ 23D introduces Pricing Engine Rate Cards to support subscription-based pricing for industries such as communications, utilities, and cloud services. These industries require invoicing or rating calculations based on multi-dimensional tables to capture complex Pricing Rules, such as for phone call or data storage usage. Pricing Engine supports this type of pricing through the creation of custom Rate Cards for determining the invoice amounts to be billed on a periodic basis.

Rate Card Templates are provided to specify the custom fields or columns that are included in a Rate Card (e.g. Usage From, Usage To, Rate). The Rate Card is then used to define the necessary rows and values for the pricing table matrix.

The process for defining a Rate Card pricing involves four steps:

1. Define the Lookups and their valid values for any menu type attributes you will use in your Rate Cards.

2. Create a Rate Card Template that defines the specific metadata or columns that will be used to define one or more Rate Cards (ex. region, call-to country) using Lookups to define the list of valid values.

3. Create a Rate Card using the Rate Card Template to define the specific column values and the resulting per unit prices for each combination of these values.

4. Associate the Rate Card with a usage charge for a product (Price Model Item).

The Rate Card Templates page lists available Rate Card Templates that can be used to define one or more Rate Cards. Pricing administrators can perform the following tasks from this page:

• Enter search criteria to filter Rate Card Templates.
• Add and delete Rate Card Templates.
• Quickly access existing Rate Card Templates and linked Rate Cards.

The Rate Card Template page shows the basic details and lists the columns that define the Rate Card. Pricing administrators can perform the following tasks from this page:

• Click Edit to access Rate Card Template details.
• Add, reorder, or delete Rate Card Template columns.
• View and access existing Rate Card Template columns.

The Rate Cards page lists available Rate Cards that can be applied to a usage-based charge. Pricing administrators can perform the following tasks from this page:

• Enter search criteria to filter Rate Card Templates.
• Add and delete Rate Card Templates.
• Quickly access existing Rate Card Templates and linked Rate Cards.

The Rate Card page shows the basic details and lists the number of Price Models in which this Rate Card is used. It also lists the rows and columns in the Rate Card that will be applied at rating-time to calculate the recurring invoice amounts. Pricing administrators can perform the following tasks from this page:

• Click Edit to access Rate Card details.
• Enter search criteria to filter Rate Card data.
• Manage Rate Card columns.
• Add, edit, or delete Rate Card data.

The new Rate Cards and associated Rate Card Templates are also supported in the Product Workbench for Oracle CX Sales product managers to define complex pricing for usage-based charges for a product. The Product Workbench UIs are aligned with Pricing Engine UIs so that both product managers and pricing managers have a very similar user experience.

CPQ pricing also writes the Rate Card data into the applicable quote line charge items. This information can be included in document outputs to assist sales users in pricing negotiations. The Rate Card data is also integrated to a subscription billing system and referenced in the downstream flow to an order management or fulfillment system.

Rate Cards templates and Rate Cards can be used to define complex usage-based pricing, and for rating of actual usage quantities (in Oracle Fusion Pricing).

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• In Oracle CPQ 23D Rate Cards are static objects that do not calculate estimated usage prices but can be used for calculating usage rating invoice amounts based on actual consumption.

• In Oracle CPQ 23D Rate Cards can only be applied to charges with a price type of 'Usage'. When CPQ is integrated with Oracle Fusion Pricing, Rate Cards can only be applied to charges with a price type of 'Usage' and which are members of a Rate Plan.

• Rate Cards can only be applied to charges. Rate Cards are not available for product prices.

• Once created, Rate Cards and Rate Card Templates may be deleted if the Rate Card is not used to price any charges and the Rate Card Template is not used by any Rate Cards.

Combine Volume, Tier, and Static Pricing in the Same Price Model

Oracle CPQ 23D combines dynamic pricing with static pricing so all pricing types can be defined in the same Pricing Engine Price Model. Prior to Oracle CPQ 23D, CPQ supported dynamic pricing options at the Price Model level. A Price Model was designated as either a Tier Pricing, Volume Pricing, Advanced, or 'None' Dynamic Pricing type. Beginning in Oracle CPQ 23D, Tier and Volume types of Dynamic Pricing are defined at the Price Model Item level (i.e. a specific product) within any type of Price Model, to provide users additional flexibility and ease of administration. Upon upgrade all Price Models will support tier, volume and flat pricing on an item by item basis and will retain any tier or volume pricing that has been previously defined.

This enhancement simplifies administration and discoverability of pricing in the Pricing Engine. Dynamic Pricing types, such as Tier or Volume Pricing, have been moved from the parent Price Model level to the Price Model Item level. This allows pricing administrators and product managers to add multiple different Dynamic Pricing type items to the same Price Model. They can also change the Dynamic Pricing type for a data item without the need to create a new Price Model.

These Price Model improvements are also reflected in the Product Workbench for Oracle CX Sales integrated customers to allow product managers to define dynamic pricing for products.

Multiple Dynamic Pricing types can be defined and changed for a product within the same Price Model.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Dynamic Pricing using a BML script is still available at the Price Model level.

Effective Dating for Price Models, Charges and Rate Plans

Oracle CPQ 23D adds effective start and end dates to the Price Models, Rate Plans, and Charges. This allows effective dating such as for time-based promotions. If needed, customers can still use Pricing Rules to define the effective dates as well. Pricing administrators can use Price Model Start and End dates to set effective dates for all products or structures included in that Price Model.

Pricing administrators and product managers can use Rate Plan Start and End dates to set effective dates for all prices and charges included in that Rate Plan.

Pricing administrators and product managers can also use charge Start and End dates to set the effective dates for an individual charge.

Effective dates can be set for Price Models, Rate Plans, and charges.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Start and End Dates are not required in CPQ.

• When integrated with Oracle Fusion Pricing, null start dates in CPQ will be defaulted to January 1, 2000 in Fusion Pricing to satisfy the requirement for a start date.

Charge Definitions

Oracle CPQ 23D also introduces optional Charge Definitions that can be used to standardize charge categories. (e.g. Activation Fee, Call Usage, Data Usage, One-time Pricing, Recurring Pricing) and to define the valid combinations of price types and charge types. Charge Definitions are highly recommended for customers using charge pricing (vs. legacy product pricing) to simplify the setup of prices. Charge Definitions are required when CPQ pricing is integrated with Oracle Fusion Pricing.

The Charge Definitions page lists available Charge Definitions. Pricing administrators can perform the following tasks from this page:

• Enter search criteria to filter Charge Definitions.
• Add new Charge Definitions, delete custom Charge Definitions, and access existing Charge Definitions.

When enabled, the pricing administrator or product manager selects a Charge Definition first when creating a charge. The charge type and price type are automatically populated.

Charge Definitions can be used to standardize charge categories and are required for integration with Oracle Fusion Pricing.

Steps to Enable

CPQ provides an easy method of uptaking Charge Definitions - especially if charges have already been defined in the productized Charge object introduced in Oracle CPQ 23C. CPQ provides a way to automatically generate your Charge Definitions from existing Charge attributes if you have already defined charges.

Complete the following steps to enable Charge Definitions.

1. Navigate to the Admin page.

2. Click Pricing Portal in the Products section.

3. Click on the Pricing Options card.

4. Click Edit.

5. Set the Enable Charge Definitions option to On.

6. Click Save or Update.

7. If you have not yet defined any pricing in CPQ using the new productized Charge feature, click Proceed to complete the enabling of Charge Definitions.

--OR—

If you have defined Charges pricing in CPQ, complete the following:

1. 1. Select Generate Charge Definitions Only to automatically create the Charge Definitions from the combinations of Price Type and Charge Type that you have already used.

   2. Review and verify the Charge Definitions that have been automatically created before taking the next step. For details on this process, refer to Pricing > Pricing Portal > Charge Definitions in the Oracle CPQ Administration Online Help.

   3. Once you are satisfied with the Charge Definitions you will be using, click Proceed and the Charge Definitions will be automatically populated on each existing pricing charge.

Tips And Considerations

• Charge Definitions must be enabled for Oracle Order Management – CPQ integrations.

• Charge Definitions can be repeatedly enabled/disabled to allow you to iteratively revise and finalize your setup.

• When enabled, CPQ automatically creates a seeded Charge Definition called 'ONE_TIME_SALES_PRICE' that aligns with the seeded values in Oracle Fusion Pricing to facilitate end-to-end integration.

Commerce

Standard Commerce Process Upgrade Support – All new functionality for controlled entities added to the Standard Commerce Process in Oracle CPQ 23D will be automatically available to existing customers as part of the product release upgrades.

• When a new Standard Process is created it automatically includes features provided in latest release.

• Override settings for default Standard Process controlled entities will not be affected by Standard Process upgrades.

• For more information about 23D Standard Commerce Process updates, refer to Oracle CPQ Administration Online Help > Commerce > Process > Standard Process.

The following Quoting & Ordering features are available in Oracle CPQ 23D.

Pricing Enhancements in Commerce

Beginning in Oracle CPQ 23D, Commerce transactions will support Rate Plan, Rate Card, and Charge Definition enhancements for subscription products and usage-based charges.

Rate Plans – When a Rate Plan is applied to a subscription type product, CPQ Pricing will apply the associated Rate Plan charges. For a given subscription/service product, the contract start date, end date, and contracted period will be applicable to all recurring and/usage charges, and pricing roll up attributes for this line item will be calculated accordingly.

Sales users can view the applied Rate Plan data for the subscription item in the Line Item Grid. Just like stand-alone charges, sales user can view associated charges from a Rate Plan in the Charge Details drawer.

The following text type attributes are added to the sub-document price attribute set to support Rate Plans:

• Applied Rate Plan (_price_applied_ratePlan)
• Applied Rate Plan Number (_price_applied_ratePlan_number)
• Applied Rate Plan Integration ID (_price_applied_ratePlan_integrationId)

Rate Cards - When enabled, the Pricing Rate Cards can be used to capture complex usage pricing for subscription products. The Rate Card data will be synchronized from CPQ Pricing to the charge array set and can be included in output documents to fully communicate to the customer the pricing that will be applied to consumption-based services. If Rate Card charges are applied to a subscription product from the Product Workbench or a Pricing Engine Price Model, a "View Rate Card" link is displayed in the Transaction's Charges Details drawer to allow sales to view the Rate Card data for the applicable line item.

This allows sales user to view the custom dynamic pricing matrix used in determining the invoice amounts to be billed on a periodic basis.

Charge Definitions – When Charge Definitions are used to provide standardized charge categories for a usage-based product, this information is displayed for the applicable charges in the Charge Details drawer. Sales users can also view Charge Definition and Rate Card data on the transaction line details page.

To support Rate Cards and Charge Definitions the following attributes will be synchronized from CPQ Pricing to the charge array set.

Attribute Name	Variable Name	Type	Description
Charge Definition Integration ID	_chargeSet_chargeDefinitionIntegrationId	Text	The Charge Definition code in the integrated order management system.
Charge Definition Code	_chargeSet_chargeDefinitionCode	Text	The code of the Charge Definition.
Charge Definition	_chargeSet_chargeDefintion	Text	The display label of the Charge Definition.
Rate Card	_chargeSet_rateCard	Text	Display label for the Rate Card applied in calculating this charge's price.
Rate Card in HTML	_chargeSet_rateCardInHTML	Text Area	The HTML-formatted Rate Card data.
Rate Card Structure	_chargeSet_rateCardStructure	Text Area	The Rate Card used in calculating this charge's price.
Rate Card Variable Name	_chargeSet_rateCardVariableName	Text	Variable Name for the Rate Card applied in calculating this charge's price.

The new charge set attributes are also available in workflow Steps and can be used in Commerce Rules, Approval conditions, and Document Designer templates to display the new attributes in output documents.

Sales users can now view data from applied Rate Plans, Rate Cards, and Charge Definitions in Commerce.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Rate Card data is read-only in Oracle CPQ 23D and cannot be modified from the Transaction UI.

Line Item Grid Personalization

Oracle CPQ provides sales users with the flexibility of selecting columns, arranging columns, and applying filters in the Line Item Grid. Previously, Line Item Grid personalization was not retained when users cleared their cache, changed browsers, or switched between devices. Beginning in Oracle CPQ 23D, sales users can personalize the Line Item Grid and save their respective preferences by selecting Save Personalization from the View drop-down. The user's personalized Line Item Grid is retained for all transactions user has access to and all subsequent user sessions. Sales users can return to the default Line Item Grid view by selecting Remove Personalization from the View drop-down.

Sales users can now save Line Item Grid personalization, and then apply their saved Line Item Grid personalization to subsequent user sessions.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

User-specific filters on the Line Item Grid are not saved/retained as part of the Line Item Grid personalization.

Default Collapsed Mode for Hierarchical Products in Line Item Grid

Beginning in Oracle CPQ 23D, hierarchical models and products will be displayed in collapsed mode by default. Sales users can identify collapsed items, and then select an individual item or use the Expand All option to view all items within the model or product hierarchy. When a sales user selects the Expand All option, their viewing preference is persistent and will be saved to their Line Item Grid personalization as well. A checkmark has been added to the view menu drop-down to indicate the selected preference.

By defaulting to the Collapsed mode for the hierarchical items in the Line Item Grid, sales users can interact with the products at the root level and when needed, see more details of the product hierarchy by Expanding the line item hierarchy.

Steps to Enable

You don't need to do anything to enable this feature.

Transaction Array Enhancements

Beginning in Oracle CPQ 23D, CPQ will allow sales users to filter and sort main and sub-document transaction arrays. Sales users can click the ascending or descending arrows in the column header to sort a transaction array.

The Simple Filter supports quick text or numeric searches. To use the Simple Filter, click on the table toolbar Simple Filter icon, and then type the desired keyword or phrase and then press <Enter> or <Return> to filter results. If the keyword is present in any column, the resulting lines are returned. To deactivate the filter, click on the active Simple Filter icon.

This feature provides improved usability for sales users viewing and editing transaction arrays.

Steps to Enable

You don't need to do anything to enable this feature.

Adopt Oracle CX Sales Custom Variable Name Conventions in Commerce

Beginning in Oracle CPQ 23D, CPQ will adopt Oracle CX Sales variable naming conventions for custom items. When administrators create new custom entities in a Standard or non-Standard Commerce Process, an “_c” suffix will be appended to the variable name. This update only effects new custom entities, and there is no change to existing custom entities. This update is applicable to the following new custom entities in both Standard and Non-Standard Processes:

• Actions
• Analytics
• Attributes and Transaction Array Sets
• Data Columns
• Integrations
• Library Functions
• Printer Friendly and Composite Attribute XSL Views
• Rules
• Workflow Steps

The new naming convention for custom variable names provides more consistency for integrations with Oracle CX Sales.

Steps to Enable

You don't need to do anything to enable this feature.

Configuration

The following Configuration features are available in Oracle CPQ 23D.

Pricing Enhancements in Product Workbench

Oracle CPQ 23C introduced the Product Workbench (previously known as the Product Launch UI) for Oracle CPQ sites integrated with Oracle CX Sales. Beginning in Oracle CPQ 23D, integrated Oracle CX Sales users can access dynamic pricing, Rate Plans, Rate Cards, and Charge Definitions.

When an Oracle CX Sales product manager selects the Price action for a Digital Sales product, they can add, edit, or view pricing in the Product Workbench. If applicable, they can perform the following tasks from the product pricing page:

• Add Product Price - Use to add a single pricing item for the product.
• Add Charges - Use to add charges for the product.
• Add Rate Plan – Use to create a group of charges for the product.
• Add to Another Set – Use to select or add a CPQ Price Model.

Rate Plans

Integrated Oracle CX Sales product managers can also use Rate Plans to define and manage groups of charges that can be optionally applied to the pricing for subscription products. When more than one Rate Plans are defined for a product, the first Rate Plan will be applied during pricing. Product manager can reorder available Rate Plans to apply a different Rate Plan.

Rate Cards

Oracle CX Sales product managers can select Rate Card Templates and use the Rate Card item to define complex pricing for usage-based charges for a product.

Charge Definitions

When enabled, Charge Definitions provide standardized charge categories to create charges. The charge type and price type are automatically populated.

Volume and Tier Pricing

Beginning in Oracle 23D, integrated Oracle CX Sales product managers can select and define dynamic pricing for product prices or charges.

• Volume pricing applies the same price or discount to all items on a single transaction line. The price or discount is based upon the quantity (total number of units).
• Tier pricing applies different unit price values to different items of a single transaction line. The total price or discount of the transaction line is based on aggregating the pricing brackets for all units of the item for that transaction line.

Oracle CX Sales product managers can use CPQ Pricing Rate Plans, Rate Cards, Charge Definitions, and dynamic pricing when pricing their products.

Steps to Enable

You don't need to do anything to enable this feature.

Configuration Actions

Oracle CPQ 23D introduces configuration actions that function as triggers to invoke Recommendation Rules. When added to the condition of Recommendation Rules, invoking the action will trigger the rules. Administrators can add the Configuration Actions to the Configuration Layout to allow sales users to invoke the new actions.

From the new Action Administration List page, administrators can translate, export, add, update, delete, and clone Configuration action.

Configuration actions provide a dedicated object (a button) with predictable behavior that can be used as an input to trigger Configuration Recommendation Rules.

Steps to Enable

Perform the following steps to create a new Configuration action.

1. Navigate to the Admin Home page.
2. Click Catalog Definition in the Products section.
3. Navigate to the applicable Product Family, Product Line, or Model.
4. Select Actions from the Navigation drop-down, and then click List.
5. Click Add.

6. Enter the Name and Variable Name.
7. Click Apply or Update.

Add Configuration Action as a Recommendation Rule Condition

Perform the following steps to add a Configuration action conditions for a Recommendation.

1. Navigate to the Admin Home page.
2. Click Catalog Definition in the Products section.
3. Navigate to the applicable Product Family, Product Line, or Model.
4. Select Recommendations from the Navigation drop-down, and then click List.
5. Select the applicable Configurable Action from the Attribute or Action drop-down.

6. The following value are auto populated:
   1. Operator: Equals
   2. Value Type: Static
   3. Values: True
7. If applicable, add Attributes and Values to Set.
8. Click Apply or Update and Back.

Add a Configuration Action to a Configuration Layout

Perform the following steps to add a Configuration action to a Configuration layout.

1. Navigate to the Admin Home page.
2. Click Catalog Definition in the Products section.
3. Navigate to the applicable Product Family, Product Line, or Model.
4. Select Configuration Flows from the Navigation drop-down, and then click List.
5. Click the “Desktop” Layout link.

6. Select Actions from the Add drop-down.
7. Select the appropriate action from Actions window.
8. Drag and drop the action into the layout editor.
9. Click Save.

Integration

The following Integration features are available in Oracle CPQ 23D.

Near Real Time Synchronization for Oracle CX Sales SPIM Integration

Beginning in Oracle CPQ 23D, Oracle CX Sales SPIM (Sales Product Information Master) products and structures can be synchronized to CPQ using the “Upsert Product in CPQ” action when an appropriate CX Sales Routine trigger occurs. The Oracle CX Sales Integration Maps use pre-defined mapping for Standard Part Attributes and additional mapping can be added for custom attributes. The CPQ 23D (v15) Upsert BOM Item List REST API can create, update, or delete CPQ BOM hierarchies using a list format, instead of the hierarchical JSON format.

For example, an Oracle CX Sales product manager creates the PTO Model structure.

The corresponding structure is added to the CPQ BOM Item Definition data table BOM Item Tree using the new Upsert BOM Item List REST API.

The near real time synchronization for Oracle CX Sales SPIM Integrations provides synchronization of a given product, without waiting for a scheduled batch synchronization to occur.

Steps to Enable

Refer to Oracle CPQ Administration Online Help > Parts > Partner Parts Integration > Oracle CX Sales Product Information Master (SPIM) Integration to establish Oracle CX Sales Product Information Master (SPIM) as the Products Source for an Oracle CX Sales – Oracle CPQ Products Integration.

Oracle CPQ Subscription Pricing Integration with Oracle Fusion Pricing

Oracle CPQ 23D provides productized integration to synchronize price definitions involving usage charges, Rate Plans, and Rate Cards between the Oracle Fusion Pricing module (also known as QP) and CPQ for subscription-based products to support usage-related rating and invoicing and creation of subscriptions in Oracle Subscription Management.

CPQ synchronizes pricing setup entities including Rate Plans, Rate Cards and usage Charges to Oracle Fusion Pricing on demand, then writes the identifiers of these objects at runtime into quote charges, which can then be integrated downstream to Oracle Fusion Pricing via Oracle Fusion Order Management. For additional information, refer to Support Rate Plans for Oracle Order Management - CPQ Integrations.

When integrated with CPQ, Oracle Fusion Order Management applies the net prices negotiated in CPQ as pre-priced sales order lines. Fusion Order Management uses the Rate Plans, Rate Cards and usage prices integrated from CPQ to perform the rating of actual usage and the calculation of invoice amounts.

The new Pricing Portal Pricing Integration module allows CPQ pricing administrators to define the Default Partner Price List and initiate synchronization of price definitions between CPQ and Oracle Fusion Pricing. The initial synchronization will synchronize all relevant price definitions. Thereafter only delta changes are sent. Pricing administrators can click on the desired Log link to view details for the synchronization task including deleted pricing definitions, updated Price Model Items, and new Price Model Items.

Synchronization of price definitions with Oracle Fusion Pricing will provide synchronized usage charges, Rate Plans, and Rate Card data for Oracle Order Management orders. For example, the following CPQ quote shows the Supremo IOT Data product with two charges.

Charge 2 uses a Rate Card to provide tiered usage-based charges. Sales users can click View Rate Card to display the associated tiered charges.

When an order is created in Oracle Order Management, billing users can view the applied usage charges in the customer order.

When Rate Card data is associated with an order, user can click the Usage charge link to view synchronized Rate Card data from Oracle Fusion Pricing.

CPQ – Oracle Order Management integrated order will include synchronized price definitions for subscription type products.

Steps to Enable

Prerequisites

• Oracle Fusion Pricing and Oracle Subscription Management must be implemented.

• Before defining other pricing, set up the same values in both CPQ and Oracle Fusion Pricing for the following objects: Charge Types, Price Types, Price Periods, Usage UOMs, and Charge Definitions.

• If Rate Cards will be used, the columns used for the cards must be defined in Oracle Fusion Pricing Matrix Classes with the same domains of values as in CPQ.

Complete the following steps to set up a CPQ-Oracle Fusion Pricing integration.

1. Navigate to the Admin page.
2. Click Integration Center in the Integration Platform section.
3. Click Create Integration.
4. Select Generic Integration from the Type drop-down.

5. Enter "Fusion Pricing Integration" for the Name.
6. Enter the Request URL for the Oracle Fusion Pricing application.
7. Enter the Username and Password login credentials for the integration user.
8. Select the Enable Integration option.
9. Click Save.

Tips And Considerations

• To apply Volume-type tier pricing to a usage charge in Oracle CPQ 23D, create a Rate Card with the from/to tier dimensions as columns.

• Note that Oracle Fusion Pricing does not support tier pricing with rating usage. Only volume tiering is supported.

Salesforce: Connect using Oracle CPQ Integration Center

A new Salesforce CRM integration type is added to the Oracle CPQ Integration Center. This feature streamlines the setup and management of the connection(s) between Oracle CPQ and Salesforce. This new interface allows administrators to directly configure the details of the Salesforce integration without the assistance of customer support. Also, Oracle CPQ 23D User Integration page provides a complete list of all enabled Salesforce organizations and the user login.

New and existing Salesforce CRM integrations will use these properties when making Web Service calls to Salesforce.

The Salesforce CRM integration in the Integration Center supports three states, as follows:

• No CRM Integration setup – Oracle CPQ to Salesforce integration is not set up and does not yet exist.
• Enable Integration checkbox Not Selected – The administrator has started to set up the Salesforce CRM integration but the integration connection is not active. In this state, no calls to Salesforce can be made. This includes calls for buy-side integrations, use token generation, administrative testing, and part synchronization.
• Enable Integration checkbox Selected/Integration Fully Active – The administrator has set up the Salesforce CRM integration and the integration connection is active between the two applications. When active, the integration exists and administrator can entirely configure CRM integrations, and the user-side will execute those integrations.

Steps to Enable

To create a Salesforce CRM integration type, administrators with permissions can complete the following steps:

1. Click Integration Center in the Integration Platform section of the Admin Home page.
2. Click Create Integration.
3. Select CRM from the Type drop-down.
4. Select Salesforce from the Vendor drop-down. The Salesforce Integration field entries display.

5. Enter the Name of the integration. This can be any human readable value. This value will be shown on the User Integration page so users can distinguish between multi-organization setups.
6. Enter the Variable Name of the integration.
7. Enter the Endpoint URL. This is the login domain for your Salesforce organization. This supports standard login domains like login.salesfroce.com or test.salesforce.com as well as custom My Domains.

IMPORTANT: This URL must be included in the allow list of approved domains. To modify the allow list of approved domains, log a Service Request (SR) with My Oracle Support.

8. Enter the Organization Id. This is a maximum of 15 uppercase characters. This value can be retrieved from the Company Information page in Salesforce.
9. Enter the Client Id. This value is captured from the Connected App page in Salesforce.
10. Enter the Client Secret. This value is captured from the Connected App page in Salesforce.
11. Enter the API Version. The default value is 31. This sets the API version that outbound integrations will use.
12. (Optional) Enter the Package Namespace. The default value is cafsl.

IMPORTANT: This field must be null if you are on Managed Package 8.1 or earlier.

13.  Click Choose File and navigate to a valid certificate (for example, a.crt file) on your device. This certificate must be the same as the one created in the Salesforce environment.

IMPORTANT:

• It is essential that the certificate in Salesforce and Oracle CPQ match.
• When the Salesforce CRM integration is saved, the certificate is stored and available for download. Also the meta data associated with the certificate is automatically populated (Last Modified, Validity, and Issued By fields).
• Certificates expire after a set period of time. They must be periodically rotated to ensure continuous operation.

14. Select the Enable Integration checkbox to enable the Salesforce CRM.
15. Click Save.

WARNING:  Once the CRM Integration is active, unselecting the Enable Integration checkbox disables any integrations which use it. Run-time integrations will not execute and some administrative features may not be available.

The User Integration page is used to store partner login credentials and to generate or revoke the user’s OAuth tokens. To manage the tokens that Salesforce generates for user access, perform the following steps:

1. Navigate to the User Integration page as follows:

• As a user, click the My Profile icon in the Navigation menu to open the My Profile page then click User Integration at the bottom of the page.
• As an administrator, click Internal Users from the Admin Home page. Click on the user login link to open the User Administration page then click User Integration at the bottom of the page.

The CRM/idP tab displays with the Customer Relationship Management/Identity Provider user fields.

2. Select the Salesforce connection from the Organization Name drop-down. The Organization Name displays one (or more) enabled Salesforce connections for the user.
3. Enter the user login in the Login field.
4. Click Save.

IMPORTANT:

• If a token exists, the Revoke Token button displays. Clicking this button deletes the authentication token and clears the partner login field.
• If a token doesn’t exist, the Generate Token button displays. Clicking this button takes you to the Salesforce login page. Enter your Salesforce username/password. This generates a valid token and returns to the Oracle CPQ User Integration page where the presence of the Remove Token button indicates a token exists.
• Generating a token is an optional step and not required for most end users. If no token exists and the partner login field is populated, the token will be automatically generated when the user punches into Oracle CPQ for the first time from Salesforce.

Tips And Considerations

• Oracle CPQ is not certified to support Oracle Identity Cloud Service (IDCS) and Salesforce CRM Integration simultaneously.
• For existing Salesforce integrations upon upgrade to 23D, the Name and Variable Name are automatically populated for the existing integration.
• A new Revoke Tokens button is added to the Salesforce CRM Integration page. This button allows administrators to revoke all authentication tokens associated with the Salesforce CRM integration. The feature is beneficial when migrating from one Salesforce organization to another. In this case, the administrator can revoke all the tokens from the existing Salesforce organization before switching users to the new one.

Salesforce: Manage Salesforce Certificates

The new Salesforce CRM Integration includes support for Salesforce certificates. A Salesforce certificate ensures that communications claiming to originate from your organization are actually from your organization. Once the certificate is applied to the Oracle CPQ site, inbound communications from the Salesforce integration can be verified.

This feature allows administrators to view certificate-related details and upload/download certificates without the assistance of customer support.

Steps to Enable

To manage the Salesforce certificates, administrators with proper permissions can perform the following steps:

IMPORTANT: If you are creating a new Salesforce CRM integration type or entering a Salesforce certificate for the first time, follow the steps provided in Salesforce: Connect Using Oracle CPQ Integration Center.

1. Click Integration Center in the Integration Platform section of the Admin Home page.
2. Click on an existing CRM > Salesforce integration. The Salesforce CRM integration page displays with fields automatically populated.
3. (Optional) If you want to download the existing certificate, click Download Certificate. The certificate file is downloaded to your device.

4. Click Browse and navigate to a valid certificate (for example, a.crt file) on your device. This certificate must be the same as the one created in the Salesforce environment. It is essential that the certificate created in the Salesforce environment and one uploaded to Oracle CPQ match.
5. Click Save.

IMPORTANT: The updated certificate is stored and available for download. Also the meta data associated with the updated certificate is automatically populated (Last Modified, Validity, and Issued By fields).

Tips And Considerations

Each Salesforce CRM integration can have its own certification or if integrating with the same CPQ site, Salesforce integrations can use the same certificate. The shared certificate will need to be uploaded from its connection integration page multiple times (once for each shared connection).

Salesforce: Support Custom Login Domains

Oracle CPQ 23D supports custom login domains as well as the previously supported login.salesforce.com and test.salesforce.com URL domains. This feature supports Salesforce’s recently introduced Domain Management features and My Domain login and redirect policies.

Prior to Oracle CPQ 23D, we only associated a single domain, either login.salesforce.com or test.salesforce.com, for all Salesforce connections for an Oracle CPQ site.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Oracle CPQ meets the requirements of the Salesforce My Domain Login Policies by allowing:

• Logins from ONLY My Domain (custom domain)
• Logins from My Domain OR login.salesforce.com and test.salesforce.com

Support Rate Plan and Rate Cards for Oracle Order Management - CPQ Integrations

Oracle CPQ 23D will support Rate Plans when creating or canceling orders for Oracle Order Management – CPQ integrations. When a Rate Plan is applied to a subscription type product, CPQ Pricing will apply the associated Rate Plan charges. Using the new pricing integration, CPQ administrators can synchronize pricing definitions with Oracle Fusion Pricing.

As previously mentioned, sales users can view applied Rate Plan data for a subscription item in the Line Item Grid.

When an order is created in Oracle Order Management, billing users will be able to view the Rate Plan and usage charges within the customer order.

When Rate Card data is associated with an order, user can click the Usage charge link to view synchronized Rate Card data from Oracle Fusion Pricing.

Beginning in Oracle CPQ 23D, Oracle Order Management – CPQ integrations will include Rate Plan and Rate Card information for subscription type products.

Steps to Enable

Customers implementing the Rate Plans for existing CPQ Standard Process - Oracle Order Management integrations import the new CPQ-Oracle Order Management Package (CPQ_FOM_Package_23D.zip) and the new OIC Integration Package (CPQFOMIntegrations_23D.par) available in this release.

• Refer to CPQ Standard Process – Order Management Integration (Doc ID 2942508.1) to download integration packages.
• Refer to the CPQ – Order Management Integration Guide, Standard Process Update 23B or Later for detailed instructions.

Support Transaction Arrays in Data Cube Export

Beginning in Oracle CPQ 23D, CPQ will support exporting transaction arrays in Data Cube exports. Main and sub-document transaction arrays and array set attributes can be added to the Data Cube XML mapping file. Likewise, the default generated sample mapping.xml file now includes all array sets and array set attributes for the specified process. Data Cube exports also support filtering of transactions based on the criteria provided for the array set attributes.

For example, the following Data Cube XML mapping file includes a main document array set (services_c) and a sub-document array set (shippingOptions_c). The <array_set> tag is used to define the transaction arrays. The example filter (highlighted in green) will only export records where the “region_c” attribute values are “North America”.

Exported zip files will include .ctl and .dat files for each transaction array listed in the XML mapping file. The following example highlights the services_c (bm_rt_3023066262.ctl and bm_rt_3023066262.dat) and shippingOptions_c (bm_rt_3023068615.ctl and bm_rt_3023068615.dat) transaction array files included in the Data Cube export.

This feature allows customers to store Commerce attribute information in an array set, and then export the array set instead of exporting a large number of Commerce attributes.

Steps to Enable

You don't need to do anything to enable this feature.

Parts

The following Parts feature is available in Oracle CPQ 23D.

New Service-Related Parts Fields

Oracle CPQ 23D adds the following service-related standard parts fields for CPQ sites that are integrated with Oracle CX Sales.

Attribute Name	Type	Description
Service Duration Type	Type	Type of duration for an item that fulfills a service contract. Acceptable values: O (Open Ended), V (Variable), F (Fixed)
Duration	Integer	The duration to service a product, measured in the unit of Service Duration Period. Only applicable to a product that fulfills a service contract.
Duration Period	Text	The time period unit in which a product is service, e.g., month or year. Only applicable to a product that fulfills a service contract.

These fields are used to capture basic service attributes for “Extended Warranty”, "Included Warranty", "Maintenance", or "Subscription" Sales Product Type items. With this data, Quoting will be able to develop pre-defined logic specific for these items. For example, when an Extended Warranty is defined as F (Fixed), a sales representative won't be able to change the Duration, nor the Duration Period. On the other hand, when an Extended Warranty is defined as O (Open Ended), the Quote should allow the override of Duration and Duration Period.

The new parts fields support service-related products.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• To add the service-related standard part fields to the sub-document Part Attribute set, refer to Oracle CPQ Administration Online Help > Commerce > Attributes & Arrays > Attribute Sets > Manage Parts Attributes.

• To add attributes to the Line Item Gid, refer to the Line Item Grid section in Oracle CPQ Administration Online Help > Commerce > Documents > Commerce Layout Editor.

User Management

The following User Management feature is available in Oracle CPQ 23D.

Deactivate User Groups

Oracle CPQ 23D supports the ability for administrators to deactivate user groups. The Group Lists page will display active and inactive groups. Once a group is deactivated, it will no longer be allowed access permissions nor will it be selectable for access to Commerce and Configuration properties.

Administrators can grant different access to groups of users (using Participant Profiles) and different user-experiences in Commerce. This feature allows administrators to better manage their implementation of user groups. For example, administrators may deactivate a user group to further segment the group or to address changes in business processes.

Steps to Enable

To deactivate a user group, perform the following steps:

1. Click Groups in the Users section of the Admin Home page. The Group Administration page displays showing the active and inactive group lists.

 

2. To deactivate an existing group, click its Group Name to open the Group Administration page.
3. Click Inactivate.

The selected user group is moved to the Inactive Groups List and the group is no longer allowed access permissions nor is selectable for access to Commerce and Configuration properties.

Tips And Considerations

• A dependency error message displays while deactivating a group if it has any Administration, Commerce, or Configuration dependency. You must remove all dependencies before a Group can be deactivated.
• If the group variable name is used in BML scripts, a dependency error message does not display. Administrators can manually search BML scripts for the group variable and modify the logic before deactivating the group.
• All Access Administration Group cannot be deactivated.
• Both Host Company and Partner Organization Groups can be deactivated.
• The Get User Group REST APIs response result will only provide active groups.

Web Services

The following Web Service features are available in Oracle CPQ 23D.

Add Last Deploy Date to Configure REST API

Beginning in Oracle CPQ 23D (REST version v15), the Last Deploy Date of the product family will be added to the Configure Model REST API response when Configuration cache is enabled.

This will allow customers to validate if a local cache instance is up to date with the most current Configuration layout updates.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

BOM Mapping REST API Enhancements

Oracle CPQ 23D provides the following BOM Mapping REST API enhancements:

• “Root BOM Item Label” and “Root BOM Item Part Number” are now included in the BOM Item Definition instance and collection responses.
• Case insensitive queries can now be performed on the BOM Item Setups collection.

Upsert BOM Item List

Oracle CPQ 23D also adds the Upsert BOM Item List endpoint to create, update, or delete CPQ BOM hierarchies. This endpoint uses a list format, instead of the hierarchical JSON format.

• Endpoint: /rest/v15/bomItemSetups/actions/upsertBomItemList
• Method:  POST

Oracle CPQ 23D (v15) BOM Mapping REST API enhancements support new pricing features, facilitate product structure synchronization with Oracle CX Sales, and enable case insensitive searching for BOM items.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Calculate Price REST API Enhancements

The Calculate Price REST API is updated to support Charges and Rate Plans.

Oracle CPQ 23D (v15) Calculate Price REST API enhancements support new pricing features.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Configuration Product Administration REST API Enhancements

Oracle CPQ 23D provides the following enhancements to the Configuration Product Administration REST API:

The following endpoints are added to support Product Family Deployment:

Deploy a Product Family

Use this endpoint to deploy a product family using web services. Deployments can be scheduled, and users can set up email notifications. Data tables associated with rules can be deployed along with the product family.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/actions/deploy
• Method:  POST

Get Undeployed Data Tables

Use this endpoint to retrieve a list of undeployed and live data tables that are referenced within the product family's table-based configuration rules.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/actions/getRelatedUndeployedDataTables
• Method:  POST

Oracle CPQ 23D also adds endpoints to support Configuration actions:

Get All Configuration Actions

These endpoints retrieve all Configuration actions for the respective Product Family, Product Line, or Model.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName} /productLines/{prodFamLineName}/models/{modelVarName}/_actions
• Method:  GET

Add a Configuration Action

These endpoints add a Configuration action to the respective Product Family, Product Line, or Model.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions
• Method:  POST

Get a Configuration Action

These endpoints retrieve the specified Product Family, Product Line, or Model Configuration action.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}_actions/{actionVarName}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions/{actionVarName}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions/{actionVarName}
• Method:  GET

Update a Configuration Action

These endpoints update the specified Product Family, Product Line, or Model Configuration action.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions/{actionVarName}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions/{actionVarName}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions/{actionVarName}
• Method:  PUT

Delete a Configuration Action

These endpoints delete the specified Product Family, Product Line, or Model Configuration action.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions/{actionVarName}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions/{actionVarName}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions/{actionVarName}
• Method:  DELETE

Get All Configuration Action Translations

These endpoints retrieve all Configuration action translations for the respective Product Family, Product Line, or Model.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_ations/translations
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions/translations
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions/translations
• Method:  GET

Add a Configuration Action Translation

These endpoints add a Configuration action translation to the respective Product Family, Product Line, or Model.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions/translations
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions/translations
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions/translations
• Method:  POST

Get a Configuration Action Translation

These endpoints retrieve the specified Product Family, Product Line, or Model Configuration action translation.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions/{actionVarName}/translations/{translationId}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{ prodFamLineName}/_actions/{actionVarName}/translations/{translationId} 
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions/{actionVarName}/translations/{translationId}
• Method:  GET

Update a Configuration Action Translation

These endpoints update the specified Product Family, Product Line, or Model Configuration action translation.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions/{actionVarName}/translations/{translationId}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/_actions/{actionVarName}/translations/{translationId}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines//{prodFamLineName}/models/{modelVarName}/_actions/{actionVarName}/translations/{translationId}
• Method:  POST

Delete a Configuration Action Translation

These endpoints delete the specified Product Family, Product Line, or Model Configuration action translation.

• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/_actions/{actionVarName}/translations/{translationId}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{ prodFamLineName}/_actions/{actionVarName}/translations/{translationId}
• Endpoint: /rest/v15/allProductFamilySetups/{varName}/productFamilies/{prodFamVarName}/productLines/{prodFamLineName}/models/{modelVarName}/_actions/{actionVarName}/translations/{translationId}
• Method:  DELETE

The new Oracle CPQ 23D (v15) Configuration Product Administration REST APIs support Product Family deployment and management the new Configuration actions.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

History Action for Commerce REST API

Oracle CPQ 23D adds support for Commerce History type actions for (v15) REST APIs. This endpoint allows customers to retrieve historical changes for a transaction, similar to the Display History Action on the Transaction UI, using REST API web services.

• Endpoint: /rest/v15/commerceDocumentsOraclecpqoTransaction/(id}/actions/getHistory
• Method: POST

Beginning in Oracle CPQ 23D (v15), customers can use web services to retrieve historical changes for a transaction.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Migration Package REST API

Oracle CPQ 23D supports the following migration package and migration resource REST API web services enhancements:

• Add Util Library Namespaces to migration package REST APIs to aid in package lifecycle management. The unique namespace can be applied when creating, updating, or searching migration package resources. Refer to Product Lifecycle Management for Util Library Namespace usage and procedures.
• Specify granular (low-level) content in the request payload while creating or updating a migration package using the following endpoints:
  • Create (POST) - /migrationPackages
  • Update (PATCH) - /migrationPackages/{id}
  • Update (POST) - /migrationPackages/{id}

IMPORTANT: The REST API call supports only one granular (low-level) content request as part the associated high-level content in the request payload.

The following new migration package and migration resource REST API web services are supported:

Get Migration Package Content Dependencies

Use this endpoint to retrieve content dependencies for a migration package.

• Endpoint:  /rest/v15/migrationPackages/{id}/content/dependencies

• Method:  GET

Get Dependencies for Selected Migration Resources or Migration Package from Source Site

Use this endpoint to retrieve dependencies for selected migration resources or migration package from a source site.

• Endpoint:  /rest/v15/migrationResources/dependencies

• Method:  POST

Migrate Selected Migration Resources or Migration Package from Source Site

Use this endpoint to migrate the selected migration resources or migration package from a source site.

• Endpoint:  /rest/v15/migrationResources/actions/migrate

• Method:  POST

Steps to Enable

To enable this feature you need to log a Service Request (SR).

Tips And Considerations

• Once this feature is enabled by logging a Service Request on My Oracle Support., the Migration REST API is available from the Oracle CPQ Integration Catalog.
• The migration package REST APIs are only available for users with administrative permissions and have access to the Migration feature.

Pricing Setup REST API Enhancements

Oracle CPQ 23D adds the following REST API web services to support the Rate Plan business object and pricing integration:

Submit Fusion Pricing Synchronization Task

Use this endpoint to submit a task to synchronize pricing definitions from CPQ to Fusion Pricing.

• Endpoint: /rest/v15/pricingSetup/actions/syncWithFusionPricing
• Method:  POST

Charge Attributes

Get All Charge Attributes

Use this endpoint to retrieve all pricing Charge Attributes.

• Endpoint: /rest/v15/pricingSetup/chargeAttributes
• Method:  GET

Add a Charge Attribute

Use this endpoint to add a Charge Attribute

• Endpoint: /rest/v15/pricingSetup/chargeAttributes
• Method:  POST

Update a Charge Attributes

Use this endpoint to update pricing Charge Attributes.

• Endpoint: /rest/v15/pricingSetup/chargeAttributes
• Method:  PATCH

Get a Charge Attribute

Use this endpoint to retrieve the specified Charge Attribute.

• Endpoint: /rest/v15/pricingSetup/chargeAttributes/{attributeVarName}
• Method:  GET

Delete a Charge Attribute

Use this endpoint to delete the specified Charge Attribute.

• Endpoint: /rest/v15/pricingSetup/chargeAttributes/{attributeVarName}
• Method:  DELETE

Update a Charge Attribute

Use this endpoint to update the specified Charge Attribute.

• Endpoint: /rest/v15/pricingSetup/chargeAttributes/{attributeVarName}
• Method:  PATCH

Charge Definitions

Get All Charge Definitions

Use this endpoint to retrieve all pricing Charge Definitions.

• Endpoint: /rest/v15/pricingSetup/chargeDefinitions
• Method:  GET

Add a Charge Definition

Use this endpoint to add a pricing Charge Definition.

• Endpoint: /rest/v15/pricingSetup/chargeDefinitions
• Method:  POST

Get a Charge Definition

Use this endpoint to retrieve the specified pricing Charge Definition.

• Endpoint: /rest/v15/pricingSetup/chargeDefinitions/{code}
• Method:  GET

Delete a Charge Definition

Use this endpoint to delete the specified pricing Charge Definition.

• Endpoint: /rest/v15/pricingSetup/chargeDefinitions/{code}
• Method:  DELETE

Update a Charge Definition

Use this endpoint to update the specified pricing Charge Definition.

• Endpoint: /rest/v15/pricingSetup/chargeDefinitions/{code}
• Method:  PATCH

Price Models

Get All Price Model Items

Use this endpoint to retrieve all Price Model Items for the specified Price Model.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems
• Method:  GET

Add a Price Model Item

Use this endpoint to add a Price Model Item to the specified Price Model.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems
• Method:  POST

Get a Price Model Item

Use this endpoint to retrieve the specified Price Model Item.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  GET

Delete a Price Model Item

Use this endpoint to delete the specified Price Model Item.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  DELETE
• Rate Plans

Charges & Rate Plans

Get All Charges

Use this endpoint to retrieve all charges for the specified Price Model Item.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}/charges
• Method:  GET

Add a Charge

Use this endpoint to add a charge for the specified Price Model Item.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}/charges
• Method:  POST

Update Charges

Use this endpoint to update charges for the specified Price Model Item.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}/charges
• Method:  PATCH

Get a Charge

Use this endpoint to retrieve the specified Price Model Item charge.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  GET

Delete a Charge

Use this endpoint to delete the specified Price Model Item charge.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  DELETE

Update a Charge

Use this endpoint to update a Price Model Item charge.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  PATCH

Get All Rate Plans

Use this endpoint to retrieve all pricing Rate Plans associated to the specified Price Model Item.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  GET

Add a Rate Plan

Use this endpoint to add a pricing Rate Plan to a Price Model Item.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  POST

Update Rate Plans

Use this endpoint to update the specified Price Model Item Rate Plans.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  PATCH

Get a Rate Plan

Use this endpoint to retrieve the specified the specified Price Model Item Rate Plan.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  GET

Delete a Rate Plan

Use this endpoint to delete the specified the specified Price Model Item Rate Plan.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  DELETE

Update a Rate Plan

Use this endpoint to update the specified the specified Price Model Item Rate Plan.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  PATCH

Get All Rate Plan Charges

Use this endpoint to retrieve all charges for the specified Price Model Item Rate Plan.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  GET

Add a Rate Plan Charge

Use this endpoint to add a charge to a Price Model Item Rate Plan.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  POST

Update Rate Plan Charges

Use this endpoint to update charges for the specified Price Model Item Rate Plan.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  PATCH

Get a Rate Plan Charge

Use this endpoint to retrieve the specified Price Model Item Rate Plan charge.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  GET

Delete a Rate Plan Charge

Use this endpoint to delete the specified Price Model Item Rate Plan charge.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  DELETE

Update a Rate Plan Charge

Use this endpoint to update the specified Price Model Item Rate Plan charge.

• Endpoint: /rest/v15/pricingSetup/models/{modelVarName}/priceModelItems/{priceModelItemId}
• Method:  PATCH

Rate Card Templates & Rate Cards

Get All Rate Card Templates

Use this endpoint to retrieve all Rate Card Templates.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates
• Method:  GET

Add a Rate Card Template

Use this endpoint to add a Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates
• Method:  POST

Get a Rate Card Template

Use this endpoint to retrieve the specified Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}
• Method:  GET

Delete a Rate Card Template

Use this endpoint to delete the specified Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}
• Method:  DELETE

Update a Rate Card Template

Use this endpoint to update the specified Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}
• Method:  PATCH

Get All Rate Card Template Columns

Use this endpoint to retrieve all columns for the specified Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns
• Method:  GET

Add a Rate Card Template Column

Use this endpoint to add column to the specified Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns
• Method:  POST

Update Rate Card Template Columns

Use this endpoint to update columns for the specified Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns
• Method:  PATCH

Get a Rate Card Template Column

Use this endpoint to retrieve a Rate Card Template column.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns/{id}
• Method:  GET

Delete a Rate Card Template Column

Use this endpoint to delete a Rate Card Template column.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns/{id}
• Method:  DELETE

Update a Rate Card Template Column

Use this endpoint to update the specified Rate Card Template column.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns/{id}
• Method:  PATCH

Get All Rate Card Template Column Translations

Use this endpoint to retrieve translations for the specified Rate Card Template column.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns/{id}/translations
• Method:  GET

Add Rate Card Template Column Translations

Use this endpoint to add Rate Card Template column translations.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns/{id}/translations
• Method:  PUT

Get a Rate Card Template Column Translation

Use this endpoint to retrieve the specified language translation for a Rate Card Template column.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/columns/{id} /{languageCode}
• Method:  GET

Get All Rate Card Template Translations

Use this endpoint to retrieve translations for the specified Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/translations
• Method:  GET

Add Rate Card Template Translations

Use this endpoint to add Rate Card Template translations.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/translations
• Method:  PUT

Get a Rate Card Template Translation

Use this endpoint to retrieve the specified language translation for a Rate Card Template.

• Endpoint: /rest/v15/pricingSetup/rateCardTemplates/{templateVarName}/translations/{languageCode}
• Method:  GET

Get All Rate Cards

Use this endpoint to retrieve all Rate Cards.

• Endpoint: /rest/v15/pricingSetup/rateCards
• Method:  GET

Add a Rate Card

Use this endpoint to add a Rate Card.

• Endpoint: /rest/v15/pricingSetup/rateCards
• Method:  POST

Get a Rate Card

Use this endpoint to retrieve the specified Rate Card.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}
• Method:  GET

Delete a Rate Card

Use this endpoint to delete a Rate Card.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}
• Method:  DELETE

Update a Rate Card

Use this endpoint to update the specified Rate Card.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}
• Method:  PATCH

Get Rate Card Data

Use this endpoint to retrieve data for the specified Rate Card.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}/data
• Method:  GET

Update Rate Card Data

Use this endpoint to update Rate Card data.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}/data
• Method:  PATCH

Get Rate Card Translations

Use this endpoint to retrieve translations for the specified Rate Card.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}/translations
• Method:  GET

Add Rate Card Translations

Use this endpoint to add Rate Card translations.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}/translations
• Method:  PUT

Get a Rate Card Translation

Use this endpoint to retrieve the specified language translation for a Rate Card.

• Endpoint: /rest/v15/pricingSetup/rateCards/{rateCardVarName}/translations/{languageCode}
• Method:  GET

Oracle CPQ 23D provides the following updates to existing endpoints:

• Added the Enable Charge Definition option to Pricing Options endpoints.
• Added Dynamic Pricing Type property to Price Model Pricing Data endpoints.

Oracle CPQ 23D removes support or limits the following existing endpoints:

• Add Price Model Pricing Data (Replaced with Add a Price Model Item)
• Delete a Price Model Pricing Data Item (Replaced with Delete a Price Model Item)
• Update a Price Model Pricing Data Item (Replaced with Update a Price Model Item)

Oracle CPQ 23D (v15) Pricing Setup REST API enhancements support new pricing features.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

IMPORTANT Actions and Considerations

PRE-UPGRADE CONSIDERATIONS

Modifications to Known Functionality

Before upgrading to Oracle CPQ 23D, we recommend you review the modifications to known functionality and plan accordingly.

Oracle COQ Feature	Description
Pricing Bulk Service	With the introduction of the new Price Model Item object, the signature for bulk services on prices has changed. Bulk download files created on earlier releases can no longer be uploaded without revision. We advise generating a new bulk download of pricing data after upgrading to 23D to use as the basis for performing updates.
Price Charges-related Attributes	When using pricing charges, the standard Charge Key Attributes (Price Type, Price Period, and Charge Type) now require a non-null value. If null values exist prior to upgrade, the values will be populated with the default value on upgrade, with the Price Period populated only for recurring and usage charges. A Usage UOM value is now required for charges with a Price Type of 'Usage'. If none is specified, when you modify the charge's pricing the default Usage UOM will be applied.
Pricing REST API	Several REST APIs for Price Model Pricing Data have been replaced with Price Model Item APIs to support the new Price Model Item object. See the Pricing Setup REST API Enhancements.
Fusion Order Management Integration	Beginning in Oracle CPQ 23C, Oracle Fusion Order Management application requires that each Charge for an item have a unique combination of Price Type and Charge Type. If you are integrating Oracle CPQ with Fusion Order Management, you will need to define a different Charge Type to distinguish Charges with the same Price Type but different Price Periods.
Site License Metric	Oracle CPQ 23C modified the user license counting to exclude Web Services Only users in the count. In addition, once the maximum number of licenses is allocated, Web Services Only users can still be added to the site.

Planned Changes to Supported Features

To continually improve our application, Oracle CPQ routinely evaluates product capabilities to identify older features that should be replaced with improved functionality. Supporting outdated features adversely impacts the value that we bring to our customers. This announcement provides information to CPQ administrators and IT professionals to prepare for future updates, including the uptake of provided alternative functionalities. The table below includes planned feature deprecations and their removal release schedule.

What does this mean?

“Deprecated” means the feature is planned for removal in a future Oracle CPQ Update (see End of Life column in the table below). The feature will continue to function for existing users until that time but will not be further enhanced or documented. After removal, the feature will no longer be supported or function.

Oracle CPQ Feature	Deprecation Announced	End of Life and Removal	Description
Native Lightning UI for Salesforce Connector	23B	24B	In Oracle CPQ 23B, we announced the deprecation of the Native Lightning UI, also known as the “Lightning Mode”, in the Salesforce managed package. The end of life and removal of this functionality will occur in Oracle CPQ 24B.
Legacy Global Functions	21C	24A	In earlier versions of Oracle CPQ the Legacy Global Functions, also known as Jython scripts, allowed customers to write custom python scripts to use with BML for various types of processing. Due to poor performance, Oracle CPQ ended support for these scripts several years ago. If your Oracle CPQ implementation uses this functionality, we recommend administrators migrate to standard supported functionality (e.g., Util BML Libraries, Commerce BML Libraries, and BMQL). To verify if you have Legacy Global Functions enabled in your environment, follow the steps below: Navigate to the Admin Home Page. Under Developer Tools section, if you see the Global Functions option available this indicates that Legacy Global Functions are enabled for your CPQ environment.
GXT Customer Images and CSS References	21C	24A	GXT is a Java framework for building web application pages. Oracle CPQ used this framework for its internal implementation and did not expose this for customer use. We are eliminating this framework from our product. If you are referencing images or CSS provided by this framework, we strongly recommend you to remove those references from your implementation. The end of life and removal of this functionality is Oracle CPQ 24A. GXT Images/Icons References The images used by this framework are likely found under the folder path: "/gwt/gxt/images/default/" Refer to the example below. If you are referencing any image from this folder, remove those references and use the File Manager to manage your customized images. GXT CSS References The CSS file used by this framework are likely found under this folder path: "/gwt/gxt/css/gxt-all.css". Refer to the example below. If you have customized the above CSS file or referencing any CSS classes from this file, remove those customizations and use Stylesheet Manager to manage your customized CSS. IMPORTANT: Depending on your specific implementation, the folder may not be exactly in the same path as referenced above. Review the folders to find the images/default folder and gxt-all.css file.

Custom JavaScript and CSS

While Oracle CPQ does not endorse or guarantee the use of JavaScript customizations, we recognize that some customers have extended the Oracle CPQ. Customizations may conflict with new Oracle CPQ platform features, data may be corrupted or lost, maintenance and support may be difficult, cross-browser support must be verified, performance may be impaired, and testing is required for each upgrade. Customers should consider carefully the relative benefits of JavaScript customizations in light of the associated risks.

Customers are recommended to utilize the CPQJS APIs instead of manipulating the Document Object Model (DOM) structure or specific elements, classes or IDs.

If customers have added custom JavaScript that leverages the Document Object Model (DOM) structure or specific elements, classes or IDs, this customization should be thoroughly tested and may require refactoring.

Oracle CPQ 23A and later supports JET v12.1.0. Please note the following:

• Select One component (<oj-select-one>) is deprecated and has been replaced with Select Single (<oj-select-single>). The following are impacted by this change: Favorites List and Detail pages, Commerce Analytics graph, and Single Select Menu (SSM).

• Standard JET tables with data table cell tag (<td>) has updated id property syntax and the headers property is removed. For example:

  • JET v12.1.0 syntax: <td class="oj-table-data-cell oj-form-control-inherit" id="mandatoryModels-table:48_0">Recommended Model 1</td>

  • JET v10.0.0 syntax: <td class="oj-table-data-cell oj-form-control-inherit" id="mandatoryModels-table:modelName_48" headers="mandatoryModels-table:modelName">Recommended Model 1</td>

• For Configuration Array set read-only cells, .oj-table-data-cell.oj -hover styling has been updated from background-color: #f2f2f3; to linear-gradiant (rbg(242, 242, 243), rgb(242, 242, 243)).

• When changing column selections for Simple List UIs and Configuration BOM panels, you need to hover over the columns to see the options list display. This change impacts Recommended Items List, Asset List, Performance Logs, and Eligibility Rules.

• In data tables, clicking on a table cell selects the current value in the table cell (all table cell contents are highlighted). If you begin typing, the newly entered content replaces the highlighted content.

• In the Commerce Layout Editor, the tooltip remains in view even after the applicable field is no longer visible.

• The error message text for required attributes is modified from "Enter a value" to "Select a value".

• When a sales user edits a date attribute, the date-picker tool will not automatically open. The user must either type in a value or click the date picker icon to select a value. On a mobile device, the user must select the date picker icon to select a value.

IMPORTANT: JET widget CSS applies to elements with class that starts with '.oj'. Oracle JET reserves this as a namespace. As such all customized elements that include '.oj' should be reviewed, tested, and refactored. Going forward no customized elements should include '.oj' in order to prevent future issues.

Oracle CPQ 22C upgraded jQuery to 3.6.0. Customers using earlier versions of jQuery need to upgrade and test their JavaScript customizations.

Refer to the following resources for more information:

• Oracle CPQ Administration Online Help > Style & Templates > JavaScript Customizations for JET UIs
• Oracle CPQ JET Configuration and Transaction UI: Refactoring Existing JavaScript Customizations (Doc ID 2490016.1)
• JavaScript Extension Toolkit and JET v12.1.0 Release Notes

Migration

When using Import From Source or Connect To Destination to migrate content, both sites must use the same major update. The migration of content can only occur across minor updates within the same major update.

• "Major update" = Update 23D
• "Minor update" = Update 23D Patch 1

When using Migration Packages, content from 19A and forward can be uploaded to the latest site version.

Resolved Known Issues

For information on bugs fixed in Update 23D, refer to the Oracle CPQ 23D Resolved Known Issues document available on My Oracle Support and the Oracle CPQ Administration Online Help.

Translation

For some system-defined messages and components, strings were removed and others added in Oracle CPQ 23D. If you have created your own implementation-specific translations of system-defined strings, some of these strings may no longer appear. Other strings may appear in English. The strings appearing in English are new and require translation.

Most of these messages and components are on the Administration side of Oracle CPQ, but you should review both your end user and administration pages before deploying your updated installation to confirm that all strings appear in the desired language.

Translation Status

Oracle CPQ supports the consumption of both single and multi-byte character sets. Submit a service request on My Oracle Support to enable your site for a new language.

For the following languages, a translation of the Oracle CPQ user interface is available for both the platform and the reference application:

• Chinese (Simplified) [China]
• Chinese (Traditional) [Taiwan]
• Czech [Czech Republic]
• Danish [Denmark]
• Dutch [Netherlands]
• English
• Finnish [Finland]
• French
• French [Canada]
• German
• Hungarian [Hungary]
• Italian
• Japanese [Japan]
• Korean [South Korea]
• Norwegian (Bokmål) [Norway]
• Polish [Poland]
• Portuguese [Brazil]
• Romanian [Romania]
• Russian [Russia]
• Spanish (Worldwide)
• Swedish [Sweden]
• Turkish [Turkey]

POST-UPGRADE CONSIDERATIONS

Upgrade and test all test instances on Oracle CPQ 23D before upgrading to production.

Customer Upgrade Testing

Customers should actively test new versions applied to non-production environments before a scheduled production upgrade. At minimum, customers should test the lifecycle of a transaction, with the typical actions that sales users perform. These may include but are not limited to: start transaction, new configuration, reconfigure existing configuration, parts search, discounting, printing, revisions, and approvals. Integration points should also be tested. Reviewing the What's New is highly recommended as this practice may indicate additional focus areas for testing.

Customers should also test any customizations made on the environment, especially JavaScript and unsupported integrations. Note that custom JavaScript is the most frequent cause of post-upgrade issues. Custom JavaScript and unsupported integrations are not supported by Oracle Support or Development. In particular, note that an upgrade may introduce changes to the DOM, which could impact use of customer JavaScript and CSS.

While Oracle CPQ does not endorse or guarantee the use of JavaScript customizations, we recognize that some customers have extended Oracle CPQ to support critical use cases. JavaScript API ("CPQJS") includes methods for accessing attributes, actions, and other elements on the JET Configuration and JET Transaction UIs. Customers should consider carefully the relative benefits of JavaScript customizations in light of the associated risks. Customizations may conflict with new Oracle CPQ platform features, data may be corrupted or lost, maintenance and support may be difficult, cross-browser support must be verified, performance may be impaired, and testing is required for each upgrade.

Oracle CPQ does extensive testing as part of the release cycle. Therefore your testing plan efforts should focus on testing customer-specific use cases rather than general tasks such as adding a configuration attribute.

Update Early Testing and Cohort Schedule

Customers are encouraged to take advantage of the Early Test periods in their 23D Update Cohort. This provides time for you to update one or more pre-Production environments to test customizations and use cases and make any necessary adjustments. The following table summarizes the Oracle CPQ Update 23D schedule. If you are uncertain which Update Cohort you are in, please submit a Service Request (SR) on My Oracle Support.

Cohort	Early Test Updates	Pre-Production Updates	Production Updates
A	October 6 and 7	November 3 and 4	November 17 and 18
B	October 6 and 7 November 3 and 4	December1 and 2	December 15 and 16
C	November 3 and 4 December 1 and 2	January 5 and 6	January 19 and 20

Oracle CPQ follows the Oracle SaaS Cohort Update Policy and Schedule. Quarterly Updates cannot be skipped. You need to integrate your Update schedule into your business and project plans. Customers must opt-in to Early Test by submitting a SR on My Oracle Support. You may elect to permanently opt-in to Early Test but must keep the same Early Test sites and cadence to do so.

Customers may request to have a few Pre-Production environments upgraded along with the Production environment on the standard Production schedule by submitting a SR on My Oracle Support. You may request to have the same sites upgraded along with your Production environment permanently to avoid having to submit SRs every quarter.

Issues after Upgrade

If a customer experiences issues after the upgrade, there are two different processes depending on if the upgrade is a non-production or production upgrade.

Issues after Non-Production Upgrade

• Log a Service Request (SR) through My Oracle Support.
• The Service Request will be picked up by Customer Support, and assigned to the Point of Contact (POC).
• The Service Request is worked as a standard Customer Support Service Request.

NOTE: In some instances the customer administrator may resolve issues without opening a Customer Support Service Request.

Issues after Production Upgrade

• In most cases, production upgrades go smoothly and the Upgrade Service Request is closed once the upgrade completes.
• The customer is instructed to open a "Severity 1" Service Request in the event that there is a critical issue after the production upgrade that was not identified after the non-production upgrade. Critical issues after upgrade would be considered production site down, 100% of users cannot quote, or other revenue impacting business critical issues.
• Once the "Severity 1" Service Request is created, the on-call team is notified.
• On-call team member(s) will work the Service Request towards resolution.
• On-call team member will then reach out to Oracle Upgrade Specialist who performed the post upgrade validation if needed.

Browser Support

Oracle CPQ supports all browser versions that meet the criteria of the Oracle Software Web Browser Support Policy.

If you experience issues using a supported browser version, open a ticket on My Oracle Support to resolve the issue. If an issue arises when using a supported browser, use a certified browser version until a fix is delivered. Certified browsers are selected based on current market share and are thoroughly tested to work with the current version’s standard functionality.

Certified Browsers

Windows

• Google Chrome 115.x
• Mozilla Firefox 115.x
• Microsoft Edge 115.x

Mobile Devices

• Apple iPad iOS 16.x, Safari browser
• Apple iPhone iOS 16.x, Safari browser

IMPORTANT: Compatibility issues with the selected browsers may exist when sites are created with additional JavaScript, alternate CSS, or other custom functionality. Customizations may require add-on work. Contact My Oracle Support to determine the availability of workarounds and minor fixes.

Salesforce Integration Support

Oracle officially supports version 8.x of the Oracle CPQ Connector for Salesforce.

Training

Please refer to the release documentation for all versions between your current version and the version to which you are upgrading to see all new functionality, resolved known issues, and functional known issues.

Refer to the Oracle CPQ Administration Online Help to become familiar with the new features introduced in Oracle CPQ 23C. For additional help, see My Oracle Support.

Verify any information not explicitly mentioned in this document as supported by the software against the product help for Oracle CPQ 23D.

Additional Information

For more information on Oracle CPQ, visit the Oracle CPQ documentation site.

Disclaimer

The details in this document are provided for high-level informational purposes only and are not intended to function as a specification or to replace the Online Help. Upgrading to a subsequent release may require the re-deployment of Commerce Processes, Configuration, or global function settings. Modifications to integration XSL files or APIs may also be required.