Project

General

Profile

Actions

Task #19069

open

Task #19100: Sprint Planning for 17/11/2025 - 28/11/2025

File reference process flow

Added by Redmine Admin 30 days ago. Updated about 1 hour ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
11/10/2025
Due date:
11/10/2025 (30 days late)
% Done:

0%

Estimated time:
0:00 h
GitLab ID:
3488
GitLab Milestone:
GitLab Ticket Number:
1018
GitLab Time Logged:
0
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 17/11/2025 - 28/11/2025

Description

(1)   A file reference can be created with or without a flight.

(i)                  If the File reference is created with no flight, it should always be a ‘Draft’.

(2)   The Freight forwarder should create a file reference using a ‘shipment’.

(i)                  This is the baseline for the creation of a File reference (No shipment thus no file reference)

(ii)                A shipment of type ‘Provisional’ can be associated to a File reference.

(3)   Display all the costs associated to the shipment.

(4)   The Freight forwarder should be able to select one or more House Bill of lading found in the House AWB Repository to populate the House Manifest.

(5)   In case the house is missing from the House AWB Repository, system shall allow the user to create it manually.

(6)   Cost and sales shall be calculated automatically at two levels namely:

(i)                  Master level

(ii)                House level

(7)   Different status of a House B/L

(i)                  In progress – Shall be used when an operation officer is still working on a file reference. At this stage a minimal validation is required.

(ii)                Confirmed – All information has already been inserted concerning this shipment and further validation is required.

(iii)              Approved – This indicate that the File has been approved by a supervisor / manager, showing that all value related to the file is vetted. Invoice can be issued at this stage.

(iv)              Closed – Payment already effected by the Importer / Client and Delivery order issued.

 

(8)   Different of a File Reference

(i)                  In progress - Indicates that the file reference has been initiated but is awaiting further action.

(ii)                Completed - Indicates that all necessary actions related to the file reference have been completed.

(iii)              Approved – This indicates that the file has been reviewed and approved by a ‘Supervisor’ or a ‘Manager’.

(iv)              Closed – This indicates that all the documentation / administrative task has been completed and all records having a ‘closed’ status should have a ‘View only’ option.

(9)   Generation and Submission of Advice of arrival and notice of arrival.

(10)                       Transmission of the File Reference to AirCCS.

(11)                       Displaying Response received from CMS.


GitLab Sync Log

[]

Actions

Also available in: Atom PDF