CT Dates

From UG

Revision as of 16:34, 11 January 2010 (edit) Alex (Talk | contribs) (→Ver 1.4) ← Older edit		Revision as of 16:35, 11 January 2010 (edit) (undo) Alex (Talk | contribs) (→Ver 1.7) Newer edit →
Line 117:		Line 117:
	=== Ver 1.7 ===		=== Ver 1.7 ===
-	* 0001492: (Ops Misc) (CT Dates) Add required conditions for entering "actual" dates	+	* mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1492
	==== Part A. Error logic ====		==== Part A. Error logic ====

---

Revision as of 16:35, 11 January 2010

Contents 1 Intro 2 History 2.1 Ver 1.1 2.2 Ver 1.2 2.3 Ver 1.3 2.4 Ver 1.4 2.5 Ver 1.5 Should not be able to set ANY actual date beyond the current date 2.5.1 UNDEF 2.5.2 Truck-Dom 2.5.3 Truck-Air 2.5.4 Truck-Ocn 2.5.5 AIR 2.5.6 LCL 2.5.7 FCL 2.6 Ver 1.6 For Truck-Ocean remove Export Pick Up and Delivery dates from Gen tab 2.7 Ver 1.7 2.7.1 Part A. Error logic 2.7.2 Part B. Error Messages 2.8 Ver 1.8

Intro

This article covers:

• Common CT dates logic
• CT Dates Tab in CT profile

History

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

New more strict conditions/logic for setting CT dates:

• mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1410

• 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

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

LCL

Gentab:

• Actual export pickup

Exptab:

• Origin Terminal ATD
• Port Of Loading ATD
• Port Of Trans-shipment ATA
• Port Of Discharge ATA
• Destination Terminal ATA

ImpTab:

• Actual Delivery Date

FCL

Conttab.Containers:

• ContainerX.Actual collection
• ContainerX.Actual Delivery

Exptab:

• Origin Terminal ATD
• Port Of Loading ATD
• Port Of Trans-shipment ATA
• Port Of Discharge ATA
• Destination Terminal ATA

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.

Ver 1.7

• mantis: http://mantis.jaguarfreight.com/mantis/view.php?id=1492

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).

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).

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"