CT Dates
From UG
Contents |
[edit] Intro
This article covers:
- Common CT dates logic
- CT Dates Tab in CT profile
[edit] History
[edit] Ordering of dates constraint
- mantis:
- 0000334: [Ops.CT.Common.Dates] CT Dates Logic
- http://mantis.jaguarfreight.com/mantis/view.php?id=334
Please use this single rule ("Look On the dates tab):
1) starting from the top. Dates can be “same day” moving down the page, but a date cannot be “before” a date located “above” on the dates tab.
2) On the same level (actual and estimated) ther is no rule"
[edit] Ver 1.1
- ss1 // p3low // add validation to all delivery dates: Actual delivery date(s) cannot be in the future. They can only be “today” or “in the past”. (If today is jan 2 2009 and I set this date today I can not set it to any date before that).
List of Actual delivery date(s) in CT2:
- AIR or oceanLCL // ImpTab.ActualDeliveryDate
- oceanFCL or truckOcn // CntTab.ContainerTable.ContainerX.ActualDeliveryDate
- truckAir or truckDom // GenTab.y.ActualDeliveryDate
!!!! This task is a subset of #Ver 1.5 Should not be able to set ANY actual date beyond the current date
[edit] Ver 1.2
- mantis:
- 0001324: [Ops.CT.Dates] v1.2 specify CT#s in Invalid Ordering pop-up
- http://mantis.jaguarfreight.com/mantis/view.php?id=1324
- ss1 // Error pop-up we have now "Invalid ordering of dates" must clearly state what dates and in what CTs/Master have conflict. Right now it is very hard to find out when you get this error while changing date in Master Details Tab and that master have 10 CTs.
[edit] Ver 1.3
- mantis:
- http://mantis.jaguarfreight.com/mantis/view.php?id=1333
- 0001333: [Ops.CT.Dates] chg: For Actual Delivery date to be set - all contents must be assigned
- ss1 // for LCL:
- Block user from changing "ImpTab. Actual Delivery Date (LCL)" if there is at least one line in commodity table unassigned.
- ss2 // for FCL:
- Block user from changing "Container Panel.Actual Delivery date" (FCL) from empty to something for ANY container on container panel if there is at least one line in commodity table unassigned.
- ss3 // pop up text:
"Actual Delivery date can not be assigned - all commodity items must be assigned to containers"
(This is done because every commodity line must be a part of some container before it is delivered)
[edit] Ver 1.4
New more strict conditions/logic for setting CT dates:
- ocn:
- ss1 // actual arrival date can be set only through Master (M.DetTab ** 14c. Port Of Discharge ATD) - make it read only on CT
- air:
- ss3 // actual arrival date can be set only through Master (M.DetTab 14c. ATA. Airport of Destination) - make it read only on CT
[edit] Ver 1.5 Should not be able to set ANY actual date beyond the current date
See Constraints_On_Dates_(feature)#Actual_Date_can_not_be_a_future_date
[edit] Ver 1.6 For Truck-Ocean remove Export Pick Up and Delivery dates from Gen tab
For Truck-Ocean remove Export Pick Up and Delivery dates from Gen tab (estimated and actual). Total: 4 dates.
These dates are there by mistake. We have already these dates and they are per container on ContTab.Container panel.
[edit] Ver 1.7
[edit] Part A. Error logic
~ For ocean shipments: We should block the “actual departure date” if there is no “container number” We should block the “actual arrival date” if there is no “actual departure date” we should block the “delivery date” if there is no “actual arrival date” set. ~ ~ For AIR: We should block the “actual departure date” if there is no “Master Air Waybill #” We should block the “actual arrival date” if there is no “actual departure date” we should block the “delivery date” if there is no “actual arrival date” set. ~
- Note: Actual departure and actual arrival should be able to be updated in one single “save” (as opposed to enter the actual departure, save, then enter the actual arrival, then save -> same for container/awb and actual departure date, same for actual arrival and actual delivery).
[edit] Part B. Error Messages
Ocean: “A container number must be entered before the actual departure date can be confirmed” “The actual departure date must be confirmed before the actual arrival date can be confirmed” “The actual arrival date must be confirmed before the actual delivery date can be confirmed” Air: “A MAWB number must be entered before the actual departure date can be confirmed” “The actual departure date must be confirmed before the actual arrival date can be confirmed” “The actual arrival date must be confirmed before the actual delivery date can be confirmed”
- If possible the “missing” field(s) should be highlighted (low priority).
[edit] Ver 1.8
User who is trying to change master field "** 12c. ATD:(Port Of Loading)" through CT must get a blocker pop up " 12c. ATD:(Port Of Loading) can be set only through a Master"
