NAT'L INST. OF STAND 8;.,T;E,CH

A11105

NIST

PUBUCATlONSj

QC

100

.U57

^0.881-29

Special Publication 881-29

Nisr

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003070 Transaction Set 242

Data Status Tracking

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology
rhe National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . . . needed to improve product quality, to modernize manufacturing processes,

to ensure product reliability . . . and to facilitate rapid commercialization ... of products based on new scientific

discoveries."

NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's

competitiveness; advance science and engineering; and improve public health, safety, and the environment. One

of the agency's basic functions is to develop, maintain, and retain custody of the national standards of

measurement, and provide the means and methods for comparing standards used in science, engineering,

manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal

Government.

As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and

applied research in the physical sciences and engineering, and develops measurement techniques, test methods, standards, and related services. The Institute does generic and precompetitive work on new and

advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.

Major technical operating units and their principal activities are listed below. For more information contact the

Publications and Program Inquiries Desk, 301-975-3058.

Office of the Director

• National Quality Program

• International and Academic Affairs

Technology Services

• Standards Services

• Technology Partnerships

• Measurement Services

• Technology Innovation

• Information Services

Advanced Technology Program

• Economic Assessment

• Information Technology and Applications

• Chemical and Biomedical Technology

• Materials and Manufacturing Technology

• Electronics and Photonics Technology

Manufacturing Extension Partnership

Program

• Regional Programs

• National Programs

• Program Development

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology'

• Optoelectronics'

Chemical Science and Technology

Laboratory

• Biotechnology

• Physical and Chemical Properties^

• Analytical Chemistry

• Process Measurements

• Surface and Microanalysis Science

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Optical Technology

• Ionizing Radiation

• Time and Frequency'

• Quantum Physics'

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• NIST Center for Neutron Research

Manufacturing Engineering

Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Fabrication Technology

• Manufacturing Systems Integration

Building and Fire Research

Laboratory

• Structures

• Building Materials

• Building Environment

' • Fire Safety Engineering

• Fire Science

Information Technology Laboratory

• Mathematical and Computational Sciences^

• Advanced Network Technologies

• Computer Security

• Information Access and User Interfaces

• High Performance Systems and Services

• Distributed Computing and Information Services

• Software Diagnostics and Conformance Testing

'At Boulder, CO 80303. ^Some elements at Boulder, CO.
NIST Special Publication 881-29

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003070 Transaction Set 242

Data Status Tracking

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

January 1998

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Gary R. Bachula, Acting Under Secretary for Technology

National Institute of Standards and Technology

Raymond G. Kammer, 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-29

Natl. Inst. Stand. Technol. Spec. Publ. 881-29, 17 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
242 Data Status Tracking

Functional Group ID=DS

Introduction:

This Draft Standard for Trial Use contains the format and estabhshes the data contents of the Data Status Tracking

Transaction Set (242) within the context of an Electronic Data Interchange (EDI) environment. This management

transaction set is the vehicle by which the transmission status information is conveyed by a service request handler

to the interchange sender, interchange receiver, or both; it can be used to provide status information regarding

interchange as it flows from an interchange sender through one or more service request handlers to an interchange

receiver during its transmission cycle. It can be used by the interchange sender or interchange receiver to request

from a service request handler ad hoc or periodic reports containing status information regarding interchanges.

Notes:

1. Within the Federal Government, the Data Status Tracking transaction set (242) is usedfor two events:

A. it conveys information from the TA3 that was generated by a VANthat received an interchange, and

B. it is used to provide acknowledgment information

2. It shall not be used to request or provide periodic reports containing status information regarding

interchanges.

3. A single 242 transaction may be used to provide status on only a single interchange. Multiple status may be

providedfor that interchange within a single 242.

4. See Part 10 ofthe Federal Government Implementation Guidelinesfor a further discussion ofthe uses ofthe

Pos. Seg. Req. Loop Notes and

No. IB Name Pes. Max.Use Repeat Comments

Must Use 010 ST Transaction Set Header M 1

Must Use 020 BGN Beginning Segment M 1

Not Used 030 IRP Report Selection Segment O I

Not Used 040 DTP Date or Time or Period 0 10 cl

Not Used 050 REF Reference Identification 0 10 c2

Not Used 050 MSG Message Text 0 1 c3 LOOP ID - HL >1

070 HL Hierarchical Level 0 1 c4

080 IIS Interchange Identification Segment 0 1

090 Nl Name 0 I c5

Not Used 100 REF Reference Identification 0 10 c6

Not Used 110 QTY Quantity 0 >1 c7 LOOP ID - STS >I

120 STS Interchange Status Segment 0 1 c8

130 Nl Name o I c9

Not Used 140 REF Reference Identification 0 10 clO

150 QTY Quantity 0 >1 cll

Must Use 160 SE Transaction Set Trailer M 1

Transaction Set Comments

003070F242_0 15 July 1997
242 Data Status Tracking

1. The DTP segment is used to provide date/times or date/time ranges associated with the report being requested

or provided, for example the start and end dates and time of the report.

2. The REF segment contains reference numbers to further identify the report or specify the report request.

3. The MSG segment contains the report title.

4. HL identifies the appropriate hierarchical interchange level: HL03 indicates Interchange (IN), Functional

Group (FG), Transaction Set (TS). All levels are optional. All heirarchical levels that are used must be used

in the hierarchical order that they are listed.

5. The Nl segment identifies the source of the following status information.

6. The REF segment contains reference numbers assigned by the party identified in the Nl segment that fiirther identifies the interchange, functional group or transaction set.

7. The QTY segments can be used to report aggregate counts (e.g., number of functional groups and segments)

that were contained in the interchange, functional group or transaction set that is being tracked.

8. The STS segment provides status as reported by the source identified in the preceding Nl loop.

9. The Nl segment identifies the source of the status information included; provided only if the source is different from that in the HL loop Nl segment.

10. The REF segment provides reference numbers assigned by the party identified in the Nl segment that fiirther

identifies the status or error reported in STS (e.g., file number, message Id).

11. The QTY segments can be used to report aggregate counts from the status report that were contained in the

interchange, functional group or transaction set that is being tracked.

003070F242 0 2 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Mandatory

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

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

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

selects the Invoice Transaction Set).

Must Use

Must Use

Ref.

Pes.

STOl

ST02

Data

Element

143

329

Data Element Summary

Name Attributes

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

242 Data Status Tracking

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 The originator's translation software usually assigns the transaction set control number. Originating organizations may use any numbering scheme

consistent with their business practices, however, the scheme mustprovide

sufficient uniqueness to identify each transaction set. This same number is carried in SE02,

003070F242 0 3 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

BGN Beginning Segment

020

Mandatory

1To indicate the beginning of a transaction set

1 If BGN05 is present, then BGN04 is required.

1 BGN02 is the transaction set reference number.

2 BGN03 is the transaction set date. 3 BGN04 is the transaction set time.

4 BGN05 is the transaction set time qualifier.

5 BGN06 is the transaction set reference number of a previously sent transaction

affected by the current transaction.

6 BGN1 0 is related to the date in BGN03

.

Comments:

Ref.

Pes.

Must Use BGNOl

Must Use BGN02

Must Use BGN03

Must Use BGN04

Not Used BGN05

BGN06

Data Element Summary

Data

Element Name

353 Transaction Set Purpose Code

Code identifying purpose of transaction set

127

373

337

623

127

Attributes

M ID 2/2

00

01

Original

'Use to indicate that this is the initial submission ofa

''Data Status Tracking (242) transaction set. Cancellation

003070F242 0

'^se to cancel a previously transmitted Data Status

Tracking (242) transaction set. Cite the canceled

transaction set's Reference Identification in BGN06.

05 Replace

Use to completely replace a previously transmitted

Data Status Tracking (242) transaction set. All data

contained in the replaced transaction set shall be

overwritten. Cite the replaced transaction set's •Reference Identification in BGN06.

Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Quahfier

Cite a unique reference number assigned to this submission ofData Status

Tracking information by the originator.

Date M DT 6/6

Date (YYMMDD)

Cite the UTC date this 242 transaction set was originated.

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)

Cite the UTC time this 242 transaction set was originated in HHMMformat.

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

Reference Identification O AN 1/30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

4 15 July 1997
242 Data Status Tracking

BGN07 640

Not Used BGN08 306

Not Used BGN09 786

Not Used BGNIO 624

1. Do not me when BGNOl cites code 00.

2. When BGNOl cites code 01, enter the Reference Identification (BGN02)

ofthe Data Status Tracking (242) transaction set being canceled.

3. When BGNOl cites code 05, enter the Reference Identification (BGN02)

ofthe Data Status Tracking (242) transaction set being replaced.

Transaction Type Code O ID 2/2

Code specifying the type of transaction

DS Disposition

Use to indicate the transaction is providing

interchange status in accordance with the

acknowledgment model contained in Part 10 ofthe

Federal Government Implementation Guidelines.

Action Code O ID 1/2

Code indicating type of action

Security Level Code O ID 2/2

Code indicating the level of confidentiality assigned by the sender to the

information following

Century O NO 2/2

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

003070F242 0 5 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Not Used

Must Use

Not Used

Ref.

Pes.

HLOl

HL02

HL03

HL04

HL Hierarchical Level

070

HL Optional

Optional

1To identify dependencies among and the content of hierarchically related groups of data

segments

1 The HL segment is used to identify levels of detail information using a hierarchical

structure, such as relating line-item data to shipment data, and packaging data to line- item data. The HL segment defines a top-down/left-right ordered structure. 2 HLOl shall contain a unique alphanumeric number for each occurrence of the HL

segment in the transaction set. For example, HLOl could be used to indicate the

number of occurrences of the HL segment, in which case the value of HLOl would

be " 1 " for the initial HL segment and would be incremented by one in each

subsequent HL segment within the transaction.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

4 HL03 indicates the context of the series of segments following the current HL

segment up to the next occurrence of an HL segment in the transaction. For example,

HL03 is used to indicate that subsequent segments in the HL loop form a logical

grouping of data referring to shipment, order, or item-level information.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related

to the current HL segment.

A single 242 transaction may he used to provide status on only a single interchange.

Therefore, the HL Loop will be used only once.

Data

Element

628

734

735

736

Data Element Summary

Name Attributes

Hierarchical ID Number M AN 1/12

A unique number assigned by the sender to identify a particular data segment

in a hierarchical structure Enter the number L

Hierarchical Parent ID Number O AN 1/12

Identification number of the next higher hierarchical data segment that the data

segment being described is subordinate to Hierarchical Level Code M ID 1/2

Code defining the characteristic of a level in a hierarchical structure IN Interchange

Hierarchical Child Code O ID 1/1

Code indicating if there are hierarchical child data segments subordinate to the

level being described

003070F242 0 6 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use IlSOl

Must Use IIS02

Must Use IIS03

Must Use IIS04

Must Use IIS05

Must Use IIS06

Must Use IIS07

Must Use IIS08

Not Used IIS09

Not Used IISIO

003070F242 0

IIS Interchange Identification Segment

080

HL Optional

Optional

1To uniquely identify interchange control structures

1 IIS02, IIS03, IIS04, IIS05, IIS06, IIS07, and IIS08 identify the interchange control

structure being reported.

2 IIS09, IISIO, IIS 11, and IIS 12 are used to report additional control structure

identification codes.

Use this Interchange Identification Segment (IIS) to identify the interchangefor which

status is being provided in subsequent Interchange Status Segment (IIS) loops(s).

Data Element Summary

Data

Element

144

145

146

147

148

149

150

151

152

153

Name Attributes

Reported Start Segment ID O AN 2/3

This contains the start segment ID of the original interchange, functional group

or transaction set For ANSIASCXI2 interchanges, the start segment ID is always ISA

Reported Control Number O AN 1/14

This is the control number value of the original interchange, functional group

or transaction set Cite the control number assigned in the original interchange control header

(appearing in ISA13) for which status is being provided. With this control

number, this IIS loop ofthe 242 is linked to the original interchange

envelope.

Reported Date O AN 1/8

This is the date value of original interchange or functional group

Cite the date appearing in ISA09 ofthe interchangefor which status is being

provided.

Reported Time O AN 1/8

This is the time value of original interchange or functional group

Cite the time appearing in ISAIO ofthe interchangefor which status is being

provided.

Reported Interchange Sender ID Qualifier O AN 1/4

This is the sender ID qualifier value appearing in original interchange

Cite the value appearing in ISAOS ofthe interchangefor which status is being provided.

Reported Sender ID O AN 1/35

This is the sender ID value of original interchange or functional group

Cite the value appearing in ISA06 ofthe interchangefor which status is being provided.

Reported Interchange Receiver ID Qualifier O AN 1/4

This is the receiver ID qualifier value appearing in original interchange

Cite the value appearing in ISA07 ofthe interchangefor which status is being provided.

Reported Receiver ID O AN 1/35

This is the receiver ID value of original interchange or functional group

Cite the value appearing in ISAOS ofthe interchangefor which delivery

notice is being provided.

First Reference ID Qualifier O AN 1/4

This is the ID qualifier appearing in original interchange

First Reference ID O AN 1/14

This contains information from the original interchange, as defined by the First

7 15 July 1997
242 Data Status Tracking

Not Used IISll 154

Not Used IIS12 155

Not Used IIS13 161

Not Used IIS14 164

Reference ID Qualifier data element

Second Reference ID Qualifler O AN 1/4

This contains ID qualifier information appearing in original interchange

Second Reference ID O AN 1/14

This contains information from the original interchange, as defined by the

Second Reference ID Qualifier data element

Message Direction Code O ID 1/1

Code identifying whether the reported transactions have been sent and/or

received by Data Status Tracking report recipient

Reported Group or Transaction Identifier O AN 2/6

This contains the functional group or transaction set identifier code of the

reported functional group or transaction set

003070F242 0 8 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

090

HL Optional

Optional

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

1 At least one of N1 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 'TD Code" (N104) must

provide a key to the table maintained by the transaction processing party.

2 N1 05 and N1 06 further define the type of entity in N 1 0 1

Use this Nl segment to cite the originator ofthis transaction.

Data Element Summary

Must Use

Not Used

Ref.

Pes.

NlOl

N102

N103

N104

Not Used

Not Used

N105

N106

Data

Element

98

93

66

67

706

98

Name Attributes

Entity Identifier Code M ID 2/3

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

individual

FR Message From

Name X AN 1/60

Free-form name

Identification Code Qualifier X ID 1/2

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

Code (67)

D-V-N'S (Code 1) or D-U'N-S+4 (Code 9) are preferred.

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

2 Standard Carrier Alpha Code (SCAC)

4 International Air Transport Association (LATA)

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

Suffix

10 Department of Defense Activity Address Code

(DODAAC)

33 Commercial and Government Entity (CAGE)

ZZ Mutually Defined

Use to indicate VCCEI)1 Comntunications ID (Comm

ID).

Identification Code X AN 2/20

Code identifying a party or other code

1. Cite the Identification Code ofthe originator ofthefollowing status information.

2. Ifthe originator and source ofthe status information are different, the source ofthe status information is identified in the l/Nl/130 segment.

Entity Relationship Code O ID 2/2

Code describing entity relationship

Entity Identifier Code O ID 2/3

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

individual

003070F242 0 9 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use STSOl

STS Interchange Status Segment

120

STS Optional

Optional

1To identify activity taken with an interchange

1 If the time code is omitted, the qualifier will be assumed to be universal time

coordinate (UTC).

This STS loop can be repeated as many times as necessary to provide multiple status conditions related to the interchange being reported.

Data

Element

140

Data Element Summary

Name Attributes

Action Code M ID 2/2

This is a code indicating the action taken on the interchange or functional

group by the service request handler or the receiver

Cite the action codefor the status being reported within this iteration ofthe

STS loop.

Must Use STS02 141

AK Transfer to the Next Service Request Handler has been

Acknowledged

BH Transfer to Service Request Handler not Capable of

Reporting Further Status

DL Delivered Interchange by Service Request Handler

PU Purged by Interchange Receiver

RD Redirected by Service Request Handler to an Alternate

Receiver as Identified in the Reference Code

RF Refused by Interchange Receiver

RJ Rejected by Service Request Handler; See Error Reason

Code for Cause

RT Retrieved Interchange by Receiver

TR Transferred to Next Service Request Handler by Service

Request Handler, but not yet Acknowledged

Action Date M DT 6/6

This is the UTC date when the service request handler took action on the

reported interchange or functional group

Cite the UTC date the action reported in STSOl was accomplished.

Must Use STS03 142 Action Time M TM 4/6

This is the UTC time when the service request handler took action on the

reported interchange or functional group

1. Cite the UTC time the action reported in STSOl was accomplished.

2. Express time in afour-position (HHMM)format.

Not Used STS04

Not Used STS05

003070F242 0

623 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

624 Century O NO 2/2

10 15 July 1997
242 Data Status Tracking

STS06

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

143 Error Reason Code O ID 3/3

The code indicates the error found or not found in processing the control

structure or in delivery

IfSTSOl is code RJ, cite the applicable error code.

000 No Errors

001 The Interchange Control Number in the Header and

Trailer Do not Match; the Value from the Header is used in the Acknowledgment

002 This Standard as Noted in the Control Standards

Identifier is not Supported

003 This Version of the Controls is not Supported

004 The Segment Terminator is Invalid

005 Invalid Value as Shown in the Reported Interchange

Control Number

006 Invalid Value as Shown in the Reported Interchange

Date

007 Invalid Value as Shown in the Reported Interchange

Time

008 Invalid Value as Shown in the Reported Interchange

Sender ID Qualifier

009 Invalid Value as Shown in the Reported Interchange

Sender ID

010 Invalid Value as Shown in the Reported Interchange

Receiver ID Qualifier

011 Invalid Value as Shown in the Reported Interchange

Receiver ID

016 Trading Partnership not Established

017 Invalid Number of Included Groups Value

018 Invalid Control Structure

019 Improper (Premature) End-of-file (Transmission)

020 Duplicate Interchange Control Number

02 1 Invalid Data Element Separator

022 Invalid Component Element Separator

023 Failure to Transfer Interchange to the next Service

Request Handler

03 1 Receiver Not On-line

032 Abnormal Conditions

003070F242 0 11 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use NlOl

Not Used N102

N103

N104

Not Used

Not Used

N105

N106

Nl Name

130

STS Optional

Optional

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

1 At least one of N1 02 or N1 03 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 N1 05 and N1 06 further define the type of entity in N1 0 1

.

Use to identify the source ofthe status information ifdifferentfrom that identified in

the l/Nl/090 segment

Data

Element

98

93

66

67

706

98

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/3

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

individual

HQ Source Party of Information

Name X AN 1/60

Free-form name

Identification Code Qualifier X ID 1/2

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

Code (67)

D-U-N-S (Code 1) or D-U-N-S+4 (Code 9) are preferred

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

2 Standard Carrier Alpha Code (SCAC)

4 International Air Transport Association (LATA)

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

Suffix

10 Department of Defense Activity Address Code

(DODAAC)

33 Commercial and Government Entity (CAGE)

ZZ Mutually Defined

Use to indicate UCC EDI Communications ID (Comm

ID).

Identification Code X AN 2/20

Code identifying a party or other code

Cite the Identification Code ofthe source ofthefollowing status information.

Entity Relationship Code O ID 2/2

Code describing entity relationship

Entity Identifier Code O ID 2/3

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

individual

003070F242 0 12 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use QTYOl

Must Use QTY02

Not Used QTY03

Not Used COOlOl

Not Used C00102

Not Used C00103

Not Used C00104

Not Used C00105

Not Used C00106

Not Used C00107

Not Used C00108

Not Used C00109

Not Used COOnO

003070F242 0

QTY Quantity

150

STS Optional

Optional

>1

To specify quantity information

1 At least one of QTY02 or QTY04 is required.

2 Only one of QTY02 or QTY04 may be present.

1 QTY04 is used when the quantity is non-numeric.

1. This QTYsegment may be used to report the number ofitems listed in QTYOl

observed by the reporting organization,

2. This segment can not be used when the interchange status information provided in

the preceding STS segmentforwards information receivedfrom another service

grovider via a TA3.

Data Element Summary

Data

Element

673

380

COOl

355

1018

649

355

1018

649

355

1018

649

355

Attributes

M ID 2/2

X R 1/15

Name

Quantity Qualifier

Code specifying the type of quantity

2T Electronic Signatures

2U Bytes

2W Segments

2Y Functional Groups

2Z Transaction Sets

Quantity

Numeric value of quantity

Enter the number ofthe items specified in QTYOl observed by the reporting

organization.

Composite Unit of Measure O

To identify a composite unit of measure (See Figures Appendix for examples

of use)

Unit or Basis for Measurement Code M ID 2/2

Code specifying the units in which a value is being expressed, or maimer in

which a measurement has been taken

Exponent

Power to which a unit is raised

Multiplier

Value to be used as a multiplier to obtain a new value

Unit or Basis for Measurement Code

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

Exponent

Power to which a unit is raised

Multiplier

Value to be used as a multiplier to obtain a new value

Unit or Basis for Measurement Code

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

Exponent

Power to which a unit is raised

Multiplier

Value to be used as a multiplier to obtain a new value

Unit or Basis for Measurement Code

13

O R 1/15

O R 1/10

O ID 2/2

O R 1/15

O R 1/10

O ID 2/2

O R 1/15

O R 1/10

O ID 2/2

15 July 1997
242 Data Status Tracking

Not Used COOlll 1018

Not Used C00112 649

Not Used cool 13 355

Not Used C00114 1018

Not Used C00115 649

Not Used QTY04 61

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

Exponent

Power to which a unit is raised

Multiplier

Value to be used as a multiplier to obtain a new value

Unit or Basis for Measurement Code

Code specifying the units in which a value is being expressed, or manner in

which a measurement has been taken

Exponent

Power to which a unit is raised

Multiplier

Value to be used as a multiplier to obtain a new value

Free-Form Message

Free-form information

O R 1/15

O R 1/10

O ID 2/2

O R 1/15

O R 1/10

X AN 1/30

003070F242 0 14 15 July 1997
242 Data Status Tracking

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

160

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

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 that carried in ST02.

003070F242 0 15 15 July 1997
1


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

<uB

o

B

•a

o1 Co

tanda OSo00o 00

en

o

Q

B

o