2413 rfsa

From UG

(Difference between revisions)
Jump to: navigation, search
 
(44 intermediate revisions not shown)
Line 1: Line 1:
-
[[Category:Misc]]
+
[[Category:RFSA]]
-
== General Info ==
+
<div style="background-color:lightSteelBlue">
-
Dates on CT2 are supposed to be confirmed in the specific orders.
+
-
== Business Requirements ==
+
== Parent Mantis ==
-
* 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 ==
+
0002413: [Nov Dec Twks] Date Validation
-
* 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
+
 +
0001670: (Feature: Constraints On Dates) .....................<parent>
-
=== MOT:Ocean LCL ===
+
==Info==
-
'''Notification Date'''
+
-
:* Mapping: [[CT_bo#Notification_Date]]
+
-
:* Logic: This date MUST be set before any other dates
+
-
'''Authorized on'''
+
Dates should be confirmed in the specific sequence and in chronological order. 
-
:* Mapping [[CT_bo#Authorized_On]]
+
-
:* Logic: This date CANNOT be set until the Notification date has been set
+
-
'''Export pick up actual date'''
+
Dates can be confirmed the using same as or after the previous date entered.
-
:* Mapping [[CT_bo#Estimated_Export_Pick_Up_Date]]
+
-
:* Logic: This date CANNOT be set until the previous two dates have been set
+
-
'''Origin Terminal actual ATD'''
+
== Requirements ==
-
:* Mapping [[CT_bo#Origin_Terminal_Actual_Date]]
+
-
:* Logic:  This date CANNOT be set until the previous three dates have been set
+
-
'''Port of loading actual ATD'''
+
System should not allow dates to be confirmed out of this specified order. If an attempt is made to confirm a date out of order an error message should be generated and the date should not be saved.
-
:* Mapping [[CT_bo#Port_Of_Loading_Actual_Date]]
+
-
:* Logic: This date CANNOT be set until the previous four dates have been set
+
-
'''Port of Tranship ATA''' (if applicable)  
+
*The error message should indicate the details of the error (what date is causing the error)
-
:* Mapping [[CT_bo#Trans_Shipment_Actual_Date]]
+
**Example: Actual arrival date cannot be confirmed until actual departure date has been confirmed.
-
:* Logic:  This date CANNOT be set until the previous five dates have been set
+
**Example 2:  Actual delivery date cannot be confirmed until actual departure and actual arrival dates have been confirmed.
-
'''Port of discharge ATA'''
+
The system must allow each of the dates to be the same as the previous date.
-
:* Mapping [[CT_bo#Port_Of_Discharge_Actual_Date]]
+
-
:* Logic:  This date CANNOT be set until the previous six dates have been set
+
-
'''Destination Terminal ATA'''
+
===FCL shipments===
-
:* Mapping [[CT_bo#Destination_Terminal_Actual_Date]]
+
Notification date
-
:* Logic:  This date CANNOT be set until the previous seven dates have been set
+
-
'''delivery date'''
+
Actual collection date  
-
:* Mapping [[CT_bo#Actual_Delivery_Date]]
+
*Only required to be filled in if an estimated collection date is filled in
-
:* Logic:  This date CANNOT be set until all of the previous dates have been set
+
-
=== MOT:Ocean FCL ===
+
Origin terminal actual date
 +
*Only required if radio button is set to yes indicating the origin terminal is different from the port of loading
 +
Port of loading actual date
 +
Port of trans-ship actual date
 +
*Only if check box is checked indicating this record has a trans-shipment point
 +
Port of discharge actual date
-
=== MOT:Air ===
+
Destination terminal actual date
 +
*Only if radio button is set to yes indicating the destination terminal is different than the port of discharge
 +
 
 +
Actual delivery date or delivery comment
 +
 
 +
===LCL shipments===
 +
Notification date
 +
 
 +
Actual export pickup Date
 +
*Only if the estimated export pickup date is entered
 +
 
 +
Origin terminal actual date
 +
*Only if radio button is set to yes indicating it would differ from Port of Loading actual date
 +
 
 +
Port of loading actual date
 +
 
 +
Port of trans-ship actual date
 +
*Only if check box is checked indicating this record has a trans-shipment point
 +
 
 +
Port of discharge actual date
 +
 
 +
Destination terminal actual arrival date
 +
*Only if radio button is set to yes indicating the destination terminal is different than the port of discharge
 +
 
 +
Actual delivery date or delivery comment
 +
 
 +
===Air===
 +
Notification date
 +
 
 +
Actual export pickup date
 +
*Only if the estimated export pickup date is entered
 +
 
 +
Airport of departure actual time of departure
 +
 
 +
Trans-shipment airport actual time of departure
 +
*Only if check box is checked indicating this record has a trans-shipment point
 +
 
 +
Airport of destination actual time of arrival
 +
 
 +
Actual delivery date or delivery comment
 +
 
 +
===Estimated dates===
 +
 
 +
A conflict between estimated dates and actual dates should not cause an error message – the actual dates can be before or after the estimated dates.
 +
 
 +
Validations of estimated dates are no longer required.  Estimated dates should be for information purposes only.
 +
 
 +
• Exception to the above is the estimated export pick up date.  Only to be used as an indicator that the system should be requiring an actual export pickup date.
 +
 
 +
 
 +
</div>

Current revision as of 21:27, 27 January 2011


Contents

[edit] Parent Mantis

0002413: [Nov Dec Twks] Date Validation

0001670: (Feature: Constraints On Dates) .....................<parent>

[edit] Info

Dates should be confirmed in the specific sequence and in chronological order.

Dates can be confirmed the using same as or after the previous date entered.

[edit] Requirements

System should not allow dates to be confirmed out of this specified order. If an attempt is made to confirm a date out of order an error message should be generated and the date should not be saved.

  • The error message should indicate the details of the error (what date is causing the error)
    • Example: Actual arrival date cannot be confirmed until actual departure date has been confirmed.
    • Example 2: Actual delivery date cannot be confirmed until actual departure and actual arrival dates have been confirmed.

The system must allow each of the dates to be the same as the previous date.

[edit] FCL shipments

Notification date

Actual collection date

  • Only required to be filled in if an estimated collection date is filled in

Origin terminal actual date

  • Only required if radio button is set to yes indicating the origin terminal is different from the port of loading

Port of loading actual date

Port of trans-ship actual date

  • Only if check box is checked indicating this record has a trans-shipment point

Port of discharge actual date

Destination terminal actual date

  • Only if radio button is set to yes indicating the destination terminal is different than the port of discharge

Actual delivery date or delivery comment

[edit] LCL shipments

Notification date

Actual export pickup Date

  • Only if the estimated export pickup date is entered

Origin terminal actual date

  • Only if radio button is set to yes indicating it would differ from Port of Loading actual date

Port of loading actual date

Port of trans-ship actual date

  • Only if check box is checked indicating this record has a trans-shipment point

Port of discharge actual date

Destination terminal actual arrival date

  • Only if radio button is set to yes indicating the destination terminal is different than the port of discharge

Actual delivery date or delivery comment

[edit] Air

Notification date

Actual export pickup date

  • Only if the estimated export pickup date is entered

Airport of departure actual time of departure

Trans-shipment airport actual time of departure

  • Only if check box is checked indicating this record has a trans-shipment point

Airport of destination actual time of arrival

Actual delivery date or delivery comment

[edit] Estimated dates

A conflict between estimated dates and actual dates should not cause an error message – the actual dates can be before or after the estimated dates.

Validations of estimated dates are no longer required. Estimated dates should be for information purposes only.

• Exception to the above is the estimated export pick up date. Only to be used as an indicator that the system should be requiring an actual export pickup date.


Retrieved from "https://wiki.jaguarfreight.com/2413_rfsa"
Personal tools