An Example of Using a Business Event as a Trigger (Source) in an Integration

Sample Business Scenario

A business event "Event for OIP status update notification" (oracle.apps.ont.oip.statuschange.update) is used in this example to explain using the Oracle E-Business Suite Adapter to trigger an integration in Oracle Integration.

In this example, when a sales order is booked as part of the business flow, Oracle Order Management raises the event oracle.apps.ont.oip.statuschange.update, and a draft invoice is created in Oracle Accounts Receivables.

At the design time, you need to create an integration called "Order to Invoice" with Oracle E-Business Suite Order Management as a trigger (source) connected through the Oracle E-Business Suite Adapter and Oracle E-Business Suite Accounts Receivables as an invoke (target) connected through a generic REST Adapter. The "Order to Invoice" integration will subscribe to this business event.

During the runtime, when the status of the sales order is changed in the order header, the business event oracle.apps.ont.oip.statuschange.update is raised in Oracle E-Business Suite Order Management which triggers the integration. If the status of the sales order is "Booked", the order details information is fetched from Oracle E-Business Suite Order Management. The Oracle E-Business Suite Adapter prepares and propagates the order details as event payload from Order Management to invoke the integration endpoint in Oracle Integration. As a result, the draft invoice is created in Oracle Accounts Receivables.

Assumption

  • Assume that REST services are directly accessible from Oracle Integration; therefore, Oracle Integration Connectivity Agent is not used in this example.

  • Oracle E-Business Suite Order Management and Oracle E-Business Suite Accounts Receivables are two different instances used in this example.

Based on the integration scenario, the sample tasks for using an Oracle E-Business Suite business event in an integration are included in the Topics section: