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
Example: BEG00SA~PONUMBER~~20001114
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Example: FOB~PP
Sales Requirements
To specify general conditions or requirements of the sale
Example: CSH~P2
Code to identify a specific requirement or agreement of sale
- AS
- Restricted to Approved Sources
Use for promotion type orders.
- P2
- Ship As Soon As Possible
Use for Daily Orders
- UL
- Other Unlisted Sales Condition
Use for legacy promotions.
- W
- Warehouse Ship
Use for Stock Orders
- Z
- Mutually Defined
Use for Special Handling Orders
Service Characteristic Identification
To specify service characteristic data
This segment should be used for one or more of the options described in SI02 and SI03. These options depend on and relate to the type of product ordered. Paired elements SI02/SI03, SI04/SI05, SI06/SI07, SI08/SI09, SI10/SI11, and SI12/SI13 should be used as appropriate for the flags described in the segment layout below.
Example: SIASCB~1
Code identifying the agency assigning the code values
- SI01 defines the source for each of the service characteristics qualifiers.
- AS
- Assigned by Seller
Code from an industry code list qualifying the type of service characteristics
- CB
- Cancel Backorder
- CR
- Cancel Referral
- FB
- Feedback
- FT
- Flex Terms
- PR
- Promotion
- UD
- Upgrade Daily/Special Handling
Identifying number for a product or service
If SI02 = 'CB', this flag is used by the system to cancel any backorders which may occur in the processing of an order. Use '1' to request the cancel.
If SI02 = 'CR', this flag is used to cancel any PDC to PDC referral portion of a line
item order. Use value of '1' to request cancel of referrals.
If SI02 = 'FT', this flag is used to request a special discount structure:
'1' = base/normal discount structure.
'2' = return allowance.
'3' = flex plus: discount with zero return allowance.
If SI02 = 'UD', this provides for the option to upgrade the backordered items on the order to special (expedited) handling. Use value of '1' to request upgrade.
If SI02 = 'FB', this provides for capability to request feedback on the order. Valid values are:
'1' = Feedback on exceptions including referrals, supersedences, items not from facing depot.
'2' = Feedback on entire order.
If SI02 = 'PR', three character code used to identify the promotion being requested.
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Code from an industry code list qualifying the type of service characteristics
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5~~2CETRLT
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)
Name
To identify a party by type of organization, name, and code
At least two iterations are mandatory for Bill To Location and Ship To Location.
Examples:
N1BT~~9111759
N1ST~~9143171
Code identifying an organizational entity, a physical location, property or an individual
- BT
- Bill-to-Party
- DL
- Dealer
- DS
- Distributor
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 91
- Assigned by Seller or Seller'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.
FCA US-assigned code.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Example: PO1~~30EA~~~VP04574512AF
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
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
- VP
- Vendor's (Seller's) Part Number
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- BO
- Bin Location Number
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*20240809*210558*000000001*X*004010~
ST*850*0001~
BEG*00*SA*123456**20101120~
FOB*PP~
CSH*P2~
SI*AS*CB*1~
TD5**2*CETR*LT~
N1*BT**91*11759~
N1*ST**91*11759X~
PO1**30*EA***VP*NAGSPART~
CTT*1~
SE*11*0001~
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.