ASN 20 ph3 (part2)

From UG

(Difference between revisions)
Jump to: navigation, search
(→SOW 20 Enable "Expedite feature" for ASN 2 portal)
(→Solution)
Line 75: Line 75:
:* Move Expedite tab from transportation to ASN portal attribute.
:* 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.
:* 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"''

Revision as of 16:54, 28 March 2014


Contents

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

TBD


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 (mantis 4505).
  • 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 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).
  • 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.
  • 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"


See also

Retrieved from "https://wiki.jaguarfreight.com/ASN_20_ph3_(part2)"
Personal tools