ISA*00* *00* *01* *01* *920713* 1550*U*00200* *0*P*.> GS*PO* * *920713*1550*2*X* ST*850*

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

850 Purchase Order X12 Version Version: 2.0

810 IBM Subset - Invoice To Customer - (004010)

Transaction Set 860, Version ANSI Standard Version Segments used by Home Shopping Network for Traditional Purchase Orders Change.

850 Purchase Order

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

Orchard Supply Hardware Direct to Consumer 850 Purchase Order

Transaction Set 850 Version 4010VICS, Electronic Purchase Order

850 Purchase Order Version 4010

7/4/2011 Page 1 Retek850.xls

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

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

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

850 Purchase Order - v4030

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

HACHETTE BOOK GROUP USA 850 Purchase Order VERSION 4010 IMPLEMENTATION GUIDE

Purchase Order - v4010 Functional Group ID = PO

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

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

Amazon Purchase Order Acknowledgment

EDI 850 Version 4010 ANSI X12 Purchase Order Specifications

JR Simplot Corporate 810 Invoice

PLANNING SCHEDULE (830) SENT BY BLUE BIRD ANSI Segment Loop Construction

850 Purchase Order. Version: X12

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

Purchase Order Specification EDI 850

EDI Specifications Guide. 832 Customer Price Sales Catalog

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

846 RAPID Inventory Inquiry/Advice Standard

855 Purchase Order Acknowledgment. United Natural Foods

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

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

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

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

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

RCI 855 Purchase Order Acknowledgment

810 Invoice Service Parts Version:

EDI Specifications Guide. 855 Customer Purchase Order Acknowledgement

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

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

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

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

Invoice Specification EDI 810

EDI 860 Mapping. Instructions. Version 1.0 September 16, 2016

Patrick Morin. EDI Implementation Guide for Purchase Order (850) Version

940 Warehouse Shipping Order

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

EDI Specifications Guide. 856 Customer Advance Ship Notice

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

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

Inbound ANSI X Version 04010

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

850 Delhaize America Direct Store Delivery CAO Purchase Order Version 5010

870 Order Status Report

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

EDI Guidelines for Purchase Order (850) v. 4010

846 Inventory Inquiry/Advice

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

Oshkosh 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

ELECTRONIC DATA INTERCHANGE. Implementation Guidelines Outbound Purchase Order

860 Purchase Order Change Request - Buyer Initiated

Product Transfer and Resale Report - 867

855 Purchase Order Acknowledgment

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

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

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

JR Simplot Food Group Purchase Order Acknowledgment

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

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

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

855 Purchase Order Acknowledgment

Golfsmith 846 EDI Guidelines

DSW Shoe Warehouse 832 Price/Sales Catalog Vendor Direct

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

Baker & Taylor 850 EDI Specifications

865 Purchase Order Change Acknowledgment/Request - Seller Initiated

824 Application Advice

860 Purchase Order Change Request - Buyer Initiated

JR Simplot Agribusiness Ship Notice/Manifest

Purchase Order Change Request. Transaction Set (860) (Inbound to TI)

PATTERSON DENTAL SUPPLY COMPANY EDI RECORD LAYOUTS PURCHASE ORDER - VERSION 4010

Inbound X Version 04010

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

BIG Date Invoice Date. BIG02 76 Invoice Number Invoice Number. BIG Date Optional. BIG PO Number PO Number

867 Product Transfer and Resale Report Functional Group=PT

861 Receiving Advice/Acceptance Certificate

VANTAGE GROUP 850 Purchase Order. Not Define: Pos Id Segment Name Req Max Use Repeat Notes Usage ISA Interchange Control M 1 Must Use

TRW Chassis Division

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.

832 Price Sales Catalog

855 Purchase Order Acknowledgment

846 Inventory Inquiry/Advice

International Truck and Engine Corporation

830 Planning Schedule with Release Capability

844 Product Transfer Account

870 Order Status Report

NAPM RAIL INDUSTRY FORUM Application Advice IMPLEMENTATION GUIDELINE FOR EDI

Transcription:

TRANSACTION EXAMPLE ISA*00* *00* *01*006557045*01*123456789*920713* 1550*U*00200*000000003*0*P*.> GS*PO*040649824*123456789*920713*1550*2*X*002003 ST**000000001 001 BEG*02*RL*7654321*09999-92*920719 92*920719 DTM*007*920713 N1*VN*VENDOR COMPANY NAME*92*09999 N3*ATTN: MARY JOHNSON*29730 OAK ST. N4*FORT WORTH*TEXAS*75247 N1*SO*FEDERAL-MOGUL CORPORATION N3*P.O. BOX 100*ATTN: ACCOUNTING DEPARTMENT N4*JACKSONVILLE*AL*36265 N1*ST*FEDERAL-MOGUL CORPORATION N3*WORLDWIDE DISTRIBUTION CENTER*HIGHWAY 21 N. N4*JACKSONVILLE*AL*36265 N1*BT*FEDERAL-MOGUL CORPORATION N3*P.O. BOX 100*ATTN: ACCOUNTING DEPARTMENT N4*JACKSONVILLE*AL*36265 PO1*000001*500*PC***BP*M60122 PKG*S*35*ZZ*BRST*0101 BULK REF*ZZ*G*PRODUCT FLAG REF*ZZ*0100*FEDERAL-MOGUL WAREHOUSE CODE SCH*500*PC****002*920728 CTT*1*500 SE*22*000000001 GE*1*2 IEA*1*000000003 1

ST - Transaction n Set Header Heading Only Purpose: To indicate the start of a transaction set and to assign a control number. The transaction set control number entry in this header must match the transaction set control number entry in the transaction set trailer (SE) ST**000008400 ST01 143 Transaction Set Identifier M ID 03/03 Use "" ST02 329 Transaction Set Control Number M AN 04/09 2

BEG - Beginning Segment (Purchase Order) Heading Only Purpose: To indicate the beginning of the purchase order transaction set and transmit identifying numbers, and dates. None BEG*02*RL*5360530*09999 360530*09999-92*920719 92*920719 BEG01 353 Transaction Set Purpose M ID 02/02 F-M will use "02" for new PO. BEG02 92 Purchase Order Type M ID 02/02 F-M will use "RL" or "SA". If code is RL, BEG04 is mandatory. BEG03 324 Purchase Order Number M AN 01/22 BEG04 328 Release Number O AN 01/30 If BEG02 is RL this element would be mandatory. BEG05 323 Purchase Order Date M DT 06/06 Date of this transaction BEG06 326 Request Reference Nbr O AN 01/45 Not used BEG07 367 Contact Number O AN 01/30 Not used 3

NTE - Note/Special Instruction Heading Purpose: To transmit information in a freeform format if necessary, for comment or special instruction. The NTE is an optional segment that permits freeform format text which, under the ANSI X12 standard implementations, requires interventions. The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment. If highly specialized industry, trade or distributor;or group machine processable formats are to be structured. The use of the REF, PID, PKG and/or PWK segments is recommended. This optional segment may appear anywhere within the transaction set after the beginning segment and before the transaction set trailer (SE). It may be used in all loops except as the first segment in that loop. The loop repeat count must conform to the specified count for the loop in which it is used. NTE*GEN*P.O. NUMBER MUST APPEAR ON ALL BOXES,PACKAGES, SHIPPING N/L NTE*GEN*AND INVOICE DOCUMENTS N/L NTE01 363 Note Reference Code O ID 03/03 NTE02 3 Freeform Message M AN 01/60 4

REF - Reference Numbers Heading/Detail Purpose: To transmit identifying numbers associated with the named party. Used in the N1 loop and used outside the loop. When used within the loop it relates to its associated N1 segment. Either REF02 or REF03 is required. REF*ZZ*G*PRODUCT FLAG REF*ZZ*0100*FEDERAL-MOGUL WAREHOUSE CODE REF*ZZ*1111*PRODUCT LINE AND PRODUCT CLASS REF*ZZ*123456*MANUFACTURING CODE (The descriptions below are used on 860's only.) REF*ZZ*931022*PREVIOUS VENDOR PROMISE DATE ON PURCHASE ORDER REF*ZZ*1200*PREVIOUS 0*PREVIOUS QUANTITY ON PURCHASE ORDER REF*ZZ*931020*PREVIOUS DATE REQUIRED ON PURCHASE ORDER REF01 128 Reference Number Qualifier M ID 02/02 ZZ REF02 127 Reference Number C AN 01/30 REF03 352 Description C AN 01/80 See Note. Note: The REF03 description field will contain the constant values shown in the examples above for all Federal-Mogul 's and 860's. 5

N1 - Name Heading/Detail If the N1 loop is used in the detail area, this usage overrides heading area. Purpose: To identify a party by type of organization, name and code. Either N102 or N103 and N104 are required. N1*VN*AUTO PART SUPPLIER*92*09999 N1*SO*FEDERAL-MOGUL CORPORATION N1*ST*FEDERAL-MOGUL CORPORATION N1*BT*FEDERAL-MOGUL CORPORATION N101 98 Organization Identifier M ID 02/02 Use VN, SO, ST and BT. N102 93 Name C AN 01/35 Company name. N103 66 Identification Code Qualifier C ID 01/02 Use 92 only when N101 is VN. N104 67 Identification Code C ID 02/17 Use F-M F vendor code when N101 is VN. 6

N3 - Address Information Heading/Detail Purpose: To specify the location of the names party. None N3*P.O. BOX 100*ATTN: ACCOUNTING DEPARTMENT N3*WORLDWIDE DISTRIBUTION CENTER*HIGHWAY 21 NORTH N301 166 Address M AN 01/35 N302 166 Address O AN 01/35 7

N4 - Geographic Location Heading/Detail Purpose: To specify the geographic place of the named party. Used in the N1 loop at both heading and detail level. Required segment if additional information is needed to completely specify the address. Either N401 or N405 is required. If N401 is present N402 is required if N401 is in the USA. If N405 is present N406 is required. N4*JACKSONVILLE*AL*36265 (U.S.A.) N4*HAMILTON*ON*L8N3T1 (CANADA) N4*JAPAN (JAPAN) N401 19 City Name C AN 02/19 N402 156 State/Province Code C ID 02/02 N403 116 Postal Code O ID 05/09 N404 26 Country Code O ID 02/02 N405 309 Location Qualifier O ID 01/02 N406 310 Location Identifier C AN 01/25 8

ITD - Terms of Sale/Deferred Terms of Sale Heading / Detail If used in the detail area, this usage overrides heading area. Purpose: To specify terms of sale. Note: This segment will be sent on Federal-Mogul Port Everglades orders only. Percents as used in ITD03 are to be represented a whole numbers and decimals as indicated by examples below: PERCENT REPRESENTED BY Twelve and one half 12.5 Six 6 ITD*10*4*****30 ITD01 336 Terms Type Code M ID 02/02 ITD02 333 Terms Basis Date Code M ID 01/02 ITD03 338 Terms Discount Percent C R 01/06 ITD04 370 Terms Discount Due Date C ITD05 351 Terms Discount Days Due C DT 06/06 N0 01/03 ITD06 446 Terms Net Due Date C DT 06/06 ITD07 386 Terms Net Days C N0 01/03 ITD08 362 Terms Discount Amount C N2 01/10 Not used ITD09 388 Terms Deferred Due Date O DT 06/06 Not used ITD10 389 Deferred Amount Due C N2 01/10 Not used ITD11 342 Percent of Invoice Payable C R 01/05 Not used ITD12 352 Description C AN 01/80 Not used ITD13 765 Day of Month C N0 01/02 Not used 9

DTM - Date/Time Reference Heading / Detail Purpose: To specify pertinent dates and times. Date/Time is local time for sender. Use SCH for shipping information. DTM02 (Date) is mandatory. DTM*007*920628*1315*ES DTM01 374 Date/Time Qualifier M ID 03/03 007=Effective DTM02 373 Date C DT 06/06 YYMMDD format DTM03 337 Time C TM 04/04 HHMM format DTM04 623 Time Zone Qualifier O ID 02/02 ES=Eastern Std. 10

PID - Product/Item Description Heading Detail Purpose: To describe a product in coded or freeform format. This segment is used typically when a part number or similar code in segment PO1 does not completely define the product to the trading partners. Use one PID segment for each required product characteristic. Either PID04 is PID05 is required. If PID04 is present, PID03 is required. (Metals Industry) The PID segment may have to be repeated to completely describe the product. The description data element (352) is an optional element that permits freeform information/data which, under the X12 standards implementations, require interventions. When PID04 and PID05 are both used in a single use of the segment, PID05 data should further define the code in PID04. Note: This segment will be sent on Federal-Mogul Port Everglades orders only. PID*F****PART DESCRIPTION PID01 349 Item Description Type M ID 01/01 F=Free Format PID02 750 Product Characteristic Code O ID 02/03 Not used PID03 348 Item Description Qualifier O ID 02/02 Not used PID04 751 Product Description Code C ID 01/07 Not used PID05 352 Description C AN 01/80 PID06 752 Surface/Layer Indicator O ID 02/02 Not used 11

PKG - Marking, Packaging, Loading Heading Detail Purpose: To describe marking, packaging, loading and unloading requirements. Use one PKG segment for each required marking, packaging or loading characteristic. Either PKG04 of PKG05 is required. If PKG04 is present, PKG03 is required. PKG*S*35*ZZ*BRST*0101 BULK PKG*S*35*ZZ*BRST*0211 F-M PKG PKG*S*35*ZZ*BRST*5011 NAPA PKG01 349 Item Description Type M ID 01/01 S PKG02 753 Packaging Characteristic Code O ID 01/05 35 PKG03 348 Item Description Qualifier O ID 02/02 ZZ PKG04 754 Package Description Code C ID 01/07 BRST PKG05 352 Brand and State code C AN 01/80 0101 BULK 0211 F-M F PKG Note: Call Federal-Mogul for brand/state codes if your company does other types of packaging. 12

PO1 - Purchase Order Line Item Detail Only Purpose: To specify basic purchase order line item data. None PO1*000001*250*PC***BP*M60999*VP*123987 PO1*000002*150*PC***BP*M49387 PO101 350 P.O. Line Number O AN 01/06 Required on multiple line items, if PO106 & PO107 are not used. PO102 330 Quantity Ordered M R 01/09 PO103 355 Unit of Measurement Code M ID 02/02 PO104 212 Unit Price C R 01/14 PO105 639 Basis Unit Price Code O ID 02/02 Not currently used. PO106 235 Product/Service ID O ID 02/02 BP=Buyer's Part PO107 234 Product/Service ID C AN 01/30 F-M Part Nbr. PO108 Note: PO108 thru PO124 provide 9 additional pairs of Product/Service ID Qualifiers (235) and Product/Service ID (234) used in the same manner as PO106 and PO107. Vendor part ("VP" qualifier) will be sent when available. through PO124 13

SCH - Line Item Schedule Detail Only Purpose: To specify the data for scheduling a specific line item. This segment is used to specify a desired shipping date or date range for an item. When used, the unit of measurement (SCH02) must be identical to the unit of measurement in the associated PO1 segment (PO103) and the sum of the values of quantity (SCH01) in the PO1 segment. SCH*100*PC****002*920822 SCH01 380 Quantity M R 01/10 SCH02 355 Unit of Measurement Code M ID 02/02 SCH03 352 Description O AN 01/80 Not used SCH04 98 Organization Identifier O ID 02/02 Not used SCH05 93 Name C AN 01/35 Not used SCH06 374 Date/Time Qualifier M ID 03/03 002=Delivery Requested SCH07 373 Date M DT 06/06 YYMMDD SCH08 337 Time O TM 04/04 Not used SCH09 374 Date/Time Qualifier O ID 03/03 Not used SCH10 373 Date C DT 06/06 Not used SCH11 337 Time O TM 04/04 Not used 14

CTT - Transaction Totals Summary Purpose: To transmit a hash total for a specific element in the transaction set. CTT01 and CTT02 are mandatory. CTT03 thru CTT07 are not used. CTT*3*80 CTT01 354 Number of Line Items M NO 01/06 Total number of PO1 segments. CTT02 347 Hash Total O R 01/10 Accumulation of value of quantity used in (PO102) CTT03 81 Weight O R 01/10 N/A CTT04 355 Unit of Measurement Code C ID 02/02 N/A CTT05 183 Volume O R 01/08 N/A CTT06 355 Unit of Measurement Code C ID 02/02 N/A CTT07 352 Description O AN 01/80 N/A 15

SE - Transaction n Set Trailer Summary Purpose: To indicate the end of the transaction set and provide the count of the transaction set and provide the count of the transmitted segments (including the beginning and ending (SE) segment). The number of included segments is the total of all segments used in the transaction set including the (ST) and (SE) segments. The transaction set control number value in this trailer must match the same element value in the transaction set header (ST02). SE*20*000008400 SE01 96 Number of Included Segments M N0 01/06 SE02 329 Transaction Set Control Number M AN 04/09 Same as corresponding ST02 16