EDI

API DocsTerminal
NEW!
Programmatically translate EDI to JSON with the EDI Core REST API
Get started in minutes →
Transaction Set
in
X12 Release 008010

864 Text Message

Functional Group TX

This X12 Transaction Set 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.

Heading

Sequence
Segment
Name
Max use
0100
Transaction Set HeaderMandatory
Max 1
To indicate the start of a transaction set and to assign a control number
0200
Beginning Segment For Text MessageMandatory
Max 1
To indicate the beginning of a Text Message Transaction Set
0300
Date/Time Reference
Max 10
To specify pertinent dates and times
N1 Loop
Repeat 200
0400
Party Identification
Max 1
To identify a party by type of organization, name, and code
0500
Additional Name Information
Max 2
To specify additional names
0600
Party Location
Max 2
To specify the location of the named party
0700
Geographic Location
Max 1
To specify the geographic place of the named party
0800
Reference Information
Max 12
To specify identifying information
0900
Administrative Communications Contact
Max 3
To identify a person or office to whom administrative communications should be directed

Detail

Sequence
Segment
Name
Max use
MIT Loop
Repeat >1
0100
Message IdentificationMandatory
Max 1
To identify the beginning of a specific message and to allow the identification of a subject for the message
In each MIT loop, at least one occurrence of the MSG segment or the MTX segment is required.
Either the MSG segment or the MTX segment may be used in the same MIT loop.
N1 Loop
Repeat 200
0200
Party Identification
Max 1
To identify a party by type of organization, name, and code
0300
Additional Name Information
Max 2
To specify additional names
0400
Party Location
Max 2
To specify the location of the named party
0500
Geographic Location
Max 1
To specify the geographic place of the named party
0600
Reference Information
Max 12
To specify identifying information
0700
Administrative Communications Contact
Max 3
To identify a person or office to whom administrative communications should be directed
0800
Message Text
Max >1
To provide a free-form format that allows the transmission of text information
In each MIT loop, at least one occurrence of the MSG segment or the MTX segment is required.
Either the MSG segment or the MTX segment may be used in the same MIT loop.
0900
Text
Max >1
To specify textual data
To convey a large quantity of text, use of the MTX segment is preferred. Within an 864 transaction set, to avoid potential processing confusion by the receiving party, either the MTX or MSG segment should be selected for use within the MIT loop.

Summary

Sequence
Segment
Name
Max use
0100
Transaction Set TrailerMandatory
Max 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)
Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference and Mapping Guides are provided for marketing purposes and are free of charge. All names, logos, and brands of third parties listed on our site 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. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference and Mapping Guides are provided for marketing purposes and are free of charge. All names, logos, and brands of third parties listed on our site 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. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.