Data Dictionary for EDI to TMS

From UG

(Difference between revisions)
Jump to: navigation, search
(→Goals)
(→Goals)
Line 12: Line 12:
* 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
** include into xml messaging what is required
-
** block user from corrupting data
+
** 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

Revision as of 20:36, 10 August 2010


Contents

Intro

This document describes objects, fields, related XML definitions, etc 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
    • 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

Descartes Objects and fields

Shipment obj

XML example: 

<DocShipment ShipmentNo="3161007" LoadNo="3161007" MessagePurpose="1005" CarrierCode="RDWY"
 EarliestAvailDate="2010-03-11T08:00:00" LatestAvailDate="2010-03-11T16:00:00" TotalWgt="98"
 WgtUOM="200">

Object:

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

Object's fields:

Shipment No:

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

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

...

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