Data Dictionary for EDI to TMS
From UG
(Difference between revisions)
(→Intro) |
(→XML representation of Jaguar CT record) |
||
Line 15: | Line 15: | ||
<E0Client>EA Arden</E0Client> | <E0Client>EA Arden</E0Client> | ||
... | ... | ||
- | |||
<CommodTable> | <CommodTable> | ||
<Commodity> | <Commodity> | ||
Line 21: | Line 20: | ||
<SKU></SKU> | <SKU></SKU> | ||
... | ... | ||
- | |||
</Commodity> | </Commodity> | ||
</CommodTable> | </CommodTable> |
Revision as of 00:49, 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