The concept of Business Events in the context of EBS plays a critcal role in enabling event-driven integration with other systems outside the application.
In addition to that, the Business Events in E-Business Suite in particular allow for an exceptionally effective way of decoupling the standard product functionality, available out of the box, from client customizations that seek to adapt the standard product to meet customer-specific business needs. In other words, Oracle Applications developers should consider using Business Events whenever possible when configuring and customizing the standard products.
What are Business Events
“A business event is an occurrence in an internet or intranet application or program that might be significant to other objects in a system or to external agents.”
For example, the creation of a purchase order is an example of a business event in a purchasing application
Oracle Business Events =>Architecture
The Oracle Workflow Business Event System is an application service that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate business events between systems.
The Business Event System consists of the Event Manager and workflow process event activities
- Is available with both standalone and E-Business Suite Workflow
- Provides event driven processing
- Allows Application modules and external systems to raise events
- Facilitates Oracle Application modules and external system to subscribe to these events
- Subscriptions can be synchronous or asynchronous
Do you know,
- 11i10 E-Business Suite is preconfigured with 915 Business Events
- Each Business Event represents a ready to use Integration or extension point
- 915 Outbound Integration/extension points
- 915 Inbound Integration/extension points
- Integration points centered around the major E-Business Suite flows like p2p, o2c etc
Typically Business events Component can be best understood as:
Transactional Diagram of business Events can be best understood as:
Below is Architectural Diagram for Inbound Business Events , typical flow consist of
- Event Name
- Event Parameter
- Unique Event Key (auto generated)
Below is Architectural Diagram for Outbound Business Events , typical flow consist of
- Creates deferred subscription to the selected
- Deferred subscription transfers the event to the customer queue (WF_BPEL_Q)
- Unique consumer is created automatically
Event Manager for Oracle Applications
The Oracle Workflow Event Manager lets you register interesting business events that may occur in your applications, the systems among which events will be communicated, named communication agents within those systems, and subscriptions indicating that an event is significant to a particular system. The Event Manager also performs subscribtion processing when events occur.
Subscriptions for Business Events
- Events that trigger custom code
- Events that send information to Workflow
- Events that send information to other queues or systems
where you can Uses of Business Events
- System integration messaging hubs
- Distributed applications messaging
- Message-based system integration
- Business-event based workflow processes
- Non-invasive customization of packaged applications
PLSQL vs Java Business Event System
Oracle Workflow provides Business Event System implementation within the database (PLSQL) and in the middle tier (Java).
The implementation is exactly the same in terms of the event subscription processing in both these layers but the only difference is how the Developer wants to leverage Business Event System's capabilities for event processing requirements.
With the availability of Business Event System implementation in PLSQL and Java, different subscription processing scenarios can be achieved.
How to Proceed if Business events are required to use
- Design your Business Event/s
- Define your event
Setting Up the Business Event System [Adopted workflow user documentation]
To set up the Business Event System and enable message propagation, perform the following steps:
- If you want to communicate business events between the local system and external systems, create database links to those external systems.
- If you want to use custom queues for propagating events, set up your queues.
- Check the Business Event System setup parameters.
- Schedule listeners for local inbound agents.
- Schedule propagation for local outbound agents.
- If you are using the version of Oracle Workflow embedded in Oracle Applications, synchronize event and subscription license statuses with product license statuses.
- Ensure that the WF_CONTROL queue is periodically cleaned up to remove inactive subscribers.
For Creating a event in R11i or R12 you can refer to Oracle documentation .