MEDTRONIC. ANSI X12 850 Purchase Order Specifications



Similar documents
Electronic Data Interchange

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

ANSI X12 version Advance Ship Notice

810 Invoice ANSI ASC X12 Version 4010

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

VERSION: ANSI X

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS S Supplier

810 Invoice Revised 01/26/15

Portland General Electric Implementation Standard

Electronic Data Interchange

Bill of Lading Number REF Reference Identification M AN 1/30 MustUse

Invoice. Transaction Set (810) (Outbound from TI)

The EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X

ANSI X Product Transfer and Resale Report

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION August 21, 2007

EDI GUIDELINES INVOICE 810 VERSION 4010

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

3/31/08 ALTRA INDUSTRIAL MOTION Invoice Inbound 810 X Page 1 Created by Ralph Lenoir

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

860 Purchase Order Change Request Buyer Initiated

ADOBE ANSI X Version: 1.0

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

810 Invoice ANSI X.12 Version 5010

EDI GUIDELINES PURCHASE ORDER 850 VERSION 4010

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

Now, suppliers can also select EDI as a method for receiving Change and Cancel Orders.

EDI Specifications Invoice (Supplier v4010)

810 - Invoice. Set Number Set Name - Invoice Functional Group - IN

ANSI X12 version Planning Schedule with Release Capability

Staples Supplier Electronic Data Interchange Implementation Guide

Dart Container Corporation. EDI 810 Outbound Invoice Version 4010

810 Invoice. Introduction: Heading: Functional Group ID=IN

ANSI X12 version Text Message

X12 Implementation Guidelines For Outbound Receiving Advice v (861O)

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^ ^12345^ ^ ^

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

ANSI X12 version Remittance Advice

VDP Program Vendor Guidelines

EDI Specifications Advance Ship Notice (Supplier v4010)

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

Mazda North American Operations EDI Supplier Documentation October 20, 2015

Supply Chain Merchandise Logistics E-Commerce Purchase Order

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

VOLVO Dealer Programs 810 Invoice EDI Guideline

214 Transportation Carrier Shipment Status Message - LTL

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

Detail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header

ANSI X12 ASN 856 Version

Note: The following information is required on all Merchandise Invoices:

856 Advanced Shipping Notices (ASN)

Customer EDI Guidelines United States 810 Invoice

824 Application Advice

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

856 Advance Ship Notice Supplier Implementation Guide November 2015

845 PRICE AUTHORIZATION ACKNOWLEDGEMENT/STATUS - VERSION 5010

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

RANDOM HOUSE. EDI Implementation Guide Invoice X12 Version 4010

856 Ship Notice/Manifest - R US CANADA

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

Ultramar Ltd IMPLEMENTATION GUIDE

Because the 810 implementation ultimately maps to an InvoiceDetailRequest, it must conform to its rules.

Adobe - EDIFACT D97.A ORDERS

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice

LOOP ID - N N9 Reference Identification O MSG Message Text O 1000

867 Product Transfer and Resale Report Ver/Rel Electronic Data I nterchange. Utility Industry Group Implementation Guideline.

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

214 Transportation Carrier Shipment Status Message

EDI SPECIFICATIONS 4050VICS VERSION

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET

PURCHASE ORDER RESPONSE

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

ASN. HDMA Electronic Data Interchange (EDI) Guidelines for the 856 Advance Ship Notice to Support Implementation of DSCSA

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)

KANSAS CITY SOUTHERN EDI On-Boarding Guide

State of Tennessee Department of Revenue

820 ANSI X12 Version

CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

Electronic Document Interchange Standards Version 5050

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

999 Implementation Acknowledgment. Version: 1.0 Draft

BLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE

State of Nebraska. Motor Fuels Division. EDI Implementation Guide. Revised May ANSI ASC X12 V.4030

Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy

Ford Customer Service Division SDS (Supplier Direct Ship) EDI Manual

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

835 Health Care Claim Payment/Advice Functional Group=HP

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

PARTY INFORMATION MESSAGE. PARTIN Version 1.0. agreed-upon by EDI Working Group of ECR Poland

Media Saturn EDI Application Documentation

DRS Defect Report Inbound 322. DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA

Purchase Orders Message ORDERS (EDIFACT D97A)

Transcription:

ANSI X12 850 Purchase Order Specifications The American National Standards Institute (ANSI) and the Accredited Standards Committee (ASC) define this transaction as follows: 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. It should not be used to convey purchase order changes or purchase order acknowledgment information. This document lists the accepted ANSI X12 850 Purchase Order layout used by the Medtronic. The ANSI X12 version of the purchase order transaction created is 4010. The 850 Purchase Order is an outbound transaction that allows Medtronic users to transmit purchase orders to their suppliers. The following is an example of the typical format used when communicating the ANSI X12 850 transaction set. It is important to note that multiple 850 transaction sets may be contained within each valid X12 file. Header ISA - Interchange Control Header ST - Transaction Set Header BEG - Begins the Purchase Order Transaction N9 Reference Identification DTM Date/Time MSG Message Text N1 - Organization Name N3 - Address Information N4 - Geographic Location PER - Administrative Contact Total CTT - Transaction Totals SE - Transaction Set Trailer IEA - Interchange Control Trailer Detail PO1 - Purchase Order Item Data PID - Product/Item Description REF - Reference Numbers MSG Message Text Page: 1 of 10

850 Purchase Order Segment Structure by Group / Loop Segment/Element Usage Legend: M = Mandatory segment or element; required for successful Medtronic system processing. O = Optional segment or element; may be helpful but not required for successful processing. X = Conditional element; existence is conditional upon another segment or element. Transaction Set Header Segment Name Usage Max ID ST Transaction Set Header to identify the M 1 Purchase Order set BEG Beginning Segment for Purchase Orders M 1 N9 Identifies Date/Time and Message information O 1 DTM Date and Time the transaction was M 1 created MSG Message Text / To provide special O 50 Instructions for entire transaction set N1 Loop N1 Name segment O 1 N3 Address information O 1 N4 City, State and Zip O 1 PER Administrative Communication Contact O 1 Line Item Loop Segment Name Usage Max ID May repeat 100,000 times PO1 Purchase Order Baseline Item Data M 1 PID Loop PID Product/Item Description O 1 REF Reference Numbers for Cost O 3 Allocation, Purchase Requisition Number and Bin Location MSG Message Text / To provide special O 50 Instructions for line items CTT Transaction Totals M 1 SE Transaction Set Trailer M 1 Segment / Element Detail Information Transaction Set Header The following information identifies the elements used in the 850 Purchase Order. ST - Transaction Set Header Example: ST*850*191154910 ST-01 Transaction Set Identifier Code M 3/3 Transmitted code(s): Page: 2 of 10

850 - Purchase Order ST-02 Transaction Set Control Number M 4/9 Control number should match the SE-02 element. BEG - Begins the Purchase Order Transaction Example: BEG*00*SA*144**20000616 BEG- 01 Transaction Set Purpose Code M 2/2 Transmitted code(s): 00 - New Purchase Order BEG-02 Purchase Order Type Code M 2/2 Transmitted code(s): CN = ConsignmentOrder NE = NewOrder SA = StandAloneOrder RO = RushOrder 'EO' = 'EmergencyOrder' BEG-03 Purchase Order Number M 1/16 BEG-04 Release Number O 1/30 BEG-05 Purchase Order Date M 8/8 Date in CCYYMMDD format. BEG-06 Contract Number O 1/30 N9 Reference Identification Example: N9*PO*144 N9-01 Reference Identification Qualifier M 2/2 Transmitted code(s): PO Purchase Order N9-02 Reference Identification M 1/16 Purchase Order Number Page: 3 of 10

DTM - Date/Time Reference Example: DTM*097*20000616*1549 DTM-01 Date/Time Qualifier M 3/3 Transmitted code(s): 097 - Transaction create date DTM-02 System Date X 8/8 Date in CCYYMMDD format. DTM-03 System Time X 4/4 Date in HHMM format. MSG - Message Text Example: MSG*PLEASE SHIP ASAP MSG*NET 30 DAYS MSG-01 Free form message O 1/264 Special instructions and purchase order terms and conditions. N1 - Name of Organization Example: N1*BY*GENERAL HOSPITAL*91*123456 N1*BT*GENERAL SUPPLIES*91*55123456 N1*ST*WEST PARK*91*77756 N1-01 Entity ID Code M 2/2 Transmitted code(s): BY - Buying Party SE Selling Party BT Bill to Party ST Ship to VN Vendor N1-02 Name of buying party M 1/35 Communicator Name N1-03 ID Code Qualifier O 2/2 Transmitted code(s): 91 - Assigned by Seller N1-04 ID Code X 1/16 Vendor Customer Number Page: 4 of 10

N3 - Address Information of the N1 Loop Example: N3*1000 Pacer Drive*SUITE 400 Element Name Usage Min/Max N3-01 Street address M 1/30 N3-02 Street address O 1/30 Notes N4 - Geographic Location of the N1 Loop Example: N4*CHICAGO*IL*60020 Element Name Usage Min/Max N4-01 City Name O 2/18 N4-02 State or Province Code O 2/2 N4-03 Postal Code/Zip Code O 4/9 Notes PER - Administrative Contact Example: PER*SR*BARRY WILSON*TE*8475374800 PER-01 Contact Function Code M 2/2 Transmitted code(s): BD = BuyerNameorDepartment SR = SalesRepresentativeOrDepartment CR = CustomerRelations OC = 'OrderContact' DC = DeliveryContact IC = InformationContact OD = OrderDepartment ZZ = MutuallyDefined 'EB' = 'EnteredBy' 'RQ' = 'Requestor' PER-02 Name M 1/30 Name of the Contact PER-03 Communication Number Qualifier O 2/2 Transmitted code(s): TE = TelephoneNumber FX = FaxNumber EM = EmailAddress PER-04 Telephone Number X 1/25 Telephone number of the Contact Page: 5 of 10

Line Item Loop PO1 - Purchase Order Item Data Example: PO1*1*1*CS*0.01**IN*7237823*VC*7219D*SN*BRD951028817 PO1-01 Assigned Identifier O 1/3 Purchase order line number PO1-02 Quantity Ordered X 1/5 If 03 is present, then 02 is required. PO1-03 Unit of Measure O 2/2 Transmitted code(s): EA Each BX Box CT Carton PK Package CS - Case PO1-04 Item Unit Price X 1/10 Pricing sent in 2 decimal places. PO1-06 Product/Service ID Qualifiers X 2/2 Transmitted code(s): MF, MG, VC, BP, IN See chart below for descriptions of each. If either 06 or 07 is present, PO1-07 Product/Service IDs O 1/48 PO1-08 Product/Service ID Qualifiers X 2/2 If either 08 or 09 is present, PO1-09 Product/Service IDs O 1/48 PO1-10 Product/Service ID Qualifiers X 2/2 If either 10 or 11 is present, PO1-11 Product/Service IDs O 1/48 PO1-12 Product/Service ID Qualifiers X 2/2 If either 12 or 13 is present, PO1-13 Product/Service IDs O 1/48 PO1-14 Product/Service ID Qualifiers X 2/2 If either 14 or 15 is present, PO1-15 Product/Service IDs O 1/48 PO1-16 Product/Service ID Qualifiers X 2/2 If either 16 or 17 is present, PO1-17 Product/Service IDs O 1/48 PO1-18 Product/Service ID Qualifiers X 2/2 If either 18 or 19 is present, PO1-19 Product/Service IDs O 1/48 PO1-20 Product/Service ID Qualifiers X 2/2 If either 20 or 21 is present, Page: 6 of 10

PO1-21 Product/Service IDs O 1/48 PO1-22 Product/Service ID Qualifiers X 2/2 If either 22 or 23 is present, PO1-23 Product/Service IDs O 1/48 PO1-24 Product/Service ID Qualifiers X 2/2 If either 24 or 25 is present, PO1-25 Product/Service IDs O 1/48 Qualifier ANSI Definition McKessonHBOC Definition Max. MF Manufacturer Manufacturer LIC 4 MG Manufacturer s Part Manufacturer Catalog 16 Number Number VC Vendor s (seller s) Vendor Catalog Number 16 Catalog Number BP Buyer s Part Number Buyer Part (Item Number) 5 IN Buyer s Item Number Item Number (Hospital Number) 10 SN Serial Number Serial Number 15 LT Lot Number Lot Number 15 *Only 1 Serial or Lot Number to be transmitted per PO1 segment PID - Product/Item Description Example: PID*F****PCD 100ML VIALS PID-01 Item Description Type M 1/1 Transmitted code(s): F - Free form text PID-05 Description M 1/80 REF - Reference Numbers Example: REF*CA*1000*1- WEST Element Name Usage Min/Max REF-01 Reference Identification Qualifier REF-02 Reference Identification X 1/30 REF-03 Description X 1/80 Notes M 2/3 Transmitted code(s): CA - Cost Allocation RQ - Requisition Number CR - Client Reference Number EJ Patient Account Number ZZ Implanting Physician Page: 7 of 10

MSG - Message Text Example: MSG*PLEASE SHIP THIS ITEM ASAP MSG*SN:BRD8327495 BILL ONLY PT:SMITH,JOHN MSG-01 Free form message O 1/264 Special instructions for purchase order line items Using this message segment For those systems that are not able to map required information to EDI elements, Medtronic allows the use of line-item notes. The following describes how information should be specified in a message segment so that Medtronic will be able to automatically process the information. The information may be in any sequence and must contain at least one space between items. Product Serial/ Lot Numbers: Serial and lot numbers may be contained in the note segment provided that there is only one number and it is prefixed with one of the following prefixes: SN:, SN-, or S/N:. Example: SN:BRD892743. Patients Name: The patients name should be prefixed with PT:. and there should be no spaces in the patients name. Example: PT:SMITH,JOHN. Bill Only, Do not Replace Product: Placing the text BILL ONLY in the note will cause the product to only be billed and will not replace consignment inventory. Transaction Set Trailer CTT - Transaction Totals Example: CTT*1*1 Element Name Usage Min/Max CTT-01 Total number of purchase order M 1/6 line items CTT-02 Hash total of the number of O 1/10 units ordered Notes SE - Transaction Set Trailer Example: SE*24*191154910 SE-01 Number of Segments Included M 1/6 The number of segments between ST and SE inclusive. SE-02 Transaction Set Control Number M 4/9 Same as ST-02 Page: 8 of 10

Sample Data: ISA*00* *00* * ZZ*5489002 *01*197607336 *980710*154 9*U*00400*191154908*0*P* GS*PO*5489002*197607336*20000616*1549*191154909*X*004010 ST*850*191154910 BEG*00*SA*144**20000616 N9*PO*144 DTM*097*20000616*1549 MSG*PLEASE SHIP ASAP MSG*NET 30 DAYS N1*BY*GENERAL HOSPITAL*91*123456 N1*BT*GENERAL SUPPLIES*91*55123456 N1*ST*WEST PARK*91*77756 N3*1000 Pacer Drive*SUITE 400 N4*CHICAGO*IL*60020 PER*SR*BARRY WILSON*TE*8475374800 PO1*1*1*CS*0.01**IN*7237823*VC*7219D*SN*BRD951028817 PID*F****PCD 100ML VIALS REF*CA*1000*1-WEST SDQ*CS*57*1000*1 MSG*PLEASE SHIP THIS ITEM ASAP MSG*SN:BRD8327495 BILL ONLY PT:SMITH,JOHN CTT*1*1 SE*24*191154910 GE*1*191154909 IEA*1*191154908 Page: 9 of 10