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
BEG07 refers to an 855 PO Acknowledgment, NOT a 997 Functional Acknowledgment, which is required.
Be advised that the vendor number is no longer a part of the PO number for orders issued from the CTC's AOM order management system. It will still be a part of the PO number for orders issued from our legacy ordering system. The ordering system type will be identified in the new REFPHC segment and the vendor number is issued in the new REFVR segment for all PO's.
Example: BEG00SA*1234567820030214NA
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- DS
- Direct Ship
- RA
- Cross-dock
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Format: XXXXXXXX or 0XXXXXXX
Date expressed as CCYYMMDD
- BEG05 is the date assigned by the purchaser to purchase order.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
This segment will only be sent if the currency is other than Canadian dollars.
Example: CURBYUSD
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Reference Identification Process Handling Code
To specify identifying information
AOM and the Legacy order system are both active.
Example: REFPHCB
Code qualifying the Reference Identification
- PHC
- Process Handling Code
Reference Identification Vendor ID Number
To specify identifying information
Vendor number is a unique number assigned to a CTC Supplier's file based on FOB, payment terms and payment currency.
Example: REFVR9999
Code qualifying the Reference Identification
- VR
- Vendor ID Number
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example: PERICTom Brown AUTE(416) 480-3000
Code identifying the major duty or responsibility of the person or group named
- IC
- Information Contact
Code identifying the type of communication number
- TE
- Telephone
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Example: FOBPP*02FOB*OA
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- CC
- Collect
- PP
- Prepaid (by Seller)
Code identifying the source of the transportation terms
- 02
- Trade Terms Code
Code identifying the trade terms which apply to the shipment transportation responsibility
- FOB
- Free on Board
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Example: ITD3*210**30
Code identifying the beginning of the terms period
- 3
- Invoice Date
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Number of days in the terms discount period by which payment is due if terms discount is earned
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Example: TD5*****SEND RPA 7 DAYS PRIOR TO SHIPPING
Carrier Details (Special Handling, or Hazardous Materials, or Both)
To specify transportation special handling requirements, or hazardous materials information, or both
This segment is used for legacy direct ship. The BEG02 will still equal SA with this segment indicating that it is direct ship. Canadian Tire’s direct ship department will contact you with shipping instructions. It is only for Direct Ship suppliers that are not on the AOM direct ship program.
Example: TD4ZZZ** Job #029-19 Direct Ship Ship Dates Critical
Code specifying special transportation handling instructions
- ZZZ
- Mutually Defined
Name
To identify a party by type of organization, name, and code
Example: N1STCT RETAIL - BRAMPTON D.C.92016136689003
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)
- 9
- Distribution Center
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.
CTC Distribution Centre or EAP Depot number.
N104 may contain the value 2016136689000 which indicates the PO is Direct Ship to Stores.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
PO110 / PO111 - UPC/EAN codes are not always sent. Contact Electronic Commerce Dept for details.
For country of origin we use ISO 3166-1 alpha 2 codes. This will be the country of origin provided to us by the supplier. If the country of origin is the United States a state code will be added. (ISO 3166-2:US). (IE for Florida the code will be US-FL)
Effective 01JAN02, most discounts were removed from off invoice and are processed using Credit/Debit memos. Therefore, in most cases net cost will equal the quote cost in the CTP*UCP. There are still some 'off invoice' allowances and charges, shown in the SAC segment, that will affect the PO105.
For Crossdock and Direct Ship orders, the PO102 will show the total quantity ordered for this sku for all stores listed in the SDQ segment(s).
Example: PO1124EA2.45NTSK099-9999-9VP1234- 4321UP155555777778CH*CA
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
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- NT
- Net
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.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
CTC Product Number.
Format: (NNN-NNNN-N)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VP
- Vendor's (Seller'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)
- EN
- European Article Number (EAN) (2-5-5-1)
- 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)
- CH
- Country of Origin Code
Pricing Information
To specify pricing information
Example: CTP*ALT2012EA
Code identifying pricing specification
- ALT
- Alternate Price
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Pricing Information
To specify pricing information
Example: CTPUCP2.45***QT
Code identifying pricing specification
- UCP
- Unit cost price
Price per unit of product, service, commodity, etc.
- See Figures Appendix for an example detailing the use of CTP03 and CTP04.
- See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
This segment will be suppressed for Direct Ship Orders.
Example: PO4*12EA*CTN90
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
- 05
- Lift
- AS
- Assorted
- BD
- Bundle
- BG
- Bag
- BO
- Bottle
- BR
- Barrel
- BX
- Box
- CA
- Case
- CC
- Cubic Centimeter
- CF
- Cubic Foot
- CG
- Card (Blister)
- CM
- Centimeter
- CN
- Can
- CP
- Crate
- CR
- Cubic Metre
- CT
- Carton
- CX
- Coil
- DS
- Display
- EA
- Each
- FT
- Foot
- GA
- Gallon
- GR
- Gram
- HA
- Hank
- IN
- Inch
- JR
- Jar
- KG
- Kilogram
- KT
- Kit
- LB
- Pound
- LN
- Length
- LO
- Lot
- LT
- Litre
- ML
- Millilitre
- MR
- Metre
- OZ
- Ounce
- PA
- Pail
- PC
- Piece
- PD
- Pad
- PK
- Package
- PL
- Pallet
- PR
- Pair
- PT
- Pint
- PV
- Half Pint
- QU
- Quart
- RL
- Roll
- SF
- Square Foot
- SL
- Sleeve
- SM
- Square Metre
- SO
- Spool
- SQ
- Square
- ST
- Set
- TB
- Tube
- TH
- Thousand
- TY
- Tray
- UN
- Unit
- WR
- Wrapped (Skin)
- YD
- Yard
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
- BAG
- Bag
- BBL
- Barrel
- BDL
- Bundle
- BOX
- Box
- BXI
- Box, with inner container
- CAN
- Can
- CAS
- Case
- COL
- Coil
- CRT
- Crate
- CTN
- Carton
- DRM
- Drum
- JAR
- Jar
- KIT
- Kit
- LIF
- Lifts
- PCK
- Packed - not otherwise specified
- PCS
- Pieces
- PKG
- Package
- PLT
- Pallet
- ROL
- Roll
- SLV
- Sleeve
- SPL
- Spool
- TBE
- Tube
- TRY
- Tray
- UNT
- Unit
- 90
- Standard
Service, Promotion, Allowance, or Charge Information
To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge
As of 01JAN02, per Corporate Policy, most allowances and charges will be handled using a Debit/Credit note. The SAC seg will only be sent if an allowance or charge is still processed by PO.
Example: SACAC000*1253*5****02
Code which indicates an allowance or charge for the service specified
- If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
- A
- Allowance
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- A260
- Advertising Allowance
- B750
- Core Charge
- B770
- Cost recovery/adjustment
- C000
- Defective Allowance
- C310
- Discount
- C540
- Early Buy Allowance
- F810
- Promotional Discount
- F910
- Quantity Discount
- I170
- Trade Discount
- I530
- Volume Discount
- I570
- Warehouse
- I590
- Labor
Monetary amount
- SAC05 is the total amount for the service, promotion, allowance, or charge.
- If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.
Code indicating on what basis allowance or charge percent is calculated
- 3
- Discount/Gross
Tax Reference
To provide data required for proper notification/determination of applicable taxes applying to the transaction or business described in the transaction
Example: TAX*R100773019***********3~
Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number
- TAX01 is required if tax exemption is being claimed.
GST Exemption Number
Destination Quantity
To specify destination and quantity detail
The SDQ segment will only be sent if the BEG02 = "RA" or BEG02 = "DS".
SDQ03 etc. will have the numeral “7” prefix added to the four digit numeric code to designate a new store location.
Complete store listing is available as a separate document.
Example: SDQEA920012100162100036100145157004220042425
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code designating the system/method of code structure used for Identification Code (67)
- SDQ02 is used only if different than previously defined in the transaction set.
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- SDQ03 is the store number.
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Code identifying a party or other code
CTC Store Number
Format: (NNNN or NNNNN)
Date/Time Reference
To specify pertinent dates and times
Example: DTM01020030501
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*6
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
PROCESS HANDLING - LEGACY CANADIAN DOLLARS STORAGE
GS*PO*SENDERGS*RECEIVERGS*20240507*180718*000000001*X*004010~
BEG*00*SA*99991234**20030214**NA~
REF*VR*9999~
REF*PHC*B~
PER*IC*Tom Brown AU*TE*(416) 480-3000~
FOB*PP***02*FOB*OA~
ITD**3*2**10**30~
TD5*****SEND RPA 7 DAYS PRIOR TO SHIPPING~
N1*ST*CT RETAIL - BRAMPTON D.C.*9*2016136689003~
PO1*1*24*EA*2.45*NT*SK*099-9999-6*VP*1234-4321*UP*1555557777758*CH*CA~
CTP**UCP*2.45******QT~
PO4**12*EA*CTN90~
DTM*010*20030501~
CTT*1~
GE*1*000000001~
IEA*1*000000001~
PROCESS HANDLING – AOM CROSS DOCK FOREIGN CURRENCY TWO SKU – MULTIPLE STORES NEW STORE
GS*PO*SENDERGS*RECEIVERGS*20240507*180806*000000001*X*004010~
BEG*00*RA*01234567**20030214**NA~
CUR*BY*USD~
REF*VR*9999~
REF*PHC*A~
PER*IC*BILLES, JOHN AU*TE*(416) 480-3000~
FOB*PP***02*FOB*OA~
ITD**3*2**10**30~
TD5*****SEND RPA 7 DAYS PRIOR TO SHIPPING~
N1*ST*CT RETAIL – CALGARY D.C.*9*2016136689007~
PO1*1*120*EA*2.45*NT*SK*099-9999-6*VP*1234-4321*UP*155555777775*CH*CN~
CTP**UCP*2.45******QT~
PO4**12*EA*CTN90~
SDQ*EA*92*70042*12*0001*12*0036*24*0145*12*01642*24*0424*36~
DTM*010*20030501~
PO1*2*222*EA*1.14*NT*SK*099-9998-8*VP*1234-4320*UP*155555666666*CH*VN~
CTP**UCP*1.14******QT~
PO4**6*EA*CTN90~
SDQ*EA*92*70042*18*0001*12*0005*12*0145*18*0164*24*0424*12*0425*18*0426*6*0427*6*0628*18~
SDQ*EA*92*0646*12*0649*18*0701*12*0705*6*0757*6*1317*24~
DTM*010*20030501~
CTT*2~
GE*1*000000001~
IEA*1*000000001~
PROCESS HANDLING – AOM DIRECT SHIP TWO SKU – MULTIPLE STORES NEW STORE
GS*PO*SENDERGS*RECEIVERGS*20240507*181124*000000001*X*004010~
BEG*00*DS*01234567**20030214**NA~
CUR*BY*USD~
REF*VR*9999~
REF*PHC*A~
PER*IC*Tom Brown AU*TE*(416) 480-3000~
FOB*PP***02*FOB*OA~
ITD**3*2**10**30~
N1*ST*CT RETAIL - DIRECT SHIP*9*2016136689000~
PO1*1*120*EA*2.45*NT*SK*099-9999-6*VP*1234-4321*UP*155555777775*CH*CA~
CTP**UCP*2.45******QT~
SDQ*EA*92*70042*12*0005*12*0036*24*0145*12*0326*24*0424*36~
DTM*010*20030501~
PO1*2*222*EA*1.14*NT*SK*099-9998-8*VP*1234-4320*UP*155555666662*CH*US-NY~
CTP**UCP*1.14******QT~
SDQ*EA*92*70042*18*0001*12*0005*12*0036*18*0145*24*0150*12*0152*18*0162*6*0326*6*0328*18~
SDQ*EA*92*0424*12*0425*18*0654*12*0701*6*0702*6*0705*24~
DTM*010*20030501~
CTT*2~
GE*1*000000001~
IEA*1*000000001~
PROCESS HANDLING – LEGACY CANADIAN DOLLARS EAP DEPOT CASTING CHARGE of $4.00
GS*PO*SENDERGS*RECEIVERGS*20240507*180959*000000001*X*004010~
BEG*00*SA*99991234**20030214**NA~
REF*VR*9999~
REF*PHC*B~
PER*IC* Tom Brown AU*TE*(403)481-7337~
FOB*PP***02*FOB*OA~
ITD**3*2**10**30~
TD5*****SEND RPA 7 DAYS PRIOR TO SHIPPING~
N1*ST*CT RETAIL - MONTREAL DEPOT*9*2016136689052~
PO1*1*24*EA*6.45*NT*SK*099-9999-6*VP*1234-4321*UP*155555777775*CH*CA~
CTP**UCP*2.45******QT~
PO4**12*EA*CTN90~
SAC*C*B750****3*400*****02~
DTM*010*20030501~
CTT*1~
GE*1*000000001~
IEA*1*000000001~
Sample 1
GS*PO*SENDERGS*RECEIVERGS*20240507*180648*000000001*X*004010~
BEG*00*SA*12345678**20030214**NA~
CUR*BY*USD~
REF*VR*9999~
REF*PHC*B~
PER*IC*Tom Brown AU*TE*(416) 480-3000~
FOB*PP***02*FOB*OA~
ITD**3*2**10**30~
TD5*****SEND RPA 7 DAYS PRIOR TO SHIPPING~
TD4*ZZZ*** Job #029-19 Direct Ship Ship Dates Critical~
N1*ST*CT RETAIL - BRAMPTON D.C.*9*2016136689003~
PO1*1*24*EA*2.45*NT*SK*099-9999-9*VP*1234-4321*UP*155555777778*CH*CA~
CTP**ALT*20*12*EA~
CTP**UCP*2.45******QT~
PO4**12*EA*CTN90~
SAC*A*C000***125*3*5*****02~
TAX*R100773019***********3~
SDQ*EA*92*0012*10*0162*10*0036*10*0145*15*70042*20*0424*25~
DTM*010*20030501~
CTT*6~
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.