The enhanced order monitor enables you to monitor the following situations:
The order monitor can be configured to monitor the following system date types for and Purchase Order document types:
For more information about milestones, date types, and monitoring rules, refer to the Configuring Sterling Supply Collaboration, the Configuring Sterling Distributed Order Management, and the Configuring Sterling Reverse Logistics.
If you run the Enhanced Order Monitor, you must configure and run the Close Order time-triggered transaction in all applicable pipelines. For more information about the Close Order time-triggered transaction, see Close order.
The same relog interval is used for all document types.
The following are the attributes for this time-triggered transaction:
Attribute | Value |
---|---|
Base Transaction ID | ORDER_MONITOR_EX |
Base Document Type | Order |
Base Process Type | Order Fulfillment |
Abstract Transaction | No |
APIs Called | None |
The following are the criteria parameters for this monitor:
Parameter | Description |
---|---|
Action | Required. Triggers the transaction. If left blank, it defaults to Get, the only valid value. |
Number of Records To Buffer | Optional. Number of records to retrieve and process at one time. If left blank or specified as 0 (zero), it defaults to 5000. |
EnterpriseCode | Optional. Enterprise for which the Order Monitor needs to be run. If not passed, then all enterprises are monitored. |
ColonyID | Required in a multi schema deployment where a table may exist in multiple schemas. Runs the agent for the colony. |
The following statistics are tracked for this monitor:
Statistic Name | Description |
---|---|
NumOrdersProcessed | Number of orders processed. |
NumAlertsRaised | Number of alerts raised. |
For this transaction the pending job count is the number of open orders with the value of NEXT_ALERT_TS less than or equal to (<=) the current date.
The Enhance Order Monitor transaction raises the ON_AUTO_CANCEL event, but does not cancel the order. A service on this event should be configured to cancel the order.
Transaction/Event | Key Data | Data Published* | Template Support? |
---|---|---|---|
ON_AUTO_CANCEL | ORDER_ |
YFS_ORDER_MONITOR_EX.ON_ |
Yes |
* These files are located in the following directory:
|
If a monitor rule contains a condition, the <INSTALL_DIR>/repository/xapi/template/source/smcfs/monitor/ORDER_MONITOR_EX_CONDITION.xml template file is used to obtain both the order details and the evaluating monitor rule details. See the provided <INSTALL_DIR>/repository/xapi/template/source/smcfs/monitor/ORDER_MONITOR_EX_CONDITION.xml.sample file for more details.
If the <INSTALL_DIR>/repository/xapi/template/source/smcfs/monitor/ORDER_MONITOR_EX_CONDITION.xml template file does not exist, the MonitorConsolidation->Order element of the default monitor template, the <INSTALL_DIR>/repository/xapi/template/source/smcfs/monitor/ORDER_MONITOR_EX.xml file, is used.
If the default monitor template is used, the MonitorConsolidation-> Order->OrderStatuses-> OrderStatus-> MonitorRule element is ignored and is not passed into the condition.