Copyright 2002, Jos. A. Bank, Inc. All rights reserved.

Transcription

1 Copyright 2002, Jos. A. Bank, Inc. All rights reserved.

2 Table of Contents EDI Program, Ship Modes and ASN Type... 3 Compliance with EDI Program... 3 Transmitting the 856 ASN... 4 JAB Ship Modes and ASN Type... 5 EDI Implementation Information... 7 EDI Assistance... 7 VAN... 7 EDI Transactions Supported... 7 Product Identification... 7 Backorders NOT Permitted... 7 Substitutions NOT Permitted... 7 New Vendors... 7 Electronic Data Interchange (EDI) Trading Partner Data Sheet Invoice... 9 Introduction Purchase Order...19 Introduction ITD Terms of Sale/ Deferred Terms of Sale ASN...34 Introduction Example ASN Document ST Transaction Set Header BSN Beginning Segment for Advance Ship Notice HL Hierarchical Level (shipment) TD1 Carrier Details (Quantity and Weight) TD5 Carrier Details (Routing Sequence/ Transit Time) REF erence Identification (Bill of Lading) REF erence Identification DTM Date/Time erence (Shipped) N1 Name (Ship From) HL Hierarchical Level (Order) PRF Purchase Order erence REF erence Identification REF erence Identification N1 Name (Ship To) HL Hierarchical Level (Pack) MAN Marks and Numbers HL Hierarchical Level (Item) LIN Item Identification LIN Item Identification SN1 Item Detail (Shipment) CTT Transaction Totals SE Transaction Set Trailer Data ent Summary For 870 Transactions...48 Introduction

3 EDI Program, Ship Modes and ASN Type Compliance with EDI Program The Company and its affiliate and subsidiary companies recognize the importance EDI plays in the achievement of our strategic goals. The use of EDI is recognized as a remarkably effective strategic tool for improving processes and conducting business more effectively. We expect our Trading Partners also to have a similar commitment to the implementation of this technology. JAB requires compliance with our EDI program as a condition of being a Business/Trading Partner. JAB s EDI program currently consists of: Invoice (810) Purchase Order (850) Advance Ship Notice (856) Transactions - Order Status Report (870) Functional Acknowledgment (997) 3

4 Transmitting the 856 ASN All vendors must send one 856 ASN per order, per shipment, per shipping location per EDI Transmission at the time of shipping - at least 24 hours in advance of the shipment arriving at either of our distribution centers. Vendors can send the 856 ASN as soon as the order is packed and ready for pick-up. If the product arrives prior to the 856 ASN, the vendor will be subject to a non-compliance charge. Vendors located within 24 hours of our distribution center and shipping via Air Freight (or who have shipments leaving their facility on Friday) should pay special attention when determining the appropriate time to transmit the 856 ASN. In the event of an error, you must be capable of retransmitting all EDI documents within 24 hours of request. ASN compliant vendors are not required to supply a paper packing list. UCC 128 Labels Additionally, all shipments must have approved UCC-128 labels attached to all cartons. See JAB Ship Modes and ASN Type on page 5 for JAB ship modes and the type of ASN required. One-Time Only Exemption for New Vendors All New Vendors will be exempt one time only from providing an ASN for a period of 30 days of the submitted purchase order. All exempt vendors must provide a detailed consolidated packing list (for examples, see Error! erence source not found. Error! Bookmark not defined.). The packing list should be placed in or on the lead carton and the carton should be properly marked. 4

5 JAB Ship Modes and ASN Type The table below lists JAB ship modes and the type of ASN required: Ship Description Mode 1 Push/Flow Through Garments on Hangers (GOH): Merchandise shipped bulk on APPROVED hangers to be allocated directly to the stores. 2 Push/Flow Thru (Ctn) Merchandise: Merchandise shipped bulk from the vendor to be allocated directly to the stores. Cartons must be packed with one style, color and size per carton. Remaining units for colors and sizes that cannot fill a carton may be packed into mixed cartons. 3 Back Stock (Ctn) Merchandise: Merchandise shipped in bulk from the vendor to be stored at DC to replenish the stores basic items. Mixed styles, colors or sizes in a carton NOT ALLOWED 5 Master pack/case pack Merchandise: Merchandise packed in identical musical runs. ex: (S-1, M-2, L-2, XL-1). Pre-Packs for Ship Mode 5 All Pre-Packs for Ship Mode 5 must be shipped to the exact quantities as ordered and all extra units will be placed in the bulk PO. ASN Type 6 Flat-to-GOH: Flow Thru merchandise shipped in a carton to be processed on APPROVED hangers. 7 Backstock Flat to GOH: Replenishment Merchandise to be shipped in cartons on APPROVED hangers flat packed and stored at DC to replenish stores basic items 9 Garment on Hanger (GOH) Back Stock Merchandise: Merchandise shipped on APPROVED hangers to be stored at the DC to replenish the stores basic items. 10 Special Orders: sent via FedEx directly to the store(s) with shipping documents and AWB ed to Caroline.Fagundes@menswearhouse.com NONE 5

6 Ship Description Mode 11 Direct to Store: All merchandise to be shipped directly to store and not the DC 12 EDI Push (Flat Ctn): Replenishment orders generated via EDI with merchandise to be shipped in bulk from the vendor and allocated to the stores upon receipt; All units expected to ship out completely 13 EDI GOH: Orders generated via EDI with merchandise shipped on APPROVED hangers to replenish stores; All units expected to ship out completely 14 EDI Flat to GOH: Flat to GOH Replenishment orders generated via EDI to come through the DC and ship to stores; All units are expected to ship out completely (must be shipped on APPROVED hangers) 18 Drop Ship (JAB only): Special Orders sent Directly to a store for a specific customer. Not processed in DC. 21 Samples Samples, bulk -- Sent most cost effective way with FedEx. Mixed sizes in a carton ALLOWED. 22 Web/Catalog: Merchandise is shipped in bulk by vendor and is held in our DC Cartons must be packed with one style, color and size per carton. Remaining units for colors and sizes that cannot fill a carton may be packed into mixed cartons. 23 Custom Clothing thru DC: Merchandise from custom clothing orders shipped overseas to be processed in the DC. Mixed styles, colors, and sizes in a carton ALLOWED. 24 JAC Flat Flow Thru: Merchandise shipped bulk from the vendor to be allocated directly to our Joseph Abboud Collection Store. 25 JAC GOH Flow Thru: Merchandise shipped bulk on APPROVED hangers to be allocated directly to our Joseph Abboud Collection Store. ASN Type 6

7 EDI Implementation Information EDI Assistance If you are not currently EDI-capable, DIcentral, ( our preferred Web EDI Solution provider, has a variety of cost-effective solutions in addition to the traditional EDI method. As a trading partner of this Company, you will find DIcentral eager to assist you in fulfilling this obligation. VAN TMP (TECVAN) Qualifier Type: 01 Qualifier : EDI Transactions Supported Sent 850 Purchase Orders 852 Product Data Activity (Sales and Transfers, Inventory, Models) 997 Functional Acknowledgement Received 810 Invoice (Required) 856 Advance Ship Notice (ASN) (Required) 870 Order Status Report (Drop Ship vendors only) 997 Functional Acknowledgement Product Identification Jos. A. Bank will transmit our in-house SKU codes. Backorders NOT Permitted Backorders are not permitted on EDI purchase orders. As long as the ASN is received before the next time EDI purchase orders are generated, the items not filled on the previous order will be reordered. Substitutions NOT Permitted Substitutions are not permitted. When substitutions are made, the ASN cannot be processed. New Vendors We require all new vendors to fill out the Trading Partner Data Sheet and send it to our EDI Administrator. See page 8 for form. 7

8 Electronic Data Interchange (EDI) Trading Partner Data Sheet 8

9 810 Invoice Introduction This section describes mapping information for a standard 810 invoice. Version VICS Qualifier Qualifier Type: 01 Qualifier : VAN TMP (TECVAN) Transaction Sets Transaction sets must be enclosed in X.12 standard interchange (ISA-IEA) and functional group (GS-GE) envelopes. Segment Terminator: ~ ent Separator: ~ Transaction Set Format 810 ISA Interchange Start GS Group Start HEADER LEVEL ST BIG REF N1 ITD DETAIL LEVEL IT1 SAC Transaction Set Header Beginning Segment for Invoice erence Identification Name Terms of Sale Baseline Item Data (Invoice) Service Allowance/Charge SUMMARY LEVEL TDS Total Monetary Value Summary CAD Carrier Detail SAC Service Allowance/Charge CTT Transaction Totals SE Transaction Set Trailer GE Group End EA Interchange End 9

10 ST Transaction Set Header (Mandatory) The Transaction Set Header indicates the start of a transaction set and assigns a control number. Example: ST*810* ent Name Req Type Min/Max Comments ST Transaction Set Identifier Code ST Transaction Set Control Number M 3/3 810 Invoice M AN 4/9 Sequential number assigned by sender, For each functional group, the first Transaction Set Control number is 0001 and is incremented by one for each additional transaction set within the group. BIG Beginning Segment for Invoice (Mandatory) The Beginning Segment for Invoice indicates the beginning of an invoice transaction set and transmits identifying numbers and dates. Example: BIG* *91825* *M ent Name Req Type Min/Max Comments BIG Date M DT 8/8 Invoice Date CCYYMMDD BIG02 76 Invoice Number M AN 1/22 Identifying number assigned by issuer BIG Date M DT 8/8 JAB's original purchase order date, CCYYMMDD BIG Purchase Order Number M AN 1/22 JAB 's original purchase order number 10

11 REF erence Identification (Mandatory) To specify identifying information Example: REF*IA* ent Name Req Type Min/Max Comments REF erence Identification Qualifier REF erence Identification M 2/2 IA Internal Vendor number M AN 1/30 Seven digit People Soft Vendor Number REF erence Identification (Mandatory) To specify identifying information Example: REF*DP*40 ent Name Req Type Min/Max Comments REF erence Identification Qualifier REF erence Identification M 2/2 DP Division M AN 1/30 Division Number N1 Name (Mandatory) The Name identifies a buying party by type of organization, name, and code. Example: N1*ST**92*1091 Example drop ship: N1*ST*JOHN SMITH (N103 and N104 is not mandatory for drop ship) ent Name Req Type Min/Max Comments N Entity Identifier Code M 2/2 ST Ship To N Name X AN 1/60 Mandatory for drop ship N Identification Code Qualifier X 1/2 92 assigned by Buyer s agent; Mandatory when sending the N104 segment N Identification Code X AN 3/4 DC # or Store Number is mandatory for all invoices except for drop ship invoices 11

12 ITD Terms of Sale/Deferred Terms of Sale (Optional) The Terms of Sale/Deferred Terms of Sale segment specifies terms of sale. When sent, the terms must be sent exactly as the terms in the 850. Example: ITD*08*3**** *15 ent Name Req Type Min/Max Comments ITD Terms Type Code M 2/2 Code identifying type of payment terms 05 - Discount not applicable 08 Basic discount offered days after end of month ITD Terms Basis Date Code ITD Terms Discount Percent ITD Terms Discount Due Date ITD Terms Discount Days Due ITD Terms Net Due Date M 1/2 Code identifying the beginning of the terms period. 3 Invoice Date O R 1/6 Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date. Send the percent with a decimal point only when needed. ( e.g., send 10.5% as "10.5", and send 2% is as "2"). X DT 8/8 Date payment is due if discount is to be earned. CCYYMMDD X N 1/3 Number of days in the terms discount period by which payment is due if terms discount is earned. The end of the term period is derived by adding this value to the beginning of the term period, as qualified by ITD02. M DT 8/8 Date when total invoice amount becomes due expressed in format CCYYMMDD ITD Terms Net Days M N 1/3 Number of days until total invoice amount is due (discount not applicable). The end of the term period is derived by adding this value to the beginning of the term period, as qualified by ITD02. 12

13 IT1 Baseline Item Data (Mandatory) To specify the basic and most frequently used line item data for the invoice and related transactions. Example: IT1*1*6*EA*56**CB* *VA*27565*UP* ent Name Req Type Min/Max Comments IT Assigned Identification O AN 1/20 PO Line number. IT Quantity Invoiced M R 1/15 Number of units invoiced (supplier units) IT Unit or Basis for Measurement Code M 2/2 EA Each CA - Case IT Unit Price M R 1/17 Price per unit of product, service, commodity, etc. Send price with a decimal point only when needed. (e.g., $15.95 would be sent as "15.95", and $29.00 would be sent as "29"). IT Product/Service Qualifier IT Product/Service IT Product/Service Qualifier M 2/2 CB Buyer Item Number M AN 1/48 Nine character item number 850 PO O 2/2 VA Vendor s Style Number IT Product/Service O AN 1/48 Vendor s Style Number IT Product/Service Qualifier O 2/2 UP UPC Code IT Product/Service O AN 1/48 UPC Number U.P.C. Consumer Package Code 13

14 SAC Service Promotion Allowance or Charge) To request or identify a service, promotion, allowance or charge, to specify the amount or specify for the service, promotion, allowance, or charge. Mandatory for Made-to-Measure vendor otherwise do not send. Example: SAC*N*ZZZZ***15********** JABW171103US ent Name Req Type Min/Max Comments SAC Allowance or charge code SAC Service, Promotion, Allowance or Charge code M AN 1/1 N No charge M 4/4 ZZZZ Fabric Cost SAC Amount M N2 1/15 Fabric cost to make the item SAC Description M AN 1/80 Commercial invoice number CAD Carrier Detail To specify identifying information. Carrier and tracking number Mandatory for drop ship order. The 850 BEG02 DS identifies the order as drop ship. Example: CAD****FDE***BM* ent Name Req Type Min/Max Comments CAD erence Identification Qualifier CAD erence Identification Qualifier X 2/4 Standard Carrier Alpha Code Mandatory for Drop Ship vendors Optional for non-drop Ship X 2/3 BM - erence Identification code Mandatory for Drop Ship CAD erence Identification X AN 1/50 Tracking number Mandatory for Drop Ship 14

15 SAC Service Promotion Allowance or Charge To request or identify a service, promotion, allowance or charge, to specify the amount or specify for the service, promotion, allowance, or charge. Drop ship handling charge for authorized vendor. Do not send if vendor is not an authorized vendor. Example: SAC*C*D500***450 ent Name Req Type Min/Max Comments SAC Allowance or charge code SAC Service, Promotion, Allowance or Charge code X AN 1/1 C Charge X 4/4 D500 -Handling SAC Amount X N2 1/15 Handling charge TDS Total Monetary Value Summary (Mandatory) The Total Monetary Value Summary segment specifies the total invoice discounts and amounts. Example: TDS*28800 ent Name Req Type Min/Max Comments TDS Amount M N2 1/15 Total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable) 15

16 SAC Service Promotion Allowance or Charge To request or identify a service, promotion, allowance or charge, to specify the amount or specify for the service, promotion, allowance, or charge. SAC is mandatory for Moores Canada Canadian taxes. Canadian taxes do not apply to Jos A. Bank and Mens Wearhouse. Example: SAC*C*D360***18241*******06***CANADIAN.S.T Example: SAC*C*H770***4253*******06***QUEBEC SALES TAX I D ent Name Req Type Min/Max Comments SAC Allowance or charge indicator SAC Service, promotion, allowance X 1/1 C - Charge. X 4/4 D350 GST CreditT D360 GST Charge (for GST and/or HST) H770 PST Charge (for PST and/or QST) SAC Amount X FT 1/15 Total GST implied 2 decimal SAC Allowance or charge Method X 2/2 06 Charge to be paid by customer 02 off invoice SAC Description O AN 1/80 CTT Transaction Totals (Mandatory) The Transaction Totals segment transmits a hash total for the number of IT1 segments in the transaction set. Example: CTT*4 ent Name Req Type Min/Max Comments CTT Number of Line Items M N0 1/6 The number of IT1 segments present in the transaction set SE Transaction Set Trailer (Mandatory) The Transaction Totals segment transmits a hash total for the number of segments in the transaction set. Example: SE*11*

17 ent Name Req Type Min/Max Comments SE01 96 Number of Included Segments SE Transaction Set Control Number M N0 1/10 Total number of segments included in a transaction set including ST and SE segments M AN 4/9 Identifying control number- this must be the same number as is in the ST segment (ST02) for the transaction set. 17

18 Example Invoice: ISA*00* *00* *12* *01* * *1031*U*00401* *0*P*:~ GS*IN* * * *1031*99*X*004010VICS~ ST*810*990001~ BIG* * * *J ~ REF*IA* ~ REF*DP*40~ N1*ST**92*1091~ ITD*05*3**** *30~ IT1**50*EA*24**UP* ~ IT1**50*EA*24**UP* ~ IT1**50*EA*24**UP* ~ IT1**50*EA*24**UP* ~ TDS* ~ CTT*4~ SE*18*990001~ GE*1*99~ IEA*1* ~ Example Invoice - Made to Measure/Custom Clothing: ISA*00* *00* *12* EC *01* * *1340*U*00400* *1*P*>~ GS*IN* EC* * *1340*0032*X*004010VICS~ ST*810*0032~ BIG* *RCJC21V8C* *JC21V8C~ REF*IA* ~ REF*DP*30~ N1*ST*Jos A Bank*92*1091~ IT1*000001*1*EA*87.00**CB*34HN54L00~ SAC*N*ZZZZ***2890********** JABW171212US~ IT1*000002*1*EA*21.60**CB*34NA54L00~ SAC*N*ZZZZ***850********** JABW171212US~ TDS*10860~ CTT*2~ SE*12*0032~ GE*1*0032~ IEA*1* ~ Example Invoice Drop Ship: ISA*00* *00* *12* *01* * *2111*U*00401* *0*P*>~ GS*IN* * * *2111*673434*X*004010VICS~ ST*810*0001~ BIG* * * *JD ~ REF*IA* ~ REF*DP*40~ N1*ST*CHRISTOPHER DIROFF~ ITD*05*3*0* ** *30~ IT1*000001*1*EA*69.75**CB*40M625D56*VA* *UP* ~ TDS*7425~ CAD****FDEG***BM* ~ SAC*C*D500***450~ CTT*1~ SE*12*0001~ IEA*1*

19 850 Purchase Order Introduction This section describes mapping Information for: Standard EDI Purchase Order (850) Version VICS 850 Purchase order Qualifier Type: 01 Qualifier : VAN TMP (TECVAN) Transaction Sets Transaction sets must be enclosed in X.12 standard interchange (ISA-IEA) and functional group (GS-GE) envelopes. Segment Terminator: ~ ent Separator: ~ 19

20 850 PURCHASE ORDER Version 4010VICS Transaction Set Format 850 ISA Interchange Start GS Group Start Ship CR) - 001) HEADER LEVEL ST Transaction Set Header BEG Beginning Segment for Purchase Order REF erence (Vendor number - VR) REF erence (Division - DP) REF erence (Ship Mode - PRC) REF erence (Custom Order CO) REF erence (Customer reference/drop ITD Terms of sale DTM Date/Time erence (Ship date 010) DTM Date/Time erence (Cancel after date TD5 N9 MSG N1 N2 N3 N4 Carrier Details erence Identification Message statement Name (Ship To) Additional Name (Ship To) Address Information (Ship To) Geographic Location (Ship To) DETAIL LEVEL PO1 Purchase Order Baseline Item Data P Product Item Description SDQ Destination Quantity SUMMARY LEVEL CTT Transaction Totals SE Transaction Set Trailer IEA GE Group End Interchange End Drop Ship Orders: BEG02 DS Drop ship REF*PHC* 18 Ship Mode for drop ship REF*CR* xxxxx Drop ship reference number Custom Clothing Orders: REF*CO*xxxxx Custom clothing reference number for custom clothing vendors 20

21 BEG Transaction Set Purpose Code M 2/2 Code identifying purpose of transaction set 06 - Confirmation BEG02 92 Purchase Order Type Code M 2/2 Code specifying the type of Purchase Order NE - New Order DS Drop Ship BEG Purchase Order Number M AN 1/22 Identifying number for Purchase Order assigned by the orderer/purchaser Purchase order number BEG Release Number M AN 1/30 Release against the Purchase Order BEG Date M DT 8/8 Date expressed as CCYYMMDD Purchase order date REF erence Number M 2/3 erence Identification Qualifier VR - Vendor number REF erence Identification X AN 1/ Vendor Number REF erence Number M 2/3 erence Identification Qualifier DP - Division REF erence Identification X AN 1/30 10, 20, 30, 40, 50, 60, 70, 80 Divisions 10 Sports Coats 20 Slacks 30 Suits 40 Shoes 50 Dress Shirts 60 Sportswear 70 Outerwear 80 Accessories 21

22 REF erence Number M 2/3 erence Identification Qualifier PHC - Ship Mode REF erence Identification X AN 1/30 Ship Description Mode 1 Push/Flow Through Garments on Hangers (GOH): Merchandise shipped bulk on APPROVED hangers to be allocated directly to the stores. 2 Push/Flow Thru (Ctn) Merchandise: Merchandise shipped bulk from the vendor to be allocated directly to the stores. Cartons must be packed with one style, color and size per carton. Remaining units for colors and sizes that cannot fill a carton may be packed into mixed cartons. 3 Back Stock (Ctn) Merchandise: Merchandise shipped in bulk from the vendor to be stored at DC to replenish the stores basic items. Mixed styles, colors or sizes in a carton NOT ALLOWED 5 Master pack/case pack Merchandise: Merchandise packed in identical musical runs. ex: (S-1, M-2, L-2, XL-1). Pre-Packs for Ship Mode 5 All Pre-Packs for Ship Mode 5 must be shipped to the exact quantities as ordered and all extra units will be placed in the bulk PO. 6 Flat-to-GOH: Flow Thru merchandise shipped in a carton to be processed on APPROVED hangers. 7 Backstock Flat to GOH: Replenishment Merchandise to be shipped in cartons on APPROVED hangers and stored at DC to replenish stores basic items 9 Garment on Hanger (GOH) Back Stock Merchandise: Merchandise shipped on APPROVED hangers to be stored at the DC to replenish the stores basic items. 10 Special Orders: sent via FedEx directly to the store(s) with shipping documents and AWB ed to Caroline.Fagundes@menswearhouse.com ASN Type NONE 22

23 Ship Description Mode 11 Direct to Store: All merchandise to be shipped directly to store and not the DC 12 EDI Push (Flat Ctn): Replenishment orders generated via EDI with merchandise to be shipped in bulk from the vendor and allocated to the stores upon receipt; All units expected to ship out completely 13 EDI GOH: Orders generated via EDI with merchandise shipped on APPROVED hangers to replenish stores; All units expected to ship out completely 14 EDI Flat to GOH: Flat to GOH Replenishment orders generated via EDI to come through the DC and ship to stores; All units are expected to ship out completely (must be shipped on APPROVED hangers) 18 Drop Ship (JAB only): Special Orders sent Directly to a store for a specific customer. Not processed in DC. 21 Samples Samples, bulk -- Sent most cost effective way with FedEx. Mixed sizes in a carton ALLOWED. 22 Web/Catalog: Merchandise is shipped in bulk by vendor and is held in our DC Cartons must be packed with one style, color and size per carton. Remaining units for colors and sizes that cannot fill a carton may be packed into mixed cartons. 23 Custom Clothing thru DC: Merchandise from custom clothing orders shipped overseas to be processed in the DC. Mixed styles, colors, and sizes in a carton ALLOWED. 24 JAC Flat Flow Thru: Merchandise shipped bulk from the vendor to be allocated directly to our Joseph Abboud Collection Store. 25 JAC GOH Flow Thru: Merchandise shipped bulk on APPROVED hangers to be allocated directly to our Joseph Abboud Collection Store. ASN Type 23

24 REF erence Number O 2/3 erence Identification Qualifier CO - Custom Order REF erence Identification X AN 1/30 Custom Order number X REF erence Number O 2/3 erence Identification Qualifier CR Drop Ship REF erence Identification X AN 1/30 Drop Ship Order number 24

25 ITD Terms of Sale/ Deferred Terms of Sale Terms of Sale/Deferred Terms of Sale specifies terms of sale. If ITD01 = 5 then ITD02 and ITD07 is required. If ITD01 = 8 then ITD02, ITD03, ITD05 and ITD07 is required If ITD01 = 12 then ITD02, ITD03 and ITD13 is required. Example: ITD*05*3*****60 (pay net 60 days) ITD*08*3*1**30**60 (pay discount 1% paid in 30 days net amount in 60 days) ITD*12*3*3**********10 (pay 3% EOM 10 day) ITD Terms Type Code O 2/2 Code identifying type of payment terms 05 - Discount not applicable 08 Basic discount offered days after end of month ITD Terms Basis Date Code M 1/2 Code identifying the beginning of the terms period 3 - Invoice Date ITD Terms Discount Percent C R 1/6 Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the terms Discount Due Date. The percent is sent with a decimal point only when needed, e.g. send 10.5% as 10.5, and send 2% as 2. ITD Terms Discount Days C N0 1/3 Number of days in the terms discount period by which payment is due if terms discount is earned. ITD Terms Net Days C N0 1/3 Number of days until total invoice is due (discount not applicable). ITD Day of Month C N0 1/2 10 Number of days due after end of month 25

26 DTM Date/Time Qualifier M 3/3 Code identifying ship date Code identifying Ship Date DTM Ship Date or Cancel Date X DT 8/8 Date expressed as CCYYMMDD Ship Date DTM Date/Time Qualifier M 3/3 Code identifying cancel after date Code identifying Cancel After Date DTM Ship Date or Cancel Date X DT 8/8 Date expressed as CCYYMMDD Cancel after date 26

27 TD Carrier Detail Routing O AN 01/35 Carrier routing for Drop Ship FDEG FEDEX Ground FX2D FEDEX 2 Day FXND FEDEX Next Day Note The TD5 segments are specific for drop ship order N N9 erence Identification Qualifier M 2/3 erence Identification Qualifier AH Agreement number N erence Identification M N 1/ Agreement number MSG MSG Message Text M AN 1/264 Free-from message text legal statement N Entity Identifier Code O 02/03 ST Ship To N Name X AN 01/60 N Identification Code Qualifier X 02/02 N Identification Code X AN 02/80 N Name O AN 01/55 N Name X AN 01/55 N Address O AN 01/55 N Address X AN 01/55 27

28 N City Name O AN 02/30 N State or Province Code X 02/02 N Postal Code X 03/15 28

29 PO Assigned Identification M AN 01/20 Identification number - Purchase order line number PO Quantity Ordered M FT 01/15 Floating Point number representing the order quantity Ordered Quantity PO Unit or BS M 02/02 Unit of Measure EA Each PO Unit Price M FT 01/17 Floating Point number representing unit price Unit Price PO Product/Service Qualifier M 02/02 Code identifying product (BUYERS CODE) CB - for Catalog Buyers Code PO Product/Service M AN 01/48 Identifying Product/Service (Item Code) Catalog buyer code 9 character Item Code PO Product/Service Qualifier O 02/02 Code identifying product (UPC) UP Universal Product Code PO Product/Service X AN 01/48 Identifying UPC code UPC code PO Product/Service Qualifier O 02/02 Not used PO Product/Service X AN 01/48 Not used PO Product/Service Qualifier O 02/02 Code identifying product VA Vendor s Style Code PO Product/Service X AN 01/48 Identifying VA Vendor s Style Number PO Product/Service Qualifier O 02/02 Code identifying product VS Vendor s Lot Code PO Product/Service X AN 01/48 Identifying VS Vendor s Lot Number 29

30 P Item Description Type M 01/01 Code Identifying Item F Free Form P Description X AN 01/80 Identifying Item Description Item description X SDQ Unit or Basis for Measurement Code M 02/02 EA Each SDQ02 66 Identification Code Qualifier M 01/02 ZZ Assigned by Buyer JAB store number SDQ03 67 Identification Code M AN 04/04 JAB store number SDQ Quantity M N0 01/15 Store quantity SDQ05 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity SDQ07 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity SDQ09 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 30

31 SDQ Unit or Basis for Measurement Code M 02/02 Store quantity SDQ11 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity SDQ13 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity SDQ15 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity SDQ17 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity SDQ19 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity SDQ21 67 Identification Code X AN 04/04 JAB store number SDQ Quantity X N0 01/15 Store quantity Syntax Rules: 1. P If either SDQ05 or SDQ06 is present, then the other is required. 2. P If either SDQ07 or SDQ08 is present, then the other is required. 3. P If either SDQ09 or SDQ10 is present, then the other is required. 4. P If either SDQ11 or SDQ12 is present, then the other is required. 31

32 5. P If either SDQ13 or SDQ14 is present, then the other is required. 6. P If either SDQ15 or SDQ16 is present, then the other is required. 7. P If either SDQ17 or SDQ18 is present, then the other is required. 8. P If either SDQ19 or SDQ20 is present, then the other is required. 9. P If either SDQ21 or SDQ22 is present, then the other is required. Note: SDQ segments are not sent for Drop Ship orders. 32

33 CTT Number of lines Items M N0 01/06 Total number of PO1 segments 33

34 856 ASN Introduction This section describes mapping Information for Standard EDI Advance Ship Notice (856) TRANSACTION SET FORMAT ISA Interchange Start GS Group Start HEADER LEVEL ST Transaction Set Header BSN Beginning Segment for Ship Notice SHIPMENT LEVEL HL Hierarchical Level (Shipment) TD1 Carrier Details (Quantity and Weight) TD5 Carrier Details (Routing Sequence/Transit Time) REF erence Number (Bill of Lading or Carrier ) REF erence Number (Master Tracking Number) DTM Date/Time erence N1 Name (Ship From) ORDER LEVEL HL Hierarchical Level (Order) PRF Purchase Order erence REF erence Number (Invoice number) REF erence Number (Customer order number) N1 Name (Ship To) (Must be after the REF segment.) PACK LEVEL HL Hierarchical Level (Pack) MAN Marks and Numbers ITEM LEVEL HL LIN SN1 Hierarchical Level (Item) Item Identification Item Detail (Shipment) SUMMARY A CTT SE Transaction Totals Transaction Set Trailer IEA GE Group End Interchange End 34

35 Example ASN Document ST*856* BSN*00*00001* *1232 HL*1**S TD1*CTN25*0045****G* *LB TD5*B*2*RDWY*M*ROADWAY EXPRESS REF*BM*31560 REF*CN* DTM*011* N1*SF*ABC COMPANY*1* HL*2*1*O PRF*J *** REF*IV* REF*CO* l78 N1*ST**92*1025 HL*3*2*P MAN*GM* HL*4*3*I LIN*1*CB* *UP* SN1**24*EA HL*4*2*I LIN*2* CB* *UP* SN1**1*EA... CTT* SE*001341* GE*000002* IEA*00001*

36 ST Transaction Set Header Transaction Set Header indicates the start of a transaction set and assigns a control number. Example: ST*856* ent Name Req Type Min/Max Comments ST Transaction Set Code M 3/3 856 Advance Ship Notice ST Transaction Set Control Number M AN 4/9 Sequential Number assigned by sender BSN Beginning Segment for Advance Ship Notice Beginning Segment for Advance Ship Notice indicates the beginning of an advance ship notice transaction set and transmits identifying numbers and date. Example: BSN*00*00001* *1232 ent Name Req Type Min/Max Comments BSN Transaction Set Code M 2/ Original BSN Shipment Identification M AN 2/30 Unique control number assigned by vendor BSN Date ASN was created M DT 8/8 CCYYMMDD BSN Time ASN was created M TM 4/8 HHMM or HHMMSS 36

37 HL Hierarchical Level (shipment) Hierarchical Level (shipment) identifies dependencies among and the content of hierarchically related groups of data segments. Example: HL*1**S ent Name Req Type Min/Max Comments HL Hierarchical Number M AN 1/12 Unique number assigned by vendor to identify a particular portion in a hierarchical structure. At the shipment level in an ASN this will start with 1. HL Hierarchical Parent Not used at the Shipment Level HL Hierarchical Level Code M 1/1 S - Shipment TD1 Carrier Details (Quantity and Weight) Carrier Details (Quantity and Weight) specifies the transportation details relative to commodity, weight and quantity. If TD106 is present then TD107 and TD108 is required. Example: TD1*CTN25*0045****G* *LB ent Name Req Type Min/Max Comments TD Packaging Code M AN 3/5 CTN25 = Carton corrugated TD Lading Quantity M N0 1/7 Number of units in the shipment as described in TD101 TD Weight Qualifier O 1/2 G Gross Weight TD Weight X R 1/10 Numeric value of weight TD Unit of Measurement X 2/2 LB Pounds 37

38 TD5 Carrier Details (Routing Sequence/ Transit Time) Carrier Details (Routing Sequence/Transit Time) specifies the carrier and sequence of routing and provide transit time information. Example: TD5*B*2*RDWY*M*ROADWAY EXPRESS ent Name Req Type Min/Max Comments TD Routing Sequence Code M 1/1 B Origin/Delivery Carrier TD Identification Code Qualifier M 1/1 2 SCAC (Standard Carrier Alpha Code) TD Identification Code M AN 2/80 Code identifying a party TD Transportation Method M 1/2 M- Motor TD Routing M AN 1/35 Free-form description of the routing or requested routing for shipment, or the originating carrier s identity. REF erence Identification (Bill of Lading) erence Identification (Bill of Lading or Carrier erence) Example: REF*BM*31560 REF erence Identification Qualifier ent Name Req Type Min/Max Comments M 2/3 BM Bill of Lading or CN Carrier erence REF erence Identification M AN 1/50 Bill of Lading number or Carrier erence number 38

39 REF erence Identification REF -- erence Identification specifies Master Tracking Order. Mandatory on :Custom Orders otherwise do not send. Example: REF*CN* ent Name Req Type Min/Max Comments REF erence Number Qualifier O 2/3 CN Carrier erence number REF erence Number C AN 1/50 Master Tracking Order number DTM Date/Time erence (Shipped) Date/Time erence specifies pertinent dates (shipped). Example: DTM*011* ent Name Req Type Min/Max Comments DTM Date/Time Qualifier M 3/3 011 Shipped Date DTM Date M DT 8/8 Date (CCYYMMDD) 39

40 N1 Name (Ship From) Name (Ship From) identifies a (ship from) party by type of organization, name and code. At least an N102 or N103 is required. If an N103 or N104 is present then the other is required. Example: N1*SF*ABC COMPANY*1* ent Name Req Type Min/Max Comments N Entity Identifier Code M 2/2 SF Ship From N Name X AN 1/60 Vendor name N Identification Code Qualifier X 1/2 1 Dun s number 12 Telephone number, etc 91 Assigned by Buyer N Identification Code X AN 2/80 DUNS number, Telephone number, Assigned by Buyer, etc 40

41 HL Hierarchical Level (Order) Hierarchical Level (Order) identifies dependencies among and the content of hierarchically related groups of data segments. Example: HL*2*1*O ent Name Req Type Min/Max Comments HL Hierarchical Number M AN 1/12 Unique number assigned by vendor to identify a particular data segment in a hierarchical structure. HL Hierarchical Parent M AN 1/12 Identification number of the next higher hierarchical data portion. In this example, HL 2 (the order) belongs to HL 1 (the shipment) HL Hierarchical Level Code M 1/1 O - Order PRF Purchase Order erence Purchase Order erence provides a reference to a specific purchase order. Example: PRF*J *** ent Name Req Type Min/Max Comments PRF Purchase Order Number M AN 6/6 Purchase Order Number PRF Date M DT 8/8 Purchase Order Date (CCYYMMDD) 41

42 REF erence Identification REF -- erence Identification specifies invoice information. Example: REF*IV* ent Name Req Type Min/Max Comments REF erence Number Qualifier M 2/3 IV Seller s Invoice Number REF erence Number M AN 1/50 Seller s Invoice Number REF erence Identification REF -- erence Identification specifies customer order information. Mandatory on :Custom Orders otherwise do not send. Example: REF*CO* ent Name Req Type Min/Max Comments REF erence Number Qualifier O 2/3 CO Customer Order Number REF erence Number C AN 1/50 Seller s Invoice Number *REF*CO and REF*PRO are required when REF*CO is sent in the 850. *These two REF segments apply to Moores customer order vendor. 42

43 N1 Name (Ship To) Name (Ship To) identifies a party by type of organization, name and code. Example: N1*ST**92*025 ent Name Req Type Min/Max Comments N Entity Identifier Code M 2/2 ST- Ship To N Name O AN 1/50 Jos A Bank N Code Qualifier M 2/2 92 Assigned by Buyer N Code M AN 4/4 JAB Store Number HL Hierarchical Level (Pack) Hierarchical Level (Pack) identifies dependencies among and the content of hierarchically related groups of data segments. Example: HL*3*2*P ent Name Req Type Min/Max Comments HL Hierarchical Number M AN 1/12 Unique number assigned by vendor to identify a particular data segment in a hierarchical structure. HL Hierarchical Parent M AN 1/12 Identification number of the next higher hierarchical data portion. In this example, HL 3 (the carton or pack) belongs to HL 2 (the order) HL Hierarchical Level Code M 1/1 P - Pack 43

44 MAN Marks and Numbers Marks and Numbers specifies identifying marks and numbers for shipping containers. Example: MAN*GM* MAN01 88 Marks and Numbers Qualifier ent Name Req Type Min/Max Comments M 1/2 GM General Merchandise & Apparel Implementation Committee (20 digit UCC128 Shipping Container Code) MAN02 87 Marks and Numbers M AN 1/48 Marks and numbers used to identify a shipment of parts of a shipment (carton number) HL Hierarchical Level (Item) Hierarchical Level (Item) identifies dependencies among and the content of hierarchically related groups of data segments. Example: HL*4*3*I ent Name Req Type Min/Max Comments HL Hierarchical Number M AN 1/12 Unique number assigned by vendor to identify a particular data segment in a hierarchical structure. HL Hierarchical Parent M AN 1/12 Identification number of the next higher hierarchical data portion. In this example, HL 4 (the item) belongs to HL 3 (the carton or pack) HL Hierarchical Level Code M 1/1 I-Item 44

45 LIN Item Identification Item Identification specifies the basic item identification data. Examples LIN*1*CB* *UP* LIN*1*CB* LIN*1*UP* ent Name Req Type Min/Max Comments LIN Assigned Identification O AN 1/20 assigned within a transaction set LIN Product Qualifier M 2/2 CB - Buyer s Catalog Number (9 digit Item Code) or UP - U.P.C. LIN Product M AN 1/48 Identifying number for product LIN Product Qualifier O 2/2 CB - Buyer s Catalog Number (9 digit Item Code) or UP - U.P.C. LIN Product O AN 1/48 Identifying number for product 45

46 LIN Item Identification Item Identification specifies the basic item identification data. Example: LIN*1*CB* ent Name Req Type Min/Max Comments LIN Assigned Identification O AN 1/20 assigned within a transaction set LIN Product Qualifier M 2/2 CB - Buyer s Catalog Number (9 digit Item Code) LIN Product M AN 1/48 Identifying number for product SN1 Item Detail (Shipment) Item Detail (Shipment) specifies line-item detail relative to shipment. Example: SN1**24*EA ent Name Req Type Min/Max Comments SN Number of Units Shipped M R 1/10 Total number of pieces (eaches) shipped SN Unit of Measure M 2/2 EA - Each 46

47 CTT Transaction Totals Transaction Totals transmit a hash total for a specific element in the transaction set. Example: CTT* ent Name Req Type Min/Max Comments CTT Number of line items M N0 1/6 Total number of line segments in the transaction set. SE Transaction Set Trailer Transaction Set Trailer indicates the end of the transaction set and provides the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Example: SE*73* ent Name Req Type Min/Max Comments SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 47

48 Data ent Summary For 870 Transactions Introduction This section describes mapping Information for 870 Transactions - Sales Order Report Version 4010VICS REF. DES DATA ELEMENT NAME ATTRIBUTES BSR Status Report Code M 1/2 Code indicating the reason for sending the report 2 - Prearranged Schedule or Agreement BSR Order/Item Code M 1/2 Code identifying a group of orders and items PP - Select orders Selected Items BSR erence: Identification M AN 1/50 Number assigned by the sender to uniquely identify this transaction BSR Date M DT 8/8 Date expressed as CCYYMMDD The date of this report from the sender REF erence Number M 2/3 erence Identification Qualifier VR - PeopleSoft Vendor Number REF erence Identification M AN 1/30 PeopleSoft Vendor Number 48

49 HL Hierarchical Id Number M AN 1/12 Unique number assigned by vendor to identify a particular data segment in hierarchical structure. HL Hierarchical Parent O AN 1/12 Identification number of the next higher hierarchical data portion. HL Hierarchical Level Code M 1 O - Order PRF Purchase Order Number M 1/22 Original purchase order number PRF Date M DT 8/8 Date expressed as CCYYMMDD Original purchase order date REF erence Number M 2/3 erence Identification Qualifier CR - Customer erence number / Drop ship REF erence Identification M AN 1/30 Customer sales order number 49

50 REF erence Number M 2/3 erence Identification Qualifier DP - Division REF erence Identification M AN 1/2 10, 20, 30, 40, 50, 60, 70, 80 Divisions 10 Sports Coats 20 Slacks 30 Suits 40 Shoes 50 Dress Shirts 60 Sportswear 70 Outerwear 80 Accessories PO Assigned Identification O AN 1/20 Identification number - Purchase order line number PO Quantity Ordered C FT 01/15 Floating Point number representing the order quantity Ordered Quantity Original Purchase Order Quantity PO Unit or BS C 02/02 Unit of Measure EA - Each PO Product/Service Qualifier O FT 01/17 Code identifying product (BUYERS CODE) CB - for Catalog Buyers Code PO Product/Service O 02/02 Identifying Product/Service (Item Code) Catalog buyer code 9 digit Item Code PO Product/Service Qualifier C 02/02 Code identifying product (UPC) UP Universal Product Code PO Product/Service C AN 01/48 Identifying UPC code UPC code 50

51 ISR Shipment/Order Status Code M 2/2 Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction. BP Shipment Partial, Back Order to Ship on (Date) CC Shipment Complete on (Date) CP Partial Shipment on (Date), Considered No Backorder ED Expect to ship by (Date) IC Item Canceled NN Not in Process No Shipping Schedule RD Revised Expect to Ship By (Date) SC Shipment Quantity Decrease DE Delete order CU Canceled Line DI Discontinued DS Out of Stock Condition BO Back Ordered ISR Date M DT 8/8 Date expressed as CCYYMMDD Required if IRS01 requires a date IRS Status Reason Code O 3/3 Code indicating the status reason 51

52 QTY Quantity Qualifier M 02/02 Code specifying the type of Quantify 01 Discrete Quantity QTY02 66 Quantity X R 01/02 Numeric value of quantity QTY03 67 Identification Code M AN 02/80 Identifying our store number Our Store Number QRY17 67 Identification Code M AN 02/80 Identifying our store number Our Store Number QTY Quantity M FT 01/15 CTT Number of lines Items M INT 01/06 52