Data Dictionary for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(CT Num)
(Lean style CT2 data dictionary for Truck Dom)
Line 33: Line 33:
=== CT2 Field 1 ===
=== CT2 Field 1 ===
-
* ''Type:''
+
 
-
* ''Length:''
+
* ''Description/Notes:''
* ''Description/Notes:''
* ''Matching Lean Field:''
* ''Matching Lean Field:''
* ''Link to [[CT bo]]:''
* ''Link to [[CT bo]]:''
 +
* ''Type:''
 +
* ''Length:''
 +
* ''Required?''
=== CTNum ===
=== CTNum ===
-
* ''Type:'' N
+
 
-
* ''Length:'' ?
+
-
* ''Required?'' N
+
* ''Description/Notes:'' Unique id for the CT2 shipment
* ''Description/Notes:'' Unique id for the CT2 shipment
* ''Matching Lean Field:'' [[ll#ScheduleNum]]? (but it is too smal - only 3 digits!)
* ''Matching Lean Field:'' [[ll#ScheduleNum]]? (but it is too smal - only 3 digits!)
* ''Link to CT bo:'' [[CT#CT_Num]]
* ''Link to CT bo:'' [[CT#CT_Num]]
 +
* ''Type:'' N
 +
* ''Length:'' ?
 +
* ''Required?'' N

Revision as of 18:37, 19 July 2010


Contents

Intro

This document describes fields that will participate in integration with Lean.

It will be sent to Lean so they may review.

XML representation of Jaguar CT record using Jaguar names

Only fields that required by TMS.

<CT>
  <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

Type:

  • A
  • AN - alphanumeric
  • N
  • D - date


CT2 Field 1

  • Description/Notes:
  • Matching Lean Field:
  • Link to CT bo:
  • Type:
  • Length:
  • Required?

CTNum

  • Description/Notes: Unique id for the CT2 shipment
  • 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
Personal tools