Cybertrax 2.1 Client (data dictionary)

From UG

Revision as of 17:59, 22 June 2010 by Alex (Talk | contribs)
Jump to: navigation, search


Contents

CT fields

PO Issued by

NEW FIELD!


Pick up Location

a.k.a. CT#Export_Pick_Up

  • Meaning: This is the location of where the goods are actually located and shipping from.
  • Standard Long Label: Export Pick Up
  • Standard Short Label: Exp Pick Up
  • Other Labels in use:
  • Format/type: This field contains Company-City-Note
  • Min/max: [TBD]
  • Possible Values: [TBD]
  • Widget: searchbox
  • Default value:
    • Internal: blank
    • Shipper: "Copy from Shipper:" is checked (Yes) and "Pick up Location" is filled from "Shipper"
  • Required field?
    • Internal: N
    • Shipper: Y
  • User Read Access: all
  • User Write Access: internal, shipper unless Cybertrax_2.1_Client_(requirements)#What_CTs_Shipper_may_edit_RULE is true
  • Mode Of Transport: All


Ship to Location

a.k.a. CT#Delivery To

  • Meaning: This is the location of where the goods are shipping to.
  • Standard Long Label: Delivery To
  • Standard Short Label: Delivery To
  • Other Labels in use:
  • Format/type: This field contains Company-City-Note
  • Min/max: [TBD]
  • Possible Values: [TBD]
  • Widget: searchbox
  • Default value: blank
  • Required field?
    • Internal: N
    • Shipper: Y (NOTE: Ship To location from portal should map to Delivery To(T5) on Internal App as well as and Consignee (T2) field on the Internal App)
  • User Read Access: all
  • User Write Access: internal, shipper unless Cybertrax_2.1_Client_(requirements)#What_CTs_Shipper_may_edit_RULE is true
  • Mode Of Transport: All


Pick up Instructions

a.k.a. CT#Pick Up Comments


Commodity Description

a.k.a. CT#Commodity Description


Cargo Available

a.k.a. CT#Cargo Available


Commodity fields

P.O.

a.k.a. Commodity#PO

  • Meaning: This is the purchase order number for the product shipping.
  • Standard Long Label: PO #
  • Standard Short Label: PO #
  • Other Labels in use:
  • Format/type: Alphanumeric
  • Min/max: from 0 to 30 chars
  • Possible Values: TBD
  • Widget: Textbox
  • Default value: blank
  • Required field?
    • Internal: N
    • Shipper: Y
  • User Read Access: client, shipper, planner, internal
  • User Write Access: internal, shipper
  • Mode Of Transport: All


SKU

a.k.a. Commodity#SKU

  • Meaning: This is the sku number of the product shipping.
  • Standard Long Label: Sku #
  • Standard Short Label: Sku #
  • Other Labels in use:
  • Format/type: Alphanumeric
  • Min/max: from 0 to 30 chars
  • Possible Values: TBD
  • Widget: Textbox
  • Default value: blank
  • Required field?
    • Internal: N
    • Shipper: Y
  • User Read Access: client, planner, shipper, internal
  • User Write Access: internal, shipper
  • Mode Of Transport: All


Quantity

a.k.a. Commodity#Qty

  • Meaning: These are the actual number of pieces for the product shipping.
  • Standard Long Label: Quantity
  • Standard Short Label: Qty #
  • Other Labels in use:
  • Format/type: Positive Integer
  • Min/max: from 0 to 9999999999 digits
  • Possible Values: TBD
  • Widget: Textbox
  • Default value: 0
  • Required field?
    • Internal: N
    • Shipper: value must be > 0
  • User Read Access: client, planner, shipper, internal
  • User Write Access: internal, shipper
  • Mode Of Transport: All


Item Description

a.k.a. Commodity#Description

  • Meaning: This is the description of the PO and SKU that is shipping.
  • Standard Long Label: Commodity Line 1
  • Standard Short Label: Com Ln1
  • Other Labels in use:
  • Format/type: Alphanumeric
  • Min/max: from 0 to 60 chars
  • Possible Values: TBD
  • Widget: Textbox
  • Default value: blank
  • Required field?
    • internal: N
    • shipper: Y
  • User Read Access: client, planner, shipper, internal
  • User Write Access: internal, shipper
  • Mode Of Transport: All


Number of Plts

a.k.a. Commodity#Plts


Pkgs on Plts

a.k.a. Commodity#Pkgs On Plts


Loose Pkgs

a.k.a. Commodity#Loose Pkgs


GW

a.k.a. Commodity#Gross Lb


Total Value
  • Meaning: This is the total value of the unit piece price multiplied by the quantity of each PO/SKU that is shipping.
  • Default value: Blank
  • Required field? Y
  • Format/Datatype: Datatypes#ascii
Haz/Non-Haz

a.k.a. CT#Hazardous Yes No


  • Meaning: This is to advise if the product shipping is hazardous or not.
  • Location: Gen Tab
  • Mode Of Transport: All but Truck modes
  • Standard Long Label: Hazardous Yes No
  • Standard Short Label: Haz Y N
  • Other Labels in use:
  • Format/type: Radio option [Yes][No]
  • Min/max: n/a
  • Possible Values: Yes, No
  • Widget: radiogroup
  • Default value: No
  • Required field? N
  • User Read Access: client
  • User Write Access: internal


Stackable

  • Meaning: This is to advise if the pallets for the product shipping are stackable or not. This is a new CT2 field.
  • Default value: Yes
  • Required field? Y
  • Format/Datatype: Listbox option [Yes][No]

Piece price

  • Meaning: This is the unit price of each piece piece shipping for a PO/SKU. This is a new CT2 field.
  • Default value: Blank
  • Required field? Y
  • Format/Datatype: Currency - USD

Planner role fields

CT Authorization status

  • Meaning: It allows a planner to set a status (approve, reject, or hold) to any shipments created by a supplier.
  • Default value: Blank
  • Required field? Y
  • Format/Datatype: Listbox with option to choose one of three choices

Approved For Date

  • "Approved for" date feature acts as a ‘hold to ship date’ – meaning hold until (IE 05/24/10) before scheduling the pick up.
  • Meaning: It allows a planner to place a shipment on hold until a particular date. System will automatically approve on the date selected at 12:01 AM. This field can be updated anytime until 3 days before the date selected
  • Default value: Blank
  • Required field? N
  • Format/Datatype: Datebox with a clear button

Approved By

Approved On

  • (with name of person who approved, including the date & time)
  • Meaning: Shipment was approved for transportation by whom and when
  • Default value: Read only - First and last name of the approval user(planner) and date timestamps with (EST) calculated time zone
  • Required field? Y - when status is approved
  • Format/Datatype:Read only Textarea

Hold Info

  • Name of person who placed on hold, including the date & time)
  • Meaning: Shipment was placed on hold for transportation by whom and when. It also allows a planner to come back to update the status to approve, reject, or hold with a date. This field will record any updates made by a planner in the history log and will display the last update recorded on the shipment record.
  • Default value: Read only - First and last name of the approval user(planner) and date timestamps with (EST) calculated time zone
  • Required field? Y - when status is placed on hold
  • Format/Datatype: Read only Textarea with history log button
  • Additional Info: Comment pop-up window will appear once a planner clicks Apply

Rejected Info

  • Name of person who rejected it, including the date & time)
  • Meaning: Shipment was rejected for transportation by whom and when
  • Default value: Read only - First and last name of the approval user(planner) and date timestamps with (EST) calculated time zone
  • Required field? Y - when status is rejected
  • Format/Datatype: Read only Textarea
  • Additional Info: Comment pop-up window will appear once a planner clicks Apply

Comment Info

  • Reason for placing a shipment on hold or rejecting a shipment
  • Meaning: It allows a planner to note to the supplier why they are holding or rejecting a shipment.
  • Default value: Blank
  • Required field? N
  • Format/Datatape: textarea
  • Addition Info: It is a field on a shipment record that records status, reason, by whom and when. Last updated info will be on the top.

History Log Info

  • Keeps a record of all status events
  • Meaning: It is a field of recorded status events shown on a shipment record.
  • Default value: blank
  • Required field? Y - when there is an updated info
  • Format/Datatype: a button to a history log screen
  • Additional Info: Event status, name of the planner, and date and timestamps.
  • Example: 9-Jun-2010 Put on hold Alex Doe


Read only properties of Planner role fields

  • [a] ...
Retrieved from "https://wiki.jaguarfreight.com/Cybertrax_2.1_Client_(data_dictionary)"
Personal tools