Kmart
/
Purchase Order Acknowledgment DC
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Kmart. Contact Kmart for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Kmart logo

X12 855 Purchase Order Acknowledgment DC

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/kmart/purchase-order-acknowledgment-dc/01HAT5AX0T3BTXXDXY4QXAG8D0
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BAK
020
Beginning Segment for Purchase Order Acknowledgment
Max use 1
Required
REF
050
Department Number
Max use 1
Required
REF
050
Internal Vendor Number
Max use 1
Required
REF
050
Purchase Order Number Suffix
Max use 1
Required
DTM
150
Date/Time Reference
Max use 1
Required
N1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PR
Purchase Order Acknowledgement (855)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BAK
020
Heading > BAK

Beginning Segment for Purchase Order Acknowledgment

RequiredMax use 1

To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbers and dates

Usage notes

A separate 855 must be generated for each ship Duns number (LIN05 in the 852).

All items on an 855 P.O. must have the same ship date.

Example
BAK-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BAK-02
587
Acknowledgment Type
Required
Identifier (ID)

Code specifying the type of acknowledgment

AP
Acknowledge - Product Replenishment
BAK-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

KMart purchase order number (11 characters)
This must be the same as the number specified in XPO01 and/or XPO02 in the 852 Product Activity transaction

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BAK04 is the date assigned by the purchaser to purchase order.
Usage notes

PO order date

REF
050
Heading > REF

Department Number

RequiredMax use >1

To specify identifying information

Example
Variants (all may be used)
REFInternal Vendor NumberREFPurchase Order Number Suffix
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

DP
Department Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 3

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

If REF01 contains DP, REF02 contains department number (3 characters).

REF
050
Heading > REF

Internal Vendor Number

RequiredMax use >1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IA
Internal Vendor Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 11

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

If REF01 contains IA, REF02 contains KMart-assigned Vendor number (11 characters).

REF
050
Heading > REF

Purchase Order Number Suffix

RequiredMax use >1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

PS
Purchase Order Number Suffix
REF-02
127
Reference Identification
Required
String (AN)

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

If REF01 contains PS, REF02 contains the KMart P.O. type code (1 or 2 characters). This is used for Special Project Orders only.

The KMart PO types are:
Q - Regular stock replenishment
QA - Allocation / Event

Q
Regular stock replenishment
QA
Allocation / Event
DTM
150
Heading > DTM

Date/Time Reference

RequiredMax use 1

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

067
Current Schedule Delivery
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

P.O. arrival date

N1 Loop
OptionalMax 200
N1
300
Heading > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

ST
Ship To
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

'KMART' (5 characters)

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

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
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

KMart DC Duns number '000394726' plus 4 character DC number.

N1 Loop end
Heading end

Detail

PO1 Loop
OptionalMax 100000
PO1
010
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Usage notes

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 (after EIM conversion.).

The Purchaser's Item Number (qualifier PI in data element 235) is used to specify the Product Identification that is the top of the item hierarchy.

Rules for Data Element 234 when data element 235 contains PR:
Order type - 2 characters
AUX number - 3 characters
Allocation Plan ID – 10 characters
The three pieces of information are considered an “event”. The three numbers are
concatenated and sent as one number in the EDI 852 in ZA07 and is required to be
returned on the 855.
Order types
40 - Reorder
43 - Check off sheet/event
45 - General order

AUX numbers can be found in ZA07 of the 852. If the order type is 40, the AUX number must be 000.

Allocation Plan ID determines how merchandise is allocated to the stores.

The KSN (qualifier IN) and shipping GTIM (qualifier UK) are always required.

Example
If Unit or Basis for Measurement Code (PO1-03) is present, then Quantity Ordered (PO1-02) is required
If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
If either Product/Service ID Qualifier (PO1-12) or Product/Service ID (PO1-13) is present, then the other is required
If either Product/Service ID Qualifier (PO1-06) or Product/Service ID (PO1-07) is present, then the other is required
If either Product/Service ID Qualifier (PO1-14) or Product/Service ID (PO1-15) is present, then the other is required
PO1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
PO1-02
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

PO1-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
EA
Each
PO1-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PI
Purchaser's Item Code
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)
PO1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

13 - 13 EAN number (PO1 Qualifier=EN)
9 - 9 Kmart KSN item number (PO1 Qualifier=IN)
1 – 48 Purchaser's Item Code (PO1 Qualifier=PI) – see note 2
15 – 15 Process number (PO1 Qualifier=PR) – see note 3
14 - 14 Shipping GTIN (PO1 Qualifier=UK)
12 - 12 U.P.C. number (PO1 Qualifier=UP)

PO1-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PI
Purchaser's Item Code
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)
PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See PO107

PO1-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PI
Purchaser's Item Code
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)
PO1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See PO107

PO1-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PI
Purchaser's Item Code
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)
PO1-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See PO107

PO1-14
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PI
Purchaser's Item Code
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)
PO1-15
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See PO107

DTM
200
Detail > PO1 Loop > DTM

Date/Time Reference

RequiredMax use 1

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

015
Promotion Start
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Must match the date sent in the ZA05 (arrival date) of the 852.

PO1 Loop end
Detail end

Summary

CTT Loop
OptionalMax 1
CTT
010
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

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-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

CTT Loop end
SE
030
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.