Shipment

From UG

Revision as of 20:44, 10 July 2013 (edit) Alex (Talk | contribs) (→SOWs) ← Older edit		Revision as of 14:01, 24 July 2013 (edit) (undo) Andrei (Talk | contribs) (→SOW 1) Newer edit →
Line 191:		Line 191:
	* 0/ there should be at least one commodity line (all MOTs)		* 0/ there should be at least one commodity line (all MOTs)
-	* 1/ all commodities must be assigned to containers (all ocean MOTs)	+	* 1/ there should be at least one container (all ocean MOTs)
		+
		+	* 2/ all commodities must be assigned to containers (all ocean MOTs)
	** Error message should say: "Error: Not all commodities are assigned to containers"		** Error message should say: "Error: Not all commodities are assigned to containers"
-	* 2/ each container of this CT records must have at least ONE commodity assigned (FCL only)	+	* 3/ each container of this CT record must have at least ONE commodity assigned (all ocean MOTs)
	** Error message should specify container's numbers that have no assignments		** Error message should specify container's numbers that have no assignments
		+
		+	* 4/ in Master case, system should validate all CTs contained in Master
	NOTE: Now we have similar validation when Actual Delivery date is set. Remove it.		NOTE: Now we have similar validation when Actual Delivery date is set. Remove it.

---

Revision as of 14:01, 24 July 2013

Contents 1 Shipment 2 CT 3 Master 4 MOTs defined 5 Lifecycle 5.1 Events 5.2 Milestones 5.2.1 Origin Door 5.2.2 Destination Door 5.2.3 Path 5.3 Lanes 5.3.1 Geography From To 5.3.2 Shipper to Consignee Lane 6 Fields 6.1 Shipper Consignee Notify 6.1.1 Shipper 6.1.2 Consignee 6.1.3 Notify 6.2 Geography 6.2.1 Origin country 6.2.2 Destination country 6.2.3 Export Pick Up 6.3 Dates 6.3.1 Actual Departure Date 6.3.2 Actual Delivery Date 7 Validations 8 See Also 9 SOW 1 9.1 Commodity and Container related validations

Shipment

Shipment is by definition:

• in case of Truck with TMS it is a "TMS load"
• in all other cases it is:
  • a group of CTs (if GRP exists) or
  • individual CT (if it is not a part of a group)

CT

Master

MOTs defined

MOT = Mode Of Transport.

CT2 system has these MOTs defined:

• Undefined
• Air
• LCL
• Client Consol
• FCL(AW)
• FCL(MLB)
• Truck Air
• Truck Domestic
• Truck Ocean

Lifecycle

There are key #Events and key #Milestones in terms of geographical path.

Events

• Approval or Authorization

Milestones

Origin Door

• in CT2 called #Export Pick Up

Destination Door

• truck ocean / tr dom / tr air : Gen Tab > Export Delivery To (T5)
• Ocean / Air : Imp Tab > Delivery Address (Import Delivery Location)(T7):

Path

Path for Air:

• "departure" from "origin door"
• "arrival" to origin airport
• ""

Key points for Ocean:

Lanes

We have 2 different flavors of Lane term:

Geography From To

Geography From To is defined as a pair {From, To} where From and To could have 3 different types of values:

• Any (indicates that there is no restriction)
• Region
• Country

Shipper to Consignee Lane

It is defined as a pair {From, To} where From = #Shipper and To = #Consignee.

Fields

Shipper Consignee Notify

Shipper

Gen Tab > 2. Shipper (T1):

Consignee

Gen Tab > 3. Consignee (T2):

Notify

Gen Tab > 4. Notify (T3):

Geography

Origin country

Defines country of origin door and related note.

Origin Country selector:

• Combobox with a list of countries
• UI: Gen Tab > 11. Origin country
• DB: tblGenericShipment.OriginPointCountryId (join with tblCountry)
• Required? No

Origin Country Note:

TBD

Destination country

Defines country of destination door and related note.

• Combobox with a list of countries
• UI: Gen Tab > 12. Destination country
• DB: tblGenericShipment.DestinationPointCountryId (join with tblCountry)
• Required? No

Destination Country selector:

TBD

Export Pick Up

Defines #Origin Door.

• Combobox with a list + Textarea with address (pre-filled by system)
• UI: Gen Tab > 5. Export Pick-up (T4)
• MOTs: all
• DB: ???

Dates

Actual Departure Date

Air

Ocean FCL

Port of Loading, Actual Time of Departure (Exp Tab > 12c. ATD)

Ocean LCL and Client Consol

Port of Loading, Actual Time of Departure (Exp Tab > 12c. ATD)

Trucking Domestic

Trucking Air

Trucking Ocean

Earliest among Actual Collection dates in container table.

Actual Delivery Date

Air

Ocean FCL

Ocean LCL and Client Consol

Trucking Domestic

Trucking Air

Trucking Ocean

Latest among Actual Delivery dates in container table.

Validations

See Also

• Shipment Milestones and Phases
• CT

SOW 1

Commodity and Container related validations

mantis: 4206

Add validations for the session when user sets Actual Departure Date:

• 0/ there should be at least one commodity line (all MOTs)

• 1/ there should be at least one container (all ocean MOTs)

• 2/ all commodities must be assigned to containers (all ocean MOTs)
  • Error message should say: "Error: Not all commodities are assigned to containers"

• 3/ each container of this CT record must have at least ONE commodity assigned (all ocean MOTs)
  • Error message should specify container's numbers that have no assignments

• 4/ in Master case, system should validate all CTs contained in Master

NOTE: Now we have similar validation when Actual Delivery date is set. Remove it.

Also after Actual Departure Date is set and user attempts to:

• remove all commod lines
• change container assignments to leave one of them unassigned

system should prevent users giving error.