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
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
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
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
- 01
- Cancellation
- 05
- Replace
Code specifying the type of Purchase Order
- BK
- Blanket Order (Quantity Firm)
- RL
- Release or Delivery Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DP
- Department Number
This code may be used in the header area or the detail area, but not both.
- IA
- Internal Vendor Number
Identification number assigned to the vendor, by the retailer, for use within the retailer's system
- PG
- Product Group
Product group or selling zone
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Sales Requirements
To specify general conditions or requirements of the sale
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.
- OHPR
- Special Event Purchase Order
- OHRO
- Replenishment (AIR/BARS) Purchase Order
- OHZQ
- Ecomm Indicator
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.
- ECOM
- When SAC04 is OHZQ
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.
- 01
- Basic
- 02
- End of Month (EOM)
- 05
- Discount Not Applicable
- 08
- Basic Discount Offered
- 12
- 10 Days After End of Month (10 EOM)
- 14
- Previously agreed upon
Code identifying the beginning of the terms period
- 3
- Invoice Date
- 4
- Specified Date
- 7
- Effective Date
The date is specified in the DTM segment in the header area using code 007 in DTM01.
- 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
Date payment is due if discount is to be earned expressed in format CCYYMMDD where CC represents the first two digits of the calendar year
Number of days in the terms discount period by which payment is due if terms discount is earned
Date when total invoice amount becomes due expressed in format CCYYMMDD where CC represents the first two digits of the calendar year
Date/Time Reference
To specify pertinent dates and times
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
- L1
- Letters or Notes
Text
To specify textual data
This segment will contain any text clauses for the agreement referenced in the previous N9 segment.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
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
- AS
- Assortment
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
- 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.
- EN
- EAN/UCC - 13
- UP
- UCC - 12
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
Pricing Information
To specify pricing information
Code identifying pricing specification
- RTL
- Retail
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Destination Quantity
To specify destination and quantity detail
This segment is used to distribute the line item quantity to various locations. SDQ02 serves the same purpose as N103, and all occurrences of Data Element 67, in this segment, function as N104. The SDQ segment functions as an N1 segment containing code BY in N101, that is, the SDQ segment specifies various buying locations. The N1 segment, in the basic order, specifies only one location. The sum of all quantities in the SDQ segment(s), for a line item, must equal the quantity ordered in PO102.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- AS
- Assortment
- 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.
If the SDQ03 equals 0850 please note this is a bulk placeholder code. It is not a store and is not to be shipped on.
Code which identifies a specific location
- SDQ23 identifies the area within the location identified in SDQ03, SDQ05, SDQ07, SDQ09, SDQ11, SDQ13, SDQ15, SDQ17, SDQ19, and SDQ21.
- SDQ23 may be used to identify areas within a store, e.g., front room, back room, selling outpost, end aisle display, etc. The value is agreed to by trading partners or industry conventions.
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.
- I
- Included
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.
- EN
- EAN/UCC - 13
- UP
- UCC - 12
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)
- BO
- Buyers Color
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
Pricing Information
To specify pricing information
Code identifying pricing specification
- RTL
- Retail
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
Belk850PurchaseOrder Sample
GS*PO*612383000T*147844419*20230630*1550*4*X*004030VICS
ST*850*0002
BEG*00*RL*9999106**20230523
REF*DP*0289
REF*IA*2902625
REF*PG*SHOES
PER*BD*BRITTANY MOELLER
CSH*N
ITD*05*3***0**30
DTM*010*20230530
DTM*038*20230613
N9*L1*Legal Disclaimer
MTX*ORI*VENDOR ACKNOWLEDGES THAT ANY PURCHASE MADE UNDER THIS PURCHASE ORDER IS SUBJECT TO THE STANDARD TERMS AND CONDITIONS OF BELKS PURCHASE ORDERS, AND VENDOR ACKNOWLEDGES THE EXISTENCE OF SUCH TERMS AND CONDITIONS IN, INCLUDING FUTURE VERSIONS, ARE AVAILABLE ON BELK.COM/ABOUT BELK/VENDOR RESOURCES.
MTX*ORI*https://www.belk.com/customer-service/about-us/vendor-resources/
PO1*1*7*EA*81.76*WE*UP*887740803708*VA*MEGAPLUSH
CTP*RS*RTL*110
SDQ*EA*92*0001*1*0006*2*0008*1*0266*2*0320*1
PO1*2*7*EA*81.76*WE*UP*887740803685*VA*MEGAPLUSH
CTP*RS*RTL*110
SDQ*EA*92*0001*1*0006*2*0008*1*0266*2*0320*1
PO1*3*7*EA*81.76*WE*UP*885833659195*VA*ENVY
CTP*RS*RTL*110
SDQ*EA*92*0001*1*0006*2*0008*1*0266*2*0320*1
CTT*3
SE*24*0002
GE*1*4
IEA*1*000000004
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.