The objective of this ticket is to review the existing Air Export HAWB screen and apply the required functional changes based on the behaviours identified from the Air Import House Repository and the requested Air Export rules.

The existing screen should continue to be used. Only the required changes listed below should be catered for.

Scope Clarification¶

In Scope¶

The existing Air Export HAWB screen should be enhanced for the following areas:

Area	Required Action
Basic details	Apply Export-specific defaulting and validation
Routing	Apply Air Export origin and destination logic
Use Existing HAWB	Retrieve Import HAWBs marked as Landing & Shipping
Link MAWB	Show and link only Air Export MAWBs
Cost and Sales	Filter charges by Air Export cargo type / shipment channel
Ready for FHL	Validate Air Export HAWB correctly
Regression	Ensure Air Import is not impacted

Note:
The Ready for FHL indicator may be set or validated from the Air Export HAWB Repository. However, the actual FHL transmission will be performed from the File Reference functionality, not directly from the HAWB Repository screen.

This ticket covers only the following enhancements:

1. Apply Air Export-specific defaulting and validation in Basic Details.
2. Apply Air Export origin and destination logic in Routing.
3. Ensure Air Export HAWB can link only to Air Export MAWB.
4. Filter Cost and Sales charge selection by Air Export cargo type / shipment channel.
5. Validate and set Ready for FHL for Air Export HAWB.
6. Ensure the actual FHL message is sent from File Reference, not from HAWB Repository.
7. Ensure the existing Use Existing HAWB function retrieves eligible Import HAWBs.
8. Perform regression testing to ensure Air Import HAWB is not impacted.

Functional Requirements¶

1 — Basic Details: Apply Air Export Defaulting and Validation¶

The existing Basic Details section of the Air Export HAWB screen must apply export-specific behaviour.

When the user creates or retrieves an Air Export HAWB, the system must ensure that the record is treated as Air Export throughout the screen.

The following behaviour is required:

Field / Area	Required Behaviour
Cargo Type / Shipment Channel	Must be Air Export / Export
HAWB Type	Must be Export
House Air Waybill	Must be mandatory as per existing HAWB rules
Nature of Goods	Must be mandatory as per existing rules
Number of Pieces	Must be numeric and greater than zero
Gross Weight	Must be numeric and greater than zero
Chargeable Weight	Must be numeric and greater than zero
Weight Code	Must be required as per existing Air rules
Origin / Destination	Must follow Air Export routing logic
Public / Private	Existing behaviour should remain unchanged

If any existing Air Import-specific defaulting is being applied incorrectly to Air Export, it must be corrected.

2 — Routing: Apply Air Export Origin and Destination Logic¶

The Air Export HAWB routing must follow export logic.

For Air Export:

Field	Required Export Logic
Origin / Airport of Departure	Local export departure airport, normally MRU, that is, configured local airport in settings.
Destination / Airport of Destination	Overseas final destination airport
Airport Codes	Must follow existing IATA airport validation
Routing compatibility	Must be compatible with linked Air Export MAWB where applicable

The system must ensure that origin and destination are not treated as Air Import routing.

Example:

Air Import Logic	Air Export Logic
Origin is usually foreign airport	Origin is usually MRU / local departure airport
Destination is usually Mauritius	Destination is overseas destination

3 — Link MAWB: Show and Link Only Air Export MAWBs¶

The existing Link MAWB functionality must be reviewed for the Air Export HAWB screen.

When the current HAWB is Air Export, the Link MAWB popup must display only Air Export MAWBs.

The following must be ensured:

Area	Required Behaviour
Link MAWB popup	Reuse existing popup
MAWB list	Display only Air Export MAWBs
Air Import MAWBs	Must not be displayed
Ocean records	Must not be displayed
Link validation	Export HAWB must link only to Export MAWB
Route validation	Validate route compatibility where applicable
Link Status	Update correctly after successful link

The system must prevent an Air Export HAWB from being linked to an Air Import MAWB.

4 — Cost and Sales: Filter Charges by Air Export Cargo Type / Shipment Channel¶

In the Air Export HAWB Repository → Cost and Sales section, users can add charges through the Add Charges / Add Multiple Charges popup.

The available charges must be filtered based on the current HAWB’s Air Cargo Type / Shipment Channel.

For Air Export HAWB, the popup must show only Air Export charges.

The rule must apply to both:

Section	Popup
Cost Details	Add Charges / Add Multiple Charges
Sales Details	Add Charges / Add Multiple Charges

The system must not display:

Charges Not to Display
Air Import charges when the HAWB is Air Export
Ocean Import charges
Ocean Export charges
Unrelated charges

The search function inside the popup must also respect the Air Export charge filter.

For example, if the current HAWB is Air Export and the user searches for “docu”, the system must return only documentation-related charges configured for Air Export.

Existing charges already saved in the Cost and Sales grids must remain unchanged. This change applies only to new charge selection from the popup.

5 — Ready for FHL: Validate Air Export HAWB Correctly¶

The Air Export HAWB Repository must be able to validate whether the HAWB is Ready for FHL.

The Ready for FHL indicator may be displayed or set from the HAWB Repository screen.

However, the actual FHL transmission must be done from File Reference, not from the HAWB Repository.

The Ready for FHL validation should check the required Air Export HAWB information, including:

Area	Validation
HAWB Header	HAWB number, pieces, weight, nature of goods
Parties	Shipper and consignee, where required by existing rules
Routing	Origin and destination airports
Cargo	Commodity information, where required
Charges / CVD	Required values where applicable
MAWB Link	Linked Air Export MAWB, if required
Codes	Valid airport, country, currency, and handling codes where applicable

The validation must apply Air Export rules and must not incorrectly apply Air Import-only rules.

6 - Use Existing HAWB: Retrieve Import HAWBs Marked as Landing & Shipping¶

The Use Existing HAWB / Use Existing HAWB Landing & Shipping popup already exists in the Air Export HAWB Repository.

This popup must retrieve HAWBs from the Air Import HAWB Repository that have been marked as Landing & Shipping.

This functionality is required because some HAWBs created at import level may need to be reused for export processing.

Required Behaviour¶

Area	Required Behaviour
Popup	Reuse existing popup
Source of records	Air Import HAWB Repository
Eligibility	Only Import HAWBs marked as Landing & Shipping
Current module	Air Export HAWB Repository
Purpose	Allow eligible Import HAWB to be reused in the Export HAWB process
Removal from available list	Remove only after the Export HAWB is saved successfully
Wrong selection	User must be able to clear/unlink before saving
After saved	User must be able to unlink based on permission/status rules
Traceability	System should retain reference to original Import HAWB where applicable

Search / Filter Options¶

The popup should allow the user to search eligible HAWBs using:

Filter	Description
HAWB Number	Search by full or partial HAWB number
Origin	Search by origin airport
Destination	Search by destination airport
Date Range	Search by HAWB date / created date as per existing logic

The popup must not display all Import HAWBs. It should display only Import HAWBs where Landing & Shipping has been marked and which are not already actively used by another saved Air Export HAWB.

Selection and Save Behaviour¶

When the user selects an eligible HAWB from the popup:

1. The selected Import HAWB details should be copied/reused in the Air Export HAWB screen as per existing behaviour.
2. The selected HAWB should be temporarily linked to the current Export HAWB draft.
3. The selected HAWB should not be removed from the available list immediately upon selection.
4. The selected HAWB should be removed from the available list only after the Air Export HAWB is saved successfully.
5. If the user closes the screen, cancels the action, or does not save the Export HAWB, the selected Import HAWB should remain available in the popup.

Wrong Selection / Clear Before Save¶

If the user selects the wrong HAWB before saving the Air Export HAWB:

1. The user should be able to clear or remove the selected HAWB.
2. Once cleared, the copied/reused details should be removed or reset based on existing screen behaviour.
3. The Import HAWB should remain available in the Use Existing HAWB popup because it has not yet been saved/used.

Unlink After Save¶

If the Air Export HAWB has already been saved with a selected Landing & Shipping Import HAWB:

1. The user should be able to unlink the selected Import HAWB if the Export HAWB is still in an editable status.
2. Once unlinked, the source Import HAWB should become available again in the Use Existing HAWB popup.
3. The unlink action should be restricted if the Export HAWB is already Confirmed, Approved, Finalized, linked to MAWB, or used in downstream processes, based on existing permission/status rules.
4. The unlink action must be logged for audit purposes.

Duplicate Usage Control¶

An eligible Import HAWB marked as Landing & Shipping should not be used in multiple active Air Export HAWBs at the same time.

The system should prevent duplicate active usage.

Example:

Scenario	Expected Behaviour
Import HAWB marked as Landing & Shipping and not yet used	Display in popup
Import HAWB selected but Export HAWB not saved	Still available if user cancels/closes without saving
Import HAWB selected and Export HAWB saved	Remove from available popup list
Export HAWB unlinked while still editable	Import HAWB becomes available again
Export HAWB finalized / downstream process started	Unlink should be restricted

7.- Regression: Ensure Air Import Is Not Impacted¶

The changes made for Air Export must not break or change the existing Air Import HAWB behaviour.

The following Air Import behaviour must continue to work as before:

Area	Expected Regression Behaviour
Air Import Basic Details	Existing defaulting and validation remain unchanged
Air Import Routing	Existing Import origin/destination logic remains unchanged
Air Import Link MAWB	Air Import HAWB links only to Air Import MAWB
Air Import Cost and Sales	Air Import HAWB displays only Air Import charges

Acceptance Criteria¶

1 — Air Export Basic Details Defaulting¶

Given the user creates or opens an Air Export HAWB,
when the screen is displayed,
then the HAWB must be treated as Air Export with the correct Cargo Type / Shipment Channel.

2 — Air Export Mandatory Field Validation¶

Given the user saves, confirms, or validates an Air Export HAWB,
when mandatory fields such as HAWB number, pieces, gross weight, chargeable weight, weight code, or nature of goods are missing or invalid,
then the system must display the appropriate validation message.

3 — Numeric Field Validation¶

Given the user enters pieces, gross weight, or chargeable weight,
when the value is zero, negative, or invalid,
then the system must prevent the action based on the existing IATA validation rules.

4 — Air Export Routing Logic¶

Given the HAWB is Air Export,
when routing details are entered,
then the origin / airport of departure must represent the local export departure airport, normally MRU or configured local airport, and the destination must represent the overseas final destination.

5 — Airport Code Validation¶

Given the user enters or selects an airport,
when the HAWB is saved or validated,
then the system must accept only valid airport codes based on the existing IATA airport validation rules.

6 — Link MAWB Popup Shows Only Air Export MAWBs¶

Given the current HAWB is Air Export,
when the user opens the Link MAWB popup,
then only Air Export MAWBs must be displayed.

7 — Air Import MAWB Not Displayed for Air Export HAWB¶

Given the current HAWB is Air Export,
when the Link MAWB popup is displayed,
then Air Import MAWBs must not be displayed.

8 — Successful Export MAWB Link¶

Given the user selects a valid Air Export MAWB,
when the link is confirmed,
then the Air Export HAWB must be linked to the selected Air Export MAWB and the Link Status must be updated correctly.

9 — Route Compatibility During MAWB Link¶

Given the selected Air Export MAWB route is not compatible with the HAWB route,
when the user tries to link,
then the system must show a validation warning based on the existing business rules.

10 — Air Export Cost Charges Filter¶

Given the current HAWB is Air Export,
when the user opens Cost Details → Add Charges / Add Multiple Charges,
then only Air Export charges must be displayed.

11 — Air Export Sales Charges Filter¶

Given the current HAWB is Air Export,
when the user opens Sales Details → Add Charges / Add Multiple Charges,
then only Air Export charges must be displayed.

12 — Charge Search Respects Air Export Filter¶

Given the current HAWB is Air Export,
when the user searches by charge code or charge name in the Add Charges popup,
then the results must remain restricted to Air Export charges only.

13 — Wrong Module Charges Not Displayed¶

Given the current HAWB is Air Export,
when the user opens the charge selection popup,
then Air Import, Ocean Import, Ocean Export, and unrelated charges must not be displayed.

14 — Existing Saved Charges Not Affected¶

Given an Air Export HAWB already has saved cost or sales charges,
when this enhancement is deployed,
then the existing saved charges must remain unchanged.

15 — Ready for FHL Can Be Set or Validated¶

Given the HAWB is Air Export,
when all required FHL-related data is complete,
then the system must show or set the HAWB as Ready for FHL.

---

16 — Ready for FHL Shows Not Ready When Data Is Missing¶

Given the HAWB is Air Export,
when required FHL-related data is missing or invalid,
then the system must show that the HAWB is not Ready for FHL and display relevant validation messages where applicable.

17 — FHL Transmission Is Not Done from HAWB Repository¶

Given the HAWB is marked or validated as Ready for FHL,
when the user is working in the HAWB Repository,
then the system must not send the FHL message from this screen.

The actual FHL sending must be handled from the File Reference functionality.

18 — Use Existing HAWB Popup Shows Only Landing & Shipping Import HAWBs¶

Given the user opens the Use Existing HAWB / Use Existing HAWB Landing & Shipping popup from the Air Export HAWB Repository,
when the popup loads,
then the system must display only HAWBs from the Air Import HAWB Repository where Landing & Shipping has been marked.

19 — Non-Landing & Shipping Import HAWBs Must Not Be Displayed¶

Given Import HAWBs exist without Landing & Shipping marked,
when the user opens the Use Existing HAWB popup,
then those non-eligible Import HAWBs must not be displayed.

20 — Already Used Landing & Shipping HAWBs Must Not Be Displayed¶

Given an Import HAWB marked as Landing & Shipping has already been selected and saved in an active Air Export HAWB,
when the Use Existing HAWB popup is opened,
then that Import HAWB must not be displayed in the available list.

21 — Selected HAWB Is Removed Only After Save¶

Given the user selects an eligible Import HAWB from the Use Existing HAWB popup,
when the Air Export HAWB has not yet been saved,
then the selected Import HAWB must not be permanently removed from the available list.

22 — Cancel or Close Without Save Keeps HAWB Available¶

Given the user selects an eligible Import HAWB,
when the user closes the screen, cancels the action, or does not save the Air Export HAWB,
then the selected Import HAWB must remain available in the Use Existing HAWB popup.

23 — Save Export HAWB Removes Selected Import HAWB from Available List¶

Given the user selects an eligible Import HAWB and saves the Air Export HAWB successfully,
when the Use Existing HAWB popup is opened again,
then the selected Import HAWB must no longer appear in the available list.

24 — User Can Clear Wrong Selection Before Save¶

Given the user selected the wrong Import HAWB,
when the Air Export HAWB has not yet been saved,
then the user must be able to clear/remove the selected HAWB and select another eligible HAWB.

25 — Unlink Saved HAWB While Export HAWB Is Editable¶

Given an Air Export HAWB has been saved using an Import HAWB marked as Landing & Shipping,
when the Export HAWB is still in an editable status,
then the user should be able to unlink the selected Import HAWB.

26 — Unlinked Import HAWB Becomes Available Again¶

Given the user unlinks the selected Import HAWB from the Air Export HAWB,
when the Use Existing HAWB popup is opened again,
then the unlinked Import HAWB should become available again in the list.

27 — Unlink Restricted After Downstream Processing¶

Given the Air Export HAWB has already been Confirmed, Approved, Finalized, linked to MAWB, or used in File Reference,
when the user attempts to unlink the selected Import HAWB,
then the system should prevent unlinking.

Unlinking should be done in the File Reference, if FHL has not been sent to Airline

28 — Source Import HAWB Remains Traceable¶

Given an Import HAWB is reused in the Air Export HAWB process,
when the Air Export HAWB is saved,
then the system should retain a reference to the source Import HAWB for traceability.

29— Use Existing HAWB Search Respects Eligibility¶

Given the user searches by HAWB number, Origin, Destination, or Date Range,
when the search results are returned,
then the system must return only Import HAWBs that are marked as Landing & Shipping and are not already actively used by another saved Air Export HAWB.

30 — Air Import MAWB Link Regression¶

Given the current HAWB is Air Import,
when the user opens the Link MAWB popup,
then the existing Air Import MAWB linking behaviour must remain unchanged.

31 — Air Import Charge Filter Regression¶

Given the current HAWB is Air Import,
when the user opens Cost Details or Sales Details Add Charges popup,
then only Air Import charges must be displayed as per the existing Air Import rules.

32 — Ocean Charge Behaviour Not Impacted¶

Given the changes are deployed for Air HAWB Repository,
when users work in Ocean modules,
then Ocean charge selection behaviour must not be impacted.