X12 850 DTC 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
- 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
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
- 00400
- Standard Issued as ANSI X12.5-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
- 004000
- ASC X12 Standards Approved by ANSI in 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
Example: BEG00DS*9009001234**20190406~
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- DS
- Dropship
Identifying number for Purchase Order assigned by the orderer/purchaser
TSC 10-digit Purchase Order Number
Customer Order Number
To specify identifying information
Example: REFCO1234564565~
Code qualifying the Reference Identification
- CO
- Customer Order Number
Internal Vendor Number
To specify identifying information
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Example: FOB*TP~
Sales Requirements
To specify general conditions or requirements of the sale
Example: CSH*N~
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Example: ITD0530NET 30~
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.
- 05
- Discount Not Applicable
- 08
- Basic Discount Offered
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
The ITD03 will only be used if the ITD01 value is 08.
Number of days in the terms discount period by which payment is due if terms discount is earned
The ITD05 will only be used if the ITD01 value is 08.
Number of days until total invoice amount is due (discount not applicable)
Delivery Requested
To specify pertinent dates and times
Requested Ship
To specify pertinent dates and times
Example: DTM01020190406~
Paperwork
To identify the type or transmission or both of paperwork or supporting information
Only included for LTL shipments providing delivery details.
Example:
PWKBL*****ATTN CARRIER: PRIMARY CONTACT NUMBER 877-718-6750~
Code indicating the title or contents of a document, report or supporting item
- BL
- Bill of Lading
- P1
- Packing List
- PG
- Packaging Specification
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5O2UPSNU********CG~
Code describing the relationship of a carrier to a specific shipment movement
- O
- Origin Carrier (Air, Motor, or Ocean)
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.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
- CNWY
- Con-way Freight
- UPSN
- United Parcel Service
Code specifying the method or type of transportation for the shipment
- LT
- Less Than Trailer Load (LTL)
- MP
- Motor (Package Carrier)
- U
- Private Parcel Service
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Included only if there are special handling instructions.
Example: TD4*HZC~
Name
To identify a party by type of organization, name, and code
The N1ST, N1Z7 and N1*BT will always be included.
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.
- 5509
Address Information
To specify the location of the named party
Example: N3123 MAIN STSUITE A~
Geographic Location
To specify the geographic place of the named party
Example: N4NEW YORKNY10001US~
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)
Name
To identify a party by type of organization, name, and code
The N1ST, N1Z7 and N1*BT will always be included.
Code identifying an organizational entity, a physical location, property or an individual
- Z7
- Mark-for 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.
- 9999
Address Information
To specify the location of the named party
Example: N3123 MAIN STSUITE A~
Geographic Location
To specify the geographic place of the named party
Example: N4NEW YORKNY10001US~
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)
Name
To identify a party by type of organization, name, and code
The N1ST, N1Z7 and N1*BT will always be included.
Example: N1STJOE SMITH929999~
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.
- 9999
Address Information
To specify the location of the named party
Example: N3123 MAIN STSUITE A~
Geographic Location
To specify the geographic place of the named party
Example: N4NEW YORKNY10001US~
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
Example:
PERDCJOE SMITHTE123-456 7890EMCUSTOMERSERVICE@TRACTORSUPPLY.COM~
Code identifying the major duty or responsibility of the person or group named
- CR
- Customer Relations
- DC
- Delivery 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
- 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: PO1X9EA9*IN1234567VN123-456UP123456789098~
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
EDI 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.
Unit Cost
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.
- IN
- Buyer's Item Number
Identifying number for a product or service
TSC's 7-digit SKU
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Pricing Information
To specify pricing information
Example: CTP*RTL30.00~
Code identifying pricing specification
- RTL
- Retail
Product/Item Description
To describe a product or process in coded or free-form format
Example: PIDF***PRODUCT 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
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*9~
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
LTL Order Sample
GS*PO*6120930010*064193840ZZ*20190627*15372942*000000005*X*004010~
ST*850*0001~
BEG*00*DS*9003025779**20190627~
REF*CO*3003012333~
REF*IA*800410~
FOB*TP~
CSH*N~
ITD*05******60*****NET 60~
DTM*010*20190627~
DTM*002*20190712~
PWK*BL******ATTN CARRIER: PRIMARY CONTACT NUMBER 615-440-4037~
PWK*BL******ATTN CARRIER: EXPECTED DELIVERY DATE 07-12-2017~
PWK*BL******ATTN CARRIER: DELIVERY WINDOW 12:00-16:00~
PWK*BL******ATTN CARRIER: LIFTGATE REQUIRED~
PWK*BL******ATTN CARRIER: RESIDENTIAL DELIVERY~
TD5*O*2*CNWY*LT********CG~
N1*ST*First Name Last Name*92*9999~
N3*5401 VIRGINIA WAY*SUITE A3142~
N4*BRENTWOOD*TN*37027*US~
PER*DC*First Name Last Name*TE*615-440-4037*EM*CUSTOMERSERVICE@TRACTORSUPPLY.COM~
N1*Z7*First Name Last Name*92*9999~
N1*BT*TSC*92*5509~
N3*PO BOX 7000~
N4*BRENTWOOD*TN*37027*US~
PO1*10*1*EA*82.24**IN*1264211*VN*411*UP*008055041201~
CTP**RTL*99.99~
PID*F****HAMMOCK~
CTT*1~
SE*28*0001~
GE*1*000000005~
IEA*1*000000008~
Parcel Order Sample
GS*PO*6120930010*8008488707*20190411*09511312*000000004*X*004010~
ST*850*0001~
BEG*00*DS*9005008934**20190411~
REF*CO*3005008575~
REF*IA*800301~
FOB*TP~
CSH*N~
ITD*05******60*****NET 60~
DTM*010*20190412~
TD5*O*2*UPSN*U********SC~
N1*ST*FirstName LastName*92*9999~
N3*5401 VIRGINIA WAY~
N4*BRENTWOOD*TN*37027-7536*US~
PER*DC*FirstName LastName*TE*615-440-4037*EM*CUSTOMERSERVICE@TRACTORSUPPLY.COM~
N1*Z7*FirstName LastName*92*9999~
N1*BT*TSC*92*5509~
N3*PO BOX 7000~
N4*BRENTWOOD*TN*37027*US~
PO1*10*1*EA*12.99**IN*1213140*VN*CSNSS58075*UP*078627583336~
CTP**RTL*18.99~
PID*F****Swan Soft Supple 75 ft. x 5/8 in. Water Hose~
CTT*1~
SE*22*0001~
GE*1*000000004~
IEA*1*000000005~
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.