Arden 110 Air

From UG

(Difference between revisions)
Jump to: navigation, search
(Load Number)
Line 86: Line 86:
* '''notes:''' TBC group case  (internally only?)
* '''notes:''' TBC group case  (internally only?)
** per Arden - info including address (city, state, zip and county code)
** per Arden - info including address (city, state, zip and county code)
-
** per Jaguar - in case of groups map to CT with a smallest number in the group
 
=== Consignee Info ===
=== Consignee Info ===
Line 95: Line 94:
* '''notes:''' TBC group case (internally only?)
* '''notes:''' TBC group case (internally only?)
** Per Arden - includes address (city, state, zip and county code)
** Per Arden - includes address (city, state, zip and county code)
-
** per Jaguar - in case of groups map to CT with a smallest number in the group
 
=== Port of Entry ===
=== Port of Entry ===
Line 104: Line 102:
* '''notes:'''  
* '''notes:'''  
** Per Arden - only required air / ocean int. shipments
** Per Arden - only required air / ocean int. shipments
-
** per Jaguar - in case of groups map to CT with a smallest number in the group
 
=== Port of Departure ===
=== Port of Departure ===
Line 113: Line 110:
* '''notes:'''  
* '''notes:'''  
** Per Arden - only required air / ocean int. shipments
** Per Arden - only required air / ocean int. shipments
-
** per Jaguar - in case of groups map to CT with a smallest number in the group
 
=== Delivery Date ===
=== Delivery Date ===
Line 121: Line 117:
* '''EDI:'''
* '''EDI:'''
* '''notes:''' TBC (estimated is OK? destination door date and not port, OK?)
* '''notes:''' TBC (estimated is OK? destination door date and not port, OK?)
-
** per Jaguar - in case of groups map to CT latest delivered in the group
 
=== Ship Date ===
=== Ship Date ===
Line 129: Line 124:
* '''EDI:'''  
* '''EDI:'''  
* '''notes:''' TBC (Origin Airport is OK or need Origin Door date?)
* '''notes:''' TBC (Origin Airport is OK or need Origin Door date?)
-
** per Jaguar - in case of groups map to CT latest departed number in the group
 
=== Invoice Date ===
=== Invoice Date ===
Line 144: Line 138:
* '''EDI:'''
* '''EDI:'''
* '''notes:''' TBC if need to include loose as well into count
* '''notes:''' TBC if need to include loose as well into count
-
**
 
=== Total Weight ===
=== Total Weight ===
Line 156: Line 149:
* '''item#''' o
* '''item#''' o
-
* '''map:'''
+
* '''map:''' [[#CT#Chargeable Weight]]
* '''EDI:'''
* '''EDI:'''
* '''notes:''' TBC
* '''notes:''' TBC

Revision as of 06:59, 2 September 2013


Contents

Intro

This wiki defines fields required for EDI transmission of Air (110) Sales Invoices from JaguarFreight (3PL) to Elizabeth Arden (Client) through Data2Logistics (EDI partner).

Each section corresponds to one field from Required List Of Fields Jaguar received from Arden through Data2Logistics at the beginning of the project. This list can be found in section #Original Ardens List at the end of this wiki.

Format

For each field below Jaguar added the following information - see below.

Item represents item# on original Arden's list.

Map provides info about internal mapping into CT2 fields.

EDI represents relevant EDI protocol info (segment, element, required or not, format, etc).

Notes supply some additional in most cases business analysis related info. Fields that are self explanatory and well understood contain no notes.

Tags

Each field could be tagged with these values:

  • UNUSED - if it will not be used for some reason. See "notes" section for reasons.
  • TBC - if any aspect of use of this field is yet To Be Confirmed

Credit Notes vs Invoices

Credit Notes will be transmitted with the same set of fields as invoices. Special EDI element will be passed to distinguish between Invoice and Credit Note.

Group Logic

In case Invoice is issued against the group of CTs (GRP) apply same old logic to fields that we have had for paper (pdf) based invoices.

Original Fields

Ultimate Consignee

  • item # a
  • map: #Consignee
  • EDI:
  • notes: UNUSED, TBC
    • Per Arden - must be captured for International Shipments.
    • Per D2L - this is in the event of a stop off scenario. Otherwise this is just the consignee.
    • Per Jaguar - based on above we use #Consignee Info instead

Invoice Number

Bill Of Lading Number

  • item # c
  • map: CT#HAWB
  • EDI:
  • notes: TBC
    • per Jaguar - for Air we pass HAWB, which in most cases will be a CT#

Load Number

  • item# d
  • map: GRP#CT List
  • EDI:
  • notes: TBC
    • per Arden - required for inbound only.
    • Per Jaguar - we suggest to pass list of CTs against which this invoice is issued. Alternative is to pass group number (GRP#) that corresponds to that group. If it is an invoice for one CT then pass that one CT#. Suggest to pass for all transport modes and all types of moves.

Shipper Acct Number

  • item# e
  • map:
  • EDI:
  • notes: UNUSED, TBC
    • Per Arden - only required for small package carriers.
    • Per Jaguar - this is irrelevant to this project

Shipper Info

  • item# f
  • map: CT#Shipper and CT#Shipper Address
  • EDI:
  • notes: TBC group case (internally only?)
    • per Arden - info including address (city, state, zip and county code)

Consignee Info

  • item# g
  • map: CT#Consignee and CT#Consignee Address
  • EDI:
  • notes: TBC group case (internally only?)
    • Per Arden - includes address (city, state, zip and county code)

Port of Entry

Port of Departure

Delivery Date

Ship Date

Invoice Date

Total # of pieces

  • item# m
  • map: Commodity#plts
  • EDI:
  • notes: TBC if need to include loose as well into count

Total Weight

Billed Weight

Mileage

  • item# p
  • map:
  • EDI:
  • notes: UNUSED, TBC
    • Per D2L - this should be included in the L7:11 field for both Ocean and Air when available.
    • Per Jaguar - we do not have this information available now in our system. Since it is optional we can include it into the future releases.

Movement Type

  • item# q
  • map: CT#Transport Mode Type
  • EDI:
  • notes: TBC
    • Per Arden - this is mode and any expedited options.
    • Per D2L(Brandon) - this is referencing any special service levels – Examples – 1 day Air, 2 day air, air priority, etc.
    • Per Jaguar - best match for this requirement is our Transport Mode Type field. It has 3 options: Air, Ocean, Truck.

Container Size

(20, 40, 40HC, LCL) (only required air / ocean int. shipments)

  • item# r
  • map:
  • EDI:
  • notes: TBC

Terms / Incoterms

  • item# s
  • map:
  • EDI:
  • notes:

Carrier Name

  • item# t
  • map:
  • EDI:
  • notes:

Pro#

  • item# u
  • map:
  • EDI:
  • notes: UNUSED for Air and Ocean, TBC
    • Per D2L - should be included in a N9:03 field with a ‘PO’ qualifier in the N9:02 field.
    • Per Jaguar - we do not have this info in our system for Air/Ocean

Freight Cost

  • item# v
  • map:
  • EDI:
  • notes: TBC
    • see #Table Of Charges Fields section.
    • Per D2L - these can be the codes from your system but we require a list of these codes and their definitions to define them within our system.

Accessorial costs

Additional Fields

Invoice Amount

  • Map: SI#Total Invoice
  • EDI spec:
  • Notes: From Jaguar - this field is obviously required on invoice but was missing from Original Fields List so we added it.

Invoice Currency

  • Map: SI#Total Invoice Currency
  • EDI spec:
  • Notes: From Jaguar - this field is obviously required on invoice but was missing from Original Fields List so we added it.

Invoice Bill To Company Name

  • Map: SI#Bill To
  • EDI spec: N102; AN; 1/60; use with N101=BT
  • Notes: From Jaguar - this was one of the key fields on pdf version of Jaguar invoices to Arden so we added it to EDI version as well.

Invoice Bill To Address

  • Map: SI#Bill To Address
  • EDI spec:
  • Notes: From Jaguar - this was one of the key fields on pdf version of Jaguar invoices to Arden so we added it to EDI version as well.

Table Of Charges Fields

This corresponds to the following two Items on the #Original Fields List:

  • v. Freight Cost
  • w. Accessorial costs

To cover information above we usually has been sending to Arden in the past (in pdf form) these three pieces of information for each type of cost (a.k.a. charge) in one set:

Note that the number of sets (table lines) differ from invoice to invoice.

Please also note that Data2Logistics will be doing translation of #Charge Code into Charge Description for Arden based on mapping table that we provided.

Charge Code

Charge Amount

Charge Currency

Future Fields

Invoice Comments

Misc

Original Ardens List

  • a. Ultimate Consignee must be captured for International Shipments
  • b. Invoice Number
  • c. Bill of Lading number
  • d. LOAD NUMBER (required for inbound only)
  • e. Shipper Acct # (only required for small package carriers)
  • f. Shipper info including address (city, state, zip and county code)
  • g. Consignee Info including address (city, state, zip and county code)
  • h. Port of Entry (only required air / ocean int. shipments)
  • i. Port of Departure (only required air / ocean int. shipments)
  • j. Delivery Date
  • k. Ship Date
  • l. Invoice Date
  • m. Total # of pieces
  • n. Total Weight
  • o. Billed Weight
  • p. Mileage
  • q. Movement Type (Mode and any expedited options)
  • r. Container Size (20, 40, 40HC, LCL) (only required air / ocean int. shipments)
  • s. Terms / Incoterms
  • t. Carrier Name
  • u. Pro#
  • v. Freight Cost
  • w. Accessorial costs
Personal tools