2555 rfd
From UG
(Difference between revisions)
(wiki created) |
(→Requirements and Solutions: completed) |
||
| Line 6: | Line 6: | ||
== Requirements and Solutions == | == Requirements and Solutions == | ||
| + | |||
| + | If operator attempt to change MAWB then system should perform: | ||
| + | : 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. | ||
| + | :* But MAWB can reuse 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. | ||
== Architect Review == | == Architect Review == | ||
Revision as of 14:27, 21 December 2010
Contents |
Info
- mantis: 0002555: ([Air Status EDI] (Use case) Operator attempted to change MAWB
Requirements and Solutions
If operator attempt to change MAWB then system should perform:
- 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.
- But MAWB can reuse 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.
