Data Dictionary for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(Fields Dictionary)
Line 5: Line 5:
This document describes fields that will participate in integration with TMS.
This document describes fields that will participate in integration with TMS.
-
== Fields definitions ==
+
== Goals ==
We need to identify on per fields basis:
We need to identify on per fields basis:
-
* CT2 fields to send to TMS
+
* CT2 fields to send to TMS for each IP
-
* TMS fields to send to CT2
+
* TMS fields to send to CT2 for each IP
 +
* what fields to be updated in CT2 and what in TMS
* what additional fields to create/re-define in CT2
* what additional fields to create/re-define in CT2
* what additional fields to create/re-define in TMS
* what additional fields to create/re-define in TMS
* mapping of CT2 to TMS fields
* mapping of CT2 to TMS fields
-
=== CT2 Truck Dom fields as of July 2010 ===
 
-
==== Shipper and Planner Fields ====
+
 
 +
 
 +
== Descartes Objects and fields ==
 +
 
 +
=== Shipment obj ===
 +
 
 +
Object:
 +
 
 +
* ''Matching CT2 object name:'' CT
 +
* ''Descartes XML tag/attribute:'' '''DocShipment''' tag
 +
 
 +
Object's fields:
 +
 
 +
'''Shipment No:'''
 +
* ''Matching CT2 field:'' [[CT#CT_Num]]
 +
* ''Descartes XML tag/attribute:'' '''ShipmentNo''' attribute of '''DocShipment''' tag
 +
 
 +
==== Pick up Location obj ====
 +
 
 +
...
 +
 
 +
== 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>
 +
 
 +
== Types ==
 +
Type:
 +
* A
 +
* AN - alphanumeric
 +
* N
 +
* D - date
 +
 
 +
== CT2 Truck Dom fields ==
 +
 
 +
=== 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 62: Line 109:
</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
// todo: complete this sec
Line 70: Line 117:
...
...
-
 
-
== Overview of CT2 objects ==
 
-
 
-
//todo (Alex)
 
-
 
-
 
-
 
-
== Overview of CT2 objects vs Lean Objects ==
 
-
 
-
//todo (Alex)
 
-
 
-
 
-
== Overview of CT2 objects vs Descartes Objects ==
 
-
 
-
//todo (Denise)
 
-
 
-
 
-
 
-
 
-
== Descartes Objects and fields ==
 
-
 
-
=== Shipment obj ===
 
-
 
-
Object:
 
-
 
-
* ''Matching CT2 object name:'' CT
 
-
* ''Descartes XML tag/attribute:'' '''DocShipment''' tag
 
-
 
-
Object's fields:
 
-
 
-
'''Shipment No:'''
 
-
* ''Matching CT2 field:'' [[CT#CT_Num]]
 
-
* ''Descartes XML tag/attribute:'' '''ShipmentNo''' attribute of '''DocShipment''' tag
 
-
 
-
==== Pick up Location obj ====
 
-
 
-
...
 
-
 
-
== 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
 

Revision as of 21:26, 9 August 2010


Contents

Intro

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

Goals

We need to identify on per fields basis:

  • CT2 fields to send to TMS for each IP
  • TMS fields to send to CT2 for each IP
  • what fields to be updated in CT2 and what in TMS
  • what additional fields to create/re-define in CT2
  • what additional fields to create/re-define in TMS
  • mapping of CT2 to TMS fields



Descartes Objects and fields

Shipment obj

Object:

  • Matching CT2 object name: CT
  • Descartes XML tag/attribute: DocShipment tag

Object's fields:

Shipment No:

  • Matching CT2 field: CT#CT_Num
  • Descartes XML tag/attribute: ShipmentNo attribute of DocShipment tag

Pick up Location obj

...

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>

Types

Type:

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

CT2 Truck Dom fields

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

...

Personal tools