FFA

Description

Meeting on 14/01/25

Mail subject: FFA_Notes of Meeting_Improvement on FFA

• Maintaining the number of container and container numbers at Freight purchase level to avoid misuse of container number.

  Functionality need further investigation and use cases, probably we should decide on container management in another workshop / Brainstorming session

Business Dev Analysis

In order to eliminate updating container references in multiple file references, the Release Order function and the container Reference field should now be managed directly within the Freight Purchase screen.  After updating a container reference, it’s corresponding dummy reference should be automatically updated in the File Reference screen.

The following changes have been identified:

Acceptance Criteria:

1. Separate Container Details into a Dedicated Section
   • Introduce a “Container Details” section within the Freight Purchase screen.
   • Move all container-related fields into this section.
2. Add a "Container Reference" Field Supporting Multiple Entries
   • Place it besides the "Container Type" field.
   • Initially, each Container Reference will display a dummy reference.
   • After receiving the Release Order, the user must be able to update each reference individually.
   • The system should ensure that all container references are correctly linked to the corresponding File Reference.
3. The user must be able to add multiple containers within the same Freight Purchase and the details are displayed in a grid.
4. Add a Container Grid

o   A new "Container Details" grid should be added to the “Container Details Section under the container input fields.

o   The user enters container details in input fields, and upon clicking "Add" button, the data will be stored and displayed in the grid.

The grid should have columns for:

• Container Type
• Container Reference
• Release Order Status
• Release Order Recipient
• Actions: Edit & Delete

o   Editing a row allows the user to modify the container reference and other related fields.

o   Deleting a row removes the container from the Freight Purchase.

For point 2 to 4, it should be noted that further brainstorming should be made by software dev. Team to decide whether to do the CRUD operations on the container grid itself or proceed as above.

5. Move the "Release Order" Functionality from File Reference Screen to the Freight Purchase Screen
   • Add a "Release Order" section above or below the "Purchase Freight Charges" section.
6. Update the Freight Purchase Reference which is a number today to a specific reference format which will be eventually use as a master reference in the file references.

o   Ensure "Freight Purchase Ref: X" displays a system-generated Master File Reference (e.g., EDL24MSFE0001).

1. This Master File Reference will be used by multiple salespersons across different File References.
2. When selecting a Vessel Schedule in a File Reference, the system should retrieve the associated Master File Reference.

Additional Considerations:

• The UI should allow users to add or remove containers dynamically within a Freight Purchase.
• The system should ensure that duplicate container references are not allowed.
• Once a container reference is updated in Freight Purchase, the corresponding dummy reference in File Reference should automatically update.