Project

General

Profile

Actions

Task #17258

closed

Task #16518: Sprint Planning 22/07/2024 - 29/07/2024

FE - MBL Create

Added by Redmine Admin 7 months ago. Updated about 2 hours ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
05/26/2024
Due date:
05/26/2024
% Done:

100%

Estimated time:
0:00 h
Spent time:
GitLab ID:
607
GitLab Milestone:
GitLab Ticket Number:
100
GitLab Time Logged:
64800
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning 22/07/2024 - 29/07/2024

Description

Objective: Develop and enhance the Master BL Screen module to efficiently create, manage, and track Master Bill of Lading (MBL) or Master Air Waybill (MAWB) for both Ocean and Air Import/Export operations.
User Stories for Master BL Screen Module:

  1. MBL/MAWB Creation:
  • As a user, I want to create a new MBL/MAWB record with a unique reference number and select shipper, consignee, notify parties, ports, charges, etc. from dropdown lists populated with existing clients in the system. (Acceptance Criteria: Unique reference number generation, ability to enter details like Shipper, Consignee, Notify Party, Ports.
    Integration with existing client database, dropdown population based on user permissions).
  1. Salesperson/Client List Integration:
  • As a salesperson, I want to view and manage only my client/consignee list when creating or editing MBLs/MAWBs. (Acceptance Criteria: Implement user-based client filtering)
  1. Weight and Chargeable Weight Calculation:
  • As a user, I want the system to automatically calculate Master Chargeable Weight (in case of Air) and ensure that master weight tallies with associated HBLs/HAWBs.
  • Chargeable Weight = (Dimension * No. of Pieces) / 6000
  • (Acceptance Criteria: Develop automatic chargeable weight calculation based on HBL/HAWB data)
  1. Status Update Handling:
  • As a user, I want to update statuses of MBLs/MAWBs at different stages of processing, such as when DO is received from shipping line or Airline. (Acceptance Criteria: Define and implement status options, allow users to update status)
  1. Data Exchange Integration:
  • As a system, I want to ensure secure, accurate, and timely data exchange between the Freight Forwarding system and external systems. (Acceptance Criteria: Define data security protocols, implement data validation for external exchanges)
  1. Linking to Bookings and Schedules:
  • As a user, I want MBLs/MAWBs to be linked to the corresponding booking if exist and vessel/flight schedules for accurate tracking and scheduling of cargo. (Acceptance Criteria: Develop functionality to link MBL/MAWBs to bookings and schedules)

Fields (Ocean & Air)

  1. General Information
  • Unique MBL/MAWB Reference Number
  • Shipment Date
  • Voyage/Flight Number (if applicable)
  1. Parties Involved
  • Shipper
  • Consignee
  • Notify Party
  1. Locations
  • Origin City/Country
  • Destination City/Country
  1. Cargo Details
  • Number of Packages
  • Description of Goods
  1. Weights and Measurements
  • Gross Weight
  • Volume (if applicable)
  1. Charges
  • Total Freight Charges (may be broken down further)
  1. Status
  • Current status of the shipment (e.g., Booking Confirmed, Cargo Received, Delivered)

Ocean Specific Fields

  1. Locations
  • Port of Loading (POL)
  • Port of Discharge (POD)
  1. Cargo Details
  • Container Details (Type, Size, Seal Number, etc..)
  1. Additional Information
  • Hazardous Material Indicator
  • Booking Number (for reference)

Air Specific Fields

  1. Locations
  • Airport of Departure (AOD)
  • Airport of Arrival (AOA)
  1. Cargo Details
  • Handling Information (e.g., Fragile, Perishable)
  • Special Requirements (SSR) (e.g., Temperature Control)
  1. Additional Information
  • Incoterms (International Commercial Terms)

image


GitLab Sync Log

[{"id": "5772", "author": "Nihaal Ramfoll", "hours": 6.0, "created": "2024-06-27T06:44:51.255Z", "log_date": "2024-06-27", "comment": "Imported from GitLab by @Nihaal Ramfoll on 2024-06-27T06:44:51.255Z: 6h-(6.0)h spend at: 2024-06-27", "status": "active", "deleted_by": "", "redmine_entry_id": 8685}, {"id": "5771", "author": "Nihaal Ramfoll", "hours": 6.0, "created": "2024-06-27T06:44:44.153Z", "log_date": "2024-06-27", "comment": "Imported from GitLab by @Nihaal Ramfoll on 2024-06-27T06:44:44.153Z: 6h-(6.0)h spend at: 2024-06-27", "status": "active", "deleted_by": "", "redmine_entry_id": 8686}, {"id": "5768", "author": "Nihaal Ramfoll", "hours": 6.0, "created": "2024-06-27T06:43:12.792Z", "log_date": "2024-06-27", "comment": "Imported from GitLab by @Nihaal Ramfoll on 2024-06-27T06:43:12.792Z: 6h-(6.0)h spend at: 2024-06-27", "status": "active", "deleted_by": "", "redmine_entry_id": 8687}]

Actions #1

Updated by Redmine Admin 7 months ago

  • GitLab Sync Log updated (diff)
Actions

Also available in: Atom PDF