To start and identify an interchange of zero or more functional groups and interchange-related control segments
Sheplers X12 864 Text Message
Plan X12 864 Text Message for Sheplers (via ecUtopia). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 8
- Loops
- 1
- X12 864
- Partner references ↗
Implementation guide
Sheplers (via ecUtopia): 864 mapping and validation
X12 864 Text Message is used when a trading partner sends information intended for a recipient. Preserve message reference, subject and related business document so the business message in your business system stays connected to the original document.
This document is listed for Sheplers (via ecUtopia). Confirm the version, required fields and responses that apply to your account.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | business message message reference, subject and related business document |
|
| Update the receiving system | Processing the business message ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the business message Original document reference and matching response |
|
The document reference includes 8 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a trading partner sends information intended for a recipient. Name the operational owner of the business message and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map message reference, subject and related business document. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and Sheplers guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic business message data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful business message processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 864 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic business message data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out business message without processing it twice.
Transaction context
Where 864 Text Message fits on Sheplers (via ecUtopia)
- Sheplers channels
- 1 of 1
1 of Sheplers's 1 channel list 864
- Trading partners
- 15
partner references list 864
- Channels
- 25
channel entries list 864
Frequently listed alongside 864
The directory associates ecUtopia and 864 with 2 channels.
Document structure
X12 864 Text Message at the element level
The X12 864 reference contains 16 segment entries and 52 data elements; 35 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Segment reference — 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)
Related references
Other transactions in Sheplers (via ecUtopia)
Other EDI documents listed on this channel.
Purchase Order X12 850 Purchase Order Acknowledgment X12 855 Ship Notice Manifest X12 856 Invoice X12 810 Inventory Inquiry Advice X12 846
No references match your search.
Showing 5 of 5 references
Browse the full directorySheplers (via ecUtopia) EDI 864 questions
Common questions about 864 Text Message on the Sheplers (via ecUtopia) channel.
What is X12 864 Text Message used for?
864 is used when a trading partner sends information intended for a recipient. It carries information for the business message. Match it to your business system using message reference, subject and related business document.
Is 864 required for Sheplers (via ecUtopia)?
864 is listed for Sheplers (via ecUtopia). Confirm the required version and direction for your business unit and account with the partner.
What should I map for X12 864?
Start with message reference, subject and related business document and the target business message. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 864 error handling?
Preserve line breaks and readable content in the receiving work queue. Test an urgent message linked to an order and assign a human owner instead of silently filing it. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 864 relate to other EDI messages?
X12 850 Purchase Order is a related document also listed on Sheplers (via ecUtopia). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 864 and 850?
864 is used when a trading partner sends information intended for a recipient. 850 is used when a buyer places an order. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
Connect Sheplers EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
