Transactional events

A transactional event is triggered by a change to a business object. For example, an order is created, or an order is modified.

IBM® Sterling™ Order Management System publishes transactional events to data lake and configuration and master data events to Sterling Intelligent Promising.

This integration is built of top of Integrating with other applications by using IBM Data Exchange with data publish target as kafka.

With this integration enabled, the real-time transaction events are published from Order Management System to the data lake as part of the OMS-SIP integration. These events provide operational data for analytics, reporting, and predictive modeling in the data lake environment.

The data lake uses these transaction events for:
  • Data analytics
    Analyzing order patterns, fulfillment performance, and operational metrics.
  • Predictive modeling
    Building machine learning models for demand forecasting, capacity planning, and inventory optimization.
  • Business intelligence
    Creating dashboards and reports for business insights.
  • Historical analysis
    Maintaining a complete audit trail of order and shipment lifecycle events
All transaction events follow the CloudEvents 1.0 specification and are published in JSON format.

IBM Sterling Selling and Fulfillment Suite provides below transactional events:

  • orderCreated event
    The orderCreated event provides basic order information, order lines, and order line statuses. It is published when a confirmed order is created or when a draft order is confirmed.
  • orderModified event
    This event is published whenever a confirmed order is successfully modified. It publishes basic order information along with the modified order lines and their complete status break up.
  • orderShipped event
    This event is published whenever an order is shipped either partially or completely. It publishes important information such as the shipment number, carrier service, tracking number and so on.
  • shipmentModified event
    When a Shipment is created or modified, the shipment details are published as a shipmentModified event. The same event is raised for shipment status change as well.
  • shipNodeStatusChange event
    Published when a ship node's operational status changes (Active/Inactive) using item node controls.
  • capacityAvailability event
    Published when capacity availability is updated for a ship node and resource pool combination.
  • shortagereason
    Published when inventory shortage is recorded during order fulfillment - shortage recording during picking or allocation.
  • exception
    Triggered by the backend when an exception occurs while asynchronously processing an order reassignment request initiated from the Order Hub UI.