2555 rfd

From UG

Current revision as of 01:16, 3 January 2011

[edit] Info

• mantis: 0002555: ([Air Status EDI] (Use case) Operator attempted to change MAWB

[edit] Requirements and Solutions

If operator attempt to change MAWB then system should perform the next:

1) validate the entered value to avoid duplicate MAWB.

• If duplicate is found then the system should generate a warning message that this MAWB has already been used and specify the number of CT where it is used.

• Showing of warning message should not stop using of MAWB but only draw attention.

• All shipments under the same master record will have the same airway bill.
• MAWB can be reused from a shipment that may have previously been cancelled.

2) send outgoing message with new MAWB to Descartes.

• The system should recognize the new (or corrected) MAWB as the only MAWB and apply any incoming message.
• The incoming messages for an unrecognized MAWB should be kept or stored in an unrelated area for review.

[edit] Concept of cancelled shipment

• Cancelled shipment has filled actual delivery date and may have an indicating comment.
  • NOTE: If a shipment is already marked as delivered it should not allow an update of an arrival or departure (which would be the updates sent by Descartes) because the date validation would be out of order.
• MAWB cannot be removed from the cancelled shipment because we may have purchase invoices associated with the CT and purchase invoices will reflect MAWB as a reference number.

[edit] Possible suggestion

• Add a place to indicate the shipment has been cancelled.
  • If we do this, we should have a warning message advising the operator they are going to cancel this shipment: "Are you sure you want to do this?"

[edit] Architect Review

[edit] Implementation Notes

[edit] QA Plan

[edit] History