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

AlllDS

NIST

publications!

Nisr

QC

TOO

U57

NO. 881 -51

998

NIST Special Publication 881-51

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003070 Transaction Set 824T

Application Advice (Trading Partner

Registration)

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-51

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003070 Transaction Set 824T

Application Advice (Trading Partner

Registration)

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-51

Natl. Inst. Stand. Technol. Spec. Publ. 881-51, 16 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNIVIENT PRINTING OFFICE

WASHINGTON: 1998

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
824 Application Advice

Functional Group ID= AG

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice

Transaction Set (824) for use within the context of an Electronic Data Interchange (EDI) environment. The

transaction set can be used to provide the ability to report the results of an application system's data content edits of

transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set

level, in either coded or free-form format. It is designed to accommodate the business need of reporting the

acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used

in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order

acknowledgment sent in response to a purchase order).

Notes:

This implementation ofthe ANSIASCX12 824 Transaction Set is used by the Federal Government to provide

application advice concerning tradingpartner registrations submitted to the Central Contractor Registration

System.

Heading:

Pos. .Sep Req. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

Must Use 010 ST Transaction Set Header M 1

Must Use 020 BGN Beginning Segment M 1 LOOP ID - Nl >1

030 Nl Name 0 I

Not Used 040 N2 Additional Name Information 0 2

Not Used 050 N3 Address Information 0 2

Not Used 060 N4 Geographic Location 0 I

Not Used 070 REF Reference Identification 0 12

080 PER Administrative Communications Contact 0 3

Detail:

Pos. Seg. Req. Loop Notes and

No. ID Name Pes. Max. Use Repeat Comments

LOOP ID - OTI >1

Must Use 010 OTI Original Transaction Identification M I nl

Not Used 020 REF Reference Identification 0 12 n2

030 DTM Date/Time Reference 0 2 n3

Not Used 040 PER Administrative Communications Contact 0 3 n4

Not Used 050 AMT Monetary Amount 0 >1 nS

Not Used 060 QTY Quantity 0 >1 n6

Not Used 065 NMl Individual or Organizational Name 0 9 n? LOOP ID - TED >1

070 TED Technical Error Description 0 I

Not Used 080 NTE Note/Special Instruction 0 ICQ

Not Used 082 RED Related Data 0 100 n8

003070F824T0 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

LOOP ID -LM >1

Not Used 085 LM Code Source Information 0 1 n9

LOOP ID -LQ 100

Not Used 086 LQ Industry Code M 1

Not Used 087 RED Related Data 0 100 nlO

Must Use 090 SE Transaction Set Trailer M I

Transaction Set Notes

1. The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this appUcation acknowledgment.

2. The REF segment allows for the provision of secondary reference identification or numbers required to uniquely identify the original transaction set. The primary reference identification or number should be

provided in elements OTI02-03.

3. The DTM segment allows for the provision of date, time, or date and time information required to uniquely

identify the original transaction set.

4. The PER segment should be utilized if administrative communications contact information is important to the

unique identification of the original transaction set.

5. The AMT segment should be utilized if monetary amount information is important to the unique

identification of the original transaction set.

6. The QTY segment should be utilized if quantity information is important to the unique identification of the

original transaction set.

7. The NMl segment allows for the provision of entity identification information required to uniquely identify

the original transaction set.

8. The RED segment may be used to provide data related to the error condition specified in the associated

TEDOl element.

9. The LM loop is used to identify industry-based or proprietary application error conditions.

10. The RED segment may be used to provide data related to the error condition specified in the associated LQ02

element.

003070F824T0 2 11 September 1997
824T - Application Advice (Trading Partner Registration)

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

Ref. Data

Pes. Element

Must Use STOl 143

Must Use ST02 329

Data Element Summary

Name Attributes

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

824 X12.44 Application Advice

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 identify a unique number assigned by the originator ofthe transaction

set This number may be system generated.

003070F824T0 3 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

BGN Beginning Segment

020

Heading

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 BGN10 is related to the date in BGN03.

Comments:

Must Use

Not Used

Not Used

Not Used

Not Used

Not Used

Ref.

Pes.

BGNOl

Must Use BGN02

Must Use BGN03

Must Use BGN04

BGN05

BGN06

BGN07

BGN08

BGN09

Must Use BGNIO

Data

Element

353

127

373

337

623

127

640

306

786

624

Data Element Summary

Name Attributes

Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set 00 Original

Reference Identification M AN 1/30

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

Use to identify the unique reference number assigned to this 824 transaction

set, not the transaction set that is being reported.

Date M DT 6/6

Date (YYMMDD)

Use to identify the date this 824 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)

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

Transaction Type Code O ID 2/2

Code specifying the type of transaction

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)

003070F824T0 4 11 September 1997
824T - Application Advice (Trading Partner Registration)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

Ref.

Pes.

Must Use NlOl

Not Used N102

Must Use N103

N104

Not Used N105

Not Used N106

030

Nl Optional

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

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

Address information is to be transmitted using only code values contained in a

combination ofNlOl, N103/N104 data elements.

2. There must be 2 iterations ofthe Nl loop in each transmission; one iteration to carry the name and address ofthe party transmitting the 824 transaction set and a

second iteration containing the name and address ofthe party to whom the 824

transaction is being sent,

3. The name and address ofeach party will be conveyed by use ofcode N103/04.

Data Element Summary

Data

Element

98

Name Attributes

M ID 2/3

93

66

67

706

98

Entity Identifier Code

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

individual

FR Message From

Use to indicate the entity sending the transaction set

TO Message To

Use to indicate tM^'SKity to whom the transaction set

is being senL

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 Identificarion

Code (67)

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

Use ofthe DUNS orDUNS+4 number is preferred

over any other coded number to identify an entity.

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

Suffix

Use ofthe DUNS orDUNS+4 number is preferred

f^j^^^l^^^^lll^^rf number to identify an entity.

Identification Code X AN 2/20

Code identifying a party or other code

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

003070F824T0 5 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

PER Administrative Communications Contact

080

Nl Optional

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.

When NlOl is code FR, use to identify a contact to whom inquiries regarding this

transaction set should be directed.

Must Use

Ref.

Pes.

PEROl

PER02

PER03

PER04

PER05

Data

Element

366

93

365

364

365

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

AL Alternate Contact

Person to be contacted when the main contact is not

available

Use to indicate an alternate party to whom inquiries

regarding this transaction set should be directed.

EA EDI Coordinator

Use to indicate the primary party to whom inquiries

gfigarding this transaction set should be directed.

Name O AN 1/60

Free-form name

Cite the last namefirst, followed by thefirst name. Do not truncate the last

name ifthe whole name is longer than 60 characters. Instead, truncate the

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

Code identifying the type of communication number

EM Electronic Mail

EX Telephone Extension

FX Facsimile

IT International Telephone

TE Telephone

'tlse to indicatfthe commerciaTielepltone numli^foj

the party cited in the PER02.

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

When PER03 is code TE, include the area code.

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

PER03. For example, ifthe PER03/04 cites a commercial telephone

number, PER05/06 can be used to cite an electronic mail address.

EM Electronic Mail

EX Telephone Extension

Use only ifPEROS is code TE.

003070F824T0 6 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

PER06 364

Not Used PER07 365

Not Used PER08 364

Not Used PER09 443

FX Facsimile

IT International Telephone

TE Telephone

Use to indicate the commercial telephone number of

the party cited in the PER02.

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

When the PER05 is code TE, include the area code.

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

003070F824T0 7 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

OTI Original Transaction Identification

010

OTI Mandatory

Detail

Mandatory

1To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, or accepted-with-change edit result

1 If OTI09 is present, then OTI08 is required.

1 OTI03 is the primary reference identification or number used to uniquely identify the

original transaction set. 2 OTI06 is the group date. 3 OTI07 is the group time.

4 If OTIl 1 is present, it will contain the version/release under which the original

electronic transaction was translated by the receiver.

5 OTI 12 is the purpose of the original transaction set, and is used to assist in its imique

identification.

6 OTI 13 is the type of the original transaction set, and is used to assist in its unique

identification.

7 OTI 14 is the application type of the original transaction set, and is used to assist in

its unique identification.

OTI 15 is the type of action indicated or requested by the original transaction set, and

is used to assist in its unique identification.

OTI 16 is the action requested by the original transaction set, and is used to assist in

its unique identification.

OTI 17 is the status reason of the original transaction set, and is used to assist in its unique identification.

Comments: 1 OTI02 contains the qualifier identifying the business transaction from the original

business application, and OTI03 will contain the original business application

identification.

2 If used, OTI04 through OTI08 will contain values from the original electronic

flinctional group generated by the sender.

3 If used, OTI09 through OTI 10 will contain values from the original electronic

transaction set generated by the sender.

Notes: Use this loop to identify the transaction set that is being reported and the action taken on that transaction set. Use multiple iterations ofthe OTIloop to report on more than one transaction set.

8

10

Ref.

Pes.

Must Use OTIOl

Must Use OTI02

Must Use OTI03

Data

Element

110

128

127

Data Element Summary

Name Attributes

Application Acknowledgment Code M ID 1/2

Code indicating the application system edit results of the business data

Use to identify the action taken regarding the transaction set being reported

in the same OTI loop.

TA Transaction Set Accept

TR Transaction Set Reject

Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

Use to indicate the unique reference number ofthe transaction set being

reported.

TN Transaction Reference Number

Use to indicate the transaction set reference number.

Reference Identification M AN 1/30

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

003070F824T0 8 11 September 1997
824T - Application Advice (Trading Partner Registration)

Not Used

Not Used

Not Used

Not Used

OTI04

OTI05

OTI06

OTI07

OTI08

OTI09

Must Use OTIlO

OTIll

When the OTIlO is code 838, cite the number in the BTP02 a^The l transaction set

142 Application Sender's Code O AN 2/15

Code identifying party sending transmission; codes agreed to by trading

partners

124 Application Receiver's Code O AN 2/15

Code identifying party receiving transmission. Codes agreed to by trading

partners

373 Date O DT 6/6

Date (YYMMDD)

337 Time O 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)

28 Group Control Number X NO 1/9

Assigned number originated and maintained by the sender

Use to identify the number cited in GS06 ofthefunctional group in which

"

the reported transaction was transmitted.

329 Transaction Set Control Number q 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 identify the transaction set control number cited in the SE02 oj

transaction set being reported.

143 Transaction Set Identifier Code O ID 3/3

Code uniquely identifying a Transaction Set

838 X12.17 Trading Partner Profile

480 Version / Release / Industry Identifier Code O AN 1/12

Code indicating the version, release, subrelease, and industry identifier of the

EDI standard being used, including the GS and GE segments; if code in DE455

in GS segment is X, then in DE 480 positions 1-3 are the version number;

positions 4-6 are the release and subrelease, level of the version; and positions

7-12 are the industry or trade association identifiers (optionally assigned by

user); if code in DE455 in GS segment is T, then other formats are allowed

Each Federal and Department ofDefense (DoD) Implementation

Convention (IC) used by the Federal government has a unique identifier

specified asfollows:

1. For Federal and DoD ICs based on an ANSIASCX12 transaction set:

Positions 1 through 6: ANSIASCXI2 Version and Release

number (e.g. 003010) upon which the

IC is based.

Position 7: Organizational Scope

F - Federal

D = DOD

G = Government (transitional)

Positions 8 through 10: Transaction Set Identifier Code

(e.g. 850).

Position 11: Variant: A character used to differentiate betyveen different

functional implementations ofthe

same transaction set.

003070F824T0 9 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

Position 12:

Ifthe convention is not a variant, an

underscore (_) will appear in this

position.

A sequential number starting with 0

and incremented by 1 each time the

implementation convention is revised.

An example ofthe Version/Release/Industry Identifier Codefor

revision 1 ofthe Federal specific ICfor the X12 Version 003050

Commercial Invoice (8I0C) transaction set is 0030SOF810C1.

2, For Federal and DoD ICs based on a UN/EDIFACT message:

Positions I through 3: UN/EDIFACT Version number

(e.g. 921, 97A) upon which the

IC is based.

Position 4:

Not Used OTI12 353

Not Used OTI13 640

Not Used OTI14 346

Not Used OTI15 306

Not Used OTI16 305

Not Used OTI17 641

Positions 5 through 10:

Position 11:

Position 12:

Organizational Scope

F = Federal

D=DOD

G = Government (transitional)

Message Identifier Code

(e.g. ORDERS).

Variant: A character used to differentiate between different

functional implementations ofthe

same message.

Ifthe convention is not a variant, an

underscore (_) will appear in this

position.

A sequential number starting with 0

and incremented by 1 each time the

implementation convention is revised.

An example ofthe Version/Release/Industiy Identifier Codefor

revision 1 ofthe Federal specific ICfor the UN/EDIFACT Version

97A Purchase Order (ORDERS) message is 97AFORDERS_l.

003070 Draft Standards Approved for Publication by ASC X 1

Procedures Review Board through October 1996

Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set Transaction Type Code O ID 2/2

Code specifying the type of transaction

Application Type O ID 2/2

Code identifying an application

Action Code O ID 1/2

Code indicating type of action

Transaction Handling Code O ID 1/2

Code designating the action to be taken by all parties

Status Reason Code O ID 3/3

Code indicating the status reason

003070F824T0 10 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use DTMOl

Must Use DTM02

DIM Date/Time Reference

030

OTI Mandatory

Detail

Optional

2

To specify pertinent dates and times

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

2 If DTM04 is present, then DTM03 is required.

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

'XJse this segment to identify the creation date ofthe referenced transaction set being

reported.

Data Element Summary

Data

Element Name Attributes

374 Date/Time Qualifier M ID 3/3

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

097 Transaction Creation

373 Date X DT 6/6

Date (YYMMDD)

1. When OTIlO is code 838, cite the datefrom BTP08 ofthe 838 transaction

set.

Must Use DTM03

Not Used DTM04

Must Use

Not Used

Not Used

DTM05

DTM06

DTM07

337 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 = mmutes (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)

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

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

1250 Date Time Period Format Qualifier X ID 2/3

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

1251 Date Time Period X AN 1/35

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

003070F824T0 11 1 1 September 1997
824T - Application Advice (Trading Partner Registration)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

TED

Must Use

Ref.

Des.

TEDOl

TED02

TED03

TED04

TED05

Technical Error Description

070

TED Optional

Detail

Optional

1To identify the error and, if feasible, the erroneous segment, or data element, or both

1 If used, TED02 will contain a generic description of the data in error (e.g., part

number, date, reference number, etc.).

1. Use this segment to identify errors within the reported transaction set.

2. Use multiple repetitions ofthis segment to identify multiple errors within the

reported transaction set.

Data

Element

647

721

719

722

Data Element Summary

Name

Application Error Condition Code

Code indicating application error condition

Attributes

M ID 1/3

006

007

847

DTE

INC

ZZZ

Duplicate

Missing Data

Closed/Non-Existent Account Number

Use to indicate an erroneous DUNS number.

IncoiTect Date

The reported date is incorrect (e.g. premature date for

transaction or non-existent date such as February 30)

Incomplete Transaction

Optional Element(s) required by the application are missing

Mutually Defined

Use to indicate an erroneous TIN number.

~"

"O' 'an 1/60

TED06 725

Free Form Message

Free-form text Segment ID Code O ID 2/3

Code defining the segment ID of the data segment in error (See Appendix A - Number 77)

Wse to identify the segment containing the error. "^^^H^PII^

Segment Position in Transaction Set O NO 1/6

The numerical count position of this data segment from the start of the

transaction set: the transaction set header is count position 1 Use to identify the position ofthe segment within the transmission ofthe

transaction set containing an error, e.g., 15. This is read as the 15th segment

transmitted.

Element Position in Segment O NO 1/2

This is used to indicate the relative position of a simple data element, or the

relative position of a composite data structure with the relative position of the

component within the composite data structure, in error; in the data segment

the count starts with 1 for the simple data element or composite data structure immediately following the segment ID

Use to identify the segment position ofthe data element containing the error,

e.g., 01 in the transmitted DTM segment, if that was the element in error. Data Element Reference Number O NO 1/4

003070F824T0 12 11 September 1997
824T - Application Advice (Trading Partner Registration)

TED07 724

Not Used TED08 961

003070F824T0 13 1 1 September 1 997

Reference number used to locate the data element in the Data Element

Dictionary

Use to identify the segment data element containing an error, e.g., 374.

Copy of Bad Data Element O AN 1/99

This is a copy of the data element in error Use to identify the erroneous content ofthe data element, e.g., 999.

Data Element New Content O AN 1/99

New data which has replaced erroneous data
824T - Application Advice (Trading Partner Registration)

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

090

Detail

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.

Must Use

Must Use

Ref.

Pes.

SEOl

SE02

Data

Element

96

329

Data Element Summary

Name Attributes

Number of Included Segments M NO 1/10

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

segments

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 the same unique control number assigned by the originator

ofthe transaction setf as the control number cited in ST02.

003070F824T0 14 11 September 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 1 949 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.
uS V. W c o on

oI o\OS

00Or-i

o

E 3

60 , O on

c