X12 850 Purchase Order (Shrinkwrapped Orders)
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
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: BEG00NE*MH80312**20150831
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- NE
- New Order
Adobe: Shrink Wrap
- SA
- Stand-alone Order
Adobe: Shrink Wrap
Identifying number for Purchase Order assigned by the orderer/purchaser
Adobe: The maximum PO length for Adobe's back office is 20 characters. PO numbers exceeding 20 characters will be truncated by Adobe's back office system to the first 20 characters read.
Date expressed as CCYYMMDD
- BEG05 is the date assigned by the purchaser to purchase order.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Currency is MANDATORY and must be sent.
Example: CURSEUSD
Reference Identification
To specify identifying information
This reference identification is used by Adobe to communicate the buying party's contract number.
Example: REFCT123456
Code qualifying the Reference Identification
REF with CT qualifier contains the contract number between the partner originating the PO and Adobe.
- CT
- Contract Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Delivery Requested
To specify pertinent dates and times
Example: DTM00220150901
Requested Ship
To specify pertinent dates and times
Example: DTM01020150831
Name
To identify a party by type of organization, name, and code
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Bill-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Bill-To ID.
Example: N1BTBILL TOZZ04332571
Code identifying an organizational entity, a physical location, property or an individual
Adobe: All parties are required to process the purchase order.
- BT
- Bill-to-Party
This code represents the Bill-To Party.
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- ZZ
- Mutually Defined
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.
Name
To identify a party by type of organization, name, and code
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Sold-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Sold-To ID.
Example: N1BYBUYING PARTYZZ04332571
Code identifying an organizational entity, a physical location, property or an individual
Adobe: All parties are required to process the purchase order.
- BY
- Buying Party (Purchaser)
This code represents the Sold to party.
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- ZZ
- Mutually Defined
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.
Name
To identify a party by type of organization, name, and code
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Payer ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Payer ID.
Example: N1POPAYER PARTYZZ04332571
Code identifying an organizational entity, a physical location, property or an individual
All parties are required to process the purchase order.
- PO
- Party to Receive Invoice for Goods or Services
This code represents the Payer party.
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- ZZ
- Mutually Defined
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.
Name
To identify a party by type of organization, name, and code
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the destination party. It is encouraged that the trading partners codify all addresses within their systems.
Adobe: ID codes are utilized for location identification. Additions, Enhancements, or Changes to the Ship-To ID will require extra configuration on Adobe’s Part. Please contact your Adobe Business Representative to provide any changes or additions for Ship-To ID.
Example: N1STSHIP TOZZ04332571
Code identifying an organizational entity, a physical location, property or an individual
Adobe: All parties are required to process the purchase order.
- ST
- Ship To
This code represents the ship-to party.
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
- ZZ
- Mutually Defined
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
COMPTIA: In this Header position of the Purchase Order document, this segment provides additional detail to the N1 segment. It is encouraged that the trading partners codify all addresses within their systems.
Example: N2*M. BUYER
Address Information
To specify the location of the named party
Adobe: Adobe accepts up to 3 iterations of the N3. This first iterations contains address lines 1 and 2 and the second iteration contains address line 3. Only the N301 will be used from the second iteration. If an N302 is sent it will not be mapped.
Example: N3*123 MAIN STREET, SE
Address information
Adobe: The maximum length for Adobe's back office is 35 characters. A street address exceeding 35 characters will be truncated by Adobe's back office system to the first 35 characters read.
Address information
Adobe: The maximum length for Adobe's back office is 35 characters. A street address exceeding 35 characters will be truncated by Adobe's back office system to the first 35 characters read.
Geographic Location
To specify the geographic place of the named party
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the city, state/province, and postal code of the destination party.
Example: N4CEDAR RAPIDSIA*524032140
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)
Code identifying the country
COMPTIA: For U.S. and Canadian locations, CompTIA does not recommend the use of N404. For non-U.S./Canadian locations the two-character country code qualifier established by ISO 3166(E/F) should be used.
Adobe: For non-U.S./Canadian locations, the two-character country code qualifier established by ISO 3166(E/F) is MANDATORY.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
COMPTIA: In this Header position of the Purchase Order document, this segment identifies the parties responsible for originating the Purchase Order.
Example: PERICJ SMITHTE8015551234FX8015554321EMjohn@doe.com
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Adobe: Used to communicate general contact information.
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
- FX
- Facsimile
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
Adobe: Adobe's back office allows for an email address with a MAXIMUM of 58 characters in length.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Adobe: There is one PO1 segment for each line item. Product/Service ID's must be sent in the order listed.
Example: PO1111EA588.00CABP12345678MG*65158494
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Adobe: This element is used to identify the purchase order line item 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
- CA
- Catalog
- 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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MG
- Manufacturer's Part Number
Identifying number for a product or service
Date/Time Reference
To specify pertinent dates and times
Example: DTM01020150831
Adobe: Code specifying type of date or time, or both date and time
- 010
- Requested Ship
A requested ship date provided at this detail level will override the date provided in the DTM segment at the header level.
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
Monetary Amount
To indicate the total monetary amount
- If AMT is used in the summary area, then AMT01 will = TT and AMT02 will indicate total transaction amount as calculated by the sender.
Adobe: All monetary amounts must be provided in USD. This segment will be used to verify that the total extended values of the line items match this total amount. If there is any discrepancy our translator will reject the 850 document.
Example : AMTTT6468
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
GS*PO*SENDERGS*RECEIVERGS*20231030*023108*000000001*X*004010
ST*850*130581
BEG*00*NE*MH80312**20150831
CUR*SE*USD
REF*CT*123456
DTM*010*20150831
DTM*002*20150901
N1*BY*BUYING PARTY*ZZ*04332571
N1*PO*PAYER PARTY*ZZ*04332571
N1*BT*BILL TO*ZZ*04332571
N1*ST*SHIP TO*ZZ*04332571
N2*M. BUYER
N3*123 MAIN STREET, SE
N4*CEDAR RAPIDS*IA*524032140
PER*IC*J SMITH*TE*8015551234*FX*8015554321*EM*john@doe.com
PO1*1*11*EA*588.00*CA*BP*12345678*MG*65158494
DTM*010*20150831
CTT*1
AMT*TT*6468
SE*19*130581
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.