Q and A for EDI to TMS

From UG

Revision as of 23:09, 16 July 2010 (edit) Alex (Talk | contribs) m (moved EDI to TMS Q and A to Q and A for EDI to TMS) ← Older edit		Revision as of 23:59, 16 July 2010 (edit) (undo) Alex (Talk | contribs) (→What fields could be updated from CT2 after CT is loaded into TMS (integr point A)) Newer edit →
Line 25:		Line 25:
	* TMS user		* TMS user
	* Carrier System user		* Carrier System user
		+
		+	=== Fields CustomerRef and Customer seem to duplicate each other ===
		+
		+	<CustomerRef>943847</CustomerRef> in Order Plan XML
		+	<Customer>943847</Customer> in Order XML
	== Answered Questions ==		== Answered Questions ==

---

Revision as of 23:59, 16 July 2010

Contents 1 How to use this doc 2 New Unanswered Questions and Discussion 2.1 What fields could be updated from CT2 after CT is loaded into TMS (integr point A) 2.2 Fields CustomerRef and Customer seem to duplicate each other 3 Answered Questions

How to use this doc

Question could be posted here.

Add wiki signature, forward link to someone you think might answer.

Discussion could be posted here.

If answer is final then spec must be updated and question marked as answered - move to #Answered Questions.

New Unanswered Questions and Discussion

What fields could be updated from CT2 after CT is loaded into TMS (integr point A)

I assume none or just some. Also, this is not on a diagram.

Ideally we need to define per field when and from what system it may be updated. We deal with 5 systems/users:

• CT2 shipper user (I assume they have read rights only at the point CT is fed into TMS)
• CT2 planner user (I assume they have read rights only at the point CT is fed into TMS)
• CT2 internal user
• TMS user
• Carrier System user

Fields CustomerRef and Customer seem to duplicate each other

<CustomerRef>943847</CustomerRef> in Order Plan XML
<Customer>943847</Customer> in Order XML

Answered Questions