Data Dictionary for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(→Intro)
(→History)
 
(27 intermediate revisions not shown)
Line 1: Line 1:
[[Category: EDI to TMS]]
[[Category: EDI to TMS]]
-
== Intro ==
+
== Mantis ==
-
This document describes fields that will participate in integration with Lean.
+
'''0002229''': [EDI to TMS] (Preliminary) Create data dictionary / TMS to CT2 fields mapping table
-
It will be sent to Lean so they may review.
+
== Intro ==
-
 
+
-
== Required fields and updates ==
+
-
 
+
-
=== Minimum set of CT2 fields required by TMS from CT2 for IP1 ===
+
-
 
+
-
=== Minimum set of fields required by CT2 from TMS for IP2 IP3 IP4 ===
+
-
 
+
-
==== Internal ====
+
-
 
+
-
==== Client Shipper Planner ====
+
-
 
+
-
== XML representation of Jaguar CT record using Jaguar names ==
+
-
Only fields that required by TMS.
+
This document describes objects, fields, related XML definitions, etc that will participate in integration with TMS.
-
<CT>
+
== Goals ==
-
  <CTNum>124896</CTNum>
+
-
  <E0Client>EA Arden</E0Client>
+
-
  ...
+
-
  <CommodTable>
+
-
    <Commodity>
+
-
      <PO>5454</PO>
+
-
      <SKU></SKU>
+
-
      ...
+
-
    </Commodity>
+
-
  </CommodTable>
+
-
</CT>
+
-
== Lean style CT2 data dictionary for Truck Dom ==
+
We need to identify on per fields basis:
-
Type:
+
* CT2 fields to send to TMS for each IP
-
* A
+
* TMS fields to send to CT2 for each IP
-
* AN - alphanumeric
+
* what fields to be updated in CT2 and what in TMS
-
* N
+
** include into xml messaging what is required
-
* D - date
+
** 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 ==
-
=== CT2 Field 1 ===
+
See xls in http://ct.jaguarfreight.com/mantis/view.php?id=2229
-
* ''Description/Notes:''
+
== History ==
-
* ''Matching Lean Field:''
+
-
* ''Link to [[CT bo]]:''
+
-
* ''Type:''
+
-
* ''Length:''
+
-
* ''Required?''
+
-
=== CTNum ===
+
=== 0002347: [EDI to TMS] (Preliminary) CT to XML mapping ===
-
* ''Description/Notes:'' Unique id for the CT2 shipment
+
=== 0002693: [EDI to TMS] (Shipment_Import) Change: Pass Loose Pkgs on Shipment Import as 1 line item ===
-
* ''Matching Lean Field:'' [[ll#ScheduleNum]]? (but it is too smal - only 3 digits!)
+
-
* ''Link to CT bo:'' [[CT#CT_Num]]
+
-
* ''Type:'' N
+
-
* ''Length:'' ?
+
-
* ''Required?'' N
+

Current revision as of 22:04, 14 January 2011


Contents

[edit] Mantis

0002229: [EDI to TMS] (Preliminary) Create data dictionary / TMS to CT2 fields mapping table

[edit] Intro

This document describes objects, fields, related XML definitions, etc that will participate in integration with TMS.

[edit] 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

[edit] Data Dictionary

See xls in http://ct.jaguarfreight.com/mantis/view.php?id=2229

[edit] History

[edit] 0002347: [EDI to TMS] (Preliminary) CT to XML mapping

[edit] 0002693: [EDI to TMS] (Shipment_Import) Change: Pass Loose Pkgs on Shipment Import as 1 line item

Retrieved from "https://wiki.jaguarfreight.com/Data_Dictionary_for_EDI_to_TMS"
Personal tools