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
- None included
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
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
Example: BEG00SA*1599999999**20131031
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- RE
- Reorder
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
This element contains the BJs purchase order number. This element is required to be included in the packing slip if you are creating your own.
Date expressed as CCYYMMDD
- BEG05 is the date assigned by the purchaser to purchase order.
Reference Identification
To specify identifying information
Examples:
REFIAV12345
REFIT987654321
REFX9123456789
REFCOB93993832
REFWS*23454
Code qualifying the Reference Identification
The IA and X9 qualifiers are always used.
- CO
- Customer Order Number
Customer's order number w/merchant (REF02). Customer PO Index (REF03).
- IA
- Internal Vendor Number
Merchant assigned vendor number.
- IO
- Inbound-to or Outbound-from Party
In cases where a Purchase Order is being simultaneously presented to more than one party, this REF segment identifies the other party to whom the Purchase Order is being presented. It is expected that receiver of the 850 and the party identified in this REF segment will coordinate to achieve fulfillment of the Purchase Order.
- WS
- Warehouse storage location number
Id for supplier's warehouse from which goods are to be shipped.
- X9
- Internal Control Number
CommerceHub internal ID.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
Example: DTM00620130227
Code specifying type of date or time, or both date and time
- 006
- Sold
Customer order date.
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)
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5*****UG
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
This element will contain a BJs specific code that indicates who the shipper is and what the service level is. Contact CommerceHub to obtain a complete list of codes that apply to your relationship with BJs.
Name
To identify a party by type of organization, name, and code
Example: N1BTBARBARA LEWIS
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
Free-form name
The N1 segment contains the full name for the party. If the first and last names are reported separately, they will be found in the N2 segment.
Address Information
To specify the location of the named party
Example: N321 CORPORATE DRSUITE 205
Address information
This element is required to be included in the packing slip if you are creating your own.
Address information
This element is required to be included in the packing slip if you are creating your own.
Geographic Location
To specify the geographic place of the named party
Example: N4CLIFTON PARKNY120658763USA
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
This element is required to be included in the packing slip if you are creating your own.
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.
This element is required to be included in the packing slip if you are
creating your own.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This element is required to be included in the packing slip if you are
creating your own.
Code identifying the country
This element is required to be included in the packing slip if you are
creating your own.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Used to associate a company name, telephone number and/or e-mail address with N1 entity.
Example:
PERBD**TE555-555-5555**EMCUSTOMER_SUP@ONLINE.COM
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
Used for primary instance of PER segment in N1 loop.
- IC
- Information Contact
Optional - used only when a PER segment is needed in the N1 loop to convey 'attention line'.
Free-form name
When PER01 = "BD" : Optional Company name for mailing address.
When PER01 = "IC" : Optional Attention line for mailing address.
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Name
To identify a party by type of organization, name, and code
Example: N1STJOANNE WELLS
Code identifying an organizational entity, a physical location, property or an individual
The ST qualifier will always be used.
- ST
- Ship To
Free-form name
The N1 segment contains the full name for the party. If the first and last names are reported separately, they will be found in the N2 segment.
Address Information
To specify the location of the named party
Example: N321 CORPORATE DRSUITE 205
Address information
This element will contain address line 1 for the Ship To Party.
This element is required to be included in the packing slip if you are creating your own.
Address information
This element will contain address line 1 for the Ship To Party.
This element is required to be included in the packing slip if you are creating your own.
Geographic Location
To specify the geographic place of the named party
Example: N4CLIFTON PARKNY120658763USA
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
This element is required to be included in the packing slip if you are creating your own.
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.
This element is required to be included in the packing slip if you are
creating your own.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
This element is required to be included in the packing slip if you are
creating your own.
Code identifying the country
This element is required to be included in the packing slip if you are
creating your own.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Used to associate a company name, telephone number and/or e-mail address with N1 entity.
Example:
PERBD**TE555-555-5555**EMCUSTOMER_SUP@ONLINE.COM
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
Used for primary instance of PER segment in N1 loop.
- IC
- Information Contact
Optional - used only when a PER segment is needed in the N1 loop to convey 'attention line'.
Free-form name
When PER01 = "BD" : Optional Company name for mailing address.
When PER01 = "IC" : Optional Attention line for mailing address.
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Code identifying the type of communication number
- EM
- Electronic Mail
Complete communications number including country or area code when applicable
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Example:
PO1015EA31.02TESKJ07874VN49-98760*UP99999999999
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Merchant's PO line number.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
Unit cost the merchant expects to be billed for each unit fulfilled.
Code identifying the type of unit price for an item
- FX
- Fixed Price
Buyer and seller agree on a final price; invoice cut
for this price; credit for provisional price.Used to convey unit cost adjustment flag.
- TE
- Contract 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)
This code is used to qualify the merchant's SKU code.
Identifying number for a product or service
Merchant's SKU code.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
This code is used to qualify the vendor's SKU code.
Identifying number for a product or service
Vendor's product SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
This code is used to qualify the product UPC code.
Identifying number for a product or service
UPC code.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer's Part Number
This code is used to qualify the Manufacturer's ID.
Identifying number for a product or service
Manufacturer’s ID.
Product/Item Description
To describe a product or process in coded or free-form format
Example: PIDF08***BLOUSE
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
A free-form description to clarify the related data elements and their content
Date/Time Reference
To specify pertinent dates and times
Example: DTM03820000227
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5*****UG
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
This element will contain a BJs specific code that indicates who the shipper is and what the service level is. Contact CommerceHub to obtain a complete list of codes that apply to your relationship with BJs.
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.
Example: CTT*1
Total number of line items in the transaction set
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
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.