Text Message 864


Documentation

M&M MSG 864

M&M/MARS

 

864 Text Message 
 

Functional Group ID=TX

 
Introduction: 
 
This MARS Inc. Standard 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. 
 
Notes: 
 

* is used as a data delimiter to separate and maintain element position.
MARS Inc. will send selected qualifiers that have been approved for use in this version of the EDI Standards.
Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M 010 ST Transaction Set Header M 1
M 020 BMG Beginning Segment For Text Message M 1
030 DTM Date/Time Reference O 10
LOOP ID - N1 200
040 N1 Name O 1
070 N4 Geographic Location O 1
080 REF Reference Identification O 12
090 PER Administrative Communications Contact O 3
Detail:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
LOOP ID - MIT >1
M 010 MIT Message Identification M 1
M 080 MSG Message Text M 100000
Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M 010 SE Transaction Set Trailer M 1

Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Notes: Example: 
 
ST*864*1000000100001 
 
The Transaction Set Identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition. 
 
864 is the code used to identify the Text Message Transaction Set.

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M ST01 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
864    Text Message
M ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
ST Control Number must be the same as the Control Number (SE02) in the SE Segment.

Segment: BMG Beginning Segment For Text Message
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of a Text Message Transaction Set

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M BMG01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set

Segment: DTM Date/Time Reference
Position: 030
Loop:
Level: Heading
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times
Notes: Example: 
 
DTM**20000129

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
DTM02 373 Date X DT 8/8
Date expressed as CCYYMMDD

Segment: N1 Name
Position: 040
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Notes: Example: 
 
N1*BY*NAME

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M N101 98 Entity Identifier Code M ID 2/3
Code identifying an organizational entity, a physical location, property or an individual
BT    Bill-to-Party
BY    Buying Party (Purchaser)
FR    Message From
N102 93 Name X AN 1/60
Free-form name

Segment: N4 Geographic Location
Position: 070
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To specify the geographic place of the named party
Notes: Example: 
 
N4*Hackettstown*NJ

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
N401 19 City Name O AN 2/30
Free-form text for city name
N402 156 State or Province Code O ID 2/2
Code (Standard State/Province) as defined by appropriate government agency

Segment: REF Reference Identification
Position: 080
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 12
Purpose: To specify identifying information
Notes: Example: 
 
REF*IK*122123

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M REF01 128 Reference Identification Qualifier M ID 2/3
Code qualifying the Reference Identification
IK    Invoice Number
Manufacturer's invoice number for vehicle/component
REF02 127 Reference Identification X AN 1/30
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Segment: PER Administrative Communications Contact
Position: 090
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 3
Purpose: To identify a person or office to whom administrative communications should be directed
Notes: Example: 
 
PER*ZZ*M&M/MARS*TE*122123

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of the person or group named
PER02 93 Name O AN 1/60
Free-form name
PER03 365 Communication Number Qualifier X ID 2/2
Code identifying the type of communication number
TE    Telephone
PER04 364 Communication Number X AN 1/80
Complete communications number including country or area code when applicable

Segment: MIT Message Identification
Position: 010
Loop: MIT Mandatory
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To identify the beginning of a specific message and to allow the identification of a subject for the message
Notes: Example: 
 
MIT*012*M&M/MARS

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M MIT01 127 Reference Identification M AN 1/30
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
MIT02 352 Description O AN 1/80
A free-form description to clarify the related data elements and their content

Segment: MSG Message Text
Position: 080
Loop: MIT Mandatory
Level: Detail
Usage: Mandatory
Max Use: 100000
Purpose: To provide a free-form format that allows the transmission of text information
Notes: Example: 
 
MSG*Message Text

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M MSG01 933 Free-Form Message Text M AN 1/264
Free-form message text

Segment: SE Transaction Set Trailer
Position: 010
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Notes: Example: 
 
SE*32*10012

 
Data Element Summary 

Ref. Data
Des. Element Name Attributes
M SE01 96 Number of Included Segments M N0 1/10
Total number of segments included in a transaction set including ST and SE segments
M SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

 

M&M/Mars Txt Msg Set: 864 Version 4010 X12 June 28, 2000

Back     Home