ASN 20 ph3 (part2)

From UG

Revision as of 11:04, 9 April 2014 (edit) Andrei (Talk | contribs) (→Solution) ← Older edit		Revision as of 11:37, 9 April 2014 (edit) (undo) Andrei (Talk | contribs) (→Solution) Newer edit →
Line 101:		Line 101:
	*		*
	:* Action - empty for Add new or Modify existing user (Not using currently)		:* Action - empty for Add new or Modify existing user (Not using currently)
-	:* Email	+	:* Email - User Email as Identifier, mandatory field
-	:* First Name	+	:* First Name, Last Name, Password - Optional, Required for New Shippers only. For existing user are ignored.
-	:* Last Name	+	:* Shipper Company name - Mandatory for new shippers only. If specified for existing user - then it will be updated '''"CompanyName - City[ - Remark]"''' (Remark is optional, used if several companies with same Name and City are exists).
-	:* Password	+	:* ASN Portal Name - Shipper's Portal
-	:* Shipper Company name	+
-	:* ASN Portal Name	+
	:* PO Issued By Name		:* PO Issued By Name
	:* Air Approval		:* Air Approval

---

Revision as of 11:37, 9 April 2014

Contents 1 SOWs 1.1 SOW 18 Display Estimated Delivery Date in ASN 1.1.1 Core Requirements 1.1.2 Solution 1.2 SOW 19 Set and update Origin and Destination Countries automatically for ASN records 1.2.1 Core Requirements 1.2.2 Solution 1.3 SOW 20 Enable "Expedite feature" for ASN 2 portal 1.3.1 Core Requirements 1.3.2 Business needs 1.3.3 Solution 1.4 SOW 21 Create an upload list of shippers/planners functionality (script) 1.4.1 Core Requirements 1.4.2 Business needs 1.4.3 Solution 2 See also

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

• Provide an ability to mass creating the new ASN2 User Profiles.

Solution

• .

Generic Shipper

• 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]" (Remark is optional, used if several companies with same Name and City are exists).
• ASN Portal Name - Shipper's Portal
• PO Issued By Name
• Air Approval
• Cargo Due Date
• Transport Mode
• Approval Mode

Generic Planner

• Action
• Email
• First Name
• Last Name
• Password
• ASN Portal Name
• PO Issued By
• Regular
• Super
• Air
• View Only

---

See also

• ASN 20 ph3 - first part of SOWs for ASN 2.0