Arden 110 Air

From UG

Contents 1 Intro 1.1 Format 1.2 Tags 1.3 Credit Notes vs Invoices 1.4 Group Logic 2 Original Fields 2.1 Ultimate Consignee 2.2 Invoice Number 2.3 Bill Of Lading Number 2.4 Load Number 2.5 Shipper Acct Number 2.6 Shipper Info 2.7 Consignee Info 2.8 Port of Entry 2.9 Port of Departure 2.10 Delivery Date 2.11 Ship Date 2.12 Invoice Date 2.13 Total # of pieces 2.14 Total Weight 2.15 Billed Weight 2.16 Mileage 2.17 Movement Type 2.18 Container Size 2.19 Terms / Incoterms 2.20 Carrier Name 2.21 Pro# 2.22 Freight Cost 2.23 Accessorial costs 3 Additional Fields 3.1 Invoice Amount 3.2 Invoice Currency 3.3 Invoice Bill To Company Name 3.4 Invoice Bill To Address 3.5 Table Of Charges Fields 3.5.1 Charge Code 3.5.2 Charge Amount 3.5.3 Charge Currency 4 Future Fields 4.1 Invoice Comments 4.2 File Ref Num 4.3 Notify Party 4.4 PO numbers 4.5 Airport of Departure 4.6 Airport Of Destination 4.7 Customer ref 4.8 Flight number 4.9 Volume 5 Misc 5.1 Original Ardens List 6 See Also

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).

There are 3 lists of fields here:

• #Original Fields - 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.

• #Additional Fields - fields that Jaguar added to above list for the first release

• #Future List - possible additional options

Format

For each field 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. To distinguish between Invoice and Credit Note:

• there is indicator in B3 segment

• nothing for Sales Invoice
• CA (Cancelled Bill) for Credit Note

• and also "-" sign before amount

Group Logic

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

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

• item # b
• map: SI#Invoice Number
• EDI: B302

Bill Of Lading Number

• item # c
• map: CT#HAWB
• EDI: L502
• 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: B303
• 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.
  • Brandon - what is a good segment for this?
  • Dawn - will it be used?

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: N1, N3, N4 (SH)
• 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: N1, N3, N4 (CN)
• notes: TBC group case (internally only?)
  • Per Arden - includes address (city, state, zip and county code)

Port of Entry

• item# h
• map: CT#Airport Of Destination
• EDI:
• notes: R15
  • Per Arden - only required air / ocean int. shipments

Port of Departure

• item# i
• map: CT#Airport Of Departure
• EDI: R13
• notes:
  • Per Arden - only required air / ocean int. shipments

Delivery Date

• item# j
• map: CT#Estimated Delivery Date
• EDI: B309
• notes: TBC (estimated is OK? destination door date and not port, OK?)

Ship Date

• item# k
• map: CT#Airport Of Departure Actual Date
• EDI:
• notes: TBC (Origin Airport is OK or need Origin Door date?)

Invoice Date

• item# l
• map: SI#Issuing Date
• EDI: B36
• notes:

Total # of pieces

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

Total Weight

• item# n
• map: Commodity#Grand Total: Gross Kg
• EDI: L0_4, L3_1
• notes: TBC

Billed Weight

• item# o
• map: CT#Chargeable Weight
• EDI:
• notes: TBC

Mileage

• item# p
• map:
• EDI: L0_4, L3_1
• 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: GS_3 (ELARUS1,ELARUS2, ELARUS3)
• 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

• item# r
• map:
• EDI:
• notes: UNUSED, TBC
  • per Arden: (20, 40, 40HC, LCL) (only required air / ocean int. shipments)
  • per Jaguar - we do not have this info for Air in the system

Terms / Incoterms

• item# s
• map: CT#Shipping Terms
• EDI: B314
• notes: TBD

Carrier Name

• item# t
• map: CT#Airline
• EDI: R104
• 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: B3_7, L3_5
• 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

• item# w
• map:
• EDI: L1_4
• notes: TBC
  • see #Table Of Charges Fields section

Additional Fields

Invoice Amount

• Map: SI#Total Invoice
• EDI spec: B3_7, L3_5
• 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: C3_1
• 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: N3, N4 (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.

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:

• #Charge Code
• #Charge Amount
• #Charge Currency

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

• Map: SI#CC
• EDI spec: L1_8

Charge Amount

• Map: SI#CC Amount
• EDI spec: L1_4

Charge Currency

• Map: SI#CC Currency
• EDI spec: L1_20

Future Fields

Many of these fields were inspired by pdf version of invoice.

Invoice Comments

File Ref Num

Notify Party

PO numbers

Airport of Departure

Airport Of Destination

Customer ref

Flight number

Volume

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

See Also

• Sales Invoices EDI - master wiki for this project