ANSI X12 850 (Purchase Order) Outbound (from Eclipse .
ANSI X12850 (Purchase Order)Outbound (from Eclipse)Version 4010Eclipse 850 4010 (Vendor)12/10/2016
850Purchase OrderFunctional Group POPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the PurchaseOrder Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to provide for customary and established business and industry practice relative to theplacement of purchase orders for goods and services. This transaction set should not be used to convey purchaseorder changes or purchase order acknowledgment 40FOBDTMTD5270MANLOOP ID - N9295N9300MSGLOOP ID - N1310N1330N3340N4Segment NameReqBeginning Segment forMPurchase OrderReference IdentificationOAdministrativeOCommunications ContactF.O.B. Related Instructions ODate/Time ReferenceOCarrier Details (RoutingOSequence/Transit Time)Marks and NumbersOMax Use1RepeatNotesUsageMust usePage3 13UsedUsed45 21314101000Reference IdentificationMessage TextOO11000NameAddress InformationGeographic LocationOOO12 1ReqMax UseM1200Detail:PosIdLOOP ID - PO1010PO1LOOP ID - PID050PID100REF289MSGSegment NameBaseline Item DataRepeat100000NotesUsagePageN2/010Must use15UsedUsedUsed1718191000Product/Item DescriptionReference IdentificationMessage TextOOO1 1 1ReqMax UseO1Summary:PosIdSegment NameLOOP ID - CTT010CTT Transaction s:2/0103/010L3/010PO102 is required.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.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.Eclipse 850 4010 (Vendor)22/10/2016
BEG Beginning Segment forPos: 020Max: 1Heading - MandatoryLoop: N/AElements: 5Purchase OrderUser Option (Usage): Must usePurpose: To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers anddatesElement Summary:RefBEG01Id353Element NameTransaction Set Purpose CodeReqMTypeIDMin/Max2/2UsageMust use2/2Must use1/22Must useDescription: Code identifying purpose of transaction setCodeList Summary (Total Codes: 65, Included: 1)CodeName00OriginalBEG0292Purchase Order Type CodeMIDDescription: Code specifying the type of Purchase OrderCodeList Summary (Total Codes: 69, Included: 2)CodeNameDSDropshipNENew OrderBEG03324Purchase Order NumberMANDescription: Identifying number for Purchase Order assigned by the orderer/purchaserBEG04328Release NumberOAN1/30UsedDescription: Number identifying a release against a Purchase Order previously placed bythe parties involved in the transactionBEG05373DateMDT8/8Must useDescription: Date expressed as CCYYMMDDSemantics:1. BEG05 is the date assigned by the purchaser to purchase order.Eclipse 850 4010 (Vendor)32/10/2016
Pos: 050Max: 1Heading - OptionalLoop: N/AElements: 2Reference IdentificationREFUser Option (Usage): UsedPurpose: To specify identifying informationElement Summary:RefREF01Id128Element NameReference Identification QualifierReqMTypeIDMin/Max2/3UsageMust use1/30UsedDescription: Code qualifying the Reference IdentificationCodeList Summary (Total Codes: 1503, Included: 4)CodeNameCOCustomer Order NumberCTContract NumberPRPrice Quote NumberQ1Quote NumberREF02127Reference IdentificationXANDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierSemantics:1. REF04 contains data relating to the value cited in REF02.Eclipse 850 4010 (Vendor)42/10/2016
AdministrativeCommunications ContactPERPos: 060Max: 3Heading - OptionalLoop: N/AElements: 4User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directedElement Summary:RefPER01Id366Element NameContact Function CodeReqMTypeIDMin/Max2/2UsageMust useDescription: Code identifying the major duty or responsibility of the person or group namedCodeList Summary (Total Codes: 230, Included: 1)CodeNameBDBuyer Name or Description: Free-form namePER03365Communication Number QualifierDescription: Code identifying the type of communication numberCodeList Summary (Total Codes: 40, Included: 1)CodeNameTETelephonePER04364Communication NumberXANDescription: Complete communications number including country or area code whenapplicablePER05365Communication Number QualifierXID2/2Used1/80UsedDescription: Code identifying the type of communication numberCodeList Summary (Total Codes: 40, Included: 1)CodeNameEMElectronic MailPER06364Communication NumberXANDescription: Electronic email address.Eclipse 850 4010 (Vendor)52/10/2016
F.O.B. Related InstructionsFOBPos: 080Max: 1Heading - OptionalLoop: N/AElements: 1User Option (Usage): UsedPurpose: To specify transportation instructions relating to shipmentElement Summary:RefFOB01Id146Element NameShipment Method of PaymentReqMTypeIDMin/Max2/2UsageMust useDescription: Code identifying payment terms for transportation chargesCodeList Summary (Total Codes: 28, Included: 1)CodeNamePPPrepaid (by Seller)Semantics:1.2.3.4.FOB01 indicates which party will pay the carrier.FOB02 is the code specifying transportation responsibility location.FOB06 is the code specifying the title passage location.FOB08 is the code specifying the point at which the risk of loss transfers. This may be different than thelocation specified in FOB02/FOB03 and FOB06/FOB07.Eclipse 850 4010 (Vendor)62/10/2016
DTMPos: 150Max: 10Heading - OptionalLoop: N/AElements: 2Date/Time ReferenceUser Option (Usage): UsedPurpose: To specify pertinent dates and timesElement Summary:RefDTM01Id374Element NameDate/Time QualifierReqMTypeIDMin/Max3/3UsageMust useDescription: Code specifying type of date or time, or both date and timeCodeList Summary (Total Codes: 1112, Included: 1)CodeName002Delivery RequestedDTM02373DateXDT8/8UsedDescription: Date expressed as CCYYMMDDEclipse 850 4010 (Vendor)72/10/2016
Carrier Details (RoutingSequence/Transit Time)TD5Pos: 240Max: 12Heading - OptionalLoop: N/AElements: 2User Option (Usage): UsedPurpose: To specify the carrier and sequence of routing and provide transit time informationElement Summary:RefTD504Id91Element NameTransportation Method/Type CodeReqXTypeIDMin/Max1/2UsageUsedDescription: Code specifying the method or type of transportation for the shipmentCodeList Summary (Total Codes: 71, Included: 13)CodeNameAAirCConsolidationDParcel PostHCustomer PickupLContract CarrierMMotor (Common Carrier)RRailTBest Way (Shippers Option)UPrivate Parcel ServiceAEAir ExpressBUBusLTLess Than Trailer Load (LTL)SRSupplier TruckTD505387RoutingXAN1/35UsedDescription: Free-form description of the routing or requested routing for shipment, or theoriginating carrier's identitySyntax Rules:1.2.3.4.5.6.7.R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.C0203 - If TD502 is present, then TD503 is required.C0708 - If TD507 is present, then TD508 is required.C1011 - If TD510 is present, then TD511 is required.C1312 - If TD513 is present, then TD512 is required.C1413 - If TD514 is present, then TD513 is required.C1512 - If TD515 is present, then TD512 is required.Semantics:1. TD515 is the country where the service is to be performed.User Note 1:The codes listed for the TD504 are per NAED EDIPro guidelines. Eclipse is not restricted to the use of only thesecodes. They are a guideline.Eclipse 850 4010 (Vendor)82/10/2016
Pos: 270Max: 10Heading - OptionalLoop: N/AElements: 2Marks and NumbersMANUser Option (Usage): UsedPurpose: To indicate identifying marks and numbers for shipping containersElement Summary:RefMAN01Id88Element NameMarks and Numbers QualifierReqMTypeIDMin/Max1/2UsageMust useDescription: Code specifying the application or source of Marks and Numbers (87)CodeList Summary (Total Codes: 20, Included: 1)CodeNamePBPremarked by BuyerMAN0287Marks and NumbersMAN1/48Must useDescription: Marks and numbers used to identify a shipment or parts of a shipmentSyntax Rules:1. P0405 - If either MAN04 or MAN05 is present, then the other is required.2. C0605 - If MAN06 is present, then MAN05 is required.Semantics:1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to thesame physical container.2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 isthe ending number of that range.3. When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06 isthe ending number of that range.User Note 1:PO NumberEclipse 850 4010 (Vendor)92/10/2016
Pos: 295Max: 1Heading - OptionalLoop: N9Elements: 2Reference IdentificationN9User Option (Usage): UsedPurpose: To transmit identifying information as specified by the Reference Identification QualifierElement Summary:RefN901Id128Element NameReference Identification QualifierReqMTypeIDMin/Max2/3UsageMust use1/30UsedDescription: Code qualifying the Reference IdentificationCodeList Summary (Total Codes: 1503, Included: 1)CodeNameL1Letters or NotesN902127Reference IdentificationXANDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierSyntax Rules:1. R0203 - At least one of N902 or N903 is required.2. C0605 - If N906 is present, then N905 is required.Semantics:1. N906 reflects the time zone which the time reflects.2. N907 contains data relating to the value cited in N902.Eclipse 850 4010 (Vendor)102/10/2016
Pos: 300Max: 1000Heading - OptionalLoop: N9Elements: 1Message TextMSGUser Option (Usage): UsedPurpose: To provide a free-form format that allows the transmission of text informationElement Summary:RefMSG01Id933Element NameFree-Form Message TextReqMTypeANMin/Max1/264UsageMust useDescription: Free-form message textSyntax Rules:1. C0302 - If MSG03 is present, then MSG02 is required.Semantics:1. MSG03 is the number of lines to advance before printing.Eclipse 850 4010 (Vendor)112/10/2016
Pos: 310Max: 1Heading - OptionalLoop: N1Elements: 4NameN1User Option (Usage): UsedPurpose: To identify a party by type of organization, name, and codeElement Summary:RefN101Id98Element NameEntity Identifier CodeReqMTypeIDMin/Max2/3UsageMust useDescription: Code identifying an organizational entity, a physical location, property or anindividualCodeList Summary (Total Codes: 1312, Included: 3)CodeNameBTBill-to-PartyBYBuying Party (Purchaser)STShip ToN10293NameXAN1/60UsedXID1/2UsedDescription: Free-form nameN10366Identification Code QualifierDescription: Code designating the system/method of code structure used for IdentificationCode (67)CodeList Summary (Total Codes: 215, Included: 3)CodeName1D-U-N-S Number, Dun & Bradstreet9D-U-N-S 4, D-U-N-S Number with Four Character Suffix92Assigned by Buyer or Buyer's AgentN10467Identification CodeXAN2/80UsedDescription: Code identifying a party or other codeSyntax Rules:1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.User Note 1:The BY and BT N1 loops contain only the N1 line. The N1 ST loop will contain N1, N3, and N4.Eclipse 850 4010 (Vendor)122/10/2016
N3Pos: 330Max: 2Heading - OptionalLoop: N1Elements: 2Address InformationUser Option (Usage): UsedPurpose: To specify the location of the named partyElement Summary:RefN301Id166Element NameAddress InformationReqMTypeANMin/Max1/55UsageMust useOAN1/55UsedDescription: Address informationN302166Address InformationDescription: Address informationEclipse 850 4010 (Vendor)132/10/2016
Pos: 340Max: 1Heading - OptionalLoop: N1Elements: 3Geographic LocationN4User Option (Usage): UsedPurpose: To specify the geographic place of the named partyElement Summary:RefN401Id19Element NameCity ption: Free-form text for city nameN402156State or Province CodeDescription: Code (Standard State/Province) as defined by appropriate government agencyN403116Postal CodeOID3/15UsedDescription: Code defining international postal zone code excluding punctuation and blanks(zip code for United States)Syntax Rules:1. C0605 - If N406 is present, then N405 is required.Eclipse 850 4010 (Vendor)142/10/2016
PO1Pos: 010Max: 1Detail - MandatoryLoop: PO1Elements: 15Baseline Item DataUser Option (Usage): Must usePurpose: To specify basic and most frequently used line item dataElement Summary:RefPO101Id350Element NameAssigned ption: Alphanumeric characters assigned for differentiation within a transaction setPO102330Quantity OrderedXR1/15UsedOID2/2UsedDescription: Quantity orderedPO103355Unit or Basis for Measurement CodeDescription: Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenAll valid standard codes are used. (Total Codes: 794)PO104212Unit PriceXR1/17Used2/2Used2/2UsedDescription: Price per unit of product, service, commodity, etc.PO105639Basis of Unit Price CodeOIDDescription: Code identifying the type of unit price for an itemAll valid standard codes are used. (Total Codes: 91)PO106235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)CodeList Summary (Total Codes: 477, Included: 1)CodeNameVCVendor's (Seller's) Catalog NumberPO107234Product/Service IDXAN1/48Used2/2UsedDescription: Identifying number for a product or servicePO108235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)CodeList Summary (Total Codes: 477, Included: 3)CodeNameUIU.P.C. Consumer Package Code (1-5-5)UKU.P.C./EAN Shipping Container Code (1-2-5-5-1)UPU.P.C. Consumer Package Code (1-5-5-1)PO109234Product/Service IDXAN1/48Used2/2UsedDescription: Identifying number for a product or servicePO110235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)CodeList Summary (Total Codes: 477, Included: 1)CodeNameBPBuyer's Part NumberEclipse 850 4010 (Vendor)152/10/2016
PO111234Product/Service IDXAN1/48Used2/2UsedDescription: Identifying number for a product or servicePO112235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)CodeList Summary (Total Codes: 477, Included: 1)CodeNameINBuyer's Item NumberPO113234Product/Service IDXAN1/48Used2/2UsedDescription: Identifying number for a product or servicePO114235Product/Service ID QualifierXIDDescription: Code identifying the type/source of the descriptive number used inProduct/Service ID (234)CodeList Summary (Total Codes: 477, Included: 1)CodeNameVPVendor's (Seller's) Part NumberPO115234Product/Service IDXAN1/48UsedDescription: Identifying number for a product or serviceSyntax Rules:1.2.3.4.5.6.7.8.9.10.11.12.C0302 - If PO103 is present, then PO102 is required.C0504 - If PO105 is present, then PO104 is required.P0607 - If either PO106 or PO107 is present, then the other is required.P0809 - If either PO108 or PO109 is present, then the other is required.P1011 - If either PO110 or PO111 is present, then the other is required.P1213 - If either PO112 or PO113 is present, then the other is required.P1415 - If either PO114 or PO115 is present, then the other is required.P1617 - If either PO116 or PO117 is present, then the other is required.P1819 - If either PO118 or PO119 is present, then the other is required.P2021 - If either PO120 or PO121 is present, then the other is required.P2223 - If either PO122 or PO123 is present, then the other is required.P2425 - If either PO124 or PO125 is present, then the other is required.Eclipse 850 4010 (Vendor)162/10/2016
Pos: 050Max: 1Detail - OptionalLoop: PIDElements: 2Product/Item DescriptionPIDUser Option (Usage): UsedPurpose: To describe a product or process in coded or free-form formatElement Summary:RefPID01Id349Element NameItem Description TypeReqMTypeIDMin/Max1/1UsageMust use1/80UsedDescription: Code indicating the format of a descriptionCodeList Summary (Total Codes: 3, Included: ion: A free-form description to clarify the related data elements and their contentSyntax Rules:1.2.3.4.5.C0403 - If PID04 is present, then PID03 is required.R0405 - At least one of PID04 or PID05 is required.C0703 - If PID07 is present, then PID03 is required.C0804 - If PID08 is present, then PID04 is required.C0905 - If PID09 is present, then PID05 is required.Semantics:1. 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.3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specifiedattribute applies to this item; an "N" indicates it does not apply. Any other value is indeterminate.4. PID09 is used to identify the language being used in PID05.Eclipse 850 4010 (Vendor)172/10/2016
Pos: 100Max: 1Detail - OptionalLoop: PO1Elements: 2Reference IdentificationREFUser Option (Usage): UsedPurpose: To specify identifying informationElement Summary:RefREF01Id128Element NameReference Identification QualifierReqMTypeIDMin/Max2/3UsageMust use1/30UsedDescription: Code qualifying the Reference IdentificationCodeList Summary (Total Codes: 1503, Included: 3)CodeNameCTContract NumberPRPrice Quote NumberQ1Quote NumberREF02127Reference IdentificationXANDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierSyntax Rules:1. R0203 - At least one of REF02 or REF03 is required.Semantics:1. REF04 contains data relating to the value cited in REF02.Eclipse 850 4010 (Vendor)182/10/2016
Pos: 289Max: 1Detail - OptionalLoop: PO1Elements: 1Message TextMSGUser Option (Usage): UsedPurpose: To provide a free-form format that allows the transmission of text informationElement Summary:RefMSG01Id933Element NameFree-Form Message TextReqMTypeANMin/Max1/264UsageMust useDescription: Free-form message textSyntax Rules:1. C0302 - If MSG03 is present, then MSG02 is required.Semantics:1. MSG03 is the number of lines to advance before printing.Eclipse 850 4010 (Vendor)192/10/2016
CTTPos: 010Max: 1Summary - OptionalLoop: CTTElements: 1Transaction TotalsUser Option (Usage): UsedPurpose: To transmit a hash total for a specific element in the transaction setElement Summary:RefCTT01Id354Element NameNumber of Line ItemsReqMTypeN0Min/Max1/6UsageMust useDescription: Total number of line items in the transaction setSyntax Rules:1. P0304 - If either CTT03 or CTT04 is present, then the other is required.2. P0506 - If either CTT05 or CTT06 is present, then the other is required.Eclipse 850 4010 (Vendor)202/10/2016
Eclipse 850 4010 (Vendor) 2 2/10/2016 850 Purchase Order Functional Group PO This Draft Standard for Trial Use contains the format Purpose: and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data
Eclipse 850 4010 (Customer) 1 10/11/2012 ANSI X12 850 (Purchase Order) Inbound (to Eclipse) Version 4010. Eclipse 850 4010 (Customer) 2 10/11/2012 850 Purchase Order Functional Group PO This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Purpose:
VOLVO Application of ANSI X12 1 P a g e Application of ANSI X12 General ANSI X12 or ASC X12 (Accredited Standards Committee) develops and maintains EDI standards. X12 was the sequential designator assigned by
STANDARDS EVOLVE · Working papers · Three times a year · Draft standards · ANSI standards · Version & release 001000 ANSI - 1983 002000 ANSI - 1986 002040 Draft X12 May 89 003000 ANSI - 1992 003020 Draft X12 Oct 91 003021 Draft X12 Feb 92 004000 ANSI - 1997 004010 Draft X12 Oct 97 CHANGES · Simplify data. · Eliminate transactions.
Inbound X12 850 Version 004010 For Ordering Shrink Wrap Product Version: ANSI ASC X12 850 4010 Author: Adobe EDI Company: Modified: 9/29/2015. 9/29/2015 Purchase Order - 850 SW_X12_850_4010_092915.ecs 1 For internal use only 850 Purchase .
06/09/10 Purchase Order - 850 CLP_X12_ANSI8504010_060910.ecs 1 For internal use only . Inbound ANSI X12 850 Version 04010. For CLP License Ordering. Version: ANSI X12 850 4010 . Author: Adobe EDI Modified: 06/09/2010
Aug 05, 2012 · Navistar, Inc. X12V3040 Purchase Order - 850 850_3050_DRAFT.ecs 1 Production Ver X12 V3040 NAV 850Purchase Order Functional Group PO Purpose: 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 El
X12 EDI 850 Purchase Order Specifications . 2 Contents Purchase Order Details 3 Introduction 3 File Format 3 X12 EDI 850 Segments 4 . This specification contains the format and data content of the Purchase Order sent from Coupa, outbound to suppliers/distributors following the EDI
- Digit digit test X3 X3 X3 X3 - Digit symbol test X3 X3 X3 X3 - Controlled Oral Word Association (COWA) X12 X12 X12 - Telephone Interview for Cognitive Status (TICS) X14 X14 X14 Contact information X X XX X X X X X X X X X X X X X X X X X X X X X X X12 X12 X12 Demographics - age X - educatio
