Text message transactions
The Text message transaction enables trading partners to exchange free-form, human-readable messages directly through standard EDI channels. Unlike transactional EDI messages that require structured data for system processing, the text message is designed for non-transactional communication such as instructions, clarifications, alerts, or one-time announcements that benefit from being shared within the EDI framework but do not need to trigger system actions.
As a standardized alternative to email, fax, or phone calls, the text message allows person-to-person communication within existing EDI workflows. Its lightweight and flexible format makes it ideal for delivering operational updates, compliance notices, regulatory announcements, or supporting messages related to other EDI transactions.
The direction of the Text Message depends on which party needs to communicate. Manufacturers, suppliers, distributors, 3PLs, or carriers use text message to share updates with customers, wholesalers, hospitals, or retailers—and vice versa. For example, a manufacturer could send a text message to inform a retailer about a product recall, while a wholesaler might use it to clarify a previously rejected order.
By embedding unstructured messages into the EDI environment, the text message transaction helps partners communicate faster, reduce confusion, minimize manual follow-up, and avoid introducing new communication channels—streamlining business interactions across the supply chain.
Type = API Reference,; Topic = Multienterprise Information Network Tower (MINT),;Persona = TraceLink Administrator, User,; Orchestration = Manufacturing, Logistics, Commerce,; Function = Supply Chain, IT, Procurement,
Text message (X12)
The text message is exchanged asynchronously through standard EDI channels in X12 format and typically appears in EDI inboxes or line-of-business systems that support message viewing.
Contact your TraceLink Services representative for more information about integrating with this message.
- Message Type: MPC_TEXT_MESSAGE
- X12 Format: TEXTMESSAGE
B2B_EDI_X12_864_TextMessage_IB_V1
B2B_EDI_X12_864_TextMessage_OB_V1
Transform Names:
| Input Element | Occurs | Length | Description | Example | ||||
|---|---|---|---|---|---|---|---|---|
| ISA | 1…1 | - | Required. ISA interchange envelope. | - | ||||
| ISA01 | 1…1 | 2/2 | Required. Qualifier for authorization control number in ISA02. | 00 | ||||
| ISA02 | 1…1 | 10/10 | Required. Information used for additional identification or authorization of the interchange sender or the data in the interchange/ 10 spaces a valid entry. | - | ||||
| ISA03 | 1…1 | 2/2 | Required. Qualifier for security information in ISA04. | 00 | ||||
| ISA04 | 1…1 | 10/10 | Required. Identifies security information about the interchange sender or data | - | ||||
| ISA05 | 1…1 | 2/2 |
Required. Interchange sender partner ID qualifier.
|
07 | ||||
| ISA06 | 1…1 | 15/15 | Required. Interchange sender identification mapping to fileSenderNumber with party type defined in ISA05. | 7777776067344 | ||||
| ISA07 | 1…1 | 2/2 |
Required. Interchange receiver partner ID qualifier.
|
01 | ||||
| ISA08 | 1…1 | 15/15 | Required. EDI receiver ID mapping to file control header and to ServiceLinkId. | 888888404358877 | ||||
| ISA09 | 1…1 | 6/6 | Required. Interchange date in 6 char YYMMDD format. | 250615 | ||||
| ISA10 | 1…1 | 4/4 | Required. Interchange time in 4 char HHMM format. | 1420 | ||||
| ISA11 | 1…1 | 1/1 |
Required. This value is dependent on X12 version.
|
^ | ||||
| ISA12 | 1…1 | 5/5 | Required. Interchange control version number. This could be any X12 version. | 00501 | ||||
| ISA13 | 1…1 | 9/9 | Required. Interchange Control Number mapping to file control header. | 0000000000619827 | ||||
| ISA14 | 1…1 | 1/1 |
Required. Interchange level acknowledgement requested. Valid values:
|
0 | ||||
| ISA15 | 1…1 | 1/1 |
Required. Indicates whether the interchange is for production, test, or information purposes. Valid values:
|
P | ||||
| ISA16 | 1…1 | 1/1 | Required. Component element separator. Delimiter that separates data elements within a composite data structure. Must be different than the data element separator and segment terminator. | > | ||||
| GS | 1…* | - | Required. GS group functional envelope. Child of ISA. Only one GS group expected per interchange. | - | ||||
| GS01 | 1…1 | 2/2 |
Required. GS group function code. Valid value is |
TX | ||||
| GS02 | 1…1 | 2/15 | Required. Application Sender's Code. | 2222224043588 | ||||
| GS03 | 1…1 | 2/15 | Required. Application Receiver's Code. | TRACELINK | ||||
| GS04 | 1…1 | 8/8 | Required. Current date stamp in 8 char X12 date format YYYYMMDD. | 20250615 | ||||
| GS05 | 1…1 | 4/8 | Required. Current time stamp in 6 char X12 time format HHMMSS. | 142000 | ||||
| GS06 | 1…1 | 1/9 | Required. Group Control ID Number. | 619827 | ||||
| GS07 | 1…1 | 1/2 |
Required. Responsible Agency Code. Valid values:
|
X | ||||
| GS08 | 1…1 | 1/12 | Required. X12 message version code. This could be any X12 version. | 005010 | ||||
| ST | 1…* | - | Required. ST transaction set envelope. Child of GS group. Only one ST transaction expected. | - | ||||
| ST01 | 1…1 | 3/3 | Required. Transaction set identifier code. | 864 | ||||
| ST02 | 1…1 | 4/9 | Required. Transaction set ID number. Counter for each ST segment beginning with 1. | 0001 | ||||
| BMG | 1…1 | - | Required. Text Message beginning segment. | - | ||||
| BMG01 | 1…1 | 2/2 |
Required. Transaction set purpose code. (missing or bad snippet) |
00 | ||||
| BMG02 | 0…1 | 1/80 | Description about the text message or purpose of text message. | Purchase Order change | ||||
| BMG03 | 0…1 | 2/2 |
Code specifying the type of transaction document supporting the message. (missing or bad snippet) |
03 | ||||
| DTM | 0…10 | - | Dates relevant to location events, provision given to map to EDIFACT data. | - | ||||
| DTM01 | 1…1 | 3/3 |
Required. Date type related to shipment events at port, in date format YYYYMMDD and time format (IDoc/ X12) HHMMSS.
|
069 | ||||
| DTM02 | 0…1 | 8/8 | Date defined by referenced date type in date format YYYY-MM-DD. Transform will pass thru whatever it finds in IDoc date and time fields. | 20241215 | ||||
| DTM03 | 0…1 | 4/8 | Time expressed in 24-hour clock time as follows. | 161025 | ||||
| DTM04 | 0…1 | 2/2 | Time zone for referenced dates. | ES | ||||
| DTM05 | 0…1 | 2/3 |
Describes the date format, time format, or date and time period format type.
|
DT | ||||
| DTM06 | 0…1 | 1/35 | Describes the date format, time format, or date and time period. | - | ||||
| N1 | 0…200 | - | Required. N1 segment loop at header for party address and location information. | - | ||||
| N101 | 1…1 | 2/3 |
Required. Entity qualifier for the Customer or Buyer party identifier and address information.
|
SU | ||||
| N102 | 0…1 | 1/60 | Required. Name | Pharma customer | ||||
| N103 | 0…1 | 1/2 |
Required. Identifier code qualifier. Valid values:
|
UL | ||||
| N104 | 0…1 | 2/80 | Required. Buyer party identifier as qualified by N103 mapping to companyIdentifierValue. | 3333331013655 | ||||
| N3 | 0…1 | - | N3: Address: Child of customer party N1 name segment. | - | ||||
| N301 | 1…1 | 1/55 | Required. Street address 1. | 555 Neelan Road | ||||
| N302 | 0…1 | 1/55 | Street address 2. | Suite 123 | ||||
| N4 | 0…1 | - | N4: Geographic Location. Child of customer party N1 name segment. | - | ||||
| N401 | 0…1 | 2/30 | City name. | Sacramento | ||||
| N402 | 0…1 | 2/2 | State or province code. Code (Standard state/province) as defined by appropriate government agency. | CA | ||||
| N403 | 0…1 | 3/15 | Postal code. Code defining international postal zone code excluding punctuation and blanks. | 95833 | ||||
| N404 | 0…1 | 2/3 | Country code. | US | ||||
| N405 | 0…1 | 1/2 | Type of location. | CA | ||||
| N406 | 0…1 | 1/30 | Specific location. | 95833 | ||||
| N407 | 0…1 | 1/3 | Country subdivision. | US | ||||
| REF | 0…12 | - | REF segment to specify instructions for business relationship or a reference number. | - | ||||
| REF01 | 1…1 | 2/3 |
Required. Code qualifying the Reference Identification.
|
PO | ||||
| REF02 | 0…1 | 1/80 | Required. Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier. | 45892345 | ||||
| REF03 | 0…1 | 1/80 | A free-form description to clarify the related data elements and their content. | - | ||||
| PER | 0…3 | - | Contact Information. | - | ||||
| PER01 | 1…1 | 2/2 |
Required. Contact function code identifying major duty or responsibility of person or group named as contact. Valid value:
|
IC | ||||
| PER02 | 0…1 | 1/60 | Required. Name of the contact person responsible for authenticating the pedigree information. | John Smith | ||||
| PER03 | 0…1 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:
|
TE | ||||
| PER04 | 0…1 | 1/2048 |
Communication number:
|
+1.516.747.6849 | ||||
| PER05 | 0…1 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:
|
EM | ||||
| PER06 | 0…1 | 1/2048 |
Communication number:
|
jsmith@manufac.com | ||||
| MIT | 1…* | - | Required. Line item loop start for text message, referring a line number in a transaction set. | - | ||||
| MIT01 | 1…1 | 1/80 | Required. Transaction reference identifier value or message number as defined by enum in transactionReferenceType. | ABCD4567321 | ||||
| MIT02 | 0…1 | 1/80 | Description about the text message or purpose of text message. | Purchase Order change | ||||
| MIT03 | 0…1 | 1/3 | Maximum number of characters per line, expected in the message text. | 20 | ||||
| MIT04 | 0…1 | 1/3 | Maximum number of lines per page, expected in the message text. | 105 | ||||
| N1 | 0…200 | - | Required. N1 segment loop at line item for party address and location information. | - | ||||
| N101 | 1…1 | 2/3 |
Required. Entity qualifier for the Customer or Buyer party identifier and address information.
|
SU | ||||
| N102 | 0…1 | 1/60 | Required. Name | Pharma customer | ||||
| N103 | 0…1 | 1/2 |
Required. Identifier code qualifier. Valid values:
|
UL | ||||
| N104 | 0…1 | 2/80 | Required. Buyer party identifier as qualified by N103 mapping to companyIdentifierValue. | 3333331013655 | ||||
| N3 | 0…1 | - | N3: Address: Child of customer party N1 name segment. | - | ||||
| N301 | 1…1 | 1/55 | Required. Street address 1. | 555 Neelan Road | ||||
| N302 | 0…1 | 1/55 | Street address 2. | Suite 123 | ||||
| N4 | 0…1 | - | N4: Geographic Location. Child of customer party N1 name segment. | - | ||||
| N401 | 0…1 | 2/30 | City name. | Sacramento | ||||
| N402 | 0…1 | 2/2 | State or province code. Code (Standard state/province) as defined by appropriate government agency. | CA | ||||
| N403 | 0…1 | 3/15 | Postal code. Code defining international postal zone code excluding punctuation and blanks. | 95833 | ||||
| N404 | 0…1 | 2/3 | Country code. | US | ||||
| N405 | 0…1 | 1/2 | Type of location. | CA | ||||
| N406 | 0…1 | 1/30 | Specific location. | 95833 | ||||
| N407 | 0…1 | 1/3 | Country subdivision. | US | ||||
| REF | 0…12 | - | REF segment to specify instructions for business relationship or a reference number. | - | ||||
| REF01 | 1…1 | 2/3 |
Required. Code qualifying the Reference Identification. (missing or bad snippet) |
PO | ||||
| REF02 | 0…1 | 1/80 | Required. Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier. | 45892345 | ||||
| REF03 | 0…1 | 1/80 | A free-form description to clarify the related data elements and their content. | - | ||||
| PER | 0…3 | - | Contact Information. | - | ||||
| PER01 | 1…1 | 2/2 |
Required. Contact function code identifying major duty or responsibility of person or group named as contact. Valid value:
|
IC | ||||
| PER02 | 0…1 | 1/60 | Required. Name of the contact person responsible for authenticating the pedigree information. | John Smith | ||||
| PER03 | 0…1 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid value:
|
TE | ||||
| PER04 | 0…1 | 1/2048 |
Communication number
|
+1.516.747.6849 | ||||
| PER05 | 0…1 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid value:
|
EM | ||||
| PER06 | 0…1 | 1/2048 |
Communication number:
|
jsmith@manufac.com | ||||
| MSG | 0…* | - | To provide a free-form format that allows the transmission of text information. | - | ||||
| MSG01 | 1…1 | 1/264 | Required. Free-form message text | ABCD4567321 | ||||
| MSG02 | 0…1 | 2/2 | A field to be used for the control of the line feed of the receiving printer. | SS | ||||
| MSG03 | 0…1 | 1/9 | A generic number. | - | ||||
| SE | 1…1 | - | Required. ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected. | - | ||||
| SE01 | 1…1 | 1/10 | Required. Total count of segments in ST … SE transaction set including ST and SE segments. | 10 | ||||
| SE02 | 1…1 | 4/9 | Required. Transaction set control number. | 0001 | ||||
| GE | 1…1 | - | Required. GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected. | - | ||||
| GE01 | 1…1 | 1/6 | Required. Number of transaction sets in functional group. | 5 | ||||
| GE02 | 1…1 | 1/9 | Required. Functional group control number. | 619827 | ||||
| IEA | 1…1 | - | Required. ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission. | - | ||||
| IEA01 | 1…1 | 1/5 | Required. Number of functional groups in interchange. | 1 | ||||
| IEA02 | 1…1 | 9/9 | Required. Interchange control number. | 0000000000619827 | ||||
ISA*00*ISA0210100*00*ISA0410100*07*7777776067344 *01*888888404358877*250612*1332*U*00401*000619827*0*P*:~
GS*IO*2222224043588*TRACELINK*20250611*142000*619827*X*004010~
ST*864*0001~
BMG*00*Purchase Order change*03~
DTM*069*20251202*141140*ES*DT*test~
N1*SU*SU_name*UL*SU_123~
N3*Address1_SU*Address2_SU~
N4*city_SU*MP*909090*IND*CA*97533*US~
REF*SI*SI_Value*SI_desc~
PER*IC*IC_name*EM*Email@gmail.com*TE*1234548~
MIT*ABCD4567321*Purchase Order change*20*105~
N1*CA*CA_name*UL*BY_1256~
N3*Address1_CA*Address2_CA~
N4*CityCA*CA*CA_12361*IND*SB*84*US~
REF*SI*SI_Value*descPO~
PER*IC*IC_1270*EM*email@yahoo.com*TE*1234574~
MSG*ABC*AA*12~
SE*206*s207~
GE*208*209~
IEA*210*s211sssss~
Tag end


