Copyright 2002, Jos. A. Bank, Inc. All rights reserved. VOL. 5 EDI
|
|
- Cleopatra Wiggins
- 6 years ago
- Views:
Transcription
1 Copyright 2002, Jos. A. Bank, Inc. All rights reserved. VOL. 5 EDI
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 Purchase Order ASN...29 Data ent Summary For 870 Transactions
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), and Functional Acknowledgment (997) 3
4 Transmitting the 856 ASN All vendors must send one 856 ASN per order, per shipment, per shipping location at least 24 hours in advance of the shipment arriving at our distribution center. 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 Mode Description 1 Garments on Hangers (GOH) Flow Through: Merchandise shipped bulk on 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. 3 Back Stock (Ctn) Merchandise: Merchandise shipped in bulk from the vendor to be placed on a shelf or flow rack to replenish the stores basic items. 5 Master pack/case pack Merchandise: Merchandise packed in identical musical runs. (S-1, M-2, L-2, XL-1). 6 Flat-to-Hang (Ctn) Merchandise: Merchandise shipped in a carton to be processed on hangers. 7 EDI Flat to GOH: Replenishment Merchandise to be shipped on a hanger flat packed to replenish weekly/biweekly or monthly seasonal POs 9 Garment on Hanger (GOH) Back Stock Merchandise: Merchandise shipped on hangers to be stored at the DC to replenish the stores basic items. 10 Special Orders: All merchandise ordered for a specific customer or group sale. 11 Direct to Store: All merchandise to be shipped directly to the store and not the DC. 12 EDI Push (Ctn): Replenishment Merchandise to be shipped in bulk from the vendor and allocated to the stores upon receipt. 13 EDI GOH: Merchandise shipped on a hanger to replenish weekly/biweekly or monthly seasonal POs ASN Type Case Level Case Level Case Level Case Level Case Level Case Level Case Level NONE Case Level Case Level Case Level 5
6 Ship Mode Description ASN Type 14 Flat To Hang (Carton) Merchandise: Merchandise packed in a carton with hanger designated for backstock. er to hanger requirements on the tech pack. Mixed styles, colors and sizes in a carton ALLOWED. Hanger Direction: Goods must be packed with garment hangers facing the opposite way every six garments. 18 Drop Ship: Special Orders sent Directly to a store for a specific customer. 19 Flat Factory: Merchandise shipped in a carton specifically for the factory stores. 20 GOH Factory: Merchandise shipped on a hanger specifically for the factory stores. 21 Samples Samples, bulk -- Sent most cost effective way with UPS. Mixed sizes in a carton ALLOWED. 22 Web/Catalog: Merchandise is shipped in bulk by supplier and is 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. Case Level Case Level Case Level Case Level Case Level Case Level 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 ECOM Systems 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 4101VICS 810 Invoice Qualifier Type: 01 Qualifier : Transaction Sets Transaction sets must be enclosed in X.12 standard interchange (ISA-IEA) and functional group (GS-GE) envelopes. Segment Terminator: Carriage Return/Line Feed, Hex 0D/0A ent Separator: Asterisk Character, Hex 2A Transaction Set Format 810 ISA Interchange Start GS Group Start HEADER LEVEL POS.NO. SEG Name 010 ST Transaction Set Header 020 BIG Beginning Segment for Invoice 050 REF erence Identification 070 N1 Name 130 ITD Terms of Sale/Deferred Terms of Sale DETAIL LEVEL POS.NO. SEG Name 010 IT1 Baseline Item Data (Invoice) SUMMARY LEVEL POS.NO. SEG Name 010 TDS Total Monetary Value Summary 070 CTT Transaction Totals 080 SE Transaction Set Trailer GE Group End IEA 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 t ti t ithi th 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 7/7 Seven digit People Soft Vendor Number sent on PO 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 Department number M AN 1/4 JAB Department number N1 Name (Mandatory) The Name identifies a buying party by type of organization, name, and code. Example: N1*ST**92*1091 ent Name Req Type Min/Max Comments N Entity Identifier Code M 2/2 ST Buying Partner N Name O AN 1/60 N Identification Code Qualifier M 1/2 92 assigned by Buyer or Buyer s agent N Identification Code M AN 4/4 JAB store number 11
12 ITD Terms of Sale/Deferred Terms of Sale (Optional) The Terms of Sale/Deferred Terms of Sale segment specifies terms of sale. If sent, the terms must be sent exactly as on 850 PO. 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 D 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 D 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 (Invoice) (Mandatory) The Terms of Sale/Deferred Terms of Sale segment specifies terms of sale. Example: IT1*000100*1116*EA*3.75**UP* *VA*ER491 ent Name Req Type Min/Max Comments IT Assigned Identification O AN 1/20 PO Line number. IT Quantity Invoiced M R 1/10 Number of units invoiced (supplier units) IT Unit or Basis for Measurement 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 IT Product/Service Qualifier IT Product/Service IT Product/Service Qualifier M 2/2 CB Buyer Item Number M AN 9/9 Nine digit buyer item number sent on 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 U.P.C. Consumer Package Code ( ) IT Product/Service O AN 12/12 UPC Number 13
14 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 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 M N0 1/6 The number of IT1 segments present in the transaction set SE Transaction Set Trailer (Mandatory) The 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*11* 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. 14
15 EXAMPLE: ST*810*3280l BIG* *C * *J REF*IA* REF*DP*80 N1*ST**92*0033 ITD*01*3**** *60 IT1*1*2*EA*7**CB*83KN03201*VA*BP06014 IT1*2*2*EA*7**CB*83KN03401*VA*BP06014 IT1*3*3*EA*5.5**CB*80JX03601*VA*BA35001 IT1*4*3*EA*5.5**CB*80JX04021*VA*BA35001 IT1*5*3*EA*5.5**CB*80N403201*VA*BA35146 IT1*6*2*EA*7**CB*84KT04221*VA*BP02001 TDS*9150 CTT*6 SE*15*
16 850 Purchase Order Introduction This section describes mapping Information for: Standard EDI Purchase Order (850) Version 4101VICS 850 Purchase order Qualifier Type: 01 Qualifier : VAN ECOM Systems Transaction Sets Transaction sets must be enclosed in X.12 standard interchange (ISA-IEA) and functional group (GS-GE) envelopes. Segment Terminator: Carriage Return/Line Feed, Hex 0D/0A ent Separator: Asterisk Character, Hex 2A 16
17 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 N3 N4 Carrier Details erence Identification Message statement 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 17
18 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 18
19 REF erence Number M 2/3 erence Identification Qualifier PHC - Ship Mode REF erence Identification X AN 1/30 Ship Mode Description ASN Type 1 Garments on Hangers (GOH) Flow Through: Merchandise shipped bulk on hangers to be allocated directly to the stores. Case Level 2 Push/Flow Thru (Ctn) Merchandise: Merchandise shipped bulk from the vendor to be allocated directly to the stores. Case Level 3 Back Stock (Ctn) Merchandise: Merchandise shipped in bulk from the vendor to be placed on a shelf or flow rack to replenish the stores basic items. Case Level 5 Master pack/case pack Merchandise: Merchandise packed in identical musical runs. (S-1, M-2, L-2, XL-1). Case Level 6 Flat-to-Hang (Ctn) Merchandise: Merchandise shipped in a carton to be processed on hangers. Case Level 7 EDI Flat to GOH: Replenishment Merchandise to be shipped on a hanger flat packed to replenish weekly/biweekly or monthly seasonal POs Case Level 9 Garment on Hanger (GOH) Back Stock Merchandise: Merchandise shipped on hangers to be stored at the DC to replenish the stores basic items. Case Level 10 Special Orders: All merchandise ordered for a specific customer or group sale. NONE 11 Direct to Store: All merchandise to be shipped directly to the store and not the DC. Case Level 12 EDI Push (Ctn): Replenishment Merchandise to be shipped in bulk from the vendor and allocated to the stores upon receipt. Case Level 13 EDI GOH: Merchandise shipped on a hanger to replenish weekly/biweekly or monthly seasonal POs Case Level 14 Flat To Hang (Carton) Merchandise: Merchandise packed in a carton with hanger designated for backstock. er to hanger requirements on the tech pack. Mixed styles, colors and sizes in a carton ALLOWED. Hanger Direction: Goods must be packed with garment hangers facing the opposite way every six garments. Case Level 18 Drop Ship: Special Orders sent Directly to a store for a specific customer. Case Level 19 Flat Factory: Merchandise shipped in a carton specifically for the factory stores. Case Level 20 GOH Factory: Merchandise shipped on a hanger specifically for the factory stores. Case Level 21 Samples: Samples, bulk -- Sent most cost effective way with UPS. Mixed sizes in a carton ALLOWED. 22 Web/Catalog: Merchandise is shipped in bulk by supplier and is 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. Case Level 19
20 REF erence Number O 2/3 erence Identification Qualifier CO - Custom Order REF erence Identification X AN 1/30 Custom Order number REF erence Number O 2/3 erence Identification Qualifier CR Drop Ship REF erence Identification X AN 1/30 Drop Ship Order number 20
21 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 21
22 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 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 Address O AN 01/55 N Address X AN 01/55 N City Name O AN 02/30 N State or Province Code X 02/02 N Postal Code X 03/15 22
23 TD Carrier Detail Routing O AN 01/35 Carrier routing for Drop Ship UPSN UPS USPS USPS Parcel Post TD Service Level Code X 2/2 Service level code for Drop Ship CG UPS Ground 3-5 business days SE UPS 2 Day ND UPS Overnight SD Saturday Delivery CG USPS Parcel Post 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 23
24 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 24
25 P Item Description Type M 01/01 Code Identifying Item F Free Form P Description X AN 01/80 Identifying Item Description Item description 25
26 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 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 26
27 SDQ Unit or Basis for Measurement Code M 02/02 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. 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 to a customer. 27
28 CTT Number of lines Items M N0 01/06 Total number of PO1 segments 28
29 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 29
30 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*
31 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 31
32 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 32
33 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 33
34 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) 34
35 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 35
36 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) 36
37 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. 37
38 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 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 38
39 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 39
40 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 40
41 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 41
42 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 42
43 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 43
44 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 44
45 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 45
46 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 46
47 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 47
K&G System Migration EDI SPECIFICATION
K&G System Migration EDI SPECIFICATION 850 PURCHASE ORDER Version 4010VICS Qualifier Type: 12 Qualifier : 4043517987 Transaction Sets Transaction sets must be enclosed in X.12 standard interchange (ISA-IEA)
More information856 Ship Notice/Manifest Purchase Order Carton Consolidation Shipment Pick/Pack Structure
856 Ship Notice/Manifest Purchase Order Carton Consolidation Shipment Pick/Pack Structure Macy s VICS Version 4010 VICS Document Mapping Updated 10/8/10 NOTE: The POs that are Stand Alone must appear first
More information856 Ship Notice/Manifest Standard Carton Pack Structure
856 Ship Notice/Manifest Standard Carton Pack Structure Macy s VICS Version 5010 VICS Document Mapping Effective 06/12/09 The following is an outline of what is expected when receiving VICS 856 Ship Notice
More information870 Order Status Report (Version 4010) Target Corporation Common
870 Order Status Report (Version 4010) Target Corporation Common Revised: August 26, 2003 Introduction: Functional Group ID=RS This Draft Standard for Trial Use contains the format and establishes the
More informationEDI IMPLEMENTATION GUIDE FOR DOMESTIC VENDORS VALUE ADDED NETWORK: GXS INTERCHANGE ID QUAL: 12 INTERCHANGE ID #:
EDI IMPLEMENTATION GUIDE FOR DOMESTIC VENDORS VALUE ADDED NETWORK: GXS INTERCHANGE ID QUAL: 12 INTERCHANGE ID #: 2816465200 EDI DEPARTMENT: EDISupport@academy.com 1 TRANSACTION SET: 850 Purchase Order
More information856 - Ship Notice/Manifest
General Information All Ship Notice/Manifest documents must contain UCC 128 carton label information. Shipments must comply with Von Maur, Inc. routing instructions, available through the traffic department.
More informationEDI Implementation Guide 856 Advance Ship Notice Version 4010
EDI Implementation Guide 856 Advance Ship Notice Version 4010 Stores, Inc. and Subsidiaries and Affiliates 8000 Bent Branch Dr. Irving, TX 75063 (972) 409-1300 856 Ship Notice/Manifest 4010 Functional
More informationBelk Stores 810 Invoice. X12/V4030/810: 810 Invoice
Belk Stores 810 Invoice X12/V4030/810: 810 Invoice 810V4030-2 (004030VICS) 1 February 25, 2016 Belk Technical Information for 810: All EDI Transmissions are through the Inovis network VICS 810 Version
More informationVerizon Business Purchasing, LLC 856 Guide 856 Ship Notice/Manifest
856 Ship Notice/Manifest Introduction: Functional Group ID=SH This Standard for Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within
More informationEDI Specifications Guide. 856 Supplier Advance Ship Notice Last updated February 2017
856 Supplier Advance Ship Notice Last updated February 2017 856 Ship Notice/Manifest - Functional Group=SH VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents
More informationAdvance Shipment Notice Specification EDI 856
Advance Shipment Notice Specification EDI 856 This document is solely for the use of Logicbroker, Inc. personnel and its intended client. No part of it may be circulated, Quoted, or reproduced for distribution
More informationJCPenney 856 Ship Notice/Manifest Version 4030
TABLE OF CONTENTS JCPenney Mapping Differences between Versions 3060 and 4030... 1.2 Transaction Set Purpose... 1.3 Pick Pack Shipment Segment Hierarchy... 1.3 Standard Pack Shipment Segment Hierarchy...
More information856 Advance Ship Notice Segment Descriptions Transmission Data File Specifications Ansi X12 Version 4010
O Reilly / Ozark Automotive Inc. 856 ASN Implementation Guide To: Trading Partners From: Jim Edwards Date: 08/10/01 856 Advance Ship Notice Segment Descriptions Transmission Data File Specifications Ansi
More informationKOHL S INVOICE PROGRAMMER'S REFERENCE GUIDE VERSION 4010VICS. Revised: July 10, 2015
PROGRAMMER'S REFERENCE GUIDE VERSION 4010VICS Revised: July 10, 2015 Within the retail industry, there exists two uses of the retail invoice document: Detail Invoicing and Consolidated Invoicing. Kohl
More informationTSC 856 Store & DC. Message Implementation Guideline. based on. 856 Ship Notice/Manifest X
Message Guideline TSC 856 Store & DC based on 856 Ship Notice/Manifest X12 004010 Version: 1.7 Variant: 1.0 Issue date: 10/19/2015 Updated: 4/8/2016 Author: TSC 1 Message Structure... 3 3 Segments... 4
More informationACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X
ACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X12 4010 *NOTES: PLEASE REFERENCE 1 PO PER 856 TRANSACTION SET (ST-SE ENVELOPE). THE 856 SHOULD BE SENT THE SAME DAY THE ORDER IS SHIPPED. MAKE SURE ALL SHIP
More information810 - Invoice. Version: X12
810 - Invoice Version: 004010 X12 Company: DOT FOODS, INC. Publication: 12/23/2010 810 Invoice Functional Group= IN Purpose: This Draft Standard for Trial Use contains the format and establishes the data
More informationANSI X12 version Invoice
ANSI X12 version 4010 810 Invoice VERSION: 01.00.04 Author: EDI Administration Team Publication Date: 09/21/2007 Trading Partner: All Contact Information: O. C. Tanner Company EDI Administration Team 1930
More informationEDI X Implementation Guide. Advanced Ship Notice
EDI X12 004010 856 Implementation Guide Advanced Ship Notice Issued by: AM General Date: July 15, 2009 The information disclosed herein is proprietary to AM GENERAL and is not to be used or disclosed to
More information810 Invoice Functional Group=IN
810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic
More informationLOWE'S EDI. 856 Advance Ship Notice. Version:
LOWE'S EDI 856 Advance Ship Notice Version: 004010 Author: Lowes Companies, Inc. Modified: 4/3/2009 Notes: This 856 Implementation Guide is the same for all vendors submitting the ASN. Lowe's Companies,
More informationFunctional information for outbound Advance Ship Notice (ASN) EDIFACT - DESADV ANSI X12-856
Functional information for outbound Advance Ship Notice (ASN) EDIFACT - DESADV ANSI X12-856 Micron has created a standard electronic Advance Ship Notice (ASN) document format. This standard format includes
More informationDo it Best Corp. Advance Ship Notice (ASN) Guidelines
Do it Best Corp. Advance Ship Notice (ASN) Guidelines Introduction The purpose of this document is to present and explain Advance Shipment Notices (ASN s) as they pertain to shipments into a Retail Service
More informationWakefield's Advance Ship Notice 856 Documentation INTRODUCTION
Purpose of this Document Wakefield's Advance Ship Notice 856 Documentation INTRODUCTION This document was written to provide Wakefield's trading partners with a detailed guideline for sending an electronic
More information852 Product Activity Data Version 04010
1830 Route 130 North Burlington, NJ 08016 Phone: (609) 387-7800 Fax: (609) 387-2764 852 Product Activity Version 04010 Table of Content Introduction...1 ST Transaction Set Header...1 XQ Reporting Date/Action...2
More information856 Ship Notice/Manifest
856 Ship Notice/Manifest Functional Group ID=SH Introduction: KOSTAL 4010 Inbound 856 Trading Partner Specs Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010
More informationDENSO North America Supplier Web IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS
DENSO North America Supplier Web IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS SHIP NOTICE/MANIFEST TRANSACTION SET (856) VERSION/RELEASE 004010 Technical Contact: Wes Stringfield, North American
More informationKOHLER COMPANY VENDOR SHIP NOTICE LAYOUT (856) Kohler Description Number M = Mandatory O = Optional C = Conditional
ISA Field ISA Field Description M = Mandatory O = Optional C = Conditional M = Mandatory O = Optional C = Conditional ISA - Interchange Control Header ISA01 101 Authorization Info. Qualifier M ID 2/2 M
More information850 Outbound Purchase Order Macy s VICS Version 4030 VICS Document Mapping Updated 12/16/2010
850 Outbound Purchase Order Macy s VICS Version 4030 VICS Document Mapping Updated 12/16/2010 The following is an outline of what will be provided when transmitting VICS 850 Purchase Orders to a vendor.
More informationAdvanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice
Advanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice Author: Publication: Trading Partner: Notes: Seagate B2B Outbound from Seagate to trading partner Cust856 1 2012 Seagate Technology
More informationMMG 856 Inbound Ship Notice/Manifest Macy s Merchandising Group ANSI X.12 Version 4010 ANSI X.12 Document Mapping Effective 03/15/2016
MMG 856 Inbound Ship Notice/Manifest Macy s Merchandising Group ANSI X.12 Version 4010 ANSI X.12 Document Mapping Effective 03/15/2016 STANDARD CARTON PACK STRUCTURE SHIPMENT/ORDER/ITEM/PACK The following
More information850 Purchase Order VICS / GTIN
SEGMENT: ST Transaction Set Header ST01 143 Transaction Set Identifier Code 850 - Purchase order M 3/3 ST02 329 Transaction Set Control Number Control Number M 4/9 SEGMENT: BEG Beginning Segment for Purchase
More informationCSI EDI ASN 856 specification Version /21/ ASN Advance Shipping Notice. Version: ANSI X /21/2012 V 1.
Charming Technology Services EDI Specification 856 - ASN Advance Shipping Notice Version: ANSI X12 004030 07/21/2012 V 1.2 From domestic vendor to CSI From Domestic Vendors to CSI 1 of 51 Table of Content
More information810 Invoice. Version: 1.0 Final. Company: Oshkosh Corporation Publication: 9/26/2016 Currently available for ONLY JLG and McNeilus
810 Invoice Version: 1.0 Final Company: Oshkosh Corporation Publication: 9/26/2016 Notes: Currently available for ONLY JLG and McNeilus Table of Contents 810 Invoice.................................................................................................................
More informationEDI Implementation Guide for SAP ASN
EDI Implementation Guide for SAP ASN March 2015 TRANSACTION SET 856 Advanced Ship Notice ANSI X.12 Table of Contents 856 Advanced Ship Notice Usage Convention...1 ANSI X.12 Version...2 H-D EDI Qualifier
More informationElectronic Data Interchange 850 Pre-Pack Purchase Order (VICS Version ) March Powered By:
Electronic Data Interchange 850 Pre-Pack Purchase Order (VICS Version - 4010) March 2011 Powered By: Purpose This document provides detailed guidelines and conventions for implementing electronic purchase
More information856 Ship Notice/Manifest v4010
INTRODUCTION This document specifies Sears requirements for transmission of the 856 Ship Notice/Manifest transaction set. The document includes the data requirements for reporting all shipments made directly
More informationBERGEN BRUNSWIG DRUG COMPANY
810 Invoice BERGEN BRUNSWIG DRUG COMPANY Introduction: Functional Group ID=IN This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810)
More informationVDP Program Vendor Guidelines (EDI X12 version )
AutoZone Merchandising Systems Vendor Reference VDP Program Vendor Guidelines (EDI X12 version 004010) Revised by Dept. 8309 EDI group July 2007 Portions of this document contain hyperlinks that are navigable
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR PURCHASE ORDER (850) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS MOPAR DISTRIBUTOR PURCHASE ORDER (850) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 004010
More informationThis document defines the AAFES Business Requirements for the Ship Notice/Manifest.
856 Ship Notice/Manifest Functional Group ID=SH Introduction: This X12 Transaction Set contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within
More informationPittsburgh Glass Works. X Purchase Order Specifications
X-12 850 Purchase Order Specifications Contents 850 - Generic Purchase Order... 4 Introduction... 4 Heading... 4 Detail... 6 Summary... 6 Transaction Set Notes... 7 Segment: ST Transaction Set Header...
More information850 Outbound Purchase Order Federated Department Stores, Inc. (FDS) VICS Version 4030 VICS Document Mapping Revised 11/01
850 Outbound Purchase Order Federated Department Stores, Inc. (FDS) VICS Version 4030 VICS Document Mapping Revised 11/01 The following is an outline of what will be provided when transmitting VICS 850
More informationLOOP-ID SAC LOOP REPEAT 25 LOOP-ID N9 LOOP REPEAT 1000 LOOP-ID N1 LOOP REPEAT 200 LOOP-ID PO1 LOOP REPEAT LOOP-ID CTP LOOP REPEAT >1
FUNCTIONAL GROUP: PO THIS DRAFT STANDARD FOR TRIAL USE CONTAINS THE FORMAT AND ESTABLISHES THE DATA CONTENTS OF THE PURCHASE ORDER TRANSACTION SET (850) FOR USE WITHIN THE CONTEXT OF AN ELECTRONIC DATA
More informationLOOP ID - IT IT1 Baseline Item Data (Invoice) M 1 LOOP ID - SAC SAC Service, Promotion, Allowance, or Charge Information
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More informationSTERLING, INC. EDI TRADING PARTNER GUIDEBOOK. VICS Version 4010
STERLING, INC. EDI TRADING PARTNER GUIDEBOOK VICS Version 4010 Revised June 2001 TABLE OF CONTENTS CHAPTER 1 - INTRODUCTION AND OVERVIEW OF EDI 1 Software Upgrades 1 X12 Standards 1 Functional Acknowledgments
More informationEDI MAPPING SPECIFICATIONS 4010 VICS August 24, 2011 Revision
EDI MAPPING SPECIFICATIONS August 24, 2011 Revision Mapping Revisions This listing highlights the major changes in EDI Mapping Specifications. As you page through this document, you will notice text that
More informationWarehouse Shipping Advice - 945
945 Warehouse Shipping Advice - 4010 INBOUND Version: 1.0 Author: Modified: 01/15/2004 V4010 1 945 Warehouse Shipping Advice Functional Group=SW This Draft Standard for Trial Use contains the format and
More information810 Invoice. X12/V4010/810: 810 Invoice. Version: 4.0 Final
810 Invoice X12/V4010/810: 810 Invoice Version: 4.0 Final Author: John Parkhill Company: Burlington Stores, Inc. Publication: 5/3/2016 Trading Partner: Merchandise Notes: Table of Contents 810 Invoice.................................................................................................................
More informationTransaction 856. Benteler Automotive Electronic Data Interchange Specifications. Version 2.2 November 30, 2009
Benteler Automotive Electronic Data Interchange Specifications Transaction 856 Version 2.2 November 30, 2009 NAO_LO-023 Benteler Automotive 1 November 30,2009 856 Version 4010 Version 2.2 Changes from
More information204 Motor Carrier Load Tender X12 Version 4010 Outbound from Advance Auto
204 Motor Carrier Load Tender X12 Version 4010 Outbound from Advance Auto Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 2/16/16 i Publication Record Rev. Date Author
More information810 Invoice. Introduction: Notes: Heading: Detail: Functional Group ID=IN
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More information211 Motor Carrier Bill of Lading
211 Motor Carrier Bill of Lading X12/V4010/211: 211 Motor Carrier Bill of Lading Version: 1.0 Final Publication: 1/27/2009 Notes: Table of Contents 211 Motor Carrier Bill of Lading...1 ISA Interchange
More information856 Ship Notice/Manifest
856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 5.0 4010 Draft Company: itradenetwork -dc Publication: 6/19/2015 Trading Partner: itn Supplier Version Notes: Universal 856 Draft
More informationEDI Implementation Guide 850 Purchase Orders Version 4010 Effective Date: 25 July 2008
EDI Implementation Guide 850 Purchase Orders Version 4010 Effective Date: 25 July 2008 Michaels Stores, Inc. and Subsidiaries and Affiliates 8000 Bent Branch Dr. Irving, TX 75063 (972) 409-1300 850 Purchase
More informationBIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 PC TRANSACTION SET 860 VENDOR VERSION 5010
BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 PC TRANSACTION SET 860 VENDOR VERSION 5010 Summary of Changes 2012 Changes 67 N1 04 Changed length to a maximum of 5 digits SLN segment has been
More informationFunctional information for inbound EDI purchase order (PO) EDIFACT - ORDERS ANSI X12-850
Functional information for inbound EDI purchase order (PO) EDIFACT - ORDERS ANSI X12-850 In order for Micron to best automate the processing of inbound orders from our customers, we have created a standard
More information211 Motor Carrier Bill of Lading
211 Motor Carrier Bill of Lading X12/V4060/211 : 211 Motor Carrier Bill of Lading Version: 2.0 Final Author: Thomas A. Smith Company: Burlington Coat Factory Publication: 12/26/2012 Trading Partner: Notes:
More informationCaterpillar Inc. 02/11/ Electronic Invoice
Caterpillar Inc. 02/11/2010 810 Electronic Invoice PREFACE... 3 EXPLANATION OF DATA SEGMENT LAYOUTS... 4 TRANSACTION SEQUENCE WITH LEVELS... 6 ISA-INTERCHANGE CONTROL HEADER SEGMENT... 7 GS -FUNCTIONAL
More information810 Invoice. X12/V4010/810 : 810 Invoice. Version: 1.0 Final
810 Invoice X12/V4010/810 : 810 Invoice Version: 1.0 Final Author: EDI Department Company: D&H Distributors Publication: 03/01/2015 Trading Partner: Modified: 03/03/2016 Current: 03/03/2016 Notes EDI notes
More information862 Shipping Schedule
862 Shipping Schedule Functional Group ID=SS Introduction: This standard provides the format and establishes the data contents of a shipping schedule transaction set within the context of an electronic
More informationEDI Specifications Guide. 850 Supplier Purchase Order
850 Supplier Purchase Order 850 Purchase Order - Functional Group=PO VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Supplier Purchase
More informationARMY & AIR FORCE EXCHANGE SERVICE 810 Invoice
ARMY & AIR FORCE EXCHANGE SERVICE 810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set
More information10/04/2017 NORDSTROM CANADA Invoice - 810
810 NORDSTROM CANADA Invoice Functional Group=IN Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the
More information180 Return Merchandise Authorization and Notification
180 Return Merchandise Authorization and Notification Functional Group ID=AN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the return Merchandise
More informationX12 Implementation Guidelines For Outbound Purchase Order v2001 (850O)
X12 Implementation Guidelines For Outbound Purchase Order v2001 (850O) 850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the
More informationARVINMERITOR P.O.'S 850 TRANSACTION SET WILL BE UTILIZED TO COMMUNICATE CONTRACTUAL INFORMATION REGARDING PART AND PRICE
ArvinMeritor 850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850)
More informationLOOP-ID SAC LOOP REPEAT 25 LOOP-ID N9 LOOP REPEAT 1000 LOOP-ID N1 LOOP REPEAT 200 LOOP-ID PO1 LOOP REPEAT LOOP-ID CTP LOOP REPEAT >1
FUNCTIONAL GROUP: PO THIS DRAFT STANDARD FOR TRIAL USE CONTAINS THE FORMAT AND ESTABLISHES THE DATA CONTENTS OF THE PURCHASE ORDER TRANSACTION SET (850) FOR USE WITHIN THE CONTEXT OF AN ELECTRONIC DATA
More informationBriggs & Stratton. 856 Ship Notice/Manifest Version B&S 856 ASN EDI Manual
856 Ship Notice/Manifest Version 004010 B&S 856 ASN EDI Manual Revision: March 2007 856 Ship Notice/Manifest ii Table of Contents 856 Ship Notice Introduction... 3 Standard Carton Structure:... 3 856 Ship
More informationEDI Implementation Guide 860 Purchase Order Changes Version 4010 Effective Date: 25 July 2008
EDI Implementation Guide 860 Purchase Order Changes Version 4010 Effective Date: 25 July 2008 Michaels Stores, Inc. and Subsidiaries and Affiliates 8000 Bent Branch Dr. Irving, TX 75063 (972) 409-1300
More information09/25/2015 Motor Carrier Freight Details and Invoice Table of Contents
Table of Contents 210 Motor Carrier Freight Details and Invoice............................................................................................ ... 1 GS Functional Group Header...........................................................................................................
More informationNAPM RAIL INDUSTRY FORUM INVOICE IMPLEMENTATION GUIDELINE FOR EDI. Pos Id Segment Name Req Max Use Repeat Notes Usage
810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic
More information850 Inbound Purchase Order
850 Inbound Purchase Order Macy s VICS Version 4030 VICS Document Mapping Effective 06/01/07 The following is an outline of what is expected when receiving VICS 850 Purchase Orders from a vendor. For definitions
More informationNAPM RAIL INDUSTRY FORUM PURCHASE ORDER IMPLEMENTATION GUIDELINE FOR EDI
850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of
More information855 Inbound Purchase Order Acknowledgment
855 Inbound Purchase Order Acknowledgment Macy s VICS Version 4050 VICS Document Mapping Effective 06/01/07 The following is an outline of what is required when receiving VICS 855 Purchase Order Acknowledgments
More information810 Invoice ANSI X.12 Version 5010
810 Invoice SI X.12 Version 5010 *** HEADE AEA *** SEG SEGMENT EQ MAX LOOP NAME DES USE EPEAT ISA Interchange Control Header M 1 GS Functional Group Header M 1 ST Transaction Set Header M 1 BIG Beginning
More information856 Advance Ship Notice/ Supplier Implementation Guide Getting Started with EDI
856 Advance Ship Notice/ Supplier Implementation Guide Getting Started with EDI 1 Contents Introduction to EDI 856 Advance Ship Notice / 824 Application Advice...2 Introduction.. 3 What is EDI...4 What
More informationDSD Invoice TRANSACTION SET 810 VERSION 4010
DSD Invoice TRANSACTION SET 810 VERSION 4010 EDI provides an efficient means for our trading partner to submit invoices for payment. Receipt of the invoices, as well as an indication of any EDI-related
More information05/11/1998 Ingram Book Company Purchase Order INGRAM BOOK COMPANY Electronic Data Interchange Mapping Requirements PURCHASE ORDER (850)
INGRAM BOOK COMPANY Electronic Data Interchange Mapping Requirements PURCHASE ORDER (850) 1 2 850 Purchase Order Functional Group=PO This standard provides the format and establishes the data contents
More informationEDI SPECIFICATIONS 210 MOTOR FREIGHT INVOICE
TranzAct Technologies, Inc. Freight Audit and Payment EDI SPECIFICATIONS 210 MOTOR FREIGHT INVOICE 210 Motor Carrier Freight Details and Invoice Functional Group=IM Purpose: This Draft Standard for Trial
More informationElectronic Data Interchange. 850 Purchase Order. Version 4030
Electronic Interchange 850 Purchase Order Version 4030 March 2005 Table of Contents ISA Interchange Control Header... 2 GS Functional Group Header... 3 ST Transaction Set Header... 4 BEG Beginning Segment
More informationProgress Energy Company
Progress Energy Company Electronic Data Interchange 860 Implementation Guide Version 4010 September 18, 2006 I Explanation of Guide 1.0 Introduction Progress Energy Company is committed to continually
More informationMenards Implementation Guidelines
Menards Implementation Guidelines 810 Invoice 3/17/2006 Table of Contents q Menard, Inc. Electronic Commerce Information General contact and setup information you will need to properly set up Menards in
More information856 Advance Ship Notice/ Supplier Implementation Guide Getting Started with EDI
856 Advance Ship Notice/ Supplier Implementation Guide Getting Started with EDI 1 Contents Introduction to EDI 856 Advance Ship Notice / 824 Application Advice...2 Introduction.. 3 What is EDI...4 What
More information944 Warehouse Stock Transfer Receipt Advice
944 Warehouse Stock Transfer Receipt Advice Introduction: Functional Group ID=RE This Draft Standard for Trial Use contains the format and establishes the data contents of the Warehouse Stock Transfer
More information810 Invoice - v4010. Version: 1.2 X12/V4010/810. Publication: April 1, 2008 Modified: September 15, N _v1.2 (004010) Ver 1.
Invoice - 810 810 Invoice - v4010 X12/V4010/810 Version: 1.2 Author: OpenText Publication: April 1, 2008 Modified: September 15, 2015 N8104010_v1.2 (004010) Ver 1.2 Page 1 Invoice - 810 Revision History
More information211 Motor Carrier Bill of Lading
211 Motor Carrier Bill of Lading X12/V4010/211 : 211 Motor Carrier Bill of Lading Version: 4.0 Final Author: Thomas A. Smith Company: Burlington Stores Publication: 10/24/2014 Trading Partner: Carrier
More information846 Inventory Availability
846 Inventory Availability X12/V4010/846: 846 Inventory Availability Version: 4.0 Final Author: John Parkhill Company: Burlington Stores Publication: 6/16/2017 Trading Partner: Direct to Consumer Notes:
More information945 Warehouse Shipping Advice
945 Warehouse Shipping Advice Functional Group ID=SW Introduction: This transaction set is used to confirm shipment of product from a public warehouse. The transaction should always include the full order
More informationEDI SPECIFICATIONS 4050 VICS VERSION
EDI SPECIFICATIONS 4050 VICS VERSION OCTOBER 10, 2017 TABLE OF CONTENTS 1 OVERVIEW OF CURRENT REVISIONS... 2 2 CONTACTS... 3 3 EDI IMPLEMENTATION... 4 SFA INBOUND DOCUMENTS... 4 SFA OUTBOUND DOCUMENTS...
More informationMMG 850 Outbound Purchase Order SUPPLIER ANSI X.12 Version 4030 Effective 03/15/2016
MMG 850 Outbound Purchase Order The following is an outline of what will be required when transmitting ANSI X.12 850 Purchase Orders to a Supplier. For definitions of the segments, please see the ANSI
More informationCSI EDI PO 850 specification Version /28/2011. Version: ANSI X /28/2011 V 1.1. From CSI TO Domestic 3PL
Charming Technology Services EDI Specification 850 Purchase Order Version: ANSI X12 004030 09/28/2011 V 1.1 From CSI TO Domestic 3PL From CSI to Domestic 3PL 1 of 32 Table of Content Introduction: 850
More informationThe Marmaxx Group EDI Purchase Order Transaction set 850 Version 4010
The Marmaxx Group EDI Purchase Order Transaction set 850 Version 4010 Contacts: EDI Project Leader Doug Davies (508) 475-8221 doug_davies@tjx.com EDI Analyst Wayne Harrison (508) 475-8255 wayne_harrison@tjx.com
More informationEDI Specifications Version 4010 / Transaction Set 820 Payment Order/Remittance Advice
EDI Specifications Version 4010 / Transaction Set 820 Payment Order/Remittance Advice Copyright 1995-2003 Transportation Solutions Inc; all rights reserved. This document and all intellectual property
More information210 Motor Carrier Freight Details and Invoice
210 Motor Carrier Freight Details and Invoice X12/V4010/210: 210 Motor Carrier Freight Details and Invoice Version: 2.0 Author: Charles Mackey Company: Publication: 2/27/2018 Trading Partner: Modified:
More informationIntroduction: Heading: Detail: Transaction Set Notes. Functional Group ID=RG
754 Routing Instructions Functional Group ID=RG Introduction: This X12 Transaction Set contains the format and establishes the data contents of the Routing Instructions Transaction Set (754) for use within
More informationFILE LAYOUT FOR 855 EDI TRANSACTION (OUTBOUND)
FILE LAYOUT FOR 855 EDI TRANSACTION (OUTBOUND) VERSION 4010 Page 1 of 29 OVERVIEW PURPOSE OF TRANSACTION Inbound (Hubbell to Trading Partner) Purchase Order Acknowledgement VERSION Version 1 SUPPLIER Hubbell
More informationVerizon Business Purchasing, LLC 855 Guide 855 Purchase Order Acknowledgment
855 Purchase Order Acknowledgment Introduction: Functional Group ID=PR This Standard contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) for
More informationMessage Implementation Guideline for JIS suppliers MBUSI_003050_856. based on. 856 Ship Notice/Manifest X
Message Guideline for JIS suppliers MBUSI_003050_856 based on 856 Ship Notice/Manifest X12 003050 Version 1.2: 22-JUL-2016 Note This document is an EDI specification guideline for JIS suppliers to implement
More informationX12 Implementation Guidelines For. Inbound Primary Metals Advance Ship Notice V002002FORD. (856i Primary Metals)
X12 Implementation Guidelines For Inbound Primary etals Advance Ship Notice V002002FORD (856i Primary etals) FD856PI (002002FORD) 1 January 6, 2010 856 Ship Notice/anifest Functional Group ID=SH Introduction:
More information