Oracle Configure, Price, Quote Cloud 23C What's New

Expand All

Update 23C

Revision History
Overview
Feature Summary
Configure, Price, Quote
IMPORTANT Actions and Considerations

Update 23C

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
27 JUN 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 23C.

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

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

	Ready for Use by End Users (Feature Delivered Enabled) Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.
Feature	Report	UI or Process-Based: Small Scale	UI or Process-Based: Larger Scale*
Configure, Price, Quote
Pricing
Multiple Charges for a Product
Extensible Charge Attributes
Pricing Engine Reference Data
Product Launch Support
Commerce
Add Products with Fixed Structure to a Commerce Transaction
Transaction Support for Multiple Charges
Configuration
Multi-Charge Price in Configuration
Rollup in Configuration
Integration
Product Hub Integration Added to Oracle Fusion CRM Integration
Product Launch for Oracle Sales Integration
Oracle CX Sales Product Information Master (SPIM) Integration
Batch Integration with SPIM for Structures and Components
Standard Process - Order Management Integration Charge Entity Support
Web Services
Calculate Price REST API
Configuration Run-Time Data REST API Enhancements
Extract Bulk Transaction Data REST API
Migration Package REST API
Parts REST API Enhancements
Parts Setup REST API Enhancements
Pricing Administration REST API Enhancements
SCIM-Compliant User Management REST API
>>Click for IMPORTANT Actions and Considerations

Configure, Price, Quote

Pricing

Oracle CPQ 23C introduces several new Pricing features to support the pricing of products with multiple charges. This capability dramatically reduces SKU proliferation and product complexity by allowing administrators to define a set of multiple prices or charges that will be applied when selling a single product in CPQ quoting and configuration. For example, a product could be sold as a subscription with both a monthly recurring subscription fee and a one-time activation fee without adding any additional SKUs or parts.

Multiple Charges for a Product

The subscription economy requires the ability to price a single product with multiple charges. Oracle CPQ 23C provides a productized, easy to implement and maintain means of defining and administering pricing for simple and complex products using one time, recurring, and usage/consumption-based pricing. The new Pricing Portal Charge object in association with the Pricing Engine delivers multiple product prices and charges during price execution for products including simple parts and complex BOMs.

For example, the following Pricing Data items are defined for the GENH-102:

The Activation Fee charge type, which is a One Time price type.
The Maintenance charge type, which is a Recurring price type with a Per Year price period.

In Commerce, the multiple charges will be stored as a child entity of a line item in addition to the line price.

When sales users select a line item with multiple charges and click Charge Details, information for the applied charges is displayed in the charge panel. Refer to Transaction Support for Multiple Charges for more information.

Charges can be defined in CPQ Pricing Engine, or via the CPQ Product Launch, both user interfaces access and maintain the same, single set of pricing defined in the CPQ Pricing Engine with different user experiences designed to support Product Management (Product Launch) and Pricing Management (Pricing Portal) personas.

For information about adding Product Launch charges, refer to Product Launch for Oracle CX Sales Integration.

For detailed instructions about adding Pricing Data items, refer to Pricing > Pricing Engine > Price Models in the Oracle CPQ Administration Online Help.

The business world is moving rapidly into new revenue models that capture value on a periodic recurring or consumption basis. This shift in business and revenue models requires greater flexibility in defining the pricing for products, including the application of multiple prices and types of pricing for a single product. The new 23C feature for multiple charges supports these new business models with the ability to define multiple prices of one-time, recurring, and usage type (also known as Price Type) and of varying charge types such as Installation Fee, Activation Charge, Storage Usage.

Steps to Enable

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

Tips And Considerations

Customers should continue to use the existing product pricing features in CPQ unless multiple prices are needed for a product. Upgrading to Oracle CPQ 23C will not impact existing pricing definitions for part and model-based product pricing.
By default, CPQ Pricing Engine uses a standard natural key for the Charge object including Price Type, Charge Type, and Price Period.
Both Charges and Product Prices are now returned in the internal CPQ pricing service and the Calculate Price REST API.
Charges and Product Prices are visible in quoting in the new Charge Panel and in Configuration in the Bill of Materials Panel.
When charges are defined, discounts for these charges will also need to be explicitly defined in Discount Price Models using the same charge key values.
Oracle CPQ 23C provides Bulk Services support for bulk maintenance of Pricing Engine Charge prices. Modifications of Charge Schema (Charge Attributes, keys, and associated Lookups) are not supported in Bulk Services.
Line item prices provide backward compatibility and can be setup with or without charges.

Extensible Charge Attributes

Oracle CPQ 23C introduces the ability to define custom pricing Charge Attributes in CPQ Pricing Engine, with the ability to incorporate this charge schema in Product Launch, Quoting, and the Calculate Price REST API. CPQ administrators can access Charge Attributes by clicking on the new Charge Attributes card in the Pricing Portal.

The Charge Attributes page lists standard and custom Charge Attributes. Customers can add their own custom charge attributes or use standard charge attributes that are provided in Oracle CPQ 23C.

When an administrator clicks on the Name of a charge attribute, details are displayed.

Standard Charge Attributes

Oracle CPQ 23C provides the following standard charge attributes to allow administrators to quickly define their own charges for their products. Standard charge attributes cannot be reordered, deleted, or inactivated.

Oracle CPQ provides unrivaled abilities to extend your implementation to meet the widest variety of unique business requirements. In 23C CPQ provides that same level of extensibility for defining the schema for the Charge object. Customers can define custom Charge Attributes that can be returned as part of the pricing REST APIs, CPQ pricing service, and displayed in the Transaction Charge Details panel.

Steps to Enable

Add a Charge Attribute

Perform the following steps to create a new Custom Charge Attribute:

Navigate to the Admin page.
Click Pricing Portal in the Products section.
Click on the Charge Attributes card.
Select Add from the Actions drop-down. The Create Charge Attribute panel opens.

Enter a name in the Name field.
Enter the Variable Name. Variable names can only contain alpha-numeric characters and underscores. The entry can be changed before saving, but after saving the value is read-only. Note: "_c" is automatically appended to the end of custom charge attributes.
Select the Data Type: Boolean, Currency, Date, Decimal, Integer, String, or Text Area.
Select a pricing lookup from the Lookup drop-down.
1. This field is only available for string data types.
2. Refer to Pricing Engine Reference Data for more pricing lookup information.
(Optional) Select or enter a Default Value.
1. The default value cannot be specified for currency or text area data types.
2. Only True or False values can be selected for Boolean data types.
3. When a Lookup is selected, you can select a default value from values defined in Pricing Lookups.
The Visibility field identifies if the charge attribute is visible in other CPQ modules. This field is automatically populated. Visibility options can be deleted, but this field cannot be empty. You can click inside the Visibility field to reselect modules.

Administration: CPQ administrator UIs, for example, Pricing Portal, Product Launch

Administration must be visible to display an attribute in Price Model > Pricing Data.

Runtime: Buy-side UIs, for example, quoting & configuration buy-side.

Check Required to make this field mandatory.
Check Negotiable to allow modification of this attribute at runtime.
(Optional) Enter a Description.

Note: The Key field cannot be modified and is only enabled for the Price Type, Charge Type, and Price Period standard charge attributes.

Tips And Considerations

By default, CPQ Pricing Engine uses a standard natural key for the Charge object including Price Type, Charge Type, and Price Period.
Oracle Order Management requires that each Charge for an item has a unique combination of Price Type and Charge Type. If you are integrating Oracle CPQ with Oracle Order Management you will need to define a different Charge Type to distinguish Charges with the same Price Type but different Price Periods.
Refer to Transaction Line Charge Array Set for instructions to synchronize charge attribute updates to the Transaction Line Charge Array Set.

Pricing Engine Reference Data

Oracle CPQ 23C introduces a new Pricing Lookups module that allows administrators to view, add, and manage the list of values that are available for use in product charges. Standard pricing lookups are provided for Charge Type, Discount Types, Price Periods, Price Types, and Usage Units of Measure. Pricing lookups allow customers to define defaults and domains of values for charge items.

The Pricing Lookup page lists standard and custom pricing lookups. Customers can add their own custom pricing lookups or use standard pricing lookups that are provided in Oracle CPQ 23C. In Oracle 23C these lists of menu values are used to control the available options for standard pricing attributes such as Price Type, Charge Type or Price Period, and for any menu-type custom attribute used in defining charges.

Standard Pricing Lookups

Oracle CPQ 23C provides the following standard pricing lookups to support standard charge attributes:

Price Type - Indicates the basis on which the pricing will be levied, whether one time, on a periodic basis or on usage. When pricing is rolled up for a model or system the pricing may contain a mixture of price types and is indicated by the value 'mixed'.

Price Periods - The time frequency, periodicity, or recurrence with which the price is levied or charged. For example, usage prices may be charged to the customer monthly or weekly.

Discount Types - Manual discount types. For example, Discount Percent or Discount Amount. These values are used in quoting to discount charges.

Charge Types - The classification of a charge associated with the price for a product or service. This attribute differentiates the purpose of charges with the same price type and price period. For example, the sale of a network device may have both a one-time purchase price (with charge type of 'Purchase Price') and a one-time installation price (with charge type of 'Installation Fee').

Usage Units of Measure - Units of measures for usage quantities. For example, cell phone calling may be measured by minutes, while cell phone data usage by GB.

You cannot inactivate or delete standard pricing lookups but you can add new lookup values and modify the display labels for these lookups.

CPQ’s new Pricing Reference Data (also referred to as ‘lookups’) provides a single place for defining the domains of values for pricing-related attributes. Pricing lookups allow pricing architects to manage the types of pricing that can be defined by pricing and product management personas and assure that the pricing can be accurately applied in downstream invoicing and subscription rating.

Steps to Enable

Add a Pricing Lookup

Perform the following steps to create a new pricing lookup.

Navigate to the Admin page.
Click Pricing Portal in the Products section.
Click on the Pricing Lookups card.
Click Add. The Create Pricing Lookup panel opens.

Enter a name in the Name field.
Enter the Variable Name. Variable names can only contain alpha-numeric characters and underscores. The entry can be changed before saving, but after saving the value is read-only. Note: "_c" is automatically appended to the end of custom pricing lookups.
(Optional) Enter an Integration ID.
(Optional) Enter a Description.
Click Create.
Click the Lookup Values Edit button.
Click Add.

Enter the following information:

Enter the Display Text for this option.
Enter the Variable Name. Variable names can only contain alpha-numeric characters and underscores. The entry can be changed before saving, but after saving the value is read-only. Note: "_c" is automatically appended to the end of custom pricing lookup values.
(Optional) Enter a Description.
(Optional) Enter an Integration ID.
The Status is automatically set to Active. To inactivate this option, select Inactive.

Perform one of the following:

Click Update when you done adding lookup values.
Click Cancel to undo your changes.
Click Add to create another lookup value.
To delete a single lookup value set the Status to Inactive, then click the line ellipsis and select Delete.

Associate a Pricing Lookup to a Charge Attribute

You can associate a pricing lookup to a charge attribute when you create a new string type charge attribute.

Refer to Add a Charge Attribute and select the applicable pricing lookup from the Lookup drop-down.
When a Lookup item is selected, you can also select a Default Value.

Tips And Considerations

Pricing Lookups cannot be migrated in Oracle CPQ 23C.
Oracle CPQ 23C only supports using Pricing Engine Reference Data to define the domain of values for Charge Attributes.

Product Launch Support

The new Product Launch feature, available for Oracle Sales integrated customers, provides an alternative UX for product managers to define prices and multiple charges for simple parts and complex BOMs that are applied at runtime in quoting and configuration. Prices defined in Product Launch are visible in the CPQ Pricing Engine, and base prices defined in Pricing Engine are visible in Product Launch.

Pricing and product managers use the new Product Launch feature to:

Discover and easily view multiple prices or charges that are currently defined for a product.
Understand and view prices that are defined for a product when it is sold standalone versus when it is part of a specific bundle or BOM.

Oracle CPQ 23C introduces new administrator user experiences tailored to the differing needs of product and pricing management personas. The CPQ Pricing Portal provides a cross-product view of pricing whereas Product Launch provides a product-centric ability to view and define prices and charges. CPQ Pricing Engine and Product Launch maintain a single, shared set of pricing data to assure consistency across your CPQ application and pricing consumers.

Steps to Enable

Perform the following procedures to enable Product Launch.

Set Up Oracle CX Sales Product Information Master (SPIM) Integration - Refer to 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.
Enter the Integration User Credentials - Refer to Product Hub Integration Added to Oracle Fusion CRM Integration to create a CRM integration type and include the Product Hub integration credentials.

Tips And Considerations

In Oracle CPQ 23C, Product Launch only displays Product Prices and Charges defined for Price Models associated to the Base Pricing Rule in Pricing Engine. Pricing Engine displays all Product Prices and Charges for all Price Model types (e.g. Absolute Price and Discount Price Models).

Migration Behavior

Beginning in Oracle CPQ 23C changes in behavior will be implemented for the migration of pricing items.
The Migration Center no longer supports migration of Price Model pricing data (including Product Prices, Tier Pricing, and Volume Pricing). This data can still be uploaded/downloaded using Bulk Services.
- The Migration Center continues support for migration of Pricing Rules, Pricing Rule Conditions, Price Model headers, and Price Model conditions.
- You can use Bulk Download and Upload to move Price Model pricing data and Charges.
Pricing Lookups and Charge Attributes cannot be migrated in Oracle CPQ 23C.

Commerce

Standard Commerce Process Upgrade Support - Beginning in 23C, any new functionality added to the Standard Commerce Process 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.

The following Commerce features are available in Oracle CPQ 23C.

Add Products with Fixed Structure to a Commerce Transaction

Beginning in Oracle CPQ 23C, products with fixed structures (BOM hierarchies) can be selected and added to the quote from Quick Add, Parts Search, Multi-part search, etc. Fixed structure products are accessible via the Quick Add functionality when the following conditions are met:

The root BOM item and does not have a model configuration defined with it. The root BOM can have a hierarchy under it in the BOM Item Definition table.
The product is marked as Direct-buy in the parts definition.
The BOM Item Definition ModelPath is empty for the root BOM item.
The following BOM Item Definition values are set for the root BOM item and all its child items:
- Optional is set to 'N'
- ItemType is not set to 'Option Class'

The root item icon is displayed in the Quick Add drop-down for BOM root items.

If the selected product is a root item, the associated BOM hierarchy is added to the Line Item Grid.

Oracle CPQ 23C introduces the new "Enable Fixed Product Structure expansion on Commerce transactions" Commerce option to support adding products with fixed structures to a transaction. This setting is enabled by default.

Sales users can now add products with fixed structures (BOM hierarchies) to a transaction using Quick Add.

Steps to Enable

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

Tips And Considerations

Supported capability/flows for Fixed Product structures:

Copy Line Items
Copy to Favorite
Add From Catalog
Add From Favorites
Add From Parts
Add from Multi Parts Buy
Import Line Item
Add From BML
Add from Quick Add
Revenue Line Item Import
Via Rest API
Add to Shopping Cart
Create Quote from Shopping Cart

Non-Supported flows:

Recommended Items

Transaction Support for Multiple Charges

Beginning in Oracle CPQ 23C, Commerce will support multiple charges for Add From Catalog, Quick Add, Opportunity Import, and corresponding REST APIs. In Oracle CPQ 23C, the Standard Quote Process’s pricing rollup attributes, like Price Type (rollup), Net Price (rollup), etc. are updated to incorporate Charges in the standard calculation logic.

For example, If a given subscription product line on a quote has both product pricing and multiple charges, then the Contract Value (Net Rollup) attribute will reflect the total calculated contract price value for all the price points.

The Multi-Charge indicator is displayed in the Line Item Grid for line items with multiple charges.

Sales users can select a line item with multiple charges and click on Charge Details to view the charge breakdown. The charge panel displays the charge type, price type, unit price, price period, and discount amount for all associated charges.

Sales users can also click View More Details to navigate to a charge’s detailed view page to modify charge item fields that are designated as negotiable in Pricing.

Transaction Line Charge Array Set

Beginning in Oracle CPQ 23C, customers can synchronize the pricing charge schema with Commerce to enable multiple charges for transaction line items. The pricing charge schema is defined by standard and extensible custom charge attributes. The new Synchronize Charge Array Set action allows administrators to synchronize the Transaction Line Charge Array Set with the pricing charge schema.

The new transaction Charge Array Set contains the following read-only attributes.

Customers can identify and characterize multiple charges for a single product. For example, a product could have a monthly recurring price and a one-time installation fee.

Steps to Enable

Complete the following steps to synchronize the Transaction Line Charge Array Set with the pricing charge schema, which is comprised of standard and extensible custom charge attributes. If the Transaction Line Charge Array Set doesn’t exist, it will be created when the Synchronize Charge Array Set action is invoked.

Navigate to the Admin Home Page.
Click Process Definition in the Commerce and Documents section.
Select Documents from the applicable process Navigation drop-down menu, and then click List.
Select Attributes from the Transaction Line Navigation drop-down menu, and then click List.
Click Synchronize Charge Array Set at the bottom of the Attribute List page.

Tips And Considerations

Refer to Multiple Charges for a Product for more information about multiple charges in pricing.
Refer to Extensible Charge Attributes for Pricing Charge Attributes administration information.
Charge Amount calculations apply their parent line's quantity as they do not have their own quantity in Oracle CPQ 23C.
If a Transaction Line Charge Array Set doesn’t exist, it will be created when the Synchronize Charge Array Set action is invoked.
Oracle CPQ 23C also supports usage of charge set attributes in Document Designer documents and Workflow Steps.
The Oracle CPQ 23C Commerce Standard Process is updated to support multiple charges for transaction line items.

Configuration

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

Multi-Charge Price in Configuration

Beginning in Oracle CPQ 23C, the Bill of Materials panel will display multiple charges where applicable. When there is more than one price associated with a BOM item, the price value will be replaced with a link with the phrase "Details". Clicking on or hovering over the "Details" link will show a popup with specific price information.

When there is more than one price associated with a BOM item, customers can view the multiple charges in the Configuration Bill of Materials panel.

Steps to Enable

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

Rollup in Configuration

Beginning in Oracle CPQ 23C, the Prices panel will display subtotals for the One-Time and Recurring charges. Tooltips are also provided to help users understand the significance of each new total.

Customers can view subtotals for the One-Time and Recurring charges in the Configuration Prices panel. To view more information about the multiple changes they hover over or click on the Details link in the Bill of Materials panel.

Steps to Enable

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

Integration

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

Product Hub Integration Added to Oracle Fusion CRM Integration

Product Hub integration is added to the Fusion Customer Relationship Management (CRM) integration type in the Oracle CPQ Integration Center. This new section stores the credentials required to access the Oracle Fusion Supply Chain Management (SCM) Product Information Management (PIM) application where the source parts data is maintained.

When the Oracle Fusion CRM Integration is connected with proper Product Hub credentials, part administrators can run or schedule part import or export directly from the Parts Integration page.

Steps to Enable

To create a CRM integration type and include the Product Hub integration credentials, administrators with access permissions can complete the following steps:

Click Integration Center in the Integration Platform section of the Admin Home page.
Click Create Integration.
Select CRM from the Type drop-down. The CRM Integration field entries display. The Vendor, Name, and Variable Name automatically-fill text for Fusion integration.

Enter the Endpoint URL. This is the Fusion domain URL.
Enter the Username of a Fusion Integration user with the sales administrator role.
Enter the Password of a Fusion Integration user with the sales administrator role.

IMPORTANT: The username and password of a Fusion Integration user with the sales administrator permissions is required to allow Oracle CPQ REST calls to sync a quote to an opportunity or to sync a sales catalog part in Oracle CX Sales.

(Optional) Enter the Scope. This is the OAuth Provider scope value.
In the Product Hub Integration section, enter the Username of the product administrator role.
In the Product Hub Integration section, enter the Password of the product administrator role.
Select the Enable Integration checkbox to enable the Oracle Fusion CRM.
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.

Once the Oracle Fusion CRM Integration is established with proper Product Hub credentials, part administrators can run or schedule part import or export directly from the Parts Integration page as follows:

IMPORTANT: Oracle CPQ 23C also supports Oracle CX Sales Product Information Master (SPIM) integration which provides pre-defined synchronization and single source control of parts management from Oracle CX Sales to Oracle CPQ. Refer to CX Sales Product Information (SPIM) Integration for more information.

Click Parts in the Products section of the Admin Home page. The Part Administration page displays.
Click Integration from the Part Administration page.

Select an import or export process from List Integrations section.
Click Run Now to begin the selected integration or Schedule to begin the selected integration at a later time.

(Optional) If you opted to schedule the integration for a later time, click Refresh to view the scheduled integration in the Scheduled Integrations section.
(Optional) View the Integration History to verify the status of a part import or export job and see log details.

Tips And Considerations

Prior to Oracle CPQ 23C, Oracle Fusion CRM part administrators maintained Product Hub credentials within the PIM tab of their My Profile page. In Oracle CPQ 23C, entry and maintenance of those credentials is moved to the Integration Center. Therefore, the PIM tab within the My Profile page is removed.
Prior to Oracle CPQ 23C, customers were required to log a Service Request in order to designate whether the product master for their site was CPQ or PIM. When PIM was selected, only import integrations were shown. When CPQ was designated, only export integrations were shown. In Oracle CPQ 23C and later, you no longer must designate a product master and both import and export processes are available.
The Integrations Log section of the Parts Integrations page designates if the job is parts import or export.
You are not able to run or schedule a single job which includes both import and export integrations. You may only run integrations of one type at a time.

Product Launch for Oracle Sales Integration

Oracle CPQ 23C introduces the Product Launch UI for Oracle CPQ sites integrated with Oracle Sales. Product Launch is a new solution designed for product managers, with the goal of making the definition and management of their products and services more intuitive and seamless. Product Launch provides the ability to set and edit pricing from the product-centric point of view (i.e. the user is presented with all the pricing defined for a particular product). If the product should be priced differently under different condition sets, Product Launch will display all records on a single page, grouped by those condition sets, making it easier to read.

Product Launch also makes it easy to define "contextual pricing", which can be thought of as the ability to define differentiated pricing when the product or service is to be sold together with other products and/or services.

Another major innovation introduced by Product Launch is the ability to define multiple charges for each product or service under the different circumstances mentioned above (conditional and contextual pricing) in a very intuitive way. These multiple charges can be of different types and there’s no limit to the number of charges associated with each product or service.

Product Launch is activated when an Oracle CX Sales product manager selects the Price action for a Digital Sales product.

The Product Launch page provides the following functions:

The product name and description are displayed at the top of the page.
The product status informs the sales user that the product is created or priced.
The Pricing Summary displays pricing plans and associated charges for the product. Pricing plans specify conditions that must be met to apply defined plan charges. The default plan always applies associated charges.
Product managers can click the Actions ellipsis symbol for the product to view product details or add/edit/view charges.
After editing charges for the product, sales users can cancel or submit the changes to return to the Oracle CX Sales Product page.

For complex structures (i.e. BOMs), the product hierarchy is displayed as an expandable/collapsible item.

When product managers click the View Product Details action, they can view the sales-related data for the product, extended descriptions, integration information. After viewing product details, product managers click Cancel to return to the Product Launch page.

When product managers click the Edit/View Charges action, they can view and manage pricing plans along with their associated charges.

Add a New Product Charge

Perform the following steps to add a new product charge:

Sign into Oracle CX Sales.
Navigate to Digital Sales > Products.
Select the Price action for a product. The CPQ Product Launch application will open.
Click on the product Action ellipsis, then select Edit/View Charges.
Click Add Charges.
Select the Charge Type.

Depending on the Charge Type, a second drop-down may appear to specify additional parameters for the selected charge type. For example,

Recurring charge types will have frequency options (e.g. Monthly, Yearly).
Usage charge types will have options to measure for usage quantities. For example, cell phone calling may be measured by minutes, while cell phone data usage may be measured by GB.

Enter the value for the charge.
If applicable, click Add Charges to add additional charges for the product price plan.
After adding new charges or modifying existing charges, click one of the following options.

Cancel to undo changes.
Save to keep new charges or changes to existing charges.
Submit to save new charges or changes and return to the Product Launch page.

In the process of launching new products, Product Managers have a product-centric user experience that provides seamless access to set product pricing. This pricing can consist of multiple charges of different types, can be defined differently in the context of commercial bundles, and/or different conditions.

Steps to Enable

Perform the following procedures to enable Product Launch.

Set Up Oracle CX Sales Product Information Master (SPIM) Integration - Refer to 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.
Enter the Integration User Credentials - Refer to Product Hub Integration Added to Oracle Fusion CRM Integration to create a CRM integration type and include the Product Hub integration credentials.

Oracle CX Sales Product Information Master (SPIM) Integration

Previously, XSL web service calls were used to integrate parts between Oracle CX Sales and Oracle CPQ. Although this approach allowed two-way communication, synchronization was labor intensive because part fields did not match and parts could be maintained in both Oracle CX Sales and Oracle CPQ applications. Oracle CPQ 23C delivers SPIM integration, which provides the following enhancements:

Pre-defined scheduled synchronization of parts from Oracle CX Sales to CPQ.
Single source control of parts management. When Oracle CPQ is integrated with the Oracle CX Sales Product Master, CX Sales becomes the parts master, and parts that are synchronized with the Product Master are non-editable in Oracle CPQ.

In Oracle CPQ 23C, the product synchronization from the Oracle CX Sales Product Master and CPQ is performed in scheduled batches, typically once every 24 hours. At the scheduled time:

CPQ sends a synchronization request to Oracle CX Sales.
Oracle CX Sales exports the entire set of records or a delta set of record charges to CPQ. Refer to Parts Synchronization Behavior for more information.
After receiving the export completion notification, CPQ updates parts in the CPQ application.

By default, the frequency of the parts synchronization is scheduled to occur daily (i.e. every 24 hours) and the batch download size is set to 100,000 exported items.

The Parts Administration page provides integration information and provides access to synchronization details and controls. To access the Parts Administration page navigate to the CPQ to the Admin Home page, and then click Parts in the Products section.

When CPQ is integrated with the Oracle CX Sales Product Master, "UnifiedProducts" is listed as the Item Master on the Parts Administration page.

CPQ administrators can still import and add new CPQ parts, but parts originated in CPQ are not synchronized with Oracle CX Sales.
For parts synchronized from the Oracle CX Sales Product Master, CPQ administrators can only view and provide translations for the integrated items. Synchronized parts can only be modified and deleted in the Oracle CX Sales application.
When Oracle CX Sales Product Information Master (SPIM) integration is enabled, existing CPQ parts that have the same part number as an Oracle CX Sales Product Master part will be synchronized, and thus become read-only in CPQ.
If a new part is added to the Oracle CX Sales Product Master and the part number matches an existing CPQ part, it will be synchronized, and thus become read-only in CPQ after the next synchronization.

To access synchronization details and controls, click the Integration button on the Parts Administration page. Synchronization details are displayed for both parts/items and BOM hierarchies/structures. Refer to Batch Integration with SPIM for Structures and Components for more information about BOM synchronization.

The following example shows synchronization details for an active parts synchronization.

Click the Sync Control Pause button to suspend the currently scheduled synchronization. When the synchronization is resumed:

A new part synchronization will begin immediately. Either a full synchronization or delta synchronization will occur.
The next part synchronization will initiate after a pre-defined interval, measured from the time the previous synchronization was initiated.

Parts Synchronization Behavior

A complete synchronization will occur for the first synchronization. If your parts system contains a large number of parts, complete synchronizations can be very time-consuming. After the initial synchronization, delta synchronizations will occur if the prior synchronization completes successfully without any record failures. Delta synchronizations are less time-consuming than a complete synchronization because they only transfer updates and additions that occurred since the last successful synchronization.

For parts synchronization, the max last updated date is used as filter parameter for delta records.
For BOM synchronization, the Last Sync Date header is used as filter parameter for delta records. If the Last Sync Date header is empty, all BOM records are exported.

A scheduled parts synchronization will not fail if an individual part fails to synchronize. However, an individual part synchronization failure will prevent delta synchronization from occurring until the individual part synchronization error is resolved. Part synchronization errors should be resolved as soon as possible since complete parts synchronizations can be very time-consuming. Customers can submit a Service Request (SR) on My Oracle Support to request synchronization logs

A parts synchronization will fail if:

The Oracle CX Sales site cannot be reached.
The Oracle CX Sales site credentials in Integration Center are incorrect.
The REST Notification Name specified in Configuration Settings doesn't match the name of the Web Service defined in Oracle CX Sales. When this occurs CPQ is not notified of a completed Oracle CX Sales export and will not continue the synchronization process.

The synchronization request to Oracle CX Sales site exceeds the CX Sales API timeout. If required, customers can contact My Oracle Support to change the CX Sales API timeout value.

The Oracle CX Sales Product Information Master (SPIM) Integration provides single source control of parts management.

Steps to Enable

The following procedures will establish Oracle CX Sales Product Information Master (SPIM) as the Products Source for an Oracle CX Sales – Oracle CPQ Products Integration.

View Current Parts Source in Oracle CPQ

Log into Oracle CPQ as a parts administrator or as a Full Access user.
Navigate to the Admin Home page.
Click Parts under Products. The Parts Search for Admin page appears.
The Item Master field shows the current parts source. If you see "UnifiedProducts" as the item master (source), your CPQ site is integrated with the Oracle CX Sales Product Master.

Note: If you don't find the Item Master section on the Parts Search for Admin page, contact My Oracle Support to enable the Oracle CX Sales Product Information Master (SPIM) parts integration.

Enter the Integration User Credentials

Beginning in Oracle CPQ 23C, the Product Hub integration is added to the CRM integration type in the Oracle CPQ Integration Center. Refer to Product Hub Integration Added to Oracle Fusion CRM Integration to create a CRM integration type and include the Product Hub integration credentials.

Set Up Unified Products Sync Configuration Options

Log into Oracle CPQ as a parts administrator or as a Full Access user.
Navigate to the Admin Home page.
Click Configuration Settings in the Products section.
Configure the Unified Products Sync options.

1. REST Notification Name: The name that will identify the export completion notification from Oracle CX Sales. This name must match the name of the Web Service defined in Oracle CX Sales.
2. Mapping ID: The Oracle CX Sales Integration Map Number that is used to map Oracle CX Sales to Oracle CPQ part attributes when synchronizing parts. The Mapping ID for the default mapping, which maps standard parts attributes, is DATAINTG-100.

Oracle CX Sales administrators can modify or clone the default mapping.

- - - The default mapping can be modified to map an additional Oracle CX Sales standard or custom part attribute to a CPQ custom part attribute.
    - The default mapping must be cloned if you want to map an additional Oracle CX Sales standard or custom part attribute to a CPQ standard part attribute.
    - When the default mapping is cloned, a new Mapping ID will be generated.

Enable Unified BOM Sync: This option to enable synchronization of Oracle CX Sales complex structures to Oracle CPQ BOM hierarchies.

IMPORTANT: Refer BOM Synchronization Behavior before enabling Unified BOM Sync.

Click Apply.

Tips And Considerations

Customers can submit a Service Request (SR) on My Oracle Support to change the synchronization frequency and/or batch download size.

Batch Integration with SPIM for Structures and Components

Beginning in Oracle CPQ 23C, complex structures created in Oracle CX Sales can be automatically synchronized into Oracle CPQ on a scheduled basis. When the Unified BOM Sync is enabled, this integration will synchronize Oracle CX Sales structures to the Oracle CPQ BOM Item Definition table. The unified BOM synchronization is initiated upon completion of the parts synchronization. The initial BOM sync will be a complete synchronization. The following BOM synchronizations will be delta synchronizations. BOM sync uses Last Sync Date header value to retrieve records during delta synchronization

When the Unified BOM Sync is enabled BOM synchronization details and controls are displayed below the part synchronization section on the integration page.

If required, Oracle CPQ administrators can click the Unified BOM Sync Details Start BOM Sync button to initiate a synchronization before the scheduled synchronization. If there is an active parts synchronization administrators will be prompted to wait for competition of the current synchronization before initiating a new BOM synchronization.

BOM Synchronization Behavior

This section identifies synchronization behavior that is specific to BOM/complex structure synchronizations.

A BOM synchronization will fail if:
- The Oracle CX Sales site cannot be reached.
- The Oracle CX Sales site credentials in Integration Center are incorrect.
- The REST Notification Name specified in Configuration Settings doesn't match the name of the Web Service defined in Oracle CX Sales When this occurs CPQ is not notified of a completed Oracle CX Sales export and will not continue the synchronization process.
- The synchronization request to Oracle CX Sales site exceeds the CX Sales API timeout. If required, customers can contact My Oracle Support to change the CX Sales API timeout value.
- Unified BOM Sync is not enabled in CPQ Configuration settings.
If an individual Oracle CX Sales structure fails to synchronize, it will not fail the entire BOM synchronization.
If a part that is referenced in a BOM fails part synchronization, the root BOM for that item will fail BOM synchronization. This will not affect synchronization of other root BOM items.
If BOM record synchronization failures occur, the earliest failure time is recorded and the number of BOM record synchronization failures will be displayed. When the next BOM Sync occurs, it will start from earliest failure time. For example, if there are 50 BOM records to synchronize and the 31st BOM record fails synchronization:
- The earliest failure time is recorded as the 31st BOM record.
- "1’ is displayed for the Failed Records in Last Successful Sync.
- 1 failure and 49 inserted/updated records will be listed in the Sync Details.
- When the next BOM Sync occurs, it will start from the 31st BOM record.

BOM/Structure Attribute Mapping

The following table shows the mapping between Oracle CX Sales and the CPQ BOM Item Definition table fields.

The Oracle CX Sales Product Information Master (SPIM) Integration with BOM Sync enabled allows synchronization of Oracle CX Sales complex structures to Oracle CPQ BOM hierarchies.

Steps to Enable

Complete the following steps to enable BOM synchronization.

Note: Oracle CX Sales Product Information Master (SPIM) Integration must be established prior to enabling BOM synchronization.

Navigate to the Admin Home page.
Click Configuration Settings in the Products section.
Set the Unified Products Sync - Enable Unified BOM Sync option to Yes.

Click Apply.

Standard Process - Order Management Integration Charge Entity Support

Oracle CPQ 23C will support multiple charges for Oracle Order Management – CPQ Standard Process integrations. The Oracle Order Management sales orders will include transaction line Charge Array Set attributes that are synchronized with CPQ Pricing Charge Attributes.

Beginning in Oracle CPQ 23C, Oracle Order Management sales orders can include multiple charges for Oracle Order Management – CPQ Standard Process integrations.

Steps to Enable

Customers implementing the multiple charges for existing CPQ Standard Process - Oracle Order Management integrations import the new CPQ-Oracle Order Management Package (CPQ_FOM_Package_23C.zip) and the new OIC Integration Package (CPQFOMIntegrations_23C.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 23C or Later for detailed instructions.

Tips And Considerations

IMPORTANT: Oracle CPQ - Oracle Order Management integrations from releases prior to Oracle CPQ 23B will not support multiple charges for Oracle Order Management sales orders.

Web Services

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

Calculate Price REST API

Oracle CPQ 23C updates the Calculate Price REST API to support charges in the pricing data.

Beginning in Oracle CPQ 23C, customers can use this web service to calculate and return both product prices and any charges defined in Pricing Engine.

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 Run-Time Data REST API Enhancements

Oracle CPQ 23C adds price type, price period, and pricing charges to the following endpoints:

Get BOM Items (Configuration)
Configure Model
Configure Model in System
Next Configuration Node
Reconfigure from Favorites
Reconfigure Model
Resume Configuration
Update Configuration

Beginning in Oracle CPQ 23C Configuration Run-Time Data REST APIs will support multiple charges in Configuration.

Steps to Enable

Extract Bulk Transaction Data REST API

The Extract Bulk Transaction Data REST API sends bulk transaction and transaction line data to the Oracle Cloud Infrastructure Object Storage service, which can be picked up by the Fusion Analytics Warehouse (FAW) to produce advanced reports and dashboards. This feature is released for customers on controlled availability in Oracle CPQ 23C. The release introduces the following endpoints to manage CPQ data extraction into the Object Storage:

Request Data Extract

This action will submit an asynchronous task to extract CPQ transaction and transaction lines data.

Endpoint: /rest/v14/extract/transactions
Method: POST

Get Site Status for Data Extract

This action returns the status of the site if it is available for extraction.

Endpoint: /rest/v14/extract/siteStatus
Method: GET

Get Data Extract Task Status

This action will return of the data extract task status.

Endpoint: /rest/v14/extract/status/{taskId}
Method: GET

Cancel Data Extract Task

This action will cancel the data extract task if not complete.

Endpoint: /rest/v14/extract/cancel/{taskId}
Method: POST

With the CPQ 23C release, customers now have available a high performance process for automatically populating a Fusion Analytics Warehouse subject area and dashboard for BI, reporting, and analysis of quoting and pricing data.

Steps to Enable

Submit a Service Request (SR) on My Oracle Support to File an SR to enable the extract process for your CPQ site.

Tips And Considerations

You will need a subscription to Fusion Analytics Warehouse to enable this feature, but there is no additional cost for the automated data pipeline that will populate FAW.

Migration Package REST API

Oracle CPQ 23C introduces Migration Package REST API endpoints to aid administrators in the creation, distribution, and deployment of migration packages to different environments. Migration Resource endpoints retrieve the data source entities that are required for successful migration. Oracle CPQ supports retrieving all migration resources, migration resources within a defined Oracle CPQ category, and specific migration resources from within a category.

In order for the following Migration Package and Migration Resource REST API endpoints to be available in the Oracle CPQ Interface Catalog, log a Service Request on My Oracle Support.

Migration Package

Create a Migration Package

Use this endpoint to create a new migration package.

Endpoint: /rest/v14/migrationPackages

Method: POST

Update a Migration Package

Use this endpoint to update the migration package properties of an existing migration package. Only the specified properties are added or updated using the PATCH method.

Endpoint: /rest/v14/migrationPackages/{id}

Method: PATCH

Delete a Migration Package

Use this endpoint to delete a migration package.

Endpoint: /rest/v14/migrationPackages/{id}

Method: DELETE

Get All Migration Package Content

Use this endpoint to retrieve all migration resources included in an existing package.

Endpoint: /rest/v14/migrationPackages/{id}/contents

Method: GET

Get Migration Package Category Content

Use this endpoint to retrieve all migration resources for a specific category included in an existing migration package.

Endpoint: /rest/v14/migrationPackages/{id}/contents/{category}

Method: GET

Get Migration Package Resource Low-level Details

Use this endpoint to retrieve low-level details of a migration resource within a specific category of a migration package.

Endpoint: /rest/v14/migrationPackages/{id}/contents/{category}/{variableName}

Method: GET

Update Migration Package Content

Use this endpoint to update all content within a migration package. Using the PUT method replaces the entire package contents with new package contents.

Endpoint: /rest/v14/migrationPackages/{id}/contents

Method: PUT

Update Migration Package Resource Low-level Details

Use this endpoint to update low-level details of a migration resource within a specific category of a migration package. Using the PUT method replaces the entire package contents with new package contents.

Endpoint: /rest/v14/migrationPackages/{id}/contents/{category}/{variableName}

Method: PUT

Version a Migration Package

Use this endpoint to version an existing migration package. The new version copies the name, properties and all contents of the original version and is given a new higher version number of the existing migration package and a new identifier.

Endpoint: /rest/v14/migrationPackages/{id}/actions/newVersion

Method: POST

Migrate Package

Use this endpoint to migrate a migration package that has been uploaded to the server.

Endpoint: /rest/v14/migrationPackages/actions/migrate

Method: POST

Upload ZIP File for a Migration Package

Use this endpoint to upload a migration package ZIP file to the server.

Endpoint: /rest/v14/migrationPackages/actions/uploadPackage

Method: POST

Migration Resources

Get All Migration Resources

Use this endpoint to retrieve all migration resources, grouped by category.

Endpoint: /rest/v14/migrationResources

Method: GET

Get Category Migration Resources

Use this endpoint to return all migration resources for a specific category.

Endpoint: /rest/v14/migrationResources/{category}

Method: GET

Get Migration Resource Low-level Details

Use this endpoint to retrieve low-level details of a migration resource within a specific category.

Endpoint: /rest/v14/migrationResources/{category}/{variableName}

Method: GET

Steps to Enable

To enable this feature, you need to log a Service Request (SR) on My Oracle Support.

Tips And Considerations

Once this feature is enabled by logging a Service Request on My Oracle Support, the Oracle 23C migration package and migration resources endpoints are 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.

Parts REST API Enhancements

Oracle CPQ 23C updates the Parts REST APIs to include the variable name of the root BOM item, part configurable flag, and product status.

The Parts REST API updates provide information used to support Product Launch.

Steps to Enable

Parts Setup REST API Enhancements

Oracle CPQ 23C introduces the Update/Insert action for the Parts Setup REST API.

Update/Insert Parts

Use this endpoint to update or insert CPQ parts. If an included Part Number already exists, the existing part will be updated based on the request payload. Otherwise, a new Part will be added.

Endpoint: /rest/v14/partSetups/actions/upsertParts
Method: POST

This action will enable customers to update or create CPQ Parts using REST API web services.

Steps to Enable

Pricing Administration REST API Enhancements

Oracle CPQ 23C introduces the following endpoints to support pricing lookups for charges:

Add a Pricing Lookup Type

Use this endpoint to add a pricing lookup type.

Endpoint: /rest/v14/pricingSetup/pricingLookups
Method: POST

Add a Pricing Lookup Value

Use this endpoint to add a pricing lookup value.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}/lookupValues
Method: POST

Delete a Pricing Lookup Type

Use this endpoint to delete the specified pricing lookup type.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}
Method: DELETE

Delete a Pricing Lookup Value

Use this endpoint to delete the specified pricing lookup value.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}/lookupValues
Method: DELETE

Get a Pricing Lookup Type

Use this endpoint to retrieve the specified pricing lookup type.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}
Method: GET

Get a Pricing Lookup Value

Use this endpoint to retrieve the specified pricing lookup value.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}/lookupValues
Method: GET

Get All Pricing Lookup Types

Use this endpoint to retrieve all pricing lookup types.

Endpoint: /rest/v14/pricingSetup/pricingLookups
Method: GET

Get All Pricing Lookup Values

Use this endpoint to retrieve all pricing lookup values for the specified lookup type.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}/lookupValues
Method: GET

Update a Pricing Lookup Type

Use this endpoint to update the specified pricing lookup type.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}
Method: PATCH

Update a Pricing Lookup Value

Use this endpoint to update the specified pricing lookup value.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}/lookupValues
Method: PATCH

Update Pricing Lookup Types

Use this endpoint to update pricing lookup types.

Endpoint: /rest/v14/pricingSetup/pricingLookups
Method: PATCH

Update Pricing Lookup Values

Use this endpoint to update pricing lookup values.

Endpoint: /rest/v14/pricingSetup/pricingLookups/{lookupTypeVarName}/lookupValues
Method: PATCH

Oracle CPQ now supports the ability to automate the creation, reading, updating and deletion of Pricing Lookup Types and Values. Customers can now automate the synchronization of updates to Pricing Lookup menus and menu values.

Steps to Enable

SCIM-Compliant User Management REST API

The System for Cross-domain Identity Management (SCIM) specification is an open standard that facilitates managing user identities across cloud-based applications and services. Oracle CPQ 23C adds a PATCH method to the SCIM-Compliant User Management REST API which allows administrators to update a user record instead of fully replacing the entire record.

Administrators need to determine the best method for adding, updating, or removing migration package contents. The differences in the SCIM-Compliant User Management PUT and PATCH methods are as follows:

PUT – replaces the entire set of values with an entire new set of values which include the added and/or updated resource. You may want to use this method when there are many changes to the values. If there is a validation failure with any field, the request fails and the content remains unchanged.
PATCH – adds or updates resource within the existing set of values. You may to use this method when the sequence of resource changes is key to the content result and when error checking for each modification is desired.

Add, Update, or Remove User Information

Use this endpoint to perform an operation to add user information, update existing user information or remove existing user information for a specified user. The endpoint supports a single operation request or multiple operation requests performed sequentially.

Endpoint: /rest/v14/scim/users/{id}
Method: PATCH

SCIM-compliant REST APIs simplifies user provisioning and management of user-related information across Oracle cloud-based applications.

Steps to Enable

Tips And Considerations

Each PATCH method operation represents a single action to be applied to the SCIM resource specified by the request URI. Operations are applied sequentially as they appear in the array. Each operation in the sequence is applied to the target resource; the resulting resource becomes the target of the next operation. Evaluation continues until all operations are successfully applied or until an error condition is encountered.
A PATCH method request, regardless of the number of operations included, is treated as a single request. If a single operation within the request encounters an error condition, the original user information is restored and an error message indicating the request failed is returned.
Mandatory field values cannot be removed. Mandatory fields can be added or replaced using this endpoint.
When performing an add, update, or replace operation for a field value, the permission setting for that field and if the field is mandatory or not, determines if the operation is allowed. Permission settings are: Read/Write; Write Only; or Read Only. Refer to the Oracle CPQ and Core User Schema Attribute Mapping in the Oracle CPQ Administration Online Help for detailed information.

IMPORTANT Actions and Considerations

PRE-UPGRADE CONSIDERATIONS

Modifications to Known Functionality

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

Oracle CPQ Feature	Description
Fusion Order Management Integration	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 has 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.
Pricing	Beginning in Oracle CPQ 23B, pricing settings are no longer set via General Site Options or Commerce Settings. Pricing settings are now consolidated in the Pricing Portal Pricing Options. Navigation links are provided from the prior settings locations to direct administrators to the Pricing Options page.

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	We are announcing 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.
Legacy Commerce UI	21C	24A	In Oracle CPQ 21C, we announced the deprecation of Legacy Commerce Transaction UI. The end of life and removal of this functionality is Oracle CPQ 24A. We introduced JET Responsive UI for Commerce in Oracle CPQ 18C, and after years of evolution and production experience, our customers are experiencing the benefits of the new JET Responsive UI for both Commerce and Configuration. The majority of Oracle CPQ customers have successfully made the complete transition to the JET UI. Moving forward, we are focusing our development efforts on enhancing the JET Responsive UI to improve the overall user experience. We’re announcing these changes to give our customers early visibility and the opportunity to prepare for this update. If your Oracle CPQ implementation still uses Legacy Commerce UI, we encourage you to start preparing for the transition to the JET UI. For more information on enabling JET Commerce UI, visit the Oracle CPQ Administration Online Help JET Transaction UI topic or watch the CPQ JET UI: Best Practices and Customization Video.
Legacy Configuration UI	21C	24A	In Oracle CPQ 21C, we announced the deprecation of Legacy Configuration UI. The end of life and removal of this functionality is Oracle CPQ 24A. We introduced JET Responsive UI for Configuration in Oracle CPQ 19B, and after years of evolution and production experience, our customers are experiencing the benefits of the new JET Responsive UI for both Commerce and Configuration. The majority of Oracle CPQ customers have successfully made the complete transition to the JET UI. Moving forward, we are focusing our development efforts on enhancing the JET Responsive UI to improve the overall user experience. We’re announcing these changes to give our customers early visibility and the opportunity to prepare for this update. If your Oracle CPQ implementation still uses Legacy Configuration UI, we encourage you to start preparing for the transition to the JET UI. For more information on enabling JET Configuration UI, visit the Oracle CPQ Administration Online Help JET Configuration UI topic or watch the CPQ JET UI: Best Practices and Customization Video.
Legacy Commerce and Configuration Mobile Layouts	21C	24A	In Oracle CPQ 21C, we announced the deprecation of Legacy Commerce and Configuration Mobile Layouts. The end of life and removal of this functionality is Oracle CPQ 24A. Legacy Mobile Layouts were built to provide an adaptive experience for quoting and configuring on mobile devices. The JET Responsive UI provides a clean, streamlined user experience that is fully responsive across desktop, tablet, and phone devices, eliminating the need for the administration of separate UI Layouts for desktop and mobile users. If your Oracle CPQ implementation has legacy mobile layouts enabled, we advise you to make a transition to JET Responsive UI to provide an optimal experience for your end users. For more information on enabling the JET UI responsive experience, refer to the Oracle CPQ Administration Online Help. We’re announcing these changes to give our customers early visibility and the opportunity to prepare for this update. If your Oracle CPQ implementation still uses Legacy Configuration UI, we encourage you to start preparing for the transition to the JET UI. For more information on enabling JET Configuration UI, visit the Oracle CPQ Administration Online Help JET Responsive UI topic.
Legacy Rich Text Editor	21C	24A	In Oracle CPQ 21C, we are announced the deprecation of the Legacy Rich Text Editor. The end of life and removal of this functionality is Oracle CPQ 24A. Oracle CPQ occasionally disables old areas of the product that have been replaced by newer and improved versions. As previously announced in CPQ 20C, we introduced a new inline editor for rich-text editable attributes (RTE). The new JET editor includes more text formatting options than the legacy editor. Features include undo/redo, images, links, table tools, and functions with the browser's native spell-check. We are also working on adding user-specific template support to the new editor before retiring the legacy editor from the product.
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 23C
"Minor update" = Update 23C 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 23C, refer to the Oracle CPQ 23C 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 23C. 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 23C 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 23B 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 23B 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	July 7 and 8	August 4 and 5	August 18 and 19
B	July 7 and 8 August 4 and 5	September 1 and 2	September 15 and 16
C	August 4 and 5 September 1 and 2	October 6 and 7	October 20 and 21

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 113.x
Mozilla Firefox 112.x
Microsoft Edge 112.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 23C.

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.