Generic Integration

Overview

This integration type defines a connection to an arbitrary third party system. Once defined, system integrators can use BML to retrieve these connection details prior to making a Web Service call to that system. Refer to Commerce Integrations for additional information.

Oracle CPQ 25C introduced the following generic integrations:

Generative AI is used to develop Generative AI (GenAI) Quote Summaries for Customer Relationship Management (CRM) integrated Oracle CPQ sites (for example, Salesforce or Microsoft Dynamics). Oracle CPQ leverages Generative AI (GenAI) to automatically generate comprehensive quote summaries. Users can then choose to use the generated quote summary when communicating with customers or internal stakeholders. The GenAI quote summaries are available for Redwood Quote UI and JET Transaction UI.

Note: Oracle Sales integrated sites do not need to create a Generic Integration to utilize Generative AI Quote Summaries.
Fusion Product Integration is used for synchronizing parts and product structures for an Oracle CPQ and Salesforce integrated site. Once the connections are established, Oracle Sales Product Information Master (SPIM) integration can be used to synchronize products and product structures. Parts and BOM synchronization can be regularly scheduled or a be a one-time synchronization event.

Oracle CPQ 25D introduced a new system attribute for Parts called the Fusion Part ID. Prior to Oracle CPQ 25D, the existing Partner Part ID attribute was used as an external identifier for both Fusion Products and Salesforce Products. This introduced a limitation where CPQ could not link its Parts to both Fusion Products and Salesforce Products at once.

The Fusion Part ID field has been added as a dedicated external identifier for Fusion Product Integrations. When integrating with Fusion Products all Oracle managed and seeded product-part syncs will leverage this field as a linking attribute and external ID.
- If you are setting up a Salesforce Products integration for the first time, you do not need to take any additional steps. Any seeded integrations will be pre-mapped to use the original Partner Part ID attribute.
- If you have an existing Salesforce Products integration you do not need to take any action. Existing integration files and field mappings will remain unchanged and will continue to use the Partner Part ID for all flows.
- If you are setting up a Fusion Products integration for the first time, you do not need to take any additional steps to use the Fusion Part ID. It is available immediately upon upgrade and any managed or seeded integrations will use this attribute.
  
  If your site was provisioned prior to Oracle CPQ 25D and you have not previously set up the Fusion Products integration it is likely that the older seeded integration files will still reference the Partner Part ID field. You should modify these files to use the Fusion Part ID prior to enabling the integration.
- If you have an existing Fusion Product integration setup on your site, the values stored in the Partner Part ID attribute will be copied to the Fusion Part ID attribute at the time of upgrade. Any Oracle managed integration flows will begin using the Fusion Part ID immediately. Any previously seeded Fusion integration files - those that were provided to sites provisioned prior to 25D - and custom integrations will continue to point at the old Partner Part ID.
  
  To ensure that both patterns continue working without disruption we have provided a new setting on the Configuration Settings page called Update Partner Part ID with Fusion Part ID value. This property will ensure that the Fusion Part ID and Partner Part IDs are the same. Any updates to the Fusion Part ID as part of Fusion Product syncs will propagate to the Partner Part ID.
  
  The Update Partner Part ID with Fusion Part ID value will be set to Yes at the time of upgrade if you have a Fusion Product integration defined and do not have a Salesforce Product integration set up. If you wish to set up a Salesforce Product Integration and a Fusion Product Integration up at the same time, this must be set to No. You must also refactor any existing Fusion Products integration files and custom integrations to use the Fusion Part ID exclusively. Refer to Configuration Settings > Options - Unified Products Sync.
  - Salesforce Product integrations will continue using the existing Partner Part ID attribute for Parts Syncs. There are no changes in behavior for Salesforce Product integrations.
  - The Fusion Part ID field should not be used to store any information other than Fusion Product IDs. Doing so may cause upgrade issues and integration issues with other Fusion applications.
  - The Update Partner Part ID with Fusion Part ID value setting is a one-way sync. It will copy the Fusion Part ID to the Partner Part ID. It does not work the other way; any updates to the Partner Part ID mapping will not propagate to the Fusion Part ID.
  - The Update Partner Part ID with Fusion Part ID value setting will only be available for existing customers who already have a Fusion Product Integration defined. New customers and customers only using a Salesforce integration will not see this setting.
  - All customers with an existing Fusion Products integration that leverages the Partner Part ID should consider updating those integrations to leverage the Fusion Part ID exclusively to ensure that you can take advantage of future enhancements.

Administration

Set Up a Generic Integration

Set Up a Generative AI Generic Integration for Non-Oracle CRM-Integrated Sites

Target Audience

Non-Oracle Sales Cloud integrated customers

Note: Oracle Sales integrated sites do not need to create a Generic Integration to utilize Generative AI Quote Summaries.

Pre-Requisites

Customers must have a provisioned Oracle Fusion environment.
Set the Quote Summary Prompt:
- Refer to Administration Interface to Manage Prompts Used for Generative AI Features
- Seeded prompt code - cx.cpq.quote_summary

Set Up a Generative AI Generic Integration for Non-Oracle CRM-Integrated Sites

Navigate to the Integration Center.
1. Click Admin to go to the Admin Home Page.
2. Click Integration Center in the Integration Platform section.
  The Integration Center page opens.

Click Create Integration.
Select Generic Integration from the Type drop-down.
Enter "Generative AI" in the Name field.

Generative AI Generic Integration

Enter the Fusion environment URL in the Request URL field.
Enter the Username and Password credentials.
Select the Enable Integration check box.
Click Save.

A Generate Quote Summary action is required to generate the summary. If this action does not exist, refer to Redwood Quote UI > Create Quote Summary Action or JET Transaction UI > Create Quote Summary Action.

Once the integration is active, unselecting the Enable Integration checkbox disables any integrations which use it. Run-time integrations will not execute and some administrative features may not be available.

Set Up a Fusion Product Information Generic Integration for Salesforce Product Synchronization

To create a Fusion Product Information Generic integration type, complete the following steps:

Navigate to the Integration Center.
1. Click Admin to go to the Admin Home Page.
2. Click Integration Center in the Integration Platform section.
  The Integration Center page opens.

Click Create Integration.
Select Generic Integration from the Type drop-down.
Enter "Fusion Product Information" in the Name field.

Fusion Product Integration Generic Integration

Enter the Fusion Product Integration environment URL in the Request URL field.
Enter the Username and Password credentials.
Select the Enable Integration check box to enable the integration.
Click Save.

To maintain integrity of products and product structures, we recommended that when using this integration you only export part information to Salesforce and do not import part information from Salesforce.

Once the Fusion Product Integration is setup, the Parts Administration page provides the available parts information and ability to veiw regularly scheduled synch or initiate a one-time synchronization event.

Log into Oracle CPQ as a parts administrator or as a Full Access user.
Navigate to the Admin Home page
Click Parts in the Products section. The Parts Administration page opens.

The Integration button allows you to view the Salesforce CRM product integration.
Click Sales Catalogue Integration to view the Part and BOM Sync Request status or to perform a One-Time Sync Request.
To view a sync log, click the link under Log.
To initiate a One Time Sync Request for Part or BOM sync, enter one of the following:
- Part Identifier - enter a list of comma-separated part numbers
- BOM Identifier - enter a list of comma-separated Bill Sequence IDs
- From Date - enter the date or select the calander date for either the Part or BOM one time sync request
  Notes:
  - When running the One-Time Part or BOM Sync, only specify one of the entry options. An error will occur is you provide both the Identifier and a From Date.
  - The log file name will identify if a specific run occurred as part of the recurring synchronization or it was a one-time sync triggered by a user.
  - Unlike batch synchronization, the One-Time Part or BOM Sync is NOT triggered after the One-Time Part Sync.
Click Run.

NOTES

After the Generic integration has been created, the details can be retrieved using BMQL and used in a BML integration to send messages to the external service. Example BMQL is provided below.

intSettings = bmql(“select username, password, requestUrl FROM integration.genericIntegration WHERE name = $intName");

For password security, do not include in thowerror message or print the password value within the BML script. Otherwise when the BML print log is enabled, the cleartext password will be visible in the bm.log.

Generic Integration

Overview

Administration

NOTES

Related Topics