CPQ Salesforce Install Guide Sept2022
CPQ Salesforce Install Guide Sept2022
Salesforce
Installation and Setup Guide
September 2022
Copyright © 2022, Oracle and/or its affiliates
TABLE OF CONTENTS
Table of Contents .......................................................................................................................................................................... 1
Revision History............................................................................................................................................................................. 3
Introduction .................................................................................................................................................................................... 5
Prerequisites ................................................................................................................................................................................................. 6
Check the Oracle CPQ and Reference Application Versions................................................................................................................ 7
Locate the Oracle CPQ Version Info............................................................................................................................................................ 7
Locate the Reference Application Information ........................................................................................................................................ 8
Enable My Domain ....................................................................................................................................................................................... 9
My Oracle Support ....................................................................................................................................................................................... 9
Register in My Oracle Support ..................................................................................................................................................................... 9
Log an Oracle CPQ Connector for Salesforce Service Request ............................................................................................................ 9
Installation ..................................................................................................................................................................................... 11
Authentication ............................................................................................................................................................................. 12
Authorize an Oracle CPQ Site within Salesforce ................................................................................................................................... 12
Register the Oracle CPQ Site as a Remote Site ....................................................................................................................................... 12
Add CPQ Environment To CORS Allow List ............................................................................................................................................. 13
Add CPQ Environment to CSP Allow List................................................................................................................................................. 14
Create a Certificate .........................................................................................................................................................................................15
Import the Certificate into Additional Salesforce Instances (Optional) ............................................................................................. 17
Setup Salesforce for OAuth 2.0 ................................................................................................................................................................18
Create a Connected App in Salesforce ......................................................................................................................................................18
Locate Security Integration Values for Oracle CPQ............................................................................................................................... 22
Provide Salesforce Security Settings to My Oracle Support ............................................................................................................... 22
Integration User Pairing ............................................................................................................................................................................23
Pair Integration User and Generate Access Token................................................................................................................................ 23
Verify Integration User Partner Login ...................................................................................................................................................... 26
Permissions and Page Layouts................................................................................................................................................. 27
Assign the Admin Permission Set........................................................................................................................................................... 27
Setup Page Layouts and Overrides ........................................................................................................................................................ 29
Create the Lightning Page........................................................................................................................................................................... 29
Update the Opportunity and Account Page Layouts............................................................................................................................ 32
Update the User Layout ............................................................................................................................................................................... 35
Setup Action Overrides ................................................................................................................................................................................ 37
Integration Settings .................................................................................................................................................................... 41
CPQ Site Settings ........................................................................................................................................................................................41
Retrieve CPQ Process Version ID ............................................................................................................................................................... 41
Create the CPQ Site Settings....................................................................................................................................................................... 42
Review CPQ Commerce Process Integrations ...................................................................................................................................... 46
Review CPQ Account Integrations .......................................................................................................................................................... 48
Review CPQ Parts Integrations ................................................................................................................................................................ 50
Review Integration Tab Settings on Oracle CPQ Commerce Actions .............................................................................................. 52
Verify the Process Auto Fill Option ........................................................................................................................................................... 52
Verify the Process Integration Tab ............................................................................................................................................................ 53
Verify the Open Transaction Integration Tab.........................................................................................................................................54
Verify the Refresh Address Action Integration Tab .............................................................................................................................. 55
Verify the Return to Opportunity Action Integration Tab.................................................................................................................... 57
Verify the Return to Account Action Integration Tab ........................................................................................................................... 59
Verify the Select an Alternative Address Action Integration Tab .......................................................................................................61
Verify the Lightning Sync Action Integration Tab ................................................................................................................................. 62
Setup Opportunity to Oracle Quote Synchronization......................................................................................................................... 64
Mapping Opportunity Product Fields to Oracle Quote Line Item Fields ..........................................................................................64
Mapping Opportunity Fields to Oracle Quote Fields (Optional) ........................................................................................................66
Parts Sync .................................................................................................................................................................................... 68
Verify the Parts Master ............................................................................................................................................................................. 68
Synchronizing Parts................................................................................................................................................................................... 68
Price Book Mapping ......................................................................................................................................................................................69
Populate the Oracle CPQ Part Number ....................................................................................................................................................69
SEP 2022 Installation Updated the CPQ Connector for Salesforce and
CPQ Extension for Salesforce download links and
passwords to version 8.5.
Create CPQ Site Settings Updated to include User Account Pattern field.
Provision CPQ Users Updated to include the Oracle CPQ Cloud login
field.
JUL 2022 Installation Updated the CPQ Connector for Salesforce and
CPQ Extension for Salesforce download links and
passwords to version 8.4.
Assign the Admin Permission Set Added note for administrator to verify
Organization Sharing Settings for objects.
Create a Connected App in Salesforce Updated Location field in the Required Canvas App
Settings table.
APR 2019 Installation Provided CPQ Connector for Salesforce version 8.1
download links and passwords.
It is written for the administrator of your organization who has the access and permissions to change your Salesforce Org. It
guides the administrator through the installation of the Oracle CPQ Connector for Salesforce packages (also called the
Salesforce Connector) and the process to setup all integration modes. It does not comprehensively describe every single
feature that is part of the Salesforce-CPQ integration, please refer to the Oracle CPQ Administration Online Help for additional
CPQ-related details.
The Oracle CPQ Connector for Salesforce is comprised of two new managed packages:
Note: Customers currently using an older version of this integration (managed package version 7 or earlier) need to
install the latest managed package (version 8) and reconnect their CPQ site as part of the upgrade process. Refer to the
Oracle CPQ Connector for Salesforce Upgrade and Migration Guide for more information.
GIVE US FEEDBACK
We welcome your comments and suggestions to improve the content. Please send us your feedback at
[email protected].
Oracle CPQ Version Salesforce Managed Package v8.5 is certified to work with Oracle CPQ
Update 22D.
Salesforce Managed Package v8.4 was certified and requires
customers to be on Oracle CPQ Update 22C or later.
Occasionally, newly released features are not compatible with earlier
versions of Oracle CPQ. Please reference the What's New documents
for specific version compatibility details.
Refer to Check the Oracle CPQ and Reference Application Versions.
Enable CRM OAuth in Oracle CPQ You must verify Enable CRM OAuth setting is set to Yes in the Oracle
CPQ Admin > General Site Options page.
Enable My Domain in Salesforce You must enable My Domain for your Salesforce Organization, see the
Salesforce article called My Domain.
My Oracle Support Account You must have an active My Oracle Support account to complete the
Oracle CPQ Connector for Salesforce installation and setup. Refer to
My Oracle Support .
Notes:
This document assumes that the site has been provisioned with the latest Oracle CPQ Reference Application for
Salesforce. If you do not have the latest Reference Application (Ref App) on the site, additional setup steps are
required. Refer to the Oracle CPQ Connector for Salesforce Upgrade and Migration Guide for instructions.
Navigation steps within this document assume you are using the Salesforce Lightning Experience. If you have a
question regarding Salesforce Classic navigation, refer to Salesforce documentation.
5. Click Back.
To locate the current Reference Application Version Info and Read Me files, complete the following steps:
3. Click File Manager under Utilities. The File Manager page displays.
5. From the list of files within the folder, click on the README.txt file. The README file opens.
6. Review the Oracle CPQ Reference Application version information to ensure you have Salesforce Ref App Version 5.0
or later.
7. (Optional) Return to the About folder and select the RefAppVersionInfo.txt file. The RefAppVersionInfo file opens.
Review the change log and Ref App version information.
8. (Optional) Return to the About folder and select the CatalogOfRefAppElements.xlsx file. The
CatalogOfRefAppElements file opens. Review the Microsoft Excel file which itemizes all of the elements contains in the
latest Ref App.
To create and deploy “My Domain” to Salesforce, refer to Salesforce help topic Set Up a My Domain Name.
My Oracle Support
My Oracle Support enables you to search Oracle's knowledge base, manage Service Requests (SRs) when you need assistance,
and take advantage of proactive capabilities for managing systems. During the installation and setup of the Oracle CPQ
Connector for Salesforce, you will be directed to open a Service Request (SR) on My Oracle Support. This section includes
instructions on the following:
My Oracle Support (MOS) customer user accounts are managed by individuals within your organization in the role of
Customer User Administrator (CUA). Most organizations have more than one CUA. The CUA approves or denies access to My
Oracle Support by managing access to your company's SIs.
If you are the first user to register, you are prompted to accept the CUA role. You must accept the CUA role for your
organization to proceed.
To access My Oracle Support, you must have an Oracle Single Sign On (SSO) account. This account is created when you
complete the registration process on oracle.com. For additional SSO account information, refer to Requesting an Oracle Single
Sign On Account.
Once you have your SSO account established, go to My Oracle Support to complete the MOS registration and initial sign in
process to obtain your Support Account. Detailed instructions are provided in the following article, Registration and Sign In.
Note: You must have a Support Account with an approved Support Identifier (SI) to log a Service Request (SR). Refer
to Register in My Oracle Support.
To generate a CPQ Connector for Salesforce SR, complete the following steps:
FIELD DESCRIPTION
Problem Description A detailed description of the problem. Include the following information:
Managed package Name (for example, Oracle CPQ Connector for
Salesforce or Salesforce Commerce Integration)
Managed package version
Oracle CPQ version
Issue type (for example, Setup, Upgrade, Migration, or
Troubleshooting)
If Setup, provide the last step completed in the guide
If Upgrade or Migration, provide the previous version of the
managed package
If Troubleshooting, provide the steps to reproduce the error
5. Select the Cloud tab within the Where’s the Problem section.
6. Select Oracle BigMachines CPQ Cloud Service for the Service Type.
7. Select Integration and Salesforce from drop down for the Problem Type.
The password for the Oracle CPQ Connector for Salesforce package is lvZF9m0W
The password for the Oracle CPQ Extension for Salesforce package is cy21bf0g
For instructions on these Salesforce procedures, refer to the Salesforce online article Install a Package.
Notes:
Always install and test in a sandbox environment before making any changes in production.
If you use multiple Salesforce logins, you must log out of any active sessions before beginning the installation. You
are prompted to log in as a system administrator for the target Salesforce environment.
Install the Oracle CPQ Connector for Salesforce BEFORE you install the Oracle CPQ Extension for Salesforce.
During installation you are prompted to choose a security option, please choose the option most appropriate for
your use case. If you do not know which to choose, we suggest you select "Install for Admins Only”.
For detailed instructions on how to enable the Lightning Experience for your org, refer to Salesforce’s online help at:
Enable the Lightning Experience.
The Salesforce Connector provides seamless and secure authentication for Salesforce users with a valid CPQ license enabling
them to access their content without leaving Salesforce. In order to successfully establish a connection, you need to create a
Connected App, add a remote site, and create a certificate within Salesforce.
4. Create a Certificate
To register your Oracle CPQ site as a remote site, complete the following steps:
1. Navigate to Setup > Security > Remote Site Settings. The All Remote Sites page displays.
2. Click New Remote Site. The Remote Site Edit page displays.
ATTRIBUTE VALUE
Description (Optional)
Active Checked
4. Click Save. The new remote site appears in the list on the All Remote Sites page.
To register your Salesforce My Domain as a remote site, complete the following steps:
1. Click New Remote Site to create a setting for your Salesforce org customer domain name. The Remote Site Edit
page displays.
2. Enter the following values to create a setting for your Salesforce org’s custom “My Domain” URL.
ATTRIBUTE VALUE
Description (Optional)
Active Checked
3. Click Save. The new Salesforce org domain name site appears in the list on the All Remote Sites page.
To add the CPQ environment to CORS allow list, complete the following steps:
1. Navigate to Setup > Security > CORS. The CORS page displays.
3. Enter your CPQ environment instance URL (for example, https://<cpq_site_url>) in the Origin URL text box.
To add your CPQ environment to the CSP allow list, complete the following steps:
1. Navigate to Setup > Security > CSP Trusted Sites. The Content Security Policy Sites page displays.
3. Enter the following values to create a trusted site for your CPQ environment.
ATTRIBUTE VALUE
Description (Optional)
Active Checked
Context All
4. Click Save. The new trusted site appears in the list on the Content Security Policy Trusted Sites page.
2. Enter the following values to create a trusted site for your Salesforce org’s custom “My Domain” URL.
ATTRIBUTE VALUE
Description (Optional)
Active Checked
Context All
3. Click Save. The new trusted site appears in the list on the Content Security Policy Trusted Sites page.
CREATE A CERTIFICATE
Generating a certificate, signed by Salesforce, ensures that communications purporting to originate from your organization
are actually from your organization. Once this certificate is applied to your Oracle CPQ site inbound communications from the
Salesforce Connector can be verified.
Create a self-signed certificate that is loaded into your Oracle CPQ site by Oracle support. For more information, refer to the
Salesforce article called Generate a Self-Signed Certificate.
4. Enter a Unique Name or keep the name that is automatically populated by the label just entered. Make note of the
unique name chosen. This is used again when you Create the Site Settings, where the value entered is case-sensitive
and must precisely match the unique name value entered in this step.
8. A prompt asking if you want to save a .crt file. The certificate (created by you) is downloaded to your default download
folder.
Notes:
The certificate will be valid for one (1) or two (2) years. Before the certificate expires, a new certificate must be
created and re-registered. The process is the same when creating a new certificate or re-registering a certificate.
After you save a Salesforce certificate, you cannot change its type or key size.
Make a note of your certificate filename and its location. The certificate file is required when you perform the steps
within Provide Salesforce Security Settings to My Oracle Support.
1. Navigate to Setup > Security Controls > Certificate and Key Management.
4. Click Export.
After you have exported the certificate from the Salesforce instance that was first connected, you must then import that
certificate to each additional Salesforce instance you plan to connect to Oracle CPQ.
To import the certificate file (JKS format) from a Keystore, complete the following steps:
1. Navigate to Setup > Security Controls > Certificate and Key Management.
2. Click Import from Keystore. The Import from a Keystore page displays.
3. Click Browse and select the file previously saved to your system.
5. Click Save. The certificates inside the Keystore are imported into your organization.
For more information on Connected Apps using OAuth 2.0, refer to the Salesforce online help article Connected Apps
Overview.
Note: These steps assume that you are creating a Connected App for your Oracle CPQ site for the first time. If you are
upgrading and you already have a Connected App in use, please refer to the Oracle CPQ Connector for Salesforce
Upgrade and Migration Guide.
1. Navigate to Setup > Platform Tools > Apps > App Manager.
4. Enter the following required Basic Information values to create a new Connected App. All other fields in Basic
Information section are optional. Refer for the Salesforce online help article Create a Connected App for detailed
information.
BASIC INFORMATION
Connected App Name Text string for label name Oracle Adapter
Attribute Value
7. Click Save.
8. The Manage Connected Apps page displays. Save the Consumer Key and Consumer Secret (click to reveal) field
information for easy reference later when performing the Provide Salesforce Security Settings to My Oracle Support
procedure.
Note: Refer to the Salesforce article Create a Connected App for more information.
1. Navigate to Setup > Platform Tools > Apps > App Manager and view the Lightning Experience App Manager.
2. Locate the Connected App that you want to view. Open the option menu and choose View.
3. Note both the Consumer Key and Consumer Secret (click to reveal), under the API (Enable OAuth Settings)
section. You need these values to connect your Oracle CPQ and Salesforce environments when performing the
Provide Salesforce Security Settings to My Oracle Support procedure.
Note: You must have a Support Account with an approved Support Identifier (SI) to log a Service Request (SR).
To provide Oracle Support with the Salesforce security settings, complete the following steps:
1. Generate an SR from the My Oracle Support (MOS) website. Refer to Log an Oracle CPQ Connector for Salesforce
Service Request and specify the following field designations.
2. Select Site Maintenance > Site Setting Changes for the Problem Type.
3. Enter the Consumer Key into the Salesforce Client Key field (see Locate Security Integration Values for Oracle CPQ).
4. Enter the Consumer Secret into the Salesforce Consumer Secret field (see Locate Security Integration Values for
Oracle CPQ).
5. Upload d the Certificate file (see Create a Certificate). For help on uploading a file, refer to Oracle online help Working
with Service Requests.
6. Specify if you are trying to connect to Salesforce Production or a Sandbox Organization to your CPQ site.
Note: Production environments will have a login URL similar to https://login.salesforce.com/...; Sandbox environments
will have a login URL similar to https://test.salesforce.com/...
If you have additional user accounts you’d like to pair manually, each user will individually follow the steps in the next section
to pair their logins by generating a security token. You typically perform this step for your Integration User account first.
Notes:
Do not proceed with this process until Oracle CPQ Support has completed the Service Request to establish the
security and connected app. Refer to Log an Oracle CPQ Connector for Salesforce Service Request
If you are upgrading and migrating you do not need to perform this procedure as you already have an integration
user paired and integrated. Please reference the Oracle CPQ Connector for Salesforce Upgrade and Migration
Guide.
User accounts must be paired before a user can SSO from Salesforce into Oracle CPQ. When a user punches into CPQ from
Salesforce the first time an Access Token is automatically generated, however during the initial setup the Integration User will
need to manually generate their access token to push data from CPQ to Salesforce using their APIs.
Once a user has generated this token, they will continue to be able to sign on from Salesforce and sync data back to Salesforce
from CPQ even after their Salesforce or CPQ user password changes. In this section, we describe how to manually generate
the token.
Note: Before you begin, log out of all Salesforce instances so that you do not accidently pair to the wrong user account
or organization.
1. Log into Oracle CPQ with your Integration Username and Password.
2. Click the My Profile icon in the Navigation bar at the top of the page.
My Profile Icon
Note: The My Profile icon and location may vary based on your CPQ site configuration.
6. Log in to Salesforce with the credentials for the user account you want to integrate.
The User Integration page displays with confirmation that the Token Generated
Note: Before you have completed the steps for User Sync, you need to complete these steps for each additional user
who you want to integrate. If you try to access Oracle CPQ from Salesforce with a user that has not been paired, they will
see errors when trying to open quotes.
Note: The steps provided in this procedure are for pairing integration users; however, you can follow the same steps to
pair any user accounts. Refer to Manually Integrate Existing Users from Oracle CPQ.
Upon completion of the installations, you will notice new permission sets when viewing the Permission Sets page in
Salesforce (Setup > Administration > Users > Permission Sets). The following permission sets appear:
Administrators need both the Oracle Adapter Admin and the Oracle CPQ Extension Admin permission sets.
To assign the two new permission sets to your administrative profile, complete the following steps:
1. Navigate to Setup > Administration > Users > Users and click on your username to access your user profile.
2. Scroll down to the Permission Set Assignments list and click Edit Assignments. The Permission Set Assignments
page displays.
3. Select Oracle Adapter Admin and Oracle CPQ Extension Admin from Available Permissions Sets area and click the
Add button to move them to the Enabled Permission Sets area.
These Admin permissions grant access rights to the objects listed in the following table.
Embedded CPQ Site Settings Create, Read, Update, Delete, View/Modify All
Oracle Quote Line Items Create, Read, Update, Delete, View/Modify All
These permissions additionally grant access to a number of Visualforce pages, Apex Classes, and Assigned Apps which are
required for the proper function of the managed package.
Note: Administrators should verify that the Organization Sharing Settings are properly configured for each of the above
objects. Refer to Salesforce Help for Salesforce Organization and Sharing Settings information. If you are enabling
Communities access for partner users, you may need to change the Default External Access policies. Consult with your
Salesforce administrator for guidance on how best to provide access to the managed package settings and data.
1. Create the Lightning Page for the Oracle Quotes and Line Items
1. In Salesforce, navigate to Setup > Platform Tools > User Interface > Lightning App Builder.
4. Click Next.
7. Click Next.
9. Click Finish.
10. From the Lightning Components sidebar, under Custom, drop and drag the recordView component into the view.
Note: If you are not able to view the recordView component, you may need to deploy your previously created My
Domain.
12. Click Activate. The Activation for the specified page displays.
15. Repeat these steps to create the Oracle Quote Line Items and any other customer pages requiring update or click
Close.
Note: Refer to the Lighting App Builder online help for additional assistance.
To expose the Oracle Quote related list on the Opportunity layout, complete the following steps. Repeat these steps for each
layout that users have the ability to access.
1. In Salesforce, navigate to Setup > Platform Tools > Objects and Fields > Object Manager > Opportunity.
3. Select Edit under the option menu for the Page Layout you want to edit.
6. Click the icon in the tab for the Oracle Quotes section. The Related List Properties – Oracle Quotes section
displays.
7. Move the fields you want to display into the Selected Fields area using the Add and Remove arrows within the
Columns section of the page. Use the Up and Down arrows to order the fields within the Selected Fields area.
8. Select the field you want to sort by from the Sort By drop-down.
9. Specify whether you want the values to display in Ascending or Descending order.
11. Select the New checkbox within the Standard Buttons section.
12. Add the Clone, Move and Mark as Active buttons into the Selected Buttons area using the Add and Remove arrows
within the Custom Buttons section.
Notes:
The custom New button is no longer used. You should leave this unselected.
The Move action is not supported in the Salesforce Mobile application. For more information, reference Salesforce
Issue information.
15. Repeat these steps for each Opportunity Layout that CPQ users have the ability to access.
16. Repeat these steps for the Account Page Layout but navigating to Setup > Platform Tools > Objects and Fields >
Object Manager > Account > Page Layouts.
Note: The Mark as Active button should not be used on Account Page Layouts, it is only used when synchronizing
Quotes with Opportunities.
To add the Oracle User Layout to the user record layout, complete the following steps:
1. Navigate to Setup > Platform Tools > Objects and Fields > Object Manager > User
3. Select Edit under the option menu for the Page Layout you want to edit.
5. Click and drag a Section to move it onto the User Layout page. The Section Properties page displays.
Note: We recommend naming this section the Oracle User section and choosing 1-column layout.
7. Hover the cursor over the newly placed page and click the icon. The Visualforce Page Properties displays.
Note: We recommend naming this section the Oracle User section and choosing 1-column layout.
8. Click OK.
9. Click Save.
Note: Refer to User Sync for additional detail on configuring Oracle users.
1. In Salesforce, navigate to Setup > Platform Tools > Objects and Fields > Object Manager > Oracle Quote.
2. Click on Buttons, Links, and Actions. The Buttons, Links, and Actions page displays.
3. Locate the View action and click Edit under the option menu. The view action’s Override Properties page displays.
4. Select Visualforce Page for the Salesforce Classic Override. Choose OracleQuoteView from the list of pages.
6. Select Lightning Component for the Mobile Override. Choose oafsl:recordView from the list of components.
7. Click Save.
8. Return to the Buttons, Links, and Actions page. Locate the Edit action and click Edit under the option menu. The Edit
action’s Override Properties page displays.
9. Select Visualforce Page for the Salesforce Classic Override. Choose OracleQuoteEdit from the list of pages.
10. Select Use Salesforce Classic override for the Lightning Experience Override.
11. Select Use Salesforce Classic override for the Mobile Override.
16. Select Use Salesforce Classic override for the Lightning Experience Override.
17. Select Use Salesforce Classic override for the Mobile Override.
Note: The following sections assume that the CPQ site has been provisioned with the latest Oracle CPQ Reference
Application for Salesforce. If you do not have the latest Reference Application (Ref App) on the site, additional setup
steps are required. Refer to the Oracle CPQ Connector for Salesforce Upgrade and Migration Guide for instructions.
CPQ Site Settings are stored in Salesforce for each connection as a Data Set. Each time you modify the CPQ Site Settings, this
Data Set must be re-deployed. The CPQ Site Settings are retained each time you upgrade Salesforce or Oracle CPQ.
Note: We highly recommend that you are in Classic Mode to perform the procedures outlined in this guide. See
Toggling Between Salesforce Classic and The Lightning Experience for additional help.
2. Navigate to the Admin home page > Commerce and Documents > Process Definition. The Processes page
displays.
3. Select the desired process and select Integrations from the Navigation drop-down.
6. Record the version_id information. This information is needed to create site settings.
To create your CPQ Site Settings using the Site Settings Wizard, complete the following steps:
1. In Salesforce using the App Launcher, navigate to the CPQ Site Settings object by entering CPQ Site Settings in the
keyword search.
3. Click New. The CPQ Site Settings, Step 1: Connection Details displays. Step 1 is where you input all the settings
needed to connect your site, initialize the Salesforce Connector, map the fields, and save the data that is specific to
your CPQ site and your integration flow.
Note: If you have not successfully paired your integration user or are not currently logged in as a paired user, you are
not able to proceed to CPQ Site Settings, Step 2: Process Details.
CPQ Site Settings Name Enter a descriptive Name for this connection to your CPQ Site. Some
sites may have multiple connections.
This name is displayed to sales users if they have permissions to select
multiple data sets during quote creation.
This name is used by administrators to Setup User Sync.
Use Embedded Transaction in Check to enforce receiving the Embedded UI instead of the Lighting UI.
Lightning This sets the admin toggle.
Note: When Embedded Transaction in Lighting is selected, Quote Name
Attribute, Lightning Sync Action and Oracle Quote ID Attribute fields do
not display in Step 3 – Adapter Settings.
Data Set Enter a data set name. Variable Name conventions apply such as
alphanumeric characters without spaces.
For advanced use cases in which more than one CPQ Site connection is
in use, this value is used to load the correct CPQ Site Settings at runtime.
It is highly recommended that data sets have a unique value. If a
duplicate value is deployed, pre-existing connection settings deployed
to production with the same data set name are truncated.
Connected App Name Enter the API Name of the Connected App that you created earlier for
this CPQ site. The API Name is case-sensitive and must precisely match
the name previously entered during the Create a Connected App in
Salesforce procedure. Refer to Create a Connected App in Salesforce if
you need to relocate your Connected App Name.
Certificate Name Enter the Unique Name of the certificate that was shared with CPQ.
This name must precisely match the name of the certificate you
provided to My Oracle Support.
Refer to Create a Certificate.
Notes:
Select Use Embedded Transaction in Lightning for your initial set up. You can switch to Lightning Mode after the
initial set up is complete.
Salesforce enforces an Apex Heap Size Limit of 6MB for synchronous transactions. The "Apex heap size too large"
error occurs when too much data is being stored in memory during processing. In some cases when setting up
Lightning Mode for a very large Commerce Process this error can occur when generating the CPQ Site Settings. This
can be resolved by reverting to Embedded Mode or deleting actions and attributes from your process.
6. Enter the process details for the fields. Refer to the table below for field information.
Select Process Select the Commerce Process to pair with the site. The list of
Commerce Processes is dynamically retrieved from your connected
CPQ site.
Document Name This field automatically populates with the specified Document Name
for the CPQ site.
Version ID Enter the version_id value. Refer to Retrieve CPQ Process Version ID.
Process Name This field automatically populates with the specified Process Name for
the CPQ site.
Subdocument Name This field automatically populates with the specified Sub-document
name for the CPQ site.
7. Click Next. The CPQ Site Settings, Step 3: Adapter Settings displays.
Use Opportunity Currency Check this if you want to set the Quote’s currency automatically based
on the Opportunity’s selected currency. When unchecked you will
need to select the currency when adding products to the quote.
Primary Check this if you want this process to be your main process used for
your users. For single connection scenarios, the Primary checkbox
must be selected.
Use Opportunity Price Book Check this if you want to set the Quote’s price book automatically
based on the Opportunity’s selected price book. When unchecked you
will need to select the price book when adding products to the quote.
User Account Pattern Select a common user account login pattern to generate the
Username field for each user, as follows:
Salesforce Username Prefix (default) equals the Salesforce
Username field which precedes the '@' character
Salesforce Username – equals an exact match of the Salesforce
Username field, including the '@' character
Email Address – the exact match of the Salesforce user's email
address
Note: The Oracle CPQ User Account Pattern applies only during the
initial creation of an Oracle user record. Once the user account is
created, changing the User Account Pattern field will not update the
Oracle CPQ Cloud Login for pre-existing CPQ users. Only
administrators can manually update a user's Oracle CPQ Cloud Login.
Notes:
When Embedded Transaction in Lighting is selected, Button Group Display Count, Data Table Page Size, Quote
Name Attribute, Lightning Sync Action, and Oracle Quote ID Attribute fields do not display.
If your Oracle CPQ site was not provisioned with the latest Oracle CPQ Reference Application, the Lightning Sync
Action may not be available for selection. To proceed, you must complete the steps in the Oracle CPQ Connector for
Salesforce Upgrade and Migration Guide to save and deploy your site settings.
11. Click Deploy Site. Deploying the settings can take a little time, sometimes up to a minute. Once complete a message
indicating successful deployment displays.
Note: If you prefer, you can click the Advanced Mode button to view each of the pages outlined above in a single
screen. To return to the wizard, click the Wizard Mode button.
To review and verify Commerce Process Integrations, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. For the process you want to verify, select Integrations from the Navigation drop-down.
4. Click List.
The integrations in the latest Ref App are listed in the following table
Opportunity Import Salesforce: Imports the Opportunity details and populates the
corresponding attribute values on the Transaction.
User Import Salesforce: Imports the User details and populates the corresponding
attribute values on the Transaction.
Quote Import Salesforce: Imports the Oracle Quote details and populates the
corresponding attribute values on the Transaction.
Lightning Quote Upsert Salesforce: Updates the Oracle Quote record that is created initially
when a new quote is created in Lightning mode. This integration
exports the Transaction ID, sets the Opportunity ID and Account ID, and
sets the associated Data Set on the Oracle Quote.
Quote Upsert Salesforce: Creates an Oracle Quote record if one does not exist,
otherwise it updates the existing one. Also sets the flag that tells the
Oracle CPQ Connector that an upsert operation has begun.
Line Item Upsert 200 Salesforce: Creates or updates Oracle Quote Line Items on the Oracle
Quote that are associated with the Lines on the Transaction and
populates the corresponding fields. This upserts the first batch of 200
lines.
Line Item Upsert 400 Salesforce: Creates or updates Oracle Quote Line Items on the Oracle
Quote that are associated with the Lines on the Transaction and
populates the corresponding fields. This upserts the second batch of
200 lines.
Line Item Upsert 600 Salesforce: Creates or updates Oracle Quote Line Items on the Oracle
Quote that are associated with the Lines on the Transaction and
populates the corresponding fields. This upserts the third batch of 200
lines.
Line Item Upsert 800 Salesforce: Creates or updates Oracle Quote Line Items on the Oracle
Quote that are associated with the Lines on the Transaction and
populates the corresponding fields. This upserts the fourth batch of
200 lines.
Line Item Upsert 1000 Salesforce: Creates or updates Oracle Quote Line Items on the Oracle
Quote that are associated with the Lines on the Transaction and
populates the corresponding fields. This upserts the fifth batch of 200
lines.
Quote Upsert Complete Salesforce: Updates the flag on the Oracle Quote that lets the Oracle
CPQ Connector know that the upsert is complete. This triggers all the
Salesforce-side updates to the Oracle Quote and Opportunity.
6. If the integrations listed match the latest Ref App list, proceed to the next section.
Notes:
If your Oracle CPQ site was not provisioned with the latest Oracle CPQ Reference Application, the Commerce Process
Integrations required for the Salesforce Connector may not be included in your environment. To proceed, you must
complete the steps in the Oracle CPQ Connector for Salesforce Upgrade and Migration Guide to create your Commerce
Process Integrations.
To export attachments to Salesforce Lightning (the Notes and Attachments feature in Salesforce was deprecated),
administrators will need to develop a custom BML integration with an action to send the attachment to Salesforce via a
REST call. Refer to Connect REST API Developer Guide in Salesforce Help for more information.
The integrations in the latest Ref App are listed in the following table.
Account Import Salesforce: Imports the Account information from the CRM and maps
those values to Account attributes. It is used by the Refresh Address
action to populate the mapped values on the transaction. When
Account Auto Fill is enabled, the Refresh Address action runs
automatically when the transaction is first created.
Contact Import Salesforce: Imports the Contact information from the CRM and maps
those values to Account Address attributes. It is used by the Select An
Alternate Address action to populate the mapped values on the
transaction.
5. If the integrations listed match the latest Ref App list, proceed to the next section.
Note: If your Oracle CPQ site was not provisioned with the latest Oracle CPQ Reference Application, the Commerce
Process Integrations required for the Salesforce Connector may not be included in your environment. To proceed, you
must complete the steps in the Oracle CPQ Connector for Salesforce Upgrade and Migration Guide to create your
Commerce Process Integrations.
4. Review the Integrations available. The integrations in the latest Ref App are listed in the following tables.
If Salesforce is assigned as the Parts Master, the following integrations are available:
SALESFORCE AS PARTS
MASTER DESCRIPTION
PARTS INTEGRATIONS
Import Parts Salesforce: When Salesforce is the Parts Master, creates new
Parts/Items in CPQ for each new Product and updates existing Parts
with any new Product details.
Import Part Extended Salesforce: When Salesforce is the Parts Master, updates Parts
Descriptions Extended Description in CPQ with any new Product details.
Import Price Book Entries Salesforce: When Salesforce is the Parts Master, updates Prices on
Parts in CPQ with the Price Book Entry from any mapped Price Book.
If Oracle CPQ is assigned as the Parts Master, the following integrations are available:
Export Parts Salesforce: When CPQ is the Parts Master, creates new Products in
Salesforce for each new Part/Item and updates existing Products with
any new Part/Item details.
Export Part Extended Salesforce: When CPQ is the Parts Master, updates Products in
Descriptions Salesforce with any new Extended Parts Descriptions.
Export Price Book Entries Salesforce: When CPQ is the Parts Master, updates Price Book Entries
for each Product in Salesforce from the Parts/Items prices.
Note: If your Oracle CPQ site was not provisioned with the latest Oracle CPQ Reference Application, the Parts
Integrations required for the Salesforce Connector may not be included in your environment. To proceed, you must
complete the steps in the Oracle CPQ Connector for Salesforce Upgrade and Migration Guide to create your Commerce
Process Integrations.
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. Click the Name of the process. The Process Administration page displays.
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. Click the Name of the process. The Process Administration page displays.
5. Review the Available and Selected Imports and verify the following integrations are selected.
Opportunity Import (Import) Salesforce: Imports the Opportunity details and populates the
corresponding attribute values on the Transaction.
User Import (Import) Salesforce: Imports the User details and populates the corresponding
attribute values on the Transaction.
To verify the Open Transaction Integration tab, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. For the process you want to verify, select Process Actions from the Navigation drop-down.
7. Review the Integrations and verify the following integrations are selected and sequenced in the following order
Apply Modify Functions Runs the modifications defined on the Modify tab and the Advanced
Modify functions for this action.
Quote Import (Import) Salesforce: Imports the Oracle Quote details and populates the
corresponding attribute values on the Transaction.
Opportunity Import (Import) Salesforce: Imports the Opportunity details and populates the
corresponding attribute values on the Transaction.
User Import (Import) Salesforce: Imports the User details and populates the corresponding
attribute values on the Transaction.
To verify the Refresh Address Action Integration tab, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
5. For the Document you want to verify, select Actions from the Navigation drop-down.
7. Click on the Refresh Address link under the Action Name column. The Admin Action page displays.
To verify the Return to Opportunity Action Integration tab, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. For the process you want to verify, select Documents from the Navigation drop-down.
5. For the Document you want to verify, select Actions from the Navigation drop-down.
9. Review the Integrations and verify the following integrations are selected and sequenced in the following order.
Apply Modify Functions Runs the modifications defined on the Modify tab and the Advanced
Modify functions for this action.
Quote Upsert (Export) Salesforce: Creates an Oracle Quote record if one does not exist,
otherwise it updates the existing one. Also sets the flag that tells the
Oracle CPQ Connector that an upsert operation has begun.
Line Item Upsert 200 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the first batch
of 200 lines.
Line Item Upsert 400 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the second
batch of 200 lines.
Line Item Upsert 600 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the third batch
of 200 lines.
Line Item Upsert 800 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the fourth
batch of 200 lines.
Line Item Upsert 1000 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the fifth batch
of 200 lines.
Quote Upsert Complete Salesforce: Updates the flag on the Oracle Quote that lets the Oracle
CPQ Connector know that the upsert is complete. This triggers all
the Salesforce-side updates to the Oracle Quote and Opportunity.
Note: If you have quotes with more lines, you may have more integrations listed. If you have quotes with less lines, you
may have less integrations listed.
To verify the Return to Account Action Integration tab, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. For the process you want to verify, select Documents from the Navigation drop-down.
5. For the Document you want to verify, select Actions from the Navigation drop-down.
9. Review the Integrations and verify the following integrations are selected and sequenced in the following order.
Apply Modify Functions Runs the modifications defined on the Modify tab and the Advanced
Modify functions for this action.
Quote Upsert (Export) Salesforce: Creates an Oracle Quote record if one does not exist,
otherwise it updates the existing one. Also sets the flag that tells the
Oracle CPQ Connector that an upsert operation has begun.
Line Item Upsert 200 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the first batch
of 200 lines.
Line Item Upsert 400 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the second
batch of 200 lines.
Line Item Upsert 600 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the third batch
of 200 lines.
Line Item Upsert 800 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the fourth
batch of 200 lines.
Line Item Upsert 1000 (Export) Salesforce: Creates or updates Oracle Quote Line Items on the
Oracle Quote that are associated with the Lines on the Transaction
and populates the corresponding fields. This upserts the fifth batch
of 200 lines.
Quote Upsert Complete (Export) Salesforce: Updates the flag on the Oracle Quote that lets the Oracle
CPQ Connector know that the upsert is complete. This triggers all
the Salesforce-side updates to the Oracle Quote and Opportunity.
Note: If you have quotes with more lines, you may have more integrations listed. If you have quotes with less lines, you
may have less integrations listed.
To verify the Select an Alternative Address Action Integration tab, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. For the process you want to verify, select Documents from the Navigation drop-down.
5. For the Document you want to verify, select Actions from the Navigation drop-down.
To verify the Lightning Sync Action Integration tab, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. For the process you want to verify, select Documents from the Navigation drop-down.
7. Click on the Lightning Sync link under the Action Name column.
9. Review the Integrations and verify the following integrations are selected and sequenced in the following order.
Apply Modify Functions Runs the modifications defined on the Modify tab and the Advanced
Modify functions for this action.
Lighting Quote Upsert (Export) Salesforce: Updates the Oracle Quote record that is created initially
when a new quote is created in Lightning mode. This integration
exports the Transaction ID, sets the Opportunity ID and Account ID, and
sets the associated Data Set on the Oracle Quote.
In order to successfully synchronize opportunities and quotes, you must first map the quote fields to their corresponding
opportunity fields. Additionally, you must map the quote line item fields to the opportunity product fields. In this section, we
review the required standard and custom field mappings.
If any existing field mappings have a Mapping Type of Oracle Quote to Opportunity, the Oracle Quote record’s fields
are used to update fields on the Opportunity, based on the Field Mappings records that the admin user has created.
If any existing field mappings have a Mapping Type of Oracle Quote Line Item to Opportunity Line Item, Oracle
Quote Line Item records are used to create Opportunity Line Item records. The Opportunity Line Item records’ fields
are populated by fields on the Oracle Quote Line Item records, based on the Field Mappings records that the admin
user has created.
Note: This feature does not apply to a Quote created from Accounts.
To successfully create Opportunity Products certain fields are required. These fields must be mapped following the steps
below. Optionally, you can map additional fields that contain data that you want reflected on the Opportunity level.
Sales Price The sales price of the product for this Opportunity.
To create the field mappings which associate your Oracle Quote Line Item fields to your Opportunity Product fields, complete
the following steps:
1. In Salesforce, select the Sales drop-down and click Oracle CPQ Extension.
FIELD DESCRIPTION
Mapping Type Specify whether this is either a mapping from Oracle Quote to
Opportunity, or Oracle Quote Line Item to Opportunity Line Item
Source File The field on the Oracle Quote or Oracle Quote Line Item that provides the
mapping value’s source info.
Target Field The field on the Opportunity or Opportunity Line Item to be updated.
5. Click Save to save the newly created field mapping or click Save & New to save the field mapping and create an
additional field mapping.
To create field mappings which associate your Oracle Quote fields to your Opportunity Product fields, complete the following
steps:
1. In Salesforce, select the Sales drop-down and click Oracle CPQ Extension.
2. Click on the Field Mappings tab. The Recent Field Mappings page displays.
FIELD DESCRIPTION
Mapping Type Specify whether this is either a mapping from Oracle Quote to
Opportunity, or Oracle Quote Line Item to Opportunity Line Item
Source File The field on the Oracle Quote or Oracle Quote Line Item that provides the
mapping value’s source info.
Target Field The field on the Opportunity or Opportunity Line Item to be updated.
5. Click Save to save the newly created field mapping or click Save & New to save the field mapping and create an
additional field mapping.
Note: In a later section, we will explain how values from the Transaction in Oracle CPQ get saved to the Oracle Quote and
Oracle Quote Line Items records in salesforce. You may need to create new customer fields on those objects which may
be added to the field mappings later.
Note: In order to change your Parts Master selection, you must log an SR in My Oracle Support. Refer to Log an Oracle
CPQ Connector for Salesforce Service Request.
To check your current Parts Master selection, complete the following steps:
1. Log in as SuperUser.
IMPORTANT: To view the Parts Integration Settings page, you must be logged in as SuperUser.
4. Under the Item Master section, the selected Parts Master displays. The two available options are:
6. (Optional) Under List Integrations, if Salesforce is the Parts Master, three integrations are listed: Import Parts, Import
Part Extended Descriptions, and Import Price Book Entries. If Oracle CPQ is the Parts Master, the following
integrations are listed: Export Parts, Export Part Extended Descriptions, and Export Price Book Entries.
Synchronizing Parts
Once you have selected your Parts Master and you have created your parts in the master system, you are ready to
synchronize your parts between the systems. Until you have completed this step, you are not able to successfully synchronize
Oracle Quotes with Opportunities.
Part Sync supports multiple Price Books. Each Salesforce Price Book must be mapped to a corresponding Oracle CPQ
Price Book. Refer to Price Book Mapping.
Part Sync supports multiple currencies per Price Book. To use multiple currencies, you need to modify the XSL
templates provided for each parts integration and change the partner_max_export_size parameter. Open a service
request with My Oracle Support for this change.
If you have custom parts fields that you want to sync to Salesforce, you need to create custom fields on the Product
object in Salesforce and add those mappings to your XSL templates.
Products in Salesforce must be set to Active before they can be synced to an Opportunity.
If multiple Oracle CPQ sites are setup to integrate with one Salesforce instance, you can use multiple Oracle CPQ sites
as the Parts Master for integration with the same Salesforce site. You must ensure that duplicate part numbers are not
synced to Salesforce from the separate CPQ sites.
4. Click on your Price Book in the Price Book Name column. The Price Book displays.
10. Click the target Price Book name under the Name column.
11. Paste the Price Book ID (copied from Salesforce) to the Partner Price Book ID field within the Integration section.
The easiest way to populate this field on existing Salesforce products is by completing the following steps:
1. Download the Salesforce Data Loader tool. Use this tool to download the product records.
2. Copy the associated product name into the Oracle CPQ Part Number field.
The Part Numbers used when creating parts is determined by your business process. Adapt these steps as appropriate.
Note: The steps above assume Salesforce is the Parts Master. If Oracle CPQ is the Parts Master, the Oracle CPQ Part
Number field is populated by the parts export.
Note: If you have selected Oracle CPQ as the Parts Master, the steps outlined in this section are similar for exporting
Parts to Salesforce.
Note: If your SuperUser has not already been integrated, you need to click Partner Login to connect to Salesforce prior
to syncing parts.
6. Click Import.
7. Your import job appears under the Scheduled Integrations section. Click Refresh to monitor the status.
8. Once complete, your integration job appears under the Integration History section. View the details of the job. The
log is available if needed to troubleshoot errors.
9. (Optional) To verify that your parts have been created in CPQ and properly mapped to the Salesforce product,
complete the following steps:
c. Click Search under Search for Part by Part Number section. The Part Search Results display.
d. Click on the part number you want to verify. The Part Editor displays.
e. Review the information to ensure it is complete and verify the Salesforce ID under Product Integration
Information section.
Note: You may need to modify the XSL templates for this integration if you are using custom attributes, multiple
currencies, or other customizations.
Notes:
If you have selected Oracle CPQ as the Parts Master, the steps outlined in this section are similar for exporting to
Salesforce.
The part must exist in Oracle CPQ before you can update the Part Extended Description.
To import Parts Extended Descriptions from Salesforce, complete the following steps:
Note: If your SuperUser has not already been integrated, you need to click Partner Login to connect to Salesforce prior
to syncing parts.
5. Select the Import Part Extended Descriptions integration under the Name column in the List Integrations section.
6. Click Import.
7. Your import job appears under the Scheduled Integrations section. Click Refresh to monitor the status.
8. Once complete, your integration job appears under the Integration History section. View the details of the job. The log
is available if needed to troubleshoot errors.
Notes:
If you have selected Oracle CPQ as the Parts Master, the steps outlined in this section are similar for exporting to
Salesforce.
The part must exist in Oracle CPQ before you can update the Pricing Information for the part.
To import Price Book Entries from Salesforce, complete the following steps:
Note: If your SuperUser has not already been integrated, you need to click Partner Login to connect to Salesforce prior
to syncing parts.
6. Click Import.
7. Your import job appears under the Scheduled Integrations section. Click Refresh to monitor the status.
8. Once complete, your integration job appears under the Integration History section. View the details of the job. The log
is available if needed to troubleshoot errors.
Note: You may need to modify the XSL templates for this integration if you are using multiple price books, multiple
currencies, or other customizations.
5. Assign the parts sync integration action by selecting the appropriate time interval information in the Schedule Type,
Day/Frequency, Hours, and Minutes drop-downs.
6. Specify a Start Date in the format specified, such as MM/dd/yyyy h:mm am.
7. Specify an End Date, if desired, in the format specified, such as MM/dd/yyyy h:mm am.
• Delta – only export parts that have been updated since the last parts sync integration activity.
• All Parts – perform an export for every part. This overwrites all part information with the latest data.
10. Verify that the integration activity is added to the Scheduled Integrations list.
These steps are similar to the integration user pairing except with other user types. You can repeat these steps for as many
users as required.
Notes:
Do not proceed with this process until Oracle CPQ Support has completed the Service Request to establish the
security and connected app. Refer to Log an Oracle CPQ Connector for Salesforce Service Request.
If you are upgrading and migrating you may not need to perform this procedure as you already have users paired
and integrated. Please reference the Oracle CPQ Connector for Salesforce Upgrade and Migration Guide.
Once users have been paired, a user token must be generated before those users are allowed to SSO from Salesforce into
Oracle CPQ. Once a user has generated this token, they will continue to be able to sign on from Salesforce even after their
Salesforce user password changes. This section describes how to manually generate the token. If a user has been paired, but a
token has not been generated, the user is prompted to do so when they first attempt to login to Oracle CPQ.
Note: Before you begin, log out of all Salesforce instances so that you do not accidently pair to the wrong user account
or organization.
1. Log into Oracle CPQ with the Username and Password for the user to be paired.
Note: The My Profile icon and location may vary based on your CPQ site configuration.
4. Enter the Salesforce Username that you are pairing to in the Login field.
6. Log in to Salesforce with the credentials for the user account you want to integrate.
The User Integration page displays with confirmation that the Token Generated
Note: If you try to access Oracle CPQ from Salesforce with a user that has not been paired, they will see errors when
trying to open quotes.
Creating a user in Salesforce and immediately provisioning the user in Oracle CPQ
Before you can use automatic provisioning, there are a few preliminary steps you may want to perform to aid in this process.
CPQ User Groups are used to control which products users have access to and which actions they can perform on quotes,
these must be defined before provisioning users into those groups. Also, CPQ User Profiles can act as a template which
defaults the user preferences and group membership for certain categories of users.
Note: To perform these procedures, you must have an active CPQ integration user and Salesforce integration user that
has been paired (Refer to Integration User Pairing) and ensure that you are not logged in as any other user than the
paired integration user.
To retrieve Group Variable Names from Oracle CPQ, complete the following steps:
2. Under Users, click Groups. The Group Administration List displays. Leave the Group Administration List open or copy
the variable names for all groups into a document. You must reference these values in later steps.
To add CPQ Group Variable Names as Salesforce Picklist Values, complete the following steps:
2. Navigate to Build > Create > Objects to open the Custom Objects page.
4. In Custom Fields & Relationships, click on the Groups link under Field Label. The Custom Field Definition Detail
information displays.
7. Click Save.
8. In Picklist Values, delete the Standard user group by clicking the Del link next to it, unless you have a group with a
variable name of “Standard” in your Oracle CPQ site.
1. In Salesforce, select the Sales drop down and click Oracle CPQ Extension.
4. Enter the values for the fields for the desired user profile. Refer to the table below for field information.
Oracle User Profile Name Enter the desire name for the User Profile.
User Type Select the designated user type, for example, FullAccess, SalesAgent
ChannelAgent, RestrictedAcesses
Partner User Check this if the users are to be paired with a “Partner User”.
Link to CPQ User Check this to allow for users to be created in CPQ, if one does not exist.
Suspend CPQ User Sync Check this to not send changes that are made on the User Profile in
Salesforce to be sent to CPQ.
Allow Quote Creation Check this if users are allowed to create quotes.
Designated Approver Enter the name of the designated approver for the user profile.
Groups Select from the list of groups available. Refer to Create User Groups in
Salesforce.
Language Preference Select the preferred display for the language for the users assigned this
profile.
Currency Preference Select the preferred display for currency for the users assigned this
profile.
Number Format Select the number format default for this user profile. Select decimal or
comma.
Units Select the preferred display for units of measure for the users assigned
this profile.
Data Table Format Select the preferred display of the data table format for the users
assigned this profile.
Time Zone Select the time zone for the users assigned this profile.
5. Click Save.
2. Click on the user that you want to pair with CPQ and scroll down to the Oracle User section created in Update the
User Layout.
Note: The default profile feature only works when Oracle users are first created. Subsequent changes to the user
preferences must be entered manually.
5. (Optional) If you are not using default profiles, fill in the preferences for this user. Refer to the table below for field
information.
Oracle CPQ Cloud Login Maps the Saleforce user record to the CPQ User Login. This is
automatically generated based on the User Account Pattern when
provisioned. Administrators can manually override the default Oracle
CPQ User Login.
Administrators can use this field to remap a Salesforce user record to a
different/existing CPQ user when needed.
User Type Select the designated user type, for example, FullAccess, SalesAgent
ChannelAgent, RestrictedAcesses
Partner User Check this if the users are to be paired with a “Partner User”.
Link to CPQ User Check this to allow for users to be created in CPQ, if one does not exist.
Suspend CPQ User Sync Check this to not send changes that are made on the User Profile in
Salesforce to be sent to CPQ.
Allow Quote Creation Check this if users are allowed to create quotes.
Delegated Approver Enter the name of the designated approver for the user profile.
Groups Select from the list of groups available. Refer to Create User Groups in
Salesforce.
Language Preference Select the preferred display for the language for the users assigned this
profile.
Currency Preference Select the preferred display for currency for the users assigned this
profile.
Number Format Select the number format default for this user profile. Select decimal or
comma.
Units Select the preferred display for units of measure for the users assigned
this profile.
Data Table Format Select the preferred display of the data table format for the users
assigned this profile.
Time Zone Select the time zone for the users assigned this profile.
6. Click Save. The Salesforce Connector creates a user in Oracle CPQ which uses the preferences settings as entered
above.
7. (Optional) Log in to CPQ as an administrator and verify the user was created.
Notes:
After the user has been initially provisioned, you can return to this page to modify the user preferences at any time.
Each change gets synchronized to Oracle CPQ when you click Save.
If you receive an error, verify that you have proper permissions.
When a user is created in CPQ, the username is automatically generated based off the Salesforce username. With
this in mind, duplicate usernames for CPQ could occur.
2. Click on the username you want to update. The User page displays.
3. Click Edit from the User Detail panel to modify Salesforce and Oracle CPQ user details.
OU Section - Edit
6. Click Save.
Notes:
If a user is unable to create quotes, ensure that the Allow Quote Creation checkbox is selected.
If you have multiple Oracle CPQ sites or processes connected and a user has access to more than one site, they are
prompted to select the quote type when creating a quote.
Natively rendering the CPQ Lightning Transaction UI inside the Salesforce Lightning Experience
In this section, we briefly describe the different combinations and provide guidance on selecting the best option for your
business needs.
If you have not yet enabled the JET Transaction UI in CPQ for the logged in user, they will automatically see the Legacy
Transaction UI when they access CPQ.
This combination of the Salesforce Classic UI and the CPQ Legacy Transaction UI is well established and is the experience that
existing customers is most familiar with. This was the only experience available in older versions of the integration (managed
package v7 and earlier).
When using this mode you are limited to using the CPQ features that are supported in the Legacy Transaction UI. You can
customize the Legacy Transaction UI using the Layout Editor, CSS, and JavaScript to improve the experience for the sales
users.
If you have enabled the JET Transaction UI in CPQ for the logged in user, they will automatically see the JET Transaction UI
when they access CPQ.
This combination of the Salesforce Classic UI and the CPQ JET Transaction UI is a new option made available when the JET
Transaction UI was released.
If you are not planning to transition to the Lightning Experience in Salesforce at this time, this mode is the only mode you are
using if you have not adopted the JET Transaction UI in CPQ.
When using this mode, you have access to all the features supported by the JET Transaction UI. You can customize the JET
Transaction UI using the Layout Editor, CSS, and JavaScript to improve the experience for sales users.
If you have not yet enabled the JET Transaction UI in CPQ for the logged in user, they will automatically see the Legacy
Transaction UI when they access Oracle CPQ.
This combination of Salesforce Lightning Experience and the CPQ Legacy Transaction UI is a new capability available to
customers using the Salesforce Connector (managed package v8 or later). This gives existing CPQ customers who have
already invested in building out the Legacy Transaction UI a fast and easy path to using Oracle CPQ with Lightning.
When using this mode you are limited to using the CPQ features that are supported in the Legacy Transaction UI. You can
customize the JET Transaction UI using the Layout Editor, CSS, and JavaScript to improve the experience for sales users.
If you have enabled the JET Transaction UI in CPQ for the logged in user, they will automatically see the JET Transaction UI
when they access Oracle CPQ.
This combination of the Lightning Experience and the CPQ JET Transaction UI is a new capability available when using the
Salesforce Connector (managed package version 8 or later). This allows you to combine the newest CPQ UI, along with all the
new features being added to JET, with Salesforce’s latest features only available in Lightning.
When using this mode you have access to all the features supported by the JET Transaction UI. You can customize the JET
Transaction UI using the Layout Editor, CSS, and JavaScript to improve the experience for sales users.
The Lightning Transaction UI is a natively rendered UI that is provided by Oracle. It is built using Lightning Components and
the Lightning Design System and is dynamic and fully responsive. The layout, attributes, and actions displayed on the page
are all defined and managed from inside Oracle CPQ.
This combination of the Lightning Experience and the CPQ Lightning Transaction UI provides the most seamless experience
for users seeking a “native” CPQ experience within Salesforce. All the UI elements that users interact with share the same
technology as those provided for any standard Salesforce object.
When using this mode you are limited to using the CPQ features that are supported in the Lightning Transaction UI. See
Comparison of the CPQ Connector for Salesforce and the Salesforce Commerce Integration for a list of features that are not
supported in the Lightning Transaction UI. You cannot customize the styling and behavior of the Lightning Transaction UI
using CSS or JavaScript.
Note: If the user does not have access to these toggles, contact your Salesforce administrator.
To switch to Classic mode from the Lightning Experience, complete the following steps:
To switch to the Lightning Experience from Classic mode, complete the following step:
Helpful Tips
Below are useful time saving tips or advice directly from our developers and QA testers to help you configure the most
efficient system integration using the Oracle Adapter for Salesforce Lightning.
TIP DESCRIPTION
The Transaction Name attribute in Oracle CPQ should be the same size
To avoid the truncation of Quote
as the Quote Name field on the Oracle Quote (Max. 80 chars).
Name in the Oracle Adapter
Troubleshooting Issues
If you are encountering a problem the table below may have a solution to your issue.
Authorization Certificate has More than likely, it has been two (2) years since your Salesforce org’s
Expired. certificate was last authorized with Oracle CPQ using OAuth 2.0 Security.
These certificates are good for two years and then must be renewed.
The solution is to authorize a new certificate and is described Create a
Certificate.
Note: Before you officially switch over to a new certification (and its new
keychain record), we highly recommend that you perform this first in a
sandbox.
When entering CPQ site settings Verify that the Certificate Name is an exact match for the one provided
information, you get a "405" error via My Oracle Support .
when connection to CPQ.
One or more users are not unable The following may be causes of this issue:
to generate a Salesforce token from • The affected user's Salesforce profile does not allow the proper IP
Oracle CPQ. addresses for Oracle CPQ. Add the Oracle CPQ IP addresses to the
affected user's profile.
• The Connected App set up in Salesforce does not have the
Salesforce user's profile approved within it. If the profile is not
approved, requests to generate tokens will not go through.
To resolve the Connected App, perform the following:
1. Within Salesforce, navigate to Setup > Create > Apps.
2. Open the Connected App associated with the CPQ
environment.
3. Click the Manage button.
4. Under the Profiles section, click Manage Profiles.
5. Add the user's profile to the list and click Save.
Blank iFrame or insufficient Contact Salesforce support and request a change to allow OAuth access
privileges error when entering Oracle when logged as another user. When logging the Salesforce case,
CPQ through Salesforce as another justification for this change is required.
user.
Communities users cannot create Administrators should verify the Default External Access policy is not set
quotes but internal users are able to to Private for the CPQ Site Settings and Oracle User objects. If it is set
create quotes. Private, it should either be set to Public or another sharing policy should
be defined for community users to gain access.
Mark Quote as Active fails and If you receive a Salesforce non-zero error when you attempt to mark a
generates an Error quote as active, this may be caused by using zero (0) as the quantity for
a line item. Even though Oracle CPQ allows a zero (0) quantity as a line
item (e.g., subscription for 12 months), Salesforce does not. Salesforce
has a non-zero quantity rule for Opportunity products and does not add
products if a quantity is set to zero (0).
To avoid this, when adding products to your quote, do not use zero (0)
as a quantity.
Quote Names are Truncated. To avoid this, the Transaction Name attribute in Oracle CPQ should be
the same size as the Quote Name field on the Oracle Quote (Max. 80
chars).
Administrator does not receive Navigate to Salesforce Setup and search for Batch Jobs to review any
error messages when attempting to error messages that may have been received during the user creation
create a new CPQ User. process.
User sync fails. Verify the administrator has the required permission settings and
CPQ administrator groups as specified in User Sync.
Permission errors Verify that your user has been synchronized to CPQ.
An error is present in the Locate the integrations that run on that particular action (for example,
Embedded mode. including the Lightning Sync Action’s modify for New) and use the
integration debugger from within Oracle CPQ’s Admin interface.
When trying to create a new quote, Check that the certificate has been added successfully and that the
you get an error similar to "Data Not unique name for the certificate in Salesforce settings matches the value
Available" or "403" errors. entered in the CPQ Site Settings exactly. The value is case sensitive.
The Embedded UI loads a blank On the Connected App, set the Permitted Users to “Admin approved
frame. users are pre-authorized” and add the CPQ permission sets as approved
for the Connected App.
When adding a line item or If you receive a white screen and error message similar to
reconfiguring the canvas, you receive a “error=redirect_uri_mismatch&error_description…”, follow the Add CPQ
white screen and error message. Environment to CORS Allow List and Add CPQ Environment to CSP
Allow List procedures and ensure that the CPQ site URLs are entered
correctly.
Line Item Ordering is not enabled Verify that the site has been provisioned with the latest Oracle CPQ
(_sequence_number attribute Reference Application for Salesforce. Refer to the Oracle CPQ Connector
enabled). for Salesforce Upgrade and Migration Guide for instructions.
Unable to view recordView If you are not able to view the recordView component when building a
component when creating a new new Lightning App, you may need to deploy your previously created My
Lightning page in the Lightning App Domain.
Builder.
Parts Sync doesn’t work. Review the export parts, verifying the required field mappings are
correct.
The Lightning Sync Action creates Confirm you are using the correct Integration for the Lightning Sync
two objects within the Salesforce Action. Reusing the Save Action integrations can cause this issue.
Opportunity: one blank Quote and one
Quote with the details saved post-
creation.
“Apex heap size too large" error Salesforce enforces an Apex Heap Size Limit of 6MB for synchronous
transactions. The "Apex heap size too large" error occurs when too
much data is being stored in memory during processing. In some cases
when setting up Lightning Mode for a very large Commerce Process this
error can occur when generating the CPQ Site Settings. This can be
resolved by reverting to Embedded Mode or deleting actions and
attributes from your process.
If you do not see a solution to your issue, you can Log an Oracle CPQ Connector for Salesforce Service Request.
Sandbox Testing
Always upgrade in a Salesforce sandbox and test the instance of Oracle CPQ before installing into production.
Note: Previous versions of these packages are expected to continue to function; however Oracle will not address new
issues that arise. We strongly encourage customers to upgrade to the latest supported version.
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 Online Help to become familiar with the new features introduced in Oracle CPQ. 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 or the Oracle CPQ Consulting team.
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, CPQ Site Settings, or global function settings. Modifications to integration XSL files or APIs may also
be required.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to
us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the
following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs,
including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms
and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in
any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in
dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use.
Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle
and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks
of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for
any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.