830 Planning Schedule with Release Capability
Kmart · X12 004010
Kmart’s published 830 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
11 of 11 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
BFR
Beginning Segment For Planning Schedule BFR
pos 020
Required
max —
N1 Looprepeats 200
N1
Name N1
pos 230
Required
max —
DETAIL
LIN Looprequired
LIN
Item Identification LIN
pos 010
Required
max —
UIT
Unit Detail UIT
pos 020
Optional
max —
PID
Product Item Description PID
pos 080
Optional
max 1000
REF
Reference Identification REF
pos 140
Optional
max 12
SLN Looprepeats 100
SLN
Subline Item Detail SLN
The SLN segment is used to specify the KSNs, UPCs and shipping GTINs associated with the Purchaser's Item Number specified in the LIN segment. Since there can be more than one UPC and more than one GTIN per KSN, the same KSN may be specified in multiple SLN segments to show the KSN and it's related UPCs and GTINs.
The qualifiers used in data element 235 Product/Service ID Qualifier fields (e.g.SLN09, SLN11) may be sent in any order as long as they are paired with their appropriate Product ID. For example, the SLN09 may contain UP if SLN10contains the U.P.C. number. Or SLN09 may contain IN if SLN10 contains theKSN (after EIM conversion.).
pos 300
Required
max —
FST Loop
FST
Forecast Schedule FST
pos 410
Required
max —
SUMMARY
CTT
Transaction Totals CTT
pos 010
Optional
max —
SE
Transaction Set Trailer SE
pos 020
Optional
max —
Validate a 830
Paste or upload a document and check it against Kmart’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Kmart’s 830 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Kmart, and keeps the spec current as it changes.