**Intelligent Transportation Systems (ITS)**

**Commercial Vehicle Operations (CVO)**

**Electronic Data Interchange (EDI)**

**Implementation Guide**

**for Application Advice**

**(Transaction Set 824)**

**ANSI ASC X12**

**Version 4 Release 4**

**POR-99-7203 V1.0**

**March 2001**

*Prepared for*

![](media/image1.wmf)

*US Department of Transportation*

*Federal Motor Carrier Safety Administration*

*400 Seventh Street, SW*

*Washington, DC 20590*

*Prepared by*

![](media/image2.wmf){width="0.42430555555555555in" height="0.55in"}

*The Johns Hopkins University*

*Applied Physics Laboratory*

*11100 Johns Hopkins Road*

*Laurel, MD 20723*

[]{#Preface .anchor}**Preface**

**Please note that this is a Baseline Issue**

This is a baseline document. This document has completed internal and
external reviews of previously published drafts and preliminary
versions. All comments received to date have been incorporated or
addressed.

**Sponsorship**

This document was prepared under the sponsorship of the Federal Motor
Carrier Safety Administration (FMCSA). The Motor Carrier Safety
Improvement Act of 1999 established the FMCSA within the US Department
of Transportation (DOT), effective January 1, 2000. Prior to that, the
motor carrier and highway safety program was administered under the
Federal Highway Administration (FHWA). The mission of the FMCSA is to
improve truck and commercial passenger carrier safety on our nation\'s
highways through information technology, targeted enforcement, research
and technology, outreach, and partnerships. The FMCSA manages the
Intelligent Transportation Systems Commercial Vehicle Operations
(ITS/CVO) Program, a voluntary effort involving public and private
partnerships that uses information systems, innovative technologies, and
business practice reengineering to improve safety, simplify government
administrative systems, and provide savings to states and motor
carriers. The FMCSA works closely with the FHWA\'s ITS Joint Program
Office (JPO) to ensure the integration and interoperability of ITS/CVO
systems with the national ITS program. .

**Electronic Document Availability**

This document and its companion volumes are available for review and
downloading from The Johns Hopkins University/Applied Physics Laboratory
(JHU/APL) Commercial Vehicle Operations (CVO) Site on the World Wide
Web. All updates to the JHU/APL EDI implementation guides will be
maintained and published on that site; hardcopies of this and future
versions will not be distributed. The URL for the CVO Site is:

**<http://www.jhuapl.edu/cvisn/>**

For more information, please contact:

> The Johns Hopkins University
>
> Applied Physics Laboratory
>
> 11100 Johns Hopkins Road
>
> Laurel, MD 20723
>
> Ms. Theresa G. Nester
>
> Phone: (240) 228-8760
>
> Fax: (240) 228-6149
>
> E-Mail: theresa.nester@jhuapl.edu

[]{#Overview .anchor}**Overview of Changes**

This document is an update of Johns Hopkins University Applied Physics
Laboratory document POR 99-7203 D.2, dated March 2000, which is the
second draft of an Implementation Guide on the use of the ANSI X12 EDI
Transaction Set \"Application Advice (824).\" This document covers the
use of the 824 to report the results of an application system\'s data
content edits of received transaction sets. The changes between the
previous draft and this baseline version reflect alterations in some of
the mapping conventions previously adopted. The changes incorporate many
suggestions and comments made by organizations and programmers with an
interest in 824 implementation.

The information below summarizes the changes made. The version of the
824 contained herein uses X12 Standard Version 4 Release 4 and Federal
Motor Carrier Safety Administration Code Directory V1.0 (hereafter
referred to as the Code Directory). Nonetheless, it is expected that
experience with 824 use will continue to stimulate changes in usage
conventions.

**[Transaction Set Structure Changes:]{.underline}**

1.  No changes to the structure of the 824 Transaction Set have been
    made since the publication of the previous document.

**[Changes in Usage Conventions:]{.underline}**

Changes are incorporated into this document through submission of change
requests to the EDI Configuration Control Board (CCB) established at
JHU/APL. The requests are reviewed and if determined to be applicable to
the document, they are implemented. See Section 3.0 (MAINTENANCE
SUPPORT) for the formal procedure for submitting changes to this
document.

1.  **Change Request 1432 -- TS 824 IG Update**

    1.  Modifies document to reflect X12 Version 4 Release 4.

    2.  Section 3, Maintenance Support:

        1.  Modifies Section 3.1, Maintaining Guidelines, to include
            posting of approved change requests.

        2.  Deletes Section 3.4, Document Timing.

    3.  Section 4, References: updates references.

    4.  Appendix C, Code Table References: updates references.

EDI Implementation Guide

**for Application Advice**

**Transaction Set 824**

**Table of Contents**

  ----------------------------------- -----------------------------------
  Preface                             [3](#Preface)

  Overview of Changes                 [4](#Overview)
  ----------------------------------- -----------------------------------

1.0 INTRODUCTION [1-1](#introduction)

1.1 Purpose of Implementation Guide
[1-1](#purpose-of-implementation-guide)

1.2 Scope and Applicability [1-1](#scope-and-applicability)

1.3 Associated Transaction Sets [1-2](#associated-transaction-sets)

1.4 Responsible Organizations [1-3](#responsible-organizations)

2.0 BUSINESS ISSUES [2-1](#business-issues)

2.1 Business Case [2-1](#business-case)

2.1.1 TS 824 Users [2-2](#ts-824-users)

2.2 Timing of Transactions [2-4](#timing-of-transactions)

2.3 Security [2-4](#security)

2.4 Acknowledgment Procedures [2-4](#acknowledgment-procedures)

2.5 Legal Considerations [2-4](#legal-considerations)

3.0 MAINTENANCE SUPPORT [3-1](#maintenance-support)

3.1 Maintaining Implementation Guidelines
[3-1](#maintaining-implementation-guidelines)

3.2 Maintaining X12 Standards [3-1](#maintaining-x12-standards)

3.3 Maintaining External Code Sources
[3-1](#maintaining-external-code-sources)

4.0 REFERENCES [4-1](#references)

4.1 General EDI [4-1](#general-edi)

4.2 Hardware and Communications [4-1](#hardware-and-communications)

4.3 ITS/CVO and Credential Transaction
[4-2](#itscvo-and-credential-transaction)

5.0 TRANSACTION SET [5-1](#transaction-set)

5.1 Overall Data Architecture [5-1](#overall-data-architecture)

5.1.1 Header Table [5-1](#header-table)

5.1.2 Detail Table [5-1](#detail-table)

5.2 Transaction Set Table [5-2](#transaction-set-table)

6.0 SEGMENT USAGE [6-1](#segment-usage)

6.1 X12 Control Segment Usage [6-1](#x12-control-segment-usage)

6.2 Implementation Convention Segment Usage
[6-3](#implementation-convention-segment-usage)

7.0 EXAMPLE TRANSACTIONS [7-1](#example-transactions)

7.1 Scope [7-1](#scope)

7.2 Message Structures [7-1](#message-structures)

7.3 Message Type Indicators [7-3](#message-type-indicators)

7.4 Data Flow [7-3](#data-flow)

7.5 Example 1 -- Application Advice Negative
[7.5-1](#example-1-application-advice-negative)

7.6 Example 2- Application Advice Positive
[7.6-1](#example-2--application-advice-positive)

Appendix A TRANSACTION FLOW [A-1](#transaction-flow)

A.1 Valid Transactions [A-2](#valid-transactions)

A.1.1 Valid Query [A-2](#valid-query)

A.1.2 Valid Update [A-3](#valid-update)

A.2 Transactions with Syntax Errors
[A-4](#transactions-with-syntax-errors)

A.3 Invalid Transactions [A-5](#invalid-transactions)

A.3.1 Invalid Query [A-5](#invalid-query)

A.3.2 Invalid Update [A-7](#invalid-update)

A.4 Unsuccessful Query [A-9](#unsuccessful-query)

Appendix B BACKGROUND INFORMATION [B-1](#background-information)

B.1 Related Sites and Resources [B-1](#related-sites-and-resources)

Appendix C CODE TABLE REFERENCES [C-1](#code-table-references)

C.1 X12 Cited Code Sources [C-1](#x12-cited-code-sources)

C.2 Other Code Sources [C-1](#other-code-sources)

Appendix D DATA ITEM/SEGMENT CROSS-REFERENCE
[D-1](#data-itemsegment-cross-reference)

D.1 Data Items in Transaction Set Order
[D.1-1](#data-items-in-transaction-set-order)

D.2 Data Items in Alphabetical Order
[D.2-1](#data-items-in-alphabetical-order)

**List of Figures**

Figure 1‑1: Implementation Guide Scope
[1-2](#__RefHeading___Toc507819256)

Figure 2‑1: CVISN Architecture Flow Diagram for Application Advice
[2-3](#__RefHeading___Toc507819257)

Figure 3‑1: Change Request Form [3-2](#__RefHeading___Toc507819258)

Figure 3‑2: Change Resolution Form [3-4](#__RefHeading___Toc507819259)

Figure 6‑1: EDI Transmission Structure
[6-2](#__RefHeading___Toc507819260)

Figure 6‑2: Implementation Convention Segment
[6-4](#__RefHeading___Toc507819261)

Figure 7‑1: Application Advice (Postive, Negative)
[7-2](#__RefHeading___Toc507819262)

List of Diagrams

Diagram A‑1: Query With No Syntax Or Data Errors
[A-2](#__RefHeading___Toc507819263)

Diagram A‑2: Update With No Syntax Or Data Errors
[A-3](#__RefHeading___Toc507819264)

Diagram A‑3: Transaction With Syntax Errors
[A-4](#__RefHeading___Toc507819265)

Diagram A‑4: Invalid Query [A-6](#__RefHeading___Toc507819266)

Diagram A‑5: Invalid Update [A-8](#__RefHeading___Toc507819267)

Diagram A‑6: Unsuccessful Query [A-9](#__RefHeading___Toc507819268)

**List of Tables**

Table 3‑1: Change Request Form Explanation
[3-3](#__RefHeading___Toc507819269)

Table 3‑2: Change Resolution Form Explanation
[3-5](#__RefHeading___Toc507819270)

Table 6‑1: Transaction Set Segment Notes
[6-5](#__RefHeading___Toc507819271)

Table 7‑1: Data Flow [7-3](#__RefHeading___Toc507819272)

List of Matrices

Matrix D‑1: Data Item Matrix Columns [D-1](#__RefHeading___Toc507819273)

# INTRODUCTION

This document is an Implementation Guide for Electronic Data Interchange
(EDI) Transactions conducted using Accredited Standards Committee (ASC)
X12 EDI Transaction Set (TS) 824 (Application Advice). This
Implementation Guide pertains to transactions associated with the 824
for commercial vehicles that take place among requestors, data
repositories, and reporting entities.

This document was prepared by The Johns Hopkins University Applied
Physics Laboratory under contract to the US Department of Transportation
(DOT), Federal Motor Carrier Safety Administration (FMCSA). Feedback and
suggestions for improvement of this document are welcome. The last page
is a form that can be used for that purpose.

## Purpose of Implementation Guide

EDI transactions provide standard, pre-defined messages among
stakeholders to communicate CVO-related information and allow computers
to process information such as safety data and credential applications.
EDI transactions support data interfaces across various jurisdictions
and between public (e.g., state motor vehicle administration) and
private (e.g., carrier) offices.

The purpose of this document is to provide guidance and reference
information for public and private agencies to implement and maintain
one or more connections using TS 824 for Application Advice
transactions. The interface diagrams in Appendix A provide users with a
high-level perspective of the major interfaces between trading partners.

## Scope and Applicability

This guide provides specific coding information for implementing TS 824
transactions that take place among requestors, data repositories and
reporting entities. The primary audience for this document is an
experienced EDI programmer, tasked with implementing the 824 for such
transactions. The document lays out the business case and envisioned
environment for the transaction, the transaction set table and its
control segments, segment usage, transaction examples, how the
transaction set information is to be maintained, and other useful
information relating to the implementation of the transaction set.

The transaction set syntax followed in this document is that set by the
American National Standards Institute (ANSI) Accredited Standards
Committee X12. The UN/EDIFACT standard, recognized as an international
EDI standard, is not presently in wide use in US commercial vehicle
businesses.

The general contents of this document are based on the topics suggested
in Reference \[1\], in Section 4.1. Topics appropriate to Application
Advice EDI transactions were identified.

Figure 1-1 provides a view of implementation guide topics with business
related areas needed to fully implement an EDI transmission.
Implementers of this transaction set must understand their data
requirements, understand the X12 standard, and be able to use this
information to develop an interface between their application and the
X12 standard. The implementation guide provides the information
necessary for this to occur. The implementation guide identifies where
application data shall be carried in the X12 transaction set. All EDI
implementations shall conform to the implementation guide. This document
does **not** provide information on:

-   Introduction to basic EDI concepts

-   EDI translation, formatting, or mapping software

-   Hardware/communications network requirements

    Information sources for these topics can be found in the reference
    listings in Section 4.0.

[]{#__RefHeading___Toc507819256 .anchor}Figure 1‑1: Implementation Guide
Scope

![](media/image1.wmf)

## Associated Transaction Sets

The following transaction sets are associated with the TS 824 in a
Application Advice processing model, but are not addressed in this
Implementation Guide:

-   TS 284 (Commercial Vehicle Safety Reports): Provide the capability
    to request and report information relating to safe operations of
    commercial road vehicles.

```{=html}
<!-- -->
```
-   TS 285 (Commercial Vehicle Safety and Credentials Information
    Exchange): Provide standard, pre-defined messages among stakeholders
    to communicate CVO-related information and to allow computers to
    process safety and credential data.

-   TS 997 (Functional Acknowledgment): Acknowledge receipt of message.
    Communicate syntax problems in received message.

Note: EDI Implementation Guides for TS 285, Commercial Vehicle Safety
and Credentials Information Exchange, and TS 284, Commercial Vehicle
Safety Reports, are contained in separate volumes. (See references
\[21\] and \[24\] in Section 4.3.)

## Responsible Organizations

A partnership of organizations will be responsible for the development
and maintenance of this implementation guide, and for supporting
requester and source implementation of safety report and
credential-related transactions. These organizations and their roles
are:

[Federal Motor Carrier Safety Administration]{.underline} - Direct and
fund the development of ANSI ASC X12 format transaction sets and
associated documentation to support Commercial Vehicle Operations under
the ITS/CVISN architecture, and to encourage their use in commercial
vehicle operations nationwide.

[American National Standards Institute Accredited Standard Committee
X12]{.underline} -- Develop, maintain, interpret, publish, and promote
the proper use of American national standards and UN/EDIFACT
international standards for electronic data interchange.

[The Johns Hopkins University Applied Physics Laboratory]{.underline} -
Develop and maintain transaction sets and prepare or coordinate the
preparation of related documentation for the electronic data interchange
of all safety related information and credentials associated with
commercial vehicle operations under a contract with FMCSA for
development of an architecture for Commercial Vehicle Information
Systems and Networks (CVISN) and the Safety and Fitness Electronic
Records (SAFER) System.

The activities of the organizations (carriers and states/jurisdictions)
that will use the 824 transactions described in this guide are
identified in Section 2.0.

# BUSINESS ISSUES

## Business Case

The Application Advice Transaction Set (824) provides the ability to
report the results of an application system\'s data content edits of
received transaction sets. It is designed to accommodate the business
need of reporting back to the sender 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). The 824 Transaction Set may be
used to report editing results at the functional group and the
transaction level in either coded or free-form format. The 824 shall not
be used to report syntax errors; TS 997 shall be used for that purpose.

The data flows associated with an Application Advice are summarized in
Figure 2-2 as part of the Commercial Vehicle Information Systems and
Networks (CVISN) architecture. The interface diagrams in Appendix A
provide users with a high-level perspective on the major interfaces
among users of the 824.

The 824 is one of several EDI transaction sets included as part of the
CVISN project. CVISN is a Department of Transportation/Federal Motor
Carrier Safety Administration project that is generally concerned with
applying technology to improve the safety and efficiency of North
American commercial vehicle operations. The CVISN design has identified
EDI as a key to communicating data related to commercial vehicles and
their operations via open standards and transmission options. This
includes the electronic exchange of safety and credential related
information.

The transaction set is designed primarily for use in fully integrated
business system environments to automate application system detected
error notification to the sender. For the process to be successful, the
trading partners must reach agreement as to the timing and routing of
the manual response following receipt of the 824. These requirements
will likely vary based on whether or not the transaction was rejected or
accepted with error.

In a manual error response environment, EDI transactions are received
and processed in the receiver\'s application system. Errors are detected
and identified for follow-up resolution, which may include manual
notification to the EDI transaction sender.

In an integrated system environment, error conditions pertinent to the
sender could be automatically passed from the application process to the
EDI process and sent as a \'negative\' 824 to the EDI transaction
sender. If no error conditions are found as a result of processing the
incoming transaction, a response could be automatically passed from the
application process to the EDI process and sent as a \'positive\' 824 to
the EDI transaction sender. In both cases, this would minimize or
eliminate the need for manual notification of the EDI transaction
sender.

Within CVISN, this transaction set is used to transmit relevant
application processing information between entities. It provides a
positive or negative acknowledgment for transactions that result in
substantive changes (updates) to the receiving database and it reports
unusual conditions or results that an application detects during
transaction processing (queries and query responses). Reporting shall be
done at the transaction set level, i.e., a single 824 transaction shall
not be used to report the processing results of more than one received
transaction set.

### TS 824 Users

-   SAFER (Safety and Fitness Electronic Records) is a federal data
    repository tasked with assembling and forwarding safety and
    credentials data to authorized parties.

-   State Systems:

-   CVIEW (Commercial Vehicle Information Exchange Window) is a
    state-based electronic data exchange system that provides carrier,
    vehicle, and driver safety and credential information to fixed and
    mobile roadside inspection stations, state agencies, and other third
    party users.

-   Roadside Systems

-   Roadside Operations Computer (ROC) - CVIEW State

-   Roadside Operations Computer (ROC) - non CVIEW State

-   Other Users:

-   Motor carriers

-   Insurance Agencies

-   Clearinghouses

This guide provides implementation conventions for using the 824
transaction set to exchange data for:

  -------------------------------------------- ------------- -----------------------
  [Reporting Entity to Data                                  [Example]{.underline}
  Repository]{.underline}                                    

                                                             

  **Application Advice (Negative)**                          **1**

  **Application Advice (Positive)**                          **2**

                                                             
  -------------------------------------------- ------------- -----------------------

## Timing of Transactions

Transmissions shall include the date and time.

## Security

Where applicable, trading partners are responsible for following Federal
Information Processing Standards (FIPS) and other statutes relating to
computer security and privacy, including the Privacy Act of 1974. The
following documents provide guidance in these areas:

-   National Institute of Standards & Technology (NIST) FIPS (112) for
    passwords.

-   NIST Special Publication 800-9, \"Good Security Practices for
    Electronic Commerce, Including Electronic Data Interchange\"

## Acknowledgment Procedures

Received messages, except for the 997 transaction set, are uniformly
acknowledged with a 997 (Functional Acknowledgment) transaction set. The
location and nature of syntax errors in a received message are
communicated with a 997. Syntactic correctness means compliance with the
X12 standard specified in this document. Possible 997 codes indicating
accept or reject condition based on the syntax editing of the
transaction set:

  ---------- ------------------------------------------------------------
  **Code**   **Description**

  A          Accepted

  R          Rejected
  ---------- ------------------------------------------------------------

Messages received that are not in compliance with the appropriate
Implementation Guide, e.g., with elements or segments designated as
\"Not Used\" or unapproved codes, shall be acknowledged, if no syntax
errors are detected, with an 824. The 824 is also used to communicate
problems with the meaning and completeness (semantic content) of a
received message. However, a semantically incorrect 824 shall not be
acknowledged with a 824. For specific interface control information see
References \[22\] and \[23\] in Section 4.3.

## Legal Considerations

Legal considerations for this implementation include:

[Recordkeeping]{.underline} - Consider the legal issues when developing
policies and procedures for the recording of EDI data.

[Authentication]{.underline} - Verify the authenticity of the sender and
receiver, as well as the content of the messages.

[Trading Partner Agreements]{.underline} - Address the importance of
trading partner agreements. Identify other related selected issues that
should be considered when drafting an agreement. Trading partners are
bound by the terms and conditions in this agreement and its included
regulations. A model trading partner agreement (See Reference \[10\]
under Section 4.1) has been developed by the American Bar Association
(ABA) and addresses the major issues when using EDI. This model
agreement may be customized to meet specific needs of trading partners.

[Third Party Agreements]{.underline} - Identify any issues that users
and networks should consider when negotiating EDI contracts.

[Laws, Rules, and Regulations]{.underline} - Consider existing laws,
rules, and regulations that should be consulted during implementation.

# MAINTENANCE SUPPORT

There are three areas of maintenance associated with EDI credential
transactions:

-   Implementation Guides

-   X12 Standards

-   External Code Sources

## Maintaining Implementation Guidelines

The FMCSA has directed the Johns Hopkins University Applied Physics
Laboratory to provide user support related to the Transaction Set 824
Implementation Guide. An Electronic Data Interchange Configuration
Control Board (EDI-CCB) has been established at JHU/APL to fulfill this
directive. Users shall submit business requirements not covered in this
document to:

A Change Request form is supplied in Figure 3-3 with directions for its
use given in Table 3-1. The request shall be reviewed by the EDI-CCB.
Refer to Figure 3-4 for the Change Resolution form and Table 3-2 for an
explanation of the form. Approved change requests shall be posted on the
CVO web site: <http://www.jhuapl.edu/cvisn/>.

## Maintaining X12 Standards

FMCSA is no longer sponsoring modifications to the ASC X12 Standards.
Any data maintenance to the standard may be submitted directly to X12
(see Reference \[6\]).

## Maintaining External Code Sources

Several segments in the TS 824 allow referencing external code sources
(e.g., documents specifying coded values for certain types of data). A
document (see Reference \[1\] in Appendix C) containing codes
specifically designed for EDI transmission of CVO data has been drafted
under auspices of the FMCSA. Modifications to this document shall be
submitted to the EDI-CCB. Modifications to other external codes shall be
submitted to the organization maintaining that document. See Appendix C
for these documents and sources.

CVISN Change Request Form

Change Request Date: CRF Number:

Requestor\'s Full Printed Name: Organization:

Requestor\'s Phone_Number: Extension:

Requestor\'s FAX_Number:

Requestor\'s E-Mail_Address:

Priority (as perceived by the originator):

Product: Attachments: (check box for yes)

Location where the change request was detected:

> If it is a software change, please provide the software package and
> build/version number. If it is a documentation change, please provide
> the document title, version, and date.

Title: Version No.: Date: TS #:

Title: Version No.: Date: TS #:

Part 1 of 5: CHANGE

(Describe the change requested below and attach additional pages if
necessary.

Please describe what you were doing and what you want changed. Use a new
form for each change

requested.)

Problem

+-------+----------------+---------------------------------------------+
| **N   | **Name**       | **Explanation**                             |
| ote** |                |                                             |
+=======+================+=============================================+
| A     | Change Request | The date the requestor submitted the change |
|       | Date, CRF      | request. The CRF Number is the change       |
|       | Number         | request form number assigned by the         |
|       |                | EDI-CCB.                                    |
+-------+----------------+---------------------------------------------+
| B     | Requestor      | Name, organization, and communication       |
|       | Information    | numbers of the requestor.                   |
+-------+----------------+---------------------------------------------+
| C     | Priority       | Request priority as specified by the        |
|       |                | requestor.                                  |
+-------+----------------+---------------------------------------------+
| D     | Product        | Specify \"EDI Standards and IGs\"           |
+-------+----------------+---------------------------------------------+
| D     | Attachments    | Specify if attachments are included.        |
+-------+----------------+---------------------------------------------+
| E     | Document and   | The name of this document shall be supplied |
|       | Transaction    | in **Title** and the draft or baseline      |
|       | Set Reference  | version number shall be supplied in         |
|       |                | **Version No**. The publication date of the |
|       |                | document shall be entered in the **Date**   |
|       |                | field. Supply the transaction set number in |
|       |                | **TS#**. If needed, information for the     |
|       |                | Code Directory may also be supplied in      |
|       |                | these fields.                               |
+-------+----------------+---------------------------------------------+
| F     | Change         | Please provide a complete business          |
|       |                | scenario. This shall include a textual      |
|       |                | description of the specific change          |
|       |                | requested, and may include one or more      |
|       |                | diagrams and examples.                      |
|       |                |                                             |
|       |                | 1.  X12 code additions: supply the Data     |
|       |                |     Element Reference Number, Name, the     |
|       |                |     proposed Code Value, the Definition and |
|       |                |     Explanation of the code, the segment to |
|       |                |     carry the code, and the intended usage. |
|       |                |                                             |
|       |                | 2.  Code Directory Code additions: supply   |
|       |                |     the Table Identifier, the proposed      |
|       |                |     Code, the Definition of the Code, and   |
|       |                |     an Explanation of its intended use.     |
|       |                |                                             |
|       |                | 3.  Code Directory Table additions: supply  |
|       |                |     the Table Name, the Purpose of the      |
|       |                |     table, Minimum and Maximum lengths of   |
|       |                |     Code, the Codes, a Definition for each  |
|       |                |     Code, and an Explanation of usage for   |
|       |                |     each Code.                              |
|       |                |                                             |
|       |                | For a new business need (a new credential   |
|       |                | action, safety report, etc.) the following  |
|       |                | shall also be provided:                     |
|       |                |                                             |
|       |                | 1.  Data elements: including name, type,    |
|       |                |     minimum/maximum length, definition,     |
|       |                |     requirement designation (mandatory,     |
|       |                |     optional), code values and external     |
|       |                |     code source, if any.                    |
|       |                |                                             |
|       |                | 2.  Data element relationships (one to one, |
|       |                |     one to many, etc.)                      |
|       |                |                                             |
|       |                | 3.  Flow diagrams with entities involved,   |
|       |                |     transaction sets used, sequence of data |
|       |                |     exchange for valid and invalid data     |
|       |                |     exchanges.                              |
+-------+----------------+---------------------------------------------+

  --------------- -------------------------------------------------------
  CR#:            

  CR Reference:   

  Submitted by:   

  Organization:   

  Resolution      
  Date:           
  --------------- -------------------------------------------------------

  ------------------------------------------------------------------------
  Title                 Version               Date             TS \#
  --------------------- --------------------- ---------------- -----------
                                                               

                                                               
  ------------------------------------------------------------------------

**Reason for Change:**

**Analysis**

  -------------------- --------------------------------------------------
  Category:            

  Impacts:             

  Analyst              

  Analysis date:       
  -------------------- --------------------------------------------------

**Resolution**:

+-------+----------------+---------------------------------------------+
| **N   | **Name**       | **Explanation**                             |
| ote** |                |                                             |
+=======+================+=============================================+
| A     | Release        | The **CR#** field specifies the Change      |
|       | Information    | Request number and the **CR Reference**     |
|       | and Requestor  | field cites other relevant change requests. |
|       | Information    | The **Submitted By** and **Organization**   |
|       |                | fields identify the submitter of the        |
|       |                | request. The **Resolution Date** is the     |
|       |                | date the change request was completed.      |
+-------+----------------+---------------------------------------------+
| B     | Document and   | Documents modified by this change are       |
|       | Transaction    | identified in the **Title, Version,** and   |
|       | Set Reference  | **Date** fields. Applicable transaction     |
|       |                | sets are given in the transaction set (**TS |
|       |                | \#**) fields.                               |
+-------+----------------+---------------------------------------------+
| C     | Reason for     | Provides the reason for change as submitted |
|       | Change         | by the requester.                           |
+-------+----------------+---------------------------------------------+
| D     | Analysis       | The **Category** field identifies the type  |
|       |                | of change, e.g., Enhancement, Error         |
|       |                | Correction. The **Impacts** field cites     |
|       |                | documents or applications affected by the   |
|       |                | change. The **Analyst** and **Analysis      |
|       |                | date** provides the name of the analyst and |
|       |                | the date the resolution was developed.      |
+-------+----------------+---------------------------------------------+
| E     | Resolution     | The **Resolution** of the Change Request is |
|       |                | provided in this field. A Resolution for    |
|       |                | this document shall include:                |
|       |                |                                             |
|       |                | 1.  A textual explanation of the            |
|       |                |     resolution, if needed.                  |
|       |                |                                             |
|       |                | 2.  For Implementation Guides the           |
|       |                |     Resolution shall include:               |
|       |                |                                             |
|       |                | -   The Section modified by the resolution  |
|       |                |     and the change to be implemented        |
|       |                |                                             |
|       |                | 3.  For the X12 Standard: the Data          |
|       |                |     Maintenance number assigned by X12      |
|       |                |     shall be cited, if known, for           |
|       |                |     modifications to the X12 Standard.      |
|       |                |                                             |
|       |                | 4.  For the Code Directory:                 |
|       |                |                                             |
|       |                | -   The Table modified by the resolution    |
|       |                |     and the change to be implemented.       |
|       |                |                                             |
|       |                | ```{=html}                                  |
|       |                | <!-- -->                                    |
|       |                | ```                                         |
|       |                | -   New Code Tables shall include the Table |
|       |                |     Identifier, the Table Name, the Purpose |
|       |                |     of the table, the Minimum and Maximum   |
|       |                |     lengths of the Code, the Code,          |
|       |                |     Definition and Explanation of the Code. |
+-------+----------------+---------------------------------------------+

# REFERENCES

The following list of references was compiled from documentation used in
the preparation of this implementation guide. The list also contains
documentation useful to those implementing an EDI transaction system,
for areas not within the scope of this guide.

Also visit the WWW site for the CVO Program at:

<http://www.jhuapl.edu/cvisn/>

## General EDI

1.  ASC X12D/W456, ASC X12 Guideline for Electronic Data Interchange,
    EDI Implementation Reference Manual Guidelines, Data Interchange
    Standards Association (DISA), dated February 1991

2.  Motor Carrier Industry Guide to Electronic Data Interchange
    Implementation and Conventions, Version/Release 003040, Management
    Systems Council of the American Trucking Association (ATA), dated
    July 1994

3.  Electronic Data Interchange X12 Standards Draft Version 4 Release 4,
    American National Standards Institute Accredited Standards Committee
    X12

4.  EDI: A Total Management Guide, Margaret A. Emmelhainz, Ph.D., Van
    Nostrand Reinhold, copyrighted 1993

5.  EDI: What Mangers Need to Know About the Revolution in Business
    Communications, Richard H. Baker, Tab Professional and Reference
    Books, copyrighted 1991

6.  Data Interchange Standards Association (DISA) Home Page:
    <http://www.disa.org/> DISA Reference Desk, Product Catalog,
    Internet Services

7.  Federal EDI Home Page: <http://snad.ncsl.nist.gov/dartg/edi/>

8.  Interpretation of X12.20 Functional Acknowledgment Transaction Set
    (997), ASC X12C/91-889, October 11, 1991

9.  Interpretation for Use and Relationship between the ISA and GS
    segments, ASC X12S/95-67, February 8, 1995

10. Model Electronic Data Interchange Trading Partner Agreement and
    Commentary, American Bar Association, The Business Lawyer, Vol. 45,
    June 1990, pp. 1717-1749

11. Electronic Data Interchange, Paul Kimberley, McGraw-Hill, Inc.,
    copyrighted 1991

## Hardware and Communications

12. Buyer\'s Guide to Electronic Commerce, eCommerce Strategies, Shaw
    Publishing, Inc.,
    [http://www.buyersguidetoecommerce.com](http://www.buyersguidetoecommerce.com/)

13. EDI Yellow Pages, Phillips Business Information, Inc., copyrighted
    1995

## ITS/CVO and Credential Transaction

14. Midwest Electronic One Stop Shopping System, Functional Requirements
    Document, American Association of Motor Vehicle Administrators
    (AAMVA) net, Inc., dated May 16, 1996

15. ANSI D20-1998, States\' Model Motorist Data Base, Data Element
    Dictionary, For Traffic Records Systems, American Association of
    Motor Vehicle Administrators (AAMVA), approved December 10, 1998

16. POR-96-6986, Commercial Vehicle Information Systems and Networks
    (CVISN), EDI Interface Requirements, Draft, The Johns Hopkins
    University Applied Physics Laboratory, dated May 31, 1996

17. POR-95-6982, CVISN Statement of Direction (SOD) and Program
    Overview/Introduction to CVISN, The Johns Hopkins University Applied
    Physics Laboratory, dated December 28, 1995

18. POR-96-6989, CVISN Operational Concept Document (OCD), The Johns
    Hopkins University Applied Physics Laboratory, dated June 28, 1996

19. POR-96-6985, CVISN Architecture Specification, The Johns Hopkins
    University Applied Physics Laboratory, dated March 29, 1996

20. PL-96-0178, ITS/CVO Project Plan for CVISN EDI Standards Development
    and Deployment, The Johns Hopkins University Applied Physics
    Laboratory, dated April 16, 1996

21. POR-96-6995 V1.0, Electronic Data Interchange Implementation Guide
    for Commercial Vehicle Safety and Credentials Information Exchange
    Transaction Set 285, The Johns Hopkins University Applied Physics
    Laboratory, dated March 2001

22. POR-99-7129 D1.0, Safety and Fitness Electronic Records (SAFER)
    System Interface Control Document, Version 2.0, The Johns Hopkins
    University Applied Physics Laboratory, May 1999

23. POR-99-7195 D1.0, Commercial Vehicle Information Exchange Window
    (CVIEW) System Interface Control Document, The Johns Hopkins
    University Applied Physics Laboratory, May 1999

24. POR-99-7202 V1.0, Electronic Data Interchange Implementation Guide
    for Commercial Vehicle Safety Reports Transaction Set 284, Vol. I,
    The Johns Hopkins University Applied Physics Laboratory, dated March
    2001

# TRANSACTION SET

The following transaction set table reflects X12 Version 4 Release 4.
Segments marked \"N/U\" are not used in this application of the 824.
Page references provide the page within Section 6.0, Segment Usage, for
detailed information on each segment used.

## Overall Data Architecture

The 824 transaction set structure, descriptions of segments, data
elements, and valid codes are found in Section 6.0.

The 824 is divided into two (2) tables, Header and Detail.

### Header Table

The Header table (Table 1) provides information applicable to the entire
transaction. It:

-   Identifies the transaction set (ST segment)

-   Provides the purpose and identification numbers (BGN segment)

-   Identifies sender(s) and receiver(s) (N1 loop)

The purpose of the 824 is to respond to one (1) received transaction.

### Detail Table

The Detail table (Table 2) provides the acceptance status of the
received transaction and reports the edit status of each entity within a
received transaction through the OTI loop. An entity is a carrier,
driver, vehicle, subscription list, or a report. Two loops are
subordinate to the OTI: TED and LM. If errors were detected, the TED
loop provides specific errors associated with the received entity.
Errors are carried in free-form text and code format in the RED segment
at 2/0820. The LM loop carries coded information on the type of entity
received, the data view, and application acceptance advice. The Code
Directory is the source for the coded data.

## Transaction Set Table

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 35%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 8%" />
<col style="width: 2%" />
<col style="width: 1%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
<td colspan="2"></td>
<td colspan="8"><p><strong>824 Application Advice</strong></p>
<blockquote>
<p><strong>Functional Group=AG</strong></p>
<p>This X12 Transaction Set 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.,</p>
<p>purchase order acknowledgment sent in response to a purchase
order).</p>
</blockquote></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td><strong>Table1</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><strong>Page Ref</strong></td>
<td><strong>Note</strong></td>
<td><strong>Pos.No.</strong></td>
<td><p><strong>Seg.</strong></p>
<p><strong>ID</strong></p></td>
<td><strong>Name</strong></td>
<td><strong>Req. Des.</strong></td>
<td><strong>Max Use</strong></td>
<td></td>
<td></td>
<td><strong>Loop Repeat</strong></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><a href="#ST">12</a></td>
<td></td>
<td>0100</td>
<td>ST</td>
<td>Transaction Set Header</td>
<td>M</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td><a href="#BGN">13</a></td>
<td></td>
<td>0200</td>
<td>BGN</td>
<td>Beginning Segment</td>
<td>M</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>LOOP ID – N1</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"><strong>&gt;1</strong></td>
</tr>
<tr class="odd">
<td><a href="#N1">16</a></td>
<td></td>
<td>0300</td>
<td>N1</td>
<td>Name</td>
<td>O</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td></td>
<td>0400</td>
<td>N2</td>
<td>Additional Name Information</td>
<td>O</td>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>N/U</td>
<td></td>
<td>0500</td>
<td>N3</td>
<td>Address Information</td>
<td>O</td>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td></td>
<td>0600</td>
<td>N4</td>
<td>Geographic Location</td>
<td>O</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>N/U</td>
<td></td>
<td>0700</td>
<td>REF</td>
<td>Reference Identification</td>
<td>O</td>
<td>12</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td></td>
<td>0800</td>
<td>PER</td>
<td>Administrative Communications Contact</td>
<td>O</td>
<td>3</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td><strong>Table2</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><strong>Page Ref</strong></td>
<td><strong>Note</strong></td>
<td><strong>Pos.No.</strong></td>
<td><p><strong>Seg.</strong></p>
<p><strong>ID</strong></p></td>
<td><strong>Name</strong></td>
<td><strong>Req. Des.</strong></td>
<td><strong>Max Use</strong></td>
<td></td>
<td></td>
<td><strong>Loop Repeat</strong></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>LOOP ID – OTI</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"><strong>&gt;1</strong></td>
</tr>
<tr class="even">
<td><a href="#OTI">18</a></td>
<td>N</td>
<td>0100</td>
<td>OTI</td>
<td>Original Transaction Identification</td>
<td>M</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>N/U</td>
<td>N</td>
<td>0200</td>
<td>REF</td>
<td>Reference Identification</td>
<td>O</td>
<td>12</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td>N</td>
<td>0300</td>
<td>DTM</td>
<td>Date/Time Reference</td>
<td>O</td>
<td>2</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td>N/U</td>
<td>N</td>
<td>0400</td>
<td>PER</td>
<td>Administrative Communications Contact</td>
<td>O</td>
<td>3</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td>N</td>
<td>0500</td>
<td>AMT</td>
<td>Monetary Amount</td>
<td>O</td>
<td>&gt;1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><a href="#QTY_20600">21</a></td>
<td>N</td>
<td>0600</td>
<td>QTY</td>
<td>Quantity</td>
<td>O</td>
<td>&gt;1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td>N</td>
<td>0650</td>
<td>NM1</td>
<td>Individual or Organization Name</td>
<td>O</td>
<td>9</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>LOOP ID – TED</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>&gt;1</strong></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><a href="#TED_20700">22</a></td>
<td></td>
<td>0700</td>
<td>TED</td>
<td>Technical Error Description</td>
<td>O</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td></td>
<td>0800</td>
<td>NTE</td>
<td>Note/Special Instructions</td>
<td>O</td>
<td>100</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><a href="#RED_20820">24</a></td>
<td>N</td>
<td>0820</td>
<td>RED</td>
<td>Related Data</td>
<td>O</td>
<td>100</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>LOOP ID – LM</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>&gt;1</strong></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td><a href="#LM_20850">26</a></td>
<td>N</td>
<td>0850</td>
<td>LM</td>
<td>Code Source Information</td>
<td>O</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>LOOP ID – LQ</strong></td>
<td></td>
<td></td>
<td></td>
<td><strong>100</strong></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><a href="#LQ_20860">27</a></td>
<td></td>
<td>0860</td>
<td>LQ</td>
<td>Industry Code</td>
<td>M</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td>N/U</td>
<td>N</td>
<td>0870</td>
<td>RED</td>
<td>Related Data</td>
<td>O</td>
<td>100</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td><a href="#SE">28</a></td>
<td></td>
<td>0900</td>
<td>SE</td>
<td>Transaction Set Trailer</td>
<td>M</td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td colspan="2"></td>
</tr>
</tbody>
</table>

NOTES

  -------- ----------------------------------------------------------------
  2/0100   The OTI loop is intended to provide a unique identification of
           the transaction set that is the subject of this application
           acknowledgment.

  2/0200   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.

  2/0300   The DTM segment allows for the provision of date, time, or date
           and time information required to uniquely identify the original
           transaction set.

  2/0400   The PER segment should be utilized if administrative
           communications contact information is important to the unique
           identification of the original transaction set.

  2/0500   The AMT segment should be utilized if monetary amount
           information is important to the unique identification of the
           original transaction set.

  2/0600   The QTY segment should be utilized if quantity information is
           important to the unique identification of the original
           transaction set.

  2/0650   The NM1 segment allows for the provision of entity
           identification information required to uniquely identify the
           original transaction set.

  2/0820   The RED segment may be used to provide data related to the error
           condition specified in the associated TED01 element.

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

  2/0870   The RED segment may be used to provide data related to the error
           condition specified in the associated LQ02 element.
  -------- ----------------------------------------------------------------

# SEGMENT USAGE

Segment usage includes segment characteristics, identification of data
elements used, and usage notes. A single segment usage guide for the
transaction (in **bold** text) is given in this section. Specific
examples are provided in Section 7.0.

  -------------------------------------------- ------------- -----------------------
  [Reporting Entity to Data                                  [Example]{.underline}
  Repository]{.underline}                                    

                                                             

  **Application Advice (Negative)**                          **1**

  **Application Advice (Positive)**                          **2**

                                                             
  -------------------------------------------- ------------- -----------------------

## X12 Control Segment Usage

The 824 Transaction Set is transmitted within the communication/envelope
ISA, GS, GE, and IEA segments. The Interchange Control Header (ISA) and
Functional Group Header (GS) are shown as the first two control segments
in this SEGMENT USAGE section. The Functional Group Trailer (GE) and
Interchange Control Trailer (IEA) are the final two control segments in
the sequence.

The relationship of the control segments in a typical EDI transmission
structure is shown in Figure 6-5.

> ![](media/image2.wmf){width="5.165972222222222in"
> height="6.738888888888889in"}

Source: [EDI X12 Standards]{.underline}, Version 4 Release 4, published
December 2000

## Implementation Convention Segment Usage

Figure 6-6 provides an explanation to the information presented in the
Segment Usage section of this document. Table 6-3 provides explanations
for the lettered notes. Segments are presented in the Segment Usage
section in the order they appear in the transaction set.

**Note:** Segments marked as \"N/U\" (not used) in the transaction set
table do not appear in this Segment Usage.

**DTM ‑ Date/Time Reference**

To specify pertinent dates and times

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/0300           OTI                 Optional               2
  ---------------- ------ ------------ ---------------------- --------------

If a time (DTM03) is provided, a time code (DTM04) is required.

**EXAMPLE:** DTM\*196\*19990301\*0100\*ET\~

Inspection Start Date (code 196) with Eastern Time (code ET)

**Data Element Summary**

[Ref Ele ID Name RPT Attributes]{.underline}

**01 374 Date/Time Qualifier M ID 3/3**

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**           **824 Usage**
  ---------- -------------------------------------- ------------------------
  196        Start                                  Inspection Start

  --------------------------------------------------------------------------

02 373 Date X DT 8/8

03 337 Time X TM 4/8

> Time expressed in 24-hour clock time as follows: HHMM
>
> where H = hours (00-23), M = minutes (00-59)
>
> If present, DTM04 is required

03 04 623 Time Code O ID 2/2

Any code in the X12 standard for the element

05 05 1250 Date Time Period Format Qualifier X ID 2/3

Not used

06 06 1251 Date Time Period X AN 1/35

Not used

**SYNTAX NOTES**

02 R020305 ‑ At least one of DTM02, DTM03 or DTM05 is required.

04 C0403 - If DTM04 is present, then DTM03 is required.

06 P0506 ‑ If either DTM05 or DTM06 is present, then the other is
required.

+-------+----------------+---------------------------------------------+
| **N   | **Name**       | **Explanation**                             |
| ote** |                |                                             |
+=======+================+=============================================+
| A     | Segment        | A two or three alphanumeric identifier of   |
|       | Identifier     | the segment as given in the X12 standard.   |
+-------+----------------+---------------------------------------------+
| B     | Segment Name   | The name of the segment as given in the X12 |
|       |                | standard.                                   |
+-------+----------------+---------------------------------------------+
| C     | Segment        | An explanation of the intended use of the   |
|       | Purpose        | segment as given in the X12 standard.       |
+-------+----------------+---------------------------------------------+
| D     | Table/Position | This column specifies the position of the   |
|       |                | segment within the transaction set. The     |
|       |                | convention for segment position designation |
|       |                | is Table/Position. \"Table\" indicates a    |
|       |                | transaction set 'area\', a distinct section |
|       |                | of the transaction set. Table 1 is also     |
|       |                | called the 'Header\' section, Table 2 is    |
|       |                | the 'Detail\' section, and a summary        |
|       |                | section is Table 3. \"Position\" is a       |
|       |                | sequential number indicating the placement  |
|       |                | of the segment within a Table. The          |
|       |                | designation for this DTM segment is 2/0300. |
+-------+----------------+---------------------------------------------+
| E     | Loop           | If the segment is part of a loop structure, |
|       |                | the \"Loop\" column provides the Loop ID as |
|       |                | given in the X12 standard.                  |
+-------+----------------+---------------------------------------------+
| F     | Loop Repeat    | If the segment is the first segment of a    |
|       |                | loop structure, this column indicates the   |
|       |                | number of times the loop may occur as given |
|       |                | in the X12 standard.                        |
+-------+----------------+---------------------------------------------+
| G     | Requirement    | Designates the segment\'s use within the    |
|       | Designation    | transaction set as given in the X12         |
|       |                | standard. Mandatory means it must be used;  |
|       |                | Optional indicates it may be used.          |
+-------+----------------+---------------------------------------------+
| H     | Maximum Use    | The maximum occurrences of the segment at   |
|       |                | that position in the transaction set as     |
|       |                | given in the X12 standard.                  |
+-------+----------------+---------------------------------------------+
| I     | Segment Usage  | This section provides implementation notes  |
|       | Note           | for the use of the segment or for using     |
|       |                | elements within the segment. This section   |
|       |                | may also summarize how the segment is used  |
|       |                | for different iterations of an HL, LM/LQ,   |
|       |                | or other loop structures.                   |
+-------+----------------+---------------------------------------------+
| J     | Example        | The example demonstrates the functionality  |
|       |                | of the segment. The elements and codes used |
|       |                | reflect the application and conform to the  |
|       |                | usage specified in the Data Element         |
|       |                | Summary. An explanation following the       |
|       |                | Example is an English version of the data   |
|       |                | and codes used in the Example.              |
+-------+----------------+---------------------------------------------+
| K     | Ref            | The sequential number assigned by X12 to a  |
|       |                | data element within the segment.            |
+-------+----------------+---------------------------------------------+
| L     | Ele ID         | The Data Element Reference Number assigned  |
|       |                | by X12 to the data element. This number is  |
|       |                | used to find the element in the X12 Data    |
|       |                | Dictionary.                                 |
+-------+----------------+---------------------------------------------+
| M     | Name           | The name assigned by X12 for the data       |
|       |                | element.                                    |
+-------+----------------+---------------------------------------------+
| N     | RPT            | The number of times the element may be      |
|       |                | repeated in that position, as given in the  |
|       |                | X12 standard. **NOTE: this column is        |
|       |                | included [only]{.underline} when the        |
|       |                | segment contains a repeated data element.** |
+-------+----------------+---------------------------------------------+
| O     | Attributes     | The \"Attributes\" column has three fields. |
|       |                |                                             |
|       |                | 1.  The first indicates the requirement     |
|       |                |     designation of the element as given in  |
|       |                |     the X12 standard.                       |
|       |                |                                             |
|       |                | -   M: Mandatory, element must be used. A   |
|       |                |     **BOLD** font style is used for         |
|       |                |     mandatory elements.                     |
|       |                |                                             |
|       |                | -   O: Optional, element may be used        |
|       |                |                                             |
|       |                | -   X: Relational, element is used under    |
|       |                |     specified conditions given in the       |
|       |                |     syntax notes.                           |
|       |                |                                             |
|       |                | > Note: a \"Z\" in the requirement          |
|       |                | > designator column indicates a semantic    |
|       |                | > note exists for that data element.        |
|       |                |                                             |
|       |                | 2.  The second field specifies the data     |
|       |                |     element type as given in the X12        |
|       |                |     standard.                               |
|       |                |                                             |
|       |                | 3.  The last field provides the minimum and |
|       |                |     maximum length of the data element (the |
|       |                |     number of characters that may be        |
|       |                |     carried) type as given in the X12       |
|       |                |     standard.                               |
+-------+----------------+---------------------------------------------+
| P     | Approved Codes | The table specifies the codes approved for  |
|       |                | use. The \"Code\" and \"Definition &        |
|       |                | Explanation\" columns are taken from the    |
|       |                | X12 standard. The \"Usage\" column provides |
|       |                | guidance for the code use within the        |
|       |                | application. If any code may be used for    |
|       |                | the element, the following note appears:    |
|       |                | \"Any code in the X12 standard for this     |
|       |                | element\".                                  |
+-------+----------------+---------------------------------------------+
| Q     | Data Element   | Additional comments specific to the use of  |
|       | Implementation | the element within the application.         |
|       | Note           |                                             |
+-------+----------------+---------------------------------------------+
| R     | Data Element   | If the element is not used, the note \"Not  |
|       | Not Used Note  | Used\" is supplied.                         |
+-------+----------------+---------------------------------------------+
| S     | Segment Notes  | Syntax Notes, Semantic Notes, and Comments  |
|       |                | as given in the X12 standard.               |
+-------+----------------+---------------------------------------------+

**ISA - Interchange Control Header**

To start and identify an interchange of zero or more functional groups
and interchange-related control segments

Although this is a fixed length segment, data element separators are
used between data elements for consistency. The separator to be used in
the transmission is given by its first occurrence in the ISA segment
(the fourth character of the segment). The segment terminator to be used
in the transmission is given by its first occurrence in the ISA segment
(the character following the last data element of the segment). The use
of the asterisk, \"\*\", (data element separator), the colon, \":\",
(component element separator), the tilde, \"\~\", (segment terminator),
and the \"\^\", (repetition separator) are for illustration purposes
only.

A unique non-printable character shall be used for each separator and
terminator. The following table provides the characters that shall be
used.

  ----------------------------------------------------- -----------------
  **Field**                                             **HEX**

  Data Element Separator                                1D

  Component Element Separator                           1F

  Segment Terminator                                    1C

  Repetition Separator                                  1E
  ----------------------------------------------------- -----------------

**EXAMPLE:**
ISA\*00\*••••••••••\*00\*••••••••••\*01\*123456789••••••\*01\*

112233445••••••\*990821\*1000\*\^\*00404\*000000001\*0\*P\*:\~

This interchange has No Authorization Information Present (code 00) and
No Security Information Present (code 00) from Sender ID (code 01 = Duns
Number) 123456789 to Receiver ID (code 01 = Duns Number) 112233445. It
was created 8/21/1999 at 10 A.M. using repetition separator \"\^\" in
Version 4 Release 4 (00404) with control number 000000001. No
Interchange Acknowledgment Requested (code 0) is specified and usage
indicator 'P\' specifies a production mode of processing. The \":\" is
the component element separator. In the example the \"•\" character
indicates a space. These spaces are not truncated when the segment is
created because the fields are fixed length.

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01** **I01** **Authorization Information Qualifier M ID 2/2**

> Any code in the X12 standard for this element may be used to identify
> the type of information given in I02.

**02 I02 Authorization Information M AN 10/10**

**03 I03 Security Information Qualifier M ID 2/2**

Any code in the X12 standard for this element

**04 I04 Security Information M AN 10/10**

> Password shall be supplied if ISA03 is 01. The password must be agreed
> to by both sender and receiver.

**05 I05 Interchange ID Qualifier M ID 2/2**

> The following table provides commonly used codes to identify the
> Interchange Sender ID, I06.

+-------+---------------------------------------+---------------------+
| **C   | **Definition & Explanation**          | **824 Usage**       |
| ode** |                                       |                     |
+=======+=======================================+=====================+
| 01    | Duns (Dun & Bradstreet)               |                     |
+-------+---------------------------------------+---------------------+
| 02    | SCAC (Standard Carrier Alpha Code)    |                     |
+-------+---------------------------------------+---------------------+
| 12    | Phone                                 | No punctuation      |
+-------+---------------------------------------+---------------------+
| SA    | User Identification as assigned by    |                     |
|       | the Safety and Fitness Electronic     |                     |
|       | Records (SAFER) System                |                     |
|       |                                       |                     |
|       | [SEE CODE SOURCE 851]{.smallcaps}     |                     |
+-------+---------------------------------------+---------------------+

**06 I06 Interchange Sender ID M AN 15/15**

**07 I05 Interchange ID Qualifier M ID 2/2**

+-------+---------------------------------------+---------------------+
| **C   | **Definition & Explanation**          | **824 Usage**       |
| ode** |                                       |                     |
+=======+=======================================+=====================+
| 01    | Duns (Dun & Bradstreet)               |                     |
+-------+---------------------------------------+---------------------+
| 02    | SCAC (Standard Carrier Alpha Code)    |                     |
+-------+---------------------------------------+---------------------+
| 12    | Phone                                 | No punctuation      |
+-------+---------------------------------------+---------------------+
| SA    | User Identification as assigned by    |                     |
|       | the Safety and Fitness Electronic     |                     |
|       | Records (SAFER) System                |                     |
|       |                                       |                     |
|       | [SEE CODE SOURCE 851]{.smallcaps}     |                     |
+-------+---------------------------------------+---------------------+

**08 I07 Interchange Receiver ID M AN 15/15**

**09 I08 Interchange Date M DT 6/6**

**10 I09 Interchange Time M TM 4/4**

**11 I65 Repetition Separator M 1/1**

**12 I11 Interchange Control Version Number M ID 5/5**

> This is not the same Version Number as in the GS segment. It is for
> the envelope only.

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**             **824 Usage**
  ---------- ---------------------------------------- ----------------------
  00404      Draft Standards for Trial Use Approved   
             for Publication by ASC X12 Procedures    
             Review Board through October 2000        

  --------------------------------------------------------------------------

**13 I12 Interchange Control Number M N0 9/9**

> A control number assigned by the interchange sender
>
> The number shall uniquely identify the interchange over an extended
> time.

**14 I13 Acknowledgment Requested M ID 1/1**

> The TA1 is not supported; no acknowledgment shall be requested.

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**       **824 Usage**
  ---------- ---------------------------------- ----------------------------
  0          No Acknowledgment Requested        

  --------------------------------------------------------------------------

**15 I14 Usage Indicator M ID 1/1**

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**       **824 Usage**
  ---------- ---------------------------------- ----------------------------
  P          Production Data                    Used when in production mode

  T          Test Data                          Used when in test mode
  --------------------------------------------------------------------------

**16 I15 Component Element Separator M 1/1**

This shall be different from the data element separator.

**GS - Functional Group Header**

To indicate the beginning of a functional group and to provide control
information

**EXAMPLE:**
GS\*AG\*123456789ABCDE\*112233445566778\*19990821\*1020\*1\*X\*004040\~

Functional Group Application Advice (code AG) from Sender 123456789ABCDE
to Receiver 112233445566778 dated 8/21/1999 at 10:20 A.M. with control
number 1 and Responsible Agency Code Accredited Standards Committee X12
(code X) identifying transaction sets within this functional group to be
in Version 4 Release 4 (code 004040).

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 479 Functional Identifier Code M ID 2/2**

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**             **824 Usage**
  ---------- ---------------------------------------- ----------------------
  AG         Application Advice (824)                 

  --------------------------------------------------------------------------

**02 142 Application Sender\'s Code M AN 2/15**

A unique identifier for the sender agreed to by both sender and
receiver. Normally the same as ISA06, but may be used to identify
sub-organizations (department within a company, etc.)

**03 124 Application Receiver\'s Code M AN 2/15**

A unique identifier for the receiver agreed to by both sender and
receiver. Normally the same as ISA08, but may be used to identify
sub-organizations (department within a company, etc.)

**04 373 Date M\|Z DT 8/8**

**05 337 Time M\|Z TM 4/8**

> Time expressed in 24-hour clock time as follows: HHMM,
>
> where H = hours (00-23), M = minutes (00-59)

**06 28 Group Control Number M\|Z N0 1/9**

Assigned number originated and maintained by the sender

> The number shall, together with the application sender\'s and
> receiver\'s codes, be unique, within an extended time, to identify
> each functional group.

**07 455 Responsible Agency Code M ID 1/2**

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**             **824 Usage**
  ---------- ---------------------------------------- ----------------------
  X          Accredited Standards Committee X12       

  --------------------------------------------------------------------------

**08 480 Version/Release/Industry Identifier M AN 1/12**

**Code**

This is the version and release for the transaction sets within the
functional group; it is not the same as the version number given in
ISA12.

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**             **824 Usage**
  ---------- ---------------------------------------- ----------------------
  004040     Draft Standards for Trial Use Approved   
             for Publication by ASC X12 Procedures    
             Review Board through October 2000        

  --------------------------------------------------------------------------

SEMANTIC NOTES

  ---- ------------------------------------------------------------------
  04   GS04 is the group date.

  05   GS05 is the group time.

  06   The data interchange control number GS06 in this header must be
       identical to the same data element in the associated functional
       group trailer, GE02.
  ---- ------------------------------------------------------------------

COMMENTS

  ---- ------------------------------------------------------------------
  00   A functional group of related transaction sets, within the scope
       of X12 standards, consists of a collection of similar transaction
       sets enclosed by a functional group header and a functional group
       trailer.

  ---- ------------------------------------------------------------------

[]{#ST .anchor}**ST ‑ Transaction Set Header**

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

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  1/0100                               Mandatory              1
  ---------------- ------ ------------ ---------------------- --------------

**EXAMPLE:** ST\*824\*0001\*V1.0\~

Application Advice (824), unique control number (0001), and
implementation convention reference V1.0.

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 143 Transaction Set Identifier Code M\|Z ID 3/3**

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**             **824 Usage**
  ---------- ---------------------------------------- ----------------------
  824        Application Advice                       

  --------------------------------------------------------------------------

**02 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

03 1705 Implementation Convention Reference O\|Z AN 1/35

For this implementation convention, the reference is V1.0

SEMANTIC NOTES

  ---- ------------------------------------------------------------------
  01   The transaction set identifier (ST01) is used by the translation
       routines of the interchange partners to select the appropriate
       transaction set definition (e.g., 810 selects the Invoice
       Transaction Set).

  03   The implementation convention reference (ST03) is used by the
       translation routines of the interchange partners to select the
       appropriate implementation convention to match the transaction set
       definition.
  ---- ------------------------------------------------------------------

[]{#BGN .anchor}**BGN ‑ Beginning Segment**

To indicate the beginning of a transaction set

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  1/0200                               Mandatory              1
  ---------------- ------ ------------ ---------------------- --------------

This segment is used to:

• Indicate the purpose of the transaction set

• Provide a unique identification number for it

• Provide the date of the transaction set

If the transaction set time (BGN04) is provided, a Time Code (BGN05) is
required. Reference to a previous transaction set may also be given
(BGN06).

**EXAMPLE:** BGN\*11\*1016\*19991010\*1125\*ET\*54321\~

Response (code 11), sender control number (1016), transmission date
(10/10/1999), Eastern Time (code ET) 11:25, with a reference to a
previously sent transaction (54321).

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 353 Transaction Set Purpose Code M ID 2/2**

+-------+---------------------------+----------------------------------+
| **C   | **Definition &            | **824 Usage**                    |
| ode** | Explanation**             |                                  |
+=======+===========================+==================================+
| 11    | Response                  | Use to indicate:                 |
|       |                           |                                  |
|       |                           | -   Response to a previously     |
|       |                           |     sent transaction             |
+-------+---------------------------+----------------------------------+

**02 127 Reference Identification M\|Z AN 1/50**

**03 373 Date M\|Z DT 8/8**

04 337 Time X\|Z TM 4/8

> Time expressed in 24-hour clock time as follows: HHMM,
>
> where H = hours (00-23), M = minutes (00-59)

05 623 Time Code O\|Z ID 2/2

This is required if a time, (BGN04), is present.

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation** **824 Usage**
  ---------- ---------------------------- ----------------------------------
  10         Equivalent to ISO P10        Covers: Guam (Mariana Islands)
                                          (GMT + 1000) and Northern Mariana
                                          Islands (GMT + 1000)

  12         Equivalent to ISO P12        Covers: Wake Islands (GMT + 1200)

  14         Equivalent to ISO M11        Covers: American Samoa (GMT --
                                          1100) and Midway Islands (Leeward
                                          Islands, Hawaiian Chain) (GMT --
                                          1100)

  AD         Alaska Daylight Time         

  AS         Alaska Standard Time         

  AT         Alaska Time                  

  CD         Central Daylight Time        

  CS         Central Standard Time        

  CT         Central Time                 

  ED         Eastern Daylight Time        

  ES         Eastern Standard Time        Also covers: Navassa (Uninhabited)

  ET         Eastern Time                 

  HD         Hawaii-Aleutian Daylight     
             Time                         

  HS         Hawaii-Aleutian Standard     
             Time                         

  HT         Hawaii-Aleutian Time         

  MD         Mountain Daylight Time       

  MS         Mountain Standard Time       

  MT         Mountain Time                

  ND         Newfoundland Daylight Time   

  NS         Newfoundland Standard Time   

  NT         Newfoundland Time            

  PD         Pacific Daylight Time        

  PS         Pacific Standard Time        

  PT         Pacific Time                 

  TD         Atlantic Daylight Time       

  TS         Atlantic Standard Time       Also covers: Puerto Rico (GMT --
                                          0400) and Virgin Islands (GMT --
                                          0400)

  TT         Atlantic Time                
  --------------------------------------------------------------------------

06 127 Reference Identification O\|Z AN 1/50

Used to specify a previous transaction set reference identification
(sent in BGN02) when BGN01 is \"11\".

> Use is mandatory.

07 640 Transaction Type Code O ID 2/2

Not used

08 306 Action Code O ID 1/2

Not used

09 786 Security Level Code O ID 2/2

Not used

SYNTAX NOTES

  ------ ----------------------------------------------------------------
  05     C0504 ‑ If BGN05 is present, then BGN04 is required.

  ------ ----------------------------------------------------------------

SEMANTIC NOTES

  ---- ------------------------------------------------------------------
  02   BGN02 is the transaction set reference number.

  03   BGN03 is the transaction set date.

  04   BGN04 is the transaction set time.

  05   BGN05 is the transaction set time qualifier.

  06   BGN06 is the transaction set reference number of a previously sent
       transaction affected by the current transaction.
  ---- ------------------------------------------------------------------

[]{#N1 .anchor}**N1 ‑ Name**

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

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  1/0300           N1     \>1          Optional               1
  ---------------- ------ ------------ ---------------------- --------------

This N1 segment is used to provide details on the sender of the
transaction set. The name carried in this segment is a syntactical
entity. No guidance for parsing this entity shall be given.

**EXAMPLE:** N1\*41\*SAFER\*12\*8885555555\~

The name supplied is for the sender (code 41), a non-person entity (code
2) with telephone number (code 12).

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 98 Entity Identifier Code M ID 2/3**

+-------+---------------------------------+----------------------------+
| **C   | **Definition & Explanation**    | **824 Usage**              |
| ode** |                                 |                            |
+=======+=================================+============================+
| 41    | Submitter                       |                            |
|       |                                 |                            |
|       | *Entity transmitting            |                            |
|       | transaction set*                |                            |
+-------+---------------------------------+----------------------------+

02 93 Name X AN 1/60

03 66 Identification Code Qualifier X ID 1/2

Application dependent; applicable codes are in the following table.

+-------+---------------------------------+----------------------------+
| **C   | **Definition & Explanation**    | **824 Usage**              |
| ode** |                                 |                            |
+=======+=================================+============================+
| 12    | Telephone Number (Phone)        |                            |
+-------+---------------------------------+----------------------------+
| 40    | Electronic Mail User Code       |                            |
|       |                                 |                            |
|       | *Identifies the Electronic Mail |                            |
|       | User locally defined and        |                            |
|       | maintained between trading      |                            |
|       | partners*                       |                            |
+-------+---------------------------------+----------------------------+
| 56    | Division                        |                            |
+-------+---------------------------------+----------------------------+
| 57    | Department                      |                            |
+-------+---------------------------------+----------------------------+

04 67 Identification Code X AN 2/80

05 706 Entity Relationship Code O D 2/2

Not used

06 98 Entity Identifier Code O ID 2/3

Not used

SYNTAX NOTES

  ----- -----------------------------------------------------------------
  02    R0203 - At least one of N102 or N103 is required.

  03    P0304 - If either N103 or N104 is present, then the other is
        required.
  ----- -----------------------------------------------------------------

**COMMENTS**

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

  05   N105 and N106 further define the type of entity in N101.
  ---- ------------------------------------------------------------------

[]{#OTI .anchor}**OTI** **- Original Transaction Identification**

To 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

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/0100           OTI    \>1          Mandatory              1
  ---------------- ------ ------------ ---------------------- --------------

**EXAMPLE:** OTI\*IR\*2I\*Track Number 102\*\*\*\*\*\*\*285\~

Application Acknowledgment Code is Item Reject (code IR) with tracking
number (code 2I) and transaction set identifier (285).

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 110 Application Acknowledgment Code M ID 1/2**

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation** **824 Usage**
  ---------- ---------------------------- ----------------------------------
  IR         Item Reject                  

  TA         Transaction Set Accept       

  TP         Transaction Set Partial      
             Accept/Reject                

  TR         Transaction Set Reject       
  --------------------------------------------------------------------------

**02 128 Reference Identification Qualifier M ID 2/3**

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation** **824 Usage**
  ---------- ---------------------------- ----------------------------------
  2I         Tracking Number              Previously sent tracking number.
                                          Used when OTI01 is \"IR\".

  TN         Transaction Reference Number Previously sent transaction
                                          reference number. Used when OTI01
                                          is \"TA\", \"TP\", or \"TR\".
  --------------------------------------------------------------------------

**03 127 Reference Identification M/Z AN 1/50**

04 142 Application Sender\'s Code O AN 2/15

Not used

05 124 Application Receiver\'s Code O AN 2/15

Not used

06 373 Date O/Z DT 8/8

Not used

07 337 Time O/Z TM 4/8

Not used

08 28 Group Control Number X N0 1/9

Not used

09 329 Transaction Set Control Number O AN 4/9

Not used

10 143 Transaction Set Identifier Code O ID 3/3

  --------------------------------------------------------------------------
  **Code**   **Definition & Explanation**       **824 Usage**
  ---------- ---------------------------------- ----------------------------
  284        Commercial Vehicle Safety Reports  

  285        Commercial Vehicle Safety and      
             Credentials Information Exchange   
  --------------------------------------------------------------------------

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

Not used

12 353 Transaction Set Purpose Code O/Z ID 2/2

Not used

13 640 Transaction Type Code O/Z ID 2/2

Not used

14 346 Application Type O/Z ID 2/2

Not used

15 306 Action Code O/Z ID 1/2

Not used

16 305 Transaction Handling Code O/Z ID 1/2

Not used

17 641 Status Reason Code O/Z ID 3/3

Not used

SYNTAX NOTES

  ------ ----------------------------------------------------------------
  09     C0908 - If OTI09 is present, then OTI08 is required.

  ------ ----------------------------------------------------------------

SEMANTIC NOTES

  ---- ------------------------------------------------------------------
  03   OTI03 is the primary reference identification or number used to
       uniquely identify the original transaction set.

  06   OTI06 is the group date.

  07   OTI07 is the group time.

  11   If OTI11 is present, it will contain the version/release under
       which the original electronic transaction was translated by the
       receiver.

  12   OTI12 is the purpose of the original transaction set, and is used
       to assist in its unique identification.

  13   OTI13 is the type of the original transaction set, and is used to
       assist in its unique identification.

  14   OTI14 is the application type of the original transaction set, and
       is used to assist in its unique identification.

  15   OTI15 is the type of action indicated or requested by the original
       transaction set, and is used to assist in its unique
       identification.

  16   OTI16 is the action requested by the original transaction set, and
       is used to assist in its unique identification.

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

COMMENTS

  ---- ------------------------------------------------------------------
  02   OTI02 contains the qualifier identifying the business transaction
       from the original business application, and OTI03 will contain the
       original business application identification.

  04   If used, OTI04 through OTI08 will contain values from the original
       electronic functional group generated by the sender.

  09   If used, OTI09 through OTI10 will contain values from the original
       electronic transaction set generated by the sender.
  ---- ------------------------------------------------------------------

[]{#QTY_20600 .anchor}**QTY ‑ Quantity**

To specify quantity information

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/0600           OTI                 Optional               \>1
  ---------------- ------ ------------ ---------------------- --------------

The QTY segment provides totals for transaction entities received,
approved and disapproved.

**EXAMPLE:** QTY\*87\*100\~

Total number of items received (code 87) is 100.

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 673 Quantity Qualifier M ID 2/2**

+------+-------------------------+-------------------------------+----+
| **Co | **Definition &          | **824 Usage**                 | *  |
| de** | Explanation**           |                               | *O |
|      |                         |                               | TI |
|      |                         |                               | ** |
+======+=========================+===============================+====+
| 87   | Quantity Received       | Total number of items         | TA |
|      |                         | received for processing       |    |
|      |                         |                               | TP |
|      |                         |                               |    |
|      |                         |                               | TR |
+------+-------------------------+-------------------------------+----+
| QA   | Quantity Approved       | Total number of items with no | TA |
|      |                         | errors                        |    |
|      |                         |                               | TP |
+------+-------------------------+-------------------------------+----+
| QC   | Quantity Disapproved    | Total number of items with    | TP |
|      |                         | errors                        |    |
|      |                         |                               | TR |
+------+-------------------------+-------------------------------+----+

02 380 Quantity X R 1/15

03 C001 Composite Unit of Measure O

Not used

04 61 Free-Form Message X/Z AN 1/30

Not Used

SYNTAX NOTES

  ------- ---------------------------------------------------------------
  02      R0204 - At least one of QTY02 or QTY04 is required.

  02      E0204 - Only one of QTY02 or QTY04 may be present.
  ------- ---------------------------------------------------------------

SEMANTIC NOTES

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

  ------- ---------------------------------------------------------------

[]{#TED_20700 .anchor}**TED - Technical Error Description**

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

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/0700           TED    \>1          Optional               1
  ---------------- ------ ------------ ---------------------- --------------

**EXAMPLE:** TED\*NAU\~

The Application Error Condition Code is Not Authorized (code NAU)

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 647 Application Error Condition Code M ID 1/3**

  --------------------------------------------------------------------------------
  **Code**   **Definition &             **824 Usage**                    **OTI**
             Explanation**                                               
  ---------- -------------------------- -------------------------------- ---------
  007        Missing Data               Expected or required field(s)    IR
                                        not received                     

  011        Not Matching               No data matched query criteria   IR

  012        Invalid Combination        A combination of two or more     IR
                                        fields is inconsistent.          

  848        Incorrect Data             Invalid value for field. Used to IR
                                        identify fields not compliance   
                                        with appropriate Implementation  
                                        Guide.                           

  NAU        Not Authorized             User is either not authorized to IR
                                        receive the requested data or    
                                        the user is not authorized to    
                                        send an update.                  

  OTH        Other                                                       IR
  --------------------------------------------------------------------------------

02 3 Free Form Message O AN 1/60

Not used

03 721 Segment ID Code O ID 2/3

Not used

04 719 Segment Position in Transaction Set O N0 1/6

Not used

05 722 Element Position in Segment O N0 1/2

Not used

06 725 Data Element Reference Number O N0 1/4

Not used

07 724 Copy of Bad Data Element O AN 1/99

Not used

08 961 Data Element New Content O AN 1/99

Not used

COMMENTS

  ---- ------------------------------------------------------------------
  02   If used, TED02 will contain a generic description of the data in
       error (e.g., part number, date, reference number, etc.).

  ---- ------------------------------------------------------------------

[]{#RED_20820 .anchor}**RED - Related Data**

To provide business data related to an item within a transaction to
which a business application editing process has been applied, and an
error condition has resulted

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/0820           TED                 Optional               100
  ---------------- ------ ------------ ---------------------- --------------

**EXAMPLE:** RED\*Error description\*\*FH\*\*T25\*1001\~

Error related information with coded error data (code 1001) given in the
specific industry code list (T25) and the assigning agency (code FH).

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 352 Description M/Z AN 1/80**

Provides business data related to code given in RED06. It is recommended
a label be provided with the data.

02 1609 Related Data Identification Code X/Z ID 2/3

Not used

03 559 Agency Qualifier Code X/Z ID 2/2

+------+-------------------------+-------------------------------+----+
| **Co | **Definition &          | **824 Usage**                 | *  |
| de** | Explanation**           |                               | *O |
|      |                         |                               | TI |
|      |                         |                               | ** |
+======+=========================+===============================+====+
| FH   | Federal Highway         |                               | IR |
|      | Administration          |                               |    |
|      |                         |                               |    |
|      | [SEE CODE SOURCE        |                               |    |
|      | 534]{.smallcaps}        |                               |    |
+------+-------------------------+-------------------------------+----+

04 822 Source Subqualifier O/Z AN 1/15

Not used

05 1270 Code List Qualifier Code X/Z ID 1/3

  --------------------------------------------------------------------------------
  **Code**   **Definition &             **824 Usage**                    **OTI**
             Explanation**                                               
  ---------- -------------------------- -------------------------------- ---------
  T25        Safety and Fitness         Provides codes for errors        IR
             Electronic Record Systems  detected.                        
             Error Code                                                  

  --------------------------------------------------------------------------------

06 1271 Industry Code X/Z AN 1/30

See Code Source 534

SYNTAX NOTES

  ---- ------------------------------------------------------------------
  02   R0206 - At least one of RED02 or RED06 is required.

  02   E0206 - Only one of RED02 or RED06 may be present.

  03   P030506 - If either RED03, RED05 or RED06 are present, then the
       others are required.

  04   C0403 - If RED04 is present, then RED03 is required.
  ---- ------------------------------------------------------------------

SEMANTIC NOTES

  ---- ------------------------------------------------------------------
  01   RED01 provides the related business data, whose nature is defined
       by the code in RED02 or RED06.

  02   RED02 is an X12-defined code identifying the specific type of
       related data in RED01.

  03   RED03 identifies the agency maintaining the code list identified
       in RED05.

  04   RED04 provides further qualification of the agency identified in
       RED03.

  05   RED05 identifies the code list containing the code indicated in
       RED06.

  06   RED06 is an industry-defined code identifying the specific type of
       related data in RED01.
  ---- ------------------------------------------------------------------

COMMENTS

  ---- ------------------------------------------------------------------
  01   As an example of the use of the RED01 element, an application edit
       is applied to the Unit Price element within an Invoice (810)
       transaction set. The result of that edit indicates an invalid unit
       price. One piece of related business data would be the associated
       Product or Service Identification (data element #234). In this
       example, RED01 would be used to convey the associated Product or
       Service Identification.

  ---- ------------------------------------------------------------------

[]{#LM_20850 .anchor}**LM ‑ Code Source Information**

To transmit standard code list identification information

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/0850           LM     \>1          Optional               1
  ---------------- ------ ------------ ---------------------- --------------

With the **LQ** segment, this LM segment is used to identify the data to
which the current iteration of the LM loop relates.

**EXAMPLE:** LM\*FH\~

This example provides the code identifying the agency assigning the code
values (code FH = Federal Highway)

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 559 Agency Qualifier Code M ID 2/2**

+------+-------------------------+-------------------------------+----+
| **Co | **Definition &          | **824 Usage**                 | *  |
| de** | Explanation**           |                               | *O |
|      |                         |                               | TI |
|      |                         |                               | ** |
+======+=========================+===============================+====+
| FH   | Federal Highway         |                               | IR |
|      | Administration          |                               |    |
|      |                         |                               | TP |
|      | [SEE CODE SOURCE        |                               |    |
|      | 534]{.smallcaps}        |                               |    |
+------+-------------------------+-------------------------------+----+

02 822 Source Subqualifier O AN 1/15

Not used

COMMENTS

  ----- -----------------------------------------------------------------
  02    LM02 identifies the applicable industry code list source
        information.

  ----- -----------------------------------------------------------------

[]{#LQ_20860 .anchor}**LQ ‑ Industry Code**

Code to transmit standard industry codes

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/0860           LQ     100          Mandatory              1
  ---------------- ------ ------------ ---------------------- --------------

With the **LM** segment, this LQ segment is used to identify the data to
which the current iteration of the LM loop relates.

**EXAMPLE:** LQ\*T07\*Q105\~

This example specifies Carrier Snapshot View (code Q105) as given in the
specific industry code list (T07).

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

01 1270 Code List Qualifier Code O ID 1/3

This is required for the 824

+------+-------------------------+-------------------------------+----+
| **Co | **Definition &          | **824 Usage**                 | *  |
| de** | Explanation**           |                               | *O |
|      |                         |                               | TI |
|      |                         |                               | ** |
+======+=========================+===============================+====+
| T07  | View Parameters         | Codes to specify the contents | IR |
|      |                         | of a document, report or      |    |
|      | [See code source        | supporting item using the     |    |
|      | 534]{.smallcaps}        | Carrier, Driver and Vehicle   |    |
|      |                         | Data View Code Series         |    |
+------+-------------------------+-------------------------------+----+
| T25  | Safety and Fitness      | Codes to identify entity      | IR |
|      | Electronic Record       | (\"Entity\" Code Series) or   |    |
|      | Systems Error Code      | provide processing message    | TP |
|      |                         | (Entity-related Code Series). |    |
|      | [See code source        |                               |    |
|      | 534]{.smallcaps}        |                               |    |
+------+-------------------------+-------------------------------+----+

02 1271 Industry Code X AN 1/30

See Code Source 534

SYNTAX NOTES

  ------- ---------------------------------------------------------------
  01      C0102 ‑ If LQ01 is present, then LQ02 is required.

  ------- ---------------------------------------------------------------

[]{#SE .anchor}**SE ‑ Transaction Set Trailer**

To indicate the end of the transaction set and provide the count of the
transmitted segments (including the beginning (ST) and ending (SE)
segments).

  ---------------- ------ ------------ ---------------------- --------------
  Table/Position   Loop   Loop Repeat  Requirement            Maximum Use
                                       Designation            

  2/3900                               Mandatory              1
  ---------------- ------ ------------ ---------------------- --------------

**EXAMPLE:** SE\*20\*000010001\~

Indicates the end of the transaction set and provides the count (20) of
the transmitted segments (including the beginning (ST) and ending (SE)
segments) with control number 000010001 which is the same control number
as ST02.

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 96 Number of Included Segments M N0 1/10**

**02 329 Transaction Set Control Number M AN 4/9**

This must be the same number cited in ST02

COMMENTS

  ------- ---------------------------------------------------------------
  00      SE is the last segment of each transaction set.

  ------- ---------------------------------------------------------------

**GE - Functional Group Trailer**

To indicate the end of a functional group and to provide control
information

**EXAMPLE:** GE\*5\*1\~

Indicates the end of a functional group and provides the count of ST
segments (5) and a control number 1 which shall match GS06.

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 97 Number of Transaction Sets M N0 1/6**

**Included**

**02 28 Group Control Number M\|Z N0 1/9**

This must match GS06.

SEMANTIC NOTES

  ---- ------------------------------------------------------------------
  02   The data interchange control number GE02 in this trailer must be
       identical to the same data element in the associated functional
       group header, GS06.

  ---- ------------------------------------------------------------------

COMMENTS

  ---- ------------------------------------------------------------------
  00   The use of identical data interchange control numbers in the
       associated functional group header and trailer is designed to
       maximize functional group integrity. The control number is the
       same as that used in the corresponding header.

  ---- ------------------------------------------------------------------

**IEA - Interchange Control Trailer**

To define the end of an interchange of zero or more functional groups
and

interchange-related control segments

**EXAMPLE:** IEA\*3\*000000001\~

Defines the end of an interchange containing three (3) functional groups
and interchange-related control number 000000001 which matches ISA13.

**Data Element Summary**

[Ref Ele ID Name Attributes]{.underline}

**01 I16 Number of Included Functional M N0 1/5**

**Groups**

The number of GS segments within the transmission.

**02 I12 Interchange Control Number M N0 9/9**

This must match ISA13.

# EXAMPLE TRANSACTIONS

## Scope

This section shows examples of messages, based on the segment usage
guide in

Section 6.0, illustrating the use of TS 824 for interchanges among
users. The examples cover the following application advice functions (in
**bold** text):

  -------------------------------------------- ------------- -----------------------
  [Reporting Entity to Data                                  [Example]{.underline}
  Repository]{.underline}                                    

                                                             

  **Application Advice (Negative)**                          **1**

  **Application Advice (Positive)**                          **2**

                                                             
  -------------------------------------------- ------------- -----------------------

## Message Structures

Messages sent with the 824 use the OTI loop in Table 2 of the
transaction set to show looping relationships among blocks of data. The
examples shown below all use one looping structure to organize the data.
This structure is summarized in Figure 7-7. The diagram lists the
example messages using that structure.

## Message Type Indicators

Transaction set 824 is used to report the application edit results for a
received transaction. A received transaction set is either completely
accepted (positive advice) or is completely or partially rejected
(negative advice).

The Header Table in an 824 provides information applicable to the entire
transaction. It identifies the transaction set, its purpose, provides
identification numbers, and identifies sender(s) and receiver(s). In all
824 messages, BGN06 shall provide a cross-reference to the message being
edited. BGN06 echoes the transaction set reference identification
supplied by the sender in BGN02 of the original message.

The Detail Table contains information about the transaction and for a
negative advice, about entities within that transaction. Entities in a
285 transaction set are: Carrier, Vehicle, Driver, Subscription List.
The entities in a 284 transaction set are reports. Each instance of the
824 shall include one iteration of the OTI loop starting at 2/0100 to
identify the transaction being edited, to report the acceptance or
rejection of the transaction, and to report the entities received,
accepted, and rejected. The OTI segment, at 2/0100, carries the
acknowledgment code, the reference identification of the original
transaction (identifier from BGN02 of the original transaction), and the
transaction set identifier code (ST01 of the original transaction).
Multiple instances of the QTY segment at 2/0600 carry the total entities
received, accepted, and rejected.

When the 824 reports on errors found, additional iterations of the OTI
loop are used to report the rejection of entities within the received
transaction. The TED loop is used to specify the error condition(s). The
LQ loop is used to provide additional information about the entity, such
as the data view and entity type.

## Data Flow

Table 7-4 summarizes the segment elements and codes required in these
exchanges.

[]{#__RefHeading___Toc507819272 .anchor}Table 7‑4: Data Flow

+-----------+-----------+----------+----------+---------+------+------+
| **Data    | **Tran    | **       | **App    | **Re    | *    | **LQ |
| Flow**    | saction** | Previous | lication | ference | *TED | Lo   |
|           |           | TS       | Ack.     | ID      | Lo   | op** |
|           | **Set     | R        | Code     | Qu      | op** |      |
|           | Purpose   | eference | (        | alifier |      |      |
|           | (BGN01)** | ID       | OTI01)** | (O      |      |      |
|           |           | (        |          | TI02)** |      |      |
|           |           | BGN06)** |          |         |      |      |
+===========+===========+==========+==========+=========+======+======+
| Positive  | 11        | Used     | TA       | TN      | N/A  | N/A  |
| Advice    |           |          |          |         |      |      |
+-----------+-----------+----------+----------+---------+------+------+
| Negative  | 11        | Used     | TP,      | TN^1^   | N/   | N/   |
| Advice    |           |          | TR[^1]   |         | A^1^ | A^1^ |
|           |           |          |          | 2I ^2^  |      |      |
|           |           |          | IR[^2]   |         | Use  | Use  |
|           |           |          |          |         | d^2^ | d^2^ |
+-----------+-----------+----------+----------+---------+------+------+

## Example 1 -- Application Advice Negative

This example is intended to show the capability of the transaction and
may carry more data than is required for an Application Advice message.

The transaction purpose code (\"11\") in the BGN segment defines the
transaction as a response. The N1 loop at 1/0300 indicates the sender of
the transaction.

One iteration of the OTI loop provides the acceptance status of the
received transaction set. The code in OTI01 provides this status and the
OTI03 provides the reference identification of the original transaction.
OTI03 shall match BGN06. The Transaction Set Identifier Code of the
original transaction is carried in OTI10. The QTY segments in this loop
carry the number of entities received, accepted, and rejected.

One iteration of the OTI loop is generated for each entity. OTI03
carries the tracking number for the entity, as given in the original
transaction set, and the Transaction Set Identifier Code of the original
transaction is carried in OTI10. One or more RED segments are created to
provide further information for the \'error\' specified in the TED
segment. In this example, one OTI loop reports on the errors detected in
a received query. The TED segment indicates \'missing data\' and the RED
segments identify the data required. Another iteration of the OTI loop
reports the search results for a query. In this case, the query was
syntactically and semantically correct, but no data matched the
specified parameters.

The LM loop is used to provide additional information about the original
transaction set. This includes the entity and a Data View, if
applicable.

  ----------------------------------------------------------------------------------
  **SEGMENT : Loop ID : TS Table/Position**      **DEFINITION**
  ---------------------------------------------- -----------------------------------
  ST\*824\*000000001\*V1.0\~                     Application Advice transaction set
                                                 (824), unique control number
                                                 (000000001), and Implementation
                                                 Convention.

  BGN\*11\*TSREFID1\*19990226\*1430\*ET\*PRIOR   Response (code 11), sender control
  REF ID NUMBER 1\~                              number, transmission date
                                                 (02/26/1999) and Eastern Time (code
                                                 ET) 14:30 and a reference to a
                                                 previously sent transaction

  **LOOP ID - N1: 1/0300**                       **Sender**

  N1\*41\*SENDER NAME 100\*57\*DEPT\~            The name supplied is for the sender
                                                 (code 41 = Submitter) with sender
                                                 name, department (code 57) and
                                                 department number

  **LOOP ID - OTI: 2/0100**                      **Original Transaction
                                                 Identification**

  OTI\*TP\*TN\*PRIOR REF ID NUMBER               Application acknowledgment of
  1\*\*\*\*\*\*\*285\~                           Transaction Set Partial
                                                 Accept/Reject (code TP) with
                                                 Transaction Reference Number (code
                                                 TN) and transaction set identifier
                                                 (285)

  QTY\*87\*100\~                                 Quantity Received (code 87)

  QTY\*QA\*98\~                                  Quantity Approved (code QA)

  QTY\*QC\*2\~                                   Quantity Disapproved (code QC)

  **LOOP ID - OTI: 2/0100**                      **Original Transaction
                                                 Identification**

  OTI\*IR\*2I\*TRACK NUMBER                      Application acknowledgment of Item
  102\*\*\*\*\*\*\*285\~                         Reject (code IR) with Tracking
                                                 Number (code 2I) and Transaction
                                                 Set Identifier (285)

  **LOOP ID - TED: 2/0700**                      **Technical Error Description**

  TED\*007\~                                     Application error condition of
                                                 missing data (code 007)

  RED\*Missing DOT Number\*\*FH\*\*T25\*1001\~   Error description and agency
                                                 qualifier (code FH = FHWA), missing
                                                 DOT number (code 1001) as given in
                                                 the specific industry code list
                                                 (T25)

  RED\*Missing Issuing                           Error description and agency
  Authority\*\*FH\*\*T25\*1002\~                 qualifier (code FH), missing
                                                 issuing authority (code 1002) as
                                                 given in the specific industry code
                                                 list (T25)

  **LOOP ID - LM: 2/0850**                       **Code Source**

  LM\*FH\~                                       Code identifying the agency (code
                                                 FH = FHWA) assigning the code
                                                 values

  **LOOP ID - LQ: 2/0860**                       **View Parameters**

  LQ\*T07\*Q105\~                                This contains Carrier Snapshot
                                                 (code Q105) data as given in the
                                                 specific industry code list (T07)

  **LOOP ID - LQ: 2/0860**                       **View Parameters**

  LQ\*T25\*MC\~                                  This contains Motor Carrier (code
                                                 MC) data as given in the specific
                                                 industry code list (T25)

  **LOOP ID - OTI: 2/0100**                      **Original Transaction
                                                 Identification**

  OTI\*IR\*2I\*TRACK NUMBER                      Application acknowledgment of Item
  100\*\*\*\*\*\*\*285\~                         Reject (code IR) with Tracking
                                                 Number (code 2I) and Transaction
                                                 Set Identifier (285)

  **LOOP ID - TED: 2/0700**                      **Technical Error Description**

  TED\*011\~                                     Application error condition of Not
                                                 Matching (code 011)

  RED\*Snapshot not found\*\*FH\*\*T25\*1000\~   Error description and agency
                                                 qualifier (code FH = FHWA), the
                                                 requested snapshot was not found
                                                 (code 1000) as given in the
                                                 specific industry code list (T25)

  **LOOP ID - LM: 2/0850**                       **Code Source**

  LM\*FH\~                                       Code identifying the agency (code
                                                 FH = FHWA) assigning the code
                                                 values

  **LOOP ID - LQ: 2/0860**                       **View Parameters**

  LQ\*T07\*Q105\~                                This contains Carrier Snapshot
                                                 (code Q105) data as given in the
                                                 specific industry code list (T07)

  **LOOP ID - LQ: 2/0860**                       **View Parameters**

  LQ\*T25\*MC\~                                  This contains Motor Carrier (code
                                                 MC) data as given in the specific
                                                 industry code list (T07)

  SE\*xx\*000000001\~                            Transaction set trailer with the
                                                 number of segments (xx) and the
                                                 control number (000000001)
  ----------------------------------------------------------------------------------

## Example 2- Application Advice Positive

This example is intended to show the capability of the transaction and
may carry more data than is required for an Application Advice message.

The transaction purpose code (\"11\") in the BGN segment defines the
transaction as a response. The N1 loop at 1/0300 indicates the sender of
the transaction.

The only iteration of the OTI loop provides the acceptance status of the
received transaction set. The code in OTI01 provides this status and the
OTI03 provides the reference identification of the original transaction.
OTI03 shall match BGN06. The Transaction Set Identifier Code of the
original transaction is carried in OTI10. The QTY segments in this loop
carry the number of entities received and accepted.

  ----------------------------------------------------------------------------------
  **SEGMENT : Loop ID : TS Table/Position**      **DEFINITION**
  ---------------------------------------------- -----------------------------------
  ST\*824\*000000002\*V1.0\~                     Application Advice transaction set
                                                 (824), unique control number
                                                 (000000002), and Implementation
                                                 Convention.

  BGN\*11\*TSREFID2\*19990226\*1430\*ET\*PRIOR   Response (code 11), sender control
  REF ID NUMBER 2\~                              number, transmission date
                                                 (02/26/1999) and Eastern Time (code
                                                 ET) 14:30 and a reference to a
                                                 previously sent transaction

  **LOOP ID - N1: 1/0300**                       **Sender**

  N1\*41\*SENDER LAST 100\*57\*100\~             The name supplied is for the sender
                                                 (code 41 = Submitter) with sender
                                                 last name, department and
                                                 department number

  **LOOP ID - OTI: 2/0100**                      **Original Transaction
                                                 Identification**

  OTI\*TA\*TN\*PRIOR REF ID NUMBER               Application acknowledgment of
  2\*\*\*\*\*\*\*285\~                           Transaction Set Accept (code TA)
                                                 with Transaction Reference Number
                                                 (code TN) and transaction set
                                                 identifier (285)

  QTY\*87\*3\~                                   Quantity received (code 87)

  QTY\*QA\*3\~                                   Quantity approved (code QA)

  SE\*xx\*000000002\~                            Transaction set trailer with the
                                                 number of segments (xx) and the
                                                 control number (000000002)
  ----------------------------------------------------------------------------------

####### TRANSACTION FLOW

The following discussion describes several transaction sequences that
are typical of electronic data exchange. The Section A.1 describes
transaction flows when no syntax or data errors are encountered. The
Section A.2 illustrates the transaction flow when syntax errors are
found and Section A.3 covers data errors. Section A.4 describes an
unsuccessful query. All of the transaction sequences in this appendix
assume that appropriate trading partner agreements have been executed
and telecommunications methods and procedures are established. Example
transactions in Section 7.0 are associated with many of the arrows
labeled \"TS 824\" in the diagrams. All transmissions, except queries
and 997s, are acknowledged by return of a \"Functional Acknowledgment
(997)\" transaction.

######## Valid Transactions

######### Valid Query

The following diagram, Diagram A-1, provides the transaction flow
between a requester and a source when the source has all the data
required to satisfy the request and no syntax or data errors were
encountered with the query.

The transaction process begins when the sender transmits a 284 or 285
transaction set with the proper data for a query.

The receiver verifies the query\'s syntax, verifies the eligibility of
the sender to receive the information, and determines the processing
requirements specified by the transaction. In a fully functional
transaction processing environment this process can be completed in near
real time. In this exchange, the Query is NOT acknowledged with a TS
997. Once the transaction process is completed, the receiver transmits a
transaction back to the sender with the requested data. The sender may
optionally acknowledge this response with a TS 997.

[]{#__RefHeading___Toc507819263 .anchor}Diagram A‑1: Query With No
Syntax Or Data Errors

TS 284/285 Query

TS 284/285 Response

######### Valid Update

Diagram A-2 shows the transaction flow between a sender with data
updates (Add, Delete, Change, or Replace) and a receiver when no syntax
or data errors were encountered with the data update.

The transaction process begins when the sender transmits a 284 or 285
transaction set with the proper data for an update.

The receiver verifies the update\'s syntax, verifies the eligibility of
the sender to send the information, and determines the processing
requirements specified by the transaction. In a fully functional
transaction processing environment this process can be completed in near
real time. Once the transaction process is completed, the receiver
transmits a transaction back to the sender with the acceptance status of
the update. Acknowledgment via a TS 997 of the 285 update and the 824
acceptance is required in this exchange.

[]{#__RefHeading___Toc507819264 .anchor}Diagram A‑2: Update With No
Syntax Or Data Errors

######## Transactions with Syntax Errors

The simplest type of erroneous transmission is the case of syntax
errors. A syntax error is a specific failure to conform to the structure
of the known corresponding transaction set definition. Such a
transaction sequence is shown in Diagram A-3. The receiving system is
unable to recognize the data as being part of any transaction set, or
the transaction set ends abruptly with insufficient information to
characterize the missing data.

The transaction process begins when the sender transmits a syntactically
incorrect 824 transaction set.

In this exchange, the 824 received is acknowledged with a TS 997
specifying that a syntactically incorrect transmission was received
thereby notifying the sender that a retransmission is required. In all
transaction flow diagrams in this Appendix, whenever a TS 824 is sent,
there is the possibility of syntax errors. The sequence in this diagram
is applicable to all other transaction flow diagrams when this occurs.
When the 824 is corrected, processing proceeds as given in the other
diagrams.

[]{#__RefHeading___Toc507819265 .anchor}Diagram A‑3: Transaction With
Syntax Errors

TS 824

(Syntax error)

Corrected TS 824

######## Invalid Transactions

######### Invalid Query

More interesting errors may also occur, in which the erroneous
transaction is syntactically correct, but the request made is invalid. A
transmission may contain \"semantic\" errors, the message is readable,
but some data is inconsistent or missing. In such cases, the receiving
system can frequently provide information on the problem to the
requester. In such situations, a TS 824 is sent back to the sender with
descriptions of the problem provided. A straightforward example of such
an error would be failure to provide mandatory data items (e.g.,
omitting the PWK segment at the \"RP\" level for a TS 284). Diagram A-4
shows a transaction sequence in which the information source informs the
requester that a query does not have all the fields necessary to satisfy
the request. (This particular error would be caught by a well-designed
automated transaction system before the requester transmitted the
transaction. Of course, the source system cannot assume well-designed
software and sophisticated users on the requester side.)

The transaction process begins when the requester transmits a
transaction set without the proper data for a query.

The source verifies the query\'s syntax, verifies the eligibility of the
requester to receive the information, and determines the processing
requirements specified by the transaction. In a fully functional
transaction processing environment this process can be completed in near
real time. In this exchange, the Query is NOT acknowledged with a TS
997. The information source determines the query is not valid and sends
a TS 824 to the requester indicating the error(s) found. The requester
acknowledges the TS 824 with a TS 997 and then submits a correct query.
The query is NOT acknowledged via a TS 997. Once the transaction process
is completed, the source transmits a transaction back to the requester
with the requested data. The requester may optionally acknowledge this
response with a TS 997.

[]{#__RefHeading___Toc507819266 .anchor}Diagram A‑4: Invalid Query

TS 284/285 Query

(Data error)

TS 284/285 Response

######### Invalid Update

More interesting errors may also occur, in which the erroneous
transaction is syntactically correct, but the request made is invalid.
An update (Add, Delete, Change or Replace) transmission may contain
\"semantic\" errors, the message is readable, but some data is
inconsistent or missing. In such cases, the receiving system can
frequently provide information on the problem to the source. In such
situations, a TS 824 is sent back to the source with descriptions of the
problem provided. A straightforward example of such an error would be
failure to provide mandatory data items (e.g., omitting the PWK segment
at the \"RP\" level in a TS 284). Diagram A-5 shows a transaction
sequence in which the receiver informs the source that an update does
not have all the fields necessary. (This particular error would be
caught by a well-designed automated transaction system before the source
transmitted the transaction. Of course, the receiving system cannot
assume well-designed software and sophisticated users on the source
side.)

The transaction process begins when the source transmits a transaction
set without the proper data for an update.

The receiver verifies the update\'s syntax, verifies the eligibility of
the source to send the information, and determines the processing
requirements specified by the transaction. In a fully functional
transaction processing environment this process can be completed in near
real time. In this exchange, the receiver first returns a TS 997
acknowledging syntactical correctness, then determines the update is not
valid, and sends a TS 824 to the source indicating the error(s) found.
The source acknowledges the TS 824 with a TS 997, corrects the problem,
resubmits the transaction, and the transaction process proceeds. Once
the transaction process is completed, the receiver transmits a TS 824
transaction back to the source with the acceptance status of the update.
Acknowledgment via a TS 997 of the update and the TS 824 acceptance is
required in this exchange.

[]{#__RefHeading___Toc507819267 .anchor}Diagram A‑5: Invalid Update

TS 284/285 Update

(Data error)

TS 824 (negative)

^1^SAFER does not return a 997.

######## Unsuccessful Query

A query transmission may be syntactically and semantically correct, but
no data match the query parameters. In such situations, a TS 824 is sent
back to the requester with a message indicating no data were found.
Diagram A-6 shows the transaction sequence that occurs in such a case.

The transaction process begins when the requester transmits a
transaction set with the proper data for a query.

The source verifies the query\'s syntax, verifies the eligibility of the
to requester receive the information, and determines the processing
requirements specified by the transaction. In a fully functional
transaction processing environment this process can be completed in near
real time. In this exchange, the Query is NOT acknowledged with a TS
997. The receiver processes the request and returns a \'negative\' TS
824 with the result of the search. The requester acknowledges the TS 824
with a TS 997.

[]{#__RefHeading___Toc507819268 .anchor}Diagram A‑6: Unsuccessful Query

####### BACKGROUND INFORMATION

######## Related Sites and Resources

Following are a few hyperlinks provided for assistance in the initial
effort to address safety report processing issues.

**Note:** The Federal Highway Administration link has a \'Related
Sites\' link to access additional information.

Web Sites

-   [U.S. Department of Transportation - Federal Highway
    Administration](http://www.fhwa.dot.gov/) http://www.fhwa.dot.gov/

-   [Commercial Vehicle Information Systems and Networks
    (CVISN)](http://www.jhuapl.edu/cvisn/) http://www.jhuapl.edu/cvisn/

-   [Safety and Fitness Electronic Records System
    (SAFER)](http://www.safersys.org/) http://www.safersys.org/

####### CODE TABLE REFERENCES

The following list of code table references includes those documents
used in compiling the segment usage guide and examples in this document
(Section C.1), as well as references of potential use in 824
transactions (Section C.2). The complete list of codes for use in EDI
transaction sets can be found in [Electronic Data Interchange X12
Standards]{.underline}, Draft Version 4 Release 4. This document is
available from:

> Data Interchange Standards Association, Inc. (DISA)
>
> 333 John Carlyle Street, Suite 600
>
> Alexandria, VA 22314-5743
>
> 1-(888)-363-2334
>
> Web: <http://www.disa.org/>

######## X12 Cited Code Sources

1.  [Federal Motor Carrier Safety Administration Codes,]{.underline}
    (X12 Code Source 534): Contains alphanumeric codes for the exchange
    of information on the safety performance, regulatory compliance and
    credential status of commercial motor vehicles, carriers, and
    drivers.

Source: Federal Motor Carrier Safety Administration Code Directory

Available From:

> Federal Motor Carrier Safety Administration

Turner-Fairbanks Highway Research Center

6300 Georgetown Pike

McLean, VA 22101

Available from JHU/APL

2.  [Safety and Fitness Electronic Records (SAFER) User ID
    Number]{.underline}, (X12 Code Source 851): A unique number assigned
    by the Safety and Fitness Electronic Records (SAFER) system to
    uniquely identify trading partners as either the sender or receiver
    of a transmission.

> Source: Safety and Fitness Electronic Records (SAFER) User ID Number
>
> Available From:
>
> Department of Transportation
>
> Volpe Center
>
> Cambridge, MA 02142

######## Other Code Sources

3.  [National Zip Code and Post Office Directory]{.underline}, (X12 Code
    Source 22): Provides names, abbreviations, and codes for the 50
    states, the District of Columbia, and the outlying areas of the U.S.
    The entities listed are considered to be the first order divisions
    of the U.S.

> Source: National Zip Code and Post Office Directory
>
> Available From:
>
> U.S. Postal Service
>
> National Information Data Center
>
> P.O. Box 2977
>
> Washington, DC 20013

4.  [National Insurance Crime Bureau (NICB)]{.underline}, (X12 Code
    Source 213): Published annually, the manual provides VIN decoding
    for vehicles sold in the U.S. Each manual provides current plus last
    4 model years.

Source: Passenger Vehicle Identification Manual

Available From:

National Insurance Crime Bureau (NICB)

10330 South Roberts Road

Palls Hills, IL 60465

5.  [National Motor Freight Classification]{.underline}, (X12 Code
    Source 11): An identification code for commodities transported by
    motor carriers. The commodity code is a six-digit numeric of the
    form: dddddd. A seventh digit is added where necessary to indicate
    supplementary information such as density ranges, different forms of
    shipment, special packaging requirements, etc.

Source: National Motor Freight Classification, NMF 100 Series

Available From:

American Trucking Association

2200 Mill Road

Alexandria, VA 22314-4677

6.  Federal Information Publishing Standards (FIPS) Publication Number
    10-3, [Countries, Dependencies, Areas of Special Sovereignty, and
    Their Principal Administrative Divisions]{.underline}; National
    Institute of Standards and Technology, U.S. Department of Commerce,
    Change 14 dated February 8, 1993

> National Technical Information Service
>
> U.S. Department of Commerce
>
> Springfield, VA 22161

7.  [Vehicle Maintenance Reporting Standards Handbook (VMRS
    2000),]{.underline} (Code Source 95):

> This is the standard equipment maintenance management and parts
> inventory control information system of the motor carrier industry. It
> includes repair codes, system codes, assembly codes, part codes, part
> failure codes, reason for repair codes and other maintenance codes.

This is the recognized standard of the American Trucking Associations,
its Maintenance Council, and the manufacturers who use VMRS 2000 for
equipment identification.

Management Systems Council

American Trucking Association

2200 Mill Road

Alexandria, VA 22314-4677

8.  [Hazardous Materials Identification]{.underline}, DOT, Code of
    Federal Regulations, Transportation, Title 49, Parts 100 to 177,
    (X12 Code Source 52): Provides codes, names, and hazard classes for
    materials designated by the U.S. Department of Transportation as
    hazardous for purposes of transportation in commerce.

> [HazMat Code List]{.underline}, Code of Federal Regulations,
> Transportation, Title 49, Subchapter C, Sub Part B, Table of Hazardous
> Materials and Special Provisions, October 1, 1992 Version, Pages 120 -
> 238.

Superintendent of Documents

U.S. Government Printing Office

Washington, D.C. 20402

9.  [Identification Marking for Freight Containers]{.underline}, ISA
    2716-1972

American National Standards Institute

11 West 42^nd^ St., 13^th^ Floor

New York, NY 10036

10. [National Association of Insurance Commissioners (NAIC) Code List
    Manual]{.underline}, (Code Source 245): Codes that uniquely identify
    each insurance company.

National Association of Insurance Commissioners

Publications Department

12^th^ Street, Suite 1100

Kansas City, MO 64105-1925

11. [National Crime Information Center (NCIC) Reference
    Codes]{.underline}, (X12 Code Source 677): A Federal Bureau of
    Investigation maintained code reference vehicle make codes.

NCIC 2000 Product Development Team

National Crime Information Center NCIC

1000 - Custer Hollow Road

Clarksburg, WV 26306

12. [Codes for Representation of Names of Countries, ISO-3166-(Latest
    Release)]{.underline}, (X12 Code Source 5): Part 1 (Country codes)
    of the ISO 3166 international standard establishes codes that
    represent the current names of countries, dependencies, and other
    areas of special geopolitical interest, on the basis of lists of
    country names obtained from the United Nations.

> Source: Codes for Representation of Names of Countries, ISO
> 3166-(Latest Release)
>
> Available From:

American National Standards Institute

11 West 42^nd^ St., 13^th^ Floor

New York, NY 10036

####### DATA ITEM/SEGMENT CROSS-REFERENCE

Sections 1 and 2 of this appendix provide cross-reference tables
designating the mapping of data items to TS 824 segments and elements.
The following provides an explanation of the table column headings:

[]{#__RefHeading___Toc507819273 .anchor}Matrix D‑1: Data Item Matrix
Columns

  -----------------------------------------------------------------------
  **Column**                   **Description**
  ---------------------------- ------------------------------------------
  Table/Position               **Table** is the transaction set table.
                               For the 824, 1 indicates the Table 1
                               (Header table) and 2 indicates the Table 2
                               (Detail table). **Position** is the
                               relative position of the segment within
                               the transaction set table. Refer to
                               Section 5.2, 824 Transaction Set Table,
                               for table and segment position numbers.

  Segment/Element Number:Name  **Segment** is the name of the ASC X12
                               segment used to transmit the data element.
                               Element **Number** is the ASC X12
                               identification number for the data element
                               within the segment. **Name** is the ASC
                               X12 name of the data element.

  OTI                          Application acknowledgment code provided
                               in OTI01.

  LQ                           Code Directory table identifiers used in
                               this LQ loop (2/0860).

  Data Item                    Name for industry specific data or
                               information

  Comments                     An expanded definition of the data item or
                               additional information on its usage.
  -----------------------------------------------------------------------

######## Data Items in Transaction Set Order

**Purpose:** To provide an example of data carried for the 824
transaction set, not to specify data required by each transaction.

This table presents the usage of the segments and data items arrayed in
***Transaction Set Order (shaded).***

All information indicated by the LQ segment table number in these
transactions shall be considered to be contained in the Code Source
referenced by code 'FH\' in the LM segment unless otherwise specified.

+----+-------------------+----+-----+-------------------+---+---+-------+
|    |                   |    |     | > **Example**     | * | * |       |
|    |                   |    |     |                   | * | * |       |
|    |                   |    |     |                   | 1 | 2 |       |
|    |                   |    |     |                   | * | * |       |
|    |                   |    |     |                   | * | * |       |
+====+===================+====+=====+===================+===+===+=======+
| >  | > **Segment/      | >  | >   | > **Data Item**   | > | > | **    |
| ** | > Element No.:    |  * | **L |                   |   |   | Comme |
| Ta | > Name**          | *O | Q** |                   | * | * | nts** |
| bl |                   | TI |     |                   | * | * |       |
| e/ |                   | ** |     |                   | N | P |       |
| ** |                   |    |     |                   | e | o |       |
| >  |                   |    |     |                   | g | s |       |
| >  |                   |    |     |                   | a | i |       |
| ** |                   |    |     |                   | t | t |       |
| Po |                   |    |     |                   | i | i |       |
| s. |                   |    |     |                   | v | v |       |
| ** |                   |    |     |                   | e | e |       |
|    |                   |    |     |                   | * | * |       |
|    |                   |    |     |                   | * | * |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > ST01/143:       |    |     | > Transaction Set | X | X |       |
| 1/ | > Transaction Set |    |     | > ID              |   |   |       |
| 01 | > Identifier Code |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > ST02/329:       |    |     | > Transaction Set | X | X |       |
| 1/ | > Transaction Set |    |     | > Control Number  |   |   |       |
| 01 | > Control Number  |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > ST03/1705:      |    |     | > Implementation  | X | X |       |
| 1/ | > Implementation  |    |     | > Convention      |   |   |       |
| 01 | > Convention      |    |     | > Reference       |   |   |       |
| 00 | > Reference       |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN01/353:      |    |     | > Transaction Set | X | X |       |
| 1/ | > Transaction Set |    |     | > Purpose         |   |   |       |
| 02 | > Purpose Code    |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN02/127:      |    |     | > Transaction Set | X | X |       |
| 1/ | > Reference ID    |    |     | > Reference ID    |   |   |       |
| 02 |                   |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN03/373: Date |    |     | > Transaction Set | X | X |       |
| 1/ |                   |    |     | > Date Sent       |   |   |       |
| 02 |                   |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN04/337: Time |    |     | > Transaction Set | X | X |       |
| 1/ |                   |    |     | > Time Sent       |   |   |       |
| 02 |                   |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN05/623: Time |    |     | > Transaction Set | X | X |       |
| 1/ | > Code            |    |     | > Time Sent Time  |   |   |       |
| 02 |                   |    |     | > Code            |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN06/127:      |    |     | > Transaction Set | X | X |       |
| 1/ | > Reference ID    |    |     | > Previously Sent |   |   |       |
| 02 |                   |    |     | > Reference ID    |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > N101/98: Entity |    |     | > Sender Last     | X | X |       |
| 1/ | > Identifier Code |    |     | > Name,           |   |   |       |
| 03 | >                 |    |     | >                 |   |   |       |
| 00 | > N102/93: Name   |    |     | > Identification  |   |   |       |
|    | >                 |    |     | > Number          |   |   |       |
|    | > N103/66:        |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Code Qualifier  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > N104/67:        |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Code            |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > OTI01/110:      | >  |     | > Application     | X |   |       |
| 2/ | > Application     | IR |     | > Acknowledgment, |   |   |       |
| 01 | > Acknowledgment  |    |     | > Tracking        |   |   |       |
| 00 | > Code            |    |     | > Number, And     |   |   |       |
|    | >                 |    |     | > Transaction Set |   |   |       |
|    | > OTI02/128:      |    |     | > Identifier      |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Qualifier       |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI03/127:      |    |     |                   |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI10/143:      |    |     |                   |   |   |       |
|    | > Transaction Set |    |     |                   |   |   |       |
|    | > Identifier Code |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > OTI01/110:      | >  |     | > Application     |   | X |       |
| 2/ | > Application     | TA |     | > Acknowledgment, |   |   |       |
| 01 | > Acknowledgment  |    |     | > Transaction Set |   |   |       |
| 00 | > Code            |    |     | > Reference ID,   |   |   |       |
|    | >                 |    |     | > And Transaction |   |   |       |
|    | > OTI02/128:      |    |     | > Set Identifier  |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Qualifier       |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI03/127:      |    |     |                   |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI10/143:      |    |     |                   |   |   |       |
|    | > Transaction Set |    |     |                   |   |   |       |
|    | > Identifier Code |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > OTI01/110:      | >  |     | > Application     | X |   |       |
| 2/ | > Application     | TP |     | > Acknowledgment, |   |   |       |
| 01 | > Acknowledgment  |    |     | > Transaction Set |   |   |       |
| 00 | > Code            |    |     | > Reference ID,   |   |   |       |
|    | >                 |    |     | > And Transaction |   |   |       |
|    | > OTI02/128:      |    |     | > Set Identifier  |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Qualifier       |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI03/127:      |    |     |                   |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI10/143:      |    |     |                   |   |   |       |
|    | > Transaction Set |    |     |                   |   |   |       |
|    | > Identifier Code |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > QTY01/673:      | >  |     | > Quantity        |   | X |       |
| 2/ | > Quantity        | TA |     | > Received And    |   |   |       |
| 06 | > Qualifier       |    |     | > Approved        |   |   |       |
| 00 | >                 |    |     |                   |   |   |       |
|    | > QTY02/380:      |    |     |                   |   |   |       |
|    | > Quantity        |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > QTY01/673:      | >  |     | > Quantity        | X |   |       |
| 2/ | > Quantity        | TP |     | > Received,       |   |   |       |
| 06 | > Qualifier       |    |     | > Approved And    |   |   |       |
| 00 | >                 |    |     | > Disapproved     |   |   |       |
|    | > QTY02/380:      |    |     |                   |   |   |       |
|    | > Quantity        |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > TED01/647:      | >  |     | > Application     | X |   |       |
| 2/ | > Application     | IR |     | > Error Condition |   |   |       |
| 07 | > Error Condition |    |     |                   |   |   |       |
| 00 | > Code            |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > RED01/352:      | >  |     | > Application     | X |   |       |
| 2/ | > Description     | IR |     | > Error           |   |   |       |
| 08 | >                 |    |     | > Description,    |   |   |       |
| 20 | > RED03/559:      |    |     | > Agency          |   |   |       |
|    | > Agency          |    |     | > Qualifier And   |   |   |       |
|    | > Qualifier Code  |    |     | > Error Code      |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > RED05/1270:     |    |     |                   |   |   |       |
|    | > Code List       |    |     |                   |   |   |       |
|    | > Qualifier Code  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > RED06/1271:     |    |     |                   |   |   |       |
|    | > Industry Code   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > LM01/559:       | >  |     | > Agency          | X |   |       |
| 2/ | > Agency          | IR |     | > Qualifier       |   |   |       |
| 08 | > Qualifier Code  |    |     |                   |   |   |       |
| 50 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > LQ01/1270: Code | >  | >   | > Data View       | X |   |       |
| 2/ | > List Qualifier  | IR | T07 |                   |   |   |       |
| 08 | > Code            |    |     |                   |   |   |       |
| 60 | >                 |    |     |                   |   |   |       |
|    | > LQ02/1271:      |    |     |                   |   |   |       |
|    | > Industry Code   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > LQ01/1270: Code | >  | >   | > Entity          | X |   |       |
| 2/ | > List Qualifier  | IR | T25 |                   |   |   |       |
| 08 | > Code            |    |     |                   |   |   |       |
| 60 | >                 |    |     |                   |   |   |       |
|    | > LQ02/1271:      |    |     |                   |   |   |       |
|    | > Industry Code   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > SE01/96: Number |    |     | > Transaction Set | X | X |       |
| 2/ | > of Included     |    |     | > Number Of       |   |   |       |
| 39 | > Segments        |    |     | > Segments        |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > SE02/329:       |    |     | > Transaction Set | X | X |       |
| 2/ | > Transaction Set |    |     | > Control Number  |   |   |       |
| 39 | > Control Number  |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+

######## Data Items in Alphabetical Order

**Purpose:** To provide an example of data carried for the 824
transaction set, not to specify data required by each transaction.

This table presents the usage of the segments and data items arrayed in
***Alphabetical*** ***Data Item Order (shaded).***

All information indicated by the LQ segment table number in these
transactions shall be considered to be contained in the Code Source
referenced by code 'FH\' in the LM segment unless otherwise specified.

+----+-------------------+----+-----+-------------------+---+---+-------+
|    |                   |    |     | > **Example**     | * | * |       |
|    |                   |    |     |                   | * | * |       |
|    |                   |    |     |                   | 1 | 2 |       |
|    |                   |    |     |                   | * | * |       |
|    |                   |    |     |                   | * | * |       |
+====+===================+====+=====+===================+===+===+=======+
| >  | > **Segment/      | >  | >   | > **Data Item**   | > | > | **    |
| ** | > Element No.:    |  * | **L |                   |   |   | Comme |
| Ta | > Name**          | *O | Q** |                   | * | * | nts** |
| bl |                   | TI |     |                   | * | * |       |
| e/ |                   | ** |     |                   | N | P |       |
| ** |                   |    |     |                   | e | o |       |
| >  |                   |    |     |                   | g | s |       |
| >  |                   |    |     |                   | a | i |       |
| ** |                   |    |     |                   | t | t |       |
| Po |                   |    |     |                   | i | i |       |
| s. |                   |    |     |                   | v | v |       |
| ** |                   |    |     |                   | e | e |       |
|    |                   |    |     |                   | * | * |       |
|    |                   |    |     |                   | * | * |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > LM01/559:       | >  |     | > Agency          | X |   |       |
| 2/ | > Agency          | IR |     | > Qualifier       |   |   |       |
| 08 | > Qualifier Code  |    |     |                   |   |   |       |
| 50 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > OTI01/110:      | >  |     | > Application     | X |   |       |
| 2/ | > Application     | IR |     | > Acknowledgment, |   |   |       |
| 01 | > Acknowledgment  |    |     | > Tracking        |   |   |       |
| 00 | > Code            |    |     | > Number, And     |   |   |       |
|    | >                 |    |     | > Transaction Set |   |   |       |
|    | > OTI02/128:      |    |     | > Identifier      |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Qualifier       |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI03/127:      |    |     |                   |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI10/143:      |    |     |                   |   |   |       |
|    | > Transaction Set |    |     |                   |   |   |       |
|    | > Identifier Code |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > OTI01/110:      | >  |     | > Application     |   | X |       |
| 2/ | > Application     | TA |     | > Acknowledgment, |   |   |       |
| 01 | > Acknowledgment  |    |     | > Transaction Set |   |   |       |
| 00 | > Code            |    |     | > Reference ID,   |   |   |       |
|    | >                 |    |     | > And Transaction |   |   |       |
|    | > OTI02/128:      |    |     | > Set Identifier  |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Qualifier       |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI03/127:      |    |     |                   |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI10/143:      |    |     |                   |   |   |       |
|    | > Transaction Set |    |     |                   |   |   |       |
|    | > Identifier Code |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > OTI01/110:      | >  |     | > Application     | X |   |       |
| 2/ | > Application     | TP |     | > Acknowledgment, |   |   |       |
| 01 | > Acknowledgment  |    |     | > Transaction Set |   |   |       |
| 00 | > Code            |    |     | > Reference ID,   |   |   |       |
|    | >                 |    |     | > And Transaction |   |   |       |
|    | > OTI02/128:      |    |     | > Set Identifier  |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Qualifier       |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI03/127:      |    |     |                   |   |   |       |
|    | > Reference       |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > OTI10/143:      |    |     |                   |   |   |       |
|    | > Transaction Set |    |     |                   |   |   |       |
|    | > Identifier Code |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > TED01/647:      | >  |     | > Application     | X |   |       |
| 2/ | > Application     | IR |     | > Error Condition |   |   |       |
| 07 | > Error Condition |    |     |                   |   |   |       |
| 00 | > Code            |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > RED01/352:      | >  |     | > Application     | X |   |       |
| 2/ | > Description     | IR |     | > Error           |   |   |       |
| 08 | >                 |    |     | > Description,    |   |   |       |
| 20 | > RED03/559:      |    |     | > Agency          |   |   |       |
|    | > Agency          |    |     | > Qualifier And   |   |   |       |
|    | > Qualifier Code  |    |     | > Error Code      |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > RED05/1270:     |    |     |                   |   |   |       |
|    | > Code List       |    |     |                   |   |   |       |
|    | > Qualifier Code  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > RED06/1271:     |    |     |                   |   |   |       |
|    | > Industry Code   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > LQ01/1270: Code | >  | >   | > Data View       | X |   |       |
| 2/ | > List Qualifier  | IR | T07 |                   |   |   |       |
| 08 | > Code            |    |     |                   |   |   |       |
| 60 | >                 |    |     |                   |   |   |       |
|    | > LQ02/1271:      |    |     |                   |   |   |       |
|    | > Industry Code   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > LQ01/1270: Code | >  | >   | > Entity          | X |   |       |
| 2/ | > List Qualifier  | IR | T25 |                   |   |   |       |
| 08 | > Code            |    |     |                   |   |   |       |
| 60 | >                 |    |     |                   |   |   |       |
|    | > LQ02/1271:      |    |     |                   |   |   |       |
|    | > Industry Code   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > ST03/1705:      |    |     | > Implementation  | X | X |       |
| 1/ | > Implementation  |    |     | > Convention      |   |   |       |
| 01 | > Convention      |    |     | > Reference       |   |   |       |
| 00 | > Reference       |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > QTY01/673:      | >  |     | > Quantity        |   | X |       |
| 2/ | > Quantity        | TA |     | > Received And    |   |   |       |
| 06 | > Qualifier       |    |     | > Approved        |   |   |       |
| 00 | >                 |    |     |                   |   |   |       |
|    | > QTY02/380:      |    |     |                   |   |   |       |
|    | > Quantity        |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > QTY01/673:      | >  |     | > Quantity        | X |   |       |
| 2/ | > Quantity        | TP |     | > Received,       |   |   |       |
| 06 | > Qualifier       |    |     | > Approved And    |   |   |       |
| 00 | >                 |    |     | > Disapproved     |   |   |       |
|    | > QTY02/380:      |    |     |                   |   |   |       |
|    | > Quantity        |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > N101/98: Entity |    |     | > Sender Last     | X | X |       |
| 1/ | > Identifier Code |    |     | > Name,           |   |   |       |
| 03 | >                 |    |     | >                 |   |   |       |
| 00 | > N102/93: Name   |    |     | > Identification  |   |   |       |
|    | >                 |    |     | > Number          |   |   |       |
|    | > N103/66:        |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Code Qualifier  |    |     |                   |   |   |       |
|    | >                 |    |     |                   |   |   |       |
|    | > N104/67:        |    |     |                   |   |   |       |
|    | > Identification  |    |     |                   |   |   |       |
|    | > Code            |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > ST02/329:       |    |     | > Transaction Set | X | X |       |
| 1/ | > Transaction Set |    |     | > Control Number  |   |   |       |
| 01 | > Control Number  |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > SE02/329:       |    |     | > Transaction Set | X | X |       |
| 2/ | > Transaction Set |    |     | > Control Number  |   |   |       |
| 39 | > Control Number  |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN03/373: Date |    |     | > Transaction Set | X | X |       |
| 1/ |                   |    |     | > Date Sent       |   |   |       |
| 02 |                   |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > ST01/143:       |    |     | > Transaction Set | X | X |       |
| 1/ | > Transaction Set |    |     | > ID              |   |   |       |
| 01 | > Identifier Code |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > SE01/96: Number |    |     | > Transaction Set | X | X |       |
| 2/ | > of Included     |    |     | > Number Of       |   |   |       |
| 39 | > Segments        |    |     | > Segments        |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN06/127:      |    |     | > Transaction Set | X | X |       |
| 1/ | > Reference ID    |    |     | > Previously Sent |   |   |       |
| 02 |                   |    |     | > Reference ID    |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN01/353:      |    |     | > Transaction Set | X | X |       |
| 1/ | > Transaction Set |    |     | > Purpose         |   |   |       |
| 02 | > Purpose Code    |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN02/127:      |    |     | > Transaction Set | X | X |       |
| 1/ | > Reference ID    |    |     | > Reference ID    |   |   |       |
| 02 |                   |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN04/337: Time |    |     | > Transaction Set | X | X |       |
| 1/ |                   |    |     | > Time Sent       |   |   |       |
| 02 |                   |    |     |                   |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+
| >  | > BGN05/623: Time |    |     | > Transaction Set | X | X |       |
| 1/ | > Code            |    |     | > Time Sent Time  |   |   |       |
| 02 |                   |    |     | > Code            |   |   |       |
| 00 |                   |    |     |                   |   |   |       |
+----+-------------------+----+-----+-------------------+---+---+-------+

  ----------------------- ----------------------- -----------------------
  ![](media/image2.wmf)                           

  ----------------------- ----------------------- -----------------------

[^1]: OTI Loop for entire transaction set reporting

[^2]: OTI Loop(s) for entity reporting