Bookshelf Home | Contents | Index | Search | PDF

Siebel Connector for Oracle Applications > Developer Procedures > Integration Overview >

Integration Dependencies and Steps

---

The interdependencies and recommended sequence of data loads are shown in Figure 3.

Figure 3. Integration Dependencies

Figure 3 shows the integrations initiated by the System Administrator and by Users. As the figure indicates, integrations should be run in the following order:

Organizations. This integration takes place during the setup, before all other integrations. During the initial setup, Organizations are created in Siebel Applications and loaded with Oracle Operating Unit data.
Inventory Locations. This integration take places during the Setup, well before the Product integration. During the initial setup, Inventory Locations are created in Siebel and loaded with Oracle Inventory Organizations data.
Product. This integration associates Siebel integration object Product - Get Oracle Item (Siebel Applications) with the Oracle Applications R10.7 integration object Product - Get Oracle Item (Oracle Applications) or the Oracle Applications R11i integration object Product - Get Oracle11i Item (Oracle Applications). Product integration (also known as Product Catalog Import):
Incorporates Oracle multi-organization support. Items are transferred from the Oracle inventory master organization. Associations with other Inventory Organizations are also created in Siebel Applications.
Price List. In this operation, Oracle Price Lists, Discounts, and Price List Line Items are integrated into the Siebel Admin Price List business object.

Price List integration:

Imports an Oracle price list. For data consistency, Oracle Applications should be the Price List master. Changes to Price Lists should be performed in the Oracle application and brought into Siebel Applications through Connector processes.
Uses a base unit-of-measure.
Discounts. Discount data is pulled from the Oracle Applications and integrated into Siebel Applications. This integration associates Siebel business components with Oracle Discount information through the following mappings:
Oracle Discount Lines are mapped to the Siebel Volume Discount business component.
Oracle Discounts Price Breaks are mapped to the Siebel Volume Discount Item business component. These are Unit, not Monetary, Volume Price Breaks.

NOTE:  In Oracle Applications, a new Discount Line can be created for an item that exists under the same Discount but at a different time period. By contrast, in Siebel Applications there is a one-to-one relationship between a Price List item and a Discount. For this reason, only active Oracle Discount Lines are pulled into a Siebel application as Volume Discounts.

Generally, this integration (also known as Discount Rule Import):

Imports Oracle Applications discount rules.
Creates Discount Price List.
Accounts. This two-way integration maps Siebel Account-to-Oracle Customer data and Oracle Customer-to-Siebel Account data. See User Procedures for information about the steps and workflow for this integration.

In summary, this integration:

Starts with data captured by Siebel Applications. After that, changes are made at either side.
Permits synchronization of customer contacts, telephone numbers, and addresses between the two applications.
Maintains Oracle Applications address, customer, and site numbering hierarchy.
Involves near real-time synchronization, triggered by update events at Siebel Applications and alerts at Oracle Applications.
Orders. Performed by Users, this is the final integration. All other integrations must precede it. This two-way integration maps Siebel Order-to-Oracle Order data and Oracle Order-to-Siebel Order Status data. User Procedures describes the steps and workflow for this integration.

In summary, this integration (also referred to as Ordering and Order Status Update):

Supports the creation of an order without a quote, deferring to Oracle Applications for price calculation or creation of an order with a quote using a price list imported from Oracle Applications.
Allows tax and shipping costs to be estimated within the Siebel application. However, the final invoice figure is determined by Oracle Applications.
Uses a back office applet to submit orders (using the Submit button) into Oracle Applications in near real-time. Orders can be submitted as Enter or Booked.
Freezes an order in Siebel Applications once it is submitted. Changes are made only in Oracle Applications.
Checks credit in Oracle Applications. The result of a credit check is reported in the Order Status field.
Allows order line changes in Oracle Applications.
Transmits order status and updates asynchronously back to the Siebel application at regular intervals, or transmits order status and updates synchronously on-demand in real-time using a Get Status button on the Siebel Applications back office applet.

Bookshelf Home | Contents | Index | Search | PDF