2555 rfsa

From UG

(Difference between revisions)
Jump to: navigation, search
(Reusing a MAWB)
(Warning Message)
Line 18: Line 18:
====Warning Message====
====Warning Message====
-
To avoid duplicate MAWB's from being used, the system should generate an error or warning message advising that this MAWB has already been used.  It should not stop the operator from using it because they should be able to reuse a MAWB from a shipment that may have previously been cancelled.  
+
To avoid duplicate MAWB's from being used, the system should generate an error or warning message advising that this MAWB has already been used.  It should not stop the operator from using it, in case it is being reused intentionally
 +
* This is in case they would like to reuse a MAWB from a shipment that may have previously been cancelled.
==Business Requirements==
==Business Requirements==

Revision as of 20:08, 17 December 2010

Contents

Info

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


Business information

Operators are given a "block" of master airway bill numbers from each airline. Each master airway bill number can only be used once. We have two cases in which the master airway bill number should be changed.

Human error

If the operator makes a type-o when entering the master airway bill number, they will need to be able to correct this.

Re-using a MAWB

The block of numbers assigned to us by the airline is kept in a book. Operators manually select a MAWB from this list and type it into CT. In rare occasions, two operators have selected the same MAWB from the list. When this happens one operator must change the MAWB they have used.

Warning Message

To avoid duplicate MAWB's from being used, the system should generate an error or warning message advising that this MAWB has already been used. It should not stop the operator from using it, in case it is being reused intentionally

  • This is in case they would like to reuse a MAWB from a shipment that may have previously been cancelled.

Business Requirements

Descartes does not have currently have a provision for correcting a MAWB. In the event a MAWB is changed.

The system should resend the MAWB as a new shipment. The system should recognize the new or corrected MAWB as the only MAWB and apply any incoming/outgoing message. The system should not remember the incorrect or previous MAWB. Any incoming messages for an unrecognized MAWB should not generate a system update.

  • The incoming messages for an unrecognized MAWB should be kept or stored in an unrelated area for review.



Personal tools