X12 850 Retail 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
- ^ Repetition
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code identifying 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 identifying 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)
Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified
- 08
- UCC EDI Communications ID (Comm ID)
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
Code indicating 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
Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator
- ^
- Repetition Separator
Code specifying the version number of the interchange control segments
- 00403
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
A control number assigned by the interchange sender
Code indicating sender's request for an interchange acknowledgment
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code indicating 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
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480
- 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
- 004030
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999
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 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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
- 06
- Confirmation
- 07
- Duplicate
Code specifying the type of Purchase Order
- BK
- Blanket Order (Bulk and Release)
- RE
- Reorder (Basics System generated)
- RL
- Release
- SA
- Stand Alone (Item/Fashion)
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
For Release Orders Only
- 1
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
- BEG05 is the date assigned by the purchaser to purchase order.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- BT
- Batch Number
Unique 10-character Batch Number
for Macy’s Internal Use - CO
- Customer Order Number
Retailer’s PO Number if Vendor’s
PO Number is Given in BEG03
(Ex. REFCO6327321) - DP
- Department Number
Department Number (Ex. 0873).
- PG
- Product Group
Fob Description (Ex: Housewares)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Unique 10-character Batch Number
for Macy’s Internal Use
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.
- DF
- Defined by Buyer and Seller
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
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.
- N
- No Allowance or Charge
Code identifying the agency assigning the code values
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
Agency maintained code identifying the service, promotion, allowance, or charge
- SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with SAC03 to further define SAC02.
- HA
- Hanger Service
- OHRO
- Order Handling Rush Order
- TC09
- As agreed by Trading Partners
- TC10
- Do Not Price
A free-form description to clarify the related data elements and their content
Text of Hanger Service: Hanger Service Required; Must Ship on Hangers
Text of Ticketing Instructions: Tickets Must be Marked with Retail
Prices OR Do Not Mark Retail Prices on Tickets
Terms of Sale/Deferred Terms of Sale
To specify terms of sale
Code identifying type of payment terms
- If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
- 02
- End of Month (EOM)
- 05
- Discount Not Applicable
Code identifying the beginning of the terms period
- 2
- Delivery Date
- 3
- Invoice Date
- 8
- Invoice Transmission Date
- 15
- Receipt of Goods
Terms discount percentage, expressed as a percent, available to the purchaser if an invoice is paid on or before the Terms Discount Due Date
Discount Percent (Expressed in %.Use decimal point only when needed, for example, 10.5% is 10.5 and 2% is 2.)
Number of days in the terms discount period by which payment is due if terms discount is earned
If Discount Available—Days Due
Number of days until total invoice amount is due (discount not applicable)
If Net Terms—Days Due
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
010 – Requested Ship Date (Do Not Ship Before) As of 10/31/10ONLY
for orders shipped prior to 2/27/11- will become obsolete
064 – Do not deliver Before (Macy’s In DC Date) As of 10/31/10
ONLY for orders placed for a 2/27/11 or later DC arrival
- 001
- Cancel After (Do Not Ship After)
- 010
- Requested Ship Date (Do Not Ship Before)
As of 10/31/10ONLY for orders shipped prior to
2/27/11- will become obsolete - 015
- Promotion Start
- 064
- Do not deliver Before (Macy’s In DC Date)
As of 10/31/10 ONLY for orders placed for a
2/27/11 or later DC arrival
Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- LMI
- Local Media Identifier
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
To transmit large volumes of message text
Test Message
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
PO108 and PO109 are optional fields transmitted for vendor preticketing.
If the order is a pre-ticket order elements will contain class qualifier and class number
If the order is a Macy’s by Mail order elements will contain Buyer’s Catalog Number qualifier and the MBM catalog number.
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
- CA
- Case
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- NC
- No Charge
- WE
- Wholesale Price per Each
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.
IN Buyer’s Item Number
- EN
- EAN Number (13 Digits)
- IN
- Buyer's Item Number
- UN
- UK Number (14 Digits)
- UP
- UPC Number (12 Digits)
Identifying number for a product or service
UPC Number (12 Digits)
EAN Number (13 Digits)
UK Number (14 Digits)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
'CG’ sent only for pre-ticket orders
‘CB’ sent only for Macy’s by Mail PO’s
- CB
- Buyer's Catalog Number
- CG
- Commodity Grouping
Identifying number for a product or service
If CG is sent in PO108, this will be the Class Number for pre-ticket
orders only
If CB is sent in the PO10, this will be the Buyer’s Catalog Number - for
Macy’s by Mail orders only.
Indicates the MBM catalog number.
Note: CTP02 and CTP03 are optional fields transmitted for vendor preticketing.
Ticketing Information:
Dept/Class/Retail 999-99 $99,999.99
Department from REF segment (REF02)
Class from PO1 segment (PO109)
Retail price from CTP segment (CTP03 should be printed in black ink
on a white label and affixed to zone 6 of the vendor UPC ticket)
Pricing Information
To specify pricing information
Code identifying pricing specification
- RTL
- Retail
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.
Product/Item Description
To describe a product or process in coded or free-form format
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
- X
- Semi-structured (Code and Text)
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
- VI
- Voluntary Inter-Industry Commerce Standard (VICS) EDI
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.
- FN01SSC
- SIZE
- FN02BOK
- PID
- FN02FTB
- COVER
- FN02LOT
- FLOOR-ID
- FN02TMC
- TAG FOR
- FN02TMS
- FINISH
- FN02TPC
- COLOR
A free-form description to clarify the related data elements and their content
Will send a maximum of 10 characters
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
The number of inner containers, or number of eaches if there are no inner containers, per outer container
Numeric value of gross volume per pack
Quantity per Inner Carton
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Unit of Measure
The number of eaches per inner container
Pack Ratio
Destination Quantity
To specify destination and quantity detail
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
- 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.
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Code identifying a party or other code
Store Number
Numeric value of quantity
Quantity for Above Store
Subline Item Detail
To specify product subline detail item data
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- D
- Delete
- I
- Included
- S
- Substituted
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/source of the descriptive number used in Product/Service ID (234)
- SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- IN
- Buyer's Item Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VA
- Vendor's Style Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SZ
- Vendor Alphanumeric Size Code
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- UCC - 12
Identifying number for a product or service
Pricing Information
To specify pricing information
Code identifying pricing specification
- RTL
- Retail
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.
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
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.