2413 rfsa

From UG

Revision as of 19:35, 2 November 2010 (edit) Montira (Talk | contribs) (→Detail Requirements) ← Older edit		Revision as of 19:37, 2 November 2010 (edit) (undo) Montira (Talk | contribs) (→Detail Requirements) Newer edit →
Line 11:		Line 11:
	=== MOT:Ocean LCL ===		=== MOT:Ocean LCL ===
	'''Notification Date'''		'''Notification Date'''
		+	:* Mapping: [[CT_bo#Notification_Date]]
		+
	'''Authorized on'''		'''Authorized on'''
		+
		+
	'''Export pick up actual date'''		'''Export pick up actual date'''
		+
		+
	'''Origin Terminal actual ATD'''		'''Origin Terminal actual ATD'''
		+
		+
	'''Port of loading actual ATD'''		'''Port of loading actual ATD'''
		+
		+
	'''Port of Tranship ATA''' (if applicable)		'''Port of Tranship ATA''' (if applicable)
		+
		+
	'''Port of discharge ATA'''		'''Port of discharge ATA'''
		+
		+
	'''Destination Terminal ATA'''		'''Destination Terminal ATA'''
		+
		+
	'''delivery date'''		'''delivery date'''

---

Revision as of 19:37, 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

MOT:Ocean LCL

Notification Date

• Mapping: CT_bo#Notification_Date

Authorized on

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