Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →An EDI 850 is an X12 Purchase Order Transaction Set: a structured electronic message used to place an order for goods or services. In X12’s annotated 004010 example, the wire text uses asterisks between data elements and tildes between segments. Read it as a specific teaching example—not a universal template for every trading partner.
What an EDI 850 is—and what it is not
X12 defines the 850 as the Purchase Order Transaction Set for EDI use. It carries the format and data contents used to place purchase orders according to customary business and industry practices. X12 says the 850 is not intended to convey purchase-order changes or purchase-order acknowledgments; those are different transaction purposes. X12’s 850 description states the scope.
A real 850 example, identified by version
The following is X12’s annotated basic purchase-order example for version 004010, referencing 004010X357. It describes ABC Aerospace Corporation ordering a line item from XYZ Aircraft Parts. Its values and segment choices illustrate that example; they do not establish what another buyer, supplier, or implementation must send. X12’s 004010 basic purchase-order example provides the annotations.
ST*850*0001~
BEG*00*RL*508517*1001*20000506**NA*IEL~
N1*BY*ABC Aerospace Corporation*9*123456789-0101~
N3*1000 BOARDWALK DRIVE~
N4*SOMEWHERE*CA*98898~
PO1*1*48*EA*3*PE*MG*R5656-2~
IT8*******B0~
CTT*1~
AMT*TT*144~
SE*10*0001~In this displayed transmission, * separates elements and ~ marks the end of a segment. Those visible characters belong to this sample; do not assume they are fixed for every interchange. The applicable X12 version and trading-partner implementation guide determine the details to follow.
How to read the segments
Transaction start: ST
ST*850*0001~ begins the transaction set. 850 identifies the purchase-order transaction type, while 0001 is its control number in this example.
Order purpose and identifiers: BEG
BEG*00*RL*508517*1001*20000506**NA*IEL~ provides order context and identifying details. X12 annotates it as an original release/delivery order, with purchase-order number 508517, release number 1001, and date 20000506 (May 6, 2000). The remaining coded values are part of this sample’s order context; their interpretation should be read in the relevant version and partner guide.
Buyer name and address: N1, N3, N4
N1*BY*ABC Aerospace Corporation*9*123456789-0101~ identifies the buyer. The BY code marks the buyer role, followed here by the organization name and identifier. N3 supplies the street address, and N4 supplies locality details: Somewhere, California, ZIP code 98898.
Ordered line: PO1
PO1*1*48*EA*3*PE*MG*R5656-2~ describes line 1: quantity 48, unit of measure EA (each), and price 3 per unit. The product identifiers include MG and manufacturer’s part number R5656-2. In this example, the line therefore represents 48 each at $3 each.
Recommended Free Tools
Substitution instruction: IT8
IT8*******B0~ carries an item-related code that X12 annotates in this example as indicating product substitution is not allowed. The specific interpretation is tied to this example and its implementation context.
Line count and order total: CTT and AMT
CTT*1~ reports one line item. AMT*TT*144~ gives the transaction total of $144, consistent with the example’s 48 units at $3 each.
Rank #4
Transaction end: SE
SE*10*0001~ closes the transaction set. The segment count is 10, and the control number 0001 matches the one in the opening ST segment.
Use the example as a reading guide, not a partner checklist
The sample makes the basic structure visible: an opening transaction identifier, order-level details, party and address information, a product line, totals, and a closing segment. Which segments, codes, identifiers, and delimiters are appropriate in a live exchange depends on the applicable X12 version and the trading partners’ implementation requirements. X12’s EDI examples index includes examples in different versions and notes that the library expands as X12 and other entities contribute examples.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
