2413 rfsa

From UG

(Difference between revisions)
Jump to: navigation, search
(→Detail Requirements)
 
(23 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.
+
 +
== Parent Mantis ==
-
== Business Requirements ==
+
0002413: [Nov Dec Twks] Date Validation
-
* 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.
+
 +
0001670: (Feature: Constraints On Dates) .....................<parent>
-
== Detail Requirements ==
+
==Info==
-
* 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
+
 +
Dates should be confirmed in the specific sequence and in chronological order. 
-
=== MOT:Ocean LCL ===
+
Dates can be confirmed the using same as or after the previous date entered.
 +
== Requirements ==
-
'''Notification Date'''
+
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#Notification_Date]]
+
-
:* Logic: This date MUST be set before any other dates (Usually this date is set by default to today date as CT is created)
+
 +
*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.
-
'''Authorized on'''
+
The system must allow each of the dates to be the same as the previous date.
-
:* Mapping [[CT_bo#Authorized_On]]
+
-
:* Logic: This date CANNOT be set until the previous date has been set
+
-
:** Authorized on date cannot be set if Notification date is empty
+
-
:** Authorized on date set cannot be before Notification date set
+
-
:** Authorized on date set can be the same date or after Notification date
+
 +
===FCL shipments===
 +
Notification date
-
'''Export pick up actual date'''
+
Actual collection date  
-
:* Mapping [[CT_bo#Estimated_Export_Pick_Up_Date]]
+
*Only required to be filled in if an estimated collection date is filled in
-
:* Logic: This date CANNOT be set until the previous two dates have been set
+
-
:** Export pick up actual date cannot be set if Authorized on date is empty
+
-
:** Export pick up actual date set cannot be before Authorized on date set
+
-
:** Export pick up actual date can be set the same date or after Authorized on date
+
 +
Origin terminal actual date
 +
*Only required if radio button is set to yes indicating the origin terminal is different from the port of loading
-
'''Origin Terminal ATD'''
+
Port of loading actual date  
-
:* Mapping [[CT_bo#Origin_Terminal_Actual_Date]]
+
-
:* Logic:  This date CANNOT be set until the previous three dates have been set
+
-
:** Origin Terminal ATD date cannot be set if Export Pick up actual date is empty.
+
-
:** Origin Terminal ATD date cannot be before Export pick up actual date set
+
-
:** Origin Terminal ATD date can be the same date or after Export pick up date
+
 +
Port of trans-ship actual date
 +
*Only if check box is checked indicating this record has a trans-shipment point
-
'''Port of loading ATD'''
+
Port of discharge actual date
-
:* Mapping [[CT_bo#Port_Of_Loading_Actual_Date]]
+
-
:* Logic:  This date CANNOT be set until the previous four dates have been set
+
-
:** If Origin Terminal ATD is set to '''Yes''' , then apply logic below:
+
-
:*** Port of loading ATD date cannot be set if Origin terminal ATD date is empty
+
-
:*** Port of loading ATD date cannot be before Origin terminal ATD date set
+
-
:*** Port of loading ATD date can be the same date or after the Origin terminal ATD date set
+
-
:** Else Origin Terminal ATD date will be default the same as Port of loading ATD date
+
 +
Destination terminal actual date
 +
*Only if radio button is set to yes indicating the destination terminal is different than the port of discharge
-
'''Port of Transship ATA''' (if applicable)
+
Actual delivery date or delivery comment
-
:* Mapping [[CT_bo#Trans_Shipment_Actual_Date]]
+
-
:* Logic:  This date CANNOT be set until the previous five dates have been set
+
-
:** If the Port of Transship ATA date is set, apply logic below:
+
-
:*** Port of Transship ATA date cannot be set if Port of loading ATD date is empty
+
-
:*** Port of Transship ATA date set cannot be before Port of loading ATD date set
+
-
:*** Port of Transship ATA date can be the same date or after as the Port of loading ATD date set
+
-
:** Else do nothing
+
 +
===LCL shipments===
 +
Notification date
-
'''Port of discharge ATA'''
+
Actual export pickup Date
-
:* Mapping [[CT_bo#Port_Of_Discharge_Actual_Date]]
+
*Only if the estimated export pickup date is entered
-
:* Logic:  This date CANNOT be set until the previous six dates have been set
+
-
:** Port of discharge ATA date cannot be set if Port of transship ATD OR Port of loading ATD is empty
+
-
:** Port of discharge ATA date cannot be set before Port of transship OR Port of loading date set
+
-
:** Port of discharge ATA date can be the same date or after Port of transship OR Port of loading date set
+
 +
Origin terminal actual date
 +
*Only if radio button is set to yes indicating it would differ from Port of Loading actual date
-
'''Destination Terminal ATA'''
+
Port of loading actual date
-
:* Mapping [[CT_bo#Destination_Terminal_Actual_Date]]
+
-
:* Logic:  This date CANNOT be set until the previous seven dates have been set
+
-
:** If Destination Terminal ATA is set to '''Yes''', then apply logic below:
+
-
:*** Destination Terminal ATA date cannot be set if Port of discharge ATA date is empty
+
-
:*** Destination Terminal ATA date cannot be set before Port of discharge ATA date set
+
-
:*** Destination Terminal ATA date can be set the same date or after Port of discharge ATA date set
+
-
:** Else Destination Terminal ATA date will be default the same as Port of discharge ATA date
+
 +
Port of trans-ship actual date
 +
*Only if check box is checked indicating this record has a trans-shipment point
-
'''Delivery date'''
+
Port of discharge actual date
-
:* Mapping [[CT_bo#Actual_Delivery_Date]]
+
-
:* Logic:  This date CANNOT be set until all of the previous dates have been set
+
-
:** Delivery date cannot be set if Destination Terminal ATA date is empty
+
-
:** Delivery date cannot be set before Destination Terminal ATA date set
+
-
:** Delivery date can be the same date or after Destination Terminal ATA date set
+
-
:** Note: This date is default to the same as Destination Terminal ATA date if Enter Delivery Comment is '''checked'''
+
-
=== MOT:Ocean FCL ===
+
Destination terminal actual arrival date
 +
*Only if radio button is set to yes indicating the destination terminal is different than the port of discharge
-
'''Notification date'''
+
Actual delivery date or delivery comment
-
:* Mapping [[CT_bo#Notification_Date]]
+
-
:* Logic: This date MUST be set before any other dates
+
-
'''Authorized on'''
+
===Air===
-
:* Mapping [[CT_bo#Authorized_On]]
+
Notification date
-
:* Logic: This date CANNOT be set until the previous date has been set
+
-
'''Actual collection'''
+
Actual export pickup date
-
:* Mapping [[Container#Actual_Export_Pick_Up_Date]]
+
*Only if the estimated export pickup date is entered
-
:* Logic: This date CANNOT be set until the previous two dates have been set
+
-
'''Origin terminal ATD'''
+
Airport of departure actual time of departure
-
:* Mapping [[CT#Origin_Terminal_Actual_Date]]
+
-
:* Logic: This date CANNOT be set until the previous three dates have been set
+
-
'''Port of loading ATD'''
+
Trans-shipment airport actual time of departure
-
:* Mapping [[CT#Port_Of_Loading_Actual_Date]]
+
*Only if check box is checked indicating this record has a trans-shipment point
-
:* Logic: This date CANNOT be set until the previous four dates have been set
+
-
'''Port of transship (if applicable) ATA'''
+
Airport of destination actual time of arrival
-
:* Mapping [[CT#Trans_Shipment_Actual_Date]]
+
-
:* Logic: This date CANNOT be set until the previous five dates have been set
+
-
'''Port of discharge ATA'''
+
Actual delivery date or delivery comment
-
:* Mapping [[CT#Port_Of_Discharge_Actual_Date]]
+
-
:* Logic: This date CANNOT be set until the previous six dates have been set
+
-
'''Destination terminal ATA'''
+
===Estimated dates===
-
:* Mapping [[CT#Destination_Terminal_Actual_Date]]
+
-
:* Logic: This date CANNOT be set until the previous seven dates have been set
+
-
'''Actual delivery'''
+
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.
-
:* Mapping [[Container#Actual_Delivery_Date]]
+
-
:* Logic: This date CANNOT be set until all of the previous dates have been set
+
-
=== MOT:Air ===
+
Validations of estimated dates are no longer required.  Estimated dates should be for information purposes only.
-
'''Notification date'''
+
-
:* Mapping [[CT#Notification_Date]]
+
-
:* Logic: This date MUST be set before any other dates
+
-
'''Authorized on'''
+
• 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.
-
:* Mapping [[CT#Authorized_On]]
+
-
:* Logic: This date CANNOT be set until the previous dates have been set
+
-
'''Actual Export Pick-Up Date'''
 
-
:* Mapping [[CT#Actual_Export_Pick_Up_Date]]
 
-
:* Logic: This date CANNOT be set until the previous two dates have been set
 
-
'''Airport of departure actual time of departure'''
+
</div>
-
:* Mapping [[CT#Airport_Of_Departure]]
+
-
:* Logic: This date CANNOT be set until the previous three dates have been set
+
-
 
+
-
'''Trans-shipment Airport actual time of arrival'''
+
-
:* Mapping [[CT#Trans_Shipment_Actual_Date]]
+
-
:* Logic: This date CANNOT be set until the previous four dates have been set
+
-
 
+
-
'''Airport of destination actual time of arrival'''
+
-
:* Mapping [[CT#Airport_Of_Destination_Actual_Date]]
+
-
:* Logic: This date CANNOT be set until the previous five dates have been set
+
-
 
+
-
'''Actual delivery Date or delivery comment'''
+
-
:* Mapping [[CT#Actual_Delivery_Date]]
+
-
:* Logic: This date CANNOT be set until all of the previous dates have been set
+

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