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 EDI:
BEG00SA99999990*20070606~
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- BK
- Blanket Order (Quantity Firm)
- RL
- Release or Delivery Order
An order for goods and services placed against a pre-existing contract or blanket 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
For Release Orders, the presence of the Release Number > 0 indicates a Release Purchase Order for a previously sent Blanket Purchase Order. The Release Number is required on all EDI transactions sent to AT&T Mobility. Default is '0'.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Sample EDI:
CURBYUSD~
PO Type
To specify identifying information
The REF*ZZ will always be sent to the Vendor in the Purchase Order.
Sample EDI:
REFZZHandset Device Accessory~
Code qualifying the Reference Identification
- ZZ
- PO Type
Quote Number
To specify identifying information
The Quote Reference Segment is not used for Handset Device Accessory Vendors.
Sample EDI:
REFQ1999999999~
Code qualifying the Reference Identification
- Q1
- Quote Number
Supplier Number
To specify identifying information
Sample EDI:
REFZA99999999~
Code qualifying the Reference Identification
- ZA
- Supplier
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Sample EDI:
PERBDFirstName LastNameTE123-456-7890**EMemail.address@company.com~
Code identifying the major duty or responsibility of the person or group named
- BD
- Buyer Name or Department
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
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Sample EDI:
FOB*PC~
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Sample EDI:
ITD013**********IMMEDIATE~
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
Code identifying the beginning of the terms period
- 3
- Invoice Date
This loop only used for Blanket POs.
Monetary Amount
To indicate the total monetary amount
This segment only used for Blanket POs.
Sample EDI:
AMTACR12200*D~
Monetary amount
If a Blanket Purchase Order, the AMT02 will contain the Amount Agreed.
Date/Time Reference
To specify pertinent dates and times
This segment only used for Blanket POs.
Sample EDI:
DTM00720070630~
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
With N9*ZZ, AT&T Mobility will always send the value "AT&T MOBILITY MESSAGES" if the header level MSG segments exist.
Sample EDI:
N9ZZAT&T MOBILITY MESSAGES~
Code qualifying the Reference Identification
- ZZ
- Message Type
Message Text
To provide a free-form format that allows the transmission of text information
Sample EDI:
MSGFREE-FORM MESSAGE TEXTSS~
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1BTBILL TO PARTY~
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.
Address Information
To specify the location of the named party
Sample EDI:
N3*STREET ADDRESS~
Geographic Location
To specify the geographic place of the named party
Sample EDI:
N4CITYSTZIPCOUS~
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 EDI:
PERBIFirstName LastNameTE123-456-7890**EMemail.address@company.com~
Code identifying the major duty or responsibility of the person or group named
- BI
- Bill Inquiry Contact
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
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1STSHIP TO~
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.
Address Information
To specify the location of the named party
Sample EDI:
N3*STREET ADDRESS~
Geographic Location
To specify the geographic place of the named party
Sample EDI:
N4CITYSTZIPCOUS~
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 EDI:
PERSTFirstName LastNameTE123-456-7890**EMemail.address@company.com~
Code identifying the major duty or responsibility of the person or group named
- ST
- Ship To Contact
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
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1VNVENDOR NAME92VENDOR ID~
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
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.
Address Information
To specify the location of the named party
Sample EDI:
N3*STREET ADDRESS~
Geographic Location
To specify the geographic place of the named party
Sample EDI:
N4CITYSTZIPCOUS~
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 EDI:
PERSUFirstName LastNameTE123-456-7890**EMemail.address@company.com~
Code identifying the major duty or responsibility of the person or group named
- SU
- Supplier Contact
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
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Sample EDI:
PO11100EA424*SKRTL.12345VNITEM DESCRIPTION~
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
- BG
- Bag
- BX
- Box
- CA
- Case
- CT
- Carton
- DA
- Days
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- HR
- Hours
- HU
- Hundred
- LB
- Pound
- LO
- Lot
- MO
- Months
- PD
- Pad
- PF
- Pallet (Lift)
- PK
- Package
- Q1
- Quarter (Time)
- RL
- Roll
- RM
- Ream
- ST
- Set
- SY
- Square Yard
- TH
- Thousand
- YR
- Years
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.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
This is the AT&T Mobility SKU
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Additional Item Detail
To specify additional item-related data involving variations in normal price/quantity structure
The PO3 segment is only used to pass the Extended Price to the partner.
The PO301 is not used as a Change to the Purchase Order but is used as per the X12 Standard requirements dictate.
Sample EDI:
PO3UP20070606EST42400*100EA~
Code specifying the reason for price or quantity change
- UP
- Unit Price
Code identifying pricing specification
- EST
- Estimated Price
Price per unit of product, service, commodity, etc.
Extended Unit Price - This is the total price for the line item.
Calculated as Line Item Quantity x Item Unit Price = Extended Unit Price
Numeric value of quantity
This should match the Item Quantity for the item in the matching PO1 segment.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO307 defines the unit of measure for PO306.
- BG
- Bag
- BX
- Box
- CA
- Case
- CT
- Carton
- DA
- Days
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- HR
- Hours
- HU
- Hundred
- LB
- Pound
- LO
- Lot
- MO
- Months
- PD
- Pad
- PF
- Pallet (Lift)
- PK
- Package
- Q1
- Quarter (Time)
- RL
- Roll
- RM
- Ream
- ST
- Set
- SY
- Square Yard
- TH
- Thousand
- YR
- Years
Product/Item Description
To describe a product or process in coded or free-form format
Sample EDI:
PIDF***ITEM 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
Reference Identification
To specify identifying information
Used to notify the trading partner that the line item is Taxable or Non-Taxable.
Sample EDI:
REFZZTAXABLE - YES~
REFZZTAXABLE - NO~
Code qualifying the Reference Identification
- ZZ
- Taxable Flag
Message Text
To provide a free-form format that allows the transmission of text information
Item Level messages/attachments
NOTE: AT&T Mobility can send Item Level messages/attachments as well as Shipment Level messages/attachments in the N9 loop which may follow this MSG segment.
Sample EDI:
MSGFREE-FORM MESSAGE TEXTSS~
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
With N9*ZZ, AT&T Mobility will always send the value "AT&T MOBILITY MESSAGES" if the header level MSG segments exist.
Sample EDI:
N9ZZAT&T MOBILITY MESSAGES~
Code qualifying the Reference Identification
- ZZ
- Message Type
Message Text
To provide a free-form format that allows the transmission of text information
Shipment Level messages/attachments
NOTE: AT&T Mobility can send Item Level messages/attachments as well as Shipment Level messages/attachments in the MSG segment which may precede this N9 Loop.
Sample EDI:
MSGFREE-FORM MESSAGE TEXTSS~
Name
To identify a party by type of organization, name, and code
Sample EDI:
N1STMEMPHIS DISTRIBUTION CENTER9210107048~
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Free-form name
- FORT WORTH DISTRIBUTION CENTER
- MEMPHIS DISTRIBUTION CENTER
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.
- 10107048
- Memphis Distribution Center
- 10110146
- Ft. Worth Distribution Center
Address Information
To specify the location of the named party
Sample EDI:
N3*STREET ADDRESS~
Geographic Location
To specify the geographic place of the named party
Sample EDI:
N4CITYSTZIPCOUS~
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)
Quantity
To specify quantity information
Sample EDI:
QTYB3100*EA~
Code specifying the type of quantity
- B3
- Requested Amount
QTY03 should match PO103
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- BG
- Bag
- BX
- Box
- CA
- Case
- CT
- Carton
- DA
- Days
- DZ
- Dozen
- EA
- Each
- FT
- Foot
- HR
- Hours
- HU
- Hundred
- LB
- Pound
- LO
- Lot
- MO
- Months
- PD
- Pad
- PF
- Pallet (Lift)
- PK
- Package
- Q1
- Quarter (Time)
- RL
- Roll
- RM
- Ream
- ST
- Set
- SY
- Square Yard
- TH
- Thousand
- YR
- Years
Distribution Number
To specify identifying information
Distribution Number is being sent with the Line Item and is required for return on the EDI 855 PO Acknowledgement, the EDI 856 Shipment Notice and the EDI 810 Invoice. Default Distribution Number cannot be null.
Sample EDI:
REFKA1~
Code qualifying the Reference Identification
- KA
- Distribution List
Qualifies a list of addresses to which the distribution of something should be made
Shipment Number
To specify identifying information
Shipment Number is being sent with the Line Item and is required for return on the EDI 855 PO Acknowledgement, the EDI 856 Shipment Notice and the EDI 810 Invoice. Default Shipment Number cannot be null.
Sample EDI:
REFSI1~
Code qualifying the Reference Identification
- SI
- Shipper's Identifying Number for Shipment (SID)
A unique number (to the shipper) assigned by the shipper to identify the shipment
Delivery Contact
To identify a person or office to whom administrative communications should be directed
Sample EDI:
PERRQDELIVERY CONTACTTE123-456-7890~
Code identifying the major duty or responsibility of the person or group named
- RQ
- Delivery Contact
Code identifying the type of communication number
- TE
- Telephone
Ship To Contact
To identify a person or office to whom administrative communications should be directed
Sample EDI:
PERDCSHIP TO CONTACTTE123-456-7890~
Code identifying the major duty or responsibility of the person or group named
- DC
- Ship To Contact
Code identifying the type of communication number
- TE
- Telephone
Date/Time Reference
To specify pertinent dates and times
Sample EDI:
DTM01720070630~
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 EDI:
CTT*1~
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.
Sample EDI:
AMTBAP42400*D~
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
BEG*00*SA*9999999*0*20070606~
CUR*BY*USD~
REF*Q1*999999999~
REF*ZZ*Handset Device Accessory~
REF*ZA*99999999~
PER*BD*FirstName LastName*TE*123-456-7890***EM*email.address@company.com~
FOB*PC~
ITD*01*3**********IMMEDIATE~
AMT*ACR*12200*D~
DTM*007*20070630~
N9*ZZ*AT&T MOBILITY MESSAGES~
MSG*FREE-FORM MESSAGE TEXT*SS~
N1*BT*BILL TO PARTY~
N3*STREET ADDRESS~
N4*CITY*ST*ZIPCO*US~
PER*BI*FirstName LastName*TE*123-456-7890***EM*email.address@company.com~
N1*ST*SHIP TO~
N3*STREET ADDRESS~
N4*CITY*ST*ZIPCO*US~
PER*ST*FirstName LastName*TE*123-456-7890***EM*email.address@company.com~
N1*VN*VENDOR NAME*92*VENDOR ID~
N3*STREET ADDRESS~
N4*CITY*ST*ZIPCO*US~
PER*SU*FirstName LastName*TE*123-456-7890***EM*email.address@company.com~
PO1*1*100*EA*424**SK*RTL.12345*VN*ITEM DESCRIPTION~
PO3*UP*20070606*EST*42400**100*EA~
PID*F****ITEM DESCRIPTION~
REF*ZZ*TAXABLE - YES~
MSG*FREE-FORM MESSAGE TEXT*SS~
N9*ZZ*AT&T MOBILITY MESSAGES~
MSG*FREE-FORM MESSAGE TEXT*SS~
N1*ST*MEMPHIS DISTRIBUTION CENTER*92*10107048~
N3*STREET ADDRESS~
N4*CITY*ST*ZIPCO*US~
QTY*B3*100*EA~
REF*KA*1~
REF*SI*1~
PER*DC*SHIP TO CONTACT*TE*123-456-7890~
PER*RQ*DELIVERY CONTACT*TE*123-456-7890~
DTM*017*20070630~
CTT*1~
AMT*BAP*42400*D~
SE*44*0001~
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.