X12 864 Text Message
This Draft Standard for Trial Use 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.
- BBB will use the 864 (Text Message) to automate the notification of invoice errors. All Trading Partners will be required to support the 864 document to be notified of invoices that do not pass our internal edits.
- Rejected documents must be corrected and resent through EDI. (Sample error messages are listed below).
- ~ Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- TX
- Text Message (864)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 864
- Text Message
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment For Text Message
To indicate the beginning of a Text Message Transaction Set
Code identifying purpose of transaction set
- 44
- Rejection
A free-form description to clarify the related data elements and their content
- BMG02 contains the message subject.
REJECTION
Code specifying the type of transaction
- 04
- Electronic Mail Message
Code identifying an organizational entity, a physical location, property or an individual
- VN
- Vendor
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Vendor Number
Detail
Message Identification
To identify the beginning of a specific message and to allow the identification of a subject for the message
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- MIT01 contains the message number.
ZZ
A free-form description to clarify the related data elements and their content
- MIT02 contains the message subject.
"DELETED DOCUMENTS, CORRECT & RESEND"
Message Text
To provide a free-form format that allows the transmission of text information
Free-form message text
Invoice #, Error/Description
Possible Error Descriptions
• INVALID PO #
• PO DOESNT BELONG TO THIS VENDOR
• THIS INVOICE ALREADY EXISTS
• INVALID INVOICE DATE
• INVALID STORE #
• DETAILS DONT = TOTAL
• INVOICE DATE IS GREATER THAN CURRENT DATE
• TOTAL INVOICE LESS THAN 0
Summary
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample
BMG*44*REJECTION*04
DTM*097*20071114
N1*CQ*BED BATH & BEYOND
N1*VN*ACME HOME PRODUCTS*92*120306
MIT*ZZ*DELETED DOCUMENTS, CORRECT & RESEND
MSG*INV 116924 INVALID PO # 123723112507
MSG*INV 116924 DETAILS DONT = TOTAL INV TOTAL 212.99 DETAIL TOTAL 234.27
SE*9*10001
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page 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. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.