Examples

This section contains examples of communication with Application Document messages through the ION Service Bus. A monitor can verify a single document and various documents from different sources.

Example 1 - Single document Monitor

You define a monitor that verifies incoming Sync.SalesOrder documents. The monitor triggers an alert if a Sync.SalesOrder document contains a status change.

An ERP SalesOrder has status Hold. Inventory arrives and the order status is changed to Open, so the order can be processed. ERP issues an update to this SalesOrder and sends a Sync.SalesOrder document through the Service Bus to Event Management.

In Event Management, the monitor verifies the received Sync.SalesOrder document. Because of the status change, the monitor triggers an alert.

Example 2 - Monitor with multiple documents

You define a monitor that compares incoming Sync.SalesOrder and Sync.Shipment documents. The monitor triggers an alert if:

  • The actual shipment took place later than promised. That is: if the delivery date in the Sync.Shipment document is later than the promised delivery date in the Sync.SalesOrder document.
  • A partial shipment was performed. That is: if the delivered quantity in the Sync.Shipment document is less than the quantity in the Sync.SalesOrder document.

In ERP the status of a SalesOrder is changed from Working to Shipped. ERP sends a Sync.SalesOrder document through the Service Bus to Event Management.

The order is shipped. The warehousing application generates a Sync.Shipment document for the SalesOrder. The Status is Shipped. The Sync.Shipment document is sent, through the Service Bus, to ERP and to Event Management.

In Event Management, the monitor compares the received Sync.SalesOrder and Sync.Shipment documents and creates an alert if one of the conditions is met.