From UG
(Difference between revisions)
|
|
| Line 1: |
Line 1: |
| | [[Category:EDI to TMS]] | | [[Category:EDI to TMS]] |
| - |
| |
| - |
| |
| - | == 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
| |
| - |
| |
| - | === What happens if we add new address on CT2 side? ===
| |
| - |
| |
| - | == Answered Questions ==
| |
Revision as of 18:41, 24 October 2010
