2413 rfsa
From UG
Contents |
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
- Mapping CT_bo#Estimated_Export_Pick_Up_Date
- Logic: This date CANNOT be set until the previous two dates have been sent
Origin Terminal actual ATD
- Mapping CT_bo#Origin_Terminal_Actual_Date
- Logic: This date CANNOT be set until the previous three dates have been sent
Port of loading actual ATD
- Mapping CT_bo#Port_Of_Loading_Actual_Date
- Logic: This date CANNOT be set until the previous four dates have been sent
Port of Tranship ATA (if applicable)
- Mapping CT_bo#Trans_Shipment_Actual_Date
- Logic: This date CANNOT be set until the previous five dates have been sent
Port of discharge ATA
- Mapping CT_bo#Port_Of_Discharge_Actual_Date
- Logic: This date CANNOT be set until the previous six dates have been sent
Destination Terminal ATA
- Mapping CT_bo#Destination_Terminal_Actual_Date
- Logic: This date CANNOT be set until the previous seven dates have been sent
delivery date
- Mapping CT_bo#Actual_Delivery_Date
- Logic: This date CANNOT be set until all of the previous dates have been sent
