Web Facelift – Enquiry Function (Business Quick Status)
The purpose is for user to review the status of full shipment cycle.
=======================================================
Open PO  PO on Hand  On The Water  Arrived at Discharge Port
=======================================================
A.
Open PO – To capture all POs or PO/Items are not yet booked during a
specific period
**
Focus on Non-cancelled POs
Checking Logic
#1
If there is no ship window in PO, then use “PO Last Updated Date” as the
checking parameter
 PO or PO/item is not yet booked (Partial Shipment)
 PO Last Updated Date is between “SYSDATE – n days” and “SYSDATE”
#2
If there is the ship window in PO Header level, then use “Last Ship Date” as the
checking parameter
 PO or PO/item is not yet booked (Partial Shipment)
 Last Ship Date is between “SYSDATE – x days” and “SYSDATE”
Case (a)
Case (b)
#3
Else if the ship window exists in PO Item level, then use “Last Ship Date” as the
checking parameter
 PO or PO/item is not yet booked (Partial Shipment)
 Last Ship Date is between “SYSDATE – y days” and “SYSDATE”
Case (a)
Case (b)
**
If scenario 2 & 3 are coexisted, then the checking logic should be based on
scenario 3 (the lowest level)
#4
If there is ONLY Early Ship Date in PO Header level, then use “Early Ship
Date” as the checking parameter
 PO or PO/item is not yet booked (Partial Shipment)
 Early Ship Date is between “SYSDATE – x days” and “SYSDATE + y days”
#5
Else If ONLY Early Ship Date exists in PO Item level, then use “Early Ship
Date” as the checking parameter
 PO or PO/item is not yet booked (Partial Shipment)
 Early Ship Date is between “SYSDATE – x days” and “SYSDATE + y days”
**
If scenario 4 & 5 are coexisted, then the checking logic should be based on
scenario 5 (the lowest level)
B.
PO on Hand – To capture all POs are booked but not yet shipped during a
specific period
** Non-cancelled booking
Checking Logic
#1
If PO is booked but without FCR information
 Not show if “Booking Last Updated Date” is more than n days.
That means to show the PO records with “Booking Last Updated Date” between
“SYSDATE – n days” and “SYSDATE”, which are not associated with any FCR
#2
Else if FCR exists with booked PO
 ETD is between “SYSDATE” and “SYSDATE + x days”
C.
On the Water – To capture all the containers that are on the water (Sailing)
during a specific period
**
**
Sea Shipments only
Non-cancelled shipments
Checking Logic
#1
“ETA Discharge Port” at shipment level is between “SYSDATE + x days” and
“SYSDATE + y days”
D.
Arrived at Discharge Port - To capture the containers to be scheduled arrival
at Discharge Port (within a period) **** NEXT PHASE****
**
**
Suggest considering the MCC Hubs and normal shipments only
Non-cancelled shipments
Checking Logic
#1
“ETA Discharge Port” at shipment level is between “SYSDATE – x days” and
“SYSDATE-y days”
Supporting Table – Master Setup for Web Tracking Query
Suggest setting the date range with “FROM” and “TO” parameters and also with
“Minus”, “Plus” concepts. So, it would be more flexible to set up for different customers.
i.e.
PO Last Updated Date is between “SYSDATE – n days” and “SYSDATE”
 Then “PO Last Updated” -- FROM “-” n days TO “-/+” 0 day
i.e.
“ETA Discharge Port” at shipment level is between “SYSDATE + x days” and
“SYSDATE + y days”
 Then “ETA Discharge Port” – FROM “+” x days TO “+” y days
??? If no setting, then ignore the checking? Or get all the records?