Troubleshooting
Problem
Shipment monitor 'Has Not Reached' rule still raises alert for a reached status >>Order,milestone,cancelled
Symptom
PART: Platform-Config 5.0 SP2 Platform
PRODUCT: Distributed Order
Management
I am using the 'Milestone has not Reached before a date'
rule.
Relevant pipeline:
ASN Created (1100.001) -> ASN Submitted
(1100.005) -> ASN Confirmed (1100.010) .....
Have created a milestone
for ASN Submitted and set the time to 48 hrs and it checks for 'Requested
Delivery Date'. I find that if I create a shipment and move it to 'ASN
Submitted' and then run the shipment monitor it still raises an alert. This
should not happen as it has already gone past the milestone.
Can you
confirm this is a problem. We are on 5.0sp2
Similar problem is - We find
the system raising alerts for Cancelled Shipments when we are tracking only
ASN_LOADED and ASN_SUBMITTED.
Cause
Resolving The Problem
Troubleshooting Steps.
1. First Confirm that the Event Raised is for the
correct Milestone.
2. In situations where you have multiple milestones, but
using the same raise Events, this is a common mistake to do.
The event
could be raised for the Other Milestone. In this case the client was using the
same event for both ASN_LOADED and ASN_SUBMITTED.
You can track this
behavior by querying the YFS_SHIPMENT.NEXT_ALERT_TS and YFS_MONITOR_ALERT where
FIELD1='ShipmentKey'
you will notice that even when the Shipment reaches the
ASN_SUBMITTED Milestone.
It will have a NEXT_ALERT_TS as DELIVERY_DATE+48h
for the next MILESTONE namely ASN_LOADED.
If you change your event for
ASN_LOADED to something else, You will be able to differentiate that event
triggered is NOT the event linked to ASN Submitted.
3. There is a
related problem here with using the NOT condition
When you define the
MILESTONE say REACHED_ASN_LOADED and you intend to use it as a negative test.
Then you should include all SAFE statuses as part of that milestone.
So for
REACHED_ASN_LOADED, All statuses (1100 to 1400.005 should be
included).
4. It would be a good idea to included Cancelled Status also
in the milestone status, because a cancelled Order
will NOT HAVE REACHED
the ASN_LOADED status ever. You dont want to be repeatedly raising an alert for
this.
Historical Number
PRI49318
Product Synonym
[<p><b>]Fact[</b><p>];
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21541798