2555 rfsa
From UG
(Created page with '<div style="background-color:lightSteelBlue"> </div>') |
|||
| (16 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:RFSA]] | ||
| + | |||
<div style="background-color:lightSteelBlue"> | <div style="background-color:lightSteelBlue"> | ||
| + | |||
| + | ==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 and the CT number it is used in. 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. | ||
| + | |||
| + | ==Cancelled Shipments== | ||
| + | |||
| + | When an operator cancels a shipment they do this by filling in the actual delivery date. | ||
| + | |||
| + | They also may indicate in the comment section that the shipment is cancelled, but this is not always done. | ||
| + | |||
| + | MAWB cannot be removed from the CT even when it is cancelled because we may have purchase invoices associated with the CT and purchase invoices will reflect MAWB as a reference number. | ||
| + | |||
| + | |||
| + | 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. | ||
| + | |||
| + | |||
| + | ===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. | ||
| + | |||
| + | |||
| + | ==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. | ||
| + | |||
| + | |||
| + | |||
| + | |||
</div> | </div> | ||
Current revision as of 20:15, 30 December 2010
Contents |
[edit] Info
Mantis:0002555: [Air Status EDI] (Use case) Operator attempted to change MAWB
[edit] 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.
[edit] 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.
[edit] 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.
[edit] 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 and the CT number it is used in. 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.
[edit] Cancelled Shipments
When an operator cancels a shipment they do this by filling in the actual delivery date.
They also may indicate in the comment section that the shipment is cancelled, but this is not always done.
MAWB cannot be removed from the CT even when it is cancelled because we may have purchase invoices associated with the CT and purchase invoices will reflect MAWB as a reference number.
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.
[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] 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.
