Data Dictionary for EDI to TMS
From UG
(Difference between revisions)
(→Lean style CT2 data dictionary for Truck Dom) |
(→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. | ||
+ | |||
+ | == 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 == | == XML representation of Jaguar CT record using Jaguar names == |
Revision as of 18:56, 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.
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.
<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