Data Dictionary for EDI to TMS
From UG
(Difference between revisions)
(→Data Dictionary) |
(→Data Dictionary) |
||
| Line 23: | Line 23: | ||
== Data Dictionary == | == Data Dictionary == | ||
| - | See xls in http:// | + | See xls in http://ct.jaguarfreight.com/mantis/view.php?id=2229 |
== History == | == History == | ||
=== 0002347: [EDI to TMS] (Preliminary) CT to XML mapping === | === 0002347: [EDI to TMS] (Preliminary) CT to XML mapping === | ||
Revision as of 21:49, 14 January 2011
Contents |
Mantis
0002229: [EDI to TMS] (Preliminary) Create data dictionary / TMS to CT2 fields mapping table
Intro
This document describes objects, fields, related XML definitions, etc that will participate in integration with TMS.
Goals
We need to identify on per fields basis:
- CT2 fields to send to TMS for each IP
- TMS fields to send to CT2 for each IP
- what fields to be updated in CT2 and what in TMS
- include into xml messaging what is required
- if field is present in both systems then .... block user from corrupting data
- what additional fields to create/re-define in CT2
- what additional fields to create/re-define in TMS
- mapping of CT2 to TMS fields
Data Dictionary
See xls in http://ct.jaguarfreight.com/mantis/view.php?id=2229
