To start and identify an interchange of zero or more functional groups and interchange-related control segments
Sheplers X12 864 Text Message
X12 864 (Text Message) is the EDI transaction exchanged between Sheplers (Sheplers (via ecUtopia)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 8
- Loops
- 1
- X12 864
- All partners ↗
Transaction context
Where 864 Text Message fits on Sheplers (via ecUtopia)
- Sheplers channels
- 1 of 1
- Trading partners
- 15
- Channels
- 25
1 of Sheplers's 1 channel carries 864
partners across the Stacksync network trade 864
channels network-wide carry 864
Most common alongside 864
On ecUtopia, 864 runs on 2 channels.
The 864 transmits free-form, human-readable text such as one-time notices, error explanations, and policy or system announcements through the same audited EDI channel as structured documents. A common production use in retail supply chains is a buyer telling a supplier that a previously submitted document, often an invoice or ASN, failed validation and must be corrected. Because the content has no machine-processable schema, it is written for people rather than for automated posting. Either party can originate one, but in practice it is usually sent by the retailer, buyer, or 3PL to the supplier's EDI or accounting team.
When it fires: A buyer's system rejects a supplier document, for example an invoice that fails validation rules, and issues an 864 explaining the errors and requesting a corrected retransmission.
Common 864 rejection causes
- Messages go unread because they require human review; rejection notices sit in the mailbox while the flawed invoice or ASN is never corrected.
- Used to carry structured business data that belongs in a dedicated transaction set such as the 824 Application Advice, so the receiver cannot process it automatically.
- MSG and MTX text segments mixed inconsistently within a message loop, which X12 usage notes warn will confuse receivers.
- No reference identification linking the text to the failed document, forcing the supplier to guess which transaction the notice concerns.
Specification summary
X12 864 Text Message at the element level
The X12 864 specification defines 16 segments carrying 52 data elements, 35 of which are mandatory.
- Segments
- 16
- Data elements
- 52
- Mandatory elements
- 35
| Segment | Elements | Mandatory |
|---|---|---|
| BMG | 3 | 1 |
| N1 | 4 | 1 |
| MIT | 1 | 1 |
| N3 | 2 | 1 |
| REF | 2 | 1 |
| PER | 4 | 1 |
| MSG | 1 | 1 |
Key identifiers in 864
- Transaction Set Purpose Code
- Entity Identifier Code
- Reference Identification
- Address Information
- Reference Identification Qualifier
- Contact Function Code
- Free-Form Message Text
Full segment guideline — 8 segments 1 loop · X12 864 Text Message
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of a Text Message Transaction Set
To specify pertinent dates and times
MIT Loop
To identify the beginning of a specific message and to allow the identification of a subject for the message
To provide a free-form format that allows the transmission of text information
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
5+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
PU Purchase Order PU Purchase Order Acknowledgment SH Ship Notice Manifest IN Invoice IN Inventory Inquiry Advice
No trading partner matches your search.
Browse the full directory
Sheplers Sheplers (via ecUtopia) EDI 864 FAQ
Common questions about 864 Text Message on the Sheplers (via ecUtopia) channel.
What is X12 864 Text Message?
X12 864 (Text Message) is the EDI transaction set used to exchange text message data. Sheplers's Sheplers (via ecUtopia) channel requires it from trading partners.
Does Sheplers Sheplers (via ecUtopia) require 864 for trading partners?
Yes, Sheplers (Sheplers (via ecUtopia)) supports X12 864 Text Message. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Sheplers 864 with Stacksync?
Most companies go live with Sheplers 864 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 864 on Sheplers (via ecUtopia)?
On Sheplers (via ecUtopia), X12 864 is typically exchanged alongside 850 Purchase Order, 810 Invoice, 856 Ship Notice Manifest, 855 Purchase Order Acknowledgment. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Sheplers EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
