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
- None included
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
Example: BEG00SA*PONUM-001**20191224
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of Purchase Order
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Customer Order Number
To specify identifying information
Example: REFCO202001650090501
Code qualifying the Reference Identification
- CO
- Customer Order Number
Internal Vendor Number
To specify identifying information
Example: REFIAVENDORNUM
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Example: PERODOrderingDepartmentTE1-800-123-4567
Code identifying the major duty or responsibility of the person or group named
- OD
- Order Department
Code identifying the type of communication number
- TE
- Telephone
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
Examples:
SACNF050**Thank you for shopping at ONLINE!
SACS*H151***From mom and dad!
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 service, promotion, allowance, or charge
- F050
- Other (See related description)
Packslip Message
- H151
- Special Services
Gift Message
Paperwork
To identify the type or transmission or both of paperwork or supporting information
Up to 4 PWK segments may be sent.
Example: PWKR5**URcustomer-service*WWW.BRYLANEHOME.COM
Code indicating the title or contents of a document, report or supporting item
- R5
- Technical Information
Code designating the system/method of code structure used for Identification Code (67)
- PWK05 and PWK06 may be used to identify the addressee by a code number.
- UR
- Uniform Resource Locator (URL)
Code identifying a party or other code
Code identifying URL type.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
The TD505 is the Ship Code. It tells you the preferred carrier and service level. Please contact your Partner Setup specialist for the complete list of codes that are in play for this relationship.
If any of the codes sent begin with UNSP they mean Unspecified. You are
allowed to select whatever carrier you prefer (FedEx, UPS, etc.), but you must provide the shipment level requested (Ground, Next Day, etc.) and report the exact code used back in the 856.
Ship method codes can be found in the Logicbroker portal under Account->Shipment Options
Example: TD5*****UPSN_CG
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
Example: N9SD05
Code qualifying the Reference Identification
Code qualifying the Sales Division.
- SD
- Subday Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The FullBeauty Sales Division
- 00
- WOMAN WITHIN
- 05
- ROAMANS
- 11
- KING SIZE DIRECT
- 14
- BARGAIN OUTLET
- 15
- BRYLANE HOME
- 23
- JESSICA LONDON
- 77
- ONE STOP PLUS
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
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 U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
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 U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
If you notice problems with the SKUs sent to you by your merchant, please call your representative there immediately. LogicBroker does not maintain vendor SKU lists. SKUs contained in your Purchase Order come from what is setup with the merchant. We cannot alter the SKUs that are sent to us in the original PO.
Example: PO1011EA205TESKMS-123VNVN-123*****PI12345
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Merchant line number. Required to be returned in the shipment confirmation.
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
- TE
- Contract 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.
Indicates that the FullBeauty SKU for the product is contained in the PO107 data element.
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
FullBeauty product SKU
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Indicates that the Vendor SKU for the product is contained in the PO109 data element.
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Vendor's product SKU
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Indicates that the merchant item number is contained in the PO117 data element.
- PI
- Purchaser's Item Code
Pricing Information
To specify pricing information
Example: CTPRSRES*379.99
Code identifying pricing specification
- RES
- Resale
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.
The unit price to the customer.
Product/Item Description
To describe a product or process in coded or free-form format
This item level PID is used to convey specific item information that is generally only needed on a packing slip at the item level. If you are using the packing slips generated by Logicbroker you can generally disregard these unless you have a special need for them. If you are creating your own packing slips please refer to the Packing Slip Guide in the Resource Center for more specific notes on their use.
Examples:
PIDF08*ARMOIRE
PIDF*35**CHE
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
Code identifying the general class of a product or process characteristic
- 08
- Product
- 35
- Color
- SIZ
- Sizing
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.
- C
- Charge
Code identifying the service, promotion, allowance, or charge
- G821
- Shipping
- H850
- Tax
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
This TD5 should mirror the one sent at the header level. It is sent so that you have flexibility in where you pick it up from and the same rules apply as the header level version.
Example: TD5*****UNSP_CG
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
The TD505 is the Ship Code. It tells you the preferred carrier and service level. Please contact your Partner Setup specialist for the complete list of codes that are in play for this relationship.
If any of the codes sent begin with UNSP they mean Unspecified. You are allowed to select whatever carrier you prefer (FedEx, UPS, etc), but you must provide the shipment level requested (Ground, Next Day, etc) and report the exact code used back in the 856.
Shipmethod codes can be found in the Logicbroker portal under
Account->Shipment Options
Example: TD5*****UPSN_CG
Message Text
To provide a free-form format that allows the transmission of text information
Up to 4 MSG segments can be passed.
Example: MSG*Sample MSG
Free-form message text
This may contain personalization information. Personalization data is presented as 'name = value' where name is the type of personalization
data being provided and value is the actual personalized data. The equal sign is not part of the personalized data. In cases where a merchant does not provide a name for the type of personalization, the data string will begin with the equal sign followed by the uncategorized personalized data.
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*1
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
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.