Kohl's
/
Retail Text Message
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Kohl's. Contact Kohl's for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Kohl's logo

X12 864 Retail Text Message

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data content of the Text Message Transaction Set (864) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide users with a capability to electronically move messages, contracts, explanations, and other one-time communications.

It is the intent of this transaction set to provide electronic communication (messages) for people, not for computer processing. The use of the transaction set to transmit quasi or unique transaction set standards is discouraged.

The use of the Text Message transaction set demands of the sender certain detailed information about the recipient. The transaction set's purpose is to provide communication to the recipient in some human-readable form. The recipient's network will dictate what capabilities are available for delivery of the information. It is the responsibility of the sender to obtain this information and include it in the transmission.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
    View the latest version of this implementation guide as an interactive webpage
    https://www.stedi.com/app/guides/view/kohls/retail-text-message/01HBTVTKPHBDADCAD3WDYXNZN5
    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
    detail
    MIT 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

    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

    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
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    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

    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

    Code identifying a group of application related transaction sets

    TX
    Text Message (864)
    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
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    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

    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
    004010VICS

    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

    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).
    864
    Text Message
    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

    BMG
    020
    Heading > BMG

    Beginning Segment For Text Message

    RequiredMax use 1

    To indicate the beginning of a Text Message Transaction Set

    Example
    BMG-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    00
    Original
    BMG-03
    640
    Transaction Type Code
    Optional

    Code specifying the type of transaction

    04
    Electronic Mail Message
    Heading end

    Detail

    MIT Loop
    RequiredMax >1
    MIT
    010
    Detail > MIT Loop > MIT

    Message Identification

    RequiredMax use 1

    To identify the beginning of a specific message and to allow the identification of a subject for the message

    Example
    MIT-01
    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

    • MIT01 contains the message number.
    MIT-02
    352
    Description
    Optional
    String (AN)
    Min 1Max 80

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

    • MIT02 contains the message subject.
    N1 Loop
    RequiredMax >1
    N1
    020
    Detail > MIT Loop > 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

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

    FR
    Message From
    N1-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    Usage notes

    KOHL’S DEPARTMENT STORES

    PER
    070
    Detail > MIT Loop > N1 Loop > PER

    Administrative Communications Contact

    RequiredMax use 3

    To identify a person or office to whom administrative communications should be directed

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

    Code identifying the major duty or responsibility of the person or group named

    IC
    Information Contact
    PER-02
    93
    Name
    Optional
    String (AN)
    Min 1Max 60

    Free-form name

    Usage notes

    Name and/or Email Contact

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    FX
    Facsimile
    PER-04
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    Usage notes

    Facsimile Number

    PER-05
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-06
    364
    Communication Number
    Optional
    String (AN)
    Min 1Max 80

    Complete communications number including country or area code when applicable

    Usage notes

    Telephone Number

    N1 Loop end
    MSG
    080
    Detail > MIT Loop > MSG

    Message Text

    RequiredMax use 100000

    To provide a free-form format that allows the transmission of text information

    Example
    MSG-01
    933
    Free-Form Message Text
    Required
    String (AN)
    Min 1Max 264

    Free-form message text

    MIT Loop end
    Detail end

    Summary

    SE
    010
    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

    EDI Samples

    Notification of a translation rejection

    ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231004*1524*U*00401*000000001*0*T*>
    GS*TX*SENDERGS*RECEIVERGS*20231004*152454*000000001*X*004010
    ST*864*000000001
    BMG*00**04
    MIT*000000085*Bypassed Inbound Transmission
    N1*FR*KOHL'S DEPARTMENT STORES
    PER*IC*EDIMIO@kohls.com
    MSG*KOHLs has received the following EDI transmissions from your company: Trading Partner Name
    MSG*ISA Control#:000000085, Date Transmitted: 09/04/2018, GS Control#: 200, ST Control#: 0003
    MSG*Document Type: 856 and Application Reference Number: BSN 200809041655
    MSG*This transmission failed to process for the reason(s) below.
    MSG*Error Number #: 779 Mandatory Segment Missing
    MSG* - Source Error Within Attachment: kosn41vis.att
    MSG*This error message is intended for your company's EDI department. It is critical the EDI department address this issue immediately.
    MSG*Please review the Translation Error Detail document located under the EDI tab on www.connection.kohls.com for more information.
    MSG*There is no attachment included with this notification. Trading Partners will need to go to the EDI data to find the error.
    MSG*If a line number is referenced in the error message, line #1 is the ST segment.
    SE*16*000000001
    GE*1*000000001
    IEA*1*000000001

    Notification of an unacknowledged 850 or 860 transmission

    ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231004*1523*U*00401*000000001*0*T*>
    GS*TX*SENDERGS*RECEIVERGS*20231004*152325*000000001*X*004010
    ST*864*000000001
    BMG*00**04
    MIT*600000003*GS Control Number - Missing FA
    N1*FR*KOHL'S DEPARTMENT STORES
    PER*IC*EDIMIO@kohls.com
    MSG*KOHLs has transmitted the following EDI 850s to your company.
    MSG* PO Numbers: Date Transmitted: GS Control #: Ship Date
    MSG* 12345678 08/26/2018 600000003 09/02/2018
    MSG* 23456789 08/26/2018 600000003 09/02/2018
    MSG*We have not received the 997 (Functional Acknowledgement). KOHLs requires
    MSG*that the Acknowledgement must be sent within 48 hours of transmission.
    MSG*Failure to respond may result in chargebacks. Thank you for your
    MSG*assistance in this matter.
    MSG*KOHLs Department Stores
    MSG*Merchandise Information Office - MIO
    MSG*Email: EDIMIO@kohls.com
    SE*17*000000001
    GE*1*000000001
    IEA*1*000000001

    Notification of Kohl’s EDI Outage

    ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231004*1526*U*00401*000000001*0*T*>
    GS*TX*SENDERGS*RECEIVERGS*20231004*152609*000000001*X*004010
    ST*864*000000001
    BMG*00**04
    MIT*000000477*Kohl's EDI Outage 8/31/18
    N1*FR*KOHL'S DEPARTMENT STORES
    PER*IC*EDIMIO@kohls.com
    MSG*Please note Kohl's has a planned EDI outage on Tuesday, August 31st, 2018 from
    MSG*1 am to 9 am central time. Kohl’s will not be able to send or receive EDI
    MSG*transmissions to or from our trading partners during this time. If your AS2
    MSG*software has an automated process to resend a file due to a failure, Kohl’s
    MSG*encourages your company to enable the resend process.
    SE*11*000000001
    GE*1*000000001
    IEA*1*000000001

    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.