Data Dictionary for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(Lean style CT2 data dictionary for Truck Dom)
Line 3: Line 3:
== Intro ==
== Intro ==
-
This document describes fields that will participate in integration with Lean.
+
This document describes fields that will participate in integration with TMS.
-
It will be sent to Lean so they may review.
+
== Fields definitions ==
-
== Required fields and updates ==
+
We need to identify on per fields basis:
 +
* CT2 fields to send to TMS
 +
* TMS fields to send to CT2
 +
* what additional fields to create/re-define in CT2
 +
* what additional fields to create/re-define in TMS
 +
* mapping of CT2 to TMS fields
-
=== Minimum set of CT2 fields required by TMS from CT2 for IP1 ===
+
=== CT2 Truck Dom fields as of July 2010 ===
-
=== Minimum set of fields required by CT2 from TMS for IP2 IP3 IP4 ===
+
==== Shipper and Planner Fields ====
-
 
+
-
==== Internal ====
+
-
 
+
-
==== Client Shipper Planner ====
+
-
 
+
-
 
+
-
 
+
-
== CT2 Truck Dom fields as of July 2010 ==
+
-
=== Shipper and Planner Fields ===
+
List below is from [[Cybertrax 2.1 Client (data dictionary)]]
List below is from [[Cybertrax 2.1 Client (data dictionary)]]
<pre>
<pre>
Line 66: Line 62:
</pre>
</pre>
   
   
-
=== Additional fields for Truck Dom available for Jaguar internal user ===
+
==== Additional fields for Truck Dom available for Jaguar internal user ====
 +
// todo: complete this sec
...  
...  
Line 74: Line 71:
...
...
-
== Lean style CT2 data dictionary for Truck Dom ==
+
== Overview of CT2 objects ==
-
Type:
+
-
* A
+
-
* AN - alphanumeric
+
-
* N
+
-
* D - date
+
 +
//todo (Alex)
-
=== CT2 Field 1 ===
 
-
* ''Description/Notes:''
+
 
-
* ''Matching Lean Field:''
+
== Overview of CT2 objects vs Lean Objects ==
-
* ''Link to [[CT bo]]:''
+
 
-
* ''Type:''
+
//todo (Alex)
-
* ''Length:''
+
 
-
* ''Required?''
+
 
 +
== Overview of CT2 objects vs Descartes Objects ==
 +
 
 +
//todo (Denise)
 +
 
 +
 
 +
 
 +
 
 +
== Fields Dictionary ==
=== CTNum ===
=== CTNum ===
Line 95: Line 95:
* ''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!)
 +
* ''Matching Descartes Field:''
* ''Link to CT bo:'' [[CT#CT_Num]]
* ''Link to CT bo:'' [[CT#CT_Num]]
-
* ''Type:'' N
+
 
-
* ''Length:'' ?
+
-
* ''Required?'' N
+
== XML representation of Jaguar CT record using Jaguar names ==
== XML representation of Jaguar CT record using Jaguar names ==
Line 116: Line 115:
   </CommodTable>
   </CommodTable>
  </CT>
  </CT>
 +
 +
== Lean style CT2 data dictionary for Truck Dom ==
 +
Type:
 +
* A
 +
* AN - alphanumeric
 +
* N
 +
* D - date

Revision as of 16:23, 20 July 2010


Contents

Intro

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

Fields definitions

We need to identify on per fields basis:

  • CT2 fields to send to TMS
  • TMS fields to send to CT2
  • what additional fields to create/re-define in CT2
  • what additional fields to create/re-define in TMS
  • mapping of CT2 to TMS fields

CT2 Truck Dom fields as of July 2010

Shipper and Planner Fields

List below is from Cybertrax 2.1 Client (data dictionary)

# 1 CT fields

    * 1.1 PO Issued by
    * 1.2 Pick up Location
    * 1.3 Ship to Location
    * 1.4 Pick up Instructions
    * 1.5 Commodity Description
    * 1.6 Cargo Available
    * 1.7 Fields that Shipper can not edit
          o 1.7.1 Shipper
          o 1.7.2 Pick Up Trucker
          o 1.7.3 Delivery Trucker
          o 1.7.4 Estimated Pick up date
          o 1.7.5 Actual Pick up date
          o 1.7.6 Estimated Delivery date
          o 1.7.7 Actual Delivery date
          o 1.7.8 Last Update
          o 1.7.9 Last Update date time
          o 1.7.10 Routed Date
    * 1.8 Field related to Planners
          o 1.8.1 CT Authorization status
          o 1.8.2 Approved For Date
          o 1.8.3 Approved By
          o 1.8.4 Approved On
          o 1.8.5 Authorization Comment

# 2 Commodity fields

    * 2.1 P.O.
    * 2.2 SKU
    * 2.3 Quantity
    * 2.4 Item Description
    * 2.5 Number of Plts
    * 2.6 Pkgs on Plts
    * 2.7 Loose Pkgs
    * 2.8 GW
    * 2.9 GW Unit
    * 2.10 Haz/Non-Haz
    * 2.11 Stackable
    * 2.12 Piece price
    * 2.13 Total Value

Additional fields for Truck Dom available for Jaguar internal user

// todo: complete this sec ...

#Consol Warehouse

...

Overview of CT2 objects

//todo (Alex)


Overview of CT2 objects vs Lean Objects

//todo (Alex)


Overview of CT2 objects vs Descartes Objects

//todo (Denise)



Fields Dictionary

CTNum

  • Description/Notes: Unique id for the CT2 shipment
  • Matching Lean Field: ll#ScheduleNum? (but it is too smal - only 3 digits!)
  • Matching Descartes Field:
  • Link to CT bo: CT#CT_Num


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
Personal tools