Basic Enhanced Order Monitor operation, with Milestones

Answer

Configuration:

Milestone configured:
Milestone(Has Been in status) is configured which will check if the order is in 1500(Scheduled) status for x hrs (0.167 hrs=10 mins) and raise an alert.

Working:

Here are the steps followed for controlled testing:
1. Create an order

2. Schedule the order. Hence moving it to 1500 status
NEXT_ALERT_TS= 12:06:30 PM (current system date)

3. Trigger the monitor agent.
NEXT_ALERT_TS = 12:16:31 PM (current sys date + 10 min)

4. Change any attribute in the order
NEXT_ALERT_TS = 12:16:33 PM (current system date)

5. Trigger the monitor agent.
NEXT_ALERT_TS = 12:26:34 PM (current sys date + 10 min)


The next_alert_ts stamp is seen from the YFS_ORDER_HEADER table

Hence any change in the order will cause the NEXT_ALERT_TS to be stamped as current date. When the Enhanced Order Monitor is run, it will check the status of the order, if it does match, depending on the elapsed hour setting, it will update the NEXT_ALERT_TS.

Enhanced order monitor does not pick up closed orders for monitoring.

Working of Enhanced Order Monitor with respect to threads:

To understand how do threads work in conjunction with the monitoring rules, lets consider an example where we have 50 monitoring rules, for a YFS_ORDER_HEADER table having 1,00,000 records and the monitor being configured with 4 threads.

In this case, when the monitor is triggered, a query will be fired to fetch all open records from the YFS_ORDER_HEADER table. Now the threads configured, will work on the resultant set of records and for each Order, all the monitoring rules will be checked. Hence in case of 4 threads, 4 orders will be picked up at a time and for each of these orders, all the 50 rules will be checked.