X12 855 Purchase Order Acknowledgment Direct-to-store and JIT
This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction Set (855) 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 a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.
- ~ 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
- PR
- Purchase Order Acknowledgement (855)
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).
- 855
- Purchase Order Acknowledgment
Beginning Segment for Purchase Order Acknowledgment
To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates
Code identifying purpose of transaction set
- 00
- Original
Code specifying the type of acknowledgment
- ZZ
- Mutually Defined
Identifying number for Purchase Order assigned by the orderer/purchaser
This number must ALWAYS be 10 digits.
For merchandise shipped to our distribution center for cross-dock to the stores (JIT), the purchase order acknowledgement number must be all zeroes.
For merchandise shipped directly to the stores from the vendor, the purchase order acknowledgement range will be supplied by Kmart.
Internal Vendor Number
To specify identifying information
If REF01 contains IA, REF02 contains Kmart-assigned Vendor number. This must be an 11-digit number.
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Vendor Order Number
To specify identifying information
If REF01 contains VN, REF02 contains Vendor-assigned order number. The Vendor Order number does not need to be the same as the Kmart purchase order number.
Code qualifying the Reference Identification
- VN
- Vendor Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
If REF01 contains VN, REF02 contains Vendor-assigned order number.
The Vendor Order number does not need to be the same as the Kmart purchase order number.
Date/Time Reference
To specify pertinent dates and times
'Deliver on" date must be within 30 days of the current date
Name
To identify a party by type of organization, name, and code
If the merchandise is being shipped to a Kmart unit and you have been provided a 9 digit Vendor Order Duns number, then N103 must contain the qualifier 9 and N104 must contain your 9 digit Vendor Order Duns number plus 4 character Kmart store.
If the merchandise is being shipped to a Sears unit and you have been provided a 11 digit Vendor Order ‘Duns’ number, then N103 must contain the qualifier 92 and N104 must contain your 11 digit Vendor Order ‘Duns’ number plus 4 character Kmart store.
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
Code designating the system/method of code structure used for Identification Code (67)
- 9
- D-U-N-S+4, D-U-N-S Number with Four Character Suffix
- 92
- Assigned by Buyer or Buyer's Agent
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.
Detail
Baseline Item Data
To specify basic and most frequently used line item data
- PO102 is required.
The qualifiers used in data element 235 Product/Service ID Qualifier fields (e.g. PO106, PO108) may come in any order as long as they are paired with their appropriate Product ID. For example, the PO106 may contain UP if PO107 contains the U.P.C. number. Or PO106 may contain IN if PO107 contains the KSN.
KSN is required, which is 9 characters. Product ID Qualifier must be IN.
The KSN is nine characters; the format is different than displayed in IMA. The KSN that is sent and required to be returned contains the eight characters displayed in IMA with a leading zero. The dash and check digit displayed in IMA must not be used in EDI.
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
- PR
- Promotion
- 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.
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- PR
- Process Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 - 13 EAN number (PO1 Qualifier=EN)
9 - 9 Kmart KSN item number (PO1 Qualifier=IN)
5 – 5 Process number (PO1 Qualifier=PR) – see note
14 - 14 Shipping GTIN (PO1 Qualifier=UK)
12 - 12 U.P.C. number (PO1 Qualifier=UP)
1 - 17 Vendor's item number (PO1 Qualifier=VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- PR
- Process Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See PO107
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- PR
- Process Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See PO107
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- PR
- Process Number
- UK
- U.P.C./EAN Shipping Container Code (1-2-5-5-1)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VN
- Vendor's (Seller's) Item Number
Pricing Information
To specify pricing information
If the retail selling price is not available, then do not send this segment.
Code identifying pricing specification
- MSR
- Manufacturer's Suggested Retail
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
Number of items per case
Size of supplier units in pack
Number of eaches per inner pack, if applicable
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
- EA
- Each
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DP
- Department Number
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
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
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.