Академический Документы
Профессиональный Документы
Культура Документы
OVERVIEW .............................................................................................................................................................5
PREREQUISITES ......................................................................................................................................................6
INSTALLATION ..................................................................................................................................................... 12
AUTHENTICATION ................................................................................................................................................ 13
3
REVISION HISTORY
This document will continue to evolve as existing sections change and new information is added.
All updates appear in the following table:
4
OVERVIEW
This document introduces the new Oracle CPQ Connector for Salesforce signifying the next generation
of CPQ and Salesforce integration. This is commonly referred to as the “managed package”. This
solution allows users to create quotes in CPQ from within Salesforce, securely synchronizes data
between the systems, and includes support for Salesforce Classic, Salesforce Lightning, Salesforce
Mobile and Salesforce Communities.
This document 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 Salesforce Connector) and the process to setup all
integration modes. Before you begin, be sure to read the Prerequisites section.
The Oracle CPQ Connector for Salesforce is comprised of two new managed packages:
IMPORTANT: Customers currently using an older version of this integration (managed package v7 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
cpqcloud_documentation_us_grp@oracle.com.
5
PREREQUISITES
In order to successfully install and use the new Oracle CPQ Connector for Salesforce, there are a few
pre-requisites to be aware of which are listed in the table below.
IMPORTANT: This document assumes that the site has been provisioned with the latest CPQ Cloud
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.
6
CHECK THE CPQ CLOUD AND REFERENCE APPLICATION VERSIONS
Before you begin it is important to check the version of the Reference Application applied to your CPQ
site. This section provides the steps to retrieve the Ref App version and the Catalog of Ref App
elements. This provides a more detailed view of the initial state of your site.
To locate the CPQ Cloud version information, complete the following steps:
5. Click Back.
7
LOCATE THE REFERENCE APPLICATION INFORMATION
When a CPQ Cloud site is provisioned, the Ref App is pre-loaded into the environment. In addition, files
are added to the File Manager which indicate the version of the Ref App that is provisioned and describes
the change history for the Ref App. These files are used to identify if your site requires updating to connect
to the latest managed package.
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.
8
6. Review the Oracle CPQ Cloud 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.
ENABLE MY DOMAIN
Enabling My Domain is required when using Lightning. This keeps your data more secure and ensures
that you are able to access Salesforce features which require a registered domain. If you have not
already set up My Domain, you must complete that process before you should continue with the setup
and installation procedures in this document.
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, interact in support communities, and take advantage of proactive
capabilities for managing systems. Throughout the installation and setup of the Oracle CPQ Connector
for Salesforce, you are directed to open a Service Request (SR) on My Oracle Support. This section
includes the following:
In order to log an Oracle Service Request (SR), you must have a Support Account with a registered
Support Identifier (SI). An SI identifies the products that your company has purchased and the level of
support that you are entitled to. The SI is included in the welcome letter sent from Oracle to the
technical contact listed in your company’s contract.
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.
9
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.
Administrators need to open Service Requests (SR) during the installation and setup of the CPQ
Cloud/Salesforce integration. When opening an SR, it is important to provide all the relevant
information required to ensure the Oracle support team is able to address the ticket in a timely fashion.
IMPORTANT: 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 Summary A short description of the problem.
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
• CPQ Cloud 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.
10
7. Select Integration and Salesforce from drop down for the Problem Type.
11
INSTALLATION
There are two (2) managed packages to install in order to begin using the Oracle CPQ Connector for
Salesforce.
The password for the Oracle CPQ Connector for Salesforce package is Ttr9i0Sj
The password for the Oracle CPQ Extension for Salesforce package is bO5vN7UH
For instructions on these Salesforce procedures, refer to the Salesforce online article Install a Package.
IMPORTANT:
• 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.
12
AUTHENTICATION
Now that you have installed the two new managed packages for the Oracle CPQ Connector for
Salesforce, there are additional setup procedures required to enable your Salesforce org and CPQ Cloud
site to communicate securely.
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.
This section provides instructions for preparing Salesforce to authenticate with CPQ Cloud by creating a
remote site and a certificate. Creating a remote site saves and registers the URL for the CPQ Cloud site
within Salesforce. Once the remote site is established, an encrypted certificate is required to be
downloaded and registered with CPQ Cloud.
IMPORTANT: The certificate is valid for two (2) years. After 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.
Before the Salesforce Connector can call out to your CPQ Site, that site must be registered in the
Remote Site Setting page in your Salesforce environment.
To register your CPQ Cloud site as a remote site, complete the following steps:
1. Navigate to Setup > Security Controls > Remote Site Settings. The All Remote Sites page
displays.
13
2. Click New Remote Site. The Remote Site Edit page displays.
3. Enter the following values to create a setting for your CPQ environment.
Attribute Value
Remote Site Name Variable name for this setting
Remote Site URL https://<cpq_site_url>
Disable Protocol Security Unchecked
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
Remote Site Name Variable name for this setting
Remote Site URL https://<your_domain>.my.salesforce.com
Disable Protocol Security Unchecked
Description (Optional)
Active Checked
3. Click Save. The new Salesforce org domain name site appears in the list on the All Remote Site
page.
14
ADD CPQ ENVIRONMENT TO CORS WHITELIST
Salesforce requires Cross-Origin Resource Sharing (CORS) security protocol when working with the
Oracle CPQ Connector for Salesforce application. CORS enables secure communication when using a
browser-based programming language to access content from another domain.
To add the CPQ environment to CORS whitelist, complete the following steps:
1. Navigate to Setup > Security Controls > CORS. The CORS page displays.
3. Enter your CPQ environment instance URL (for example, https://<cpq_site_url>) in the
Origin URL text box.
4. Click Save.
15
ADD CPQ ENVIRONMENT TO CSP WHITELIST
Salesforce requires Content Security Policy (CSP) protocol when working with the Oracle CPQ Connector
for Salesforce application. CSP is an added layer of security that help to protect against data theft and
distribution of malware.
To add your CPQ environment to the CSP whitelist, complete the following steps:
1. Navigate to Setup > Security Controls > 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
Trusted Site Name Variable name for this setting
Trusted Site URL https://<cpq_site_url>
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.
16
To add your Salesforce My Domain to the CSP whitelist, complete the following steps
2. Enter the following values to create a trusted site for your Salesforce org’s custom “My Domain”
URL.
Attribute Value
Trusted Site Name Variable name for this setting
Trusted Site URL https://<your_domain>.my.salesforce.com
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
Create a self-signed certificate that is loaded into your CPQ Cloud site by Oracle support. For more
information, refer to the Salesforce article called Generate a Self-Signed Certificate.
17
To create a certificate, complete the following steps:
18
IMPORTANT:
• 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.
8. A prompt asking if you want to save a .crt file. The certificate (created by you) is downloaded to
your default download folder.
9. If prompted, click Save File.
19
IMPORTANT: If you are connecting multiple Salesforce environments to your CPQ site, you need to
upload this certificate to each additional Salesforce environment.
If you are going to connect more than one Salesforce instance to CPQ, you need to export the certificate
file. To export the file, complete the following steps:
1. Navigate to Setup > Security Controls > Certificate and Key Management.
4. Click Export.
5. Save the file to your system to import that Keystore into each additional Salesforce environment
that will connect to your CPQ site.
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 CPQ Cloud.
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.
20
SETUP SALESFORCE FOR OAUTH 2.0
In this section, you create a Connected App to authorize and bind your Salesforce org to your CPQ Cloud
site using OAuth 2.0 protocol. In order to do this, you will perform the following three steps which are
outlined in their own sections called:
For more information on Connected Apps using OAuth 2.0, refer to the Salesforce online help article
Connected Apps Overview.
IMPORTANT: These steps assume that you are creating a Connected App for your CPQ Cloud 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.
Part of the integration process requires the creation of a Connected App that allows CPQ Cloud to be
loaded in a canvas inside Salesforce. Once you define your Connected App, you will provide the
consumer key and consumer secret to Oracle to be used to generate access tokens for each user.
2. Click New within the Connected Apps section. The New Connected App page displays.
21
3. 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
22
4. Enter the following required API (Enable OAuth Settings) values to enable the OAuth settings
for the new Connected App. All other fields in API (Enable OAuth Settings) are optional.
Attribute Value
Enable OAuth Settings Checked
Callback URL https://<site _domain>/admin/oauth2/salesforce/oauth_callback.jsp
Selected OAuth Scopes Add the following:
• Full access (full)
• Perform requests on your behalf at any time (refresh_token,
offline_access)
23
5. Enter the following required Canvas App Settings values to set up the Salesforce canvas app for
the new Connected App. All other fields in Canvas App Settings are optional.
Attribute Value
Force.com Canvas Checked
Canvas App URL https://<site _domain>/admin/oauth2/salesforce/oauth_callback.jsp
Access Method OAuth Webflow (GET)
24
6. Click Save. The Apps Setting 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.
IMPORTANT: Refer to the Salesforce article Create a Connected App for more information.
The security integration process requires your Consumer Key and Consumer Secret.
1. Navigate to Setup > Create > Apps and go to the Connected Apps section.
Connected Apps
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 CPQ Cloud and Salesforce
environments when performing the Provide Salesforce Security Settings to My Oracle Support
procedure.
25
PROVIDE SALESFORCE SECURITY SETTINGS TO MY ORACLE SUPPORT
Once you have gathered the Certificate file, Consumer Key and Consumer Secret, you can finalize the
integration process. My Oracle Support must fulfill the support portal ticket in order for the CPQ
Cloud/Salesforce integration can be tested.
IMPORTANT: You must have a Support Account with an approved Support Identifier (SI) to log a
Service Request (SR).
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.
4. Enter the Consumer Secret into the Salesforce Consumer Secret field.
5. Upload the Certificate file (see Create a Certificate). For help on uploading a file, refer to Oracle
online help Working with Service Requests.
Once the Service Request in the previous section has been fulfilled, connect the Integration User (typically
a SuperUser or dedicated integration user in CPQ) to their corresponding Salesforce user account
(typically a system administrator or a dedicated integration user).
Each integration user individually follows the steps in the next section to pair their logins by generating a
security token for each user. You typically perform this step for your administrator account first.
IMPORTANT:
• Do not proceed with this process until CPQ Cloud 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.
26
PAIR INTEGRATION USER AND GENERATE TOKEN
The first step for integrating users is to pair the user accounts across systems. This is done by entering
the Salesforce username that corresponds to the CPQ user on the User Integration page. If you do not
currently have a user account in both systems, create a user account in each before continuing or
contact your system administrator.
Once users have been paired, a user token must be generated before those users are allowed to SSO
from Salesforce in to CPQ Cloud. User tokens are employed to designate the connection between a
common user in both the Salesforce and CPQ Cloud systems.
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. In this section, we describe how to manually generate the
token.
IMPORTANT: 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 Cloud 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
IMPORTANT: The My Profile icon and location may vary based on your CPQ site configuration.
27
3. Click User Integration.
6. Log in to Salesforce with the credentials for the user account you want to integrate.
Salesforce Login
28
7. You may be prompted to allow your Salesforce Org Connected App access to your CPQ
environment. Click Allow.
The User Integration page displays with confirmation that the Token Generated
IMPORTANT: 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 CPQ Cloud from Salesforce with a
user that has not been integrated, they will see errors when trying to open quotes.
29
VERIFY INTEGRATION USER PARTNER LOGIN
Once the User login is bound together, verify the partner login by completing the following steps:
https://<site_domain>/admin/oauth2/salesforce/oauth_callback.jsp?redirect_url=https://
<site_domain>/partner_login.jsp&bmGetParams=state:https%3A%2F%2F<site_domain>%2Fpartne
r_login.jsp
Partner Login
IMPORTANT: 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 CPQ
Cloud.
30
PERMISSIONS AND PAGE LAYOUTS
You must assign the new admin permission sets to your own profile. Only then can you access and
configure the components of the managed packages. Once you have access to the components you
must expose them by adding them to the Page Layouts.
You must assign the new admin permission sets to your own profile in order to access and configure the
Oracle CPQ Connector for Salesforce within Salesforce.
Upon completion of the installations, you will notice new permission sets when viewing the Permission
Sets page in Salesforce (Setup > Manage 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 > Users > and click on your username to access your user profile.
2. Scroll down to the Permission Sets Assignments list and click Edit Assignments. The Permission
Set Assignments page displays.
31
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.
4. Click Save. The newly added permission sets appear in the Permission Set Assignment list within
your user profile.
These Admin permissions grant access rights to the objects listed in the following table.
32
SETUP PAGE LAYOUTS
Now that you have access to the new objects, you must expose these objects in the Salesforce User
Interface. There are four areas to consider:
• Create the Lightning Page for the Oracle Quotes and Line Items
You are required to update the Record view using the Lightning App Builder to remove any declarative
content and display the Oracle CPQ Connector for Salesforce content.
33
4. Click Next.
7. Click Next.
8. From the Choose Page Template sidebar, select One Column for the template.
9. Click Finish.
34
10. From the Lightning Components sidebar, under Custom, drop and drag the recordView
component into the view.
IMPORTANT: If you are not able to view the recordView component, you may need to deploy your
previously created My Domain.
35
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.
IMPORTANT: Refer to the Lightning App Builder online help for additional assistance.
36
UPDATE THE OPPORTUNITY PAGE LAYOUT
Once you are ready to begin testing and using the Salesforce Connector, you will want to add the Oracle
Quote related list to your Opportunities and Account pages and override the standard Quote record page
with the Oracle Quote page.
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 > Customize > Opportunities > Page Layouts. The Opportunity
Page Layout page displays.
37
4. Drag and drop the Oracle Quotes related list from the top section to the first available spot
underneath the heading of the Related Lists section.
5. Click the icon in the tab for the Oracle Quotes section. The Related List Properties – Oracle
Quotes section displays.
38
6. 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.
7. Select the field you want to sort by from the Sort By drop-down.
8. Specify whether you want the values to display in Ascending or Descending order.
9. View the Buttons section of the page by selecting the Expand icon.
39
10. Unselect the New checkbox within the Standard Buttons section. This is necessary in order to
ensure that the toggle feature works as expected and keep information in sync between
Salesforce and Oracle Connector for Salesforce.
11. Move the buttons you want to display into the Selected Buttons area using the Add and
Remove arrows within the Custom Buttons section.
14. Repeat these steps for the Account Page Layout and any additional layout that users have the
ability to access or click Close.
The Salesforce Connector adds a new object called the Oracle User which contains settings and
preferences for each user that to be provisioned and synced to CPQ Cloud. In order to access this object,
you must add an inline Visualforce page to the standard Salesforce User Layout.
To add the Oracle User Layout to the user record layout, complete the following steps:
3. Click Edit Layout from the User panel to add a Visualforce page for the specified user.
5. Click and drag a Section to move it onto the User Layout page. We recommend naming this
section the Oracle User section.
40
6. Click and drag the OracleUsers page to move it into the section you just created.
41
7. Hover the cursor over the newly placed page and click the icon. The Visualforce Page
Properties displays.
• New Section
• Single Column Layout
• Width 100%
• Height minimum of 500 pixels
• Show scrollbars
9. Click OK.
IMPORTANT: Refer to User Sync for additional detail on configuring Oracle users.
42
SETUP MOBILE OVERRIDES
If you intend to use the Oracle CPQ Connector for Salesforce in the Salesforce mobile app, you must
override the Salesforce standard action buttons and give access to the Salesforce Connector.
Custom Objects
43
3. Scroll to the Button, Links and Actions section and click the Edit link. The Override Properties
page displays.
4. Select the Lightning Experience Override, Use the package default override radio button.
5. Select the Mobile Override, Use the package default override radio button.
6. Click Save.
44
7. Scroll to the Button, Links and Actions section and click the View link. The Override Properties
page displays.
8. Select the Lightning Experience Override, Lightning component radio button and set the drop-
down list to namespace:recordView.
9. Select the Mobile Override, Lightning component radio button and set the drop-down list to
namespace:recordView.
45
INTEGRATION SETTINGS
In order to sync data between CPQ Cloud and Salesforce, you must set up the relationships between the
objects and fields that are used in each system. Some of these settings are managed in CPQ Cloud and
other in Salesforce. The following sections walk you through the set up within each system.
IMPORTANT: The following sections assume that the CPQ site has been provisioned with the latest CPQ
Cloud 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.
The CPQ Site Settings page, that is part of the managed package, is a form filled out by the
administrator. Data specific to your environments is entered, such as the Callout URL and Mapped
Fields. This initial setup allows you to quickly connect your CPQ Cloud and Salesforce environments.
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 CPQ Cloud.
IMPORTANT: 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.
Before entering the CPQ Site Settings, you must retrieve the Version ID from CPQ for the Commerce
Process that you want to pair to Salesforce.
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.
46
6. Record the version_id information. This information is needed to create site settings.
When your sales users are creating a new quote from within Salesforce, they are directed to a CPQ
Cloud Site and Commerce Process. The CPQ Site Settings store the site details such as, the site URL,
action IDs, and other process-specific details. Additionally in the site settings, you can configure certain
features that are part of the Salesforce Connector.
To create your CPQ Site Settings using the Site Settings Wizard, complete the following steps:
1. In Salesforce, select the Sales drop-down and click Oracle CPQ Extension.
47
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.
IMPORTANT: 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.
4. Enter the connection information for the fields. Refer to the table below for field information.
48
CPQ Site Settings Field Purpose/Description
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.
5. Click Next. The CPQ Site Settings Step 2: Process Details displays.
6. Enter the process details for the fields. Refer to the table below for field information.
49
7. Click Next. The CPQ Site Settings Step 3: Adapter Settings displays.
IMPORTANT: Select Use Embedded Transaction in Lightning for your initial set up. You can switch to
Lightning Mode after the initial set up is complete.
8. Enter the adapter settings values for the fields. Refer to the table below for field information.
50
IMPORTANT: If your CPQ Cloud site was not provisioned with the latest CPQ Cloud 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.
10. Click Save. The page refreshes and the Deploy Site button appears.
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.
IMPORTANT: 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.
51
REVIEW CPQ COMMERCE PROCESS INTEGRATIONS
Oracle CPQ Cloud supports a point-to-point integration where CPQ Cloud actions can import or export
data from Salesforce. Each integration performs a specific task associated with a specific action. In this
section, we review the Commerce Process Integrations provided in the Salesforce Reference Application
to ensure they are setup properly.
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.
Processes Page
4. Click List.
52
5. Review the Integrations available.
Process Integrations
The integrations in the latest Ref App are listed in the following table.
53
Process Integrations Description
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.
Attach Document Salesforce: Exports a file specified on an Export Attachment action to
the Notes & Attachments list of the Salesforce record associated to
the Transaction.
6. If the integrations listed match the latest Ref App list, proceed to the next section.
IMPORTANT: If your CPQ Cloud site was not provisioned with the latest CPQ Cloud 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.
54
REVIEW CPQ ACCOUNT INTEGRATIONS
Oracle CPQ Cloud supports a point-to-point integration where CPQ Cloud actions can import or export
data from Salesforce. Each integration performs a specific task associated with a specific action. In this
section, we review the Account Integrations that are provided in the Salesforce Reference Application to
ensure they are setup properly.
Accounts Page
Account Integrations
55
4. Review the Integrations available.
The integrations in the latest Ref App are listed in the following table.
5. If the integrations listed match the latest Ref App list, proceed to the next section.
IMPORTANT: If your CPQ Cloud site was not provisioned with the latest CPQ Cloud Reference
Application, the Account 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 Account Integrations.
56
REVIEW CPQ PARTS INTEGRATIONS
Oracle CPQ Cloud supports a point-to-point integration where CPQ Cloud actions can import or export
data from Salesforce. Each integration performs a specific task associated with a specific action. In this
section, we review the Parts Integrations that are provided in the Salesforce Reference Application to
ensure they are setup properly.
57
3. Click Integration. The List Integrations page displays.
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:
58
If CPQ Cloud is assigned as the Parts Master, the following integrations are available:
5. If the integrations listed match the latest Ref App list, proceed to the next section.
IMPORTANT:
If your CPQ Cloud site was not provisioned with the latest CPQ Cloud 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 Parts Integrations.
59
REVIEW INTEGRATION TAB SETTINGS ON CPQ CLOUD COMMERCE ACTIONS
Commerce Process Integrations and Account Integrations are triggered when Commerce actions are
executed. Sometimes these integrations are executed when a sales user clicks a button and other times
they run automatically. In this section, we review the Commerce actions that are provided in the
Salesforce Reference Application to ensure they are setup properly.
The Auto Fill Options are set at the process level and dictate what address information is used to auto
fill the address attributes on your quote when a new quote is created. When integrated with Salesforce,
the Account Integration retrieves this information from the CRM when the Accounts Information is
selected. The fields retrieved are mapped on the Refresh Address action on the Main Document.
2. Click Process Definition under Commerce and Documents. The Processes page displays.
3. Click the Name of the process. The Process Administration page displays.
60
4. In the Auto Fill Options drop-down, verify Accounts Information is selected.
Integrations set up on the Process Administration page run when new quotes are created.
2. Click Process Definition under Commerce and Documents. The Processes page displays.
61
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.
The Open Transaction Process Action runs each time a quote is opened. Integrations set on the Open
Transaction action retrieve data from Salesforce and update corresponding values on the quote.
To verify the Open Transaction Integration tab, complete the following steps:
2. Click Process Definition under Commerce and Documents. The Processes page displays.
62
3. For the process you want to verify, select Process Actions from the Navigation drop-down.
5. Click on the Open Transaction link from the Action Name column. The Admin Action page
displays.
63
7. Review the Integrations and verify the following integrations are selected and sequenced in the
following order.
The Refresh Address Action runs each time a quote is created when the Account Information Option is
selected as an Auto Fill Option on the process. It also runs when the Refresh Address button is clicked by
a sales user on the quote. When run, this action invokes the Account Integration. On the Refresh
Address Action, you must verify that the proper account integration is selected.
To verify the Refresh 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.
64
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.
65
9. Verify Account Import is selected under CRM Mapping.
The Return to Opportunity Integrations run when the Return to Opportunity button is clicked by a sales
user on the quote. This integration updates the Oracle Quote and Oracle Quote Line Items records in
Salesforce with the latest quote details.
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.
66
7. Click on the Return to Opportunity link under the Action Name column.
9. Review the Integrations and verify the following integrations are selected and sequenced in the
following order.
67
Selected Integrations Description
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 Salesforce: Creates or updates Oracle Quote Line Items on the Oracle
(Export) 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.
IMPORTANT: 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.
The Return to Account Integrations run when the Return to Account button is clicked by a sales user on
the quote. This integration updates the Oracle Quote and Oracle Quote Line Items records in Salesforce
with the latest quote details.
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.
68
5. For the Document you want to verify, select Actions from the Navigation drop-down.
7. Click on the Return to Account link under the Action Name column.
9. Review the Integrations and verify the following integrations are selected and sequenced in the
following order.
69
Selected Integrations Description
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 Salesforce: Creates or updates Oracle Quote Line Items on the Oracle
(Export) 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
(Export) CPQ Connector know that the upsert is complete. This triggers all the
Salesforce-side updates to the Oracle Quote and Opportunity.
IMPORTANT: 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.
The Select an Alternative Address Integrations run when the Select an Alternative Address button is
clicked by a sales user on the quote. When run, this action invokes the Contact Integration. On the
Select an Alternative Address Action, you must verify that the proper account integration is selected.
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.
70
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.
7. Click on the Select an Alternative Address link under the Action Name column.
71
8. Click on the Integration tab.
The Lightning Sync Integrations are triggered when the Lightning Sync Action is run. The Lightning Sync
Action is triggered by the Lightning UI as part of the New Quote flow. It is not used when Embedded
mode is turned on. The Lightning Sync action updates the Oracle Quote in Salesforce with the external
ID for the Transaction in CPQ.
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.
72
5. For the Document you want to verify, select Actions from the Navigation drop-down.
7. Click on the Lightning Sync link under the Action Name column.
73
9. Review the Integrations and verify the following integrations are selected and sequenced in the
following order.
The Salesforce Connector allows a sales user to mark an Oracle Quote as the primary quote which
triggers a synchronization of lines from the attached Oracle Quote to the Opportunity.
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.
IMPORTANT: This feature does not apply to a Quote created from Accounts.
74
MAPPING OPPORTUNITY PRODUCT FIELDS TO ORACLE QUOTE LINE ITEM FIELDS
In order to ensure that your Opportunity Forecasts and Reports are accurate, you must sync your Quote
Line Items to your Opportunity as Opportunity Products. Line items are synced to the Opportunity when
the specified quote is marked as Active. When a quote is marked as active, any changes to that quote
are always reflected on the Opportunity and the Opportunity Products.
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.
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.
75
2. Click on the Field Mappings tab. The Recent Field Mappings page displays.
Field Description
Field Mapping Name Name for the field mapping.
Data Set Data set that this mapping will affect.
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.
76
MAPPING OPPORTUNITY FIELDS TO ORACLE QUOTE FIELDS (OPTIONAL)
You may have information on the quote that you want to track at the opportunity level. To update that
information from the active quote, you must create Field Mappings for those fields.
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.
77
3. Click New. The New Field Mapping page displays.
Field Description
Field Mapping Name Name for the field mapping.
Data Set Data set that this mapping will affect
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.
IMPORTANT: In a later section, we will explain how values from the Transaction in CPQ Cloud get saved
to the Oracle Quote and Oracle Quote Line Items records in Salesforce. You may need to create new
custom fields on those objects which may be added to the field mappings later.
78
PARTS SYNC
In order to create Opportunity Products as part of your Opportunity and Quote synchronization, those
products must exist in both Salesforce and CPQ Cloud. This also establishes a master product list that
prevents duplicate product data and ensures consistent pricing. CPQ Cloud provides parts
synchronization capabilities that allow you to import products from Salesforce or to export parts from
CPQ Cloud. These features include creating or updating both products and pricing information.
Determining the system as your Parts Master is a choice that administrators must make when designing
the initial setup of the system. By default the Salesforce Reference Application, as provisioned with all
new Salesforce-integrated CPQ Cloud sites, assigns Salesforce as the Parts Master. When Salesforce is
the Parts Master, parts integrations import product and price information from Salesforce to CPQ Cloud.
If you choose CPQ Cloud as the Parts Master, parts integrations export product and price information to
Salesforce. Your specific business process should drive the decision of the Parts Master selection.
Generally, we recommend using Salesforce as your Parts Master.
IMPORTANT: 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.
2. IMPORTANT: To view the Parts Integration Settings page, you must be logged in as SuperUser.
5. Under the Item Master section, the selected Parts Master displays. The two available options
are:
79
7. (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 CPQ Cloud is
the Parts Master, the following integrations are listed: Export Parts, Export Part Extended
Descriptions, and Export Price Book Entries.
SYCHRONIZING 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 CPQ Cloud 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.
• Each part integration has a Delta option which when selected limits the integration to only
update changed parts. When unselected, all parts are updated.
• 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 CPQ Cloud sites are setup to integrate with one Salesforce instance, you can use
multiple CPQ Cloud 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.
All products in Salesforce must be contained in at least one Price Book. This Price Book is usually the
standard Price Book but this may vary depending on your implementation. Often customers use
multiple Price Books to organize their products and segment their pricing. Before you can sync parts,
you must manually map each Price Book ID from Salesforce to the corresponding Price Book in CPQ.
80
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.
When Salesforce is the Parts Master, part sync creates new parts in CPQ Cloud. In order to create a part
in CPQ Cloud, you must supply a unique value for the Part Number attribute. Before you can import
parts from Salesforce, you must supply this unique value for the integration. The Salesforce Connector
includes a field called Oracle CPQ Part Number on the Product object for this use. You must populate
this value for every Salesforce product.
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.
IMPORTANT: The steps above assume Salesforce is the Parts Master. If CPQ Cloud is the Parts Master,
the Oracle CPQ Part Number field is populated by the parts export.
81
IMPORT PARTS
Now that you have mapped your Price Books and populated the Oracle CPQ Part Number, you are ready
to import parts from Salesforce to CPQ Cloud. Importing parts from Salesforce creates new parts in CPQ
Cloud if they do not already exist and updates existing parts.
IMPORTANT: If you have selected CPQ Cloud as the Parts Master, the steps outlined in this section are
similar for exporting Parts to Salesforce.
IMPORTANT: If your SuperUser has not already been integrated, you need to click Partner Login to
connect to Salesforce prior to syncing parts.
82
5. Select the Import Parts 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.
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.
IMPORTANT: You may need to modify the XSL templates for this integration if you are using custom
attributes, multiple currencies, or other customizations.
83
IMPORT PART EXTENDED DESCRIPTIONS (OPTIONAL)
The Part Extended Descriptions attributes can be used to display additional product details to users. This
section provides steps to import this information from Salesforce.
IMPORTANT:
- If you have selected CPQ Cloud as the Parts Master, the steps outlined in this section are similar for
exporting to Salesforce.
- The part must exist in CPQ Cloud before you can update the Part Extended Description.
To import Parts Extended Descriptions from Salesforce, complete the following steps:
IMPORTANT: If your SuperUser has not already been integrated, you need to click Partner Login to
connect to Salesforce prior to syncing parts.
84
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.
IMPORTANT: You need to modify the XSL templates for this integration to point to the custom fields in
Salesforce that store the Part Extended Descriptions.
Price Book Entries are how Salesforce stores pricing information about their products. CPQ Cloud stores
pricing information differently. This integration imports the Salesforce price information for each
product and transforms it into a format that can be stored in CPQ Cloud.
IMPORTANT:
- If you have selected CPQ Cloud as the Parts Master, the steps outlined in this section are similar for
exporting to Salesforce.
- The part must exist in CPQ Cloud before you can update the Pricing Information for the part.
85
To import Price Book Entries from Salesforce, complete the following steps:
IMPORTANT: If your SuperUser has not already been integrated, you need to click Partner Login to
connect to Salesforce prior to syncing parts.
86
5. Select the Import Price Book Entries 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.
IMPORTANT: You may need to modify the XSL templates for this integration if you are using multiple
price books, multiple currencies, or other customizations.
Once the Parts Master is established and parts are initially set up between CPQ Cloud and Salesforce, it is
important to keep the parts synchronized between the applications.
87
4. Select the specific integration you want to schedule and click Schedule.
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.
88
USER SYNC
Integrated users will have two user accounts—one in Salesforce and one in CPQ Cloud. The User Sync
features allow users to manage their preferences and credentials in one system. It also saves
administrator time by automating the provisioning and pairing of new users. Once users are provisioned
and paired, users are able to Single Sign On (SSO) from Salesforce to CPQ Cloud.
If you have existing users in CPQ Cloud which need to be paired to Salesforce users, you can manually
create the connection. This establishes the relationship between the two user accounts and prepares
them for SSO.
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.
IMPORTANT:
• Do not proceed with this process until CPQ Cloud 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.
89
PAIR USER AND GENERATE TOKEN
The first step for integrating users is to pair the user accounts across systems. This is done by entering
the Salesforce username that corresponds to the CPQ user on the User Integration page. In this section,
we describe how to manually pair users, alternatively you can use the Automatic Provisioning feature.
Most often administrators manually pair a few initial test users and switch to automatic provisioning
when the integration rolls out to the rest of organization. Refer to Automatically Provision CPQ Users
from Salesforce for instructions on the Automatic Provisioning feature.
Once users have been paired, a user token must be generated before those users are allowed to SSO
from Salesforce into CPQ Cloud. 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 CPQ Cloud.
IMPORTANT: 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 Cloud with the Username and Password for the user to be paired.
2. Click the My Profile icon in the Navigation bar at the top of the page.
My Profile Icon
IMPORTANT: The My Profile icon and location may vary based on your CPQ site configuration.
90
3. Click User Integration.
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.
Salesforce Login
91
7. You may be prompted to allow your Salesforce Org Connected App access to your CPQ
environment. Click Allow.
The User Integration page displays with confirmation that the Token Generated
IMPORTANT: If you try to access CPQ Cloud from Salesforce with a user that has not been paired, they
will see errors when trying to open quotes.
92
AUTOMATICALLY PROVISION CPQ USERS FROM SALESFORCE
Automatic provisioning of CPQ users saves administrator time by automating the process of creating
users in CPQ Cloud. There are two scenarios when this feature is very beneficial:
• Creating a user in Salesforce and immediately provisioning the user in CPQ Cloud
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.
IMPORTANT: 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.
Before you can start provisioning your users, you must replicate each of your active CPQ Groups inside
Salesforce. To complete the task, you need to first login to CPQ Cloud to retrieve group variable names
then login to Salesforce to add the group names.
To retrieve Group Variable Names from CPQ Cloud, 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.
93
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.
94
6. In the Groups page, enter the variable names of each CPQ Cloud User Group that you retrieved
from CPQ Cloud. Enter each variable name on a separate line.
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 CPQ Cloud site.
Picklist Values
95
CREATE USER PROFILES (OPTIONAL)
User profiles can be thought of as templates for grouping together common default settings for a set of
similar users. This can be helpful when you have users in different countries who have differing
language and currency preferences. Another scenario for user profile is if users work in different lines of
business and require membership to different groups. Defining user profiles makes it easier for an
administrator to provision users.
1. In Salesforce, select the Sales drop down and click Oracle CPQ Extension.
96
4. Enter the values for the fields for the desired user profile. Refer to the table below for field
information.
5. Click Save.
Once you have defined your user groups and profiles, you are ready to begin automatically provisioning
users in CPQ Cloud.
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.
97
3. Click Edit on the Oracle user record.
4. (Optional) If you have created user profiles, select a Default Profile from the available drop
down. The user settings and preferences automatically populate once the profile is selected.
IMPORTANT: The default profile feature only works when Oracle users are first created. Subsequent
changes to the user preferences must be entered manually.
98
5. (Optional) If you are not using default profiles, fill in the preferences for this user. Refer to the
table below for field information.
5. Click Save. The Salesforce Connector creates a user in CPQ Cloud which uses the preferences
settings as entered above.
6. (Optional) Log in to CPQ as an administrator and verify the user was created.
IMPORTANT:
• 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 CPQ Cloud when you click Save.
• 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.
99
ALLOW QUOTE CREATION
Once users have been provisioned, they must be granted the ability to create quotes in each CPQ site or
process. This is done simply by selecting the Allow Quote Creation checkbox on each Oracle user record.
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 Cloud user details.
User Page
4. Scroll down to the Oracle User Section created in Update the User Layout, click Edit.
OU Section - Edit
100
5. Select or Unselect the Allow Quote Creation checkbox for each connection listed for the user.
When selected, the user is allowed to create quotes for the specified site or process.
6. Click Save.
IMPORTANT:
• If a user is unable to create quotes, ensure that the Allow Quote Creation checkbox is selected.
• If you have multiple CPQ Cloud 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.
101
EMBEDDED TRANSACTION UI VERSUS LIGHTNING TRANSACTION UI
Salesforce currently offers two primary user interface options for their CRM, the Lightning Experience
and the Classic UI. Oracle CPQ Cloud, when integrated with the Oracle CPQ Connector for Salesforce,
supports three Transaction user interfaces: the Legacy, JET, and Lightning Transaction UIs. This results
in different UI combinations for user experiences. Understanding the differences is important when you
begin to roll this out to users.
• 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.
EMBEDDED CPQ LEGACY TRANSACTION UI INSIDE THE CLASSIC UI
Anytime users create or edit Oracle Quotes from Salesforce Classic, the Embedded Transaction UI loads
automatically regardless of which UI mode you have chosen for use in the Lightning Experience. If these
Quotes were created when the Lightning Transaction UI was active, they will always revert to an
embedded experience when the user switches back to Classic.
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).
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 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.
103
EMBEDDED CPQ JET TRANSACTION UI INSIDE THE CLASSIC UI
Anytime users create or edit Oracle Quotes from Salesforce Classic, the Embedded Transaction UI loads
automatically regardless of which UI mode is chosen for use in the Lightning Experience. If these Quotes
were created when the Lightning Transaction UI was active, they always revert to an embedded
experience when the user switches back to Classic.
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.
104
EMBEDDED CPQ LEGACY TRANSACTION UI INSIDE THE LIGHTNING EXPERIENCE
When the CPQ Site Settings are set to Use Embedded Transaction in Lightning, users who create or edit
Oracle Quotes from the Lightning Experience will use the Embedded Transaction UI. This UI is identical
to the UI displayed when the user accesses the Quote from the Classic UI.
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 Cloud.
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 CPQ Cloud 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.
105
EMBEDDED CPQ JET TRANSACTION UI INSIDE THE LIGHTNING EXPERIENCE
When the CPQ Site Settings are set to Use Embedded Transaction in Lightning, users who create or edit
Oracle Quotes from the Lightning Experience use the Embedded Transaction UI. This UI is identical to
the UI displayed when the user accesses the Quote from the Classic UI.
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 Cloud.
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.
106
CPQ LIGHTNING TRANSACTION UI INSIDE THE LIGHTNING EXPERIENCE
If the CPQ Site Settings are set to not Use Embedded Transaction in Lightning, users who create or edit
Oracle Quotes from the Lightning Experience use the Lightning Transaction UI.
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 CPQ Cloud.
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 can not
customize the styling and behavior of the Lightning Transaction UI using CSS or JavaScript.
107
TOGGLE BETWEEN SALESFORCE CLASSIC AND THE LIGHTNING EXPERIENCE
If the logged in user has access to both Lightning Experience and Classic mode they have the ability to
switch back and forth between the two interfaces. When switching back and forth, the Salesforce
Connector loads the appropriate CPQ UI based on the active mode.
IMPORTANT: 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:
108
TROUBLESHOOTING
The section provides an up-to-date list of both helpful insights and solutions to known issues regarding
the Oracle Adapter for Salesforce Lightning. This information is intended for administrators and
developers because it provides implementation help and solutions to known issues.
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 CPQ Cloud 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 …
By default, Apple Mobile Safari sets the Accept Cookies option to Sites I
Browser Top for Apple Mobile
Visit, which presents issues for Canvas Apps. Solution: Use the
Safari users …
Salesforce suggested settings for Apple Cookies. This requires setting
the Block Cookies setting to Never. Otherwise, CPQ Cloud doesn’t have
permissions to set cookies and cannot log in users via the Salesforce
Canvas App. For additional information, refer to the Canvas Developer
Guide.
First step of troubleshooting any errors in the Lightning UI should be to
Lightning User Interface error…
check that the Embedded UI does not also have errors. Often errors
are due to problems with the integration XSL files.
TROUBLESHOOTING ISSUES
If you are encountering a problem the table below may have a solution to your issue.
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.
109
Issue Possible Solution
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 CPQ Cloud 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 CPQ Cloud 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.
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 CPQ Cloud’s Admin interface.
When trying to create a new Check that the certificate has been added successfully and that the
quote, you get an error similar to unique name for the certificate in Salesforce settings matches the
"Data Not Available" or "403" errors. value entered in the CPQ Site Settings exactly. The value is case
sensitive.
Permission errors Verify that your user has been synchronized to CPQ.
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 “error=redirect_uri_mismatch&error_description…”, follow the Add
a white screen and error message. CPQ Environment to CORS Whitelist and Add CPQ Environment to CSP
Whitelist 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 CPQ Cloud
(_sequence_number attribute Reference Application for Salesforce. Refer to the Oracle CPQ
enabled). Connector for Salesforce Upgrade and Migration Guide for instructions.
110
Issue Possible Solution
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
Lightning page in the Lightning App My 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.
If you do not see a solution to your issue, you can Log an Oracle CPQ Connector for Salesforce Service
Request.
111
POST-UPGRADE CONSIDERATIONS
Review the following after completing the setup tasks outlined in this document.
SANDBOX TESTING
Always upgrade in a Salesforce sandbox and test the instance of Oracle CPQ Cloud before installing into
production.
BROWSER SUPPORT
CPQ Cloud supports all browser versions that meet the criteria of the Oracle Software Web Browser
Support Policy.
If you experience issues using a supported browser version, open a ticket on My Oracle Support to
resolve the issue. If an issue arises when using a supported browser, use a certified browser version
until the delivery of a fix. Certified browsers are selected based on current market share and thoroughly
tested to work with the current version's standard functionality.
CERTIFIED BROWSERS
Windows
IMPORTANT: Compatibility issues with the selected browsers may exist when sites contain additional
JavaScript, alternate CSS, or other custom functionality. Customizations may require add-on work.
Contact My Oracle Support to determine the availability of workarounds and minor fixes.
Oracle officially supports version 8 and version 8.1 (installed package version 1.10 and 8.1 respectively)
of the Oracle CPQ Connector for Salesforce. We also continue to support version 7.2 of the legacy
Oracle CPQ Commerce Integration.
IMPORTANT: 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.
112
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 CPQ Cloud Online Help to become familiar with the new features introduced in Oracle CPQ
Cloud. 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 Cloud or the Oracle CPQ Cloud Consulting team.
ADDITIONAL INFORMATION
For more information on Oracle CPQ Cloud, visit the Oracle CPQ Cloud 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.
113
Copyright © 2019 Oracle and/or its affiliates. All rights reserved.
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.