NAT'L INST. OF STAND & TECH R.I.C

NIST

A111DS PUBLICATIONS

i

*M

iijiiitiiii

imiimii 1 1 1

1

1::

nist

QC

100

.U57

NO.881-14

1997

NIST Special Publication 881-14

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 864

Text Message

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

NIST Special Publication 881-14

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 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-14

Natl. Inst. Stand. Technol. Spec. Publ. 881-14, 21 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
FOREWORD

In a memorandum of October 26, 1993, the President sought to stimulate the Federal Government's deployment of

Electronic Commerce in order to simplify and streamline the acquisition process. In this regard, the President set forth the following objectives:

o Exchange acquisition information electronically between the private sector and the Federal Government to the

maximum extent practicable.

o Provide businesses, including small, small disadvantaged, and woman-owned businesses, with greater access to Federal acquisition opportunities.

o Ensure that potential suppliers are provided simplified access to the Federal Government's EC system.

o Employ nationally and internationally recognized data formats that serve to broaden and ease the interchange of

data.

o Use agency and industry systems and networks to enable the government and potential suppliers to exchange

information and access Federal acquisition data.

As part of the Federal Government wide effort to implement EC, NIST has been given the responsibility of coordinating

the development and promulgation of Implementation Conventions for the functional areas of EC which will be deployed

across the Agencies.

Various Agencies have been actively pursuing Electronic Data Interchange (EDI) for several years - the DoD, GSA,

Customs and HHS, for instance, have been particularly active in adopting ANSI X12 standards, and looking ahead to EDIFACT. There became a danger that with fragmentation of usage across the Federal Government a significant burden

would be placed on many small businesses to support an unnecessary prolusion offormats and conventions.

In the Presidential Memorandum, President Clinton required Federal agencies to implement the use of electronic commerce in Federal purchases as quickly as possible. As the initial step, the President's Management Council (PMC)

Electronic Commerce Task Force (ECTF), chaired by the Administrator, Office of Federal Procurement Policy (OFPP),

chartered the Federal Electronic Commerce Acquisition Team (ECAT) to complete the first milestone of the President's

memorandum. The PMC assigned the Electronic Commerce Acquisition Team, composed of representatives from

various Federal departments and agencies, the task of defining the architecture for the government electronic commerce

acquisition system and identifying the executive departments or agencies responsible for developing, implementing,

operating, and maintaining the Federal electronic system.

Another key step in the implementation of EDI in the Federal Government relies on the definition of

Implementation Conventions (ICs). EDI syntax standards, both ASC X12 and UN/EDIFACT, accommodate a full range of business activities for all industries. A standard is the result of a consensus among a large number of

users, each with its own set of needs. It is a superset intended to meet the diverse requirements of all users. Standards commonly contain more data elements and structure options than any one user or industry needs. Far

too many opportunities exist for inefficient, or ambiguous transactions. Therefore, actual EDI business processes

require implementation conventions (ICs) to fully define transactions. ICs do that by tailoring the use of the

standards' segments, data elements, and code values and providing a subset menu of those distinct parts. This

Special Publication defines a Federal IC based on ASC X12 Version 3050 and is the result of coordinated

development and adoption within the Federal Government.

864 -Text Message

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.

Notes:

/. This transaction set can be used by private industry andfederal agencies to exchange text information

(questions, clarifications, data, etc.) relating to solicitations, proposals, awards, invoices, material safety

data sheets, etc.

2. When used in conjunction with another transaction set, e.g., an 843 Response to Requestfor

Quotation, the unique reference number ofthe related transaction set must be cited in the l/REF/080

segment.

Heading:

Detail:

Pos. Seg. Req. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

010 ST Transaction Set Header M 1

020 BMG Beginning Segment For Text Message M 1

030 DTM Date/Time Reference

logp7d~-n1

' O 10 200~

040 Nl Name O 1

050 N2 Additional Name Information o 2

060 N3 Address Information o 2

070 N4 Geographic Location o 1

080 REF Reference Numbers o 12

090 PER Administrative Communications Contact o 3

Pos. Seg. Req. Loop Notes and

No. IS Name Pes. Max.Use Repeat Comments

003050FED01A 20 FEB 1997
864 -Text Message

Must Use 010

N/U 020

N/U 030

N/U 040

N/U 050

N/U 060

N/U 070

Must Use 080

Summary:

Pos. No. Must Use 010

LOOP1D-MJT

MIT Message Identification M 1

Nl

LOOP ID -Nl

Name O 1

200

N2 Additional Name Information O 2 N3 Address Information o 2 N4 Geographic Location o 1 REF Reference Numbers o 12 PER Administrative Communications Contact o 3 MSG Message Text M 100000

Seg. Req. Loop Notes and

ID Name Pes. Max.Use Repeat Comments

SE Transaction Set Trailer M 1

003050FED01A 2 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Heading

Mandatory

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

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

Data Element Summary

Ref. Data

Pes. Element Name Attributes

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

Code uniquely identifying a Transaction Set

864 X 1 2.34 Text Message

Must Use 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 Use to transmit a unique number assigned by the originator ofthe

transaction set. The number may be system generated. This same

number will be cited in SE02.

003050FED01A 3 20 FEB 1997
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 BMG01

BMG02

N/U BMG03

Data Element Summary

Data

Element Name

353 Transaction Set Purpose Code

Code identifying purpose of transaction set

00

640

Attributes

M ID 2/2

01

07

11

Original

Use to indicate an original transmittal

Cancellation

Use to indicate the cancellation ofa previously

transmitted text message.

Duplicate

Use to indicate the re-transmission of a previously

transmitted text message.

Response

Use to indicate a reply to an 864 transaction set. When used, cite code TN in REF01 ofthe

l/REF/080 segment and identify the unique

number ofthe 864 transaction set to which this

transaction set is responding in REF02.

Information Copy

Use to indicate an information copy ofthe original

text message. This information copy may be sent

to parties other than thosefor whom the original is

intended.

O AN 1/80

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

content

Use to provide a brief, overall subject ofthe text message.

Transaction Type Code O ID 2/2

Code specifying the type of transaction

22

352 Description

1

003050FED01A 4 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

DTM Date/Time Reference

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 DTM01

DTM02

DTM03

N/U DTM04

N/U

N/U

N/U

DTM05

DTM06

DTM07

Data

Element

374

373

337

623

624

1250

1251

Data Element Summary

Name 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)

Time X TM 4/8

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)

Time is always expressed as local time.

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an

indication in hours in relation to Universal Time Coordinate (UTC) time;

since + is a restricted character, + and - are substituted by P and M in the

codes that follow

Century O NO 2/2

The first two characters in the designation of the year (CCYY)

Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003050FED01A 5 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

040

Nl

Heading

Optional

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

1 At least one of N 1 02 or N1 03 is required.

2 If either N1 03 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 N101.

/. Whenever possible, identification and address information should be provided

using N101, N103, and N104. Use N102 and segments N2 through N4, as

applicable, when the address cannot be provided using one ofthe codes listed in

N103.

2. There must be two iterations ofthe Nl loop. One iteration will be used to

identify the party sending the message and the second iteration to identify the

party to whom the text message is being sent.

Ref.

Pes.

Must Use N101

N102

N103

Data Element Summary

Data

Element Name Attributes

98 Entity Identifier Code M ID 2/2

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

individual

FR Message From

Use to indicate the party sending the text message.

TO Message To

Use to indicate the party to whom the text message

transaction set is being sent.

93 Name X AN 1/35

Free-form name

66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for

Identification Code (67)

While thefederal EDIprogram uses the DUNS number, other

government users ofthis implementation convention may require the use of other and additional numbersfor a transition period in order to

cross reference existing data bases to newprocurement actions.

003050FED01A 6 20 FEB 1997
864 -Text Message

N/U

N/U

N104

N105

N106

10

21

33

46

A2

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

tfo? DUNS or DUNS+4 number is preferred

over other codes to identify an entity.

D-U-N-S+4, D-U-N-S Number with Four Character

Suffix

Use ofthe DUNS or DUNS+4 number is preferred

over other codes to identify an entity.

Department of Defense Activity Address Code

(DODAAC)

Use to indicate either a Department ofDefense or

Civilian Agency Activity Address Code.

Health Industry I.D. Number (HIN)

Commercial and Government Entity (CAGE)

Electronic Transmitter Identification Number (ETIN)

A unique number assigned to each transmitter and

software developer

Military Assistance Program Address Code (MAPAC)

Contained in the Military Assistance Program

Address Directory (MAPAD); represents the

location of an entity

Employee Idenfication Number

Facility Identification

This code will be deleted if a business case is not

identifiedfor its continued use.

Federal Taxpayer's Identification Number

Medicaid Provider Number

Number assigned to a health care provider for

submitting claims covered by medicaid benefits

Medicare Provider Number

Number assigned to a health care provider for

submitting claims covered by Medicare benefits

Medicaid Recipient Identification Number

Unique identification number assigned to each

member covered under a subscriber's contract

67 Identification Code X AN 2/20

Code identifying a party or other code

706 Entity Relationship Code O ID 2/2

Code describing entity relationship

98 Entity Identifier Code O ID 2/2

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

individual

EI

FA

FI

MC

MP

MR

003050FED01A 7 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

N2 Additional Name Information

050

Nl

Heading

Optional

2

To specify additional names or those longer than 35 characters in length

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use N201 93 Name M AN 1/35

Free-form name

N202 93 Name O AN 1/35

Free-form name

003050FED01A 8 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

N3 Address Information

060

Nl

Heading

Optional

2

To specify the location of the named party

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use N301 166 Address Information M AN 1/35

Address information

N302 166 Address Information O AN 1/35

Address information

003050FED01A 9 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

N4 Geographic Location

070

Nl

Heading

Optional

1To specify the geographic place of the named party

1 If N406 is present, then N405 is required.

1 A combination of either N401 through N404, or N405 and N406 may be

adequate to specify a location.

2 N402 is required only if city name (N401) is in the USA or Canada.

Data Element Summary

N/U

N/U

Ref.

Pes.

N401

N402

N403

N404

N405

N406

Data

Element Name

19

Attributes

City Name O AN 2/30

Free-form text for city name

156 State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate government

agency

116 Postal Code O ID 3/11

Code defining international postal zone code excluding punctuation and

blanks (zip code for United States)

26 Country Code O ID 2/3

Code identifying the country

309 Location Qualifier X ID 1/2

Code identifying type of location

310 Location Identifier O AN 1/30

Code which identifies a specific location

003050FED01A 10 20 FEB 1997
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 this segment to provide reference numbers that identify other transaction

sets or documents, e.g., contracts, invoices, progress payments, etc. to which this

transaction set applies.

2. At least 1 REF segment is required citing code ME in REF01.

3. When this transaction set is sent in conjunction with another transaction set,

e.g., an 840, the unique reference number ofthat transaction set must be cited in

REF02 with REF01 citing code TN. This is required to cross reference the

transaction sets.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use REF01 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

ANY CODE MA YBE USED to identify a document or some other

reference number to which the information transmitted in this

transaction set applies. Thefollowing is a preferred list ofcodes:

11 Account Number

12 Billing Account

14 Master A ccount Number

2F Consolidated In voice Number

2G Amendment

Includes modifications.

2S Catalog

2 Y Wage Determination

AW Air Waybill Number

BL Bill ofLading

Use to indicate either a commercial or Government Bill ofLading

C7 Contract Line Item Number

CT Contract Number

Use to indicate the purchase order number, contract number (including

003050FED01A 11 20 FEB 1997
864 -Text Message

Federal Supply Schedules, GSA Schedules and all other basic

contracts), BPA number, Grant, Lease or Agreement number. This is never the number of a delivery order, call or release against a basic

award instrument

IV Seller 's Invoice Number

KS Solicitation

ME Message Address or ID

Use to indicate the unique number ofthis transmission.

NR Progress Payment Number

PR Price Quote Number

RE Release Number

Use to indicate the number ofa release, call or delivery order against a

basic award instrument.

SI Shipper 's Identifying Numberfor Shipment (SID)

TN Transaction Reference Number

Use to indicate the unique number ofthe transaction set being

referenced in the instant text message. Each transaction set has a unique number assigned. Appendix A identifies where this unique

number is found in the more commonly used transaction sets. When

used, identify the transaction set number in REF03.

REF02 127 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.

REF03 352 Description X AN 1/80

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

content

1. Use tofurther identify, if necessary, the number cited in REF02.

2. When REF01 is code TN, the transaction set number to which the

number in REF02 applies MUST be identified in this data element.

003050FED01A 12 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

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.

3 If either PER07 or PER08 is present, then the other is required.

Use to indicate the name and/or communication numbersfor either an

information point ofcontact at the location where the transaction set was

originated, the contractor party certifying a requestfor a progress payment, or the

party who is to receive this transmission. When used, there must be provided

either a name, or a communication number, or both.

Data Element Summary

Ref.

Pes.

Must Use PER01

PER02

PER03

Data

Element Name

366

93

365

Attributes

Contact Function Code M ID 2/2

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

named

CE Certifier

Use to indicate the name and communication

number ofthe party who provided a certification.

IC Information Contact

Use to indicate the party at the senders location.

RE Receiving Contact

Use to indicate the party at the receiving location

who is to receive this transmission.

Name O AN 1/35

Free-form name

Cite last namefirst, followed byfirst name. Ifthe whole name is longer

than 35 characters, truncate or use initials forfirst name. If necessary, use PER09 to provide the party 's title

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

AU Defense Switched Network

Department of Defense telecommunications system

and successor of the Automatic Voice Network

(AUTOVON)

003050FED01A 13 20 FEB 1997
864 -Text Message

ED Electronic Data Interchange Access Number

EM Electronic Mail

FT Federal Telecommunications System (FTS)

FX Facsimile

IT International Telephone

Include the country code.

TE Telephone

Use to indicate the commercial telephone number

ofthe individual cited in PER02. Include the area

code.

PER04 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

PER05 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Use to identify a second communications numberfor the party cited in

PER02. For example, ifPER03/04 cites a telephone number, PER05/06

can be used to cite a FAX number.

AU Defense Switched Network

Department of Defense telecommunications system

and successor of the Automatic Voice Network

(AUTOVON)

ED Electronic Data Interchange Access Number

EM Electronic Mail

EX Telephone Extension

Use only ifPER03 is used citing code A U, FT, or TE.

FT Federal Telecommunications System (FTS)

FX Facsimile

IT International Telephone

Include the country code.

TE Telephone

Use to indicate the commercial telephone number

ofthe individual cited in PER02. Include the area

code.

PER06 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

PER07 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Use to identify a third communications numberfor the party cited in

PER02.

003050FED01A 14 20 FEB 1997
864 -Text Message

AU Defense Switched Network

Department of Defense telecommunications system

and successor of the Automatic Voice Network

(AUTOVON)

ED Electronic Data Interchange Access Number

EM Electronic Mail

EX Telephone Extension

Use only ifPEROS is used citing code A U, FT, or TE.

FT Federal Telecommunications System (FTS)

FX Facsimile

IT International Telephone

Include the country code.

TE Telephone

Use to indicate the commercial telephone number

ofthe individual cited in PER02. Include the area

code.

PER08 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

PER09 443 Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

Use, if necessary, to provide the title ofthe party cited in PER02.

003050FED01A 15 20 FEB 1997
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 MIT01 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 ofthe text message

Data Element Summary

Ref.

Pes.

Must Use MIT01

MIT02

N/U

N/U

MIT03

MIT04

Data

Element

127

352

931

932

Attributes

M AN 1/30

Name

Reference Number

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 transaction set 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 Packaging Requirements cited in MIT02; the number 002 can

be used in another iteration ofthis MITsegment to identify a second

message with the subject, Testing Procedures cited in MIT02.

Description O AN 1/80

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

content

Use to provide the subject ofthe message.

Page Width O NO 1/3

Definition of the maximum number of characters per line that can be

expected in the message text Page Length Lines O NO 1/3

Definition of the maximum number of lines per page that can be expected

in the message text

003050FED01A 16 20 FEB 1997
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 thefull 264 character capability ofdata element 933 (MSG01) unless

specifically advised by a trading partner to limit the length ofany one iteration of

the segment to 80 characters.

Ref.

Pes.

Must Use MSG01

MSG02

Data Element Summary

Data

Element Name

933 Free-Form Message Text

Free-form message text

934 Printer Carriage Control Code O ID 2/2

A field to be used for the control of the line feed of the receiving printer

Attributes

M AN 1/264

003050FED01A 17 20 FEB 1997
864 -Text Message

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE

010

Transaction Set Trailer

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

1 SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use SE01 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 ST02.

003050FED01A 18 20 FEB 1997


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

fc. <UE „ O E § o1 3 -a

aso

CM

S

00o

O GO c o

Q W5 tm itut >» s

C/3 U

ba

C

s

=

M1—1 4» _

hnolo sburg

Busi

Q

g Tec Ui<U 2

.s. atio -C 'o — 'i3 £ 3 Z c

C3

Oo -