Diagnose and Manage Event-Based Oracle Fusion Applications Integrations

You can self-diagnose the delivery of business events between Oracle Fusion Applications and Oracle Integration, such as determining if delivery issues are occurring in Oracle Fusion Applications or Oracle Integration. You can also perform some management tasks, such as retrying the delivery of business events that have failed.

The event handling framework (EHF) capability of Oracle Fusion Applications enables application business event propagation beyond the boundary of Oracle Fusion Applications. When an Oracle Fusion Applications business event is generated, the EHF ensures that the event information is enriched according to the needs of the subscriber and passed to the subscriber across the boundary. In the case of Oracle Integration, the EHF provides business event support for the following adapters configured using the Basic Authentication and OAuth security policies:
  • Oracle ERP Cloud Adapter
  • Oracle CX Sales and B2B Service Adapter (previously known as the Oracle Engagement Cloud Adapter)

An integration subscribes to business events with these adapters. When the business event is raised in the application, the EHF passes the event payload to Oracle Integration, which invokes the integration.

With the self-diagnostic capabilities of Oracle Integration, you can:

  • Diagnose Oracle Fusion Applications event-triggered integrations.
  • Minimize the need to file Oracle Fusion Applications escalations and service requests.
  • Review and self-service business event integration-related issues.
For example, assume you have the following scenario in which business events are not received by Oracle Integration:
  • User A manages logistics for ABC Corporation and is informed about a large shipment dispatch for an important customer.
  • User A observes that the notification has not appeared in the application.
  • User A contacts User C, who manages Oracle Fusion Applications at ABC Corporation, and shares their concern about the lack of a notification.
  • User C sees that the business event has been correctly created.
  • However, neither User A nor User C have any idea about how to diagnose where the event disappeared. They consider logging a service request with Oracle for troubleshooting.

    With the self-diagnostic capabilities in Oracle Integration, these users can self-diagnose message delivery, thereby reducing the need to create a service request for some basic information.


    When business events are not delivered to Oracle Integration, self-diagnosis typically indicates that the error occurred within Oracle Fusion Applications boundaries. Open a service request with Oracle Fusion Applications and include all necessary error messages to aid support in troubleshooting the issue.
  1. In the navigation pane, click Observability, then Fusion Applications.


    The Fusion Applications option in the navigation pane is only visible to users with the ServiceAdministrator role. For all other users, this option is not visible.
    The Fusion Applications page shows the list of deployed adapter connections and their role (trigger, trigger and invoke). To be shown in the Fusion Application page, the connections must satisfy the following conditions:
    • Must be either the Oracle ERP Cloud Adapter or Oracle CX Sales and B2B Service Adapter.
    • Must be a trigger or trigger and invoke role. Invoke alone is not supported.
    • Must be in a configured state.

    From this page, you can:

    • Review basic event information about configured applications.
    • Browse the selected application and see subscribed events in detail.
    • Review detailed information about failed messages for the selected application.
    Key features in the table include the following:
    • The Filter Filter icon enables you to search on connection name, user that created the connection, user that updated the connection, adapter type (Oracle ERP Cloud Adapter or Oracle CX Sales and B2B Service Adapter), and connection role (all, trigger, or trigger and invoke)
    • The Name column shows the connection name and the Oracle Fusion Applications hostname that was specified in the Properties section of the Connections page. This enables you to identify the host on which the event was generated.
    • The Project id column shows the ID of the project to which a connection belongs. If the connection is not part of any project (known as a connection that is globally available), the column cell is empty.

    • The Type column shows the adapter used by this connection.

    The Fusion Applications page lists the number of current connections. Below this is a table with columns for Name, Project id, Type, Usage, Last updated, and Status.

  2. Hover over a connection row, and click View event list for the Fusion Applications instance View event list for the Fusion Applications instance icon to view details about business event subscriptions on the Oracle Fusion Applications host. See Monitor Business Event Delivery Status.

Monitor Business Event Delivery Status

You can view details about business event subscriptions, including their status (queued, delivered, retried, and retries that have reached their limit) and potential reasons for why a business event has not been delivered to Oracle Integration. You can also retry the delivery of business events.

The Events page for the Oracle Fusion Applications host is shown. It includes a Status Overview section and a filter. Below this is a message about the number of events. Below this is a table with columns for Name, Subscriptions, Queued, Delivered, Retried, and Maxed out retries.

  1. Click Filter Filter icon to adjust the time range for gathering event details.
  2. Hover your cursor over a business event row, and click View View icon.
    The Event details panel opens. By default, the status is set to Maxed out retries.
  3. Click Filter Filter icon if you want to change the time range and the status of business events to display:
    • Maxed out retries (the default status)
    • Retried
    • Queued
    • Delivered
  4. Click Apply.
    For the following example, Maxed out retries is selected and business events that have reached their retry limit are displayed.

    The Event details page shows the currently set filters. Below this is the number of event instances. Below this is a table with columns for Event instance ID, Subscriber, Date, and Reason.

  5. Click Open Details Open details icon
    A reason for the error is displayed. For this example, the business event never triggered the integration in Oracle Integration. This may be because the message is stuck in Oracle Fusion Applications or there is a networking issue.

    The Event details page shows the currently set filters. Below this is the number of event instances. Below this is a table with columns for Event instance ID, Subscriber, Date, and Reason. Below this the reason is given for the error.

  6. If you want to attempt business message delivery again, select the event instances to retry and click Retry. You can also click Event instance ID to retry all event instances. The maximum number of retries is 10. After that, the event's status is moved to Maxed out retries. The event then requires a manual intervention (retry). Once you click Retry, the event is queued for retry, but its state has not yet changed. Therefore, that event is still shown. You must refresh the page and check to see if the event's status has changed.