Original House Bill of Lading Validation

From UG

Contents 1 Mantis 2 Introduction 3 Functionality Overview 3.1 Summary 4 Export Functionality 5 Import Functionality 6 Export OHBL validation message 7 Acknowledge Originals are Required Prior to Release at Destination Feature

Mantis

[2190]

Introduction

This feature is for all ocean shipments that Jaguar Freight arranges from origin to destination and issues an original house bill of lading (aka OHBL). This is to bring to the import operators attention that an original house bill of lading was issued and that they must have their team leaders acknowledgment of this.

Functionality Overview

Summary

There are 3 types of Jaguar operator roles involved for the Original House of Lading Validation. First is the Jaguar export operator, second is the Jaguar import operator & last are the supervisors

Core roles of Jaguar export operator:

• Create the CT to arrange the shipment from origin door or origin port to the destination port
• Creates or Issues original house bills of ladings, if and when required, as well as other export related documentation

Core roles of Jaguar import operator:

• Arranges for the shipment from destination port to destination door
• Creates arrival notices, as well as other import related documentation

Core roles of Jaguar supervisors:

• Monitor their teams work and performance
• Takes responsibility roles to ensure their teams are following the current SOP

Currently CT_bo#Original_House_Bill_Yes_No is set to default to ‘Yes’ on export tab, this needs to change to default to 'No'

Export Functionality

Upon Jaguar Export Operator updating the #Port_Of_Loading_Actual_Date the following things should happen:

• An export OHBL validation message should appear to user asking them to confirm if an original house bill of lading is required? Y/N
  • If user clicks No, record that in the updates log with the operators name, date & time stamp
    • Update CT_bo#Original_BL_Required_Yes_No to the same Y/N

• • If user clicks Yes, the following should happen:
    • Record that in the updates log, with the operators name, date & time stamp.
    • Update CT_bo#Original_BL_Required_Yes_No to the same Y/N
    • Add the following comment: "This shipment can only be released against presentation of duly endorsed ocean Bills of Ladings" into the comment tab #Comments_and_Query of the CT record or records if a part of a group
• Not allow updates to both the CT_bo#Import_Fields & the CT_bo#Import_Ref until a team leader or other super ops/management user confirms the #Acknowledge_Originals_are_Required_Prior_to_Release_at_Destination_Feature

Import Functionality

The following things should happen when a CT record has both CT_bo#Original_House_Bill_Yes_No & CT_bo#Original_BL_Required_Yes_No set to 'YES':

• Display a message to the import operator, see: #Acknowledge_Originals_are_Required_Prior_to_Release_at_Destination_Feature
• Notify team leaders, management, etc, see: #Acknowledge_Originals_are_Required_Prior_to_Release_at_Destination_Feature

Export OHBL validation message

• Message displayed will be:

Acknowledge Originals are Required Prior to Release at Destination Feature

• This feature could be similar to the #Issue_Credit_Note feature, where the import fields would require approval from a group of users who have permission to unblock those fields from being updated.
  • This should only happen if #Original_BL_Required_Yes_No is clicked to 'Yes'.
• The system should also have some sort of a notification for the group of users who have the permission to unblock the import fields.
• Also, the system should display a message to the users who try to update any of the import fields.
  • For example: You cannot proceed until an “acknowledge of originals required prior to release at destination” is confirmed by a supervisor (team leader, management etc).
• Once a team leader, management, etc, confirms this, it should record in the updates log, with their name, date & time stamp
• Lastly, make all of those fields now editable by all users.