ASN 20 ph3 (part2)
From UG
SOWs
SOW 18 Display Estimated Delivery Date in ASN
mantis: 4327 (phase: SA, status: started)
Core Requirements
- “link” ASNs to an “automated estimated delivery date” in Admin
- display an estimated delivery date in the ASN window when a planner processes an approval.
Solution
SOW 19 Set and update Origin and Destination Countries automatically for ASN records
mantis: 4349 (phase: SA, status: started)
Core Requirements
- After implementation mantis 4191, there is either a bug or a gap in logic for ASN records, with regards to updating Geb Tab 11 & 12 automatically.
Solution
- Use already implemented logic in the following way - every clicking "Save" should update without any warning:
- "Origin Country" from "Pick up Location" Country.
- "Destination Country" from "Ship to Location" Country.
SOW 20 Enable "Expedite feature" for ASN 2 portal
mantis: 4499 (phase: QA, status: closed)
Core Requirements
- Currently this functionality is working on EA Planner (implemented for ASN 1). We need to enable this for ASN 2 portal.
Business needs
- Restore functionality as it worked for ASN1.
- Additional enabling "Expedite feature" for ASN 2 portal (mantises 4505, 4524).
- Show Expedised shipments in Reports (mantis 4504).
- Show Expedised shipments in KPIs (mantis 4501).
- Log Expedited status on COM TAB on ASN 2.0 (mantis 4325).
Solution
In addition to restored functionality implemented in ASN1:
- Expedited Planner (Expeditor) is option of ASN2 Generic Planner User (as for ASN1 EA Planner).
- "Expedited" button is presented in ASN Shipment list and in ASN view window.
- Expeditor has ability to leave the comment in Confirmation window (same as the comment feature on Approve/Hold/Reject window).
- Adding of Expedited Comment can be set as mandatory field for processing the Expedited request.
- This implemented as ASN Portal option with "Expedited Comments Mandatory" checkbox in General tab of the Portal Admin section.
- Expedited Email notification should be sent to:
- Shipper who created an expedited ASN.
- Planner who expedited ASN.
- ASN Portal Team (to be defined).
- Expeditor can edit "Cargo Due Date":
- Default is the same date from the approved planner.
- Email notification content has two lines - Original Cargo Due Date and Revised Cargo Due Date.
- Indicate “expedited shipment” with red color:
- Red circle in "Status" column.
- When mouse over show hint with combined text (previous state + expedited info).
- In ASN view window, show "This is an Expedited ASN" red bold label.
- Expedised shipment should be available on report output and filter for Main:
- Report should include Reason Code, Expeditor's Comment, etc.
- Volume KPI reflects Expedites count (same as CT count):
- Move Expedite tab from transportation to ASN portal attribute.
- Add one more tab to the bottom right graph (Expedite) to show bar per reason code.
- Expedited status should be logged on COM Tab on ASN 2.0.
- Example:
- CT#XXXXXX has been EXPEDITED by <Planner Name>
- Expedited Code: <Reason Code>
- Original Cargo Due Date: Date in format "DD-MMM-CCYY" or "n/a"
- Revised Cargo Due Date: Date in format "DD-MMM-CCYY" or "n/a"
SOW 21 Create an upload list of shippers/planners functionality (script)
mantis: 4525 (phase: Est, status: open)
Core Requirements
- Create an upload list of shippers/planners functionality (script).
Business needs
- Ability to import ASN2 User Profiles into the system from Excel files.
Solution
- Data is prepared in two separated files - Shippers and Planners lists.
- Handling script works with each file, new or modified records can update the User Profiles in DB
Generic Shipper
- Shippers list provides parameters of User Profiles in the following columns:
- Action - empty for Add new or Modify existing user (not using currently).
- Email - User Email as Identifier, mandatory field.
- First Name, Last Name, Password - Optional, Required for New Shippers only. For existing user are ignored.
- Shipper Company name - Mandatory for new shippers only.
- If specified for existing user - then it will be updated "CompanyName - City [ - Remark]"
- Note: Remark is optional, used if several companies with same Name and City are exists.
- ASN Portal Name - ASN2 Portal that is applied to Shipper
- PO Issued By Name - List of POIB companies of the Portal for current Shipper.
- Air Approval, Cargo Due Date - "Y", "N" or empty for default by ASN Portal
- Transport Mode - List of all transport modes for current Shipper per PO Issued By, on Single Line "Mode [- Submode]"
- * (star) means using all current Portal settings for Shipper
- Approval Mode - optional. If empty then default Approval Mode of ASN Portal is applied.
- Possible values: (auto, single, double)
Generic Planner
- Planners list provides parameters of User Profiles in the following columns:
- Action - empty for Add new or Modify existing user (not using currently).
- Email - User Email as Identifier, mandatory field.
- First Name, Last Name, Password - Optional, Required for New Shippers only. For existing user are ignored.
- ASN Portal Name - ASN2 Portal that is applied to Planner.
- PO Issued By - appropriate "PO Issued By Name" company from applying Portal that is assigned to Planner.
- Regular, Super, Air, View Only - possible Planner parameters per PO Issued By, active are indicated with "X".
SOW 22 Allow OPS to edit MOT for ASN approved shipments to all internal users
mantis: 4508 (phase: QA, status: closed)
Core Requirements
- Allow Jaguar operator to make some change for MOT of ASN approved shipment from Internal Application.
- The feature should be control per Portal and allow all roles.
Solution
- Ability to change Transport Mode for ASN approved shipments by Jaguar Ops can be allowed from ASN Portal Admin section.
- This managed on "General" tab with using "Allow change MOT after shipment is approved" checkbox.
- When MOT changed in Internal Application it should be updated in ASN by the following rules:
- if CT2 MOT = {AIR, Trucking-Air} then ASN Transport Mode is "Air".
- if CT2 MOT = {Ocean-LCL, Client Consolidation} then ASN Transport Mode is "Ocean LCL".
- if CT2 MOT = {Ocean-FCL MBL/AW, Trucking-Ocean} then ASN Transport Mode is "Ocean FCL".
- if CT2 MOT = {UNDEFINED} then ASN Transport Mode is "Undefined".
- NOTE: MOT = Trucking-Domestic is unavailable for change and cannot be set for any ASN approved CT.
SOW 23 Log in ASN the actions for MOT changes by Ops from CT2
mantis: 4520 (phase: QA, status: closed)
Core Requirements
- Add action for MOT changed from operator in CT2 to "H" on ASN portal
- Also on communication tab
- For all ASN records
Solution
- Once Jaguar Operator (in Internal App) changed Transport Mode in the shipment approved from ASN, this action should be reflected in ASN history log.
- System shows "Transport Mode changed to MOT XXX" message in:
- Comment column of "Authorization Status History" window (click "H" in Gen tab of ASN View form).
- Other columns: Status - Approved, Last Update - time stamp of action, Updated By - System.
- Communication Log in Com tab of ASN View form.
- To: Default e-mail. From: system environment e-mail, f.e.cybertrax_kuchma@jaguarfreight.com.
SOW 24 Remove restriction to add commodity lines for ASN records in Internal App
mantis: 4481 (phase: QA, status: closed)
Core Requirements
- Remove ASN1 constraint ("This table can't have more then one commodity item!") to add commodity lines for ASN records in internal app, for CT records created with enabled in a portal/MOT option "Multiple Commodity Items".
Solution
- Option "Multiple Commodity Items" is managed from Transport Mode rule of ASN Portal Admin section (Transport Modes tab).
- If this feature is turned-on for a MOT then:
- ASN record created in the Portal with this MOT can have multiple commodity lines.
- After transmitting this ASN to CT2 it will not have constraint for adding new commodity.
- If this feature is turned-off for a MOT then:
- ASN record created in the Portal with this MOT will be splitted to several ASNs having only ONE commodity line.
- After transmitting any of these ASNs to CT2 it will be subject of ASN1 constraint for adding new commodity.
SOW 25 Pending Air Approval Filter
mantis: 4535 (phase: QA, status: new)
Core Requirements
- Provide filtering the ASNs that are pending for Air Approval process.
- Show counter of pending records.
Solution
- Filtering is provided with new button on the control panel of Shipment List in ASN Portal.
- Button becomes visible in ASN Planner UI if at least one ASN record is pending for Air approval.
- Label of button is "Pending Air Approval count: N", where N is count of pending ASN records.
- Clicking on the button filters Air Approval pending records in ASN Shipment List.
- If pending ASNs are filtered the button label becomes bold Orange and changes to "Only Pending Air Approval shown: N".
- Next clicking clears the filter and changes label and counter back to the non-filtered values.
SOW 26 Dashboard --> Pre-Approved for AIR, pending Final Air Approval
mantis: 4536 (phase: Stg, status: completed)
Core Requirements
- Type of report/additional filter.
Solution
- "Pending Air Approval" report type is implemented in ASN report.
See also
- ASN 20 ph3 - first part of SOWs for ASN 2.0