Receiver Role

From UG

Revision as of 00:28, 24 September 2013 (edit) Alex (Talk | contribs) (Created page with '== Info == * 0004283 * == Requirements == == Solution == == SOWs ==') ← Older edit		Revision as of 00:45, 24 September 2013 (edit) (undo) Alex (Talk | contribs) (→Requirements) Newer edit →
Line 4:		Line 4:
	*		*
-	== Requirements ==	+	== Business Needs ==
		+
		+	Currently we have these parties that can tag ASNs as being delivered:
		+
		+	* a) trucker (currently through Desc TMS only)
		+	* b) 3PL:
		+	** Jaguar operator (through CT2 internal) or
		+	** other 3PLs (through EDI integration)
		+
		+	We need to add ability for Receiver (Consignee) to confirm separately delivery or in case:
		+	* 1) a or b above can not do it
		+	* 2) in addition to a and b
		+
		+	Also actual contents could be entered against scheduled or indicated by a and b above.
	== Solution ==		== Solution ==
	== SOWs ==		== SOWs ==

---

Revision as of 00:45, 24 September 2013

Contents 1 Info 2 Business Needs 3 Solution 4 SOWs

Info

• 0004283

Business Needs

Currently we have these parties that can tag ASNs as being delivered:

• a) trucker (currently through Desc TMS only)
• b) 3PL:
  • Jaguar operator (through CT2 internal) or
  • other 3PLs (through EDI integration)

We need to add ability for Receiver (Consignee) to confirm separately delivery or in case:

• 1) a or b above can not do it
• 2) in addition to a and b

Also actual contents could be entered against scheduled or indicated by a and b above.

Solution

SOWs