Data Dictionary for EDI to TMS

From UG

Revision as of 17:48, 15 October 2010 (edit) Alex (Talk | contribs) ← Older edit		Revision as of 16:02, 18 October 2010 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 1:		Line 1:
	[[Category: EDI to TMS]]		[[Category: EDI to TMS]]
		+
		+	== Mantis ==
		+
		+	'''0002229''': [EDI to TMS] (Preliminary) Create data dictionary / TMS to CT2 fields mapping table
	== Intro ==		== Intro ==

---

Revision as of 16:02, 18 October 2010

Contents 1 Mantis 2 Intro 3 Goals 4 Data Dictionary

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://mantis.jaguarfreight.com/mantis/view.php?id=2229