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
Examples:
BEG00SAE0306631**20090219
BEG00DS02010001**20151101
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- DS
- Dropship
Change for TW suppliers on drop shipments was “KN”.
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Reference Identification
To specify identifying information
Example: REFPDXX123
Code qualifying the Reference Identification
- PD
- Promotion/Deal Number
Date/Time Reference Delivery Requested
To specify pertinent dates and times
Date/Time Reference Requested Ship
To specify pertinent dates and times
Example: DTM01020090301
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5*ZZUPLN
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.
- ZZ
- Mutually Defined
Code identifying a party or other code
- AACT
- AAA Cooper Transportation
- BEST
- To be determined by Warehouse
- CROSS
- Cross Dock at Operations
- CUPS
- Cross Dock at Operation, to be shipped UPS
- DROP
- Drop Ship from Vendor to Customer
- ESTES
- Estes
- FX2D
- FED EX - Econ / 2 Day Service
- FX3D
- FED EX – 3rd Day
- FXGD
- FED EX – Ground
- FXON
- FED EX – Priority O/N AM
- FXSD
- FED EX – Priority Sat Delivery
- RDWY
- Roadway
- RLCA
- R&L Carriers
- RMDS
- Rayloc Merchandise Distribution
- SEFL
- Southeatern Freight Line
- SHUT
- Shuttle
- SPCL
- Special Instructions
- U2AM
- UPS – 2nd Day Early AM
- U2DA
- UPS – 2nd Day Air
- U3DS
- UPS – 3 Day Select
- UNAM
- UPS – Next Day Air Early AM
- UNDA
- UPS – Next Day Air
- UPLN
- UPS – Ground – PLN Acct No 444893
- UPSG
- UPS – Ground
- USAM
- UPS – Saturday AM Delivery
- USLC
- UPS – Ground Acct No 840120
- WILL
- Will Call
- WOGO
- With Other Goods
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Example: N9POE0306631
Code qualifying the Reference Identification
- PO
- Purchase Order Number
Message Text
To provide a free-form format that allows the transmission of text information
Example: MSG*DELIVERY APPOINTMENT REQUIRED
Name
To identify a party by type of organization, name, and code
Examples:
N1BY**92BALKCENT
N1BY**92ARC
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
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.
- ARC
- Indianapolis, IN West Jordan, UT ARC Nashville, TN
- BALKCENT
- Plainfield, IN West Jordan, UT Nashville, TN
- DIRECT
- Direct
If BEG02 = ‘DS’.
- TWA
- Lithia Springs, GA
- TWP
- Payson, UT
Name
To identify a party by type of organization, name, and code
Examples:
When BEG02-PO type = ‘SA’.
N1STBALKAMP PLAINFIELD92BALKCENT
When BEG02-PO type = ‘DS’.
N1STBRUNNER AUTO SUPPLY 565920000158197
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.
Identifier for Distribution Center
“BALKCENT” Plainfield, IN
“BALKWEST” West Jordan, UT
“NSH” Nashville, TN
“VISIONSLC“ Packager – Salt Lake City
“ARC” Indianapolis, IN
“ARW” West Jordan, UT
“ARN” ARC Nashville, TN
If BEG02 = ‘DS’ then N104 will contain the drop ship customer’s identifier. These account numbers will change must read the address sent.
Address Information
To specify the location of the named party
Example: N3*1601 WHITAKER ROAD
Geographic Location
To specify the geographic place of the named party
Example: N4PLAINFIELDIN*46168
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.
Name
To identify a party by type of organization, name, and code
Example: N1VN**92123456789
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.
Receiving vendor id code.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
Example: PO11012EA123.45*BP123-4567VC9999999POBK123456
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/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)
- VC
- Vendor's (Seller's) Catalog Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO
- Purchase Order Number
Product/Item Description
To describe a product or process in coded or free-form format
Example: PIDFBLUE WIDGET
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: CTT34
Total number of line items in the transaction set
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
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
ORDER SHIPPING TO ONE OF OUR ARC WAREHOUSES
GS*PO*SENDERGS*RECEIVERGS*20240509*161203*000000001*X*004010~
ST*850*4330001~
BEG*00*SA*E0550554**20150518~
DTM*010*20150522~
N9*PO*E0550554~
N1*BY**92*ARC~
N1*VN**92*005138771~
N1*ST*ARC WAREHOUSE EASTERN*92*ARC~
N3*7754 WEST MORRIS STREET~
N4*INDIANAPOLIS*IN*46231~
PO1*1*8640*EA*2.983**BP*T79*VC*T79~
PID*F****ZIP WAX LIQUID 64 OZ~
CTT*1*8640~
SE*13*4330001~
GE*1*000000001~
IEA*1*000000001~
ORDER SHIPPING TO ONE OF OUR USAG WAREHOUSES
GS*PO*SENDERGS*RECEIVERGS*20240509*161102*000000001*X*004010~
ST*850*750001~
BEG*00*SA*E0306631**20090219~
DTM*010*20090301~
TD5**ZZ*BEST~
N9*PO*E0306631~
MSG*DELIVERY APPOINTMENT REQUIRED~
N1*BY**92*BALKCENT~
N1*VN**92*055555251~
N1*ST*BALKAMP,INC*92*PLN~
N3*1601 WHITAKER ROAD~
N4*PLAINFIELD*IN*46168~
PO1*000000001*216*EA*10.24**BP*501-1050*VC*85031~
PO1*000000002*24*EA*18.56**BP*701-1246*VC*20017~
PO1*000000003*100*EA*1.33**BP*701-1500*VC*22636~
PO1*000000004*150*EA*7.74**BP*701-1575*VC*76575~
CTT*6*590~
SE*17*750001~
GE*1*000000001~
IEA*1*000000001~
ORDER THAT IS SHIPPING DIRECTLY TO ONE OF BALKAMP’S CUSTOMERS
GS*PO*SENDERGS*RECEIVERGS*20240509*161138*000000001*X*004010~
ST*850*28060002~
BEG*00*DS*01036614**20151111~
DTM*010*20151111~
TD5**ZZ*UPLN~
N9*PO*01036614~
N1*BY**92*BALKCENT~
N1*VN**92*622495034~
N1*ST*BURKLEY AUTO PARTS 121*92*0000080016~
N3*311 W PERRY ST~
N4*PAULDING*OH*45879~
PO1*1*1*EA*119.3**BP*DZM371539*VC*371539*PO*BOB111115~
PID*F****BLK NB OVAL CHEVY CREWCAB P U~
CTT*1*1~
SE*14*28060002~
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.