CT Dates
From UG
(Difference between revisions)
(→Ver 1.5 Should not be able to set ANY actual date beyond the current date) |
(→AIR) |
||
| Line 67: | Line 67: | ||
=== AIR === | === AIR === | ||
| - | Gentab | + | Gentab: |
| + | |||
| + | * Actual export pickup | ||
| + | |||
| + | Exptab: | ||
| + | |||
| + | * Airport of Departure. ATD | ||
| + | * Trans-shipment Airport.ATD | ||
| + | * Airport Of Destination. ATD | ||
| + | |||
| + | ImpTab: | ||
| + | |||
| + | * Actual Delivery Date | ||
== Ver 1.6 For Truck-Ocean remove Export Pick Up and Delivery dates from Gen tab == | == Ver 1.6 For Truck-Ocean remove Export Pick Up and Delivery dates from Gen tab == | ||
Revision as of 20:40, 17 November 2009
Contents |
Intro
This article covers:
- Common CT dates logic
- CT Dates Tab in CT profile
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
Ver 1.2
- 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.
Ver 1.3
- 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)
Ver 1.4 Additional restrictions on assigning CT dates
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
- ss2 // for this date to be set system must:
- check that "act. departure date" (M.DetTab ** 12c. ATD: Port Of Loading) is set. If not produce error: "Actual Arrival Date can not be assigned - Actual Departure Date must be set first"
- check that ALL contents in ALL CTs under this M are assigned. If not then issue pop-up: "ctual Arrival Date can not be set - some contents are unassigned in CT# <list of CTs>"
- air:
- ss3 // actual arrival date can be set only through Master (M.DetTab 14c. ATA. Airport of Destination) - make it read only on CT
- ss4 // for this date to be set system must:
- check that "act. departure date" (M.DetTab ** Airport of Departure ATD) is set. If not produce error: "Actual Arrival Date can not be assigned - Actual Departure Date must be set first"
- truck:
- TBD
Ver 1.5 Should not be able to set ANY actual date beyond the current date
UNDEF
- Gentab.Actual export pickup
Truck-Dom
- Gentab.Actual export pickup
- Gentab.Actual Delivery
Truck-Air
- Gentab.Actual export pickup
- Gentab.Actual Delivery
Truck-Ocn
- Conttab.Containers.ContainerX.Actual collection
- Conttab.Containers.ContainerX.Actual Delivery
AIR
Gentab:
- Actual export pickup
Exptab:
- Airport of Departure. ATD
- Trans-shipment Airport.ATD
- Airport Of Destination. ATD
ImpTab:
- Actual Delivery Date
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.
