Constraints on Estimated Dates

From UG

Contents 1 Info 1.1 Parent Mantis 1.2 Scope of this wiki 2 SOW 1 2.1 Specific sequence of validating dates 2.1.1 FCL shipments 2.1.2 LCL shipments 2.1.3 Air shipments 2.1.4 Trucking shipments

Info

Parent Mantis

• mantis 0100

Scope of this wiki

Add constraints and validations for estimated dates. Not allowing updates out of specified chronological order and for them to work in conjunction with the actual date validations that are already in place.

SOW 1

Mantis: 3185 (CT2 Misc) Add Estimated Date Validation

Core requirements:

• Task type: Tweak.
• Where: Estimated CT Dates.
• What: System should validate the chronological order in the specific sequence for all estimated 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: Estimated arrival date cannot be confirmed until Estimated 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 not subject to Actual Date validations.

Specific sequence of validating dates

• Specific sequence of validating dates is conditioned on the set of events for the shipment.
• Each event corresponds to the date of shipment depending on the mode of transport:

FCL shipments

• estimated collection date. Only required to be filled in if an export trucker is filled in.
• Origin terminal estimated date. Only required if radio button is set to yes indicating the origin terminal is different from the port of loading.
• Port of loading estimated date.
• Port of trans-ship estimated date. Only required if check box is checked indicating this record has a trans-shipment point.
• Port of discharge estimated date.
• Destination terminal estimated date. Only required if radio button is set to yes indicating the destination terminal is different than the port of discharge.
• Estimated delivery date.

LCL shipments

• Estimated export pickup date. Only required if an export pickup trucker is filled in
• Origin terminal estimated date. Only required if radio button is set to yes indicating it would differ from Port of Loading estimated date.
• Port of loading estimated date.
• Port of trans-ship actual date. Only required if check box is checked indicating this record has a trans-shipment point.
• Port of discharge estimated date.
• Destination terminal estimated date. Only required if radio button is set to yes indicating the destination terminal is different than the port of discharge.
• Estimated delivery date.

Air shipments

• Estimated export pickup date. Only required to be filled in if an export trucker is filled in.
• Airport of departure estimated time of departure.
• Trans-shipment airport estimated time of departure. Only required if check box is checked indicating this record has a trans-shipment point.
• Airport of destination estimated time of arrival.
• Actual delivery date.

Trucking shipments

NOTE: Validations of Trucking CT dates will be specified later in separate mantis.