EDI ASN Export (Freeway Commerce format)

DOWNLOAD SAMPLE FILE: ASN_Export.txt

Exported filename is ASN_Export.txt, despite its extension it is a CSV file. In the tables below, remarks relating to Infoplex are in blue, whereas as those relating to Freeway’s specifications are in black or other colours.

The ASN Export format can contain up to four record types:

#Record TypeNote
1StructureFixed Length. 1 record per file.
2HeaderCSV – Uses Header ID from structure record. 1 record per Shipment (Invoice in TAS).
3Shipping UnitCSV – Always “SUNIT”. 1 record per Shipping Unit (per Invoice in TAS).
4Detail (Product)CSV – Uses Detail ID from structure record. 1 or more records per Shipping Unit.

Structure Record

1 per file. The first record in the file will be this string:

CSV DD/MM/YY hh:mm HEAD DTL VAT TRAIL NN

Header Record

Mandatory, one per Invoice

FieldLabelData TypeMax SizeRequired?Remarks
1Record IDA5YAs defined in structure record, i.e. “HEAD”
2Company CodeA20OAs set up in MultiTAS Central Information “Company Representation Code”. If specified, MUST match “Company Code” in Commerce Centre. Dependency: Header (1).
3Company ANA NumberN13OAs set up in MultiTAS Central Information. If specified, MUST match an EDI Detail (Code) for a Company object in Commerce Centre. Dependency: Header (1).
4Partner Account CodeA17CTAS Customer Code. Internal account code for “Head Office” (Ledger Account, Statement Account, Bill-To). Dependency: Header (2).
5Partner ANA NumberN13CNot used. [If specified, MUST match an EDI Detail (Code) for a Partner object in Commerce Centre. Dependency: Header (2)].
6Third Party Deliver To Account CodeA17CNot used. [(see additional notes). Dependency: Header (3)].
7Third Party Deliver To ANA NumberN13CNot used. [(see additional notes). Dependency: Header (3)].
8Third Party Deliver To Partner ReferenceA17CNot used. [(see additional notes). Dependency: He]ader (3)].
9Partner Deliver To Account CodeA17CTAS Customer Code (again, because it is taken also to be the code for the central distribution depot). [(see additional notes). Dependency: Header (4)].
10Partner Deliver To ANA NumberN13CNot used. [(see additional notes). Dependency: Header (4)].
11Partner Deliver To Partner ReferenceA17CNot used. [(see additional notes). Dependency: Header (4)].
12ASN NumberA30YTAS Invoice Number (maybe DEL desc as per Invoice) Same as delivery note number for entire delivery
13Booking ReferenceA20PNot used. [The Booking reference as assigned by the receiving party (if applicable)]
14Delivery DateD10YTAS Invoice Date. Formatted according to rules in structure record
15Delivery TimeT8ONot used. [Formatted according to rules in structure record]
16Original (Partner) Order NumberA30OSales Order Customer Ref in TAS. Required if not specified for each line. Dependency: General (2).
17Original Order DateD10OSales Order Date in TAS If Order Number specified for header, then based on recipient requirements. Dependency: General (2).
18Total Shipping UnitsN4YSet to 1. A count of the number of “SUNIT” records for the ASN
19Total Delivered QuantityN7OSum of all quantity amounts for all detail records.
20File Generation Number (FLGN)N4ONot used. [Sequential counter for ASN submitted from this company to this partner. Dependency: Header (5).
21File Version Number (FLVN)N4ONot used. [Normally 1, unless an FLGN is re-submitted. Then sequential within FLGN. Dependency: Header (5)].
22File Creation DateD8ONot used. [Formatted according to rules in structure record. Dependency: Header (5)].
23ASN Type IndicatorA7PNot used. [“FULL” or “PLANNED” (currently for JS ONLY)]
24Reference Text (1)A30RESERVED
25Reference Text (2)A30RESERVED
26Reference Text (3)A30RESERVED
27Reference Date (1)D10RESERVED
28Reference Date (2)D10RESERVED
29Reference Date (3)D10RESERVED

Shipping Unit Record

Currently using only 1 per Invoice.

At least 1 per ASN, can be repeated for each shipping unit. Details of products for shipping unit MUST follow record, before any repeat.

FieldLabelData TypeMax SizeRequired?Remarks
1Record IDA5YFixed value “SUNIT”.
2Unit TypeA15YSet to “PALLET”. [Can be “DELIVERY”, “PALLET”, “BOX”, “RAIL”, “CAGE” (other to be defined as required). Dependency: Shipping Unit (1).]
3Partner Deliver To Account CodeA17CMapped Customer Delivery Address Code, if it exists, otherwise the TAS Customer Delivery Address Code for the invoice, being the ultimate store destination of the goods. (see additional notes). Dependency: Shipping Unit (2).
4Partner Deliver To ANA NumberN13CNot used. [(see additional notes). Dependency: Shipping Unit (2)].
5Partner Deliver To Partner ReferenceA17CSales Order Customer Reference in TAS (see additional notes). Dependency: Shipping Unit (2).
6Unit Dimensions – HeightN7PNot used. [In millimetres]
7Unit Dimensions – WidthN7PNot used. [In millimetres]
8Unit Dimensions – DepthN7PNot used. [In millimetres]
9Unit Dimensions – Total WeightN7PNot used. [In kilograms, includes weight of actual shipping unit]
10Unit Dimensions – Goods WeightN7PIn kilograms, EXCLUDES weight of actual shipping unit (I.e. total weight of product)
11Shipping Unit Reference TypeA4CSet to “SSCC”. [Can be “SSCC” or “EAN”]
12Shipping Unit Reference NumberN30CSet to Invoice Number. [Either the SSCC or EAN reference number for this shipping unit.]
13Delivery Note ReferenceA17ONot used. [(see additional notes). Dependency: Shipping Unit (3).]
14Original (Partner) Order NumberA30ONot used. [Required if not specified for entire ASN at header level. . Dependency: General (2).]
15Original Order DateD10OSales Order Date in TAS. [If Order Number specified for shipping, then based on recipient requirements. Dependency: General (2)].
16Total Delivered QuantityN10OSum of all quantity amounts for all detail records for this shipping unit.
17Reference Text (1)A30RESERVED
18Reference Text (2)A30RESERVED
19Reference Text (3)A30RESERVED
20Reference Date (1)D10RESERVED
21Reference Date (2)D10RESERVED
22Reference Date (3)D10RESERVED

Product/Detail Record

Can be repeated for mixed units (if allowable by recipient)

FieldLabelData TypeMax SizeRequired?Remarks
1Record IDA5YAs defined in structure record, i.e. “DTL”
2Product/Stock Group/CategoryA20OIf specified, will be used in initial search. Dependency: Detail (1)(a).
3Product/Stock CodeA30CInternal (i.e. Company) Reference for the stock item. Dependency: Detail (1).
4Traded Unit DUN Code (UDEX)N14CIf not blank TAS ANA Code trimmed or padded with spaces to 14 characters 14 digit barcode reference for outer case. Dependency: Detail (1).
5Traded Unit EAN CodeN13CIf not blank TAS ANA Code trimmed or padded with spaces to 13 characters. [13 digit barcode reference for outer case (also referred to as the outer case code). Dependency: Detail (1)].
6Recipient Item ReferenceA17CMapped product code if available. [Reference for product as assigned by recipient (i.e originator of order). Dependency: Detail (1).]
7Pack SizeN5CNumber of retail units in outer case. Dependency: Detail (2).
8Measure DescriptionA6Ce.g. KG, LITRE, etc. Describes the shipping/pricing unit for this item. Dependency: Detail (2).
9Order QuantityN10CNumber of cases from original order (only required if recipient requires this data). Dependency: Detail (3).
10Order MeasureN10COriginal quantity of measure descriptor ordered (e.g. order for 6.2KG, this field equals 6.2). Dependency: Detail (3).
11Delivered QuantityN10CNumber of cases delivered on this shipping unit for this item. . Dependency: Detail (4).
12Delivered MeasureN10CQuantity of measure description delivered on thi shipping unit for this item. Dependency: D (4).
13Batch ReferenceA20ONot used. [Unique reference for batched or rotated items]
14Batch DateD10ONot used. [Formatted according to rules in structure record]
15Best Before (Expiry) DateD10ONot used. [Formatted according to rules in structure record]
16Description Line 1A35YFirst line of product description
17Description Line 2A35ONot used. [Second line of product description if required.]
18Short Delivery ReasonA30ONot used. [Code for the reason why short delivered, must conform to code list 203]
19Back Order QuantityA30ONumber of Cases Back Ordered
20Original (Partner) Order NumberA30OSkip because specified at Header level. Required if not specified for entire ASN at header level or for current Shipping Unit.
21Original Order DateD10OSkip because specified at Header level. If Order Number at Line Level, then as per Partner Requirements.
22Reference Date (2)D10RESERVED
23Reference Date (3)D10RESERVED
24Original Line NumberN10PNot used. [Original Line Number specified on the Order]