Task #19782
openTask #19803: Sprint Planning for 27/04/2026 - 11/05/2026
Air Import House Delivery Order – Create / Issue DO per HAWB
100%
Description
Create, save, issue, retrieve, and print a Delivery Order (DO) for an Air Import HAWB so that cargo release can be officially controlled and documented.
Scope
- Applicable to Air Import Shipments only
- One active DO per HAWB
- DO created through a DO screen
- Draft / Approval workflow
- Output format: PDF Refer to ticket #1363
- Accessible from File Reference Retrieve Screen at HAWB level or a new menu
- DO data must be saved in system before issue
Air Import > House Delivery Order
Screens
- DO Retrieve Screen (List of DOs)
- Issue DO Popup (List of HAWBs)
- DO Entry Screen
User Flow
- User opens Air Import > House Delivery Order
- User clicks Issue DO
- Popup opens: List of HAWBs
- User selects HAWB
- System redirects to DO Input Screen
- User can:
- Save Draft
- Submit / Approve DO
- Generate PDF after approval
- Preview DO after approval
- Download DO after approval
Functional Requirements
1. HDO Retrieve Screen
Search Filters
- HAWB Reference
- MAWB Reference
- File Reference
- Consignee
- Status
- Date Range
Grid Columns
- Created On
- HDO Reference
- MAWB No
- HAWB No
- File Reference
- Consignee
- DO Type
- Status
- Approval Status
- Action
Actions
- View
- Edit Draft
- Approve
- Preview PDF
- Download PDF
- Cancel
2. Issue DO Button
User clicks on "Issue DO" button.
System opens popup:
Popup Title:
List of HAWBs
Popup Search Filters
- HAWB No
- MAWB No
- File Ref
- Consignee
- Arrival Date
Popup Grid Columns
- Select
- HAWB No
- MAWB No
- Consignee
- Flight No
- Arrival Date
- Status
Popup Rules
- Only Air Import HAWBs shown
- Already approved active DO HAWBs excluded (or flagged)
3. On HAWB Selection
System redirects user to HDO Entry Screen
4. HDO Entry Screen Fields
Header
| Field | Rule |
|---|---|
| HDO Number | Auto-generated |
| Status | Draft / Approved / Cancelled |
| Issue Date | Today |
| MAWB No | Read only |
| HAWB No | Read only |
Shipment Details
Read only:
- Flight No
- Arrival Date
- Airport of Arrival
- Packages
- Gross Weight
- Chargeable Weight
- Goods Description
- Marks & Numbers
Parties
- Consignee
- Notify Party
- Agent / Forwarder
Editable Fields
| Field | Rule |
|---|---|
| Delivery Location | From Master AWB Terminal |
| Cargo Release Status | Pending Release / Hold / Ready for Release |
| Authorized Signatory | Logged in user |
| Remarks | Editable text area |
5. Actions on Entry Screen
Save Draft
- Save record
- Status = Draft
Approve DO
- Validate fields
- Status = Approved
- Store approved by/date
Preview HDO
Visible only when Status = Approved
Download HDO
Visible only when Status = Approved
Note that once a DO is issued, all fields printed on the DO document shall become read-only. Any changes require Cancel/Reissue based on user permission.
Cancel HDO
System shall allow authorized users to cancel a Delivery Order (DO) from:
- DO Retrieve Screen
- DO Entry / View Screen
Only DOs with status:
- Issued / Approved
may be cancelled.
Draft DOs shall be handled through Edit or Delete Draft actions.
Cancelled DOs cannot be cancelled again.
User Action: When the user clicks Cancel DO, the system shall open a confirmation popup displaying the following:
- DO Number
- HAWB No
- Consignee
- Current Status
User must provide:
- Cancellation Reason (mandatory)
System Validation
Before cancellation, the system shall validate the following:
- User has permission to cancel DO
- DO is not already cancelled
- DO is in eligible status
On Successful Cancellation
System shall:
- Update DO Status = Cancelled
- Store Cancelled By
- Store Cancelled Date & Time
- Store Cancellation Reason
- Lock record from further approval/use
- Keep record searchable in Retrieve Screen
- Write entry to Activity Log
6. PDF Rules
PDF available only after approval.
Refer to this ticket https://gitlab.maccs.mu/rnd/ffa/documentation/-/issues/1363 for the PDF format.
Cancelled DO shall no longer be valid for release.
7. Re-Issue DO
The system shall allow authorized users to re-issue a cancelled DO.
Re-issue action available only when current DO status = Cancelled.
When the user clicks Re-Issue DO, the system shall:
- Open DO Entry Screen
- Auto-populate data from cancelled DO
- Allow editable fields based on current business rules
- Generate new DO Number upon save/issue
- Link new DO to previous cancelled DO reference
System shall retain both records:
- Original Cancelled DO
- New Re-Issued DO
with relationship reference for audit purposes.
System shall write entries for:
- Re-Issue initiated
- New DO created from cancelled DO
- New DO issued
in the Activity Log.
Activity Log
System shall maintain an Activity Log for each DO similar to Ocean module.
Columns
- Activity Date & Time
- Activity By
- Activity Description
9. Business Rules
- One active approved HDO per HAWB
- Draft may be edited
- Approved HDO read-only
- Cancelled HDO remains searchable
- Air Export excluded
GitLab Sync Log
[{"id": "43498", "author": "Waliyuddin Delba", "hours": 3.0, "created": "2026-04-30T11:27:56.761Z", "log_date": "2026-04-28", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-04-30T11:27:56.761Z: 3h-(3.0)h spend at: 2026-04-28", "status": "active", "deleted_by": "", "redmine_entry_id": 13396}, {"id": "43961", "author": "Waliyuddin Delba", "hours": 3.0, "created": "2026-05-08T11:41:25.505Z", "log_date": "2026-05-07", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-08T11:41:25.505Z: 3h-(3.0)h spend at: 2026-05-07", "status": "active", "deleted_by": "", "redmine_entry_id": 13493}, {"id": "44041", "author": "Waliyuddin Delba", "hours": 4.0, "created": "2026-05-11T09:27:29.009Z", "log_date": "2026-05-10", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-11T09:27:29.009Z: 4h-(4.0)h spend at: 2026-05-10", "status": "active", "deleted_by": "", "redmine_entry_id": 13522}, {"id": "44303", "author": "Waliyuddin Delba", "hours": 3.0, "created": "2026-05-14T06:02:22.178Z", "log_date": "2026-05-12", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-14T06:02:22.178Z: 3h-(3.0)h spend at: 2026-05-12", "status": "active", "deleted_by": "", "redmine_entry_id": 13572}, {"id": "44302", "author": "Waliyuddin Delba", "hours": 4.0, "created": "2026-05-14T06:02:14.073Z", "log_date": "2026-05-11", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-14T06:02:14.073Z: 4h-(4.0)h spend at: 2026-05-11", "status": "active", "deleted_by": "", "redmine_entry_id": 13573}, {"id": "44392", "author": "Waliyuddin Delba", "hours": 4.0, "created": "2026-05-15T05:25:27.759Z", "log_date": "2026-05-13", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-15T05:25:27.759Z: 4h-(4.0)h spend at: 2026-05-13", "status": "active", "deleted_by": "", "redmine_entry_id": 13615}, {"id": "44601", "author": "Waliyuddin Delba", "hours": 4.0, "created": "2026-05-15T11:52:53.134Z", "log_date": "2026-05-14", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-15T11:52:53.134Z: 4h-(4.0)h spend at: 2026-05-14", "status": "active", "deleted_by": "", "redmine_entry_id": 13630}, {"id": "44669", "author": "Waliyuddin Delba", "hours": 4.0, "created": "2026-05-18T11:22:12.359Z", "log_date": "2026-05-17", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-18T11:22:12.359Z: 4h-(4.0)h spend at: 2026-05-17", "status": "active", "deleted_by": "", "redmine_entry_id": 13648}, {"id": "44706", "author": "Waliyuddin Delba", "hours": 3.0, "created": "2026-05-19T10:08:14.814Z", "log_date": "2026-05-18", "comment": "Imported from GitLab by @Waliyuddin Delba on 2026-05-19T10:08:14.814Z: 3h-(3.0)h spend at: 2026-05-18", "status": "active", "deleted_by": "", "redmine_entry_id": 13663}]
Updated by Redmine Admin 4 months ago
- Estimated time changed from 0:00 h to 32:00 h
- Parent task set to #19803
- gitlab project trace set to Sprint Planning for 27/04/2026 - 11/05/2026
Updated by Redmine Admin 4 months ago
- % Done changed from 0 to 9
- GitLab Time Logged changed from 0 to 10800
Updated by Redmine Admin 4 months ago
- % Done changed from 9 to 18
- GitLab Time Logged changed from 10800 to 21600
Updated by Redmine Admin 4 months ago
- % Done changed from 18 to 31
- GitLab Time Logged changed from 21600 to 36000
Updated by Redmine Admin 4 months ago
- % Done changed from 31 to 53
- GitLab Time Logged changed from 36000 to 61200
Updated by Redmine Admin 4 months ago
- % Done changed from 53 to 65
- GitLab Time Logged changed from 61200 to 75600
Updated by Redmine Admin 3 months ago
- % Done changed from 65 to 78
- GitLab Time Logged changed from 75600 to 90000
Updated by Redmine Admin 3 months ago
- % Done changed from 78 to 90
- GitLab Time Logged changed from 90000 to 104400
Updated by Redmine Admin 3 months ago
- % Done changed from 90 to 100
- GitLab Time Logged changed from 104400 to 115200
Updated by Redmine Admin 3 months ago
- Status changed from New to Development Done