EDI Specifications Guide. 855 Customer Purchase Order Acknowledgement

Similar documents
EDI Specifications Guide. 855 Supplier Purchase Order Acknowledgement. Last Update May 2016

EDI Specifications Guide. 832 Customer Price Sales Catalog

EDI Specifications Guide. 856 Customer Advance Ship Notice

855 Purchase Order Acknowledgment. United Natural Foods

HCHETTE BOOK GROUP USA 855 Purchase Order Acknowledgement VERSION 4010 IMPLEMENTATION GUIDE

RCI 855 Purchase Order Acknowledgment

850 Purchase Order. X12/V4010/850: 850 Purchase Order

ANSI X (Purchase Order) Inbound (to Eclipse) Version 4010

855 Purchase Order Acknowledgment

ANSI X (Purchase Order Acknowledgment) Inbound (to Eclipse) Version 4010

855 Purchase Order Acknowledgement v Supplier to Hubbell Inbound Transaction

810 IBM Subset - Invoice To Customer - (004010)

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes:

855 Purchase Order Acknowledgment

850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Company: JR Simplot Company Publication: 6/1/2016 Notes:

846 Inventory Inquiry/Advice

850 Purchase Order X12 Version Version: 2.0

860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0

Amazon Purchase Order Acknowledgment

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

844 Product Transfer Account

evo.com 855 Purchase Order Acknowledgment Author: SPS Commerce Company: evo.com Trading Partner: Created: 3/8/2013 Modified: 8/9/2017 Notes:

867 Product Transfer and Resale Report Functional Group=PT

ANSI X (Purchase Order Acknowledgment) Outbound (from Eclipse) Version 4010

Baker & Taylor 850 EDI Specifications

Golfsmith 846 EDI Guidelines

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008

GovX Purchase Order. X12/V5010/850: 850 Purchase Order

846 RAPID Inventory Inquiry/Advice Standard

Orchard Supply Hardware Direct to Consumer 850 Purchase Order

855 Purchase Order Acknowledgement X12/V4010/855: 855 Purchase Order Acknowledgement Version: 1.1

846 Inventory Inquiry/Advice. X12/V5010/846: 846 Inventory Inquiry/Advice

LOOP ID - PO PO1 Baseline Item Data M 1 N2/ REF Reference Identification O >1

849 Response to Product Transfer

850 Delhaize America Direct Store Delivery CAO Purchase Order Version 5010

860 Purchase Order Change Request - Buyer Initiated

849 Response to Product Transfer Account Adjustment

860 Purchase Order Change Request - Buyer Initiated

850 Purchase Order - v4030

EDI Guideline. Version: 2.2. X12/V4010/832 : 832 Price/Sales Catalog. Publication: 1/21/2019 Trading Partner: Quebec EDI Healthcare Program

867 Bill Back itradenetwork OMS

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

ANSI X (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010

855 Purchase Order Acknowledgment

846 Inventory Inquiry / Advice _Outbound

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

12/19/2017 Purchase Order Acknowledgment - 855

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

870 Order Status Report

ESIS. EDI Implementation Guide. Purchase Order Change X Version 4010 Release 8.0. EDI_Guide_Change_Order_X12_860_Version_4010_Release_8-0.

846 Inventory Inquiry/Advice

850 Purchase Order. X12/V4010/850: 850 Purchase Order

855 Purchase Order Acknowledgment

810 Invoice. Version: 1.0 Final. X12/V4010/810: 810 Invoice. Company: Baker & Taylor Modified: 10/26/2010 Notes:

Product Transfer and Resale Report - 867

867 Product Transfer and Resale Report

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 865 VERSION 4010 FROM SUPPLIER. Document version 1.5

Oshkosh 860 Purchase Order Change Request - Buyer Initiated

832 Price/Sales Catalog

855 Purchase Order Acknowledgment

861 Receiving Advice/Acceptance Certificate

Transaction Set 850 Version 4010VICS, Electronic Purchase Order

850 Purchase Order

860 Purchase Order Change v.4 (4010) Hubbell to Supplier Outbound Transaction

870 Order Status Report

JR Simplot Corporate 810 Invoice

846 Inventory Inquiry/Advice

Plex Systems IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS. 830 TRANSACTION SET MATERIAL RELEASE Version Revised November 18, 2009

850 Purchase Order. Version: X12

832 Price/Sales Catalog

Oshkosh 855 Purchase Order Acknowledgment

Inbound ANSI X Version 04010

CVS/Caremark. Implementation Guide. 810 DSD Invoice. Version X

Purchase Order Change Request - Buyer Initiated

830 Planning Schedule with Release Capability

875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

855 Purchase Order Acknowledgment

ELECTRONIC DATA INTERCHANGE. Implementation Guidelines Outbound Purchase Order

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI

846 Inventory Inquiry/Advice

Purchase Order Specification EDI 850

Purchase Order Acknowledgement Specification EDI 855

ISA*00* *00* *01* *01* *920713* 1550*U*00200* *0*P*.> GS*PR* * *920713*1550*2*X*002003

JR Simplot Food Group Purchase Order Acknowledgment

EDI Implementation Guide Version

ANSI X (Advance Shipment Notification) Inbound (to Eclipse) Version 4010

7/4/2011 Page 1 Retek850.xls

940 Warehouse Shipping Order

Invoice Specification EDI 810

846 Inventory Inquiry/Advice

Purchase Order Acknowledgement Specification EDI 855

810 Invoice. X12/V4010/810 : 810 Invoice Version: 2.0 Final

EDI Implementation Guide Version

846 Inventory Inquiry/Advice

850 Purchase Order Version 4010

830 - Material Release VERSION: 1.2

CVS/Caremark. Implementation Guide. 830 Planning Schedule with Release Capability. Version X

Transcription:

855 Customer Purchase Order Acknowledgement

855 Purchase Order Acknowledgement- Functional Group=PR VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer Purchase Order Acknowledgement Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI) environment. Please refer to the EDI Services Guide for additional information. All information contained herein is subject to change at the discretion of Fisher Scientific Company, L.L.C. Heading: Pos Id Segment Name Req Max Use Repeat Notes 010 ST Transaction Set Header M 1 020 BAK Beginning Segment for Purchase Order M 1 Acknowledgment 050 REF Reference Identification O >1 060 PER Administrative Communications Contact O 3 LOOP ID - N1 200 300 N1 Name O 1 310 N2 Additional Name Information O 2 320 N3 Address Information O 2 330 N4 Geographic Location O 1 Detail: Pos Id Segment Name Req Max Use Repeat Notes LOOP ID - PO1 100000 010 PO1 Baseline Item Data O 1 N2/010 040 CTP Pricing Information O >1 LOOP ID - PID 1000 050 PID Product/Item Description O 1 LOOP ID - ACK 104 270 ACK Line Item Acknowledgment O 1 LOOP ID - PKG 200 303 PKG Marking, Packaging, Loading O 1 LOOP ID - SCH 200 310 SCH Line Item Schedule O 1 N2/310 www.fisherwebservices.com Page 2

Summary: Pos Id Segment Name Req Max Use Repeat Notes LOOP ID - CTT 1 010 CTT Transaction Totals O 1 N3/010 030 SE Transaction Set Trailer M 1 Notes: 2/010 PO102 is required. 2/310 The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of measurement code in the associated PO1 segment (PO103) and the sum of values of quantity (SCH01) should always equal the quantity ordered (PO102) in the PO1 segment. 3/010 The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment. www.fisherwebservices.com Page 3

ST Transaction Set Header Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 To indicate the start of a transaction set and to assign a control number Ref Id Element Name Req Type Min/Max ST01 143 Transaction Set Identifier Code M ID 3/3 855 Purchase Order Acknowledgement ST02 329 Transaction Set Control Number M AN 4/9 Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). www.fisherwebservices.com Page 4

BAK Beginning Segment for Purchase Order Acknowledgment Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 6 To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates Ref Id Element Name Req Type Min/Max BAK01 353 Transaction Set Purpose Code M ID 2/2 00 Original BAK02 587 Acknowledgment Type AC Acknowledge - With Detail and Change AD Acknowledge - With Detail,No Change AE Acknowledge - With Exception Detail Only AK Acknowledge - No Detail or Change M ID 2/2 BAK03 324 Purchase Order Number M AN 1/22 BAK04 373 Date M DT 8/8 BAK05 328 Release Number O AN 1/30 BAK08 127 Reference Identification O AN 1/30 Semantics: 1. BAK04 is the date assigned by the purchaser to purchase order. 2. BAK08 is the seller's order number. www.fisherwebservices.com Page 5

REF Reference Identification Pos: 050 Max: >1 Heading - Optional Loop: N/A Elements: 3 To specify identifying information Ref Id Element Name Req Type Min/Max REF01 128 Reference Identification Qualifier M ID 2/3 RE Release Number RQ Purchase Requisition Number REF02 127 Reference Identification C AN 1/30 REF03 352 Description C AN 1/80 Syntax: 1. R0203 -- At least one of REF02 or REF03 is required. www.fisherwebservices.com Page 6

PER Administrative Communications Contact Pos: 060 Max: 3 Heading - Optional Loop: N/A Elements: 4 To identify a person or office to whom administrative communications should be directed Ref Id Element Name Req Type Min/Max Notes PER01 366 Contact Function Code M ID 2/2 N/366 BD Buyer Name or Department OC Order Contact PER02 93 Name O AN 1/60 PER03 365 Communication Number Qualifier TE Telephone C ID 2/2 PER04 364 Communication Number C AN 1/80 Syntax: 1. P0304 -- If either PER03 or PER04 are present, then the others are required. Notes: N/366 Please refer to EDI Services Guide for additional requirements. www.fisherwebservices.com Page 7

N1 Name EDI Specifications Guide Pos: 300 Max: 1 Heading - Optional Loop: N1 Elements: 4 To identify a party by type of organization, name, and code Ref Id Element Name Req Type Min/Max N101 98 Entity Identifier Code M ID 2/3 BY Buying Party (Purchaser) N102 93 Name C AN 1/60 N103 66 Identification Code Qualifier 91 Assigned by Seller or Seller's Agent C ID 1/2 N104 67 Identification Code C AN 2/80 Syntax: 1. R0203 -- At least one of N102 or N103 is required. 2. P0304 -- If either N103 or N104 are present, then the others are required. Comments: 1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2. N105 and N106 further define the type of entity in N101. www.fisherwebservices.com Page 8

N2 Additional Name Information Pos: 310 Max: 2 Heading - Optional Loop: N1 Elements: 2 To specify additional names or those longer than 35 characters in length Ref Id Element Name Req Type Min/Max N201 93 Name M AN 1/60 N202 93 Name O AN 1/60 www.fisherwebservices.com Page 9

N3 Address Information Pos: 320 Max: 2 Heading - Optional Loop: N1 Elements: 2 To specify the location of the named party Ref Id Element Name Req Type Min/Max N301 166 Address Information M AN 1/55 N302 166 Address Information O AN 1/55 www.fisherwebservices.com Page 10

N4 Geographic Location Pos: 330 Max: 1 Heading - Optional Loop: N1 Elements: 3 To specify the geographic place of the named party Ref Id Element Name Req Type Min/Max N401 19 City Name O AN 2/30 N402 156 State or Province Code O ID 2/2 N403 116 Postal Code O ID 3/15 Syntax: 1. C0605 -- If N406 is present, than N405 is required Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada. www.fisherwebservices.com Page 11

PO1 Baseline Item Data Pos: 010 Max: 1 Detail - Optional Loop: PO1 Elements: 8 To specify basic and most frequently used line item data Ref Id Element Name Req Type Min/Max PO101 350 Assigned Identification O AN 1/20 PO102 330 Quantity Ordered C R 1/15 PO103 355 Unit or Basis for Measurement Code CA Case EA Each GR Gross PC Piece PK Pack (PAK) O ID 2/2 PO104 212 Unit Price C R 1/17 PO106 235 Product/Service ID Qualifier VC Vendor's (Seller's) Catalog Number C ID 2/2 PO107 234 Product/Service ID C AN 1/48 PO108 235 Product/Service ID Qualifier CB Buyer's Catalog Number C ID 2/2 PO109 234 Product/Service ID C AN 1/48 Syntax: 1. C0302 -- If PO103 is present, than PO102 is required 2. C0504 -- If PO105 is present, than PO104 is required 3. P0607 -- If either PO106 or PO107 are present, then the others are required. 4. P0809 -- If either PO108 or PO109 are present, then the others are required. Comments: 1. See the Data Element Dictionary for a complete list of IDs. 2. PO101 is the line item identification. 3. PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU. www.fisherwebservices.com Page 12

CTP Pricing Information Pos: 040 Max: >1 Detail - Optional Loop: PO1 Elements: 4 To specify pricing information Ref Id Element Name Req Type Min/Max CTP02 236 Price Identifier Code C ID 3/3 CON Contract Price CTP03 212 Unit Price C R 1/17 CTP04 380 Quantity C R 1/15 CTP05 C001 Composite Unit of Measure C Comp 355 Unit or Basis for Measurement Code CA Case EA Each GR Gross PC Piece PK Pack (PAK) M ID 2/2 1018 Exponent O R 1/15 649 Multiplier O R 1/10 Syntax: 1. P0405 -- If either CTP04 or CTP05 are present, then the others are required. Comments: 1. See Figures Appendix for an example detailing the use of CTP03 and CTP04. 2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07. www.fisherwebservices.com Page 13

PID Product/Item Description Pos: 050 Max: 1 Detail - Optional Loop: PID Elements: 2 To describe a product or process in coded or free-form format Ref Id Element Name Req Type Min/Max PID01 349 Item Description Type M ID 1/1 F Free-form PID05 352 Description C AN 1/80 Syntax: 1. R0405 -- At least one of PID04 or PID05 is required. Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used. www.fisherwebservices.com Page 14

ACK Line Item Acknowledgment Pos: 270 Max: 1 Detail - Optional Loop: ACK Elements: 6 To acknowledge the ordered quantities and specify the ready date for a specific line item Ref Id Element Name Req Type Min/Max ACK01 668 Line Item Status Code M ID 2/2 IA Item Accepted IB Item Backordered IP Item Accepted - Price Changed IR Item Rejected IS Item Accepted - Substitution Made ACK02 380 Quantity C R 1/15 ACK03 355 Unit or Basis for Measurement Code CA Case EA Each GR Gross PC Piece PK Pack (PAK) ACK04 374 Date/Time Qualifier 011 Shipped 017 Estimated Delivery C ID 2/2 O ID 3/3 ACK05 373 Date C DT 8/8 ACK07 235 Product/Service ID Qualifier VC Vendor's (Seller's) Catalog Number C ID 2/2 ACK08 234 Product/Service ID C AN 1/48 Syntax: 1. P0203 -- If either ACK02 or ACK03 are present, then the others are required. 2. C0405 -- If ACK04 is present, than ACK05 is required 3. P0708 -- If either ACK07 or ACK08 are present, then the others are required. www.fisherwebservices.com Page 15

PKG Marking, Packaging, Loading Pos: 303 Max: 1 Detail - Optional Loop: PKG Elements: 5 To describe marking, packaging, loading, and unloading requirements Ref Id Element Name Req Type Min/Max PKG01 349 Item Description Type C ID 1/1 F Free-form PKG02 753 Packaging Characteristic Code O ID 1/5 PKG03 559 Agency Qualifier Code C ID 2/2 PKG04 754 Packaging Description Code C AN 1/7 PKG05 352 Description C AN 1/80 Syntax: 1. R040506 -- At least one of PKG04, PKG05 or PKG06 is required. 2. C0403 -- If PKG04 is present, than PKG03 is required 3. C0501 -- If PKG05 is present, than PKG01 is required Semantics: 1. PKG04 should be used for industry-specific packaging description codes. Comments: 1. Use the MEA (Measurements) Segment to define dimensions, tolerances, weights, counts, physical restrictions, etc. 2. If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used. 3. Use PKG03 to indicate the organization that publishes the code list being referred to. 4. Special marking or tagging data can be given in PKG05 (description). www.fisherwebservices.com Page 16

SCH Line Item Schedule Pos: 310 Max: 1 Detail - Optional Loop: SCH Elements: 4 To specify the data for scheduling a specific line-item Ref Id Element Name Req Type Min/Max SCH01 380 Quantity M R 1/15 SCH02 355 Unit or Basis for Measurement Code CA Case EA Each GR Gross PC Piece PK Pack (PAK) SCH05 374 Date/Time Qualifier 017 Estimated Delivery M ID 2/2 M ID 3/3 SCH06 373 Date M DT 8/8 Syntax: 1. C0304 -- If SCH03 is present, than SCH04 is required Comments: 1. SCH05 specifies the interpretation to be used for SCH06 and SCH07. www.fisherwebservices.com Page 17

CTT Transaction Totals Pos: 010 Max: 1 Summary - Optional Loop: CTT Elements: 2 To transmit a hash total for a specific element in the transaction set Ref Id Element Name Req Type Min/Max CTT01 354 Number of Line Items M N0 1/6 CTT02 347 Hash Total O R 1/10 Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness. www.fisherwebservices.com Page 18

SE Transaction Set Trailer Pos: 030 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Ref Id Element Name Req Type Min/Max SE01 96 Number of Included Segments M N0 1/10 SE02 329 Transaction Set Control Number M AN 4/9 Comments: 1. SE is the last segment of each transaction set. www.fisherwebservices.com Page 19

Below is a complete example of an 855 transmission: ISA*00* *00* *14*004321519IBMP *ZZ*7777777777 *070920*1122*U*00401*000396783*0*P*> GS*PR*004321519*7777777777*20070920*1122*396783*X*004010 ST*855*562330 BAK*00*AD*1114204*20070920****72635386 N1*BY*SPECIAL LABS*91*999999001 N3*1000 PENNSYLVANIA AVE N4*PITTSBURGH*PA*15222 N1*BT*SPECIAL LABS*92*999999001 N1*ST*SPECIAL LABS*91*999999001 N1*VN*FISHER SCIENTIFIC PO1*1*1*PK*80.5**VC*1230345*CB*1230345 PID*F****TRIAGE DOA PANEL 25/PK ACK*IA*1*PK*017*20070926*CDC*VC*1230345 SCH*1*PK***017*20070926 CTT*1*1 SE*14*562330 GE*1*396783 IEA*1*000396783 www.fisherwebservices.com Page 20