Bookshelf Home | Contents | Index | PDF     

Siebel Connector for Oracle Applications > Developer Procedures > Siebel and Oracle Applications R10.7 Integrations >

Integration Workflows

Each integration is managed through a workflow. This section provides descriptions of the predefined workflows associated with each Siebel Applications and Oracle Applications R10.7 and Oracle Applications R11i integration.

Organization Inbound Workflow

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

NOTE:  Because they are similar, the Oracle Applications R10.7 and Oracle Applications R11i Organization Inbound integrations are discussed together in this section.

This integration involves the following processes:

  1. A SQL script is run.

    For Oracle Applications R10.7:
    siebelgeneral107script_notify_org.sql

    For Oracle Applications R11i:
    siebelgeneral11iscript_notify_org.sql

  2. The script inserts records into the Notification Table for all the Oracle Organizations with the following attributes:
    • For Oracle Applications R10.7:

      OBJECT_NAME: Organization - Get Oracle Operating Unit (Oracle Applications)

      TBL_NAME: SIE_ORG_V

    • For Oracle Applications R11i:

      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:
    • For Oracle Applications R10.7:
      Organization - Receive Oracle Operating Unit workflow, passing the instance of the Oracle integration object as a parameter.
    • For Oracle Applications R11i:
      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.

      Click for full size image
  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:
      • For Oracle Applications R10.7:
        Organization - Get Oracle Operating Unit (Siebel Applications), using the Org Maps - Siebel Inbound DTE business service.
      • For Oracle Applications R11i:
        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. A SQL script is run.
    • For Oracle Applications R10.7:

    siebelgeneral07iscript_notify_invloc.sql

    • For Oracle Applications R11i:

    siebelgeneral1iiscript_notify_invloc.sql

  2. The script inserts records into the Notification Table for all the Oracle Inventory Organizations with the following attributes:
    • For Oracle Applications R10.7:

      OBJECT_NAME: InvLoc - Get Oracle Org (Oracle Applications)
      TBL_NAME: SIE_INVLOC_V

    • For Oracle Applications R11i:

      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:
    • For Oracle Applications R10.7:

      InvLoc - Receives Oracle Organization workflow and loads all inventory Locations into the Siebel application.
    • For Oracle Applications R11i:

      InvLoc - Receives Oracle11i Organization workflow and loads all inventory Locations into the Siebel application.

      The workflow diagram for this process is shown below.

      Click for full size image
  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:
      • For Oracle Applications R10.7:

        InvLoc - Get Oracle Org (Siebel Applications), using the InvLoc Maps - Siebel Inbound DTE business service.
      • For Oracle Applications R11i:

        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.

NOTE:  Because they are similar, Oracle Applications R10.7 and Oracle Applications R11i Product Inbound integrations are discussed together in this section.

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:
    • For Oracle Applications R10.7:

    OBJECT_NAME = Product - Get Oracle Item (Oracle Applications)
    TBL_NAME = SIE_PRODUCT_V

    • For Oracle Applications R11i:

    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:

    • For Oracle Applications R10.7:
      Product - Receive Oracle Item workflow and loads the item into the Siebel application.
    • For Oracle Applications R11i:
      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.

      Click for full size image
  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 eBusiness 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).

NOTE:  This verification procedure is the same for products created in either Oracle Applications R10.7 or Oracle Applications R11i.

Price List Inbound Workflow

Price Inbound integration transforms Oracle Price Lists, Discounts, and Price List Line Items into the Siebel Admin Price List business object. The elements of this process are discussed below.

Comparing Price List and Discounts

Price List and Discounts are differently related in Oracle Applications and Siebel Applications. These differences are shown in Figure 4.

Figure 4. Oracle and Siebel Price List Data Models
Click for full size image

As this comparison of data models indicates, an Oracle Price List can be associated with multiple Discounts and Price List Lines. Each Discount can be associated with multiple Discount Lines. In addition, you can specify a Price Break for each element in the Price List.

Discount Line Item

In Siebel Applications, Discounts are not associated with any Price Lists. However, you can associate a Discount with every Price List Item within a Price List. Siebel business components are associated with Oracle Price List information through the following mappings, which are supplied with the Siebel Connector for Oracle Applications:

  • Oracle Price Lists are mapped to the Siebel Price List business component without Discounts attached to its Price List items. Oracle Discounts are also mapped to the Siebel Price List business component with Discounts attached to its Price List items.
  • Oracle Price List Lines are mapped to the Siebel Internal Product business component.

Only active Oracle Price List Items are pulled into the Siebel application; Oracle Price List Items with attached pricing rules are not pulled in. Therefore, in this integration, only Active Oracle Price List Items are pulled into the Siebel application.

This integration involves the following processes:

  1. An insertion or change to a price list or price list line in Oracle Applications fires an Oracle alert.

    The Price List alerts are:

    Siebel Price Lists Insert

    Siebel Price Lists Update

    Siebel Price Lists Lines Insert

    Siebel Price Lists Lines Update

  2. The alert creates an entry in the Siebel Notification Table with the following attributes:

    For Price Lists:

    • OBJECT_NAME = Pricing - Get Oracle Price List (Oracle Applications)
    • TBL_NAME = SIE_PRICE_LISTS_V

      For Price LIst Lines:

    • OBJECT_NAME = Pricing - Get Oracle Price List (Oracle Applications)
    • TBL_NAME = SIE_PRICE_LIST_LINES_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 price list.
    3. Calls the Database Adapter to extract details of the price list into an instance of the integration object Pricing - Get Oracle Price List (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 Pricing - Receive Oracle Price List workflow and loads the Price List into the Siebel application.

    The workflow diagram for this process is shown in the following figure.

    Click for full size image
  5. The Pricing - Receive Oracle Price List workflow:
    1. Maps the instance of the Oracle integration object to an instance of the Siebel Applications integration object Pricing - Get Oracle Price List (Siebel Applications), using the Price Maps - Siebel Inbound DTE business service.
    2. Runs EAI Siebel Adapter with the Execute method to enter the new price list or price list changes into Siebel Applications.

To verify that a new Oracle Applications Price List has been sent to Siebel Applications

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

  1. Open the Call Center or another Siebel eBusiness application.
  2. Select the Pricing tab.
  3. Under the Price List tab, click the row containing the new Price List.

    The screen displays details about the new Price List.

Discount Inbound Workflow

Discount Inbound integration transforms Oracle Applications R10.7 Discount Items and Price Breaks into the Siebel Admin Volume Discount business object.

This process is summarized below.

  1. An Oracle alert or trigger fires when one of the changes listed below occurs in Oracle Applications.
    1. Insertion or update to a Discount Line

      Launches alert:

      • Siebel Discount Lines Insert

        or
      • Siebel Discount Lines Update
    2. Insertion, update, or deletion of a Price Break

      Launches alert:

      • Siebel Price Break Lines Insert

        or

      • Siebel Price Break Lines Update

        or

      • SIE_SO_PRICE_BRK_TR
  2. Discount Lines alerts create an entry in the Siebel Notification Table with the following attributes:

    OBJECT_NAME: Discount - Get Oracle Discount (Oracle Applications)

    TBL_NAME: SIE_DISCOUNT_LINES_V

  3. Price Break Lines alerts and triggers create an entry in the Siebel Notification Table with the following attributes:

    OBJECT_NAME: Discount - Get Oracle Discount (Oracle Applications)

    TBL_NAME: SIE_PRICE_BREAK_LINES_V

  4. The Oracle Receiver polls the Notification Table and gets the new entry. In response, the Receiver:
    1. Creates a query specification integration object instance to locate the Discount Line item.
    2. Calls the DB Adapter to extract the details of the Discount Line item into an Oracle integration object instance of Discount - Get Oracle Discount (Oracle Applications).

      In this integration object, the root integration component SIE_DISCOUNT_LINES_V is based on the SIE_DISCOUNT_LINES_V view. The child integration component SIE_PRICE_BREAK_LINES_V is based on the SIE_PRICE_BREAK_LINES_V view.

    3. Executes the Oracle Receiver Dispatch Workflow, passing the integration object instance as a parameter.
  5. The Oracle Receiver Dispatch Workflow calls the Discount - Receive Oracle Discount workflow, passing the Oracle integration object instance as a parameter.

    The workflow diagram for this process is shown below.

    Click for full size image
  6. The Discount - Receive Oracle Price List workflow:
    1. Maps the Oracle integration object instance to a Siebel integration object instance of Discount - Get Oracle Discount (Siebel Applications), using the Discount Maps - Siebel Inbound DTE business service.
    2. Runs the eAI Siebel Adapter, with the Execute method, to enter the new Volume Discount, Volume Discount Item, Volume Discount changes, or Volume Discount Item changes into Siebel Applications.

To verify that a new or recently updated Oracle Discount has been sent to Siebel Applications

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

  1. Using a Siebel eBusiness Application (for example, Sales), select the Pricing tab.
  2. Select Volume Discounts or Volume Discount Items in the pull-down box.
  3. Click on the line displaying a discount for details.

Account Outbound Workflow

Account Outbound integration propagates the Siebel application integration object Account Get/Put Oracle Customer to the Oracle Applications R10.7 integration object Account - Put Oracle Customer. The predefined workflow for this integration is described in the following figure.

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

Click for full size image

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 Components and populates the Siebel Integration Object Account - Get/Put Oracle Customer (Siebel Applications).
  3. Map Siebel Account to Oracle Customer—Executes the Business Service Account Maps - Siebel Outbound which maps the data from the Siebel Integration Object Account - Get/Put Oracle Customer (Siebel Applications) into the Oracle Integration Object Account - Put Oracle Customer (Oracle Applications).
  4. Write Oracle Customer to Buffer Tables—Executes the Business Service eAI Database Adapter, which reads the data from the Oracle Integration Object Account - Put Oracle Customer (Oracle Applications) and inserts it into the Oracle Buffer Tables.
  5. Validate and Copy to Interface—Executes the Business Service eAI ODBC Service, which runs the pre-validation program SIE_CUSTOMER_PREVAL_PR' 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 and also 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 the data in the Siebel Message created in the previous Loop Back to Siebel processes.
  8. End.

    NOTE:  Once data is put 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. These error messages are brought into Siebel by the Account - Receive Oracle Customer Import Status workflow.

Mapping Discussion

Several Siebel application to or from Oracle Applications mappings require extra consideration. These mapping issues are discussed below.

  • Oracle Customer Profiles

    During the Siebel Applications to Oracle Applications integration, an Oracle customer profile (class Default) is created for each new customer and new address whose SITE_USE_CODE = BILL_TO in the RA_CUSTOMER_PROFILES_INT_ALL interface table.

  • Telephone Number Mapping

    Telephone numbers are stored differently in Siebel and Oracle data models.

    In Siebel Applications, telephone numbers are stored as fields within the Account, Business Address, and Contact business components. In an Oracle application, telephone numbers are stored in a separate RA_PHONES table that is joined to the Customer, Address, and Contact tables. The PHONE_TYPE column is used to identify the type (FAX, PHONE, and so on) of the phone number.

  • Multiple site uses for an address

    Oracle Applications allow multiple site uses for an address in the RA_SITE_USES_ALL table. In Siebel Applications, the Bill Address Flag, Ship Address Flag, and Main Address Flag fields of the Business Address business component similarly correspond to the BILL_TO, SHIP_TO, and GENERAL site uses, respectively.

    The Primary Bill To Address Id, Primary Ship To Address Id, and Primary Address Id fields of the Account business component identify the address for each function that will perform a primary role. This corresponds to a setting of PRIMARY_SITE_USE_FLAG=Y in the Oracle RA_SITE_USES_ALL table.

    Site uses for an address must be set before the address is submitted to Oracle Applications. Once the address has been submitted to Oracle Applications, no changes are supported. At least one site use must be specified for each address.

Account Inbound Workflow

During Account Inbound integration, the Oracle Applications R10.7 integration object Account - Get Oracle Customer is transformed into the Siebel integration object Account - Get/Put Oracle Customer.

This integration involves the following processes:

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

    The alerts are:

    • Siebel Customer Profile Insert
    • Siebel Customer Contact Insert
    • Siebel Customer Phones Insert
    • Siebel Customer Profile Update
    • Siebel Customer Address Update
    • Siebel Customer Contact Update
    • Siebel Customer Phones Update

      Phone numbers can be deleted in the Connector. The trigger for deleting phone numbers is:

    • SIE_PHONE_DEL_TR
  2. The alert creates an entry in the Siebel Notification Table with the following attributes:

    For Accounts:

    • OBJECT_NAME = Account - Get Oracle Customer (Oracle Applications)
    • TBL_NAME = RA_CUSTOMERS

      For Addresses:

    • OBJECT_NAME = Account - Get Oracle Customer (Oracle Applications)
    • TBL_NAME = RA_ADDRESSES_ALL

      For Contacts:

    • OBJECT_NAME = Account - Get Oracle Customer (Oracle Applications)
    • TBL_NAME = RA_CONTACTS

      For Profiles:

    • OBJECT_NAME = Account - Get Oracle Customer (Oracle Applications)
    • TBL_NAME = SIE_CUSTOMER_PROFILE_AMOUNTS

      For Phones:

    • OBJECT_NAME = Account - Get Oracle Customer (Oracle Applications)
    • TBL_NAME = RA_PHONES
  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 DB Adapter to extract details of the customer into an instance of the integration object Account - Get Oracle 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 Oracle Customer workflow and loads the Account into the Siebel application.

    The predefined workflow for this integration is described as follows.

    Click for full size image

    The Account - Receive Oracle Customer workflow:

    1. Maps Oracle Customers to the Siebel Accounts Business Service.

      Account Maps - Siebel Inbound is called to convert data from the Oracle integration object to the Siebel integration object for Account.

    2. Write Accounts to Siebel database is updated with an appropriate Siebel integration object instance using the eAI Siebel Adapter.

Order Outbound Workflow

Order Outbound integration propagates the Siebel eBusiness integration object Orders - Get/Put Oracle Orders (Oracle Applications) to the Oracle Application R10.7 integration object Orders - Put Oracle Orders (Siebel Applications). The predefined workflow for this integration is described below.

NOTE:  Because a Discount_Id is needed to adjust prices, you may not be able to manually adjust prices if the price list has no discounts and if price lists and discounts exist in Oracle Applications, Order Outbound Integration passes discount and price information to Oracle Applications.

Click for full size image

As the workflow diagram shows, this integration involves the following steps:

  1. Start—The workflow starts when a new outbound order is submitted.
  2. Read Siebel Order—Executes the Business Service eAI Siebel Adapter which reads the data from the Siebel Business Components and populates the Siebel Integration Object Orders - Get Oracle Orders (Siebel Applications).
  3. Map Siebel to Oracle Order—Executes the Business Service Order Maps - Siebel Outbound, which maps the data from the Siebel Integration Object Orders - Get Oracle Orders (Siebel Applications) into the Oracle Integration Object Orders - Put Oracle Orders (Oracle Applications).
  4. Write Order to Buffer Tables—Executes the Business Service eAI SQL Adapter which reads the data from the Oracle Integration Object Orders - Put Oracle Orders (Oracle Applications) and inserts it into the Oracle buffer tables.
  5. Validate and Copy to Interface—Executes the Business Service EAI ODBC Service, which runs the prevalidation program SieOrderValidate and inserts records from the buffer table into the Oracle Interface tables.
  6. Loop Back to Siebel—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. Write to Siebel Order—Executes the Business Service EAI Siebel Adapter, which updates the Order in Siebel with the data in the Siebel message, created in the previous Loop Back to Siebel process.
  8. Ends—The workflow is complete. The Oracle interface tables are updated with order data.

    NOTE:  Once data is loaded into Oracle interface tables, the Order import is run in the Oracle application. If the import fails, the interface_status column in the interface table is updated with the error message. The Order - Receive Oracle Order Import Status workflow brings these messages into the Siebel application.

Get Oracle Order Status Workflow

Following is the Order Outbound - Get Oracle Order Status workflow.

Click for full size image

The Order Outbound - Get Oracle Order Status workflow involves the following steps:

  1. The workflow starts when a request for the Oracle Order Status is submitted.
  2. Branches on Integration ID check.
    • If Integration ID is not null, goes to next step.
    • Otherwise, issues a Get Status Failed message and ends.
  3. Gets order changes from Oracle by invoking the Oracle Receiver, which calls the Order Inbound workflow. For more information, refer to Order Outbound Workflow.
  4. End—The workflow is complete.

Order Inbound Workflow

Orders Inbound integration associates the Siebel integration object Orders - Put -Oracle Orders (Siebel Applications) with the Oracle integration object Orders - Get Oracle 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 Oracle alerts are:

    • Siebel Schedule Details Insert
    • Siebel Order Line Insert
    • Siebel Order Hold Insert
    • Siebel Shipment Details Insert
    • Siebel Order Header Update
    • Siebel Schedule Details Update
    • Siebel Order Line Update
    • Siebel Order Hold Update
    • Siebel Shipment Details Update

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

    • SIE_ORDER_HEADER_DEL_TR
    • SIE_ORDER_LINE_DEL_TR
  2. The alert makes an entry in the Siebel Notification Table with the attributes listed below.

    For Orders:

    • OBJECT_NAME = Orders - Get Oracle Orders (Oracle Applications)
    • TBL_NAME = SIE_HEADERS_ALL_V

      For Order Lines:

    • OBJECT_NAME = Orders - Get Oracle Orders (Oracle Applications)
    • TBL_NAME = SIE_LINES_ALL_V

      For Shipment details:

    • OBJECT_NAME = Orders - Get Oracle Orders (Oracle Applications)
    • TBL_NAME = SIE_SHIPMENT_QUANTITIES_V

      For Schedule details:

    • OBJECT_NAME = Orders - Get Oracle Orders (Oracle Applications)
    • TBL_NAME = SIE_SCHEDULE_QUANITITIES_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 Oracle Adapter to extract details of the Order into an instance of the integration object Orders - Get Oracle 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 Order - Receive Oracle Order workflow and loads the order into the Siebel application.

This predefined workflow for this integration is described as follows.

Click for full size image

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

  1. Start—The Oracle Receiver starts this workflow.

    For more information, refer to Understanding the Oracle Receiver.

  2. Maps the Oracle Orders to Siebel Orders—Business Service Order Maps - Siebel Inbound is called to convert data from the Oracle integration object to the Siebel integration object for Orders.
  3. Write the Order to Siebel—The EAI Siebel Adapter updates the Siebel database with an appropriate Siebel integration object instance.
  4. Ends—The workflow is complete.
    
Siebel Connector for Oracle Applications