Project

General

Profile

Actions

Task #19844

open

Task #19866: Sprint Planning for 12/05/2026- 26/05/2026

Create Air Clearing File from Existing HAWB

Added by Redmine Admin 4 months ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
05/04/2026
Due date:
05/04/2026 (about 4 months late)
% Done:

0%

Estimated time:
0:00 h
GitLab ID:
4367
GitLab Milestone:
GitLab Ticket Number:
1497
GitLab Time Logged:
0
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 12/05/2026- 26/05/2026

Description

Description

A HAWB (House Air Waybill) represents a shipment for one customer.

  • It already contains:
    • Shipment details
    • Shipper / Consignee
    • Airports
    • Weight / pieces
  • When creating a clearing file from an existing HAWB - "Use Existing HAWB" button click:
    The system must reuse this data automatically

User Flow

User clicks "Create Air Clearing File"

→ Clicks "Use Existing HAWB"

→ HAWB popup opens

→ User searches & selects HAWB

→ System loads HAWB data into Clearing Screen

→ User completes missing info

→ User clicks Save

→ Clearing File is created

UI Components

1. Button

Button Label: Use Existing HAWB

2. HAWB Selection Popup

Fields:

Field Type
HAWB Reference Text
Date Range Mandatory
Company / Individual Display
Cargo Type Import / Export
Origin Airport
Destination Airport
Status Draft / Confirmed
Created Date Date

Actions:

  • Search
  • Reset
  • Select (row click or button)

Functional Requirements

1 – Open HAWB Popup

When user clicks Use Existing HAWB:

  • System must open a popup
  • Popup displays list of HAWBs

2 – Search HAWB

User must be able to search using:

  • HAWB Reference
  • Date Range (mandatory)
  • Company / Individual
  • Origin / Destination
  • Status

3 – Select HAWB

When user selects a HAWB:

  • Popup closes
  • System loads data into Clearing screen

4 – Data Mapping

System must auto-populate fields as follows:

A. Shipment Details Mapping

Clearing Field Source (HAWB)
HAWB Reference HAWB.Ref
Cargo Type HAWB.Import/Export
Origin Airport HAWB.Origin
Destination Airport HAWB.Destination
Incoterm HAWB.Incoterm

B. Flight Information Mapping

Clearing Field Source
Airline HAWB.Airline
Flight Number HAWB.Flight No
ETD HAWB.ETD
ETA HAWB.ETA
Transit Airport HAWB.Transit

C. Party Information Mapping

Clearing Field Source
Shipper HAWB.Shipper
Consignee HAWB.Consignee
Notify Party HAWB.Notify
Delivery Agent HAWB.Agent

D. Cargo Information (if available—Display only)

Field Source
Weight HAWB.Weight
Pieces HAWB.Pieces
Description HAWB.Description

5 – Editable vs Locked Fields

Field Type Behavior
Core shipment data Read-only OR editable based on config
Clearing-specific fields Editable
BOE Empty (user must add)

6 – Prevent Duplicate Clearing File

System must validate:

  • If a clearing file already exists for the same HAWB

Behavior:

Show warning:

A clearing file already exists for this HAWB. Do you want to continue?

7 – Save Clearing File

When user clicks Save:

System must:

  1. Generate Clearing Reference
  2. Save all data
  3. Set status = DRAFT
  4. Link clearing file to HAWB

8 – Activity Log Integration

On creation, system must log:

<username> created Clearing File <CLEARING_REF> from HAWB <HAWB_REF>

9 – Mandatory Fields Before Save with minimum Info for status Draft

User must fill (if missing):

  • Origin Airport
  • Destination Airport
  • Cargo Type

Validation Rules

Field Rule
HAWB Reference Mandatory after selection
Date Range Mandatory in popup
Cargo Type Must be Import or Export
Airports Must be valid IATA codes

Acceptance Criteria

1 – Open HAWB Popup

Given I am on Create Clearing File screen,
When I click "Use Existing HAWB",
Then the HAWB selection popup should open.

2 – Search HAWB

Given I enter search criteria,
When I click Search,
Then matching HAWBs should be displayed.

3 – Select HAWB

Given I select a HAWB,
When I confirm selection,
Then the popup should close and data should populate.

4 – Auto Populate Data

Given a HAWB is selected,
When data loads,
Then shipment, flight, and party details should be populated.

5 – Save Clearing File

Given all minimum fields info are completed,
When I click Save,
Then a clearing file should be created with status DRAFT.

6 – Duplicate Handling

Given a clearing file already exists for the HAWB,
When I attempt to create another,
Then the system should show a warning.

7 – Activity Log Entry

Given a clearing file is created,
When save is successful,
Then the system should log the creation action.


GitLab Sync Log

[]

Actions #1

Updated by Redmine Admin 4 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin 4 months ago

  • Parent task set to #19866
  • gitlab project trace set to Sprint Planning for 12/05/2026- 26/05/2026
Actions

Also available in: Atom PDF