Siebel Order Management Guide Addendum for Communications > Employee Asset-Based Ordering > About Synchronizing Product Attributes, Product Classes, Products, and Promotions >

About Synchronizing Products


You can synchronize simple products with one price type and simple products with multiple price types through the integration. A simple product with, for example, two price types in Oracle Product Information Management Data Hub becomes two products in Siebel CRM. You can also synchronize complex products, that is, customizable products, through the integration.

The parameters of a product in Oracle Product Information Management Data Hub that are synchronized with Siebel CRM are as follows:

  • Default Language Code
  • Basic Product Information:
    • Product Name
    • Product line
    • Product Description
    • Structure type
  • Associated Product Line (m:m):
    • Product Line ID 1
    • Product Line ID 2...
  • Price lists:
    • Multiple price types
    • Same price list with different effective dates
  • Price List line items (one-to-many):
    • Default Price List (configurable in Siebel CRM and Oracle Application Integration Architecture)
    • Effective Date
    • Discount fields
  • Rules (one-to-many). Includes compatibility rules and recommendation messages.
    • Effective Date
    • Subject product Id, product line Id, class Id
  • Associated Class:
    • Class ID
    • Local Specific Attributes Value from inheritance (if any). This information includes Attribute Id, value sets, flags, and so on.
    • Local specific domain entity from inheritance (if any). Users can add specific products for Domain Type of Class.
  • Local Structure:
    • Relationship Name
    • Domain Type (Product, Class)
    • Cardinality (maximum, minimum, and default quantities)
    • Domain entity (class name, product name)
    • Relationship Domain (in the case of a Class domain type):
      • Product 1 Id
      • Product 2 Id...
  • Child products with relationships (for complex products):
    • Structure of parent-child relationships
    • Structure inherited from class
    • BOM

The integration does not support the synchronization of eligibility rules, or of collateral items such as image files and key features. Additionally, synchronization does not override certain product parameters. These parameters include user interface setup, configurator rules, and scripts defined in Siebel CRM. These parameters must be entered and maintained in Siebel CRM.

Most fields that are synchronized are visible in the Administration - Product screen, Detail view and the Administration - Product screen, Product Definitions view.

NOTE:  The Domain Type field value of Dynamic Class is not supported by the integration.

Siebel Order Management Guide Addendum for Communications Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.