iaiilli PUBUCATIONS

Nisr

QC

100

.U57

NO.881-19

NIST Special Publication 881-19

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 864

Text Message

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

NIST Special Publication 881-19

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 864

Text Message

Implementation Convention

Electronic Commerce Acquisition Program Management Office

Standard Management Committee - Secretariat

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Editor: Dr. Jean-Philippe Favreau

March 1997

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Mary L. Good, Under Secretary for Technology

National Institute of Standards and Technology

Arati Prabhakar, Director
Reports on Information Technology

The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL)

develops standards and guidelines, provides technical assistance, and conducts research for computers

and resources. As part of the overall federal effort to establish a single face to industry for conducting

electronic commerce, ITL has been designated as the organization responsible for coordinating the

development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are

defined by functional-area experts who create and select options from standard EDI Transaction Sets to

yield the implementations to be used for practical EDI. These ICs are made available to federal agencies

and industry by electronic means and this Special Publication Series.

National Institute of Standards and Technology Special Publication 881-19

Natl. Inst. Stand. Technol. Spec. Publ. 881-19, 14 pages (March 1997)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1997

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
864 Text Message

Functional Group ID=TX

Introduction:

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.

Heading:

Pos. No. 010

See. ID

ST

020 BMG

VjjV U 1 M

040 Nl

N/U 050 N2

N/U 060 N3

NAJ 070 N4

080 REF

090 PER

Detail:

Pos. No.Seg.

ID

010 MIT

NAJ 020 Nl

NAJ 030 N2

NAJ 040 N3

NAJ 050 N4

NAJ 060 REF

NAJ 070 PER

080 MSG

Req.

Name

Transaction Set Header

Des. MMax.Use

1

Beginning Segment For Text Message M 1

Date/Time/Period O 10

i

Name 0 1

Additional Name Information O 2

Address Information O 2

Geographic Location O 1

Reference Numbers O 12

Administrative Communications Contact O 3

Loop

Repeat

Notes and

Comments

Name

Req.

Des.

Name

Additional Name Information

Address Information

Geographic location

Reference Numbers

Administrative Communications Contact

O

O

o

o

o

o

1

2

2

1

12

3

Message Text M 100000

Summary:

Pos. No. 010Seg.

ID

SE

Name

Transaction Set Trailer

Req.

Des. M

Mai.Use

1

Loop

Repeat

Notes and

Comments

RELEASE - 003040FED00A 31 August 1994
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST

010

Transaction Set Header

Heading

Mandatory

1To indicate the start of a transaction set and to assign a control number

1 The transaction set identifier (STO 1) used by the translation routines of the

interchange partners to select the appropriate transaction set definition (e.g., 810

selects the Invoice Transaction Set).

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use STOl 143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

864 X12.34 Text Message

Must Use STOl 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 A unique number assigned to this transaction setfor control purposes.

Usually assigned by the translation software. This is the same number that

appears in the SE02.

RELEASE - 003040FED00A 2 31 August 1994
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

BMG Beginning Segment For Text Message

020

Heading

Mandatory

1To indicate the beginning of a Text Message Transaction Set

1 BMG02 contains the message subject.

Ref.

Pes.

Must Use BMGOl

BMG02

Data

Element

353

Data Element Summary

Name Attributes

Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set 00 Original

Use to indicate an original transmittal.

Cancellation

Use to indicate the cancellation ofa previously

transmitted message text. Duplicate

use to indicate the re-transmission ofa previously

transmitted text information.

O AN 1/80

A free-form description to clarify the related data elements and their content

Use to provide a briefoverall subject ofthe text message.

01

07

352 Description

RELEASE - 003040FED00A 3 31 August 1994
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

DTM Date/Time/Period

030

Heading

Optional

10

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

Ref.

Pes.

Must Use DTMOl

DTM02

Data Element Summary

Data

Element Name

374

373

Attributes

Date/Time Qualifier M ID 3/3

Code specifying type of date or time, or both date and time

097 Transaction Creation

Use to indicate the date the transaction set was

created.

Date X DT 6/6

Date (YYMMDD)

RELEASE - 003040FED00A 4 31 August 1994
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Nl Name

040

Nl

Heading

Optional

1To identify a party by type of organization, name, and code

1 At least one of N102 or N103 is required.

2 If either N103 or N104 is present, then the other is required.

1 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.

2 N105 and N106 further define the type of entity in NlOl.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use NlOl 98 Entity Identifier Code M ID 2/2

Code identifying an organizational entity, a physical location, or an individual

FR Message From

TO Message To

N103 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

1 D-U-N-S Number, Dun & Bradstreet

Use when NlOl cites code FR to cite a contractor

originating a text message. Use also when NlOl cites

code TO to cite a Federal Agency known by its DUNS

number.

10 Department of Defense Activity Address Code

(DODAAC)

Use when a Federal Agency is known only by its DoDAAC or Civilian Agency Activity adress Code

when NlOl cites either code FR or TO. Use ofthe

DUNS number is preferred.

N104 67 Identification Code X AN 2/17

Code identifying a party or other code

RELEASE - 003040FED00A 5 31 August 1994
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Numbers

080

Nl

Heading

Optional

12

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

1. Use to identify a transaction set to which the text message applies.

2. Use also to provide a unique reference numberfor this transaction set.

3. There must be at least 2 occurrences ofthis REF segment with code TN andME

cited in REFOl to identify the unique reference number ofthe transaction set to which

this message applies and to identify this transaction set

Must Use

Ref.

Pes.

REFOl

REF02

Data

Element

128

127

Data Element Summary

Name Attributes

Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

ME Message Address or ID

Use to indicate the unique reference number ofthis

transaction set When this 864 transaction set refers to another 864 transaction set, use another iteration of

the REF segment with code TN to identify the other

864 transaction set. TN Transaction Reference Number

Use to indicate the unique reference number ofthe

transaction set to which this text message applies. Cite

the reference number in the REF02 and identify the

transaction set in REF03.

W7 Commercial and Government Entity (CAGE) Code

Use, as applicable, to identify the code ofa party other

than a Federal Agency, either originating or receiving

the text message.

Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

1. When transmitting the unique reference number ofan 810 transaction set,

cite the number in BIG02 ofthe 810 transaction set

2. When transmitting the unique reference number ofan 820 transaction set,

cite the number in the TRN02 ofthe 820 transation set that is qualified by

code 1 in TRNOl.

3. When transmitting the unique reference number ofan 824 transaction set,

cite the number in the BGN02 ofthe 824 transaction set.

4. When transmitting the unique reference number ofan 832 transaction set,

cite the number in teh BCT02 ofthe 832 transaction set

RELEASE - 003040FED00A

5. When transmitting the unique reference number ofan 836 transaction set,

cite the number in the ECO10 ofthe 836 transaction set

6 31 August 1994
864 - Text Message

6. When transmitting the unique reference number ofan 838 transaction set,

cite the number in the BTP02 ofthe 838 transaction set.

7. When transmitting the unique reference number ofan 840 transaction set,

cite the number in the BQT02 ofthe 840 transaction set.

8. When transmitting the unique reference number ofan 841 transaction set,

cite the number in the SPI02 ofthe 841 transaction set.

9. When transmitting the unique reference number ofan 843 transaction set,

cite the number in the REF02 (l/REF/050) ofthe 843 transaction set that is qualified by code PR in REFOl.

10. When transmitting the unique reference number ofan 850 transaction set,

cite the number in BEG03 ofthe 850 transaction set. Ifa number is cited in

both BEG03 adn BEG04 ofthe 850 transaction set, concatencate these

numbers.

11. When transmitting the unique reference number ofan 855 transaction set,

cite the number in BAK03 ofthe 855 transaction set.

12. When transmitting the unique reference number ofan 856 transaction set,

cite the number in BSN02 ofthe 856 transaction set

13. When transmitting the unique reference number ofan 864 transaction set,

cite the number in REF02 (l/REF/080) ofthe 864 transaction set that is qualified by code ME in REFOl.

REF03 352 Description X AN 1/80

A free-form description to clarify the related data elements and their content

Use to identify the transaction set applicable to the unique reference number

cited in REF02, e.g. 810 Invoice (Commercial Invoice) transaction set, 838

Trading Partner Profile (Registration) transaction set, etc.

RELEASE - 003040FED00A 7 31 August 1994
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

PER Administrative Communications Contact

090

Nl

Heading

Optional

3

To identify a person or office to whom administrative communications should be

directed

1 If either PER03 or PER04 is present, then the other is required.

2 If either PER05 or PER06 is present, then the other is required.

Must Use

Ref.

Pes.

PEROl

PER02

PER03

PER04

PER05

Data

Element

366

93

365

364

365

PER06

RELEASE - 003040FED00A

364

Data Element Summary

Name Attributes

Contact Function Code M ID 2/2

Code identifying the major duty or responsibility of the person or group

named

IC Information Contact

Use to indicate a point ofcontactfor this transaction

set

Name O AN 1/35

Free-form name

Cite the last namefollowed by the first name. Do not truncate the last name

ifthe whole is greater than 35 characters. Instead, truncate the first name or

use the initial ofthe first name. Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

ED Electronic Data Interchange Access Nimiber

EM Electronic Mail

FX Facsimile

IT International Telephone

Inlcude country code.

TE Telephone

Use to indicate the commercial telephone number of

the namedparty.

Communication Number X AN 1/80

Complete communications number including coimtry or area code when

applicable

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

ED Electronic Data Interchange Access Nimiber

EM Electronic Mail

FX Facsimile

IT International Telephone

Include country code.

TE Telephone

Use to indicate the commercial telephone number of

the namedparty.

Communication Number X AN 1/80

Complete communications number including country or area code when

8 31 August 1994
864 - Text Message

applicable

RELEASE - O03040FEDO0A
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

MIT Message Identification

010

MIT

Detail

Mandatory

1To identify the beginning of a specific message and to allow the identification of a

subject for the message

1 MTTOl contains the message number.

2 MIT02 contains the message subject. 1 MIT03 default is 80 characters.

2 MIT04 default is 66 lines. Use this segment to identify a more detailed subject ofthis text message.

Ref.

Pes.

Must Use MITOl

MIT02

Data

Element

127

352

Data Element Summary

Name Attributes

Reference Number M AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

A unique number assigned by the originator ofthe message to identify

multiple messages contained within this transaction set. For example, the

number 001 can be used to refer to a message with the subject Packing

Requirements, cited in MIT02 and the number 002 can be used in another

iteration ofthis MIT segment to identify a second message with the subject

Testing Procedures.

Description O AN 1/80

A free-form description to clarify the related data elements and their content

Use to provide a more detailed subject ofthe message.

RELEASE - 003040FED00A 10

I

31 August 1994 I
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

MSG Message Text

080

MIT

Detail

Mandatory

100000

To provide a free form format that would allow the transmission of text information.

1 MSG02 is not related to the specific characteristics of a printer, but identifies top of

page, advance a line, etc. Use full 264 character capability ofdata element 933 (MSGOl) unless specifically

advised by the trading partner to limit length ofany one iteration ofthe segment to 80

characters.

Ref.

Pes.

Must Use MSGOl

Data Element Summary

Data

Element Name

933 Free-Form Message Text

Free-form message text

Attributes

M AN 1/264

RELEASE - 003040FEDOOA 11 31 August 1994
864 - Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

010

Summary

Mandatory

1To indicate the end of the transaction set and provide the count of the transmitted

segments (including the beginning (ST) and ending (SE) segments).

SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use SEOl 96 Number of Included Segments M NO 1/10

Total number of segments included in a transaction set including ST and SE

segments

Must Use 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 Cite the same number as the one in the ST02.

RELEASE - 003040FED00A 12 31 August 1994


Technical Publications

Periodical

Journal of Research of the National Institute of Standards and Technology—Reports NIST research

and development in those disciplines of the physical and engineering sciences in which the Institute is

active. These include physics, chemistry, engineering, mathematics, and computer sciences. Papers cover a broad range of subjects, with major emphasis on measurement methodology and the basic technology

underlying standardization. Also included from time to time are survey articles on topics closely related to the Institute's technical and scientific programs. Issued six times a year.

Nonperiodicals

Monographs—Major contributions to the technical literature on various subjects related to the

Institute's scientific and technical activities. Handbooks—Recommended codes of engineering and industrial practice (including safety codes) developed in cooperation with interested industries, professional organizations, and regulatory bodies.

Special Publications—Include proceedings of conferences sponsored by NIST, NIST annual reports, and

other special publications appropriate to this grouping such as wall charts, pocket cards, and bibliographies.

National Standard Reference Data Series—Provides quantitative data on the physical and chemical

properties of materials, compiled from the world's literature and critically evaluated. Developed under a worldwide program coordinated by NIST under the authority of the National Standard Data Act (Public

Law 90-396). NOTE: The Journal of Physical and Chemical Reference Data (JPCRD) is published

bimonthly for NIST by the American Chemical Society (ACS) and the American Institute of Physics (AIP).

Subscriptions, reprints, and supplements are available from ACS, 1155 Sixteenth St., NW, Washington, DC

20056.

Building Science Series—Disseminates technical information developed at the Institute on building

materials, components, systems, and whole structures. The series presents research results, test methods, and

performance criteria related to the structural and environmental functions and the durability and safety

characteristics of building elements and systems.

Technical Notes—Studies or reports which are complete in themselves but restrictive in their treatment of

a subject. Analogous to monographs but not so comprehensive in scope or definitive in treatment of the

subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of

other government agencies.

Voluntary Product Standards—Developed under procedures published by the Department of Commerce

in Part 10, Title 15, of the Code of Federal Regulations. The standards establish nationally recognized

requirements for products, and provide all concerned interests with a basis for common understanding of

the characteristics of the products. NIST administers this program in support of the efforts of private-sector

standardizing organizations.

Order the following NIST publications—FIPS and NISTIRs—from the National Technical Information

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FIPS PUB)—Publications in this series

collectively constitute the Federal Information Processing Standards Register. The Register serves as the

official source of information in the Federal Government regarding standards issued by NIST pursuant to the Federal Property and Administrative Services Act of 1949 as amended. Public Law 89-306 (79 Stat. 1127), and as implemented by Executive Order 11717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTIR)—A special series of interim or final reports on work performed by

NIST for outside sponsors (both government and nongovernment). In general, initial distribution is handled

by the sponsor; public distribution is by the National Technical Information Service, Springfield, VA 22161,

in paper copy or microfiche form.
o =3

O 00

o

o

I 0\

0\

00o

5 t>a

• ^ M—

I

p 2 g a o

o

5 C O 3 - — „ j= lid