Task #19324
Updated by Redmine Admin 13 days ago
The system shall allow users to create a Master Air Waybill (MAWB) file linked to a Flight Schedule, and then select, link, or create multiple House AWBs (HAWBs) from the House AWB Repository, including support for Split Shipments and Partial Shipments. **1️ Flight & Master Creation (MAWB)** **Create MAWB from Flight Schedule** Create a Master File (MAWB) by selecting an existing flight schedule and manage the House AWBs under the same flight under one parent record. **Acceptance Criteria** * User can search and select a flight from the Flight Schedule module * Selected flight auto-populates: * Flight No. * Flight Date * Origin & Destination * ETD & ETA * Airline * GHA * System generates a unique File Ref No. (e.g. MACCS25IMP000123) at this time or on Save (open to development team) * File Ref status defaults to “In Progress” **Validations** * Only active flights selectable * Flight change after HAWB linking requires confirmation **Link Existing MAWBs from FWB functionality** User should be able to search and add an existing MAWB from the FWB functionality - https://gitlab.maccs.mu/rnd/ffa/documentation/-/issues/990 Select MAWB from list of MAWBs **Fields to display for selected MAWB** * MAWB No. * Carrier / Airline * Consignee * Agent * Importer / Forwarder / Shipper * Freight Terms (Prepaid / Collect) * Total Weight, Volume, Pieces * Status lifecycle: * In Progress → Completed → Closed * Closed files are read-only **Rules** * A File Ref cannot be Closed if any linked HAWB is not “DO Issued” **Acceptance Criteria** * When setting the status to “Completed”, total pieces and weight of the master should tally against the all HAWBs pieces and weight. **Document Management at MAWB Level** The system shall allow uploading and managing MAWB-level documents. All master-level documents should be centrally available. **Documents** * Notice of Arrival * Airline Delivery Order * FWB * Airline Invoices * Other PDFs / Scan copy Document should be stored with: · Document type · Uploaded by · Timestamp, etc. **Acceptance Criteria** * User clicks Upload Document * Selects document type: Airline NOA / DO / Other * Uploads PDF or scan * Multiple files allowed * View / Download permissions controlled by role **2. Add & Manage House AWBs (HAWB Repository Integration)** **Link Existing HAWBs from repository to MAWB** User should be able to search and link existing HAWBs from the House AWB Repository (https://gitlab.maccs.mu/rnd/ffa/documentation/-/issues/928 ). **HAWB Status Lifecycle & Rules** Each House Air Waybill (HAWB) shall follow a defined lifecycle to ensure proper operational control and alignment with the MAWB status. **HAWB Status Lifecycle** * **In Progress** – HAWB created but not yet manifested * **Manifested** – Included in MAWB manifest / FHL generated * **Linked** – HAWB has been used in a File Ref * **DO Issued** – Delivery Order issued * **Closed** – HAWB completed and locked * **DO Issued** – Delivery Order issued **Business Rules** * A HAWB may only be linked to a MAWB when its status is **In Progress** or **Manifested**. * A HAWB marked as **“DO Issued**” or **Closed** shall not be unlinked. * A File Ref cannot be set to **Closed** if at least one linked HAWB is not in **“DO Issued**” status, unless override permission is granted. **Acceptance Criteria** * Search by: * MAWB No. * HAWB No. * Consignee * Shipper * Status * Date Range * Multi-select (bulk linking) enabled * Once linked: * HAWB status updates to “Linked” * HAWBs marked as part shipment should be available in the list if all pieces have not been received. **Import HAWBs** Supported import formats: * FHL IATA CIMP/CXML message **Part Shipment Handling** The user should be able to manage Partial shipments (MAWB totals include only legs linked to that MAWB) to avoid discrepancies **Part Shipment** * One HAWB partially arrived * Remaining balance tracked * Delivered quantity ≠ Manifested quantity **4. Retrieve File Reference (Search & Access)** The user should be able to retrieve existing File Reference records using flexible search criteria. A dedicated **Retrieve File Reference** screen shall be available under: * Air Export → File Reference * Air Import → File Reference **Search Criteria** Users may search using one or more of the following: **Identifiers** * File Reference * MAWB Number (prefix + serial) * HAWB Number * Airline / Carrier Code **Shipment** * Origin / Destination airport * Flight number * Flight date (from / to) **Parties** * Shipper * Consignee * Agent **Operational** * File Status (In Progress / Completed / Closed) * Created date/Last Update date **Acceptance Criteria** * At least one criterion required * Partial matches supported * Results pageable & sortable * Tenant-based data isolation enforced **Results Grid Columns** * File Reference * MAWB Number * Airline * Origin → Destination * Pieces / Weight * File Status * Last Updated * Action buttons (View/Edit, Downloads, Clone) – Refer to action buttons from Ocean File Reference **Nested Grid (HAWB Details)** * HAWB Number * Shipper/Consignee * Origin → Destination * Pieces / Weight * File Status * Last Updated * Action buttons (View/Edit, Downloads, Clone) – Refer to action buttons from Ocean File Reference **Delivery Order & Closure (to be developed since currently it is not present in CCS)** A user should be able to issue House DO. **Rules** * House Delivery Orders (HAWB DO) are the operational documents used for cargo release. * Issuing a HAWB DO automatically updates the corresponding HAWB status to DO Issued. **Acceptance Criteria** * HBL Status updates to “DO Issued” * File becomes read-only No rules to check for full invoice payment for the time being unless we get new requirements from clients **Generate House DO** * User clicks Generate HAWB DO * System validates: * HAWB status is complete **If valid** * DO generated * DO timestamp recorded * DO locked **3️ FWB & FHL Messaging (IATA Messaging)** **Generate FWB - Export** The system should allow to generate the FWB upon MAWB creation as per IATA – CIMP & CXML format. **Acceptance Criteria** * Mandatory IATA fields validated * Block sending on errors * Generated in Cargo-IMP / Cargo-XML format * Editable only before transmission **Generate FHL per HAWB - Export** The system should allow to generate FHL messages per linked HAWB **Acceptance Criteria** * One FHL per HAWB * Validates consignee, pieces, weight, HS Codes * Cannot send FHL if HAWB not “Completed” **Transmit & Track Messages** The user should be able to send and track FWB/FHL messages, monitor airline acceptance. **Message Status** * In Progress * Sent * Acknowledged (FMA) * Rejected (FNA) **Acceptance Criteria** * Transmission via SMTP / SFTP / API * Re-send option available * Acknowledgment stored & linked to file