Overview
Integrating Oracle Configure, Price, and Quote (CPQ) and Oracle CX Sales, streamlines the entire opportunity-to-quote-to-order process. Transaction data is passed seamlessly between the two applications, ensuring accuracy and allowing Oracle CX Sales users to take advantage of the on‑demand configuration, pricing, and quoting capabilities of CPQ.
CPQ-Oracle CX Sales integration enables sales representatives to work on opportunities, create quotes with accurate prices, and send proposals to customers. The integration enables you to manage quotes and orders from accounts and opportunities, finalize pricing and proposals in CPQ, update opportunity revenue with quote lines for accurate forecasting, and access proposal documents from within Oracle CX Sales.
Refer to the following documents for more information focused on Oracle CX Sales to Oracle CPQ integration implementation.
Product Workbench
The Product Workbench (previously known as the Product Launch UI) is for Oracle CPQ sites integrated with Oracle CX Sales. For more information, refer to Product Workbench.
Enhancements
Custom Filter for REST – Export Lines
The Custom line-level filter for the REST – Export Lines Commerce integration provides a custom line type filter on each integration. When this type is selected, the administrator must additionally specify a line-level attribute which indicates whether that line should be included or not included in the export. This attribute can be of type Boolean or text and if the value is 'true' then the line is included in the export. If the attribute value is anything other than 'true', the line-level attribute is not included in the export. Refer to Commerce Integrations for more information.
Custom filters give administrators a more flexible option for how to reduce the number of lines synchronized to the CRM, for example Oracle CX Sales. By limiting the number of lines synchronized based on the upstream business requirements, Commerce Actions using these integrations can perform better.
Oracle Fusion CRM Integration Added to Integration Center
A new Fusion Customer Relationship Management (CRM) integration type is added to the Oracle CPQ Integration Center. This feature streamlines the set up and management of the connection between Oracle CPQ and Oracle Fusion Sales (CX Sales). This new interface allows administrators to directly configure the details of their Fusion environment without the assistance of customer support or cloud operations. New and existing Oracle Fusion Sales (CX Sales) Commerce Integrations will use these properties when making Web Service calls to the Fusion site. Refer to Oracle Fusion CRM Integration for more information.
If you have debug-level performance logging enabled for a REST Integration, the REST Request and Response payload information is now included in the bm.log. If you don't have debug-level logging enabled, submit a service request on My Oracle Support to analyze potential site performance impact for additional logging.
The following is a sample bm.log report.
22 Nov 2022 08:31:32,066 [DEBUG] com.bm.xchange.rest.client.JerseyClient.addQueryParams(JerseyClient.java:458) - => urlAddress: https://sitename.com/crmRestApi/resources/11.13.18.05/salesOrders
22 Nov 2022 08:31:32,496 [DEBUG] com.bm.xchange.rest.client.JerseyClient.invokePost(JerseyClient.java:404) - => restRequest: {"Owner":"Super User","ContractStartDate":null,"ExternalHostName":"cpqqa130","ExternalProcessName":"oraclecpqo","QuoteTypeCategory":"NEW","Name":"11/22 lcopty","TotalRecurringRevenue":0,"CurrencyCode":"USD","TotalMonthlyRecurringRevenue":0,"TotalUsageRevenue":0,"RenewalProcess":null,"ExternalReferenceNumber":"36881588","ExternalQuoteNumber":"CPQ-297","WinStatusCode":"ZCA_IN_PROGRESS","Status":"CREATED","ExternalSystemReferenceCode":"OracleCPQ","TotalNonRecurringRevenue":30080,"ContractEndDate":null,"TotalMonthlyUsageRevenue":0,"VersionNumber":1,"OptyId":300100557968231,"ExpirationDate":null,"ProposalExistFlag":false,"OrderTotal":30080,"SoldCustomerPartyId":100000019135058}
22 Nov 2022 08:31:32,497 [DEBUG] com.bm.xchange.rest.client.JerseyClient.getResponseModel(JerseyClient.java:491) - <= restResponse Header=Keep-Alive:[timeout=61, max=100]
X-ORACLE-DMS-ECID:[005vWfzn4sqBp2Q5Ib8Dyf0007Ce0004jq]
X-Content-Type-Options:[nosniff]
Connection:[Keep-Alive]
X-ORACLE-DMS-RID:[0:5]
Date:[Tue, 22 Nov 2022 08:31:32 GMT]
X-Frame-Options:[SAMEORIGIN]
Referrer-Policy:[same-origin]
Cache-Control:[no-cache, no-store, must-revalidate]
ETag:["ACED0005737200136A6176612E7574696C2E41727261794C6973747881D21D99C7619D03000149000473697A65787000000001770400000001737200116A6176612E6C616E672E496E746567657212E2A0A4F781873802000149000576616C7565787200106A6176612E6C616E672E4E756D62657286AC951D0B94E08B02000078700000000178"]
Vary:[Accept-Encoding,User-Agent]
X-XSS-Protection:[1; mode=block]
Content-Length:[4426]
Content-Language:[en]
Link:[https://sitename.oracle.com:443/crmRestApi/resources/11.13.18.05/salesOrders/300100557981972;rel="self";kind="item";name="salesOrders"]
Content-Type:[application/json]
REST-Framework-Version:[1]
Location:[https://sitename.oracle.com:443/crmRestApi/resources/11.13.18.05/salesOrders/300100557981972]
22 Nov 2022 08:31:32,498 [DEBUG] com.bm.xchange.rest.client.JerseyClient.getResponseModel(JerseyClient.java:492) - <= restResponse: {
"CreatedBy" : "sales_user",
"CreationDate" : "2022-11-22T08:31:32+00:00",
"CurrencyCode" : "USD",
Beginning in Oracle CPQ 22C, processing of GZIP compression headers is supported for Oracle CPQ REST Integrations with Oracle CX Sales. Customers who have enabled GZIP to compress HTTP content on Oracle CX Sales will notice a seamless integration, with better error/response processing on Oracle CPQ side.
Detect Deleted CX Attributes in Imported Revenue Line Conditional Mappings
In prior releases administrators didn't have any indication when an attribute which is mapped in CPQ has been removed from Oracle CX Sales, which could result in errors when the integration is triggered. Beginning in Oracle CPQ 22B, the Attribute Mapping page will highlight missing attributes that are used in mappings as well in conditions and provide an error message when the administrator double clicks on the highlighted attribute. Informing CPQ administrators of missing Oracle CX Sales attributes prevents errors when an integration is run.
For more information refer to, Missing Oracle CX Sales Attributes in Imported Revenue Line Conditional Mappings.
Enhanced Error Messages for Imported Config Attribute Values
In prior releases, error messages for invalid Config Attribute Values JSON data only displayed one error at a time. If there were multiple errors, administrators had to fix the displayed error, and attempt to run the integration again, before seeing the next error. Beginning in Oracle CPQ 22B, CPQ provides detailed error messages for all errors when the default configuration attribute values from a Oracle CX Sales Revenue Line Import integration cannot be processed. The enhanced error messages help administrators identify the Product or Product Group with invalid values in the Config Attribute Values JSON data.
Oracle CPQ 22B also expands the sales reference application to provide predefined conditional mapping for the CPQ Model Name attribute in the Oracle CX Sales Revenue Line Import REST Integration to enable the enhanced error messages for imported Config attribute values.
For more information refer to, REST Import Quote Lines (Response Mapping).
Notes:
- The Commerce REST Import Revenue Lines integration is provided in the Oracle CPQ 22B Sales RefApp image for new sites.
- A 22B Sales RefApp migration package and implementation instructions will be provided on for existing customers.
Sort and Reorder Mapped Rows on the Commerce Integration Attribute Mapping Page
Oracle CPQ 22B provides the ability to sort and reorder mapped rows on the Commerce Integration Attribute Mapping page. The mapped rows can be sorted by the CPQ Attribute or the Mapped Attribute column in ascending or descending order. Sorting rows by the CPQ Attribute allows administrators to easily identify all attributes that are conditionally mapped to the same target attribute.
For more information refer to, Sort and Reorder Mapped Attribute Rows.
The following Oracle CX Sales Integration features are available in Oracle CPQ 22A.
Import Revenue Lines from Oracle CX Sales
Oracle CPQ 22A expands the REST – Import Commerce integration type to import transaction line level data into CPQ (i.e. Import Oracle CX Sales Revenue Lines into a CPQ transaction). Upon creation of a quote, CPQ will import the revenue lines from Oracle CX Sales and create corresponding transaction lines in CPQ. This feature completes the 'round trip' integration of transaction and revenue lines for integrations with Oracle CX Sales. End users no longer need to re-enter Oracle CX Sales revenue lines into the CPQ transaction.Oracle CX Sales revenue lines can reference product groups or products.
Oracle CX Sales product group revenue lines are imported as CPQ models and product revenue lines can be imported as CPQ models or parts. When a Oracle CX Sales revenue line is imported as a CPQ model, the transaction line will display the unconfigured model icon indicating that the line requires configuration.
The enhanced REST – Import Commerce integration also allows administrators to define query parameters for imports. This enables CPQ to filter out revenue lines that are not exposed in the Oracle CX Sales UI and to exclude those that instantiate sales splits and revenue schedule entries.
For more information, refer to Add a REST – Import Integration.
Conditional Mapping for Commerce REST Integrations
Beginning in Oracle CPQ 22A administrators can define conditional logic for the import of sub. Commerce REST integration mappings. This feature supports the import of revenue lines from Oracle Sales to create CPQ quote lines for both configured and unconfigured products by referencing model attributes from revenue line products or product groups.
For more information, refer to Conditional Mapping for REST Integrations
Default Configuration Attributes for Import Revenue Lines Integration
Oracle CPQ 22A allows Oracle CX Sales to provide configuration defaults during import for revenue lines that reference CPQ models. The default values are applied in the Configuration UI when a sales user initially configures an imported model-type transaction line.
For more information, refer to Add a REST – Import Integration.
Derive Revenue Category For All Asset-Based Ordering Modifications
Oracle CPQ 22A provides the out-of-the-box logic to derive the revenue category for all asset modification and subscription amendment use cases. This functionality supports main and sub-document revenue categories as well as additional customer-defined revenue categories. The CPQ 22A Sales RefApp provides the out-of-the-box logic to derive the revenue category for all asset modification and subscription amendment use cases.
Note: If customers apply the 21D Subscription Management package on a site with the 22A Sales RefApp, the formula setting for the revenueCategory_l attribute on save action will be lost. Customers have to manually enable the _revenueCategory_l formula on the save action for the revenueCategory_l attribute after applying the Subscription Management package.
Extensibility for Revenue Category
Oracle CPQ 21C introduced a Revenue Category system attribute for Commerce main documents. A new Revenue Category attribute was also introduced for Commerce sub-documents in the Revenue Attribute Set. Both of these attributes were non-editable and contained three menu options. Oracle CPQ 22A allows administrators to rename the default options and add, edit, and delete custom revenue category options.
Standard Oracle CX Sales Revenue Line Import REST Integration
Oracle CPQ 22A also expands the reference application to provide predefined sub-document attribute mappings for REST-based integrations. The CPQ 22A Sales RefApp is available in a migration package for existing customers or with the out-of-the-box application for new customers.
For more information, refer to REST Import Quote Lines (Response Mapping)
Oracle CPQ 21B introduces new features that support Oracle’s goal to provide superior cross-application solutions to customers. The new features allow synchronization of Oracle CPQ transactions with Oracle CX Sales to enable the following valuable operations.
- Support different types of pricing and revenue (e.g. recurring, usage, one time) in a unified sales and quoting flow.
- View the aggregated revenues for an entire model.
- Search and find quotes and quote lines (i.e. products) and drill down into the quote from within Oracle CX Sales Workbench.
- Seamlessly make any version of a quote active from within the Oracle CX Sales Opportunity.
- Retain opportunity sales splits on the revenue line throughout the quote lifecycle.
- Unify reporting and analysis of opportunities, quotes, and products.
For detailed integration instructions, refer to Integrating CX Sales with Oracle CPQ.
REST - Export Integrations for Oracle CX Sales
Used to export transaction level data from CPQ to Oracle CX Sales (e.g. Export the CPQ transaction to Oracle CX Sales). The REST-based integration updates existing Oracle CX Sales quotes and replaces the existing SOAP integrations that were used to delete and then replace Oracle CX Sales revenue lines.
For more information, refer to REST - Export Integrations for Oracle CX Sales.
REST - Import Integrations for Oracle CX Sales
Used to import transaction level data into CPQ (i.e. Import a Oracle CX Sales opportunity into a CPQ transaction). This REST-based integration replaces the existing SOAP import integration to significantly improve the administrative experience.
For more information, refer to Add a REST – Import Integration.
Enhanced Attributes and Attribute Mappings for Oracle CX Sales
Oracle CPQ 21B expands predefined attributes and attribute mappings in CPQ Reference Application (RefApp). The integration of common price types and price periods provide a unified sales and quoting flow for different types of pricing and revenue. The prolapse attributes and calculations enable Oracle CX Sales users to view aggregated revenues for an entire model. Additionally, CPQ 21B expands the attribute types available for mapping and provides access to system attributes.
The CPQ 21B Sales RefApp is available in a migration package for existing customers or with the out-of-the-box application for new customers.
Common Price Types and Price Periods
Integrated common price types and price periods (i.e. recurrence frequency) allow Oracle CX Sales users to forecast revenues for all types of pricing. Price types support recurring, one-time, and usage pricing. Price periods support the invoicing frequency and length of the contract for recurring and usage price types. The following image shows a CPQ transaction highlighting the following pricing attributes:
-
Price Types can be One Time, Recurring, or Usage.
-
Periodicity frequency of Per Month or Per Year, customers can customize to add other frequencies
-
Contract Periods is used to specify how many times the charge will occur.
To view a list of all attributes in the 21B CPQ Sales RefApp, refer to Access Information for Your CPQ Site Reference Application.
Rollup Attributes and Calculations
The CPQ 21B reference application and associated 21B migration package include attributes and calculations to provide aggregated revenue values for the root model that includes revenue values for all child items. Aggregate revenue values are calculated for non-recurring, recurring, and usage price types for the duration of the contract, with both ‘summable’ (summing these values for all lines yields the total for the quote) and 'prolapse' values. 'Rollup' values are equal to the standard price values for most lines, but will hold the summed or rolled up value for root model lines.
To view a list of all attributes with associated aggregation functions in the 21B CPQ Sales RefApp, refer to Access Information for Your CPQ Site Reference Application.
Oracle CPQ 21B introduced new system attributes. The following system attributes are available for models in the Product Definition:
-
Partner Part Id (
_bm_model_partner_part_id) -
Partner Organization Id (
_bm_model_partner_organization_id)
The following system attributes were added to the model attribute set for commerce sub-documents.
-
Model Part Number (
_partner_part_id) -
Item Organization ID (
_partner_inventory_organization_ID)
New Variables for Request Attribute Mapping
The new system attributes, Commerce Dynamic Menu attributes, the Version Attribute set, Transaction Total, and Customer ID are now supported for mapping in the Attribute Mapping UI. Oracle CPQ 21B also made System Variables available for Request attribute mapping.
Oracle CPQ 21A introduces the REST – Export Lines Commerce integration type to replicate and synchronize CPQ quote lines to Oracle CX Sales. In prior integrations quote line data did not exist on Oracle CX Sales, so users had to open one or more transactions to retrieve quote line information. This feature enables Oracle CX Sales users to search across multiple quotes to quickly retrieve the quote line data. In CPQ 21A, quote lines are synced back to Oracle CX Sales to provide visibility of the quote lines within Oracle CX Sales 21A. Additionally, the user-friendly attribute mapping UI allows administrators to drag and drop attributes to define integration mappings and eliminates the need to understand or edit XSL syntax. This integration supports the ability to integrate all quote lines, part lines, or root lines on an associated Commerce action. Root lines are models or parts without parent items and they are used to forecast revenue at a model level instead of a part level. Root line integration is useful for customers with large quotes to prevent performance issues when synchronizing a large number of quote lines.
The Quote Lines integration for Oracle CX Sales provides an efficient method to synchronize Oracle CX Sales quote lines to CPQ transaction lines to enable extensive search and reporting capabilities in Oracle CX Sales. The new searches provide data-driven information to support multiple company roles:
- Sales representatives can use this information to identify sales opportunities, direct a sales approach, and aid in discount decisions. They can also use this information to prompt customer follow-ups for status, product issues, availability issues, and renewals.
- Managers can evaluate appropriate discounts, measure product promotion marketing campaign results, focus sales team efforts, understand pricing sensitivity, and prepare sales reports.
- Customer service representatives can view order summaries and status to respond to customer inquiries.
- Site administrators can verify that integrations are working correctly.
Oracle CPQ 21A also introduces a new Attribute Mapping page that allows administrators to customize their Oracle CX Sales integration without the use of XSL.
Oracle Oracle CX Sales - Oracle CPQ integration is implemented as a point-to-point integration.
For more information on the Oracle CX Sales - Oracle CPQ point-to-point integration, refer to Oracle CPQ Commerce Integrations.
Administration
Creating and Viewing Proposals
For Proposal integration to function, you must configure Oracle CPQ to save the proposal output to a File Attachment attribute. This attribute is used in the integration between Oracle CX Sales and CPQ.
Saving Proposal Output to a File Attachment Attribute
- Navigate to the Admin home page.
-
Click Process Definition under Commerce and Documents.
-
Select Document from the applicable process Navigation drop-down, and then click List.
-
Select Actions from the main document Navigation drop-down, and then click List.
-
Locate a Print action within the Action List page and click the name of the action.
The Type column will show Print for print actions. - Navigate to the General tab within the Admin Action page.
-
Locate the field Save Document Upon Printing?.
The default setting is No.
-
To save the document without requiring any action on the part of the sales user.
-
Select Save - Automatically, then
-
Select a File Attachment Attribute from the drop-down.
-
-
To produce a pop-up dialog that gives the sales user the option to save the document.
-
Select Save - User Confirmation, then
-
Select a File Attachment Attribute from the drop-down.
-
The Print action can only be linked to one Quote-level File Attachment Attribute.
If a File Attachment attribute is linked to a Print action, the administrator can select whether the sales user can override the currently linked File Attachment attribute. Refer to Control Ability to Override the File Attachment Attribute, for more information.
-
Control Ability to Override the File Attachment Attribute
Admins can configure whether a sales user can override the currently linked File Attachment attribute, if that File Attachment attribute is linked to a Print action.
- Navigate to the Admin home page.
-
Click Process Definition under Commerce and Documents.
-
Select Documents from the applicable process Navigation drop-down, and then click List
-
Select Attributes from the main document Navigation drop-down, and then click List.
-
Locate the File Attachment attribute within the Attribute List page and click the name of the attribute.
The Type column will show File Attachment for File Attachment attributes. - Navigate to the General tab within the File Attachment Attribute Editor page.
-
Locate the field Show User Browse Button
- If the checkbox is selected, a File browse box will appear so the sales user can override the selected File Attachment Attribute.
-
If the checkbox is not selected, no File browse box will appear.
Print actions can only be saved at the Quote document level.
In Oracle CX Sales, you can generate a proposal and view a proposal by downloading it from the Quote or Opportunity.
In CPQ, you can generate a proposal and view a proposal by clicking the document's URL.
- If the admin has enabled the Show User Browse Button, the sales user can override the currently attached document by uploading a new file in the File Browse dialog box.
- If the admin has not enabled the Show User Browse Button, no File Browse dialog box will be available to override the current document selection.
-
When saving a document or proposal, the user must click a Modify action (such as Refresh, Save, or Print) for the stored proposal to appear in the Quote.
-
Otherwise, the proposal will still be saved, but will not appear on the Quote.
-
A Get Proposal REST API provides the proposal via a URL. The file is delivered as an "Export" Integration XSL Type.
-
For more information, refer to Integrating CX Sales with Oracle CPQ.
-
Quotes can be printed from within Oracle CPQ and Oracle CX Sales.
-
A saved proposal can be deleted.
Clicking Create Quote Version copies the current quote and applies an incremental version number to the new Quote version.
The main difference between creating a new version of a Quote (versioning) and copying a Quote is that versioning creates multiple version of the same Quote, while copying creates two distinct Quotes.
Versioning is ideal for making small changes when negotiating with customers. For example, two variations of a Quote, each containing different levels of discounting, could be created in advance. You will only want one Quote at the end of the negotiations, so you should create two versions of the Quote.
Once the customer makes their selection, the rest of the quoting process can be completed quickly and efficiently because that version of the Quote already exists.
The action type, Version, can be associated with Quote-level Attributes. This allows sales users to apply versions to Quotes from within Oracle CPQ or Oracle CX Sales.
-
Quote Version Number: Increments accordingly for version chain.
If a Quote is copied, the system restarts the Version number. The Quote Version number is created automatically and is numbered in chronological order from when the Quote was versioned.
Version numbering structure:
If a Quote is versioned from within Oracle CX Sales, but is not saved, the next versioned Quote will be numbered in chronological order picking up after the unsaved quote.
For example, if the unsaved Quote Version was “v8” the next Version number would be “v9”, even though “v8” would be missing.
-
Parent Transaction ID: captures the Transaction ID of the quote used to version.
The Parent Transaction ID is populated automatically upon clicking the Version action button.
- Navigate to the Admin home page.
-
Click Process Definition under Commerce and Documents.
-
Select Documents for the applicable process Navigation drop-down, and then click List.
-
Select Actions from the main document Navigation drop-down, and then click List.
-
Click Add.
-
Add a Label and Variable Name.
The Variable Name field populates automatically. 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.
- Select Version from the Action Type drop-down.
-
Click Add.
-
Navigate to the newly created Target Action field on the General tab.
This allows the Version action to be linked to another Modify action (such as Save); the Version action without a Target Action link acts simply as a Copy action.
The Version action does not have a Modify tab and is not expected to save the original Quote. -
Link the Version action to a Target Action.
It is highly recommend that the Version action is linked to another Modify action.
Creating a new Modify action that handles only the Target action, which re-initializes certain Attributes (Buy Side ID, Quote Integration Attributes, and Product Integration Attributes) provides the best results.
- Click Apply.
-
Click Update.
Only one Version action can be actively linked to an Oracle CX Sales set up Configuration.
- A sales user can version a Quote from within Oracle CX Sales by clicking Create Quote Version within the quote row.
- A Parent Transaction ID is automatically generated so the user can identify the origin of their version.
Once in the Quotes Manager, users can go back versions and create new versions from older ones.
Version numbers will continue to be identified in chronological order with the Parent Transaction ID as their origin identifier, as seen in the following graphic.
- Versions will carry over Approval status from the point at which the Create Quote Version button was clicked.
- When the action is deleted, related version number Attributes and Parent Transaction IDs are also deleted.
-
There can be an unlimited number of Quote Versions linked to an Oracle CX Sales opportunity.
If a user makes changes on the user interface and clicks the Version action button without saving the original Quote, the user interface changes will not be saved in the original Quote data. The newly created Quote retains the changes, but the original Quote will not.
The Fusion Product Model is a component of the Oracle CX Sales and Fusion PIM (Product Information Management).
The Product Model Endpoint URL is entered on the Oracle CPQ side. Either Oracle CPQ or the Fusion Product Model can act as the Item Master.
- Navigate to the Admin home page.
-
Click Catalog Definition in the Products section.
-
Select Product Families from the Navigation drop-down, and then click List.
-
Select Integrations from the applicable product family Navigation drop-down, and then click List.
Example Product Model Endpoint URL:
https://xxx.xx.xxx/egpProducts/ItemServiceV2
-
An Export is performed when the Item Master is set to
Oracle CPQ.
This exports parts to the Product Model server.Exports must be done first on the Oracle CPQ side before sales users can interact with the integration. -
An Import is performed when the Item Master is set to
Partner.
Performing an Import is very similar to performing an Export.Standard XSLs are provided for Product Model integration export and import.
Once the Fusion Product Model Integration has been performed by an admin, Oracle CPQ Line Items can be synced seamlessly with Oracle CX Sales opportunity revenue items.
Single Sign-On Logout Settings
While not required fields, it is best practice to define a SAML Logout URL and a SAML Single Logout Endpoint on the Single Sign-On Settings page (Admin > Single Sign-On) when using federated authentication for SSO in a CPQ-Oracle CX Sales integration.
| Property | Description |
|---|---|
| SAML Logout URL | The destination URL that a user will be redirected to upon logging out of CPQ. If blank, users will not be redirected after logging out of Oracle CPQ and will land on the Oracle CPQ login screen. |
| SAML Single Logout Endpoint | The logout API endpoint of the IDP system (OSC) that will start the logout of the user in the IDP system (Oracle CX Sales) when the user is logged out of CPQ. If blank, the user will not be logged out of the IDP system (Oracle CX Sales) when he/she is logged out of CPQ. |
See the Single Sign-On (SSO) topic for more information on Single Sign-On options.
Oracle CX Sales as Identity Provider (IdP)
For setting up Oracle CX Sales as Identity Provider, you need to use Identity Cloud Service (IDCS) as follows:
Oracle CX Sales (IdP) > IDCS (SP, IdP) > CPQ (SP)
By default, every Oracle CX Sales environment is now configured as an IdP to an IDCS instance as (SP). Within IDCS, it is mandatory to start the sync with the IDCS Connector for FA. The documentation is referenced below and is in Chapter Configure Provisioning and Synchronization / Enable Provisioning and Synchronization / Enable Synchronization
When integrating with CPQ, IDCS should be the IdP for CPQ as SP. Instructions to configure this can be found in IDCS SSO Setup for CPQ.
See the Single Sign-On (SSO) topic for more information on Single Sign-On options.
Notes
Notes:
-
The Target action is a Quote-level action. The Target action can be any Modify action.
-
Users are transferred between Oracle CPQ and Oracle CX Sales using Single Sign-On. For more information, see Single Sign-On (SSO).
-
Oracle CX Sales integrations, we recommend launching the CPQ page in an iFrame and setting the Occupy entire window when the site is inside a frame General Site option to No.
If you need to launch CPQ in full screen mode, there are additional steps that need to be taken. Refer to Integrating CX Sales with Oracle CPQ for more information.
