X12 850 Purchase Order
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 Electronic Data Interchange (EDI) environment. 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. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- PO
- Purchase Order (850)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
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
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 850
- Purchase Order
Beginning Segment for Purchase Order
To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates
Sample BEG Segment
BEG00SA*3131986**20110508
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Reference Identification
To specify identifying information
Sample REF Segments
REFVR1713
Code qualifying the Reference Identification
- VR
- Vendor ID Number
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Sample REF Segments
FOBPODE
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- PO
- Prepaid Only
Sales Requirements
To specify general conditions or requirements of the sale
Sample CSH Segments
CSHSC
CSHBK
Code to identify a specific requirement or agreement of sale
- BK
- Ship Partial - Balance Back Order
- SC
- Ship Complete
Monetary amount
- CSH03 is the maximum monetary amount value which the order must not exceed.
Account number assigned
- CSH04 is the account number to which the purchase amount is charged.
Cancel After
To specify pertinent dates and times
Sample DTM Segment
DTM00120110531
Requested Ship Date
To specify pertinent dates and times
Sample DTM Segment
DTM01020110508
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Sample TD5 Segment
TD52*UPSNNS*******G2
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
- FDE
- Federal Express
- UPSN
- United Parcel Service
- USPS
- United States Postal Service
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Sample N9 Segment
N9L1Notes
Code qualifying the Reference Identification
- L1
- Letters or Notes
Message Text
To provide a free-form format that allows the transmission of text information
Sample MSG Segment
Note: If the message is greater than 264 characters, the MSG segment will repeat as many times as needed to display the entire message.
MSGVen comments 1 (SAY 6/26/2012) Ven comments 2
MSGVen comments 3 (SAY 6/26/2012) Ven comments 4
Multiple occurrences of the N1 though N4 may be sent.
Sample N1 through N4 Segments
N1BT Accounts Payable
N3789 Main Street
N4MinneapolisMN55440*USA
Name
To identify a party by type of organization, name, and code
Sample N1
N1BT Accounts Payable
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- 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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Sample N2 Segment
N2*Attn John Smith
Address Information
To specify the location of the named party
Sample N3
N3*789 Main Street
Geographic Location
To specify the geographic place of the named party
Sample N4
N4MinneapolisMN55440USA
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Sample PER Segment
PERCNCONTACT NAME**TE826 803-9087
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- FX
- Facsimile
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
- TE
- Telephone
Multiple occurrences of the N1 though N4 may be sent.
Sample N1 through N4 Segments
N1STJane Doe92D20
N3123 Some StreetApt 1
N4AnyplaceMN55555USA
Name
To identify a party by type of organization, name, and code
Sample N1
N1STJane Doe92D20
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- 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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Sample N2 Segment
N2*Attn John Smith
Address Information
To specify the location of the named party
Sample N3
N3123 Some StreetApt 1
Geographic Location
To specify the geographic place of the named party
Sample N4
N4AnyplaceMN55555USA
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Sample PER Segment
PERCNCONTACT NAME**TE826 803-9087
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- FX
- Facsimile
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- FX
- Facsimile
- TE
- Telephone
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Sample PO1 Segment
PO1011000EA19.45PEVC9876543UP102398765423SK*123456
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Order Line Number
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- PE
- Price per Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VC
- Vendor's (Seller's) Catalog Number
Identifying number for a product or service
When PO106 = SK, this value is the buyers SKU
When PO106 = IN, this value is the Buyer’s item ID
When PO106 =VP, this value is the vendors Part number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VC
- Vendor's (Seller's) Catalog Number
Identifying number for a product or service
When PO108 = SK, this value is the Vendor SKU
When PO108 = IN, this value is the Buyer’s item ID
When PO108 =VP, this value is the vendors Part number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VC
- Vendor's (Seller's) Catalog Number
Product/Item Description
To describe a product or process in coded or free-form format
Sample PID Segment
PIDF08***Description
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Code identifying the general class of a product or process characteristic
- 08
- Product
Summary
Transaction Totals
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.
Sample CTT Segment
CTT*1
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample
GS*PO*SENDERGS*RECEIVERGS*20231031*004741*000000001*X*004010
ST*850*0001
BEG*00*SA*123456789**20110508
REF*VR*12345
DTM*010*20120101
TD5**2*UPSN**NS*******G2
N9*L1*Notes
MSG*Ven comments 1 (SAY 6/26/2012) Ven comments 2 (SAY 6/26/2012) Ven Comments 3 (SAY 6/26/2012) Ven comments 4 (SAY 6/26/2012) Ven comments 5 (SAY 6/26/2012) Ven Comments 6 (SAY 6/26/2012) Ven comments 7 (SAY 6/26/2012)
MSG*Ven comments8 (SAY 6/26/2012) Ven comments 9
N1*ST*Jane Doe
N3*123 Some Street*Apt 1
N4*Anyplace*MN*55555*USA
PER*CN*CONTACT NAME*TE*826 803-9087
PO1*01*1000*EA*19.45*PE*VC*9876543*UP*102398765423*SK*123456
PID*F*08***Description
PO1*02*1500*EA*9.99*PE*VC*9876542*UP*1012354754424*SK*123457
PID*F*08***Item Description
CTT*2
SE*18*0001
GE*1*000000001
IEA*1*000000001
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.