2413 rfsa

From UG

Revision as of 19:45, 2 November 2010 (edit) Montira (Talk | contribs) (→Detail Requirements) ← Older edit		Revision as of 20:03, 2 November 2010 (edit) (undo) Tracie (Talk | contribs) Newer edit →
Line 20:		Line 20:
	'''Authorized on'''		'''Authorized on'''
-		+	:* Mapping [[CT_bo#Authorized_On]]
		+	:* Logic: This date CANNOT be set until the Notification date has been sent

---

Revision as of 20:03, 2 November 2010

Contents 1 General Info 2 Business Requirements 3 Detail Requirements 3.1 MOT:Ocean LCL 3.2 MOT:Ocean FCL 3.3 MOT:Air

General Info

Dates on CT2 are supposed to be confirmed in the specific orders.

Business Requirements

• Operator should not be allowed to enter dates in incorrect orders. If a date is entered out of the order, system should show an error message and the date should not be saved.
• These dates are under different tabs per mode of transportation.

Detail Requirements

• NOTE: Each date below MUST be entered in order as the following order dates below.
• Example: MOT: Ocean LCL, Destination Terminal ATA date cannot be entered before Port of discharge ATA date is entered. And Port of discharge ATA cannot be entered before Port of Tranship ATA date is entered (if this date is application),...etc

MOT:Ocean LCL

Notification Date

• Mapping: CT_bo#Notification_Date
• Logic: This date MUST be set before any other dates

Authorized on

• Mapping CT_bo#Authorized_On
• Logic: This date CANNOT be set until the Notification date has been sent

Export pick up actual date

Origin Terminal actual ATD

Port of loading actual ATD

Port of Tranship ATA (if applicable)

Port of discharge ATA

Destination Terminal ATA

delivery date

MOT:Ocean FCL

MOT:Air