X12 850 Purchase Order
This X12 Transaction Set 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
- ^ Repetition
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
- 08
- UCC EDI Communications ID (Comm ID)
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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00501
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Interchange Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested (TA1)
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 005010
- Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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) is 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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
- 01
- Cancellation
- 04
- Change
- 05
- Replace
Code specifying the type of Purchase Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
BEG03 is the Buckle purchase order number. You will need to return this number (unaltered) on the 856 as well as the future 810 document.
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BEG05 is the date assigned by the purchaser to purchase order.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Reference Information Department
To specify identifying information
Reference Information Internal Vendor Number
To specify identifying information
REF*IA Segment – this is the internal Buckle vendor number. This number is expected back on the 856 in addition to the future 810 (Invoice). It is used to tie back your shipments/invoice to our existing order.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- CN
- General Contact
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
Sales Requirements
To specify general conditions or requirements of the sale
Code to identify a specific requirement or agreement of sale
- P2
- Ship As Soon As Possible
- P3
- May Preship
- P4
- Do Not Preship
- SC
- Ship Complete
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.
- 02
- End of Month (EOM)
- 04
- Deferred or Installment
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 where CC represents the first two digits of the calendar year
Number of days in the terms discount period by which payment is due if terms discount is earned
Number of days until total invoice amount is due (discount not applicable)
Date/Time Reference Cancel
To specify pertinent dates and times
Date/Time Reference Ship
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
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.
- 91
- Assigned by Seller or Seller's Agent
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.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
- PK
- Package
Code identifying the type of unit price for an item
- LE
- Catalog 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
- UCC - 12
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IT
- Buyer's Style Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BO
- Buyers Color
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
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
A free-form description to clarify the related data elements and their content
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code designating the system/method of code structure used for Identification Code (67)
- SDQ02 is used only if different than previously defined in the transaction set.
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- SDQ03 is the store number.
Date/Time Reference Cancel
To specify pertinent dates and times
DTM segments at the Item Level – we will occasionally order items and want them shipped at different dates. Pay careful attention to this segments because there can be multiple ship dates per order.
Date/Time Reference Cancel
To specify pertinent dates and times
DTM segments at the Item Level – we will occasionally order items and want them shipped at different dates. Pay careful attention to this segments because there can be multiple ship dates per order.
Subline Item Detail
To specify product subline detail item data
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- IT
- Buyer's Style Number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BO
- Buyers Color
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- UCC - 12
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 850
BEG*05*SA*0999999**20230331~
CUR*BY*USD~
REF*DP*062~
REF*IA*999999~
PER*CN*EDI Support*EM*EDI.SUPPORT@BUCKLE.COM~
CSH*SC~
ITD*04*1*0.5**30**30~
PO1*0001*340*EA*7.5*LE*SK*999999100*IT*XXX*BO*WHT*IZ*SMALL~
CTP**RES*34.99~
PID*F****SLEEVELESS FUNNEL MO~
SDQ*EA*92*900*340~
DTM*001*20230428~
DTM*010*20230414~
PO1*0002*445*EA*7.5*LE*SK*999999200*IT*XXX*BO*WHT*IZ*MEDIUM~
CTP**RES*34.99~
PID*F****SLEEVELESS FUNNEL MO~
SDQ*EA*92*900*445~
DTM*001*20230428~
DTM*010*20230414~
PO1*0003*360*EA*7.5*LE*SK*999999300*IT*XXX*BO*WHT*IZ*LARGE~
CTP**RES*34.99~
PID*F****SLEEVELESS FUNNEL MO~
SDQ*EA*92*900*360~
DTM*001*20230428~
DTM*010*20230414~
PO1*0004*85*EA*7.5*LE*SK*999999400*IT*XXX*BO*WHT*IZ*XLARGE~
CTP**RES*34.99~
PID*F****SLEEVELESS FUNNEL MO~
SDQ*EA*92*900*85~
DTM*001*20230428~
DTM*010*20230414~
PO1*0005*50*EA*7.5*LE*SK*999999600*IT*XXX*BO*WHT*IZ*XSMALL~
CTP**RES*34.99~
PID*F****SLEEVELESS FUNNEL MO~
SDQ*EA*92*900*50~
DTM*001*20230428~
DTM*010*20230414~
CTT*5~
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.