X12 850 Purchase Order (version 3020)
This standard provides the format and establishes the data contents of a purchase order transaction set. The purchase order transaction set provides 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
- None included
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 Transaction (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 (HHMMSS) (Time range: 000000 through 235959)
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. Positions 1-3, version number, positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).
- 003020
- Draft Standards Approved By ASC X12 Through June 1991.
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) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).
- 850
- X12.1 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.
- 00
- Original
Code specifying the type of Purchase Order.
- DS
- Dropship
- NE
- New 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.
Will send as '0' (EDI PO's won't have releases).
- 0
- 0
Date assigned by the purchaser to Purchase Order.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Will send 3 occurrences of this segment
One for Buyer contact and Phone#;
One for Accounts Payable Fax number;
One for Purchasing Dept Fax number.
Code identifying the major duty or responsibility of the person or group named.
- AP
- Accounts Payable Department
- BD
- Buyer Name or Department
Free-form name.
- Our Buyer name
- 'Accounts Payable'
- 'Purchasing Dept.'
Code identifying the type of communication number.
- FX
- Facsimile
- TE
- Telephone
Date/Time Reference
To specify pertinent dates and times
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description.
- If PID01 = "F", then PID05 is used. If PID01 = "S", then PID04 is used. If PID01 = "X", then both PID04 and PID05 are used.
- F
- Free-form
Code specifying the product or process characteristic being described.
Code identifying the agency assigning the code values.
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic.
- PID04 should be used for industry-specific product description codes.
A free-form description to clarify the related data elements and their content.
Purchase order Header Notes will be supplied using this segment. General notes below:
ANY PRICING ERRORS
WHAT'S ON BACKORDER WITH SHIP DATE
PART NUMBERS THAT ARE DISCONTINUED
PART NUMBERS THAT ARE SUBSTITUTED
Dropship Notes will be supplied using this segment:
The account number will reflect who you are to ship to, FedEx or UPS.
DROP SHIP PURCHASE ORDER
BILL OUR UPS ACCOUNT X927W7
CREATE ASN WITH TRACKING # ON B2B SITE
OR VIA EDI WITH TRACKING # IN REF*BM
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity or a physical location.
- BT
- Party to be Billed For Other Than Freight(Bill To)
Code designating the system/method of code structure used for Identification Code (67).
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party.
- 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.
This field will contain the account number that identifies us as Atech Motorsports to your company when the Entity Identifier Code is BT and the Identification Code Qualifier is 91.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
The addresses for the Drop Ships are not the easiest to code from the SRE system. We do have standards as to how the customer’s address is to be entered, but it dependent on data entry people. This allows for human inconsistencies. The EDI is coded to have the street address in the last N3 Segment. Any other shipping information will be in the first N3 segment. This generally holds true except when the address is not entered according to the addressing rules.
Examples:
N1STSTEVEN DINIERI9299
N2STSTEVEN DINIERI
N3AUTO PRECISION
N37221 NIAGARA FALLS BLVD
N4NIAGARA FALLSNY*143041715
N1STMICAHEL DOERFLER9299
N2STMICAHEL DOERFLER
N3MIKES WELDING REPAIRSROUTE 67 GRANDMAMOSES RD
N3REAR OF LJ FULLFILLMENT SERVIC
N4EAGLEBRIDGENY12057
PERDCCUSTOMER PHONETE5186869553
N1STHARRY BARABASH9299
N2STHARRY BARABASH
N352 ALTHOUSE AVE
N4EAST ROCKAWAYNY11518
PERDCCUSTOMER PHONETE5164041371
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 USA or Canada.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named.
- DC
- Delivery Contact
Dropship
- RD
- Receiving Dock
Free-form name.
- 'Receiving Dept.'
- Customer Name
Code identifying the type of communication number.
- TE
- Telephone
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier, sequence of routing and to provide transit time information
This segment will only be used for Drop Ships; it will be suppressed for anything else.
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; use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- ZZ
- Mutually Defined
Code identifying a party.
A vendor will only ship exclusively UPS (codes starting with U) or FedEx (codes starting with F) for drop ships. Summit will not send both.
Only FedEx vendors will receive FedEx Codes.
Shipping Request: On FedEx orders, could our PO number be placed in the FedEx Shipment ID?
- F-2ND DAY
- FedEx 2nd Day Air,, no special coding or priority
- F-GROUND
- FedEx Ground, no special coding or priority
- F-NEXT DAY
- Standard Overnight (No Priority please)
- F-TRUCK
- Truck
- U-2ND DAY
- Second Day Air by the end of the 2nd Business day
- U-GROUND
- Ground
- U-NEXT DAY
- Next Day Air by 10:30
- U-TRUCK
- Whatever LTL you use
- U-UPS - SAT. DEL.
- Saturday Delivery, standard
- U-UPS- 3DAY DELIV.
- Third Day Air by the end of the 3rd Business day
- U-UPS-GRND CANADA
- Ground Canada
Code specifying the method or type of transportation for the shipment.
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity or a physical location.
- SE
- Selling Party
Code designating the system/method of code structure used for Identification Code (67).
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party.
- 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.
This field will contain the account number that Atech Motorsports uses to identify your company when the Entity Identifier Code is SE and the Identification Code Qualifier is 92. This field is to be sent back on the 856 N1SF04.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
The addresses for the Drop Ships are not the easiest to code from the SRE system. We do have standards as to how the customer’s address is to be entered, but it dependent on data entry people. This allows for human inconsistencies. The EDI is coded to have the street address in the last N3 Segment. Any other shipping information will be in the first N3 segment. This generally holds true except when the address is not entered according to the addressing rules.
Examples:
N1STSTEVEN DINIERI9299
N2STSTEVEN DINIERI
N3AUTO PRECISION
N37221 NIAGARA FALLS BLVD
N4NIAGARA FALLSNY*143041715
N1STMICAHEL DOERFLER9299
N2STMICAHEL DOERFLER
N3MIKES WELDING REPAIRSROUTE 67 GRANDMAMOSES RD
N3REAR OF LJ FULLFILLMENT SERVIC
N4EAGLEBRIDGENY12057
PERDCCUSTOMER PHONETE5186869553
N1STHARRY BARABASH9299
N2STHARRY BARABASH
N352 ALTHOUSE AVE
N4EAST ROCKAWAYNY11518
PERDCCUSTOMER PHONETE5164041371
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 USA or Canada.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named.
- DC
- Delivery Contact
Dropship
- RD
- Receiving Dock
Free-form name.
- 'Receiving Dept.'
- Customer Name
Code identifying the type of communication number.
- TE
- Telephone
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier, sequence of routing and to provide transit time information
This segment will only be used for Drop Ships; it will be suppressed for anything else.
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; use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- ZZ
- Mutually Defined
Code identifying a party.
A vendor will only ship exclusively UPS (codes starting with U) or FedEx (codes starting with F) for drop ships. Summit will not send both.
Only FedEx vendors will receive FedEx Codes.
Shipping Request: On FedEx orders, could our PO number be placed in the FedEx Shipment ID?
- F-2ND DAY
- FedEx 2nd Day Air,, no special coding or priority
- F-GROUND
- FedEx Ground, no special coding or priority
- F-NEXT DAY
- Standard Overnight (No Priority please)
- F-TRUCK
- Truck
- U-2ND DAY
- Second Day Air by the end of the 2nd Business day
- U-GROUND
- Ground
- U-NEXT DAY
- Next Day Air by 10:30
- U-TRUCK
- Whatever LTL you use
- U-UPS - SAT. DEL.
- Saturday Delivery, standard
- U-UPS- 3DAY DELIV.
- Third Day Air by the end of the 3rd Business day
- U-UPS-GRND CANADA
- Ground Canada
Code specifying the method or type of transportation for the shipment.
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity or a physical location.
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67).
- 91
- Assigned by Seller or Seller's Agent
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party.
- 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.
This field will contain the Atech Motorsports warehouse number you are to ship to when the Entity Identifier Code is ST and the Identification Code Qualifier is 92.
(01 will be populated for the drop ships unless requested)
01 = 1200 Southeast Ave Tallmadge, OH 44278
02 = 960 E. Glendale Ave. Sparks, NV 89431
03 = 20 king Mill Rd McDonough, GA 30253
04 = 2200 E. Interstate 20 Arlington, TX 76018
99 = Drop Ship Customer Address located in N2, N3, and N4
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
The addresses for the Drop Ships are not the easiest to code from the SRE system. We do have standards as to how the customer’s address is to be entered, but it dependent on data entry people. This allows for human inconsistencies. The EDI is coded to have the street address in the last N3 Segment. Any other shipping information will be in the first N3 segment. This generally holds true except when the address is not entered according to the addressing rules.
Examples:
N1STSTEVEN DINIERI9299
N2STSTEVEN DINIERI
N3AUTO PRECISION
N37221 NIAGARA FALLS BLVD
N4NIAGARA FALLSNY*143041715
N1STMICAHEL DOERFLER9299
N2STMICAHEL DOERFLER
N3MIKES WELDING REPAIRSROUTE 67 GRANDMAMOSES RD
N3REAR OF LJ FULLFILLMENT SERVIC
N4EAGLEBRIDGENY12057
PERDCCUSTOMER PHONETE5186869553
N1STHARRY BARABASH9299
N2STHARRY BARABASH
N352 ALTHOUSE AVE
N4EAST ROCKAWAYNY11518
PERDCCUSTOMER PHONETE5164041371
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 USA or Canada.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named.
- DC
- Delivery Contact
Dropship
- RD
- Receiving Dock
Free-form name.
- 'Receiving Dept.'
- Customer Name
Code identifying the type of communication number.
- TE
- Telephone
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier, sequence of routing and to provide transit time information
This segment will only be used for Drop Ships; it will be suppressed for anything else.
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; use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- ZZ
- Mutually Defined
Code identifying a party.
A vendor will only ship exclusively UPS (codes starting with U) or FedEx (codes starting with F) for drop ships. Summit will not send both.
Only FedEx vendors will receive FedEx Codes.
Shipping Request: On FedEx orders, could our PO number be placed in the FedEx Shipment ID?
- F-2ND DAY
- FedEx 2nd Day Air,, no special coding or priority
- F-GROUND
- FedEx Ground, no special coding or priority
- F-NEXT DAY
- Standard Overnight (No Priority please)
- F-TRUCK
- Truck
- U-2ND DAY
- Second Day Air by the end of the 2nd Business day
- U-GROUND
- Ground
- U-NEXT DAY
- Next Day Air by 10:30
- U-TRUCK
- Whatever LTL you use
- U-UPS - SAT. DEL.
- Saturday Delivery, standard
- U-UPS- 3DAY DELIV.
- Third Day Air by the end of the 3rd Business day
- U-UPS-GRND CANADA
- Ground Canada
Code specifying the method or type of transportation for the shipment.
Detail
Purchase Order Baseline Item Data
To specify basic and most frequently used purchase order line item data
Alphanumeric characters assigned for differentiation within a transaction set.
- PO101 is the line item identification
PO Line #
Code identifying the basic unit of measurement.
- EA
- Each
Price per unit of product, service, commodity, etc.
If a discount has been granted this will show the discounted Unit Price and a DIS segment will be sent showing the discount percent.
Code identifying the type of unit price for an item.
- PE
- Price per Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- PO106 through PO125 provide for ten (10) different product/service ID's per each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., 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).
- VP
- Vendor's (Seller's) Part Number
Product/Item Description
To describe a product or process in coded or free-form format
Code indicating the format of a description.
- If PID01 = "F", then PID05 is used. If PID01 = "S", then PID04 is used. If PID01 = "X", then both PID04 and PID05 are used.
- F
- Free-form
Code specifying the product or process characteristic being described.
Code identifying the agency assigning the code values.
- Use PID03 to indicate the organization that publishes the code list being referred to.
A code from an industry code list which provides specific data about a product characteristic.
- PID04 should be used for industry-specific product description codes.
Discount Detail
To specify the exact type and terms of various discount information.
Code to define the units in which the discount will be determined, i.e., dollars, case, truckload, etc.
- PPU
- % Discount per Units Purchased
Code to define unit of discount, i.e., dollars, cases, alternate products, etc.
- PC
- Discount Determined as a Percentage of the Value of the Transaction
A multiplier amount used in conjunction with discount base qualifier to determine the value of the discount.
Code to define the units of the limits for determining discount.
- DOF
- Dollars of Purchase
Date/Time Reference
To specify pertinent dates and times
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.
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).
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.
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.