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.
The Signet Jewelers specific EDI 850 guide outlines the specific business rules and functional requirements that apply to Signet Jewelers.
During the supplier on boarding process with CommerceHub you may contact the CommerceHub Onboarding Team by sending an email to partnersetup@commercehub.com. Be sure to include the following information:
-your company name
-your contact Information (email and phone number)
-the name of the retailer that you are working with
-a detailed description of the questions that you have
Once your account has been put into production you should contact the CommerceHub Customer Support Team at 518-810-0700 and select option 2 from the main menu or via email: customersupport@commercehub.com. Customer support is available Monday through Friday from 8:00 am to 6:00 pm, Eastern Time.
In the tables below, "User Attrib" represents CommerceHub requirements.
Shipping information (Ship-to, Bill-to, Ship-from, Carrier/routing) will be communicated in the Heading unless it can vary from one PO line to the next, in which case it will be communicated in the Detail. This affects the DTM and TD5 segments and the N1 loop.
MESSAGE PURPOSE AND BUSINESS RULES:
The Signet Jewelers specific 850 conveys all information necessary to fulfill a drop ship order originating with this retailer.
The following business rules apply to the Signet Jewelers purchase order file:
- Purchase Order number must be greater than or equal to 7 digits.
- Shipping Method must be within the merchant specific table.
- Line Number must be present, greater than or equal to 1 and unique within the Purchase Order.
- Quantity Ordered must be present and greater than 0.
- Unit Cost must be present and greater than or equal to 0
- ~ 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*1599999999**20131031
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
This element contains the Signet Jewelers purchase order number. This element is required to be included in the packing slip if you are creating your own.
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
EXAMPLE: CURX6USD
CURX6CAD
Code identifying an organizational entity, a physical location, property or an individual
ISO currency in which all monetary values in order are expressed.
- X6
- International Organization
Reference Identification
To specify identifying information
The IA and X9 qualifiers are always used
EXAMPLES: REFIAV12345
REFPQ**VISA
REFX9123456789
REFCO*93993832
Code qualifying the Reference Identification
- 7U
- Related Transaction Reference Number
Secondary ID for the customer's order
- 19
- Division Identifier
Merchant / PO Issuer division
- CO
- Customer Order Number
Customer's order number w/merchant (REF02).
- IA
- Internal Vendor Number
Merchant assigned vendor number
- PQ
- Payee Identification
Credit Card Qualifier
- X9
- Internal Control Number
CommerceHub internal ID
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: SACSH151***********TRUE
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.
- S
- Service
Special processing/handling information
Code identifying the service, promotion, allowance, or charge
- H151
- Special Services
Gift processing
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.
Communicates whether customer monetary values should be suppressed on the packslip: "true" = Prices suppressed
Date/Time Reference
To specify pertinent dates and times
EXAMPLES: DTM00620130227
Code specifying type of date or time, or both date and time
- 006
- Sold
Customer order date
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)
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
EXAMPLE: TD5*****UG
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
This element will contain a Signet Jewelers specific code that indicates which service level and shipping carrier should be used. Contact CommerceHub to obtain a complete list of codes that apply to your relationship with Signet Jewelers.
Reference Identification
To transmit identifying information as specified by the Reference Identification Qualifier
EXAMPLE: N9SD0002
Code qualifying the Reference Identification
- SD
- Sales Division
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
EXAMPLE: N321 CORPORATE DRSUITE 205
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)
Reference Identification
To specify identifying information
EXAMPLE: REF4CS
REF4CC
Code qualifying the Reference Identification
- 4C
- Shipment Destination Code
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
- BD
- Buyer Name or Department
Used for primary instance of PER segment in N1 loop
Code identifying the type of communication number
- TE
- Telephone
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
EXAMPLE: N321 CORPORATE DRSUITE 205
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)
Reference Identification
To specify identifying information
EXAMPLE: REF4CS
REF4CC
Code qualifying the Reference Identification
- 4C
- Shipment Destination Code
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
- BD
- Buyer Name or Department
Used for primary instance of PER segment in N1 loop
Code identifying the type of communication number
- TE
- Telephone
Name
To identify a party by type of organization, name, and code
Address Information
To specify the location of the named party
EXAMPLE: N321 CORPORATE DRSUITE 205
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)
Reference Identification
To specify identifying information
EXAMPLE: REF4CS
REF4CC
Code qualifying the Reference Identification
- 4C
- Shipment Destination Code
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
- BD
- Buyer Name or Department
Used for primary instance of PER segment in N1 loop
Code identifying the type of communication number
- TE
- Telephone
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
EXAMPLE: PO101531.02TESKJ07874VN49-98760
PO101*531.02FXSKJ07874VN*49-98760
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Merchant's PO line number
Price per unit of product, service, commodity, etc.
Unit cost the merchant expects to be billed for each unit fulfilled
Code identifying the type of unit price for an item
- FX
- Fixed Price
Used to convey unit cost adjustment flag
If this qualifier is used, the supplier may invoice at a different unit cost than provided on the order.
- 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.
- SK
- Stock Keeping Unit (SKU)
This code is used to qualify the Signet Jeweler’s SKU code
Identifying number for a product or service
Signet Jeweler’s SKU code
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- VN
- Vendor's (Seller's) Item Number
Pricing Information
To specify pricing information
EXAMPLE: CPTRSRES*47.98
Code identifying pricing specification
- RES
- Resale
Product/Item Description
To describe a product or process in coded or free-form format
EXAMPLES: PIDF08***RING
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
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**0022037-0695-007500
SACS*H151***To: Sally^Get well soon!^From:George
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
Will communicate 19 digit code that aides in-store returns
- S
- Service
Special processing/handling information
Code identifying the service, promotion, allowance, or charge
- F050
- Other (See related description)
Packslip message
- H151
- Special Services
Gift processing
A free-form description to clarify the related data elements and their content
- If SAC-02 = F050 then packslip message
- If SAC-02 = H151 then gift message. Gift messages may include carets to indicate a line break on the packing slip.
- Otherwise, optional description of charge or allowance
Date/Time Reference
To specify pertinent dates and times
EXAMPLES: DTM01020000227
DTM00220000229
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
EXAMPLE: TD5*****UG
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
This element will contain a Signet Jewelers specific code that indicates which service level and shipping carrier should be used. Contact CommerceHub to obtain a complete list of codes that apply to your relationship with Signet Jewelers.
Message Text
To provide a free-form format that allows the transmission of text information
EXAMPLE: MSG*MONOGRAM = "DAS"
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. 'stop-sell' situation.
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.