2413 rfd
From UG
(Difference between revisions)
m (→Requirements and Solutions) |
(→Details: renamed "Details" section to "Specific sequence of validating dates") |
||
| Line 18: | Line 18: | ||
** NOTE: Validations of estimated dates are no longer required. | ** NOTE: Validations of estimated dates are no longer required. | ||
| - | === | + | === Specific sequence of validating dates === |
* Specific sequence of validating dates is conditioned on the set of events the shipment. | * Specific sequence of validating dates is conditioned on the set of events the shipment. | ||
* Each event corresponds to the date of shipment depending on the mode of transport: | * Each event corresponds to the date of shipment depending on the mode of transport: | ||
Current revision as of 10:42, 1 February 2011
Contents |
[edit] Info
- mantis 0002413: [Ops Misc Dates] Date Validation
[edit] Requirements and Solutions
- Task type: Tweak.
- Where: Actual CT Dates.
- What: System should validate the chronological order in the specific sequence for all actual dates.
- The system must allow each of the dates to be the same as the previous date or more.
- 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.
- Generalized example of error message: <Next date> cannot be confirmed until <previous date> has been confirmed in <CT #XXXXXX>.
- Specific example of error message: Actual arrival date cannot be confirmed until actual departure date has been confirmed.
- CT # should be indicated in the error message:
- 1) If CT is a part of Group and date field what out of order is selected for "Group save".
- 2) If CT is a part of Master.
- NOTE: Validations of estimated dates are no longer required.
[edit] Specific sequence of validating dates
- Specific sequence of validating dates is conditioned on the set of events the shipment.
- Each event corresponds to the date of shipment depending on the mode of transport:
[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 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 shipments
- 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] Trucking shipments
NOTE: Validations of Trucking CT dates will be specified later in separate mantis.
