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
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 specifying the type of Purchase Order
- RE
- Reorder
- SA
- Stand-alone Order
Identifying number for Purchase Order assigned by the orderer/purchaser
Will always be in this format - 246405116_212
JCPenney may send duplicate purchase order numbers.
Date expressed as CCYYMMDD
- BEG05 is the date assigned by the purchaser to purchase order.
Reference Identification
To specify identifying information
EXAMPLES: REFIAV12345 REFDP987
REFCO93993832 REF7U657889
REFMRD2S - Direct to store
Code qualifying the Reference Identification
- 7U
- Related Transaction Reference Number
ERP Customer Order Number
- CO
- Customer Order Number
This qualifier indicates that the REF02 contains the customer order number.
- DP
- Department Number
- Merchant's department/site id
- IA
- Internal Vendor Number
This qualifier indicates that the REF02 contains the JCPenney vendor ID for the party receiving this purchase order.
- MR
- Merchandise Type Code
This qualifier indicates that the REF02 contains: D2S - Direct to store
D2C - Direct to customer - X9
- Internal Control Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
The REF02 CO qualified element is required to be included in the packing slip if you are creating your own.
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
*Will only be present if the partner is configured to receive full date/time/offset values. The Purchase Order date will always be sent in the BEG05.
- 004
- Purchase Order
Date expressed as CCYYMMDD
Depending on the qualifier used this element contains the corresponding value.
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)
Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow
See HubEDI User Guide.pdf for interpretation of time codes.
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Vendor's code for intended shipping / routing. Use same code list as in vendor acknowledgments and confirmations.
Restrictions/Conditions
To specify restrictions/conditions (such as shipping, ordering)
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- 45
- Drop-off Location
LTL Delivery transmission location.
- PO
- Party to Receive Invoice for Goods or Services
- SF
- Ship From
If drop-ship, this will contain the address for returns
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
This element contains the JCP store number in the ship to loop.
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 first instance of the N3 will contain the first two lines of mailing address. If there is a third line, a 2nd instance of the N3 will be used.
EXAMPLE: N321 CORPORATE DR SUITE 205Attn. John Doe Example: Ship to Store
N3JCPENNEY COLLIN CREEK MALLATTN JOSH M HAMILTON ORDERID 1236 SCAN LABEL
Note: ORDERID will always start in position 31
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
Code identifying an organizational entity, a physical location, property or an individual
- SO
- Sold To If Different From Bill To
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 93
- Code assigned by the organization originating the transaction set
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.
This element contains the JCP store number in the ship to loop.
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 first instance of the N3 will contain the first two lines of mailing address. If there is a third line, a 2nd instance of the N3 will be used.
EXAMPLE: N321 CORPORATE DR SUITE 205Attn. John Doe Example: Ship to Store
N3JCPENNEY COLLIN CREEK MALLATTN JOSH M HAMILTON ORDERID 1236 SCAN LABEL
Note: ORDERID will always start in position 31
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)
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
Used for primary instance of PER segment in N1 loop
- BD
- Buyer Name or Department
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable
Transfer Location Phone Number
Code identifying the type of communication number
- EM
- Electronic Mail
This qualifier indicates that the PER08 contains the email address for the associated party.
Complete communications number including country or area code when applicable
This element contains the email address for the associated party
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.
- Merchant's PO line number.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Price per unit of product, service, commodity, etc.
- Unit cost the merchant expects to be billed for each unit fulfilled.
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)
This code is used to qualify the merchant's SKU code
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
Vendor's sku
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
UPC code
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
Code identifying the general class of a product or process characteristic
- 08
- Product
- 35
- Color
- 91
- Buyer's Item Size Description
Code identifying the agency assigning the code values
- Use PID03 to indicate the organization that publishes the code list being referred to.
- AB
- Assigned by Buyer
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
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
- For packslip messages
Code identifying the service, promotion, allowance, or charge
- F050
- Other (See related description)
A free-form description to clarify the related data elements and their content
- If SAC-02 = F050 then packslip message
Date/Time Reference
To specify pertinent dates and times
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Message Text
To provide a free-form format that allows the transmission of text information
Free-form message text
JCP_PID04=JCPPID04 value - Product Description Code - Exceptional personalization data
JCP_PID05_X_08=JCPPIDX08 value - Description - Product Description
JCP_PID05_X_75=JCPPIDX75 value - Description - Color JCP_PID05_X_91=JCPPIDX91 value - Description - Size
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)
Summary
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.