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

X12 864 Text Message

X12 Release 4030

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
  • ^ Repetition
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/dollar-tree/text-message/01H66GR1WBDCM7E1KDW4PZMMFC
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
0100
Transaction Set Header
Max use 1
Required
BMG
0200
Beginning Segment For Text Message
Max use 1
Required
DTM
0300
Date/Time Reference
Max use 10
Optional
Message From
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
Identifier (ID)

Code identifying 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 identifying 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

Code indicating 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

Code indicating 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
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00403
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
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 indicating sender's request for an interchange acknowledgment

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

Code indicating 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

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
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480

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

004030
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

Heading

ST
0100
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) is 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
0200
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
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BMG-02
352
Description
Optional
String (AN)
Min 1Max 80

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

  • BMG02 contains the message subject.
BMG-03
640
Transaction Type Code
Optional
Identifier (ID)

Code specifying the type of transaction

03
Report Message

A human-readable report intended to be put on paper.

DTM
0300
Heading > DTM

Date/Time Reference

OptionalMax use 10

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

003
Invoice
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

N1 Message From
OptionalMax >1
Variants (all may be used)
Message To
N1
0400
Heading > Message From > N1

Name

RequiredMax use 1

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

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

FR
Message From
N1-02
93
Name
Optional
String (AN)

Free-form name

FAMILY DOLLAR STORES
FAMILY DOLLAR STORES
N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
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 Message From end
N1 Message To
OptionalMax >1
Variants (all may be used)
Message From
N1
0400
Heading > Message To > 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

TO
Message To
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

REF
0800
Heading > Message To > REF

Internal Vendor Number

OptionalMax use 12

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
Optional
String (AN)
Min 1Max 50

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

REF
0800
Heading > Message To > REF

Seller's Invoice Number

OptionalMax use 12

To specify identifying information

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

Code qualifying the Reference Identification

IV
Seller's Invoice Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

N1 Message To end
Heading end

Detail

MIT Loop
RequiredMax >1
MIT
0100
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)

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

  • MIT01 contains the message number.
PLEASE CORRECT AND RESUBMIT
PLEASE CORRECT AND RESUBMIT
MIT-02
352
Description
Optional
String (AN)

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

  • MIT02 contains the message subject.
THIS INVOICE HAS NOT BEEN PROCESSED
THIS INVOICE HAS NOT BEEN PROCESSED
MSG
0800
Detail > MIT Loop > MSG

Message Text

RequiredMax use >1

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

Usage notes

Will repeat for every error on the particular invoice.

Error Msg: Invalid Transaction Type Flag: (The 810 transaction cannot be correctly identified as a Sale(Debit)/Credit/Non-Mdse Invoice)

Correction Required: Correct the Invoice type in the BIG07 & Retransmit

Example
If Number (MSG-03) is present, then Printer Carriage Control Code (MSG-02) is required
MSG-01
933
Free-Form Message Text
Required
String (AN)
Min 1Max 264

Free-form message text

Usage notes

If you have any questions about the Error Messages or the corresponding Correction Required please contact FDAP@familydollar.com.

Error Msg: Invalid Transaction Type Flag: (The 810 transaction cannot be correctly identified as a Sale (Debit)/Credit/Non-Mdse Invoice)

Correction Required: Correct the Invoice type in the BIG07 & Retransmit

Error Msg: Invalid Supplier Number: (The 810 transaction does not have the correct Family Dollar Supplier Number)

Correction Required: Correct supplier number in the REF02 segment. The Supplier Number is supplied on the 850 in the REF*VR segment.

Error Msg: Invalid Purchase Order: (The purchase order on the 810 is not valid in the Family Dollar Merchandise System, this doesn't affect DSD Vendors)

Correction Required: Correct the purchase order number in the BIG04 with the purchase order that was supplied on the 850 in the BEG02.

Error Msg: Must be a Valid Store or Warehouse: (The correct Family Dollar store/warehouse location number wasn't provided)

Correction Required: Correct the Store/Warehouse location and retransmit the invoice.

Error Msg: Invalid Change Code: (A SAC02 code was sent that is not on the allowed listing)

Correction Required: Correct the SAC02 code and retransmit the invoice. A complete list of accepted SAC codes at the detail and summary level are listed in the 810 specifications.

Error Msg: Number of Charge Codes supplied exceeded maximum: (The invoice/credit contains more than 25 SAC codes)

Correction Required: DO NOT RETRANSMIT! This is for your information only. Please contact Family Dollar AP Department at FDAP@familydollar.com for instructions on how to split the invoice into multiple invoices.

Error Msg: Duplicate Invoice: (The original invoice number is already processed and in our system and the duplicate will not be processed)

Correction Required: DO NOT RETRANSMIT! This is for your information only.

Error Msg: Number Of Order Numbers supplied exceed the maximum: (An invoice/credit may contain up to 25 PO numbers)

Correction Required: DO NOT RETRANSMIT! This is for your information only. Please contact Family Dollar AP Department at FDAP@familydollar.com for instructions on how to split the invoice into multiple invoices.

Error Msg: Number of VBOL supplied exceeded maximum: (An invoice/credit may contain up to 25 VBOL numbers)

Correction Required: DO NOT RETRANSMIT! This is for your information only. Please contact Family Dollar AP Department at FDAP@familydollar.com for instructions on how to split the invoice into multiple invoices.

Error Msg: Invalid SKU: (The SKU billed on the invoice is not present in our system or is different from the one provided on the purchase order)

Correction Required: Correct the SKU and retransmit. Please contact your respective merchandising department to get the correct SKU for your item. Family Dollar SKU is required with a code of "SK" in case you are not sending the item/case UPC or if the case/item UPC has not been provided to the Family Dollar Merchandising Department for a particular SKU.

Error Msg: Invalid UPC: (The UPC billed on the invoice is not present in our system or is different from the one provided on the purchase order)

Correction Required: Correct the UPC (Each/Case) and retransmit. Please provide your respective merchandising department with the correct UPC for a particular SKU. Either an EACH or a CASE UPC is required when you are not sending the Family Dollar SKU. You only need to provide the respective UPC for the UOM that you are using for Billing. UA - CASE (2-5-5) or UP - EACH (1-5-5-1).

Error Msg: Invoice UPC Qualifier: (The UPC qualifier didn't match the UOM that was sent)

Correction Required: Correct the UPC qualifier and retransmit. Family Dollar only accepts invoices in an UOM of EA and/or CA. A qualifier of UA and the corresponding shipper UPC is required when billing in cases and a qualifier of UP and the corresponding shipper UPC is required when billing in eaches.

MSG-02
934
Printer Carriage Control Code
Optional
Identifier (ID)

A field to be used for the control of the line feed of the receiving printer

  • MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.
SS
Advance to new line before print
MSG-03
1470
Number
Optional
Numeric (N0)
Min 1Max 9

A generic number

  • MSG03 is the number of lines to advance before printing.
  • If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.
Usage notes

1

MIT Loop end
Detail end

Summary

SE
0100
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.