Receiver Role

From UG

Revision as of 20:36, 24 September 2013 (edit) Alex (Talk | contribs) (→Solution) ← Older edit		Revision as of 20:44, 24 September 2013 (edit) (undo) Alex (Talk | contribs) (→About) Newer edit →
Line 1:		Line 1:
	== About ==		== About ==
-	* 0004283	+	Mantis:
-	*	+	* '''Parent''': 0004283
		+	* '''Category''': ASN: Receiver
	== Business Info ==		== Business Info ==

---

Revision as of 20:44, 24 September 2013

Contents 1 About 2 Business Info 2.1 Definitions 2.2 Business Needs 2.2.1 Confirmation of Delivery 2.2.2 Verification of Contents Delivered 2.2.3 Related Reports 3 Analysis and Proposal 4 Solution 4.1 Admin 4.2 Link to Receiver Interface 4.3 Receiver Homepage 4.4 Received On Date 4.5 Received Status 4.6 Commodity Table with Scorecarding 4.7 Reports 5 SOWs

About

Mantis:

• Parent: 0004283
• Category: ASN: Receiver

Business Info

Definitions

• Receiver - employee at Destination Door (Ship To) location who oversees delivery of goods by Trucker.

Business Needs

1) Need to provide Receiver the following functionality:

• #Confirmation of Delivery
• #Verification of Contents Delivered

2) Add #Related Reports into the system.

Confirmation of Delivery

Currently we have these parties that can tag ASNs as being delivered to Destination Door on particular delivery date:

• a) trucker (currently through Descartes TMS only or other EDI)
• b) 3PL:
  • Jaguar operators (through CT2 Internal User Interface) or
  • other 3PLs (through EDI integration)

There are several cases in which we need Receiver to be involved:

• 1/ both Trucker and 3PL can not set delivery status/delivery date
  • in this case Receiver could enter this info into the system

• 2/ Trucker or 3PL sets delivery status/delivery date but we need Receiver to confirm it separately

Verification of Contents Delivered

Receiver will verify what was delivered by Trucker and should be able to enter that into the system.

This will provide info about possible discrepancies:

• more goods received (same SKU/PO)
• less goods received (same SKU/PO)
• wrong goods received (different SKU/PO)

Related Reports

• dashboard ad KPI reports

Analysis and Proposal

1) Under each Portal add Receiver user role:

• with certain rights and access to ASN info
• link to Ship To location

2) Add ability for Receiver user to set Received On date:

• this is a new field
• it is an actual delivery date as confirmed by Receiver
• ability to set this date for multiple records (selected manually or by selecting filters); ideally need to add filters such as trucker, shipper, Received On, etc

3) Add ability for Receiver to work with Commodity Table to identify what PO/SKU/Qty were received under each ASN.

4) Add KPIs, dashboard reports.

Solution

Admin

• Under Admin> User Admin > User profile > Gen Tab > User roles > Receiver

• If Receiver is selected then "Receiver" tab will appear in user profile where all related configurations are located

• Receiver Tab should contain:
  • List of portals (multiselect) for which this user has a Receiver role
  • Under each portal selected above multiselect for Ship To Location which user is "managing".
  • Both settings above provide visibility (what records Receiver can see/manage)

Link to Receiver Interface

• Add "ASN Receiver" link between "ASN Planner" and "Flashlight" (Client App Header).

• Link above will provide similar ASN interface similar to Shipper or Planner.

Receiver Homepage

• Homepage is a Shipment List with:
  • ASN Portal selector (tabs). One tab per portal.
  • ASN/CT List View (tabs). One tab per mutually exclusive status. See details below.

• Tabs:
  • New
  • Approved
  • Hold
  • Rejected
  • Delivered
  • Archived

Received On Date

Received Status

Commodity Table with Scorecarding

Reports

SOWs