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

[edit] Mantis

2190

[edit] 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 make both the export & import operators accountable for the shipments where an original house bill of lading was issued, with managements acknowledgment of the same according to the SOP set forth by JFS.

[edit] Functionality Overview

[edit] 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 Jaguar supervisors

Core roles of Jaguar export operator:

• Create the CT and export documentation 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 - IE Dock Receipts, Pickup Orders

Core roles of Jaguar import operator:

• Arranges for the shipment from the destination port to the destination door
• Create import documentation, as well as other import related documentation - IE arrival notices, Delivery Orders
  • Note Jag import operator does create CT records for shipments that Jaguar Freight did not arrange for the export. They will play both roles, both export and import operator, but only issue import documentation

Core roles of Jaguar supervisors:

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

[edit] Export Functionality

Jaguar export operator can confirm the CT_bo#Port_Of_Loading_Actual_Date in 2 different places:

• From the CT record (inside export tab)
• From the Master (inside master details tab)

When the port of loading actual date is confirmed in CT record (export tab), 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, the following 3 things should happen:
    • Update the CT_bo#Original_House_Bill_Yes_No to 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 No

• • If user clicks Yes, the following 6 things should happen:
    • Update the CT_bo#Original_House_Bill_Yes_No to Yes
    • Record that in the updates log with the operators name, date & time stamp.
    • Update CT_bo#Original_BL_Required_Yes_No to the same Yes
    • 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
    • Block updates to both the CT_bo#Import_Fields & the CT_bo#Import_Ref
    • Block user from being able to generate an arrival notice

• When port of loading actual date is confirmed in Master, the following should happen:
  • System should look to see if there are more than 1 CT record apart and if there are more than 1 CT records, the system should give operator soem sort of way to choose which CTs have an original house bill of lading issued and which CTs do not.

• For CT records that operator checks Y the following should happen:
  • Update the CT_bo#Original_House_Bill_Yes_No to Yes
  • Record that in the updates log with the operators name, date & time stamp.
  • Update CT_bo#Original_BL_Required_Yes_No to the same Yes
  • 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
  • Block updates to both the CT_bo#Import_Fields & the CT_bo#Import_Ref
  • Block user from being able to generate an arrival notice
  • Update all other CT records that were not checked off to No, update the CT_bo#Original_House_Bill_Yes_No to No, Record that in the updates log with the operators name, date & time stamp and update CT_bo#Original_BL_Required_Yes_No to the same No

• For CT records that operator checks N the following should happen:
  • Update the CT_bo#Original_House_Bill_Yes_No to 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 No

[edit] 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 an acknowledgement message to the import operator, see: #Acknowledge_Originals_are_Required_Prior_to_Release_at_Destination_Feature
• Notify supervisor, team leaders, management of the same
• Block user from being able to generate an arrival notice until the #Acknowledge_Originals_are_Required_Prior_to_Release_at_Destination_Featureis confirmed

[edit] Export OHBL validation message

• Message displayed would be simple: IE - Please confirm if an original house bill of lading is required? Y/N

[edit] 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 CT_bo#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.