Unisource ASN Requirements

Transcription

1 Unisource ASN Requirements arch 2008 Page 1 of 23

2 UNISOURCE ASN REQUIREENTS LOGISTICS ASN REQUIREENTS... 3 ADVANCE SHIP NOTICE (ASN) (EDI 856) ADVANCE SHIP NOTICE (ASN) (EDI 856) REQUIREENTS.4/5 PALLET LABELING LICENSE PLATE NUBER (LPN) LABELS LOGISTICAL SHIPPING UNIT....6 IT ASN REQUIREENTS.. 7 SHIP NOTICE - TRANSACTION 856 REQUIREENTS DATA VALIDATION REQUIREENTS...9 APPENDIX A: CONTACTS APPENDIX B: EAN/UCC-128 LPN LABEL /12 APPENDIX C: Ship Notice Transaction APPENDIX D: Logistical Shipping unit & LPN (Visio) arch 2008 Page 2 of 23

3 Logistics ASN Requirements Advance Ship Notice (ASN) (EDI 856) The Advance Ship Notice (ASN or EDI 856) is a transaction used to confirm the configuration of a shipment of goods as well as additional information relating to the shipment. This transaction will describe the shipment at the Logistical Shipping Units level, and will include such information as lot numbers, pack dates, expiration dates, and net weight of catch weight items. Complete and accurate ASN s will ensure quick and efficient receipt of your products. The ASN is required to be received prior to shipment s arrival at the DC. It is recommended that the ASN be transmitted as the load is sealed at your dock. LPN label configurations will be tested prior to implementation. (see page 8) The ASN must accurately provide all required information about the incoming shipment. This information may include, but is not limited to the following ASN elements: arch 2008 Page 3 of 23

4 Advance Ship Notice (ASN) (EDI 856) Requirements Requirement Description Unique Shipment Identification Number Unique ASN number Unisource Purchase Order Number Unisource Purchase Order sent to the supplier. This appears at the header level. Unisource Purchase Order Line Number Item Sequence The sequence of line items on the ASN must be the exact line item indicator as the Purchase Order (850). Unisource Vendor number The number assigned to the Supplier by Unisource to represent the Supplier in Univis. Ship-From Address Supplier s Address. Ship To Information The physical address where the PO s are being shipped to. Unisource Product Code The UNISOURCE 6-digit alphanumeric number corresponding to the Supplier s item number assigned to the Supplier s item by UNISOURCE. Logistical Shipping Units Quantity See Appendix D An item may span multiple pallets, but the quantity should reflect the actual quantity per LPN per Logistical Shipping Units. Lot Number See Appendix D Lot# or batch# must be included on the pallet level ASN. If there are multiple lots on a pallet of product, multiple lot numbers must be provided in the ASN. anufacture Date See Appendix D If the product has a anufacture Date printed on the case or inner pack, it must be included on the ASN. arch 2008 Page 4 of 23

5 Expiration Date See Appendix D If the product has Expiration or Use By Date printed on the case or inner pack, it must be included on the ASN. All products must have 80% or more shelf life remaining at the time of receipt at the DC. Net Weight If the product is a catch weight item (sold by the pound) the net weight of the product on the pallet must be included in the ASN. arch 2008 Page 5 of 23

6 PALLET LABELING LOGISTICAL SHIPPING UNIT: Physical unit of same SKU (stock keeping unit) established for transport and storage of products where the largest quantity being a pallet and where there is a need for tracking and tracing individually by Qty, Lot ID, anufacturer date, Expiry date, etc in a supply chain using a LPN (Serial Shipping Container Code/SSCC). See Appendix D - Visio License Plate Number (LPN) Labels All Logistical Shipping Units (LSU) will be labeled with an SSCC-18 Serial Shipping Container Code encoded in the UCC/EAN-128 symbology. Bar code must be of scannable quality to be accepted. The data element requirements for each LPN can be found in Appendix B Each pallet of a single SKU will have 2 LPN Labels. When facing the front of the pallet (40 side), the LPN will be affixed underneath the stretch wrap to the TOP right hand corner of the front side and right side of the pallet as shown in the diagram below. Diagram 1: LPN Location on Pallet LPN (SSCC) 2 min 60 maximum LPN labels should be a minimum 6 height and 4 wide. A sample LPN label must be provided to National Logistics department for approval and prior to implementation. (see Appendix A for contact) Bar-coding standard can be found at the following site: arch 2008 Page 6 of 23

7 IT ASN Requirements SHIP NOTICE - TRANSACTION 856 REQUIREENTS Overview This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/anifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, and type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the content of a shipment to the receiver of the transaction set. The receiver of this transaction set can be any organization having an interest in the information about the contents of a shipment. The ship notice/manifest, often referred to as the ASN (Advance Ship Notice) is issued by the trading partner to let Unisource Canada know what products are included in the shipment leaving the trading partner s premises. The 856 must arrive at Unisource Canada a minimum of two hours before the shipment arrives the warehouse cannot receive the shipment if the ASN hasn t been received. Structure of the 856 The information for the ASN is organized into header information and five tables as outlined in the Data Segment List. The structure is hierarchical and designed to show relationships within a shipment, e.g., pallets on a truck, part numbers on the pallet, the cartons that parts are packed in, etc. Each table is a level in the hierarchy. Each table begins with an HL segment, value for each table as follows: arch 2008 Page 7 of 23

8 Table 1 - Shipment S to identify data related to the trading partner's whole shipment, such as bill of lading quantity, weight, ship to etc. Table 2 - Order O to identify data related to the trading partner's order and the Unisource Canada original purchase order Table 3- Item I to identify the products being shipped, quantities, packaging etc. Table 4- Package P to identify pallets/packages/boxes label. This level is mandatory Table 5 - Summary This table contains summary information. Every transaction set contains a summary table. Shipping License Plate Number (shipping container label number) Unisource Canada requires that you label your shipping containers with the Shipping License Plate serial number and provide that information in the 856 ASN that you send to us. The purpose of the SLP is to uniquely identify each shipping container (carton, group of cartons or pallet) packed by a supplier in a shipment. The container number indicated in the 856 must match the bar coded number on the shipping container. The SLP label is the physical link to the information sent electronically. Only similar items with similar properties (ex the same lot/batch number) can be packed under the same SLP. Labeling rules - one single item code (product code) may have assigned multiple LPN; - one LPN may contain only one single item code (product code) - one LPN is recommended to be used for multiple similar content packages/boxes within a skid; - every single skid will have 2 LPN s; Business Overview Unisource Canada will require 856 ASN's for all shipments being received at a Warehouse. It is the responsibility of the shipper to make certain the ASN arrives a minimum of two hours prior to the arrival of the truck at the DC, and that it is in a usable condition. arch 2008 Page 8 of 23

9 Business Processing The following guidelines will help avoid receiving problems, invoice matching issues, and possible delays to your payments. The ASN s need to be accurate. Unisource Canada systems are updated with this data and corrections are time-consuming and costly. erchandise cannot be received without an ASN. Please ensure that they arrive on time. Receiving data will be used to validate your invoice. Sending accurate data in your ASN will help eliminate delay in processing your invoice. Data Validation Requirements Suppliers must provide compliant information for all mandatory segments as per the specifications listed in this guide. The data contained in each field must be relevant to the accompanying qualifier. During the Set up and Testing phase suppliers will be provided with a snapshot of their data from Unisource Canada, Inc. to validate accuracy and update if necessary. If the data is found to be invalid or incomplete and the Supplier did not correct as per the requested updates in a timely manner, the Supplier is liable and may be charged for the expenses incurred by Unisource Canada, Inc. to fix any issue related to incorrect information. arch 2008 Page 9 of 23

10 Appendix A: Contacts For questions regarding the Logistics Electronics Requirements document, please contact the National Logistics Department at Unisource Canada, Inc. National Logistics Department Ray Hinksman, Phone: cell: ANAGER, LOGISTICS EDI Department Phone: arch 2008 Page 10 of 23

11 APPENDIX B: EAN/UCC-128 LPN LABEL 4 Width I J H K F G D 6 Height C E L A B arch 2008 Page 11 of 23

12 4 X6 LPN Data Elements Data Element Example Description A. Numeric Human Readable Bar Code Translation [00] The application identifier [00] must proceed the Licence Plate Number and must be included in parentheses B. Bar Code 30 mil 1 height EAN/UCC 128 symbology or LPN. 20 digits. Links to ASN. 1st 2 digits: Application identifier - always begins with 00. 3rd Extension Digit UCC anufacturer ID Shipping Container #:Unique number for LPN. Each LPN must consist of a different SC#. Check Digit UCC Standards (Uniform Code Council) calculates number. Text description of product C. Product Econosource 8.5 X 11 White Description D. VPC Vendors Product code printed on case E. Vendor Product Vendor system code code F. Ti/Hi 8-5 Vendor Pallet TiHi G. Quantity 5 Logistical shipping unit qty H. Postal code (420)L5T3R1 I. Vendor shipping Vendors shipping address address J. Ship to address 1475 Courtneypark dr Ship to address (may not be the final destination location) K. Carrier Carrier name, pro #, BOL # Carrier information Information L. Final 560 Hensall Circle Final destination address destination address. PO# Unisource PO # arch 2008 Page 12 of 23

13 APPENDIX C: Ship Notice Transaction 856 HEADER Segment ST-transaction set header BSN-beginning segment Required LINE DETAIL HL-Hierarchical level (Shipment Level) TD1-carrier details TD5-carrier details REF-reference REF-reference DT-date/time reference - Ship/delivery FOB-FOB related instructions N1-name Ship From name N3-address Ship From Address N4-geographic location Ship From Loc HL-Hierarchical level (Order Level) PRF-PO reference HL-Hierarchical level (Item Level) LIN-line item data SN1-item detail PO4 Item Physical detail PID-product/item description HL-Hierarchical level (Pack Level) SLN subline item detail REF- reference identification AN-arks and numbers DT-date/time reference (anufacture date) DT-date/time reference (Expire date) O O O O O SUARY CTT-transaction totals SE-transaction set trailer. arch 2008 Page 13 of 23

14 Legend: = andatory O = Optional * = Optional in the standard, but mandatory for Unisource Inc. Segment:ST Transaction set Header (ANDATORY) Ref. ID. Element name Format Size Transaction set identifier code ID 3/3 «856» Transaction set control number AN 4/9 Segment:BSN Beginning Segment Advance Ship Notice (ANDATORY) Identifying Numbers and Dates Transaction set purpose code ID 2/2 «00» =original «05» =change Shipment ID ID 2/30 Shipment identifier Date DT 6/8 Date shipment created Time DT C 4/8 Time hh:mm Segment:HL Hierarchical Level (Shipment Level) (ANDATORY) Identifying Level Structures ID number AN 2/2 ID number Parent ID number AN C 2/2 Parent ID number Hierarchical Level Code ID 1/2 Level Code Hierarchical Child Code ID C 1/1 Child Code arch 2008 Page 14 of 23

15 Segment: TD1 Carrier details (Quantity and Weight) (OPTIONAL) Packaging Code ID O 1/ Lading Quantity N0 O 1/ Commodity Code Qualifier ID O 1/ Commodity Code AN O 1/ Description AN O 1/ Weight Qualifier AN O 2/ Weight R2 O 1/ Unit of easure AN O 2/2 Segment: TD5 Carrier details (Routing Sequence) (OPTIONAL) Identification Code Qualifier ID O 1/ Identification code AN O 2/ Transportation method ID O 1/2 "H"=Customer pick-up ""=otor (common carrier) Routing AN O 1/35 Name (common carrier) Segment:REF Reference Number *(ANDATORY) To specify identifying numbers Reference Number Qualifier ID 2/2 «B» : Bill of Lading Number (shipment level) Reference Number AN 1/30 Specify identifying number arch 2008 Page 15 of 23

16 Segment:REF Reference Number *(ANDATORY) To specify identifying numbers Reference Number Qualifier ID 2/2 «VR» : Vendor Number (shipment level) Reference Number AN 1/30 Specify identifying number Segment: DT Date and time reference (ANDATORY) Ship/Delivery date Date / time qualifier ID 3/3 Date Shipped/delivered qualifier (010/011/067/068) Date DT 8/8 CCYYDD Segment:FOB F.O.B Related Instructions (OPTIONAL) To specify transportation instructions relating to shipment Shipment ethod of Payment ID 2/ Location Qualifier ID O 1/2 "PP" = Prepaid (by Seller) "PB" = Customer Pick-up "CC" = Collect "DE" = Destination "OA" = Origin Segment: N1 Name (ANDATORY) Entity identifier code ID 2/3 "SU"= Ship From Name AN 1/60 Ship From Name Identifier code qualifier ID 1/ Identification code AN 2/80 arch 2008 Page 16 of 23

17 Segment: N3 Address information * (ANDATORY) Ship From information Address 1 AN O 1/55 Ship From address Address 2 AN O 1/55 Segment: N4 Geographic location * (ANDATORY) Ship From information City name AN O 2/30 Ship From city Province code AN O 2/2 Ship From province Postal code AN O 3/15 Ship From postal code Segment:HL Hierarchical Level (Order Level) (ANDATORY) Identifying Level Structures ID number AN 2/2 ID number Parent ID number AN C 2/2 Parent ID number Hierarchical Level Code ID 1/2 Level Code Hierarchical Child Code ID C 1/1 Child Code Segment: PRF PO Reference *(ANDATORY) To specify identifying numbers Purchase Order Number ID 1/22 PO Number Release Number AN O 1/30 Specify identifying number Purchase Order Date DT 6/8 PO Date arch 2008 Page 17 of 23

18 Segment:HL Hierarchical Level (Item Level) (ANDATORY) Identifying Level Structures ID number AN 2/2 ID number Parent ID number AN C 2/2 Parent ID number Hierarchical Level Code ID 1/2 Level Code Hierarchical Child Code ID C 1/1 Child Code Segment: LIN Item Identification (ANDATORY) Assigned ID AN C 1/20 Assigned ID (line item from the PO) Product/service ID qualifier ID 2/2 VP =Vendor s Product number Product/service ID AN 1/ Product/service ID qualifier ID C 2/2 CB = Buyer s Catalog Number Product/service ID AN C 1/ Product/service ID qualifier ID C 2/2 UP =UPC Consumer Package Code UK =SCC14 UPC Code Product/service ID AN C 1/15 UPC Segment: SN1 Item Detail (ANDATORY) Assigned ID ID 1/20 Assigned ID Number Units Shipped R9 1/10 Total Number of Units Shipped Same as PO102 from transaction Unit of easure AN O 2/2 Same as PO103 from transaction 850 arch 2008 Page 18 of 23

19 Segment: PO4 Item Physical Detail (OPTIONAL) Pack N0 1/6 Pack Size R 1/8 Size of a pack Unit of easure Code ID 2/2 Unit of easure of the size Segment: PID Product/ item description (OPTIONAL) Item description type ID 1/1 «F «= free -form Description AN 1/80 Our product description Segment:HL Hierarchical Level (Pack Level) (ANDATORY) Identifying Level Structures ID number AN 2/2 ID number Parent ID number AN C 2/2 Parent ID number Hierarchical Level Code ID 1/2 Level Code Hierarchical Child Code ID C 1/1 Child Code Segment: SLN Subline Item Detail (ANDATORY) Quantity R9 1/15 Quantity per package 05 C001 /355 Unit of easure AN O 2/2 Same as PO103 from transaction 850 arch 2008 Page 19 of 23

20 Segment: REF Reference Identification (ANDATORY) Reference Identification Qualifier ID 2/3 LT = Lot Number Reference Identification AN 1/30 Lot Number Segment:AN arks and Numbers (ANDATORY) arks and numbers qualifier ID 2/2 G arks and numbers AN 1/48 SSCC-18 Package label number arks and numbers AN O 1/48 SSCC-18 Package label number Note: When both AN02 and AN03 are used, AN02 is the starting number of a sequential range and AN03 is the ending number of that range. Segment: DT Date and time reference (ANDATORY) anufacturing date Date / time qualifier ID 3/3 094 = anufacture date Date DT 8/8 CCYYDD arch 2008 Page 20 of 23

21 Segment: DT Date and time reference (ANDATORY) Expire date Date / time qualifier ID 3/3 036 = Expire date Date DT 8/8 CCYYDD Segment: CTT Transaction totals (ANDATORY) Number of line items N0 1/ Hash total R O 1/ Weight R O 1/ Unit or basis for measurement code ID O 2/ Volume R O 1/ Unit or basis for measurement code ID O 2/2 Segment:SE Transaction set trailer (ANDATORY) Number of included segment N0 1/10 Include segment ST and SE in the calculation Transaction set control number AN 4/9 Same number as segment ST02 arch 2008 Page 21 of 23

22 ASN (856) sample BSN*00* * *133853~ HL*1*0*S*1~ TD1*CTN25*1****A3* *LB~ TD5**2*TPTT~ REF*B* ~ REF*VR*54321~ DT*011* ~ FOB*PP*DE~ N1*SU*Company Name*92* ~ N3*Your Address here~ N4*City*QC*zipcode~ HL*2*1*O*1~ PRF*01234-A1A*** ~ HL*3*2*I~ LIN**CB*288801*UP* *VA*8576~ SN1**960*PK~ HL*4*3*P~ SLN****320*PK~ REF*LT*12345~ AN*G* ~ DT*094* ~ DT*036* ~ HL*5*3*P~ SLN****320*PK REF*LT*12345~ AN*G* ~ DT*094* ~ DT*036* ~ HL*6*3*P~ SLN****320*PK~ REF*LT*12345~ AN*G* ~ DT*094* ~ DT*036* ~ HL*7*2*I~ LIN**CB*779311*UP* *VA*1234~ SN1**200000*SH~ HL*8*7*P~ SLN****200000*SH~ REF*LT*12345~ AN*G* ~ DT*094* ~ DT*036* ~ CTT*2~ arch 2008 Page 22 of 23

23 APPENDIX D: Logistical Shipping unit & LPN (Visio) arch 2008 Page 23 of 23