HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

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

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

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

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

Orchard Supply Hardware Direct to Consumer 850 Purchase Order

850 Purchase Order

830W (R1) War Material Requirements 830 Planning Schedule with Release Capability

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

846 RAPID Inventory Inquiry/Advice Standard

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

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

850 Purchase Order. Version: X12

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

870 Order Status Report

850 Purchase Order X12/V4010/850 Version: 1.0 Company: JR Simplot Company Modified: 11/24/2015 Notes:

830 Planning Schedule with Release Capability

JR Simplot Corporate 810 Invoice

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

RCI 855 Purchase Order Acknowledgment

Inbound ANSI X Version 04010

850 Purchase Order - v4030

Baker & Taylor 850 EDI Specifications

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

855 Purchase Order Acknowledgment. United Natural Foods

870 Order Status Report

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

832 Price/Sales Catalog

810 IBM Subset - Invoice To Customer - (004010)

An example of a paper copy Planning Schedules with Release Capability and its ASC X12 interpretation can be found at the back of this guideline.

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

Oshkosh 860 Purchase Order Change Request - Buyer Initiated

860 Purchase Order Change Request - Buyer Initiated

855 Purchase Order Acknowledgement v Supplier to Hubbell Inbound Transaction

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

COMMUNICATION ID S. Strouds Voice (626) South Nogales St. City of Industry, Ca Fax (626)

846 Inventory Inquiry/Advice

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

Product Transfer and Resale Report - 867

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

JR Simplot Food Group Purchase Order Acknowledgment

812 Credit/Debit Adjustment

Purchase Order Change Request - Buyer Initiated

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

12/19/2017 Purchase Order Acknowledgment - 855

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

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

867 Product Transfer and Resale Report Functional Group=PT

860 Purchase Order Change Request - Buyer Initiated

855 Purchase Order Acknowledgment

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

867 Bill Back itradenetwork OMS

940 Warehouse Shipping Order

Inbound X Version 04010

844 Product Transfer Account

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

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

846 Inventory Inquiry/Advice

JR Simplot Agribusiness Ship Notice/Manifest

7/4/2011 Page 1 Retek850.xls

810 Invoice Service Parts Version:

816 Organizational Relationships

850 Purchase Order. X12/V4010/850 : 850 Purchase Order Version: 2.0 Final

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

855 Purchase Order Acknowledgment

850 Purchase Order X12 Version Version: 2.0

Zappos EDI Guideline. X12/V4010/860: 860 Purchase Order Change Request - Buyer Initiated. Version: 1.0

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

862 Shipping Schedule

850 Purchase Order. Version: 1.0 Final. X12/V4010/850 : 850 Purchase Order. Advance Auto Parts

870 Order Status Report

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

Transaction Set 849 Response to Product Transfer Account Adjustment

816 Organizational Relationships

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

Electronic Data Interchange 832 Price/Sales Catalog (VICS Version ) March Powered By:

Transaction Set 850 Version 4010VICS, Electronic Purchase Order

861 Receiving Advice/Acceptance Certificate

Introduction: Heading: Detail: Summary: Functional Group ID=TX

830 Planning Schedule with Release Capability

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

850 Purchase Order Version 4010

849 Response to Product Transfer

824 Application Advice

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

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

ANSI X (Advance Shipment Notification) Outbound (from Eclipse) Version 4010

ANSI X12 version Receiving Advice/ Acceptance Certificate

850 Purchase Order. X12/V4010/850: 850 Purchase Order. Version: 2.5 Final

879 - Price Information

EDI Specifications Guide. 832 Customer Price Sales Catalog

Zappos EDI Guideline. ANSI X Purchase Order. Version: 1.0

Oshkosh 855 Purchase Order Acknowledgment

852 Product Activity Data Functional Group=PD

EDI Guidelines for Purchase Order (850) v. 4010

EDI Specifications Guide. 856 Customer Advance Ship Notice

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

Amazon Purchase Order Acknowledgment

832 Price/Sales Catalog

831 Application Control Totals

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

Transcription:

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 400 IMPLEMENTATION GUIDE

Purchase Order 850 Functional Group PO 400 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 Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information. Heading POS. NO. SEG. ID NAME REQ. MAX USE LOOP REPEAT 00 ST Transaction Set Header M 020 BEG Beginning Segment for Purchase Order M Not Used 040 CUR Currency O Not Used 050 REF Reference Identification O > Not Used 060 PER Administrative Communications Contact O 3 Not Used 080 FOB F.O.B. Related Instructions O > Not Used 090 CTP Pricing Information O > Not Used 0 CSH Sales Requirements O 5 LOOP ID - SAC 25 Not Used 20 SAC Service, Promotion, Allowance, or Charge Information O Not Used 25 CUR Currency O Not Used 30 ITD Terms of Sale/Deferred Terms of Sale O 5 Used 50 DTM Date/Time Reference O 0 Not Used 90 PID Product/Item Description O 200 Not Used 240 TD5 Carrier Details (Routing Sequence/Transit Time) O 2 LOOP ID - N9 000 Not Used 295 REF Reference Identification O Not Used 300 MSG Message Text O 000 LOOP ID - N 200 30 N Name O Not Used 320 N2 Additional Name Information O 2 Not Rec'd 330 N3 Address Information O 2 Not Rec'd 340 N4 Geographic Location O > Detail POS. NO. SEG. ID NAME REQ. MAX USE LOOP REPEAT LOOP ID - PO 00000 00 PO Baseline Item Data M Not Used 020 CUR Currency O LOOP ID - CTP > Not Used 040 CTP Pricing Information O Not Used 043 CUR Currency O LOOP ID - PID 000 Not Rec'd 050 PID Product/Item Description O Not Used 060 MEA Measurements O 0 Not Used 090 PO4 Item Physical Details O > Not Used 40 IT8 Conditions of Sale O Not Used 90 SDQ Destination Quantity O 500 Not Used 20 DTM Date/Time Reference O 0 Summary PAGE POS. NO. SEG. ID NAME REQ. MAX USE LOOP REPEAT LOOP ID - CTT 00 CTT Transaction Totals O Not Used 020 AMT Monetary Amount O 030 SE Transaction Set Trailer M 2

Segment: ST Transaction Set Header Table/ Position / 00 Mandatory Purpose: To indicate the start of a transaction set and to assign a control number. Semantic:. The transaction set identifier (ST0) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 80 selects the Invoice Transaction Set). Data Element Summary ST0 43 Transaction Set Header Identifier Code M/Z ID 3/3 Code uniquely identifying a Transaction Set 850 X2. Purchase Order ST02 329 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 3

Segment: BEG Beginning Segment for Purchase Order Table/ Position / 020 Mandatory Purpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates Semantic:. BEG05 is the date assigned by the purchaser to purchase order. Data Element Summary Not Used remove remove remove BEG0 353 Transaction Set Purpose Code M ID 2/2 Code identifying purpose of transaction set Use of any code value other than '00' requires trading partner agreement. 00 Original 0 Cancellation 07 Duplicate BEG02 92 Purchase Order Type Code M ID 2/2 Code specifying the type of Purchase Order BEG03 324 Purchase Order Number M AN /22 Identifying number for Purchase Order assigned by the orderer/purchaser BEG04 328 Release Number O AN /30 Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction BEG05 373 Date M/Z DT 8/8 Date (CCYYMMDD) BEG06 367 Contract Number O AN /30 Contract Number BEG07 587 Acknowledgment Type O ID 2/2 Code specifying the type of acknowledgment BEG08 09 Invoice Type Code O ID 3/3 Code defining the method by which invoices are to be processed 4

Segment: DTM Date/Time Reference Table/ Position / 50 Optional 0 Purpose: To specify pertinent dates and times Syntax:. R020306 - At least one of DTM02, DTM03 or DTM06 is required. Data Element Summary Not Used Not Used Not Used Not Used DTM0 374 Date/ Time Qualifier M ID 3/3 Code specifying type of date or time, or both date and time 00 Requested Ship 037 Ship Not Before 038 Ship No Later 077 Requested for Delivery (Week of) 087 Requested for Shipment (Week of) 75 Cancel if not shipped by DTM02 373 Date X DT 8/8 Date (CCYYMMDD) DTM03 337 Time X TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) DTM04 623 Time Code O ID 2/2 Code identifying the time. In accordance with International Standards Organization standard 860, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow DTM05 250 Date Time Period Format Qualifier X ID 2/3 Code indicating the date format, time format, or date and time format DTM06 25 Date Time Period X AN /35 Expression of a date, a time, or range of dates, times or dates and times 5

Segment: N Name Table/ Position / 30 N Optional Purpose: To identify a party by type of organization, name, and code Syntax:. R0203 - At least one of N02 or N03 is required. 2. P0304 - If either N03 or N04 is present, then the other is required. Comments:. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N04) must provide a key to the table maintained by the transaction processing party. Data Element Summary Not Recommended Recommended Recommended N0 98 Entity Identifier Code M ID 2/2 Code identifying an organizational entity, a physical location, or an individual N02 93 Name X AN /35 Free-form name N03 66 Identification Code Qualifier X ID /2 Code designating the system/method of code structure used for Identification Code (67) D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix 2 Telephone Number (Phone) Recommended by the book industry. N04 67 Identification Code X AN 2/20 Code identifying a party or other code 6

Segment: N3 Address Information Table/ Position / 330 Optional 2 Purpose: To specify the location of the named party Data Element Summary N30 66 Address Information M AN /35 Address Information N302 66 Address Information O AN /35 Address Information 7

Segment: N4 Geographic Location Table/ Position / 340 Optional > Purpose: To specify the geographic place of the named party Syntax:. C0605 - If N406 is present, then N405 is required. Comments:. N402 is required only if city name (N40) is in the U.S. or Canada. Data Element Summary N40 9 City Name O AN 2/30 Free-form text for city name N402 56 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency N403 6 Postal Code O ID 3/5 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N404 26 Country Code O ID 2/3 Code identifying the country 8

Segment: PO Baseline Item Data Table/ Position 2/ 00 PO Mandatory Purpose: To specify basic and most frequently used line item data Syntax:. C0302 - If PO03 is present, then PO02 is required. 2. C0504 - If PO05 is present, then PO04 is required. 3. P0607 - If either PO06 or PO07 is present, then the other is required. 4. P0809 - If either PO08 or PO09 is present, then the other is required. 5. P0 - If either PO0 or PO is present, then the other is required. 6. P23 - If either PO2 or PO3 is present, then the other is required. 7. P45 - If either PO4 or PO5 is present, then the other is required. Comments:. See the Data Element Dictionary for a complete list of IDs. 2. PO0 is the line item identification. 3. PO06 through PO5 provide for different product/service IDs per each item. For example: UPC No., ISBN No., or SKU. Data Element Summary Recommended PO0 350 Assigned Identification O AN /20 Alphanumeric characters assigned for differentiation within a transaction set If used, this element should be unique within the PO segments in this transaction. For example the purchase order line item number. PO02 330 Quantity Ordered X R /9 Quantity Ordered PO03 355 Unit or Basis for Measurement Code O ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken CA Case Note: For non-book items CT Carton EA Each Note: For non-book items ST Set UN Unit PO04 22 Unit Price X R /7 Price per unit of product, service, commodity, etc. PO05 639 Basis of Unit Price Code O ID 2/2 Code identifying the type of unit price for an item Standard Book Industry definitions should be applied to this element. CA Catalog CT Contract NC No Charge NT Net PE Price per Each PR Promotion SR Suggested Retail PO06 235 Product/ Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) CB Buyer's Catalog Number EN European Article Number (EAN) (2-5-5-) IB International Standard Book Number (ISBN) The ISBN is the preferred product identifier. UP U.P.C. Consumer Package Code (-5-5-) VN Vendor's Item Number PO07 234 Product/ Service ID X AN /40 Identifying number for a product or service PO08 235 Product/ Service ID Qualifier X ID 2/2 9

Code identifying the type/source of the descriptive number used in Product/Service ID (234) Refer to code list specified in 'PO06' for usage. PO09 234 Product/ Service ID X AN /40 Identifying number for a product or service PO0 235 Product/ Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Refer to code list specified in 'PO06' for usage. PO 234 Product/ Service ID X AN /40 Identifying number for a product or service PO2 235 Product/ Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive Refer to code list specified in 'PO06' for usage. PO3 234 Product/ Service ID X AN /40 Identifying number for a product or service PO4 235 Product/ Service ID Qualifier X ID 2/2 Code identifying the type/source of the descriptive number used in Product/Service ID (234) Refer to code list specified in 'PO06' for usage. PO5 234 Product/ Service ID X AN /40 Identifying number for a product or service 0

Segment: PID Product/Item Description Table/ Position 2/ 050 PID Optional Not Recommended Purpose: To describe a product or process in coded or free-form format Syntax:. C0403 - If PID04 is present, then PID03 is required. 2. R0405 - At least one of PID04 or PID05 is required. Semantic:. Use PID03 to indicate the organization that publishes the code list being referred to. 2. PID04 should be used for industry-specific product description codes. Comments:. If PID0 equals "F", then PID05 is used. If PID0 equals "S", then PID04 is used. If PID0 equals "X", then both PID04 and PID05 are used. Notes: This segment is primarily used by the library community to order titles that have not yet been assigned an ISBN. Data Element Summary PID0 349 Item Description Type M ID / Code indicating the format of a description PID02 750 Product/ Process Characteristic Code O ID 2/3 Code identifying the general class of a product or process characteristic PID03 559 Agency Qualifier Code X/Z ID 2/2 Code identifying the agency assigning the code values PID04 75 Product Description Code X/Z AN /2 A code from an industry code list which provides specific data about a product characteristic PID05 352 Description X AN /80 A free-form description to clarify the related data elements and their content International Standards Organization (ISO 639)

Segment: CTT Transaction Totals Table/ Position 3/ 00 Optional Purpose: To transmit a hash total for a specific element in the transaction set Comments:. This segment is intended to provide hash totals to validate transaction completeness and correctness. Data Element Summary CTT0 354 Number of Line Items M N0 /6 Total number of line items in the transaction set CTT02 347 Hash Total O R /0 Sum of values of the specified data element. 2

Segment: SE Transaction Set Trailer Table/ Position 3/ 030 Mandatory Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Comments:. SE is the last segment of each transaction set. Data Element Summary SE0 96 Number of Included Segments M N0 /0 Total number of segments included in a transaction set including ST and SE segments SE02 329 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 3