Kmart
/
Purchase Order Change Request - Buyer Initiated
  • Specification
  • EDI Inspector
Import guide into your account
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 860 Purchase Order Change Request - Buyer Initiated

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request - Buyer Initiated Transaction Set (860) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the information required for the customary and established business and industry practice relative to a purchase order change. This transaction can be used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties.

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-change-request-buyer-initiated/01HAT5ANDCZ513B2BBW517PH09
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
BCH
020
Beginning Segment for Purchase Order Change
Max use 1
Required
REF
050
Department Number
Max use 2
Required
REF
050
Internal Vendor Number
Max use 2
Required
REF
050
Purchase Order Number Suffix
Max use 2
Required
DTM
150
Date/Time Reference
Max use 2
Optional
N1 Loop
detail
POC 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

PC
Purchase Order Change Request - Buyer Initiated (860)
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

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
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).
860
Purchase Order Change Request - Buyer Initiated
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

BCH
020
Heading > BCH

Beginning Segment for Purchase Order Change

RequiredMax use 1

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

Usage notes

BCH01 will contain code 04 for all change requests except order
level cancellations. BCH01 will contain code 01 only when all open
items on the order are cancelled.

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

Code identifying purpose of transaction set

01
Cancellation
04
Change
BCH-02
92
Purchase Order Type Code
Required
Identifier (ID)

Code specifying the type of Purchase Order

RL
Release or Delivery Order
SA
Stand-alone Order
BCH-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

9 – 11 Original P.O. number

BCH-06
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCH06 is the date assigned by the purchaser to purchase order.
BCH-11
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BCH11 is the date of the purchase order change request.
REF
050
Heading > REF

Department Number

RequiredMax use 2

To specify identifying information

Usage notes

When REF01 contains code DP, REF02 contains 3 characters.

The department number for direct to store orders will be specified at the item level. REF02 when REF01 contains code DP will always contain 999 in the header REF segment.

Direct to store orders will only have one iteration of the REF segment to specify the 999 department number.

The department number for JIT or DC orders will be specified in the header in REF02 when REF01 contains code DP.

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

REF
050
Heading > REF

Internal Vendor Number

RequiredMax use 2

To specify identifying information

Usage notes

When REF01 contains code IA, REF02 contains 11 characters.

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

REF
050
Heading > REF

Purchase Order Number Suffix

RequiredMax use 2

To specify identifying information

Usage notes

When REF01 contains code PS, REF02 contains 1 - 2 characters.
A = Accelerated flow
R = Regular
J1 = Just in Time Inventory (JIT)

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

A
Accelerated flow
J1
Just in Time Inventory (JIT)
R
Regular
DTM
150
Heading > DTM

Date/Time Reference

OptionalMax use 2

To specify pertinent dates and times

Usage notes

The DTM segment will be transmitted to specify a revised ship / delivery date only. If the date has not changed, this segment will not be sent.

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

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

002
Delivery Requested
010
Requested Ship
074
Requested for Delivery (Prior to and Including)
076
Scheduled for Delivery (Week of)
DTM-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

N1 Loop
RequiredMax 2
N1
300
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

N101 will contain BY when the purchase order is for Just In Time
Inventory only (REF02 contains J1 when REF01 contains PS).

If N101 contains ST, N104 will contain the following:
Direct to store Duns # '008965873' + 4 character store number
OR
DC Duns # '000394726' + 4 character DC number

If N101 contains BY, N104 will contain the four position store unit number

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

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

BY
Buying Party (Purchaser)
ST
Ship To
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

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
92
Assigned by Buyer or Buyer's Agent
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.
N1 Loop end
Heading end

Detail

POC Loop
OptionalMax >1
POC
010
Detail > POC Loop > POC

Line Item Change

RequiredMax use 1

To specify changes to a line item

Usage notes

POC segments will NOT be sent on order level cancellations
(BCH01 contains code 01) or order level ship date changes.

Each change to a line item will be specified in a separate POC loop.
Therefore, more than one POC loop for the same item may be present in the same transaction when more than one change is made to the item.

When an item is added to a purchase order (POC02 contains code AI), then all detail information for that item, including cost, pack quantities, and item description will be sent.

POC03 is the current (net) amount on order before the quantity is applied. POC04 is the quantity to be subtracted or added based upon the code in POC02. This is based on VICS retail industry standards.

If the shipping GTIN or retail GTIN (UPC or EAN number) is changed, there will be two POC segments generated. The first POC will contain code value DI in POC02 and the second will contain AI in POC02. Both POC segments will contain the same item line number in POC01.

The qualifiers used in data element 235 Product/Service ID Qualifier fields (e.g. POC06, POC08) may be sent in any order as long as they are paired with their appropriate Product ID. For example, the POC06 may contain UP if POC07 contains the U.P.C. number. Or POC06 may contain IN if POC08 contains the KSN (after EIM conversion.). In other words, the receiver of the 860 must be able to accept any 235 Product/Service ID Qualifier and the paired Product ID in any of the applicable fields.

POC02 containing code ‘CA’ is used to indicate that the pack quantities in the PO4 segment have changed.

If an item has been partially shipped and the remainder is cancelled by Sears Holdings, an item deletion (POC02 containing code DI) will be sent to cancel the balance

Example
If either Product/Service ID Qualifier (POC-10) or Product/Service ID (POC-11) is present, then the other is required
If either Product/Service ID Qualifier (POC-12) or Product/Service ID (POC-13) is present, then the other is required
If either Product/Service ID Qualifier (POC-14) or Product/Service ID (POC-15) is present, then the other is required
POC-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • POC01 is the purchase order line item identification.
POC-02
670
Change or Response Type Code
Required
Identifier (ID)

Code specifying the type of change to the line item

AI
Add Additional Item(s)
CA
Changes To Line Items
DI
Delete Item(s)
QD
Quantity Decrease
QI
Quantity Increase
POC-03
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

POC-04
671
Quantity Left to Receive
Optional
Decimal number (R)
Min 1Max 9

Quantity left to receive as qualified by the unit of measure

POC-05
C001
Composite Unit of Measure
OptionalMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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

AS
Assortment
CA
Case
EA
Each
POC-06
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

POC-08
235
Product/Service ID Qualifier
Required
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
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
POC-09
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

13 - 13 EAN number (POC Qualifier=EN)
9 - 9 Kmart KSN item number (POC Qualifier=IN)
14 - 14 Shipping GTIN (POC Qualifier=UK)
12 - 12 U.P.C. number (POC Qualifier=UP)
1 - 17 Vendor's item number (POC Qualifier=VN)

POC-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
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
POC-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See POC09

POC-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
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
POC-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See POC09

POC-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
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
POC-15
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See POC09

PID Loop
OptionalMax 1000
PID
050
Detail > POC Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Usage notes

The PID segment is used to provide the item description. This segment will be present for added item only (POC01 contains code AI).

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

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
PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID Loop end
PO4
090
Detail > POC Loop > PO4

Item Physical Details

OptionalMax use 1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Usage notes

The PO4 segment will be present if the pack quantities change. POC02 will contain code CA.

The PO4 segment may be present if an item is added (POC02 contains code AI).

Example
If either Size (PO4-02) or Unit or Basis for Measurement Code (PO4-03) is present, then the other is required
PO4-01
356
Pack
Optional
Numeric (N0)
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

PO4-02
357
Size
Optional
Decimal number (R)
Min 1Max 8

Size of supplier units in pack

PO4-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

  • 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".
AS
Assortment
CA
Case
EA
Each
REF
100
Detail > POC Loop > REF

Reference Identification

OptionalMax use 1

To specify identifying information

Usage notes

When REF01 contains code DP, REF02 contains 3 characters.

The department number for direct to store orders will be specified at the item level. REF02 when REF01 contains code DP will always contain 999 in the header REF segment.

The department number for JIT or DC orders will be specified in the header in REF02 when REF01 contains code DP.

Example
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 30

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

POC Loop end
Detail end

Summary

CTT Loop
RequiredMax >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

  • Number of line items (CTT01) is the accumulation of the number of POC segments.
    If used, hash total (CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment.
Usage notes

CTT01 will contain a count of POC segments. If no POC segments are present, CTT01 will contain zero.

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.