Siebel Connector for Oracle Applications > Developer Procedures > Siebel and Oracle Applications Integrations >

Integration Workflows

Each integration is driven by a workflow. This section provides an annotated workflow diagram for each Siebel application and Oracle Applications integration.

NOTE:  There are alternate names for some of the business services described in this section. The Database Adapter (or DB Adapter) is also known as the EAI SQL Adapter, and the Oracle Procedure Adapter is also known as EAI ODBC Service.

Organization Inbound Workflow

Organization Inbound integration transforms Oracle Operating Units into Siebel Internal Division business objects.

This integration involves the following processes:

1. The SQL script siebelgeneral11iscript_notify_org.sql is run.
2. The script inserts records into the Notification Table for all the Oracle Organizations with the following attributes:
   • OBJECT_NAME: Organization - Get Oracle11i Operating Unit (Oracle Applications)
   • TBL_NAME: SIE_ORG_V
3. The Oracle Receiver:
   1. Polls the Notification Table and gets the entry.
   2. Creates a query specification integration object instance that locates the particular operating unit.
   3. Calls the DB Adapter to extract details of the operating units into an instance of the Oracle integration object.
   4. Executes the Oracle Receiver Dispatch Workflow, passing the instance of the integration object as a parameter.
4. The Oracle Receiver Dispatch Workflow calls:
   • Organization - Receive Oracle11i Operating Unit workflow, passing the instance of the Oracle integration object as a parameter.

     The workflow diagram for this process is shown in the following figure.
5. The Organization - Receive Oracle Operating Unit workflow:
   1. Maps the instance of the Oracle integration object to an instance of the Siebel integration object:
      • Organization - Get Oracle11i Operating Unit (Siebel Applications), using the Org Maps - Siebel Inbound (OracleR11i) DTE business service.
   2. Runs the EAI Siebel Adapter with the Execute method to enter the new Oracle organizations into Siebel Applications.

NOTE:  The Siebel Connector for Oracle Applications provides scripts to load Oracle operating units into Siebel Applications. These scripts must be run every time a new operating unit is created in Oracle Applications so that it can be created in Siebel Applications.

Inventory Locations Inbound Workflow

Inventory Locations integration transforms Oracle Inventory Organizations data into the Siebel Inventory Location business component. This integration involves the following processes:

1. The SQL script siebelgeneral1iiscript_notify_invloc.sql is run.
2. The script inserts records into the Notification Table for all the Oracle Inventory Organizations with the following attributes:
   • OBJECT_NAME: InvLoc- Get Oracle11i Org (Oracle Applications)
   • TBL_NAME: SIE_INVLOC_V
3. The Oracle Receiver:
   1. Polls the Notification Table and gets the entry.
   2. Creates a query specification integration object instance that locates the particular inventory Organization.
   3. Calls the Database Adapter to extract details of the Inventory Organization into an instance of the Oracle integration object.
   4. Executes the Oracle Receiver Dispatch Workflow, passing the instance of the integration object as a parameter.
4. The Oracle Receiver Dispatch Workflow calls:
   • InvLoc - Receives Oracle11i Organization workflow and loads all inventory Locations into the Siebel application.

     The workflow diagram for this process is shown below.
5. The InvLoc-Receive Oracle Organization workflow:
   1. Maps the instance of the Oracle Applications integration object to an instance of the Siebel Applications integration object:
      • InvLoc - Get Oracle11i Org (Siebel Applications), using the InvLoc Maps - Siebel Inbound DTE business service.
   2. Runs the EAI Siebel Adapter with the Execute method to enter the new inventory locations into Siebel Applications.

      NOTE:  The Siebel Connector for Oracle Applications provides scripts to load Oracle Applications Inventory Organizations into Siebel Applications. These scripts must be run every time a new Inventory Organization is created in Oracle Applications so that it can be created in Siebel Applications.

Product Inbound Workflow

Product Inbound integration transforms an Oracle Applications orderable global master material item into a Siebel Internal Product business object.

The integration involves the following processes.

1. An insertion or change to a material item in Oracle Applications fires an Oracle alert or trigger. The material item alert is Siebel Product Update.

   NOTE:  The Connector also incorporates a trigger SIE_UPDATE_ITEMS_TR. The alert makes an entry into the Notification Table for every update in the Oracle base table. On the other hand, the trigger checks for the CUSTOMER_ORDER_ENABLED_FLAG and makes entries accordingly. You can disable the alert and enable the trigger to reduce the volume of entries in the Notification Table.

2. The alert creates an entry in the Siebel Notification Table with the following attributes:
   • OBJECT_NAME = Product - Get Oracle11i Item (Oracle Applications)
   • TBL_NAME = SIE_PRODUCT_V
3. The Oracle Receiver:
   1. Polls the Notification Table and gets the entry.
   2. Creates a query specification integration object instance that locates the particular material item.
   3. Calls the DB Adapter to extract details of the material item into an instance of the integration object Product - Get Oracle Item (Oracle Applications). This object is based on the SIE_PRODUCT_V view.
   4. Executes the Oracle Receiver Dispatch Workflow, passing the instance of the integration object as a parameter.

      The Oracle Receiver Dispatch workflow calls:

   • Product - Receive Oracle 11i Item workflow and loads the item into the Siebel application.

     The diagram for this workflow process is shown in the following figure.
4. The Product - Receive Oracle Item workflow:
   1. Maps the instance of the Oracle Applications integration object to an instance of the Siebel Applications integration object Product - Get Oracle Item (Siebel Applications), using the Product Maps - Siebel DTE business service.
   2. Runs EAI Siebel Adapter with the Execute method to enter the new product or product changes into Siebel Applications.

To verify that a product created in Oracle Applications has passed to Siebel Applications

The Oracle Receiver automatically brings new and updated Product data to Siebel Applications at the next scheduled run. To verify the data transfer:

1. Open the Call Center or another Siebel Business application.
2. Select the Products view and query for the product created in Oracle Applications.
3. Click the row containing the product.
4. Select a tab for additional information (for example, Details).

Account Outbound Workflow

Account outbound integration propagates the Siebel Applications integration object Account Put Oracle11i Customer (Siebel Applications) to the Oracle Application R11i integration object Account - Put Oracle 11i Customer (Oracle Applications). The predefined workflow for this integration is described below.

CAUTION:  Oracle does not support site use changes on the Siebel or Oracle side after the address is created in the Oracle application.

Account - Create or Update Oracle 11i Customer Workflow

Following is the Account - Create or Update Oracle 11i Customer workflow.

As the workflow diagram indicates, the process involves the following steps:

1. Start.
2. Read Siebel Account—Executes the Business Service EAI Siebel Adapter which reads the data from the Siebel Business Service components and populates the Siebel integration object Account - Put Oracle11i Customer (Siebel Applications).
3. Map Siebel Account to Oracle Customer—Executes the Business Service Account Maps - Siebel Outbound (Oracle Applications 11i) that maps data from the Siebel integration object Account - Put Oracle 11i Customer (Siebel Applications) into the Oracle integration object Account - Put Oracle 11i Customer (Oracle Applications).
4. Write Oracle Customer to Buffer Tables—Executes the Business Service Database Adapter, which reads data from the Oracle integration object
   Account - Put Oracle 11i Customer (Oracle Applications) and inserts it into Oracle buffer tables.
5. Validate and Copy to Interface—Executes the Business Service Oracle Procedure Adapter, which runs the prevalidation program SIE_CUSTOMER_PREVAL_PR11i and inserts records from the buffer table into the Oracle interface tables.
6. Loop Back to Siebel Applications—Creates a Siebel message by setting the Integration Id for Account, Contact, and Addresses. It also sets the corresponding Status Codes, Sync Date, and Error Text (if any).
7. Write Siebel Account—Executes the Business Service EAI Siebel Adapter which updates the account in Siebel Applications with data in the Siebel message created in the previous Loop Back to Siebel process.
8. End.

   NOTE:  Once data is loaded into the Oracle interface tables, the Customer import is run in Oracle Applications. If the import fails, the interface_status column in the interface table is updated with the error message. The Account - Receive Oracle Customer Import Status workflow is used to bring these error messages into Siebel Applications.

Account Inbound Workflow

During Account Inbound integration, the Oracle Application R11i integration object Account - Get Oracle11i Customer (Oracle Applications) is transformed into the Siebel integration object Account - Get Oracle11i Customer (Siebel Applications).

This integration involves the following processes:

1. An insert or change to an Oracle Customer, Customer Address, Customer Contact, Profile, or Phone number in the Oracle application fires an Oracle alert.

   The alerts are:

   • Siebel Customer Account Insert
   • Siebel Customer Contact Insert
   • Siebel Customer Interface Header Update
   • Siebel Customer Site Insert
2. The alert creates an entry in the Siebel Notification Table with the following attributes:
   • For Accounts:
     • OBJECT_NAME = Account - Get Oracle11i Customer (Oracle Applications)
     • TBL_NAME = HZ_CUST_ACCOUNTS
   • For Contacts:
     • OBJECT_NAME = Account - Get Oracle11i Customer (Oracle Applications)
     • TBL_NAME = SIE_CONTACTS_V
   • For Customer Site:
     • OBJECT_NAME = Account - Get Oracle11i Customer (Oracle Applications)
     • TBL_NAME = SIE_ADDRESSES_V
3. The Oracle Receiver:
   1. Polls the Notification Table and gets the entry.
   2. Creates a query specification integration object instance that locates the particular Customer.
   3. Calls the Database Adapter to extract details of the customer into an instance of the integration object Account - Get Oracle11i Customer (Oracle Applications).
   4. Executes the Oracle Receiver Dispatch workflow, passing the instance of the integration object as a parameter.
4. The Oracle Receiver Dispatch workflow calls the Account - Receive Oracle11i Customer workflow and loads the Account into the Siebel application.

Account - Receive Oracle11i Customer Workflow

The predefined workflow for this integration is described as follows.

The Account - Receive Oracle11i Customer workflow:

1. Maps Oracle Customer to the Siebel Accounts—The workflow calls Business Service Account Maps - Siebel Inbound to convert data from the Oracle integration object to the Siebel integration object for Account.
2. Write Account to Siebel Applications—The EAI Siebel Adapter is used to update the Siebel database with an appropriate Siebel integration object instance.

Order Outbound Workflow

This predefined workflow propagates Order data from Siebel Applications to Oracle Applications.

This workflow process is summarized as follows.

1. Start—The workflow starts when an order outbound is submitted.
2. Reads Siebel Order—Executes the Business Service EAI Siebel Adapter, which reads data from the Siebel business components and populates the Siebel integration object Order - Put Oracle11i Order (Siebel Applications).
3. Maps Siebel Order to Oracle Order—Executes the Business Service Order Maps - Siebel Outbound (Oracle 11i), which maps data from the Siebel integration object Order - Put Oracle11i Order (Siebel Applications) into the Oracle integration object Order - Put Oracle11i Order (Oracle Applications).
4. Writes Order to Buffer Tables—Executes the Business Service EAI DB Adapter, which reads data from the Oracle integration object Order - Put Oracle11i Order (Oracle Applications) and inserts it into the Oracle buffer tables.
5. Validate and Copy to Oracle Interface—Executes the Business Service EAI ODBC Service, which runs the prevalidation program SieOrderValidate11i. The prevalidation program validates data in the buffer table and calls the Process Order API to create the order in Oracle Applications.
6. Loops Back to Siebel Applications—Creates a Siebel message by setting the Integration Id for Order and Order Line and setting the corresponding Status Codes, Sync Date, and Error Text (if any).
7. Writes to the Siebel Order—Executes the Business Service EAI Siebel Adapter which updates the Order in Siebel with data in the Siebel message created in the previous Loop Back to Siebel process.
8. End—The workflow is complete.

Order Inbound Workflow

Order Inbound integration associates Siebel integration object Order - Put Oracle11i Order (Siebel Applications) with the Oracle integration object Orders - Get Oracle11i Orders (Oracle Applications). This integration involves the following processes:

1. An insert or change to an Oracle Order or Order Line in the Oracle application fires an Oracle alert.

   The Order alerts are:

   • Siebel Order Header Insert
   • Siebel Order Header Update
   • Siebel Order Hold Insert
   • Siebel Order Hold Update
   • Siebel Order Lines Insert
   • Siebel Order Lines Update
   • Siebel Order

     The Connector allows you to delete Order Lines and Orders if the status is ENTERED. The triggers for delete are:

   • SIE_ORDER_HEADER_DEL_TR
   • SIE_ORDER_LINE_DEL_TR
2. The alert creates an entry in the Siebel Notification Table with the following attributes:
   • For Orders:
     • OBJECT_NAME = Order - Get Oracle11i Order (Oracle Applications)
     • TBL_NAME = SIE_HEADERS_ALL_V
   • For Order Lines:
     • OBJECT_NAME = Order - Get Oracle11i Order (Oracle Applications)
     • TBL_NAME = SIE_LINES_ALL_V
3. The Oracle Receiver:
   1. Polls the Notification Table and gets the entry.
   2. Creates a query specification integration object instance that locates the particular Order.
   3. Calls the Database Adapter to extract details of the Order into an instance of the integration object Orders - Get Oracle11i Orders (Oracle Applications).
   4. Executes the Oracle Receiver Dispatch Workflow, passing the instance of the integration object as a parameter.
4. The Oracle Receiver Dispatch workflow calls the Order - Receive Oracle11i Order workflow and loads the Order into the Siebel application.

Order - Receive Oracle11i Order Workflow

As the workflow indicates, this integration involves the following steps:

1. Start—The Oracle Receiver starts this workflow. For more information, see Understanding the Oracle Receiver.
2. Maps the Oracle to Siebel Order—Calls the Siebel Business Service Order Maps - Siebel Inbound to convert data from the Oracle integration object to the Siebel integration object for Orders.
3. Writes Order to Siebel Applications—The EAI Siebel Adapter is used to update the Siebel database with an appropriate Siebel integration object instance.
4. End—The workflow is complete.