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
Code identifying purpose of transaction set
This value will be transmitted on all production Purchase orders.
- 00
- Original
Code specifying the type of Purchase Order
- DS
- Dropship
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- CO
- Customer PO Reference
- CR
- Lehigh Customer Number
- PO
- Purchase Order Number
- SA
- Salesman Number
- ZZ
- Lehigh Reference Number
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
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
- PA
- Advance Prepaid
- PB
- Customer Pick-up/Backhaul
- PC
- Prepaid but Charged to Customer
- PP
- Prepaid (by Seller)
- TP
- Third Party Pay
Code identifying type of location
- FOB02 is the code specifying transportation responsibility location.
- CI
- City
- DE
- Destination (Shipping)
- FA
- Factory
- MI
- Mill
- OR
- Origin (Shipping Point)
- PL
- Plant
- RG
- Region Code
Qualifies a code that identifies a geographic area where transportation rates apply.
- TL
- Terminal Cargo Location
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 001
- Cancel After
- 002
- Delivery Requested
- 004
- PO Creation Date
- 010
- Requested Ship
- 011
- Shipped
- 015
- Promotion Start
- 023
- Promotion Order - Start
- 038
- Ship No Later
- 077
- Requested for Delivery (Week of)
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.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
If TD503 is received with a value not equal to those listed above please contact Rocky for approval prior to using that ship method.
- FE2
- FedEx 2 Day Air
- FEDG
- FedEx Ground
- FEH
- FedEx Home
- FSP
- FedEx Air
- PM
- Priority Mail
- SMPG
- FedEx SmartPost
Code specifying the method or type of transportation for the shipment
- A
- Air
- AF
- Air Freight
- B
- Barge
- BP
- Book Postal
- C
- Consolidation
- D
- Parcel Post
- E
- Expedited Truck
- FL
- Motor (Flatbed)
- H
- Customer Pickup
- I
- Common Irregular Carrier
- L
- Contract Carrier
- LT
- Less Than Trailer Load (LTL)
- M
- Motor (Common Carrier)
- O
- Containerized Ocean
- P
- Private Carrier
- Q
- Conventional Ocean
- R
- Rail
- S
- Ocean
- SE
- Sea/Air
- T
- Best Way (Shippers Option)
- U
- Private Parcel Service
- X
- Intermodal (Piggyback)
- ZZ
- Mutually defined
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Code indicating the level of transportation service or the billing service offered by the transportation carrier
- ZZ
- Mutually Defined
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
Code specifying special transportation handling instructions
- ZZZ
- Mutually Defined
Code indicating a Yes or No condition or response
- TD405 identifies if a Material Safety Data Sheet (MSDS) exists for this product. A "Y" indicates an MSDS exists for this product; an "N" indicates an MSDS does not exist for this product.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Message Text
To provide a free-form format that allows the transmission of text information
Examples:
MSGMARK CASES/Any Name~
MSGPO NUMBER/Any Name~
MSGRocky Brands, Inc. is a federal contractor. This contractor and~
MSGsubcontractor shall abide by the requirements of 41 C.F.R. §§~
MSG60-1.4(a), 60-300.5(a), and 41 C.F.R. § 60-741.5(a) and 29 CFR Section~
MSGPart 471, Appendix A to Subpart A, if applicable. These regulations~
MSGprohibit discrimination against qualified individuals based on their~
MSGstatus as protected veterans or individuals with disabilities, and~
MSGprohibit discrimination against all individuals based on their race, ~
MSGcolor, religion, sex, sexual orientation, gender identity, or national~
MSGorigin. Moreover, these regulations require that covered prime~
MSGcontractors and subcontractors take affirmative action to employ and~
MSGadvance in employment individuals without regard to race, color, ~
MSGreligion, sex, sexual orientation, gender identity, national origin, ~
MSGprotected veteran status, or disability. This contractor and~
MSGsubcontractor incorporate by reference the requirements of 29 CFR Part~
MSG*471, Appendix A to Subpart A, where applicable. ~
Name
To identify a party by type of organization, name, and code
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
- 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.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
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
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
- 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.
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
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)
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
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- UM
- Price per Unit of Measure
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.
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ST
- Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
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
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 1
GS*PO*SENDERGS*RECEIVERGS*20240517*015428*000000001*X*004010~
ST*850*000000001~
BEG*00*SA*I224356**20150725~
REF*PO*I224318~
REF*CO*Any Name~
REF*CR*I224356~
PER*SA*NICKOLE TOLLIVER~
PER*SA*740-753-9100 2065~
PER*SA*NICKOLE.TOLLIVER@ROCKYBRANDS.CCOM~
DTM*004*20150725~
DTM*010*20150811~
DTM*002*20150811~
TD5**2*SMPG*U*FEDEX SMARTPOST*******ZZ*Y~
N9*ZZ*PO MESSAGES AND TEXT*PO INSTRUCTIONS~
MSG*MARK CASES/Any Name~
MSG*PO NUMBER/Any Name~
MSG*Rocky Brands, Inc. is a federal contractor. This contractor and~
MSG*subcontractor shall abide by the requirements of 41 C.F.R. §§~
MSG*60-1.4(a), 60-300.5(a), and 41 C.F.R. § 60-741.5(a) and 29 CFR Section~
MSG*Part 471, Appendix A to Subpart A, if applicable. These regulations~
MSG*prohibit discrimination against qualified individuals based on their~
MSG*status as protected veterans or individuals with disabilities, and~
MSG*prohibit discrimination against all individuals based on their race, ~
MSG*color, religion, sex, sexual orientation, gender identity, or national~
MSG*origin. Moreover, these regulations require that covered prime~
MSG*contractors and subcontractors take affirmative action to employ and~
MSG*advance in employment individuals without regard to race, color, ~
MSG*religion, sex, sexual orientation, gender identity, national origin, ~
MSG*protected veteran status, or disability. This contractor and~
MSG*subcontractor incorporate by reference the requirements of 29 CFR Part~
MSG*471, Appendix A to Subpart A, where applicable. ~
N1*BT*Rocky Brands, Inc~
N3*39 East Canal Street~
N4*Nelsonville*OH*45764~
N1*ST*Any Name*ZZ*99999~
N3*90 HEIGHTS~
N4*MUNFORD*TN*38058~
PO1*1*1*EA*54.63**UP*883985370401*ST*14182201*SK*14182201 0 100~
CTT*1~
SE*39*000000001~
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.