Data Dictionary for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(→Intro)
(→Intro)
Line 6: Line 6:
It will be sent to Lean so they may review.
It will be sent to Lean so they may review.
 +
 +
== XML representation of Jaguar CT record ==
 +
 +
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 ==
== Lean style CT2 data dictionary for Truck Dom ==

Revision as of 00:48, 17 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

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

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

CT Num

  • Type: N
  • Length: ?
  • Required? N
  • 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
Retrieved from "https://wiki.jaguarfreight.com/Data_Dictionary_for_EDI_to_TMS"
Personal tools