X12 850 Purchase Order

X12 Release 3010

This standard provides the format and establishes the data contents of a purchase order transaction set. The purchase order transaction set provides for customary and established business and industry practice relative to the placement of purchase orders for goods and services.
This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.

Delimiters

• ~ Segment
• * Element
• > Component

GS Functional Group Header

Required · Max use 1

To indicate the beginning of a functional group and to provide control information

GS-01 · 479 · Functional Identifier Code · Required · Identifier (ID)

Code identifying a group of application related Transaction Sets.

• PO: Purchase Order Transaction (850)

GS-02 · 142 · Application Sender's Code · Required · String (AN) · Min 2 Max 12

Code identifying party sending transmission. Codes agreed to by trading partners.

GS-03 · 124 · Application Receiver's Code · Required · String (AN) · Min 2 Max 12

Code identifying party receiving transmission. Codes agreed to by trading partners.

GS-04 · 29 · Group Date · Required · Date (DT) · YYMMDD format

Date sender generated a functional group of transaction sets.

GS-05 · 30 · Group Time · Required · Time (TM) · HHMM format

Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).

GS-06 · 28 · Group Control Number · Required · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender.

GS-07 · 455 · Responsible Agency Code · Required · Identifier (ID) · Min 1 Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard.

• T: Transportation Data Coordinating Committee (TDCC)
• X: Accredited Standards Committee X12

GS-08 · 480 · Version / Release / Industry Identifier Code · Required · Identifier (ID)

Code indicating the version, release, subrelease and industry identifier of the EDI standard being used. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).

• 003010: Draft Standards Approved By ASC X12 Through June 1990.

Heading

010 Heading > ST

ST Transaction Set Header

Required · Max use 1

To indicate the start of a transaction set and to assign a control number

ST-01 · 143 · Transaction Set Identifier Code · Required · Identifier (ID)

Code uniquely identifying a Transaction Set.

• The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).

• 850: X12.1 Purchase Order

ST-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

Identifying control number assigned by the originator for a transaction set.

020 Heading > BEG

BEG Beginning Segment for Purchase Order

Required · Max use 1

To indicate the beginning of the purchase order transaction set and transmit identifying numbers and dates.

Usage notes

Examples:
BEG00DS01001301~~210329$
BEG00NE5201259D5201259D00210329$

BEG-01 · 353 · Transaction Set Purpose Code · Required · Identifier (ID)

Code identifying purpose of transaction set.

• 00: Original

BEG-02 · 92 · Purchase Order Type Code · Required · Identifier (ID)

Code specifying the type of Purchase Order.

• DS: Dropship
• NE: New Order

BEG-03 · 324 · Purchase Order Number · Required · String (AN) · Min 1 Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser.

BEG-04 · 328 · Release Number · Optional · String (AN) · Min 1 Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.

BEG-05 · 323 · Purchase Order Date · Required · Date (DT) · YYMMDD format

Date assigned by the purchaser to Purchase Order.

030 Heading > NTE

NTE Note/Special Instruction

Optional · Max use 100

To transmit information in a free-form format, if necessary, for comment or special instruction

NTE-01 · 363 · Note Reference Code · Optional · Identifier (ID)

Code identifying the functional area or purpose for which the note applies.

• GEN: Entire Transaction Set

NTE-02 · 3 · Free Form Message · Required · String (AN) · Min 1 Max 60

Free-form text.

080 Heading > FOB

FOB F.O.B. Related Instructions

Optional · Max use 1

To specify transportation instructions relating to shipment

Usage notes

Example: FOBPPZZ~SELLERS PLANT$

FOB-01 · 146 · Shipment Method of Payment · Required · Identifier (ID)

Code identifying payment terms for transportation charges.

• FOB01 indicates which party will pay the carrier.
• If FOB03 is present, then FOB02 is required.

• PP: Prepaid (by Seller)

FOB-02 · 309 · Location Qualifier · Optional · Identifier (ID)

Code identifying type of location.

• FOB02 is the code specifying transportation responsibility location.
• If FOB04 is present, then FOB05 is required.

• ZZ: Mutually Defined

FOB-03 · 352 · Description · Optional · String (AN) · Min 1 Max 80

A free-form description to clarify the related data elements and their content.

• If FOB07 is present, then FOB06 is required.

Usage notes

SELLERS PLANT

FOB-04 · 334 · Transportation Terms Qualifier Code · Optional · Identifier (ID) · Min 2 Max 2

Code identifying the source of the transportation terms.

FOB-05 · 335 · Transportation Terms Code · Optional · Identifier (ID) · Min 3 Max 3

Code identifying the trade terms which apply to the shipment transportation responsibility.

FOB-06 · 309 · Location Qualifier · Optional · Identifier (ID) · Min 1 Max 2

Code identifying type of location.

• FOB06 is the code specifying title passage location.

FOB-07 · 352 · Description · Optional · String (AN) · Min 1 Max 80

A free-form description to clarify the related data elements and their content.

N1 Loop Party to be Billed For Other Than Freight(Bill To) Optional Max 1

Variants (all may be used)

N1 Loop Ship ToN1 Loop Vendor

310 Heading > N1 Loop Party to be Billed For Other Than Freight(Bill To) > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name and code

Usage notes

Example: N1BTMMNA9299230$

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity or a physical location.

• At least one of N102 or N103 must be present.

• BT: Party to be Billed For Other Than Freight(Bill To)

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 35

Free-form name.

• If either N103 or N104 is present, then the other is required.

Usage notes

MMNA

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

Code designating the system/method of code structure used for Identification Code (67).

N1-04 · 67 · Identification Code · Optional · Identifier (ID) · Min 2 Max 17

Code identifying a party.

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

Usage notes

99230 Account Payable Dept Cd

320 Heading > N1 Loop Party to be Billed For Other Than Freight(Bill To) > N2

N2 Additional Name Information

Optional · Max use 2

To specify additional names or those longer than 35 characters in length

N2-01 · 93 · Name · Required · String (AN) · Min 1 Max 35

Free-form name.

Usage notes

ACCOUNTS PAYABLE DEPT

N2-02 · 93 · Name · Optional · String (AN) · Min 1 Max 35

Free-form name.

330 Heading > N1 Loop Party to be Billed For Other Than Freight(Bill To) > N3

N3 Address Information

Optional · Max use 2

To specify the location of the named party

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 35

Address information

Usage notes

4031 ASPEN GROVE DRIVE SUITE 7
FRANKLIN, TN 37067

N1 Loop Ship To Optional Max 1

Variants (all may be used)

N1 Loop Party to be Billed For Other Than Freight(Bill To)N1 Loop Vendor

310 Heading > N1 Loop Ship To > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name and code

Usage notes

Examples:
N1STFOUNTAIN MITSUBISHI9210013$
N1STEASTERN PDC OPERATION9299222$

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity or a physical location.

• At least one of N102 or N103 must be present.

• ST: Ship To

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 35

Free-form name.

• If either N103 or N104 is present, then the other is required.

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67).

• 92: Assigned by Buyer or Buyer's Agent

N1-04 · 67 · Identification Code · Optional · Identifier (ID) · Min 2 Max 17

Code identifying a party.

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

Usage notes

Dealer code or MMNA PDC location code.

PDC codes:
99225 RIVERSIDE PDC OP CA
99222 EASTERN PDC OPERATION NJ
99223 SOUTHEASTERN PDC OPE GA

330 Heading > N1 Loop Ship To > N3

N3 Address Information

Optional · Max use 2

To specify the location of the named party

Usage notes

Examples:
N38701 SO. ORANGE BLOSSOM TRAIL$
N3516 HERON DRIVE$
N3ORLANDO, FL32809-7980$
N3SWEDEBORO, NJ08085$

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 35

Address information

N3-02 · 166 · Address Information · Optional · String (AN) · Min 1 Max 35

Address information

N1 Loop Vendor Optional Max 1

Variants (all may be used)

N1 Loop Party to be Billed For Other Than Freight(Bill To)N1 Loop Ship To

310 Heading > N1 Loop Vendor > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name and code

Usage notes

Example: N1VNAMREP AUTOMOTIVE PRODUCTS GROUP9210W01$

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity or a physical location.

• At least one of N102 or N103 must be present.

• VN: Vendor

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 35

Free-form name.

• If either N103 or N104 is present, then the other is required.

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67).

• 92: Assigned by Buyer or Buyer's Agent

N1-04 · 67 · Identification Code · Optional · Identifier (ID) · Min 5 Max 5

Code identifying a party.

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

Usage notes

Vendor Code assigned by MMNA.

Detail

PO1 Loop Required Max >1

010 Detail > PO1 Loop > PO1

PO1 Purchase Order Baseline Item Data

Required · Max use 1

To specify basic and most frequently used purchase order line item data

Usage notes

Example: PO10000112EA10.25~~BP~MB568933$

PO1-01 · 350 · Assigned Identification · Optional · String (AN) · Min 1 Max 6

Alphanumeric characters assigned for differentiation within a transaction set.

• PO101 is the line item identification
• If PO105 is present, then PO104 is required.

PO1-02 · 330 · Quantity Ordered · Required · Decimal number (R) · Min 1 Max 9

Quantity ordered.

• If PO106 is present, then PO107 is required.

PO1-03 · 355 · Unit of Measurement Code · Required · Identifier (ID)

Code identifying the basic unit of measurement.

• If PO108 is present, then PO109 is required.

• EA: Each

PO1-04 · 212 · Unit Price · Optional · Decimal number (R) · Min 1 Max 14

Price per unit of product, service, commodity, etc.

• If PO110 is present, then PO111 is required.

PO1-06 · 235 · Product/Service ID Qualifier · Optional · Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

• PO106 through PO125 provide for ten (10) different product/service ID's per each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
• If PO114 is present, then PO115 is required.

• BP: Buyer's Part Number

PO1-07 · 234 · Product/Service ID · Optional · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If PO116 is present, then PO117 is required.

PID Loop Optional Max >1

050 Detail > PO1 Loop > PID Loop > PID

PID Product/Item Description

Required · Max use 1

To describe a product or process in coded or free-form format

Usage notes

Example: PID~F~~~~CABIN AIR FILTER$

PID-01 · 349 · Item Description Type · Required · Identifier (ID)

Code indicating the format of a description.

• When PID01 is ``F'', PID04 is not used.

• F: Free-form

PID-05 · 352 · Description · Optional · String (AN) · Min 1 Max 80

A free-form description to clarify the related data elements and their content.

100 Detail > PO1 Loop > REF

REF Reference Numbers

Optional · Max use 12

To specify identifying numbers.

Usage notes

Used with Dropship orders.

Example: REFDC0612S$

REF-01 · 128 · Reference Number Qualifier · Required · Identifier (ID)

Code qualifying the Reference Number.

• DC: Dealer purchase order number

REF-02 · 127 · Reference Number · Optional · String (AN) · Min 1 Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

• Either REF02 or REF03 is required.

Usage notes

MMNA Dealer dropship order number.

REF-03 · 352 · Description · Optional · String (AN) · Min 1 Max 80

A free-form description to clarify the related data elements and their content.

230 Detail > PO1 Loop > SCH

SCH Line Item Schedule

Optional · Max use 200

To specify the data for scheduling a specific line item.

• The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of measurement code in the associated PO1 segment (PO103) and the sum of values of quantity (SCH01) should always equal the quantity ordered (PO102) in the PO1 segment.

Usage notes

Example: SCH12EA~~~002~210329$

SCH-01 · 380 · Quantity · Required · Decimal number (R) · Min 1 Max 10

Numeric value of quantity.

• If SCH03 is present, then SCH04 is required.

SCH-02 · 355 · Unit of Measurement Code · Required · Identifier (ID)

Code identifying the basic unit of measurement.

• If SCH09 is used, then SCH08 is required.

• EA: Each

SCH-05 · 374 · Date/Time Qualifier · Required · Identifier (ID)

Code specifying type of date or time, or both date and time.

• 002: Delivery Requested

SCH-06 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• SCH05 specifies the interpretation to be used for SCH06 and SCH07.

Summary

010 Summary > CTT

CTT Transaction Totals

Required · Max use 1

To transmit a hash total for a specific element in the transaction set

• 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.

Usage notes

Example: CTT88932$

CTT-01 · 354 · Number of Line Items · Required · Numeric (N0) · Min 1 Max 6

Total number of line items in the transaction set.

• If CTT03 is present, then CTT04 is required.

CTT-02 · 347 · Hash Total · Optional · Decimal number (R) · Min 1 Max 10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

## Example:
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.

1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.

• If CTT05 is present, then CTT06 is required.

020 Summary > AMT

AMT Monetary Amount

Optional · Max use 1

To indicate the total monetary amount.

Usage notes

Example: AMTTT16815.80$

AMT-01 · 522 · Amount Qualifier Code · Required · Identifier (ID)

Code to qualify amount

• If AMT is used in the detail area of transaction set 850, 855, 860 or 865, AMT02 will indicate total line amount as calculated by the sender. If AMT is used in the summary area of transaction set 850, 855, 860 or 865, AMT02 will indicate total transaction amount as calculated by the sender.
• If segment AMT is used in Table 2 of the 850, 855, 860 or 865 transaction sets, then AMT01 = 01. If it is used in Table 3 of those transaction sets, then AMT01 = TT.

• TT: Total Transaction Amount

AMT-02 · 782 · Monetary Amount · Required · Decimal number (R) · Min 1 Max 15

Monetary amount.

030 Summary > SE

SE Transaction Set Trailer

Required · Max use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

SE-01 · 96 · Number of Included Segments · Required · Numeric (N0) · Min 1 Max 6

Total number of segments included in a transaction set including ST and SE segments.

SE-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

Identifying control number assigned by the originator for a transaction set.

GE Functional Group Trailer

Required · Max use 1

To indicate the end of a functional group and to provide control information

GE-01 · 97 · Number of Transaction Sets Included · Required · Numeric (N0) · Min 1 Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.

GE-02 · 28 · Group Control Number · Required · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender.

EDI Samples

Dropship Order

ISA*00*          *00*          *ZZ*SENDER         *ZZ*RECEIVER       *240113*2000*U*00301*000000001*0*T*>~
GS*PO*SENDERGS*RECEIVERGS*240113*200009*000000001*X*003010~
ST*850*000247343~
BEG*00*DS*01508401**210121~
FOB*PP*ZZ*SELLERS PLANT~
N1*BT*MMSA*92*99230~
N2*ACCOUNTS PAYABLE DEPTN3*4031 ASPEN GROVE SUITE~
N3* FRANKLIN, TN 37067~
N1*ST*ANDERSON MITSUBISHI*92*1508~
N3*224 NORTH ALPINE ROAD*ROCKFORD~
N1*VN*INTERSTATE BATTERY SYSTEM OF AMERIC*92*44V49~
PO1*01*3*EA*68.99**BP*AMG8FB1X01~
PID*F****BATTERY,GROUP 35~
REF*DC*B119SSCH*3~
CTT*1*3~
AMT*TT*206.97~
SE*15*000247343~
ST*850*000247344~
BEG*00*DS*03001701**210121~
FOB*PP*ZZ*SELLERS PLANT~
N1*BT*MMSA*92*99230~
N2*ACCOUNTS PAYABLE DEPT~
N3*6400 WEST KATELLA AVE~
N3*CYPRESS, CA 90630~
N1*ST*MOXIE MITSUBISHI*92*30017~
N3*3330 SUPERIOR STREET* LINCOLN~
N3*NE 68504~
N1*VN*INTERSTATE BATTERY SYSTEM OF AMERIC*92*44V49~
PO1*01*1*EA*68.99**BP*AMG8FB1X01~
PID*F****BATTERY,GROUP 35~
REF*DC*0120S~
SCH*1*EA***002*210126~
CTT*1*1~
AMT*TT*68.99~
SE*18*000247344~
GE*2*000000001~
IEA*1*000000001~

PDC Purchase Order

ISA~00~          ~00~          ~ZZ~SENDER         ~ZZ~RECEIVER       ~240113~2301~U~00301~000000001~0~T~>
GS~PO~SENDERGS~RECEIVERGS~240113~230152~000000001~X~003010
ST~850~000005233
BEG~00~NE~5201259D~5201259D00~210129
FOB~PP~ZZ~SELLERS PLANT
N1~BT~MMNA~92~99230
N2~ACCOUNTS PAYABLE DEPT
N3~4031 ASPEN GROVE SUITE 7
N3~FRANKLIN, TN 37067
N1~ST~EASTERN PDC OPERATIO~92~99222
N3~516 HERON DRIVE~SWEDESBORO
N3~NJ 08085
N1~VN~DENSO PRODS & SVS AMERICAS INC~92~05V06
PO1~000001~2~EA~10.1~~BP~MB568933
PID~F~~~~PULLEY ASSY,A/C
SCH~2~EA~~~002~210305
PO1~000002~10~EA~5.56~~BP~MR571396
PID~F~~~~ELEMENT,AIR CLEA
SCH~10~EA~~~002~210305
PO1~000003~7420~EA~1.65~~BP~MZ690072
PID~F~~~~OIL FILTER (ASP)
SCH~7420~EA~~~002~210305
PO1~000004~200~EA~2.85~~BP~MZ690960
PID~F~~~~CABIN AIR FILTER
SCH~200~EA~~~002~210305
PO1~000005~200~EA~2.85~~BP~MZ691041
PID~F~~~~CABIN AIR FILTER
SCH~200~EA~~~002~210305
PO1~000006~120~EA~5.5~~BP~MZ691044
PID~F~~~~CABIN AIR FILTER
SCH~120~EA~~~002~210305
PO1~000007~960~EA~2.65~~BP~1230A105
PID~F~~~~OIL FILTER
SCH~960~EA~~~002~210305
PO1~000008~20~EA~7.65~~BP~1500A023
PID~F~~~~ELEMENT,AIR CLEA
SCH~20~EA~~~002~210305
CTT~8~8932
AMT~TT~16815.8
SE~38~000005233
GE~1~000000001
IEA~1~000000001

Sample 3

ISA*00*          *00*          *ZZ*SENDER         *ZZ*RECEIVER       *240113*2302*U*00301*000000001*0*T*>
GS*PO*SENDERGS*RECEIVERGS*240113*230223*000000001*X*003010
ST*850*0014
BEG*00*NE*510O887**231122
FOB*PP*ZZ*SELLERS  PLANT
N1*BT*MMNA*92*99230
N2*ACCOUNTS PAYABLE DEPT
N3*4031 Aspen Grove Dr., Suite 650
N3*FRANKLIN TN 37067
N1*ST*Mitsubishi Motors - WPDC- RS PDC*92*99225
N3*21800 Authority Way Ste 102*Riverside
N3*CA 92518
N1*VN*LUND MOTION PRODUCTS INC*92*05VBB
PO1*000001*30*EA*49.33**BP*MZ314642
PID*F****ALLOY FUEL DOOR
SCH*30*EA***002*240803
CTT*1*30
AMT*TT*1479.9
SE*17*0014
GE*1*000000001
IEA*1*000000001