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
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- DS
- Dropship
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Keystone's Purchase Order Number
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
- 01
- Basic
- 04
- Deferred or Installment
Code identifying the beginning of the terms period
- 3
- Invoice Date
- 15
- Receipt of Goods
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Date payment is due if discount is to be earned expressed in format CCYYMMDD
Number of days in the terms discount period by which payment is due if terms discount is earned
Date when total invoice amount becomes due expressed in format CCYYMMDD
Number of days until total invoice amount is due (discount not applicable)
Date deferred payment or percent of invoice payable is due expressed in format CCYYMMDD
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Message Text
To provide a free-form format that allows the transmission of text information
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Bill To Party City
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.
Bill To State/Province Code
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Bill To Postal Code
Name
To identify a party by type of organization, name, and code
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.
Keystone's Location Code or Blank for dropships
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Ship To City
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.
Ship To State/Province Code
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Ship To Postal Code
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Keystone's 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/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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Keystone's Part Number
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.
- VN
- Vendor's (Seller's) Item Number
Product/Item Description
To describe a product or process in coded or free-form format
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
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.
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 1
GS*PO*011678799*000000000000*20150811*141900*000000019*X*004010~
ST*850*0001~
BEG*00*SA*0161713**20150811~
REF*IA*X99~
ITD************TERMS DESCRIPTION~
DTM*002*20150825~
TD5*****ROADWAY~
N9*ZZ*01~
MSG*ALL TERMS AND DISCOUNTS APPLY ATTN BARB ~
MSG*COMBINE ORDERS 555-555-5555 FAX~
MSG*CONFIRM W/ERIKA – PURCHASING FAX 555 555 5555~
MSG*PLEASE DELIVER WITHIN NORMAL LEAD-TIMES~
MSG* D.O.D. PROGRAM ACCOUNT #99999 B/O~
MSG*PACKING SLIP MUST BE IN AN ENVELOPE AND ATTACHED TO THE BILL OF LADING; THE~
MSG*BILL MUST THEN BE MARKED TO SHOW THIS AS A PIECE OF GOODS BEING SHIPPED.~
N1*BT*KEYSTONE AUTOMOTIVE OPERATIONS, INC.~
N3*44 TUNKHANNOCK AVENUE~
N4*EXETER*PA*18643*USA~
N1*ST*KEYSTONE AUTOMOTIVE OPERATIONS*92*01~
N3*SLOCUM AVENUE~
N4*EXETER*PA*18643*USA~
PO1*00001*2*EA*17.25**BP*17221*VN*A-17221~
PID*F****PART DESCRIPTION 1~
PO1*00002*2*EA*45.99**BP*17228*VN*A-17228~
PID*F****PART DESCRIPTION 2~
PO1*00003*2*EA*6.50**BP*17267*VN*A-17267~
PID*F****PART DESCRIPTION 3~
CTT*3~
SE*28*0001~
GE*1*000000019~
IEA*1*000000019~
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.