oracle cpq saleforce connector installation and setup guide

Oracle CPQ Connector for Salesforce Installation and Setup Guide

December 2020 Copyright © 2020, Oracle and/or its affiliates

Oracle CPQ Connector for Salesforce Installation and Setup Guide 1

TABLE OF CONTENTS Table of Contents .......................................................................................................................................................................... 1 Revision History............................................................................................................................................................................. 3 Introduction ................................................................................................................................................................................... 4

Prerequisites ................................................................................................................................................................................................. 5 Check the Oracle CPQ and Reference Application Versions................................................................................................................ 6

Locate the Oracle CPQ Version Info............................................................................................................................................................ 6 Locate the Reference Application Information ........................................................................................................................................ 7

Enable My Domain ....................................................................................................................................................................................... 8 My Oracle Support ....................................................................................................................................................................................... 8

Register in My Oracle Support ..................................................................................................................................................................... 8 Log an Oracle CPQ Connector for Salesforce Service Request ............................................................................................................ 8

Installation .................................................................................................................................................................................... 10 Authentication .............................................................................................................................................................................. 11

Authorize an Oracle CPQ Site within Salesforce .................................................................................................................................... 11 Register the Oracle CPQ Site as a Remote Site ....................................................................................................................................... 11 Add CPQ Environment To CORS Allowlist ................................................................................................................................................ 12 Add CPQ Environment to CSP Allowlist .................................................................................................................................................... 13 Create a Certificate ........................................................................................................................................................................................ 14 Import the Certificate into Additional Salesforce Instances (Optional) .............................................................................................16

Setup Salesforce for OAuth 2.0 ................................................................................................................................................................ 17 Create a Connected App in Salesforce ...................................................................................................................................................... 17 Locate Security Integration Values for Oracle CPQ ................................................................................................................................ 21 Provide Salesforce Security Settings to My Oracle Support ................................................................................................................ 21

Integration User Pairing ............................................................................................................................................................................22 Pair Integration User and Generate Access Token ................................................................................................................................ 22 Verify Integration User Partner Login ...................................................................................................................................................... 25

Permissions and Page Layouts ................................................................................................................................................ 26 Assign the Admin Permission Set ........................................................................................................................................................... 26 Setup Page Layouts and Overrides ........................................................................................................................................................ 28

Create the Lightning Page ........................................................................................................................................................................... 28 Update the Opportunity and Account Page Layouts............................................................................................................................. 31 Update the User Layout ............................................................................................................................................................................... 34 Setup Action Overrides ................................................................................................................................................................................ 36

Integration Settings ................................................................................................................................................................... 40 CPQ Site Settings ....................................................................................................................................................................................... 40

Retrieve CPQ Process Version ID .............................................................................................................................................................. 40 Create the CPQ Site Settings....................................................................................................................................................................... 41

Review CPQ Commerce Process Integrations ...................................................................................................................................... 45 Review CPQ Account Integrations .......................................................................................................................................................... 47 Review CPQ Parts Integrations ................................................................................................................................................................ 49 Review Integration Tab Settings on Oracle CPQ Commerce Actions ............................................................................................... 51

Verify the Process Auto Fill Option ............................................................................................................................................................ 51 Verify the Process Integration Tab ............................................................................................................................................................ 52 Verify the Open Transaction Integration Tab ......................................................................................................................................... 53 Verify the Refresh Address Action Integration Tab .............................................................................................................................. 54 Verify the Return to Opportunity Action Integration Tab.................................................................................................................... 56 Verify the Return to Account Action Integration Tab ........................................................................................................................... 58 Verify the Select an Alternative Address Action Integration Tab ..................................................................................................... 60 Verify the Lightning Sync Action Integration Tab ..................................................................................................................................61

Setup Opportunity to Oracle Quote Synchronization ......................................................................................................................... 63 Mapping Opportunity Product Fields to Oracle Quote Line Item Fields .......................................................................................... 63 Mapping Opportunity Fields to Oracle Quote Fields (Optional) ........................................................................................................ 65

Parts Sync .................................................................................................................................................................................... 67 Verify the Parts Master ............................................................................................................................................................................. 67 Synchronizing Parts................................................................................................................................................................................... 67

Price Book Mapping ...................................................................................................................................................................................... 68 Populate the Oracle CPQ Part Number .................................................................................................................................................... 68


Import Parts .................................................................................................................................................................................................... 69 Import Part Extended Descriptions (Optional) ....................................................................................................................................... 70 Import Price Book Entries ............................................................................................................................................................................ 72 Schedule Parts Integrations ........................................................................................................................................................................ 73

User Sync ......................................................................................................................................................................................75 Manually Integrate Existing Users from Oracle CPQ .......................................................................................................................... 75

Pair User and Generate Token ................................................................................................................................................................... 75 Automatically Provision CPQ Users from Salesforce .......................................................................................................................... 77

Create User Groups in Salesforce .............................................................................................................................................................. 78 Create User Profiles (Optional) .................................................................................................................................................................. 80 Provision CPQ Users ......................................................................................................................................................................................81 Allow Quote Creation .................................................................................................................................................................................... 83

Embedded Transaction UI Versus Lightning Transaction UI ............................................................................................ 86 Embedded CPQ Legacy Transaction UI inside the Classic UI ............................................................................................................ 86 Embedded CPQ JET Transaction UI inside the Classic UI .................................................................................................................. 87 Embedded CPQ Legacy Transaction UI inside the Lightning Experience ....................................................................................... 88 Embedded CPQ JET Transaction UI inside the Lightning Experience ............................................................................................. 89 CPQ Lightning Transaction UI inside the Lightning Experience ...................................................................................................... 90 Toggle Between Salesforce Classic and the Lightning Experience ................................................................................................... 91

Troubleshooting ......................................................................................................................................................................... 92 Helpful Tips ................................................................................................................................................................................................. 92 Troubleshooting Issues............................................................................................................................................................................. 92

Post-Upgrade Considerations ................................................................................................................................................. 95 Sandbox Testing ........................................................................................................................................................................................ 95 Salesforce Integration Support ............................................................................................................................................................... 95 Training ........................................................................................................................................................................................................ 95 Additional Information ............................................................................................................................................................................. 95

Disclaimer .................................................................................................................................................................................... 95


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

DATE WHAT'S CHANGED NOTES

DEC 2020 Entire document updated for content accuracy, format, and editorial changes. The following new sections are added:

Import the Certificate into Additional Salesforce Instances

Setup Action Overrides

Updated Document

SEP 2019 Prerequisites Added verification of Enable CRM OAuth setting.

Installation Updated the CPQ Connector for Salesforce and CPQ Extension for Salesforce download links and passwords to version 8.2

Create a Connected App in Salesforce Updated Location field in the Required Canvas App Settings table.

MAY 2019 Installation Updated Sandbox and Production Download links for Oracle CPQ Extension for Salesforce

APR 2019 Installation Provided CPQ Connector for Salesforce version 8.1 download links and passwords

MAR 2019 Product Title and content. Updated Document

JUN 2018 Initial Document Creation


INTRODUCTION 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 “Salesforce 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 App and Salesforce Communities.

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:

Oracle Adapter for Salesforce Lightning

Oracle CPQ Extension for Salesforce Lightning

Before you begin, be sure to read the Prerequisites section.

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].

https://support.oracle.com/epmos/faces/DocumentDisplay?id=2432470.1



mailto:[email protected]


Prerequisites In order to successfully install and use the new Oracle CPQ Connector for Salesforce, there are a few prerequisites to be aware of which are listed in the table below.

PREREQUISITE DESCRIPTION/ADDITIONAL INFORMATION

Salesforce Edition A Salesforce instance using Enterprise Edition or above.

Oracle CPQ Version Update 18B or later.

Oracle CPQ Update 18B is the minimum supported version. 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.

Salesforce Reference Application Version 5.0 or later.

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.

https://help.salesforce.com/articleView?id=domain_name_overview.htm&type=0

https://support.oracle.com/



Check the Oracle CPQ 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.

This section provides procedures for the following:

Locate the Oracle CPQ Version Information

Locate the Reference Application Information

LOCATE THE ORACLE CPQ VERSION INFO

To locate the Oracle CPQ version information, complete the following steps:

1. Log in to Oracle CPQ.

2. Navigate to the Admin Home page.

3. Click View Oracle CPQ Version. The Releases page displays.

4. Note the Version.

5. Click Back.


LOCATE THE REFERENCE APPLICATION INFORMATION

When an Oracle CPQ 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:

1. Log in to Oracle CPQ.


3. Click File Manager under Utilities. The File Manager page displays.

4. Click on the About folder.

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.


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, 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:

Register in My Oracle Support

Log an Oracle CPQ Connector for Salesforce Service Request

REGISTER IN MY ORACLE SUPPORT

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.

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.

LOG AN ORACLE CPQ CONNECTOR FOR SALESFORCE SERVICE REQUEST

Administrators need to open Service Requests (SR) during the installation and setup of the Oracle CPQ/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.

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:

1. Navigate to the My Oracle Support (MOS) website.

2. Sign in using your MOS Support Account credentials.

3. Locate the Service Request tab and click Create SR.

https://help.salesforce.com/articleView?id=domain_name_setup.htm&type=5


https://www.oracle.com/index.html

https://docs.oracle.com/cd/E25290_01/doc.60/e25224/registration.htm#CACEJECG






4. Enter a Problem Summary and Problem Description.

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

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.

8. Enter your Support Identifier.

9. Enter the Severity as 3-Minor Loss of Service.

10. Click Next.

11. Follow the remaining steps as prompted.

Note: Refer to Log an SR online help articles for further assistance.



INSTALLATION There are two (2) managed packages to install in order to begin using the Oracle CPQ Connector for Salesforce.

1. Oracle CPQ Connector for Salesforce:

• Oracle CPQ Connector for Salesforce –Production Installation

• Oracle CPQ Connector for Salesforce – Sandbox Installation

2. Oracle CPQ Extension for Salesforce:

• Oracle CPQ Extension for Salesforce –Production Installation

• Oracle CPQ Extension for Salesforce – Sandbox Installation

The password for the Oracle CPQ Connector for Salesforce package is GApic4gu

The password for the Oracle CPQ Extension for Salesforce package is ad1GSYQZ

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.

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1K000002ec9m

https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1K000002ec9m

https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1K000002ec9m

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1K000002N2X5

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1K000002N2X5

https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1K000002N2X5

https://help.salesforce.com/articleView?id=distribution_installing_packages.htm&type=5

https://help.salesforce.com/articleView?id=lex_enable_intro.htm&language=en_US&type=0


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 Oracle CPQ 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.

Authorize an Oracle CPQ Site within Salesforce This section provides instructions for preparing Salesforce to authenticate with Oracle CPQ. You must register your CPQ Site as a trusted entity within Salesforce. Additionally, an encrypted certificate must be downloaded and registered with Oracle CPQ. In order to do this, you will perform the following steps which are outlined in their own sections called:

1. Register the Oracle CPQ Site as a Remote Site

2. Add CPQ Environment To CORS Allowlist

3. Add CPQ Environment to CSP Allowlist

4. Create a Certificate

REGISTER THE ORACLE CPQ SITE AS A REMOTE SITE

Before the Salesforce Connector can call out to your CPQ Site, both the CPQ site and the Salesforce MyDomain URLs must be registered in the Remote Site Setting page in your Salesforce environment.

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.


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


Active Checked

3. Click Save. The new Salesforce org domain name site appears in the list on the All Remote Sites page.

ADD CPQ ENVIRONMENT TO CORS ALLOWLIST

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 allowlist, complete the following steps:

1. Navigate to Setup > Security > CORS. The CORS page displays.

2. Click New in the Whitelisted Origins section.

3. Enter your CPQ environment instance URL (for example, https://<cpq_site_url>) in the Origin URL text box.


4. Click Save.

CORS Whitelisted Origins

ADD CPQ ENVIRONMENT TO CSP ALLOWLIST

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 helps to protect against data theft and distribution of malware.

To add your CPQ environment to the CSP allowlist, complete the following steps:

1. Navigate to Setup > Security > CSP Trusted Sites. The Content Security Policy Sites page displays.

2. Click New Trusted Site.

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>


Active Checked

Context All

4. Click Save. The new trusted site appears in the list on the Content Security Policy Trusted Sites page.


To add your Salesforce My Domain to the CSP allowlist, complete the following steps

1. Click New Trusted Site.

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


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.

To create a certificate, complete the following steps:

1. Navigate to Setup > Security > Certificate and Key Management.

https://help.salesforce.com/articleView?id=security_keys_creating.htm&language=en_US&type=0


2. Click Create Self-Signed Certificate.

3. Enter a descriptive name in the Label field for your 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.

5. Select a Key Size from the Key Size drop-down.

a. 2048 provides a one year authorization time.

b. 4096 provides a two year authorization time.

6. Click Save. The Detail page displays.


7. Click Download Certificate.

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.

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.

IMPORT THE CERTIFICATE INTO ADDITIONAL SALESFORCE INSTANCES (OPTIONAL)

If you are planning to connect more than one Salesforce instance to CPQ, you must export the certificate file from this site and import into each additional Salesforce instance.

To export the file, complete the following steps:

1. Navigate to Setup > Security Controls > Certificate and Key Management.

2. Click Export to Keystore.

3. Enter a password for the new Keystore.

4. Click Export.

5. Save the file to your system.

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.

4. Enter the Keystore Password.

5. Click Save. The certificates inside the Keystore are imported into your organization.


Setup Salesforce for OAuth 2.0 In this section, you create a Connected App to authorize and bind your Salesforce org to your Oracle CPQ site using OAuth 2.0 protocol. In order to do this, you will perform the following steps which are outlined in their own sections called:

1. Create a Connected App in Salesforce

2. Locate Security Integration Values for Oracle CPQ

3. Provide Salesforce Security Settings to My Oracle Support

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.

CREATE A CONNECTED APP IN SALESFORCE

Part of the integration process requires the creation of a Connected App that allows Oracle CPQ 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.

To create a Connected App in Salesforce, complete the following steps:

1. Navigate to Setup > Platform Tools > Apps > App Manager.

2. Click New Connected App.

https://help.salesforce.com/articleView?id=connected_app_overview.htm&type=0&language=en_US&release=204.14

https://help.salesforce.com/articleView?id=connected_app_overview.htm&type=0&language=en_US&release=204.14




3. The New Connected App page displays.

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

Attribute Value Example

Connected App Name Text string for label name Oracle Adapter

API Name Text string for API name Oracle_Adapter

Contact Email Valid email [email protected]

https://help.salesforce.com/articleView?id=connected_app_create.htm&type=0&language=en_US&release=204.14


5. 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.

REQUIRED API (ENABLE OAUTH SETTINGS)

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)

Require Secret for Web Server Flow

Checked

Include Configure ID Token Checked

Include Standard Claims Checked

API (Enable Oauth Settings)


6. 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.

REQUIRED CANVAS APP SETTINGS

Force.com Canvas Checked

Canvas App URL https://<site _domain>/admin/oauth2/salesforce/oauth_callback.jsp

Access Method OAuth Webflow (GET)

Location Add the following:

Layouts and Mobile Cards

Lightning Component

Visualforce Page

Lifecycle Class CPQDispatcherCanvasLifecycleHandler

Note: Do not select a SAML Initiation Method.

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.

https://help.salesforce.com/articleView?id=connected_app_create.htm&type=0&language=en_US&release=204.14


LOCATE SECURITY INTEGRATION VALUES FOR ORACLE CPQ

If you need to retrieve the Consumer Key and Consumer Secret, you can return to the Manage Connected Apps screen.

To view this information, complete the following steps:

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.

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 before the Oracle CPQ/Salesforce integration can be tested.

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/...

https://support.oracle.com/epmos/faces/MosIndex.jspx?_afrLoop=569925007061100&_afrWindowMode=0&_adf.ctrl-state=ja40gj32g_4

https://docs.oracle.com/cd/E25290_01/doc.60/e25224/srhome.htm#BABHFJCD

https://docs.oracle.com/cd/E25290_01/doc.60/e25224/srhome.htm#BABHFJCD

https://login.salesforce.com/

https://test.salesforce.com/


Integration User Pairing 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).

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.

PAIR INTEGRATION USER AND GENERATE ACCESS 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.

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.

To pair a user and generate a token, complete the following steps:

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.




3. Click User Integration.

4. Enter your Salesforce username in the Login field.

5. Click Generate Token.

6. Log in to Salesforce with the credentials for the user account you want to integrate.


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

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.


VERIFY INTEGRATION USER PARTNER LOGIN

Once the User logins are bound together, verify the partner login by completing the following steps:

1. Log out from Oracle CPQ and Salesforce.

2. Paste the following URL into your browser:

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>%2Fpartner_login.jsp

If the connection worked, the following Partner Login page displays.

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.


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.

Assign the Admin Permission Set 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 > Administration > Users > Permission Sets). The following permission sets appear:

Oracle Adapter Admin

Oracle Adapter Sales User

Oracle CPQ Extension Admin

Oracle CPQ Extension Sales User

Oracle CPQ Community Sales User

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.

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.

OBJECT PERMISSION ENABLED

Actions Create, Read, Update, Delete, View/Modify All

Action Steps Create, Read, Update, Delete, View/Modify All

Callout URLs Create, Read, Update, Delete, View/Modify All

Endpoints Create, Read, Update, Delete, View/Modify All

Key Chains Create, Read, Update, Delete, View/Modify All.

Routes Create, Read, Update, Delete, View/Modify All

Transforms Create, Read, Update, Delete, View/Modify All.

CPQ Site Settings Create, Read, Update, Delete, View/Modify All

Embedded CPQ Site Settings Create, Read, Update, Delete, View/Modify All

Field Mappings Create, Read, Update, Delete, View/Modify All

Oracle Quotes Create, Read, Update, Delete, View/Modify All

Oracle Quote Line Items Create, Read, Update, Delete, View/Modify All

Oracle User Profiles Create, Read, Update, Delete, View/Modify All

Oracle Users 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.


Setup Page Layouts and Overrides 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:

1. Create the Lightning Page for the Oracle Quotes and Line Items

2. Update the Opportunity and Account Page Layouts

3. Update the User Page Layout

4. Setup Action Overrides

CREATE THE LIGHTNING PAGE

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.

1. In Salesforce, navigate to Setup > Platform Tools > User Interface > Lightning App Builder.

2. Click New. The Create a New Lightning Page displays.

3. Click Record Page.

4. Click Next.

5. Enter Oracle Quote into the Label field.


6. Select Oracle Quote (Oracle_Quote__c) from the Object drop-down.

7. Click Next.

8. Select One Region under the Choose Page Template tab.

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.




11. Click Save. The Page Saved page displays.

12. Click Activate. The Activation for the specified page displays.

13. Click Assign as Org Default.

14. Click Save.

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.

https://trailhead.salesforce.com/modules/lightning_app_builder


UPDATE THE OPPORTUNITY AND ACCOUNT PAGE LAYOUTS

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 > Platform Tools > Objects and Fields > Object Manager > Opportunity.

2. Click on Page Layouts. The Opportunity Page Layouts list displays.

3. Select Edit under the option menu for the Page Layout you want to edit.

4. From the selection list on the left, select Related Lists.


5. 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.

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.


10. View the Buttons section of the page by selecting the Expand icon.

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.

13. Click Ok to save your selections.

14. Click Save to save all the settings on the page.

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.

https://trailblazer.salesforce.com/issues_view?id=a1p3A0000018BxbQAE

https://trailblazer.salesforce.com/issues_view?id=a1p3A0000018BxbQAE


UPDATE THE USER LAYOUT

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 Oracle CPQ. 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:

1. Navigate to Setup > Platform Tools > Objects and Fields > Object Manager > User

2. Click on Page Layouts.

3. Select Edit under the option menu for the Page Layout you want to edit.

4. Select Visualforce Pages from the layout tool box.

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.


6. Click and drag the OracleUsers page to move it into the section you just created.

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.


SETUP ACTION OVERRIDES

Once you have the Oracle Quote object available on the layout, you now must override the actions on the Oracle Quote object. These action overrides will navigate the user to the CPQ UI instead of the standard Salesforce UI when they try to interact with quotes.

To setup action overrides, complete the following steps:

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.


5. Select Lightning Component for the Lightning Experience Override. Choose oafsl:recordView from the list of components.

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.

12. Click Save.


13. Return to the Buttons, Links, and Actions page. Locate the standard New action and click Edit under the option menu.

14. The New action’s Override Properties page displays.


15. Select No Override (use default) for the Salesforce Classic Override.

16. Select Use Salesforce Classic override for the Lightning Experience Override.

17. Select Use Salesforce Classic override for the Mobile Override.

18. Click Save.


INTEGRATION SETTINGS In order to sync data between Oracle CPQ 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 Oracle CPQ and other in Salesforce. The following sections walk you through the set up within each system.

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 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 Oracle CPQ 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 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.

RETRIEVE CPQ PROCESS VERSION ID

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.

To retrieve your Version ID, complete the following steps:

1. Log in to CPQ as an admin.

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.

4. Click List. The Integrations page displays.

5. Click View Parameters. The parameters display.

6. Record the version_id information. This information is needed to create site settings.

Sample Version ID output



CREATE THE CPQ SITE SETTINGS

When your sales users are creating a new quote from within Salesforce, they are directed to an Oracle CPQ 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.

2. Click CPQ Site Settings.

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.

CPQ Site Settings – Step 1

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.


4. Enter the connection information for the fields. Refer to the table below for field information.

CPQ SITE SETTINGS FIELD PURPOSE/DESCRIPTION

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.

Callout URL Enter the Callout URL for your site.

For example: https://[yoursite].oracle.com or https://[yoursite].bigmachines.com where [yoursite] is the name of your designated Oracle CPQ site.

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.

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.

5. Click Next. The CPQ Site Settings Step 2: Process Details displays.

CPQ Site Setting – Step 2


6. Enter the process details for the fields. Refer to the table below for field information.

ADAPTER SETTINGS FIELDS PURPOSE/DESCRIPTION

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.


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.


8. Enter the adapter settings values for the fields. Refer to the table below for field information.

ADAPTER SETTINGS FIELDS PURPOSE/DESCRIPTION

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.

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.

Button Group Display Count Enter a number to represent the number of buttons to be visible initially in your button groups. All additional buttons will be hidden under the dropdown. The number of buttons displayed effects all button groups.

Data Table Page Size Enter the number to represent the number of line items to be visible on each page in your data list. Users will need to click Previous or Next to view additional pages of data.

Use Embedded Transaction in Lightning

Check this if you want to enforce receiving the Embedded UI instead of the Lighting UI. 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.

Quote Name Attribute (Optional) Select the variable name that stores the value used as the Quote name.

Lightning Sync Action Required for new quotes. Select the synchronization action setting.

Oracle Quote ID Attribute Commerce Main Document ID attribute that holds the Salesforce ID for the quote object.

Note: 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.

9. Click Next. The Step 4 - Complete Setup displays.





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.

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.

Review CPQ Commerce Process Integrations Oracle CPQ supports a point-to-point integration where Oracle CPQ 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:

1. In Oracle CPQ, navigate to the Admin Home page.

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.


5. Review the Integrations available.

The integrations in the latest Ref App are listed in the following table

PROCESS INTEGRATIONS DESCRIPTION

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.

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.

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.

Review CPQ Account Integrations Oracle CPQ supports a point-to-point integration where Oracle CPQ 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.

To review and verify Account Integrations, complete the following steps:


2. Click Accounts under Integration Platform. The Accounts page displays.



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 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.


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.



Review CPQ Parts Integrations Oracle CPQ supports a point-to-point integration where Oracle CPQ 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.

To review and verify Parts Integrations, complete the following steps:


2. Click Parts under Products. The Parts Administration page displays.


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:

SALESFORCE AS PARTS MASTER

PARTS INTEGRATIONS

DESCRIPTION

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 Descriptions

Salesforce: When Salesforce is the Parts Master, updates Parts 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:

CPQ AS PARTS MASTER

PARTS INTEGRATIONS

DESCRIPTION

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 Descriptions

Salesforce: When CPQ is the Parts Master, updates Products in 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.

Review Integration Tab Settings on Oracle CPQ 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.

VERIFY THE PROCESS AUTO FILL OPTION

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.

To verify the Auto Fill Options, complete the following steps:



3. Click the Name of the process. The Process Administration page displays.

4. In the Auto Fill Options drop-down, verify Accounts Information is selected.



VERIFY THE PROCESS INTEGRATION TAB

Integrations set up on the Process Administration page run when new quotes are created.

To verify the Process Integration tab, complete the following steps:



3. Click the Name of the process. The Process Administration page displays.


4. Click Integration tab from Process Administration page.

5. Review the Available and Selected Imports and verify the following integrations are selected.

INITIAL IMPORTS DESCRIPTION

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.

VERIFY THE OPEN TRANSACTION INTEGRATION TAB

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:

1. Navigate to the Admin Home page


3. For the process you want to verify, select Process Actions from the Navigation drop-down.

4. Click List. The Process Action List page displays.


5. Click on the Open Transaction link from the Action Name column. The Admin Action page displays.

6. Click on the Integration tab.

7. Review the Integrations and verify the following integrations are selected and sequenced in the following order

SELECTED INTEGRATIONS DESCRIPTION

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.

VERIFY THE REFRESH ADDRESS ACTION INTEGRATION TAB

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:



3. For the process you want to verify, select Documents from the Navigation drop-down.


4. Click List. The Documents List page displays.

5. For the Document you want to verify, select Actions from the Navigation drop-down.

6. Click List. The Action List page displays.

7. Click on the Refresh Address link under the Action Name column. The Admin Action page displays.



9. Verify Account Import is selected under CRM Mapping.

VERIFY THE RETURN TO OPPORTUNITY ACTION INTEGRATION TAB

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:








7. Click on the Return to Opportunity link under the Action Name column.

8. Click on the Integration tab on the Admin Actions page.

9. Review the Integrations and verify the following integrations are selected and sequenced in the following order.



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.

VERIFY THE RETURN TO ACCOUNT ACTION INTEGRATION TAB

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:








7. Click on the Return to Account link under the Action Name column.





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.

VERIFY THE SELECT AN ALTERNATIVE ADDRESS ACTION INTEGRATION TAB

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:








7. Click on the Select an Alternative Address link under the Action Name column.


9. Verify Contact Import is selected under the CRM Mapping.

VERIFY THE LIGHTNING SYNC ACTION 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:








7. Click on the Lightning Sync link under the Action Name column.





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.


Setup Opportunity to Oracle Quote Synchronization 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.

When a quote is marked as “active”, the following rules apply:

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.

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.

REQUIRED FIELD MAPPINGS DESCRIPTION

Sales Price The sales price of the product for this Opportunity.

Quantity The quantity 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:



2. Click on the Field Mappings tab. The Recent Field Mappings page displays.

3. Click New. The New Field Mapping page displays.

4. Enter the following values to create a new field mapping

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.


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:


2. Click on the Field Mappings tab. The Recent Field Mappings page displays.

3. Click New. The New Field Mapping page displays.


4. Enter the following values to create a new field mapping

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.

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.


PARTS SYNC In order to create Opportunity Products as part of your Opportunity and Quote synchronization, those products must exist in both Salesforce and Oracle CPQ. This also establishes a master product list that prevents duplicate product data and ensures consistent pricing. Oracle CPQ provides parts synchronization capabilities that allow you to import products from Salesforce or to export parts from Oracle CPQ. These features include creating or updating both products and pricing information.

This section provides instructions for the following activities:

Verify the Parts Master

Synchronize Products and Parts

Synchronize Price Books and Price Book Entries

Verify the Parts Master 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 Oracle CPQ sites, assigns Salesforce as the Parts Master. When Salesforce is the Parts Master, parts integrations import product and price information from Salesforce to Oracle CPQ. If you choose Oracle CPQ 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.

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.

2. Navigate to Admin Home page.

3. Click Parts. The Parts Administration page displays.

4. Under the Item Master section, the selected Parts Master displays. The two available options are:

• BigMachines - indicates Oracle CPQ as the Parts Master

• Partner - indicates Salesforce as the Parts Master.

5. (Optional) Click on Integration. The Parts Integration page displays.

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.

Considerations for Using Parts Sync:

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.


https://support.oracle.com/epmos/faces/MosIndex.jspx?_afrLoop=569925007061100&_afrWindowMode=0&_adf.ctrl-state=ja40gj32g_4


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 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.

PRICE BOOK MAPPING

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.

To map your Price Book ID, complete the following steps:

1. In Salesforce, log in as an administrator.

2. Click on All tabs (+).

3. Click on Price Books. The Price Book List page displays.

4. Click on your Price Book in the Price Book Name column. The Price Book displays.

5. Copy the Price Book ID from the URL to your clipboard.

6. Log in to Oracle CPQ as FullAccess user.

7. Go to Admin Home page.

8. Click on Parts under Products. The Parts Administration page displays.

9. Click List under the Price Book section.

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.

12. Click Update.

13. Repeat these steps for each additional Price Book.

POPULATE THE ORACLE CPQ PART NUMBER

When Salesforce is the Parts Master, part sync creates new parts in Oracle CPQ. In order to create a part in Oracle CPQ, 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.

3. Re-upload the product records with the updated 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.

https://developer.salesforce.com/page/Data_Loader


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 Oracle CPQ. Importing parts from Salesforce creates new parts in Oracle CPQ if they do not already exist and updates existing parts.

Note: If you have selected Oracle CPQ as the Parts Master, the steps outlined in this section are similar for exporting Parts to Salesforce.

To import parts from Salesforce, complete the following steps:

1. Log in to CPQ as SuperUser.


3. Click Parts under Products. The Part Administration page displays.

4. Click Integration under Item Master.

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 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:

a. Navigate to Admin Home page.

b. Click Parts. The Parts Administration page displays.

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.

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.

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:







5. Select the Import Part Extended Descriptions integration under the Name column in the List Integrations section.

6. Click Import.




Note: You need to modify the XSL templates for this integration to point to the custom fields in Salesforce that store the Part Extended Descriptions.

IMPORT PRICE BOOK ENTRIES

Price Book Entries are how Salesforce stores pricing information about their products. Oracle CPQ 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 Oracle CPQ.

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:







5. Select the Import Price Book Entries integration under the Name column in the List Integrations section.

6. Click Import.



Note: You may need to modify the XSL templates for this integration if you are using multiple price books, multiple currencies, or other customizations.

SCHEDULE PARTS INTEGRATIONS

Once the Parts Master is established and parts are initially set up between Oracle CPQ and Salesforce, it is important to keep the parts synchronized between the applications.

To schedule parts sync integration action, complete the following:

1. Log in to your application as a SuperUser.

2. Click Partner Login at the top right of the page.

3. Navigate to Admin > Parts > Integration.


4. Select the specific integration you want to schedule and click Schedule.

Parts Sync – Schedule Export

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.

8. Select one of the following part sync types:

• 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.

9. Click Add Schedule.

10. Verify that the integration activity is added to the Scheduled Integrations list.


USER SYNC Integrated users will have two user accounts—one in Salesforce and one in Oracle CPQ. 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 Oracle CPQ.

This section provides instructions for the following activities:

Manually pair existing users from Oracle CPQ

Automatically provision CPQ users from Salesforce

Allow quote creation

Manually Integrate Existing Users from Oracle CPQ If you have existing users in Oracle CPQ 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.

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.

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 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.

To pair a user and generate a token, complete the following steps:

1. Log into Oracle CPQ 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.

Note: The My Profile icon and location may vary based on your CPQ site configuration.

3. Click User Integration.

4. Enter the Salesforce Username that you are pairing to in the Login field.

5. Click Generate Token.

6. Log in to Salesforce with the credentials for the user account you want to integrate.


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

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.

Automatically Provision CPQ Users from Salesforce Automatic provisioning of CPQ users saves administrator time by automating the process of creating users in Oracle CPQ. There are two scenarios when this feature is very beneficial:

Creating a user in Salesforce and immediately provisioning the user in Oracle CPQ

Provisioning a new CPQ user for an existing Salesforce user

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.


CREATE USER GROUPS IN SALESFORCE

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 Oracle CPQ to retrieve group variable names then login to Salesforce to add the group names.

To retrieve Group Variable Names from Oracle CPQ, complete the following steps:

8. In Oracle CPQ, go to the Admin Home Page.

9. 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:

1. In Salesforce, navigate to Setup.

2. Navigate to Build > Create > Objects to open the Custom Objects page.

3. Click Oracle User.

4. In Custom Fields & Relationships, click on the Groups link under Field Label. The Custom Field Definition Detail information displays.

5. Click New under Values.


6. In the Groups page, enter the variable names of each CPQ User Group that you retrieved from Oracle CPQ. 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 Oracle CPQ site.

Note: There must be at least one user group.


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.

To create CPQ User Profiles, complete the following steps:

1. In Salesforce, select the Sales drop down and click Oracle CPQ Extension.

2. Click on Oracle User Profiles tab.

3. Click New. The New Oracle User Profile page displays.

4. Enter the values for the fields for the desired user profile. Refer to the table below for field information.

NEW ORACLE USER PROFILE FIELDS

PURPOSE/DESCRIPTION

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.


NEW ORACLE USER PROFILE FIELDS

PURPOSE/DESCRIPTION

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.

PROVISION CPQ USERS

Once you have defined your user groups and profiles, you are ready to begin automatically provisioning users in Oracle CPQ.

To provision CPQ users, complete the following steps:

1. In Salesforce, navigate to the Setup > Manage Users > Users.

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.

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.

Oracle CPQ to Salesforce User Profile Sync

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 USER FIELDS PURPOSE/DESCRIPTION

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.


ORACLE USER FIELDS PURPOSE/DESCRIPTION

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.

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.

To allow quote creation, complete the following steps:

1. In Salesforce, navigate to Setup > Manage Users > Users.

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.


4. Scroll down to the Oracle User Section created in Update the User Layout, click Edit.

OU Section - Edit

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.

Allow Quote Creation


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.


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, 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.

The Salesforce Connector supports five primary combinations of user interfaces:

Embedded CPQ Legacy Transaction UI inside the Salesforce Classic UI

Embedded CPQ JET Transaction UI inside the Salesforce Classic UI

Embedded CPQ Legacy Transaction UI inside the Salesforce Lightning Experience

Embedded CPQ JET Transaction UI inside the Salesforce Lightning Experience

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.

CPQ Legacy Transaction UI inside the Classic UI

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.

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.

CPQ JET Transaction UI inside the Classic UI

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.


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 Oracle CPQ.

CPQ Legacy Transaction UI inside the Lightning Experience

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.


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 Oracle CPQ.

CPQ JET Transaction UI inside the Lightning Experience

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.


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 Oracle CPQ.

CPQ Lightning Transaction UI inside the Lightning Experience

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.



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.

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:

1. Click on the User icon in the top-right corner of the page.

2. Click on Switch to Salesforce Classic.

Switch to Classic Option

To switch to the Lightning Experience from Classic mode, complete the following step:

1. Click on Switch to Lightning Experience just to the left of your name.

Switch to Lightning Experience Option


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

To avoid the truncation of Quote Name in the Oracle Adapter …

The Transaction Name attribute in Oracle CPQ should be the same size as the Quote Name field on the Oracle Quote (Max. 80 chars).

Browser Top for Apple Mobile Safari users …

By default, Apple Mobile Safari sets the Accept Cookies option to Sites I Visit, which presents issues for Canvas Apps. Solution: Use the Salesforce suggested settings for Apple Cookies. This requires setting the Block Cookies setting to Never. Otherwise, Oracle CPQ 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.

Lightning User Interface error… First step of troubleshooting any errors in the Lightning UI should be to 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.

ISSUE POSSIBLE SOLUTION

Authorization Certificate has Expired.

More than likely, it has been two (2) years since your Salesforce org’s 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 information, you get a "405" error when connection to CPQ.

Verify that the Certificate Name is an exact match for the one provided via My Oracle Support .

Mark Quote as Active fails and generates an Error

If you receive a Salesforce non-zero error when you attempt to mark a 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).

https://resources.docs.salesforce.com/sfdc/pdf/canvas_framework.pdf




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 error messages when attempting to create a new CPQ User.

Navigate to Salesforce Setup and search for Batch Jobs to review any error messages that may have been received during the user creation process.

An error is present in the Embedded mode.

Locate the integrations that run on that particular action (for example, 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, you get an error similar to "Data Not Available" or "403" errors.

Check that the certificate has been added successfully and that the unique name for the certificate in Salesforce settings matches the 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 frame.

On the Connected App, set the Permitted Users to “Admin approved users are pre-authorized” and add the CPQ permission sets as approved for the Connected App.

When trying to pair CPQ Integration User to Salesforce, the Generate Token button is missing from User Integration page.

Try the following steps:

1. Go to CPQ Admin 2. General Site Settings 3. Make sure Enable CRM OAuth is set to True 4. Click Update

When adding a line item or reconfiguring the canvas, you receive a white screen and error message.

If you receive a white screen and error message similar to “error=redirect_uri_mismatch&error_description…”, follow the Add CPQ Environment to CORS Allowlist and Add CPQ Environment to CSP Allowlist procedures and ensure that the CPQ site URLs are entered correctly.

Line Item Ordering is not enabled (_sequence_number attribute enabled).

Verify that the site has been provisioned with the latest Oracle CPQ Reference Application for Salesforce. Refer to the Oracle CPQ Connector for Salesforce Upgrade and Migration Guide for instructions.

Unable to view recordView component when creating a new Lightning page in the Lightning App Builder.

If you are not able to view the recordView component when building a new Lightning App, you may need to deploy your previously created My Domain.

Import Opportunity doesn’t work. Verify that Document VarName is correct.

Parts Sync doesn’t work. Review the export parts, verifying the required field mappings are correct.







The Lightning Sync Action creates two objects within the Salesforce Opportunity: one blank Quote and one Quote with the details saved post-creation.

Confirm you are using the correct Integration for the Lightning Sync Action. Reusing the Save Action integrations can cause this issue.

“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.


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 before installing into production.

Salesforce Integration Support Oracle officially supports version 8.3, 8.2, and 8.1 of the Oracle CPQ Connector for Salesforce. We also continue to support version 7.2 of the legacy Oracle CPQ Commerce Integration.

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.


http://docs.oracle.com/cloud/latest/cpq_gs/index.html

CONNECT WITH US

Call +1.800.ORACLE1 or visit oracle.com. Outside North America, find your local office at oracle.com/contact.

blogs.oracle.com facebook.com/oracle twitter.com/oracle

Copyright © 2020 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.

https://blogs.oracle.com/

https://www.facebook.com/Oracle/

https://twitter.com/oracle