Commerce Integration Attribute Mapping

Beginning in Oracle CPQ 22B, administrators can to sort and reorder mapped rows on the Commerce Integration Attribute Mapping page. The mapped rows can be sorted by the CPQ Attribute or the Mapped Attribute column in ascending or descending order. Sorting rows by the CPQ Attribute allows administrators to easily identify all attributes that are conditionally mapped to the same target attribute.

Sort Mapped Attribute Rows

The following image displays attribute mapping without sorting. Notice that the highlighted conditionally mapped rows are not grouped together.

When the administrator sorts the attribute mappings by the CPQ Attribute, the conditionally mapped rows are grouped together. This makes it easier to quickly identify Oracle Oracle CX Sales attributes that are mapped to the same CPQ attribute. Administrators need to click Save to retain the sorted attribute order.

Reorder Attribute Mapping Rows Using Drag and Drop

Administrators can also drag and drop attributes to reorder the mapped rows. Sorting rows by allows administrators to easily identify all attributes that are conditionally mapped to the same target attribute. Additionally, administrators can drag and drop items to reorder mapped rows in the order they prefer. Sorting rows by allows administrators to easily identify all attributes that are conditionally mapped to the same target attribute. Additionally, administrators can drag and drop items to reorder mapped rows in the order they prefer.

In the following image, the CPQ Parent Asset Key attribute was selected, and then dragged and dropped below the CPQ Instance ID attribute.

• When mapping row is in edit mode, it cannot be dragged and dropped.
• If you sort after dragging and dropping an attribute, the reordered attribute position will be lost.
• Administrators need to click Save to retain the reordered attribute position, which could have been arrived at by a combination of sort and manual resequencing.

Reorder Attribute Mapping Rows Using Drag and Drop

Administrators can also drag and drop attributes to reorder the mapped rows. In the following image, the CPQ Parent Asset Key attribute was selected, and then dragged and dropped below the CPQ Instance ID attribute.

• When mapping row is in edit mode, it cannot be dragged and dropped.
• If you sort after dragging and dropping an attribute, the reordered attribute position will be lost.
• Administrators need to click Save to retain the reordered attribute position, which could have been arrived at by a combination of sort and manual resequencing.

Beginning in Oracle CPQ 22A administrators can define conditional logic for the import of sub-document Commerce REST integration mappings. Conditional mapping allows the mapping of two source attributes to the same target attribute. When two source attributes are mapped to one target attribute, conditions must be defined to determine which of the source attributes to use. When conditions for the primary source attribute are not met, the secondary (default) mapping will be used.

The predefined response attribute mapping for the REST Import Revenue Lines Integration contains conditional mapping for several attributes. When two source attributes are mapped to the same target attribute, the conditional mapping icon is displayed for both mappings.

As shown in the following image, there are four instances where two Oracle CX Sales attributes (i.e. source attributes) are mapped to the same CPQ attribute (i.e. target attribute). The mappings with conditional mapping are outlined in blue, and the conditional mapping icon is outlined in red. Since both mapped attributes have the same condition, you can click on either conditional mapping icon to view the conditional mapping for the target attribute.

Edit Conditions Dialog for Conditional Mapping

To access the conditional logic for mapped items, click on the conditional mapping icon. The following image displays the conditional mapping for the CPQ Model Segment Variable Name attribute:

• Select one of the two attribute mappings from the Conditional Attribute Mapping drop-down.

  The selected mapping is used when the Condition is satisfied (e.g. Model Segment Variable Name = Product Group Model Family).

• Action based on: The action can be based on All Conditions, Any Conditions, or Complex Conditions.

• A "Condition" is defined by selecting the Attribute, Operator, and Value.

  (e.g. Product Type is equal to "Group")

  • Attribute: Select a Oracle CX Sales attribute for the condition (e.g. Product Type)
  • Operator: Available operators are based on the selected attribute type.
  • Value: Enter a value for the condition
• Click Add New Condition to define additional conditions.

• The Else – Default is automatically set to attribute mapping that isn't selected for the If Condition.

  (e.g. Model Segment Variable Name = Product Model Family)

Beginning in Oracle CPQ 22B, the Attribute Mapping page will highlight missing attributes that are used in mappings as well in conditions and provide an error message when the administrator double clicks on the highlighted attribute. Informing CPQ administrators of missing Oracle CX Sales attributes prevents errors when an integration is run.

The Edit Conditions dialog will also provide an error message about which Oracle CX Sales attribute used in the condition has been deleted. For example, when a deleted CX attribute causes an invalid condition, the condition rule editor will denote which attribute has been deleted.

New customers will have these mappings defined as part of the provisioned reference implementation. Existing customers will have a migration package to create this standard integration. Administrators can complete the following steps to add new attribute mappings or edit the existing attribute mappings.

1. Log in to Oracle CPQ and open the Admin Home page.
2. Click Process Definition, in the Commerce and Documents section.
3. Select Integrations from the Navigation drop-down menu for the applicable process, and then click List.
4. Click on the REST – Export Lines integration name.
5. Click Edit next to Request Mapping.
6. Click the Add Row icon or drag and drop an attribute to create a new attribute mapping row.
   1. Select the appropriate CPQ attribute on the left side.
   2. Select the appropriate Oracle CX Sales attribute on the right side.

   3. Click on the Apply icon or click outside the row to register the mapping.

      

7. To delete an attribute mapping, click on the delete icon.
8. To edit an existing attribute mapping, click on the edit icon.
9. Click Save to save changes, or Finish to save changes and exit the page.

CPQ provides new customers with predefined Oracle CX Sales integrations. Existing customers can import a migration package to implement the predefined integration content. The following the predefined attribute mappings are available for Oracle CX Sales REST Integrations.

Sync Quote Lines - REST Export Lines

REST Import Opportunity - REST Import

REST Upsert Quote - REST Export

REST Line Sync Complete - REST Export

REST Import Revenue Lines - REST Import