004010F824_TVR 07 April 2008 

824 Application Advice 

Functional Group ID=AG 

Introduction:

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

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

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

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

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

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

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

acknowledgment sent in response to a purchase order). 

Notes: 

1. Use this transaction set to inform the originator of a transaction set of the results of edit checks performed on 

the transaction or transaction set by the application program. The reported results can include: accepted, 

accepted with errors, accepted with data content change or rejected. All agencies may not be capable of using 

this transaction set for all intended purposes. 

2. When used to reject a transaction or transaction set or to accept a transaction or transaction set with errors, 

the errors will be identified and the correct data, if known, will be provided. 

3. When the transaction or transaction set is accepted with data content change, the corrected data MUST be 

provided. 

4. This transaction set can be used to report on multiple transactions or multiple transaction sets sent by the 

same originator during a specified time period, e.g., daily. 

5. This transaction set is not used to reject a transmission due to ASC X12 syntax errors. Use a 997 transaction 

set for this purpose. 

Heading: 

Page Pos. Seg. Req. Loop Notes and 

No. No. ID Name Des. Max.Use Repeat Comments

3 010 ST Transaction Set Header M 1 4 020 BGN Beginning Segment M 1 

 LOOP ID - N1 >1

6 030 N1 Name O 1 Not Used 040 N2 Additional Name Information O 2 Not Used 050 N3 Address Information O 2 Not Used 060 N4 Geographic Location O 1 Not Used 070 REF Reference Identification O 12 8 080 PER Administrative Communications Contact O 3 

Detail: 

Page Pos. Seg. Req. Loop Notes and 

No. No. ID Name Des. Max.Use Repeat Comments

 LOOP ID - OTI >1
824 - Application Advice

004010F824_TVR 2 07 April 2008

10 010 OTI Original Transaction Identification M 1 n1

12 020 REF Reference Identification O 12 n2

14 030 DTM Date/Time Reference O 2 n3

Not Used 040 PER Administrative Communications Contact O 3 n4

Not Used 050 AMT Monetary Amount O >1 n5

Not Used 060 QTY Quantity O >1 n6

Not Used 065 NM1 Individual or Organizational Name O 9 n7

 LOOP ID - TED >1

15 070 TED Technical Error Description O 1 Not Used 080 NTE Note/Special Instruction O 100 Not Used 082 RED Related Data O 100 n8

 LOOP ID - LM >1

085 LM Code Source Information O 1 n9

 LOOP ID - LQ 100

086 LQ Industry Code M 1 Not Used 087 RED Related Data O 100 n10

19 090 SE Transaction Set Trailer M 1 

Transaction Set Notes

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

application acknowledgment. 

2. The REF segment allows for the provision of secondary reference identification or numbers required to 

uniquely identify the original transaction set. The primary reference identification or number should be 

provided in elements OTI02-03. 

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

identify the original transaction set. 

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

unique identification of the original transaction set. 

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

identification of the original transaction set. 

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

original transaction set. 

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

the original transaction set. 

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

TED01 element. 

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

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

element. 
824 - Application Advice

004010F824_TVR 3 07 April 2008

 Segment: ST Transaction Set Header 

 Position: 010 

Loop:

Level: Heading 

Usage: Mandatory 

Max Use: 1 

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

Syntax Notes:

Semantic Notes: 1 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). 

Comments:

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

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

Code uniquely identifying a Transaction Set

824 Application Advice

Must Use ST02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set 

functional group assigned by the originator for a transaction set

Use to identify a unique number assigned by the originator of the transaction 

set. This number may be system generated.
824 - Application Advice

004010F824_TVR 4 07 April 2008

 Segment: BGN Beginning Segment 

 Position: 020 

Loop:

Level: Heading 

Usage: Mandatory 

Max Use: 1 

Purpose: To indicate the beginning of a transaction set 

Syntax Notes: 1 If BGN05 is present, then BGN04 is required. 

Semantic Notes: 1 BGN02 is the transaction set reference number. 

 2 BGN03 is the transaction set date. 

 3 BGN04 is the transaction set time. 

 4 BGN05 is the transaction set time qualifier. 

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

affected by the current transaction. 

Comments:

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use BGN01 353 Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set

00 Original

Must Use BGN02 127 Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as 

specified by the Reference Identification Qualifier

 Use to identify the unique reference number assigned to this 824 

transaction set, not the transaction set that is being reported

Must Use BGN03 373 Date M DT 8/8

Date expressed as CCYYMMDD

 Use to identify the date this 824 transaction set was originated.

Must Use BGN04 337 Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or 

HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds 

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

 Use to identify the time this 824 transaction set was originated.

BGN05 623 Time Code O ID 2/2

Code identifying the time. In accordance with International Standards 

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

in hours in relation to Universal Time Coordinate (UTC) time; since + is a 

restricted character, + and - are substituted by P and M in the codes that follow

Use only if the time is other than local time.

CT Central Time

ET Eastern Time

GM Greenwich Mean Time

MT Mountain Time

PT Pacific Time

Not Used BGN06 127 Reference Identification O AN 1/30

Reference information as defined for a particular Transaction Set or as 

specified by the Reference Identification Qualifier

BGN07 640 Transaction Type Code O ID 2/2

Code specifying the type of transaction

When the reported transaction set's beginning segment contains data 

element 640 and a code value was transmitted, cite that same code value.

Refer to 004010 Data Element Dictionary for acceptable code values.
824 - Application Advice

004010F824_TVR 5 07 April 2008

BGN08 306 Action Code O ID 1/2

Code indicating type of action

When the reported transaction set's beginning segment contains data 

element 306 and a code value was transmitted, cite that same code value.

Refer to 004010 Data Element Dictionary for acceptable code values.

Not Used BGN09 786 Security Level Code O ID 2/2

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

information following
824 - Application Advice

004010F824_TVR 6 07 April 2008

 Segment: N1 Name 

 Position: 030 

Loop: N1 Optional 

Level: Heading 

Usage: Optional 

Max Use: 1 

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

Syntax Notes: 1 At least one of N102 or N103 is required. 

 2 If either N103 or N104 is present, then the other is required. 

Semantic Notes:

Comments: 1 This segment, used alone, provides the most efficient method of providing 

organizational identification. To obtain this efficiency the "ID Code" (N104) must 

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

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

Notes: 1. Address information is to be transmitted using only code values contained in a 

combination of N101, N103/N104 data elements. 

2. There must be 2 iterations of the N1 loop in each transmission; one iteration to 

carry the name and address of the party transmitting the 824 transactions set and a 

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

transaction set is being sent. 

3. The name and address of each party will be conveyed by use of a code in N103/04.

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use N101 98 Entity Identifier Code M ID 2/3

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

individual

FR Message From

Use to indicate the entity sending the transaction set.

TO Message To

Use to indicate the entity to whom the transaction set is 

being sent.

Not Used N102 93 Name X AN 1/60

Free-form name

N103 66 Identification Code Qualifier X ID 1/2

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

Code (67)

While the federal EDI program uses the DUNS number, some government 

users of this implementation convention may require the use of other 

numbers for a transition period in order to cross reference existing data 

bases.

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

2 Standard Carrier Alpha Code (SCAC)

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

Suffix

10 Department of Defense Activity Address Code 

(DODAAC)

Use to indicate either a Department of Defense Activity 

Address Code or a Civilian Agency Activity Address 

Code.

33 Commercial and Government Entity (CAGE)

Use when a commercial entity cannot be identified by 

a DUNS number.

93 Code assigned by the organization originating the 

transaction set
824 - Application Advice

004010F824_TVR 7 07 April 2008

A2 Military Assistance Program Address Code (MAPAC)

FA Facility Identification

Use to identify a facility that cannot be identified using 

one of the listed codes.

FI Federal Taxpayer's Identification Number

Use only if the receiving organization uses a 

Taxpayer's Identification Number (TIN) to identify the 

sender.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code X AN 2/80

Code identifying a party or other code

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

Code describing entity relationship

Not Used N106 98 Entity Identifier Code O ID 2/3

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

individual
824 - Application Advice

004010F824_TVR 8 07 April 2008

 Segment: PER Administrative Communications Contact 

 Position: 080 

Loop: N1 Optional 

Level: Heading 

Usage: Optional 

Max Use: 3 

Purpose: To identify a person or office to whom administrative communications should be directed 

Syntax Notes: 1 If either PER03 or PER04 is present, then the other is required. 

 2 If either PER05 or PER06 is present, then the other is required. 

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

Semantic Notes:

Comments:

Notes: When N101 is code FR, use to identify a contact to whom inquiries regarding this 

transaction set can be directed.

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use PER01 366 Contact Function Code M ID 2/2

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

AL Alternate Contact

Use to indicate an alternate party to whom inquiries 

regarding this transaction set should be directed.

EA EDI Coordinator

Use to indicate the primary party to whom inquiries 

regarding this transaction set should be directed.

PER02 93 Name O AN 1/60

Free-form name

Cite the last name first, followed by the first name. Do not truncate the last 

name if the whole name is longer than 35 characters. Instead, truncate the 

first name or use the initial of the first name.

PER03 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

AU Defense Switched Network

EM Electronic Mail

FX Facsimile

IT International Telephone

Include country and city code.

TE Telephone

Use to indicate the commercial telephone number of 

the party cited in PER02.

PER04 364 Communication Number X AN 1/80

Complete communications number including country or area code when 

applicable

When PER03 is code TE, include the area code.

PER05 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Use to identify a second communications number for the party cited in 

PER02. For example, if PER03/04 cites a commercial telephone number, 

PER05/06 can be used to cite an Electronic Mail address.

EM Electronic Mail

EX Telephone Extension

Use only if PER03 is code TE.

FX Facsimile

TE Telephone
824 - Application Advice

004010F824_TVR 9 07 April 2008

Use to indicate the commercial telephone number of 

the party cited in PER02.

PER06 364 Communication Number X AN 1/80

Complete communications number including country or area code when 

applicable

When PER05 is code TE, include the area code.

PER07 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Use to identify a third communications number for the party cited in PER02.

EM Electronic Mail

EX Telephone Extension

Use only if PER05 is code TE

FX Facsimile

TE Telephone

Use to indicate the commercial telephone number of 

the party cited in PER02.

PER08 364 Communication Number X AN 1/80

Complete communications number including country or area code when 

applicable

When PER07 is code TE, include the area code.

PER09 443 Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

Use to indicate the office symbol or activity code for the identified party.
824 - Application Advice

004010F824_TVR 10 07 April 2008

 Segment: OTI Original Transaction Identification 

 Position: 010 

Loop: OTI Mandatory 

Level: Detail 

Usage: Mandatory 

Max Use: 1 

Purpose: 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 

Syntax Notes: 1 If OTI09 is present, then OTI08 is required. 

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

original transaction set. 

 2 OTI06 is the group date. 

 3 OTI07 is the group time. 

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

electronic transaction was translated by the receiver. 

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

identification. 

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

identification. 

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

its unique identification. 

 8 OTI15 is the type of action indicated or requested by the original transaction set, and 

is used to assist in its unique identification. 

 9 OTI16 is the action requested by the original transaction set, and is used to assist in 

its unique identification. 

 10 OTI17 is the status reason of the original transaction set, and is used to assist in its 

unique identification. 

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

business application, and OTI03 will contain the original business application 

identification. 

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

functional group generated by the sender. 

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

transaction set generated by the sender. 

Notes: Use this loop to identify the transaction or transaction set that is being reported and the 

action that is being taken. Use multiple iterations of the OTI loop to report on more 

than one transaction or transaction set. Use to identify secondary reference numbers 

associated with a business transaction identified in 2/OTI02/010.

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use OTI01 110 Application Acknowledgment Code M ID 1/2

Code indicating the application system edit results of the business data

Use to identify the action taken regarding the transaction or transaction set 

being reported and identified in the same OTI loop.

TA Transaction Set Accept

TC Transaction Set Accept with Data Content Change

TE Transaction Set Accept with Error

TR Transaction Set Reject

Must Use OTI02 128 Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

Use to indicate the unique reference number of the transaction set being 

reported, or to identify the primary transaction reference number related to a 

business transaction. Use 2/REF/020 to identify secondary reference 

numbers related to a business transaction.

5G Complaint

CT Contract Number
824 - Application Advice

004010F824_TVR 11 07 April 2008

OI Original Invoice Number

PO Purchase Order Number

TN Transaction Reference Number

UG U.S. Government Transportation Control Number

Must Use OTI03 127 Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as 

specified by the Reference Identification Qualifier

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

Code identifying party sending transmission; codes agreed to by trading 

partners. 

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

Code identifying party receiving transmission. Codes agreed to by trading 

partners

Not Used OTI06 373 Date O DT 8/8

Date expressed as CCYYMMDD

Not Used OTI07 337 Time O TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or 

HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds 

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

OTI08 28 Group Control Number X N0 1/9

Assigned number originated and maintained by the sender. 

Use to identify the number cited in GS06 of the functional group in which 

the reported transaction was transmitted.

OTI09 329 Transaction Set Control Number O AN 4/9

Identifying control number that must be unique within the transaction set 

functional group assigned by the originator for a transaction set

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

transaction set being reported.

OTI10 143 Transaction Set Identifier Code O ID 3/3

Code uniquely identifying a Transaction Set

Refer to 004010 Data Element Dictionary for acceptable code values.

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

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

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

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

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

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

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

Use to identify the ASC X12 Version/Release used to translate the 

transaction set being reported.

Refer to 004010 Data Element Dictionary for acceptable code values.

OTI12 353 Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set

OTI13 640 Transaction Type Code O ID 2/2

Code specifying the type of transaction

Not Used OTI14 346 Application Type O ID 2/2

Code identifying an application

OTI15 306 Action Code O ID 1/2

Code indicating type of action

Not Used OTI16 305 Transaction Handling Code O ID 1/2

Code designating the action to be taken by all parties

OTI17 641 Status Reason Code O ID 3/3

Code indicating the status reason
824 - Application Advice

004010F824_TVR 12 07 April 2008

 Segment: REF Reference Identification 

 Position: 020 

Loop: OTI Mandatory 

Level: Detail 

Usage: Optional 

Max Use: 12 

Purpose: To specify identifying information 

Syntax Notes: 1 At least one of REF02 or REF03 is required. 

 2 If either C04003 or C04004 is present, then the other is required. 

 3 If either C04005 or C04006 is present, then the other is required. 

Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. 

Comments:

Notes: Use to identify secondary reference numbers associated with 2/OTI02/010. Do not use 

this segment when code TN is used in 2/OTI02/010.

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use REF01 128 Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

1. Use any code. The following commonly used codes are provided for easy 

reference. 

16 Military Interdepartmental Purchase Request (MIPR) 

43 Supporting Document Number 

83 Extended (or Exhibit) Line Item Number (ELIN) 

C7 Contract Line Item Number 

CR Customer Reference Number 

CT Contract Number 

TN Transaction Reference Number 

W1 Disposal Turn-in Document Number 

W8 Suffix 

 Use with Code TN in 2/OTI02/010.

Refer to 004010 Data Element Dictionary for acceptable code values.

REF02 127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as 

specified by the Reference Identification Qualifier

REF03 352 Description X AN 1/80

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

REF04 C040 Reference Identifier O

To identify one or more reference numbers or identification numbers as 

specified by the Reference Qualifier

C04001 128 Reference Identification Qualifier M ID 2/3

Code qualifying the Reference Identification

OQ Order Number

Use with code C7 in 2/REF01/020 to identify the 

applicable call/order number.

C04002 127 Reference Identification M AN 1/30

Reference information as defined for a particular Transaction Set or as 

specified by the Reference Identification Qualifier

C04003 128 Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

Refer to 004010 Data Element Dictionary for acceptable code values.

C04004 127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as 

specified by the Reference Identification Qualifier
824 - Application Advice

004010F824_TVR 13 07 April 2008

C04005 128 Reference Identification Qualifier X ID 2/3

Code qualifying the Reference Identification

Refer to 004010 Data Element Dictionary for acceptable code values.

C04006 127 Reference Identification X AN 1/30

Reference information as defined for a particular Transaction Set or as 

specified by the Reference Identification Qualifier
824 - Application Advice

004010F824_TVR 14 07 April 2008

 Segment: DTM Date/Time Reference 

 Position: 030 

Loop: OTI Mandatory 

Level: Detail 

Usage: Optional 

Max Use: 2 

Purpose: To specify pertinent dates and times 

Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. 

 2 If DTM04 is present, then DTM03 is required. 

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

Semantic Notes:

Comments:

Notes: Use this segment to identify the creation date of the transaction or transaction set being 

reported.

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use DTM01 374 Date/Time Qualifier M ID 3/3

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

097 Transaction Creation

Must Use DTM02 373 Date X DT 8/8

Date expressed as CCYYMMDD

DTM03 337 Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or 

HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds 

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Cite the time the reported transaction set was originated, if known.

Not Used DTM04 623 Time Code O ID 2/2

Code identifying the time. In accordance with International Standards 

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

in hours in relation to Universal Time Coordinate (UTC) time; since + is a 

restricted character, + and - are substituted by P and M in the codes that follow

Not Used DTM05 1250 Date Time Period Format Qualifier X ID 2/3

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

Not Used DTM06 1251 Date Time Period X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times
824 - Application Advice

004010F824_TVR 15 07 April 2008

 Segment: TED Technical Error Description 

 Position: 070 

Loop: TED Optional 

Level: Detail 

Usage: Optional 

Max Use: 1 

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

Syntax Notes:

Semantic Notes:

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

number, date, reference number, etc.). 

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

2. Use multiple repetitions of this segment to identify multiple errors within the 

reported transaction set.

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use TED01 647 Application Error Condition Code M ID 1/3

Code indicating application error condition

1. Any code may be used. The listed codes are to be used only as indicated 

by the code value notes. 

026 Customer Identification Number is invalid 

Use to indicate an erroneous number, e.g., DUNS Number, DUNS+4 

Number, CAGE code, DoDAAC, or Civilian Activity Address code. 

029 Customer Identification Number is Missing 

Use to indicate a missing number, e.g., DUNS Number, DUNS+4 Number, 

CAGE code, DoDAAC, or Civilian Activity Address code. 

024 Other Unlisted Reason 

Use to indicate an error not identified by a specific code. Specify the error in 

TED02. 

848 Incorrect Data 

Use to indicate an unspecified error condition that cannot be described. 

OTH Other 

Use to indicate that specific application advice is conveyed under 

2/LQ01/086.

Refer to 004010 Data Element Dictionary for acceptable code values.

TED02 3 Free Form Message O AN 1/60

Free-form text

When TED01 is code 024, use to specify the error.

TED03 721 Segment ID Code O ID 2/3

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

Number 77)

Use to identify the segment containing the error.

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

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

transaction set: the transaction set header is count position 1

Use to identify the position of the segment within the transmission of the 

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

segment transmitted.

TED05 722 Element Position in Segment O N0 1/2
824 - Application Advice

004010F824_TVR 16 07 April 2008

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

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

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

the count starts with 1 for the simple data element or composite data structure 

immediately following the segment ID

Use to identify the segment position of the data element containing an error, 

e.g., 1, 12, etc.

TED06 725 Data Element Reference Number O N0 1/4

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

Dictionary

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

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

This is a copy of the data element in error

Use to identify the erroneous content of the data element, e.g., 999.

TED08 961 Data Element New Content O AN 1/99

New data which has replaced erroneous data

1. When OTI01 is code TE or TR, use to identify the correct data, if known, 

that should have been transmitted in the data element. 

2. When OTI01 is code TC, this data element is REQUIRED.
824 - Application Advice

004010F824_TVR 17 07 April 2008

 Segment: LM Code Source Information 

 Position: 085 

Loop: LM Optional 

Level: Detail 

Usage: Optional 

Max Use: 1 

Purpose: To transmit standard code list identification information 

Syntax Notes:

Semantic Notes:

Comments: 1 LM02 identifies the applicable industry code list source information. 

Notes: Use this loop to provide codified data from a code source list maintained by a federal 

agency.

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use LM01 559 Agency Code Qualifier M ID 2/2

Code identifying the agency assigning the code values

Use any code. 

DF Department of Defense 

 DLSM users must use to identify DoD.

Refer to 004010 Data Element Dictionary for acceptable code values.

LM02 822 Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source Qualifier

When LQ01 is code ZZ, identify the code list that contains the code cited in 

LQ02.
824 - Application Advice

004010F824_TVR 18 07 April 2008

 Segment: LQ Industry Code 

 Position: 086 

Loop: LQ Mandatory 

Level: Detail 

Usage: Mandatory 

Max Use: 1 

Purpose: Code to transmit standard industry codes 

Syntax Notes: 1 If LQ01 is present, then LQ02 is required. 

Semantic Notes:

Comments:

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

LQ01 1270 Code List Qualifier Code O ID 1/3

Code identifying a specific industry code list

Use any code. 

0 Document Identification Code 

 DLMS users must use to satisfy legacy system requirements.

Refer to 004010 Data Element Dictionary for acceptable code values.

LQ02 1271 Industry Code X AN 1/30

Code indicating a code from a specific industry code list

Use to cite a code that is contained in a code source list applicable to the 

qualifier code cited in LQ01 or when LQ01 is code ZZ, in a code source list 

cited in LM02.
824 - Application Advice

004010F824_TVR 19 07 April 2008

 Segment: SE Transaction Set Trailer 

 Position: 090 

Loop:

Level: Detail 

Usage: Mandatory 

Max Use: 1 

Purpose: To indicate the end of the transaction set and provide the count of the transmitted 

segments (including the beginning (ST) and ending (SE) segments) 

Syntax Notes:

Semantic Notes:

Comments: 1 SE is the last segment of each transaction set. 

Data Element Summary 

 Ref. Data 

 Des. Element Name Attributes

Must Use SE01 96 Number of Included Segments M N0 1/10

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

segments

Must Use SE02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set 

functional group assigned by the originator for a transaction set

This is the number cited in ST02.