972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Communications

EDI 864 Text Message

The X12 document trading partners use to send messages, contracts, explanations and other one-time communications in free-form text.

Sent by
Either trading partner
Received by
Either trading partner
Standard
ANSI ASC X12

What is an EDI 864?

The EDI 864 Text Message is the ANSI X12 transaction set used to move messages, contracts, explanations and other one-time communications electronically. It carries free-form text intended to be read by people rather than processed by business applications.

Retailers and other large trading partners often use the 864 to send notices to suppliers, such as changes to requirements, compliance reminders or explanations of rejected documents. Because the content is free text, the main task for the receiver is getting each message to the right person.

How the EDI 864 worksDiagram of the EDI 864 Text Message. Either trading partner sends it to either trading partner. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BMG (Beginning Segment For Text Message) and detail: the required MIT loop with MIT (Message Identification). 2 optional loops are listed by their first segment.How the EDI 864 worksText Message: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 864SENDEREither trading partnerRECEIVEREither trading partner997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TXGS … GETransaction set 864ST … SEHEADINGBMGBeginning Segment For Text Message+ 1 optional loop, starting with:N1DETAILRequired loop MIT · repeats many timesMITMessage Identification+ 1 optional loop, starting with:N1Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 864. Your trading partner's implementation guide adds its own requirements.
How the EDI 864 worksDiagram of the EDI 864 Text Message. Either trading partner sends it to either trading partner. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BMG (Beginning Segment For Text Message) and detail: the required MIT loop with MIT (Message Identification). 2 optional loops are listed by their first segment.How the EDI 864 worksText Message: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 864SENDEREither tradingpartnerRECEIVEREither tradingpartner997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code TX (GS … GE)Transaction set 864 (ST … SE)HEADINGBMGBeginning Segment For TextMessage+ 1 optional loop, starting with:N1DETAILRequired loop MIT · repeatsmany timesMITMessage Identification+ 1 optional loop, starting with:N1Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 864. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 864, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 864 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Notices of changed EDI or compliance requirements
  • Explanations of rejected or questioned documents
  • One-time announcements to all suppliers

Where it fits in the document flow

This document 864 Text Message
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 864 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BMG
  • N1
  • MIT
  • SE

Practical example

The 864 in practice

A retailer updates its ship notice requirements and sends every supplier an 864 explaining the change and the date it applies. One supplier's EDI system routes 864s straight to the integration team's mailbox, so the team updates its 856 map before the deadline and avoids compliance charges.

Implementation

Implementation considerations for the 864

  • Route 864 messages to a monitored mailbox or queue, because no application will act on them.
  • Keep received messages, as they may document requirement changes and deadlines.
  • Do not use the 864 for data that has its own transaction set, such as orders or invoices.

How ECOM helps

Automate the 864 with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

Service

Fully Managed EDI

ECOM operates your defined EDI services end to end under a service agreement.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related communications documents

All 16 communications documents

Need help with the EDI 864?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us