WIST

MDSb37

Nisr

NIST Special Publication 881-57

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 824

Application Advice

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

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 824

Application Advice

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

Natl. Inst. Stand. Technol. Spec. Publ. 881-57, 23 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
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 fiinctional group and transaction set

level, in either coded or free-form format. It is designed to accomodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used

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

acknowledgement sent in response to a purchase order).

Heading:

Pes. Seg. Req. Loop Notes and

1>0. ILI Name Pes. Max.Use Repeat Comments

Must Use 010 ST Transaction Set Header M 1 Must Use 020 BGN Beginning Segment M 1 LOO? ID - Nl 2 030 Nl Name 0 1 Not Used 040 N2 Additional Name Information O 2 Not Used 050 N3 Address Information o 2 Not Used 060 N4 Geographic Location o 1 Not Used 070 REF Reference Numbers 0 12 080 PER Administrative Communications Contact 0 3

Detail:

Pes. Seg. Req. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

LOOP ID - OTI >1 Must Use 010 OTI Onginal Transaction Identification M 1 Not Used 020 REF Reference Numbers 0 12 cl 030 DTM Date/Time Reference O 2 Not Used 040 PER Administrative Communications Contact 0 3 Not Used 050 AMT Monetary Amount 0 10 Not Used 060 QTY Quantity o 10 Not Used 065 Nl Name 0 1 LOOP ID - TED >1

070 TED Technical Error Description 0 1 Not Used 080 NTE Note/Special Instruction 0 100 LOOP ID - LM >1 Not Used 085 LM Code Source Information o 1 nl Not Used 086 LQ Industry Code M 100

Must Use 090 SE Transaction Set Trailer M 1

Transaction Set Notes

003040F824 1 29 May 1997
824 Application Advice

1. Use of the LM loop is limited to the identification of industry unique application error conditions.

Transaction Set Comments

1. REF segments can be used as needed to further identify the original transaction set.

003040F824 1 2 29 May 1997
824 Application Advice

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes:

Comments:

Ref. Pes. Must Use STOl

Must Use ST02

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 (STO 1) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810

selects the Invoice Transaction Set).

Data Element Summary

Data

Element Name Attributes

143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set 824 X 1 2 .44 Application Advice

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

set. This number may be system generated.

003040F824 1 3 29 May 1997
824 Application Advice

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 BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction. Comments: 1 BGN05 is the transaction set time quahfier.

Must Use

Ref.

Pes. BGNOl

Must Use BGN02

Must Use BGN03

Not Used BGN04

Not Used BGN05

Not Used BGN06

Not Used BGN07

Not Used BGN08

Data

Element

353

127

373

337

623

127

640

306

Data Element Summary

Name Attributes

Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set 00 Original

06 Confirmation

44 Rejection

Reference Number M AN 1/30

Reference number or identification number as defined for a particular

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

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

Refer to 003040 Data Element Dictionary for acceptable code values. Reference Number O AN 1/30

Reference number or identification number as defined for a particular

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

Transaction Type Code O ID 2/2

Code specifying the type of transaction Refer to 003040 Data Element Dictionary for acceptable code values. Action Code O ID 1/2

Code indicating type of action Refer to 003040 Data Element Dictionary for acceptable code values.

003040F824 1 4 29 May 1997
824 Application Advice

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

030

Nl Optional

Heading

Optional

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

1 At least one of N 1 02 or N 1 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. 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

98

93

66

67

Data Element Summary

Name Attributes

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 entity sending the transaction set. TO Message To

Use to indicate the entity to whom the transaction set

is being sent. Name X AN 1/35

Free-form name

Identification Code Qualifier X ID 1/2

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

1 D-U-N-S Number, Dun & Bradstreet Use ofthe DUNS or DUNS+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 or DUNS+4 number is preferred

over any other coded number to identify an entity.

10 Department of Defense Activity Address Code

(DODAAC)

Use to indicate either a Department ofDefense

Activity Address Code or a Civilian Agency Activity

Address Code.

33 Commercial and Government Entity (CAGE)

Use when a commercial or government entity cannot

be identified by a DUNS or DUNS+4 number.

Identification Code X AN 2/17

Code identifying a party or other code

003040F824 29 May 1997
824 Application Advice

Not Used N105 706 Entity Relationship Code O ID 2/2

Code describing entity relationship

Refer to 003040 Data Element Dictionary for acceptable code values. Not Used N106 98 Entity Identifier Code O ID 2/2

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

Refer to 003040 Data Element Dictionary for acceptable code values.

003040F824 1 6 29 May 1997
824 Application Advice

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

Notes:

Ref. Pes. Must Use PEROl

PER02

PER03

PER04

PER05

003040F824_1

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.

When NlOl is code FR, use to identify a contact to whom inquiries regarding this transaction set should be directed.

Data Element Summary

Data

Element Name Attributes

366 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

regarding this transaction set should be directed,

93 Name O AN 1/35

Free-form name

Cite the last namefirst, followed by thefirst name. Do not truncate the last name ifthe whole name is longer than 35 characters. Instead, truncate the

first name or use the initial ofthefirst name. 365 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)

ED Electronic Data Interchange Access Number

EM Electronic Mail

EX Telephone Extension

FX Facsimile IT International Telephone

TE Telephone

Use to indicate the commercial telephone number of

the party cited in the PEROl.

364 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. 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 PER03. For example, ifthe PER03/04 cites a commercial telephone

: 7 29 May 1997
824 Application Advice

number, PER05/06 can be used to cite an electronic mail address. 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 code TE. FX Facsimile IT International Telephone

TE Telephone

Use to indicate the commercial telephone number of

the party cited in the PER02.

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

003040F824_1 8 29 May 1997
824 Application Advice

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 OTI06 is the group date. 2 OTI07 is the group time. 3 If OTIl 1 is present, it will contain the version/release under which the original electronic transaction was translated by the receiver. 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 functional 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 OTI loop to report on more than one transaction set

Must Use

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

IR Item Reject

TA Transaction Set Accept

TC Transaction Set Accept with Data Content Change

TE Transaction Set Accept with Error TR Transaction Set Reject

Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

Use to indicate the unique reference number ofthe transaction set being

reported

TN Transaction Reference Number

Use to indicate the transaction set reference number.

VP Vendor Product Number

A unique number assigned by a vendor or manufacturer

to identify its products

Reference Number M AN 1/30

Reference number or identification number as defined for a particular

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

1. When OTIlO is code 810, cite the number in BIG02 ofthe 810 transaction

set.

2. When the OTIlO is code 820, cite the number in TRN02 ofthe 820

transaction set that is qualified by code 1 in TRNOl.

3. When the OTIlO is code 824 cite the number in the BGN02 ofthe 824

003040F824 1 29 May 1997
824 Application Advice

transaction set being reported.

4. When the OTIlO is code 832, cite the number in the BCT02 ofthe 832

transaction set

5. When the OTIlO is code 836, cite the number in the BCOlO or the 836

transaction set

6. When the OTIlO is code 838, cite the number in the BTP02 ofthe 838

transaction set.

7. When the OTIlO is code 840, cite tite number in the BQT02 ofthe 840

transaction set.

8. When the OTIlO is code 841, cite tIte number in tIte SPI02 (l/SPI/020) of

the 841 transaction set.

9. When OTIlO is code 843, cite tlie number in the REF02 (l/REF/050

segment) ofthe 843 transaction set that is qualified by code PR in REFOl.

10. When OTIlO is code 850, cite tlte number in BEG03 ofthe 850

transaction set. Ifa number is cited in both BEG03 and BEG04 ofthe 850

transaction set, concatenate these numbers.

11. When OTIlO is code 855, cite the number in the BAK03 ofthe 855

transaction set.

12. When OTIlO is code 856, cite the numberfrom BSN02 ofthe 856

transaction set.

13. When OTIlO is code 864, cite the number in REF02 (l/REF/080

segment) ofthe 864 transaction set that is qualified by code ME in REFOl.

14. When OTI02 is code VP and OTIlO is 879, cite the case UPC.

15. WIten OTI02 is code TN and OTIl 0 is 8 79, cite the number in ST02 of

the 879. Not Used OTI04 142 Application Sender's Code O AN 2/15

Code identifying party sending transmission; codes agreed to by trading

partners

Not Used OTI05 124 Application Receiver's Code O AN 2/15

Code identifying party receiving transmission. Codes agreed to by trading

partners

Not Used OTI06 373 Date O DT 6/6 Date (YYMMDD)

Not Used OTI07 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)

OTI08 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. OTI09 329 Transaction Set Control Number O AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

003040F824 10 29 May 1997
824 Application Advice

Use to identify the transaction set control number cited in the SE02 ofthe

transaction set being reported.

Must Use OTIlO 143 Transaction Set Identifier Code O ID 3/3

Code uniquely identifying a Transaction Set 101 Flight Confirmation

1 A /I ^ 1(J4 Alz.lUU An Shipment Intormation

1 AC Container/Equipment Transfer (Air)

1 A"? iU / Shipment Information for Export Declaration (Air)

1 AO 108 Shipment Iniormation tor Import (Air)

1 AA 109 Shipment Intormation lor Pick-Up/Dehvery Order

1 1 A 110 X 1 2 . 1 0 1 Air Freight Details and Invoice

111 111 Freight Details and Invoice Summary (Air)

1 1 O 113 Inquiry (Air)

1 1 C 115 Status Details Reply (Air)

1 1 116 Repetitive Pattern Maintenance (Air)

125 X12.75 Muhilevel Railcar Load Details 126 XI 2.76 Vehicle Application Advice

127 X12.77 Vehicle Baying Order

128 XI 2.78 Dealer Information

129 XI 2.79 Vehicle Carrier Rate Update

130 X12.89 Student Educational Record (Transcript) 131 XI 2.90 Student Educational Record (Transcript)

Acknowledgment

135 X12.198 Student Loan Application

139 XI 2.265 Student Loan Guarantee Result

140 X12.200 Product Registration 141 X12.201 Product Service Claim Response

1ifZ40 yvi/.zuz rroQuct ocrvicc c-iaim 143 XI/.203 Product Service Notiiication 144 XI 2.94 Student Loan Transfer and Status Verification (144)

146 X 12. 121 Request for Student Educational Record

147 XI 2. 123 Response to Request for Student Educational

Record (Transcript)

148 XI 2. 124 Report of Injury or Illness 151 XI 2.205 Electronic Filing of Tax Return Data Acknowledgment

152 XI 2.206 Statistical Government Information

154 XI 2.99 Uniform Commercial Code Filing 161 XI 2.72 Train Sheet

170 X12.210 Revenue Receipts Statement 180 X12.255 Return Merchandise Authorization and

Notification 186 X12.284 Laboratory Reporting

190 X12.264 Student Enrollment Verification

196 X12.280 Contractor Cost Data Reporting

204 X12.103 Motor Carrier Shipment Information

210 XI 2. 104 Motor Carrier Freight Details and Invoice

213 X12.105 Motor Carrier Shipment Status Inquiry

214 XI 2. 106 Transportation Carrier Shipment Status

003040F824 1 11 29 May 1997
824 Application Advice

Message

217 X 1 2 . 1 07 Motor Carrier Loading and Route Guide

218 X12.108Motor Carrier Tariff Information

250 X12.98 Purchase Order Shipment Management

Document

251 X12.288 Pricing Support

260 X12.275 Application for Mortgage Insurance Benefits

A claim filed for mortgage insurance benefits 263 XI 2.279 Residential Mortgage Insurance Application

Response

264 X12.285 Mortgage Loan Defauk Status 270 X12.281 Health Care Eligibility/Benefit Inquiry

271 X12.282 Health Care Eligibility/Benefit Information

272 X12.283 Property and Casualty Loss Notification

276 X12.316 Health Care Claim Status Request

277 XI 2.3 17 Health Care Claim Status Notification

290 XI 2. 293 Cooperative Advertising Agreement

300 X12.109 Reservation (Booking Request) (Ocean)

301 X12.109 Confirmation (Ocean)

302 Container/Specialized Equip. Pick-Up Order/Canc.

303 X1 2 . 1 1 0 Booking Cancellation (Ocean)

3 04 X1 2 . 1 1 3 Shipping Instructions 305 Container/Equipment Transfer (Ocean)

306 Dock Receipt

307 Shipment Information for Export Declaration (Ocean)

309 X12.117 U.S. Customs Manifest

310 X12.1 18 Freight Receipt and Invoice (Ocean)

311 X12.182-Canadian Customs Information (Ocean)

312 X12. 119 Arrival Notice (Ocean)

313 X1 2 . 1 20 Shipment Status Inquiry (Ocean)

314 Shipment Identities and Status Reply (Ocean)

315 X12.122 Status Details (Ocean)

316 Repetitive Pattern Maintenance (Ocean)

317 X12.271 Delivery/Pickup Order

319 X12.292 Terminal Information

321 Demurrage Guarantee (Ocean)

322 X12.127 Terminal Operations Activity (Ocean)

323 X12.128 Vessel Schedule and Intinerary (Ocean)

324 X12.129 Vessel Stow Plan (Ocean)

325 X12.208 Consolidation of Goods in Container

326 X12. 97 Consignment Summary List 350 X12.130 U.S. Customs Release Information

352 X12.131 U.S. Customs Carrier Release Information

353 ' X12.132 U.S. Customs Events Advisory Details 354 X12.133 U.S. Customs Automated Manifest Archive

Status 355 X12.134 U.S. Customs Manifest Acceptance/Rejection

356 X12.21 1 U.S. Customs Permit to Transfer Request

360 Tariff Information (Ocean)

361 XI 2. 136 Carrier Interchange Agreement (Ocean)

003040F824 1 12 29 May 1997
824 Application Advice

404

410

411

414

417

418

419

420

421

422

423

424

425

426

427

429

431

440

460

461

462

463

464

465

466

467

468

469

480

485

486

490

491

492

494

499

511

517

527

536

XI 2. 138 Rail Carrier Shipment Information

X12.139 Rail Carrier Freight Details and Invoice

Freight Details and Invoice Summary (Rail)

X12.83 Car Hire Settlements XI 2. 141 Rail Carrier Waybill Interchange

XI 2. 142 Rail Advance Interchange Consist

X12.143 Advance Car Disposition

X12.I44 Car Handling Information

XI 2. 261 Estimated Time of Arrival and Car Scheduling

X12.262 Shipper's Car Order

Average Agreement Demurrage

Switch Bills XI 2. 149 Rail Waybill Request

XI 2. 150 Rail Revenue Waybill

Waybill Response

X12.35 Railroad Retirement Activity

X12.65 Railroad Station Master File Transaction Set XI 2. 152 Shipment Weights

Rate Format Docket Data

Rate Format Level Data

Rate Format Sub-Level Data

Rate Set Docket Index

Rate Set Docket Data

Rate Set Sub-Level Data XI 2. 159 Rate Request

Scale Rate Docket Transmittal

X12.161 Rate Docket Journal Log

Rate Distribution Set Docket/Cluster Terminator

X12.164 Ratemaking Action

X12.165 Rate Docket Expiration

XI 2. 166 Rate Group Defmition

Rate Increase/Decrease Transmittal

X12.168 Miscellaneous Rates X12.169 Scale Rate Table

Application Acceptance Rejection Advice

X12.225 Requisition

Transaction set for ordering equipment and material

from a supply distribution system; this can also be used

to inquire about, amend, or terminate the original order X12.230 Material Obligation Validation

Transaction set for verifying the continued need for open orders. Can also be used to confirm open order

quantities and request reinstatement of previously

cancelled open orders XI 2.231 Material Due-In and Receipt

Transaction set for reporting material dues-in,

anticipated receipts, and receipts

XI 2.243 Logistics Reassignment

Transaction set for reporting information needed by a

003040F824 1 13 29 May 1997
824 Application Advice

561

567

568

601

602

622

805

806

810

811

812

813

815

816

818

819

820

821

822

823

824

826

827

828

829

830

831

832

833

834

835

836

837

838

839

840

841

842

843

844

845

846

847

003040F824 1

new manager when transferring inventory management

responsibility between organizations

XI 2.2 12 Contract Abstract

A summary of the essential elements of a contract,

sufficient to enable the contract administration process

to commence

X12.218 Contract Completion Status Transaction set for reporting the administrative closure

status of physically completed contracts XI 2.2 19 Contract Payment Management Report

X12.273 Shipper's Export Declaration

XI 2. 126 Transportation Sei"vices Tender

XI 2. 173 Intermodal Ramp Activity

XI 2. 195 Contract Pricing Proposal

X12.196 Project Schedule Reporting

X12.2 Invoice

XI 2.39 Consolidated Service Invoice/Statement

XI 2.40 Credit/Debit Adjustment

X12.62 Electronic Filing of Tax Return Data XI 2.42 Cryptographic Service Message

XI 2. 66 Organization Relationship

X12.256 Commission Sales Report

XI 2.43 Operating Expense Statement XI 2.4 Payment Order/Remittance Advice

XI 2.24 Financial Information Reporting

X12.25 Customer Account Analysis

X12.38 Lockbox

XI 2.44 Application Advice

XI 2. 19 Tax Information Reporting

X12.47 Financial Return Notice

XI 2.45 Debit Authorization

X12.48 Payment Cancellation Request

X12.14 Planning Schedule with Release Capability

X12.49 Application Control Totals X12.13 Price/Sales Catalog

XI 2.69 Mortgage Credit Report Order

X12.84 Benefit Enrollment and Maintenance

X12.85 Health Care Claim Payment/Advice

X12.54 Contract Award

X12.86 Health Care Claim

XI 2. 17 Trading Partner Profile X12.31 Project Cost Reporting

X12.7 Request for Quotation

X12.51 Specifications/Technical Information

XI 2.21 Nonconformance Report Transaction Set XI 2.8 Response to Request for Quotation

X12.26 Product Transfer Account Adjustment

XI 2.27 Price Authorization Acknowledgment/Status

X12.28 Inventory Inquiry/Advice

X12.63 Material Claim

14 29 May 1997
824 Application Advice

848 XI ? 36 Material Safetv Data Sheet

849 1 9 SO R p'snoTi'^p to Prnrliirt Tr^irmfpr A rrniint Adjustment

850 XI 2.1 Purchase Order

851 X12.51 Asset Schedule

852 X12.52 Product Activity Data

853 X12.64 Routing and Carrier Instruction 854 X12.68 Shipment Delivery Discrepancy Information

855 XI 2.9 Purchase Order Acknowledgment

856 X12.10 Ship Notice/Manifest

857 X12.29 Shipment and Billing Notice

858 X12.18 Shipment Information

859 X1 7 Preicfht Tnvoire

860 X12.15 Purchase Order Change Request - Buyer

Initiated 861 X12.12 Receiving Advice

862 X12.37 Shipping Schedule

863 X12.41 Report of Test Results 864 X12.34 Text Message

865 XI 2 16 Purchase Order Chanpe

Acknowledgment/Request - Seller Initiated 866 XI 2. 5 7 Production Sequence

867 XI 2.33 Product Transfer and Resale Report

868 XI 2.30 Electronic Form Structure 869 X12.1 1 Order Status Inquiry

870 XI 2. 23 Order Status Report

872 X12.53 Residential Mortgage Insurance Application

874 Purchase Order - Multipoint

875 X12.298 Grocery Products Purchase Order

876 X12.299 Grocery Products Purchase Order Change

877 Purchase Order Adjustment (UCS)

878 XI 2. 182 Product Authorization/De-Authorization

879 XI 2. 60 Price Change

880 XI 2.287 Grocery Products Invoice

881 Credit Memo/Debit Memo (UCS)

882 XI 2. 125 Direct Store Delivery Summary Information

883 Invoice - Multipoint (UCS)

884 Shipment Advice (UCS)

885 Receiving Advice (UCS)

888 X12.269 - Item Maintenance (UCS)

889 X12.183 Promotion Announcement

890 Prepayment Adjustment Advice (UCS)

891 Promotion Announcement Change

892 Promotion Announcement Confirmation

893 XI 2. 197 Item Information Request

894 XI 9 1 Delivprv/R etiim Rfi<;p Rppnrn

oyJ

'7 1 S\7 T^pl 1 \/pT*\//T? pti I t*ti A pVnr\\x/l pH fTPmptif' arst^lrw y\.iz..io/ i^cii V ci y / ivciui 11 /w^ivinj wicu^ciiiciii aiiu/oi Adjustment

896 X12.188 Product Dimension Maintenance

905 Remittance Advice (UCS)

003040F824 1 15 29 May 1997
824 Application Advice

920 XI 2. 174 Loss or Damage Claim - General

Commodities

924 X12.175 Loss or Damage Claim - Motor Vehicle

925 XI 2. 176 Claim Tracer 926 XI 2. 177 Claim Status Report and Tracer Reply

928 X12.178 Automotive Inspection Detail 940 X12.189 Warehouse Shipping Order

941 Warehouse Inventory Status Report

942 Warehouse Activity Report

943 X12. 191 Warehouse Stock Transfer Shipment Advice

944 XI 2. 192 Warehouse Stock Transfer Receipt Advice

945 XI 2. 193 Warehouse Shipping Advice

946 Delivery Information Message

947 XI 2. 194 Warehouse Inventory Adjustment Advice

980 XI 2. 179 Functional Group Totals 990 X12.180 Response To a Load Tender

994 Administrative Message

995 Advisory Information

996 X12.32File Transfer 997 XI 2.20 Functional Acknowledgment

998 X12.181 Set Cancellation

999 Acceptance/Rejection Advice

OTIll 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

Refer to 003040 Data Element Dictionary for acceptable code values.

003040F824 1 16 29 May 1997
824 Application Advice

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

Notes:

Ref. Pes. Must Use DTMOl

Must Use DTM02

DTM Date/Time Reference

030

OTI Mandatory

Detail Optional

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

Vseihis segment to identify the creation date ofthe transaction set being reported.

Data Element Summary

Data

Element Name

374

373

Attributes

Date/Time Qualifier M ID 3/3

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

097 Transaction Creation

Date X DT 6/6 Date (YYMMDD)

/. When the OTIlO is code 810, cite the datefrom the BiGOl ofthe 810

transaction set

2. When OTIlO is code 820, cite the datefrom BPR16 oftlie 820 transaction

set

3. When tlie OTIl 0 is code 824, cite the datefrom BGN03 ofthe 824

transaction set

4. When tlte OTIlO is code 832, cite the datefrom DTM02 (l/DTM/070

segment) ofthe 832 transaction set tliat is qualified by code 097 in REFOl.

5. When OTIlO is code 836, cite tlie datefrom BCO06 ofthe 836 transaction

set.

6. When OTIlO is code 838, cite tlie datefrom BTP08 ofthe 838 transaction

set.

7. When OTIlO is code 840, cite tlie datefrom BQT03 ofthe 840 transaction

set.

8. When OTIlO is code 841, cite the datefrom the DTM02 (1/DTM/lOO

segment) that is qualified by code 97 in DTMOl.

9. Wlien OTIlO is code 843, cite the datefrom BQR04 ofthe 843 transaction

set.

10. When OTIlO is code 850, cite the datefrom BEG05 ofthe 850

transaction set

11. When OTIlO is code 855, cite the datefrom BAK04 ofthe 855

transaction set

12. When OTIlO is code 856, cite the datefrom BSN03 ofthe 856

transaction set

003040F824 1 17 29 May 1997
824 Application Advice

Not Used DTM03

Not Used DTM04

DTM05

Not Used DTM06

Not Used DTM07

13. When OTIlO is code 864, cite the datefrom DTM02 ofthe 864

transaction set 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

Refer to 003040 Data Element Dictionary for acceptable code values. 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

Refer to 003040 Data Element Dictionary for acceptable code values. 1251 Date Time Period X AN 1/35

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

003040F824 1 18 29 May 1997
824 Application Advice

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes: Comments:

Notes:

Must Use

Ref. Pes. TEDOl

TED02

TED03

TED 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

Data Element Summary

Attributes

M ID 1/3

006

007

024

Name

Application Error Condition Code

Code indicating application error condition

1. Any code within data element 647 may be used, but the listed codes are

preferred.

2. When used to report on an 838 registration, use only code 847 or ZZZ.

Duplicate

Use to indicate a duplicate transmission ofa

transaction set not identified as a duplicate in data

element 353 ofa beginning segment. For example, an 850 transaction set with the exact data as a previously

received transaction set and both transaction sets contain code 00 in BEGOl.

Missing Data

Other Unlisted Reason

The reason for the application error condition cannot be

described using any other code on the standard code list Use to indicate an error not identified by a specific code. Specify the error in TED02.

Closed/Non-Existent Account Number

Use to indicate an erroneous DUNS number.

Incorrect Date The reported date is incorrect (e.g. premature date for transaction or non-existent date such as February 30)

Missing or Invalid Unit of Measure Code

Incomplete Transaction

Optional Element(s) required by the application are missing

Mutually Defined

Use to indicate an erroneous TIN number.

O AN 1/60

847

DTE

H

INC

ZZZ

Free Form Message

Free-form text When TEDOl is code 024, use to specify the error. Segment ID Code O ID 2/3

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

003040F824 1 19 29 May 1997
824 Application Advice

Number 77)

Use to identify the segment containing the error. TED04 719 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.

TED05 722 Element Position in Segment O NO 1/2

This is used to indicate the relative position of the data element in error in this data segment. The count starts with 1 for the data element immediately

following the segment ID. This value is 0 for an error in the segment ID. Use to identify the segment position ofthe data element containing the error, e.g.,DTMOL

TED06 725 Data Element Reference Number O NO 1/4

Reference number used to locate the Data Element Dictionary.

Use to identify the segment data element containing an error, e.g., 374. TED07 724 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. TED08 961 Data Element New Content O AN 1/99

New data which has replaced erroneous data

1. When the OTIOl is code TE or TR, use to identify the correct data, if known, that should have been transmitted in tite data element.

2. When OTIOl is code TC, tltis data element is required.

003040F824 1 20 29 May 1997
824 Application Advice

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.

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 SEOl 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 This is the number cited in the ST02.

003040F824 1 21 29 May 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) devel- oped 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

2(X)56.

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 NISTlRs—from the National Technical Information

Service, Springfield, VA 22161.

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

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

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

Title 15 CFR (Code of Federal Regulations).

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

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

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

in paper copy or microfiche form.
o c>o c o E 3

Is ^

Da"— Q g . o oI oOS

00oQ

60 , c > ^ DC >; Ob 3 Q< £ 5 m J:^ H x: o ^