# X12 850 Purchase Order EDI Skeleton Generator

> Source: https://netray.co/tools/x12-850-purchase-order-edi-skeleton-generator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Builds a single-line ANSI X12 850 purchase order with ISA, GS, ST, BEG, N1 and PO1 segments you can use as a test file or mapping reference.

## Category

developer

## Audience

- EDI analyst
- ERP developer
- Buyer

## Tool

**Kind:** template

**Output:** code

**Language:** edi

**Fields:**

#### Sender ID (pad to 15 characters)

**Key:** sender

**Type:** text

**Default:** BUYERCO        

**Help:** ISA06 is a fixed 15 character field.

#### Receiver ID (pad to 15 characters)

**Key:** receiver

**Type:** text

**Default:** SUPPLIERCO     

**Help:** ISA08 is a fixed 15 character field.

#### GS sender code

**Key:** gs_sender

**Type:** text

**Default:** BUYERCO

#### GS receiver code

**Key:** gs_receiver

**Type:** text

**Default:** SUPPLIERCO

#### Date (CCYYMMDD)

**Key:** date8

**Type:** text

**Default:** 20261020

#### Date (YYMMDD)

**Key:** date6

**Type:** text

**Default:** 261020

#### PO number

**Key:** po_number

**Type:** text

**Default:** PO100245

#### Ship-to name

**Key:** ship_to

**Type:** text

**Default:** ACME PRECISION PLANT 2

#### Ship-to location code

**Key:** ship_code

**Type:** text

**Default:** PLANT02

#### Quantity

**Key:** line_qty

**Type:** number

**Default:** 250

#### Unit of measure

**Key:** uom

**Type:** select

**Options:**

- EA
- FT
- LB
- KG
- BX

**Default:** EA

#### Unit price

**Key:** unit_price

**Type:** number

**Default:** 12.4500

#### Buyer part number

**Key:** part_no

**Type:** text

**Default:** BRK-1001-A

**Blocks:**

#### 850 interchange

**Body:** ISA*00*          *00*          *ZZ*{{sender}}*ZZ*{{receiver}}*{{date6}}*0900*U*00401*000000001*0*T*>~
GS*PO*{{gs_sender}}*{{gs_receiver}}*{{date8}}*0900*1*X*004010~
ST*850*0001~
BEG*00*SA*{{po_number}}**{{date8}}~
DTM*002*{{date8}}~
N1*ST*{{ship_to}}*92*{{ship_code}}~
PO1*1*{{line_qty}}*{{uom}}*{{unit_price}}**BP*{{part_no}}~
CTT*1~
SE*7*0001~
GE*1*1~
IEA*1*000000001~

**Notes:** This is a minimal skeleton for testing and mapping, not a complete trading partner implementation. ISA06 and ISA08 must be exactly 15 characters, so pad with spaces. The SE01 count of 7 covers ST through SE and must be updated when you add segments. Many partners require PER, REF, ITD, N3, N4, SCH or PID segments and their own version, such as 004010 or 005010. Follow the partner's implementation guide and keep the ISA usage indicator at T until testing is signed off.

## Content

**Intro:** The ANSI X12 850 is the electronic purchase order. This generator produces a minimal, correctly counted 850 with one line so you can test a trading partner connection or see where each PO field lands.

**Sections:**

#### How to use it

**Body:** Fill in sender and receiver IDs, PO number, ship-to and the line details, then copy the result into a text file. Most EDI translators expect no line breaks within the interchange, so check whether your tool needs segments on one line or one per line. Send it to your own test mailbox first, and only then to the partner. Keep the usage indicator at T for test until both sides confirm acknowledgements with a 997 or 999.

**Bullets:**

- Pad ISA06 and ISA08 to 15 characters
- Keep the segment terminator and element separator consistent with the partner's setup
- Confirm the version, for example 004010, with the trading partner

#### Segments explained

**Body:** ISA and IEA wrap the interchange, and GS and GE wrap a functional group of related documents. ST and SE wrap the 850 transaction itself, and SE01 holds the number of segments between and including them. BEG starts the PO with the purpose code, the PO type and the PO number and date. DTM carries dates, N1 identifies parties such as ship-to, and PO1 holds the line: quantity, unit of measure, unit price and a qualifier pair like BP for buyer's part number. CTT counts line items.

#### Common mistakes

**Body:** The usual causes of rejection are a wrong segment count in SE01, ISA fields with the wrong length, mismatched control numbers between ISA and IEA or GS and GE, and wrong qualifiers for the receiving system. Another frequent issue is sending decimals or units the partner does not accept. Always run the file through a validator and check the acknowledgement for the exact error segment before changing mappings.

**Cta:** Netray can help build the integration between your ERP purchasing tables and your EDI translator, with a human approval step before any outbound PO is released.

**Faq:**

#### What does the 850 transaction set represent?

**Answer:** The 850 is the ANSI X12 Purchase Order. A buyer sends it to a supplier to order goods or services. The supplier usually answers with a 997 functional acknowledgement, then an 855 PO acknowledgement and later an 856 ship notice and an 810 invoice.

#### How do I count the SE01 value?

**Answer:** Count every segment from ST through SE, inclusive. In this skeleton that is ST, BEG, DTM, N1, PO1, CTT and SE, which is 7. Add one for each extra segment, including each additional PO1 line and any PID, REF or PER segments you insert.

#### Why does the ISA need fixed-length fields?

**Answer:** The ISA segment is fixed-width by specification: each element has a set length, and the interchange sender and receiver IDs are 15 characters. Parsers use these lengths to detect the separators, so wrong widths can make the whole file unreadable.

#### Can I use this in production?

**Answer:** Use it as a starting point for mapping and testing only. Production 850s need the full set of segments your trading partner requires, unique control numbers, validation and acknowledgement handling. Follow the partner's implementation guide and switch the ISA15 indicator to P only after sign-off.

## Search terms

x12 850 sample, 850 purchase order edi example, edi 850 format, edi 850 segments, x12 850 generator, edi purchase order template, edi 850 mapping

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json