Data Dictionary for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(→History)
 
(22 intermediate revisions not shown)
Line 1: Line 1:
[[Category: EDI to TMS]]
[[Category: EDI to TMS]]
 +
 +
== Mantis ==
 +
 +
'''0002229''': [EDI to TMS] (Preliminary) Create data dictionary / TMS to CT2 fields mapping table
== Intro ==
== Intro ==
-
This document describes fields that will participate in integration with TMS.
+
This document describes objects, fields, related XML definitions, etc that will participate in integration with TMS.
== Goals ==
== Goals ==
Line 10: Line 14:
* CT2 fields to send to TMS for each IP
* CT2 fields to send to TMS for each IP
* TMS fields to send to CT2 for each IP
* TMS fields to send to CT2 for each IP
-
* what fields to be updated in CT2 and what in TMS
+
* what fields to be updated in CT2 and what in TMS  
 +
** include into xml messaging what is required
 +
** if field is present in both systems then .... block user from corrupting data
* 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
 +
== Data Dictionary ==
 +
See xls in http://ct.jaguarfreight.com/mantis/view.php?id=2229
 +
== History ==
-
== Descartes Objects and fields ==
+
=== 0002347: [EDI to TMS] (Preliminary) CT to XML mapping ===
-
 
+
-
=== 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)]]
+
-
<pre>
+
-
# 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
+
-
</pre>
+
-
+
-
=== Additional fields for Truck Dom available for Jaguar internal user ===
+
-
 
+
-
// todo: complete this sec
+
-
...
+
-
 
+
-
[[#Consol Warehouse]]
+
-
...
+
=== 0002693: [EDI to TMS] (Shipment_Import) Change: Pass Loose Pkgs on Shipment Import as 1 line item ===

Current revision as of 22:04, 14 January 2011


Contents

[edit] Mantis

0002229: [EDI to TMS] (Preliminary) Create data dictionary / TMS to CT2 fields mapping table

[edit] Intro

This document describes objects, fields, related XML definitions, etc that will participate in integration with TMS.

[edit] 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
    • include into xml messaging what is required
    • if field is present in both systems then .... block user from corrupting data
  • what additional fields to create/re-define in CT2
  • what additional fields to create/re-define in TMS
  • mapping of CT2 to TMS fields

[edit] Data Dictionary

See xls in http://ct.jaguarfreight.com/mantis/view.php?id=2229

[edit] History

[edit] 0002347: [EDI to TMS] (Preliminary) CT to XML mapping

[edit] 0002693: [EDI to TMS] (Shipment_Import) Change: Pass Loose Pkgs on Shipment Import as 1 line item

Retrieved from "https://wiki.jaguarfreight.com/Data_Dictionary_for_EDI_to_TMS"
Personal tools