FA: SCM: OM: How to Verify that Business Events have been Successfully Raised by an Order Management Orchestration Process. (Doc ID 1383944.1)

Last updated on DECEMBER 01, 2023

Applies to:

Goal

The Order Management Order Orchestration process has been set up to raise business events ('Notify External System') for all status updates.

However, we find that subscriptions are fired only for statuses SCHEDULED and SHIPPED. Though business events are raised for AWAIT_SHIPPING and PARTIAL_PICK statuses (as seen in the edn-db-log) we do not see the subscriptions being fired.

As a result intermediate status updates (pick/backorder) are never communicated to External Order Capture system.

The following actions are performed:

1. Orchestration process is setup with Schedule, Shipment and Invoicing Tasks and configured to raise business events for all possible status code changes using "Notify External Systems"
2. Submit a new Sales Order.
3. The order gets created in Order Management.
4. Order is scheduled and a business event is raised for change in status from CREATED to SCHEDULED.
5. Business event fires its subscription.
6. Order is sent to fulfillment system EBS.
7. Order then moves to AWAIT_SHIP status.
8. Business event is visible in edn-db-log, however business event subscriptions are not fired.
9. EBS sends intermediate status updates for picked and backordered.
10. Order Management processes these updates and fline status moves to PARTIAL_PICK status.
11. Business event is visible in edn-db-log, however business event subscriptions are not fired.
12. EBS send Shipment advise to DOO.
13. Fulfillment line status changes to SHIPPED status.
14. Business event is raised and the subscription is fired.

Is it possible to verify/trace/debug that subscriptions are firing for intermediate statuses ?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.