EDI 864 Text Message
Functional Group TX
X12C Communications and Controls Subcommittee
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
- 0100Transaction Set HeaderMandatoryMax 1
To indicate the start of a transaction set and to assign a control number
- 0200Beginning Segment For Text MessageMandatoryMax 1
To indicate the beginning of a Text Message Transaction Set
- 0300Date/Time ReferenceOptionalMax 10
To specify pertinent dates and times
- N1 Loop OptionalRepeat 200
- 0400Party IdentificationMandatoryMax 1
To identify a party by type of organization, name, and code
- 0500Additional Name InformationOptionalMax 2
To specify additional names
- 0600Party LocationOptionalMax 2
To specify the location of the named party
- 0700Geographic LocationOptionalMax 1
To specify the geographic place of the named party
- 0800Reference InformationOptionalMax 12
To specify identifying information
- 0900Administrative Communications ContactOptionalMax 3
To identify a person or office to whom administrative communications should be directed
- 0400Party IdentificationMandatoryMax 1
Detail
- MIT Loop MandatoryRepeat >1
- 0100Message IdentificationMandatoryMax 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 OptionalRepeat 200
- 0200Party IdentificationMandatoryMax 1
To identify a party by type of organization, name, and code
- 0300Additional Name InformationOptionalMax 2
To specify additional names
- 0400Party LocationOptionalMax 2
To specify the location of the named party
- 0500Geographic LocationOptionalMax 1
To specify the geographic place of the named party
- 0600Reference InformationOptionalMax 12
To specify identifying information
- 0700Administrative Communications ContactOptionalMax 3
To identify a person or office to whom administrative communications should be directed
- 0200Party IdentificationMandatoryMax 1
- 0800Message TextOptionalMax >1
To provide a free-form format that allows the transmission of text information
- 0900TextOptionalMax >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.
- 0100Message IdentificationMandatoryMax 1
Summary
- 0100Transaction Set TrailerMandatoryMax 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)