Receiver Role

From UG

Current revision as of 18:53, 31 October 2013

[edit] About

Mantis:

• Parent: 0004283
• Category: ASN: Receiver

[edit] Business Info

[edit] Definitions

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

[edit] Business Needs

1) Need to provide Receiver the following functionality:

• #Confirmation of Delivery
• #Verification of Contents Delivered

2) Add #Related Reports into the system.

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

[edit] 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)

[edit] Related Reports

• dashboard ad KPI reports

[edit] Solution

[edit] Solution Summary

1) Under each Portal add Receiver user role with certain rights and access to ASN info and link to Ship To location

2) Add ability for Receiver user to browse ASN/CT records and set Received On date and Received Status

3) Add ability for Receiver to work with Commodity Table to identify discrepancies

4) Add KPIs, dashboard reports

[edit] Admin

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

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

[edit] Visibility to ASN records

• • deleted, canceled should not be included

88 see also # Admin

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

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

[edit] New Hold Rejected and Archived Tabs

On these tabs:

• allow to only View CTs
• provide set of standard filters

[edit] Approved and Delivered Tabs

On these tabs provide:

• ability to view ASN
• standard filters
• ability to set #Received Status and #Received On Date
• ability to filter by #Received Status and #Received On Date

[edit] Received On Date

• this is a new field
• it is an attribute of CT
• editable for Receiver Role; for all other roles is read-only
• type = date
• default = blank
• it is an actual delivery date as confirmed by Receiver
• ability to set this date for multiple records (selected manually or by selecting filters);

[edit] Received Status

• this is a new field
• it is an attribute of CT
• editable for Receiver Role; for all other roles is read-only
• possible values: Y, N
• default: N
• it is an actual delivery status as confirmed by Receiver
• ability to set this date for multiple records (selected manually or by selecting filters)

[edit] Additional Filters on ASN List View

Ideally need to add filters such as trucker, shipper, Received On, etc for Receiver to easy identify records for which to set Received status/Date

[edit] Commodity Table with Scorecarding

Need to provide convenient interface to satisfy #Verification of Contents Delivered requirement.

[edit] Reports

• KPI # 1 - how many records have discrepancies
  • class: Volumes
  • KPI name: Receiver Discrepancy
  • count number of CTs with any problem code

• KPI # 2 - lead time from delivered to received
  • class: Lead Times
  • KPI name: Delivered to Received
  • difference in days between Delivered and Received

[edit] SOWs