DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 1 August 23, 2023

824 Application Advice

Functional Group=AG

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

DLMS Note:

1. Used by the processing activity for functional reject of select transactions.

2. This transaction set is not used to reject a transmission due to ASC X12 syntax errors. Use a 997 transaction set for that purpose.

3. Used by the processing activity to reject DLMS transactions which could not be processed due to erroneous or missing data. Used by the

processing activity to provide functional reject of transactions to the submitting activity. This transaction supports the functionality of

MILSTRAP Document Identifier Code (DIC) DZG, however rather than perpetuate all information from the rejected transaction as was done

under DLSS, only information necessary to identify the rejected transaction and the reject advice information is provided

4. DLMS 824R was initially developed for rejection of MILSTRAP related DLMS transactions. However the DLMS 824R scope is expanded

and it is authorized for use with other DLMS supply, contract administration and logistics bills transactions, but does not replace procedures

for error identification addressed by the DLMS 140A Small Arms and Light Weapons (SA/LW) Reporting, DLMS 870S Supply Status or

DLMS 842A/R DoD Supply Discrepancy Report Reply. Also used by DLA Transaction Services for narrative message type rejects for all

DLMS transactions subject to rejection by DAAS narrative messages.

5. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at URL: http://www.dla.mil/j-6/dlmso.

6. This DLMS Implementation Convention (IC) contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system.

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components

may coordinate with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's

automated processing system. Components must coordinate implementation with DEDSO prior to use.

e. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent to, modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

7. This revision to the DLMS IC incorporates Proposed DLMS Change (PDC) and Approved DLMS Change (ADC) listed. PDCs/ADCs are

available from the DEDSO Web site http://www.dla.mil/j-6/dlmso/elibrary/Changes/processchanges.asp

- ADC 160, New Federal Implementation Convention and DLMS Supplement 824R Reject Advice Transaction (Supply)

- ADC 179, Revise DS 824R to include DAASC Narrative Rejects, and Expansion for Rejection of Additional DLMS Transactions (Contract

Administration/Supply)

- ADC 248, Administrative Update to DLMS Supplement 824R, Reject Advice (Contract Administration/Supply)

- ADC 330, Revision to DS 824R, Reject Advice

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 471, Administrative Update to DLMS 824R Reject Advice (Supply)

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on March 27, 2014. 

- ADC 1103, Revise DLMS 824R, Reject Advice, to Include Rejection of Logistics Bills, Clarify use for Rejection of DLMS MILSTRIP

Transactions, and Document Administrative Updates

- ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

1. Used by the processing activity for functional reject of select transactions.

2. This transaction set is not used to reject a transmission due to ASC X12 syntax errors. Use a 997 transaction set for that purpose.

3. Used by the processing activity to reject DLMS transactions which could not be processed due to erroneous or missing data. Used by the

processing activity to provide functional reject of transactions to the submitting activity. This transaction supports the functionality of

MILSTRAP Document Identifier Code (DIC) DZG, however rather than perpetuate all information from the rejected transaction as was done

under DLSS, only information necessary to identify the rejected transaction and the reject advice information is provided

4. DLMS 824R was initially developed for rejection of MILSTRAP related DLMS transactions. However the DLMS 824R scope is expanded

and it is authorized for use with other DLMS supply, contract administration and logistics bills transactions, but does not replace procedures

for error identification addressed by the DLMS 140A Small Arms and Light Weapons (SA/LW) Reporting, DLMS 870S Supply Status or

DLMS 842A/R DoD Supply Discrepancy Report Reply. Also used by DLA Transaction Services for narrative message type rejects for all

DLMS transactions subject to rejection by DAAS narrative messages.

5. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at URL: http://www.dla.mil/j-6/dlmso.

6. This DLMS Implementation Convention (IC) contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system.

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components

may coordinate with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's

automated processing system. Components must coordinate implementation with DEDSO prior to use.

e. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent to, modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

7. This revision to the DLMS IC incorporates Proposed DLMS Change (PDC) and Approved DLMS Change (ADC) listed. PDCs/ADCs are

available from the DEDSO Web site http://www.dla.mil/j-6/dlmso/elibrary/Changes/processchanges.asp

- ADC 160, New Federal Implementation Convention and DLMS Supplement 824R Reject Advice Transaction (Supply)

- ADC 179, Revise DS 824R to include DAASC Narrative Rejects, and Expansion for Rejection of Additional DLMS Transactions (Contract

Administration/Supply)

- ADC 248, Administrative Update to DLMS Supplement 824R, Reject Advice (Contract Administration/Supply)

- ADC 330, Revision to DS 824R, Reject Advice

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 471, Administrative Update to DLMS 824R Reject Advice (Supply)

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on March 27, 2014. 

- ADC 1103, Revise DLMS 824R, Reject Advice, to Include Rejection of Logistics Bills, Clarify use for Rejection of DLMS MILSTRIP

Transactions, and Document Administrative Updates

- ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 2 August 23, 2023

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions

and DLMS Manuals (Supply/Contract Administration)

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 27, 2016

- ADC 1214A, Addendum to ADC 1214 New DLMS Implementation Convention (IC) 824W Disposal Turn-In Document (DTID) and

Hazardous Material/Hazardous Waste Profile Sheet (HWPS) Validation and Associated Procedures (Supply)

- ADC 1226, Revise DLMS 824R Reject Advice in support of intra-Air Force basis Government Furnished Property (GFP) Accountability

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

September 19, 2018

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions 

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on April 8, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

- ADC 1433, Data Element Additions to Update DLMS 841W, DLMS 856S, and DLMS 824R

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions

and DLMS Manuals (Supply/Contract Administration)

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 27, 2016

- ADC 1214A, Addendum to ADC 1214 New DLMS Implementation Convention (IC) 824W Disposal Turn-In Document (DTID) and

Hazardous Material/Hazardous Waste Profile Sheet (HWPS) Validation and Associated Procedures (Supply)

- ADC 1226, Revise DLMS 824R Reject Advice in support of intra-Air Force basis Government Furnished Property (GFP) Accountability

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

September 19, 2018

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions 

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on April 8, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

- ADC 1433, Data Element Additions to Update DLMS 841W, DLMS 856S, and DLMS 824R

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

010 ST Transaction Set Header M 1 Must use

020 BGN Beginning Segment M 1 Must use

LOOP ID - N1 LOOP ID - N1 >1

030 N1 Name O 1 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 Not Used

080 PER Administrative Communications

Contact

O 3 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - OTI LOOP ID - OTI >1 N2/010L N2/010L

010 OTI Original Transaction Identification M 1 N2/010 Must use

020 REF Reference Identification O 12 N2/020 Must use

030 DTM Date/Time Reference O 2 N2/030 Used

* 040 PER Administrative Communications

Contact

O 3 N2/040 Not Used

* 050 AMT Monetary Amount O >1 N2/050 Not Used

* 060 QTY Quantity O >1 N2/060 Not Used

065 NM1 Individual or Organizational Name O 9 N2/065 Used

LOOP ID - TED LOOP ID - TED >1

070 TED Technical Error Description O 1 Used

080 NTE Note/Special Instruction O 100 Used

* 082 RED Related Data O 100 N2/082 Not Used

LOOP ID - LM LOOP ID - LM >1 N2/085L N2/085L

085 LM Code Source Information O 1 N2/085 Used

LOOP ID - LQ LOOP ID - LQ 100

086 LQ Industry Code M 1 Must use

* 087 RED Related Data O 100 N2/087 Not Used

090 SE Transaction Set Trailer M 1 Must use

Notes: 

2/010L The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this application

acknowledgment.

2/010 The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this application 
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 3 August 23, 2023

acknowledgment.

2/020 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/030 The DTM segment allows for the provision of date, time, or date and time information required to uniquely identify the original

transaction set.

2/040 The PER segment should be utilized if administrative communications contact information is important to the unique identification

of the original transaction set.

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

transaction set.

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

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

set.

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

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

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

2/087 The RED segment may be used to provide data related to the error condition specified in the associated LQ02 element.
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 4 August 23, 2023

ST Transaction Set Header Pos: 010 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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

Semantics: 

1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set

definition (e.g., 810 selects the Invoice Transaction Set).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)

Code Name

824 Application Advice

ST02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: Use to identify a unique number

assigned by the originator of the transaction set.

This number may be system generated.

M AN 4/9 Must use
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 5 August 23, 2023

BGN Beginning Segment Pos: 020 Max: 1

Heading - Mandatory

Loop: N/A Elements: 7

User Option (Usage): Must use

Purpose: To indicate the beginning of a transaction set

Syntax Rules: 

1. C0504 - If BGN05 is present, then BGN04 is required.

Semantics: 

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.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

BGN01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 2)

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

Defense Logistics Management Standards (DLMS) users, use to identify a simulated mobilization

exercise transaction set. Activities initiating a simulated mobilization exercise must ensure complete

coordination with all activities involved. All transaction set recipients must use extreme caution to

ensure that individual transactions do not process as action documents which affect accountable

records.

BGN02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

DLMS Note: Use to identify the unique reference

number (document number) assigned to this DLMS

824R transaction set, not the transaction set that is

being rejected.

M AN 1/30 Must use

BGN03 373 Date

Description: Date expressed as CCYYMMDD

DLMS Note: 1. Use to identify the date this 824

transaction set was originated.

2. DLMS users, this date corresponds to the

Universal Time Coordinate (UTC).

M DT 8/8 Must use

BGN04 337 Time

Description: 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)

X TM 4/8 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F824R2RA16 6 August 23, 2023

DLMS Note: 1. Express the originating activity's

time of transaction set preparation in UTC.

2. Express time in a four (HHMM) or six-position

(HHMMSS) format with seconds optional.

BGN05 623 Time Code

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

O ID 2/2 Used

CodeList Summary (Total Codes: 51, Included: 1)

Code Name

UT Universal Time Coordinate

BGN07 640 Transaction Type Code

Description: Code specifying the type of

transaction

O ID 2/2 Used

CodeList Summary (Total Codes: 446, Included: 2)

Code Name

ZG Report of Approved Work Candidate

DLMS Note:

Use to identify HM/HW profile content acceptance.

ZT Report of Rejection or Return of Work Candidate

DLMS Note:

Use to identify a Reject Advice transaction.

BGN08 306 Action Code

Description: Code indicating type of action

O ID 1/2 Used

CodeList Summary (Total Codes: 296, Included: 2)

Code Name

80 Reconcile

DLMS Note:

1. Use to identify rejections generated by the recipient of a transaction for DAAS processing. This is a

planned future enhancement; this functionality is not currently available. 

2. DLMS enhancement; see introductory DLMS note 6a. on the IC cover page. Refer to ADC 1226.

DR Direct

DLMS Note:

1. Use for rejections generated by the recipient of a transaction for routing to the identified Message-To

addressee without further DAAS processing. 

2. DLMS enhancement; see introductory DLMS Note 6a.

3. Authorized for use for Air Force Government Furnished Property - Accountability (GFP-A). Refer to

ADC 1226
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 7 August 23, 2023

N1 Name Pos: 030 Max: 1

Heading - Optional

Loop: N1 Elements: 3

User Option (Usage): Used

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

Syntax Rules: 

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

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

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.

DLMS Note:

1. Must use 2 iterations of the 1/N1/030 loop; one iteration to identify the activity transmitting the DLMS 824R Reject Advice transaction and

a second iteration to identify the activity to whom the DLMS 824R Reject Advice transaction is being sent. 

2. Component systems generate 824R transactions under the existing authorized MILSTRAP DIC DZG functionality, rejection of materiel

release orders under PDC 1166, as well as rejection based on ADC 1226. The only other authorized RIC-From is SGA, the RIC-From of the

Component system generating 824R per legacy DIC DZG functionality, or the RIC/DoDAAC-From representing the Air Force Program

Manager in the accountable property system of record (APSR) for Air Force rejects for Air Force Government Furnished Property -

Accountability (GFP-A).

1. Must use 2 iterations of the 1/N1/030 loop; one iteration to identify the activity transmitting the DLMS 824R Reject Advice transaction and

a second iteration to identify the activity to whom the DLMS 824R Reject Advice transaction is being sent. 

2. Component systems generate 824R transactions under the existing authorized MILSTRAP DIC DZG functionality, rejection of materiel

release orders under PDC 1166, as well as rejection based on ADC 1226. The only other authorized RIC-From is SGA, the RIC-From of the

Component system generating 824R per legacy DIC DZG functionality, or the RIC/DoDAAC-From representing the Air Force Program

Manager in the accountable property system of record (APSR) for Air Force rejects for Air Force Government Furnished Property -

Accountability (GFP-A).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 2)

Code Name

FR Message From

DLMS Note:

Use to identify the activity transmitting the DLMS 824R Reject Advice transaction.

TO Message To

DLMS Note:

Use to identify the activity to whom the DLMS 824R Reject Advice transaction is being sent. The TO

address is the originator of the transaction being rejected.

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; See introductory DLMS note 6a.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 8 August 23, 2023

PER Administrative Communications

Contact

Pos: 080 Max: 3

Heading - Optional

Loop: N1 Elements: 9

User Option (Usage): Used

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

Syntax Rules: 

1. P0304 - If either PER03 or PER04 is present, then the other is required.

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

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

DLMS Note:

1. Use to identify a contact to whom inquiries regarding this transaction set can be directed.

2. This segment is a DLMS enhancement. See introductory DLMS note 6a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

PER01 366 Contact Function Code

Description: Code identifying the major duty or

responsibility of the person or group named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 1)

Code Name

IC Information Contact

PER02 93 Name

Description: Free-form name

DLMS Note: 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.

DLMS Note: 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.

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 5)

Code Name

AU Defense Switched Network

EM Electronic Mail

FX Facsimile

DLMS Note:

Use to identify the commercial FAX number.

TE Telephone

DLMS Note:

Use to indicate the commercial telephone number of the party cited in PER02.

WF Work Facsimile Number

DLMS Note:

Use to identify the DSN FAX number.

PER04 364 Communication Number

Description: Complete communications number

including country or area code when applicable

X AN 1/80 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F824R2RA16 9 August 23, 2023

DLMS Note: When PER03 is code TE, include the

area code.

PER05 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 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.

DLMS Note: 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.

X ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 5)

Code Name

AU Defense Switched Network

EM Electronic Mail

FX Facsimile

DLMS Note:

Use to identify the commercial FAX number.

TE Telephone

DLMS Note:

Use to indicate the commercial telephone number of the party cited in PER02.

WF Work Facsimile Number

DLMS Note:

Use to identify the DSN FAX number.

PER06 364 Communication Number

Description: Complete communications number

including country or area code when applicable

DLMS Note: When PER05 is code TE, include the

area code.

X AN 1/80 Used

PER07 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: Use to identify a third communications

number for the party cited in PER02.

X ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 5)

Code Name

AU Defense Switched Network

EM Electronic Mail

FX Facsimile

DLMS Note:

Use to identify the commercial FAX number.

TE Telephone

DLMS Note:

Use to indicate the commercial telephone number of the party cited in PER02.

WF Work Facsimile Number

DLMS Note:

Use to identify the DSN FAX number.

PER08 364 Communication Number

Description: Complete communications number

including country or area code when applicable

DLMS Note: When PER07 is code TE, include the

X AN 1/80 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F824R2RA16 10 August 23, 2023

area code.

PER09 443 Contact Inquiry Reference

Description: Additional reference number or

description to clarify a contact number

DLMS Note: Use to indicate the office symbol or

activity code for the identified party.

O AN 1/20 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 11 August 23, 2023

OTI Original Transaction Identification Pos: 010 Max: 1

Detail - Mandatory

Loop: OTI Elements: 11

User Option (Usage): Must use

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

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

Semantics: 

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.

DLMS Note:

Use this loop to identify the transaction that is being rejected and the action that is being taken. Use multiple iterations of the OTI loop to

report on more than one transaction set. Use 2/REF/020 to identify secondary reference numbers associated with the number cited in

OTI02/03.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

OTI01 110 Application Acknowledgment Code

Description: Code indicating the application system

edit results of the business data

DLMS Note: 1. Use to identify the action taken

regarding the transaction being rejected and

identified in the same OTI loop.

2. The following codes are authorized.

M ID 1/2 Must use

CodeList Summary (Total Codes: 20, Included: 2)

Code Name

IA Item Accept

DLMS Note:

Use in conjunction with OTI02 = WPN to indicate acceptance of the HM/HW profile identified in OTI03.

TR Transaction Set Reject

OTI02 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: 1. Use to indicate the unique reference

number of the transaction set being rejected. Use

M ID 2/3 Must use
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F824R2RA16 12 August 23, 2023

2/REF/020 to identify related secondary reference

numbers.

2. The following codes are authorized.

CodeList Summary (Total Codes: 1504, Included: 3)

Code Name

CT Contract Number

DLMS Note:

Use to identify the procurement instrument identifier (PIID). Use the legacy procurement instrument

identification number (PIIN) pending transition to the PIID. When procurement is authorized under a

PIID call/order number (F in 9th position), provide the value in the PIID field. For Other Transaction

(OT) agreements, the type of instrument (9th position of PIID) will be a 3 for Research OTs or 9 for

Prototype and Production OTs. Refer to ADC 1161A or ADC 1420.

TN Transaction Reference Number

DLMS Note:

Use to identify the document number.

WPN Waste Profile Number

DLMS Note:

1. Use to identify a Waste Profile Number on the HM/HW profile.

2. Authorized for immediate use. WPN is a migration code available in ASC X12 version 7020.

OTI03 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

M AN 1/30 Must use

OTI08 28 Group Control Number

Description: Assigned number originated and

maintained by the sender

DLMS Note: Use to identify the number cited in

GS06 of the functional group in which the rejected

transaction was transmitted.

X N0 1/9 Used

OTI09 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: Use to identify the transaction set

control number cited in SE02 of the transaction set

being rejected.

O AN 4/9 Used

OTI10 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

DLMS Note: Use to identify the Transaction Set

Number of the transaction being rejected.

All valid standard codes are used. (Total Codes:

298)

O ID 3/3 Used

OTI11 480 Version / Release / Industry Identifier Code

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

O AN 1/12 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004010F824R2RA16 13 August 23, 2023

GS segment is T, then other formats are allowed

DLMS Note: Use to identify the ASC X12

Version/Release used to translate the transaction

set being rejected.

All valid standard codes are used. (Total Codes:

36)

OTI12 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

DLMS Note: 1. Use to identify the Transaction Set

Purpose Code from the Beginning Segment of the

transaction being rejected.

2. When the rejected transaction is a DLMS 940R,

the following codes must be translated from

1/W0501/0200 to their OTI12 equivalents:

W0501 code N is equal to code 00 (zero, zero),

W0501 code X is equal to code 77 (seven, seven)

W0501 code Z is equal to code ZZ

All valid standard codes are used. (Total Codes:

65)

O ID 2/2 Used

OTI13 640 Transaction Type Code

Description: Code specifying the type of

transaction

DLMS Note: Use to identify the Transaction Type

Code from the Beginning Segment of the

transaction being rejected.

All valid standard codes are used. (Total Codes:

446)

O ID 2/2 Used

OTI15 306 Action Code

Description: Code indicating type of action

DLMS Note: Use to identify the Action Code from

the Beginning Segment of the transaction being

rejected, when applicable.

All valid standard codes are used. (Total Codes:

296)

O ID 1/2 Used

OTI17 641 Status Reason Code

Description: Code indicating the status reason

DLMS Note: Use to identify the Status Reason

Code from the Beginning Segment of the

transaction being rejected, when applicable.

All valid standard codes are used. (Total Codes:

387)

O ID 3/3 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 14 August 23, 2023

REF Reference Identification Pos: 020 Max: 12

Detail - Optional

Loop: OTI Elements: 4

User Option (Usage): Must use

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

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

DLMS Note:

1. Use to identify secondary reference numbers associated with 2/OTI02/010, and to identify the materiel.

2. When sending reject advice codes, must use at least one iteration of the REF segment to identify the transaction set of the transaction

being rejected, to include the variant code when applicable.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: 1. Use with the Document Number or

Contract Number identified in 2/OTI02/010 to

identify additional controlling numbers of ELIN,

CLIN, call/order number (for use with contract

number) or suffix code (for use with document

number).

DLMS Note: 1. Use with the Document Number or

Contract Number identified in 2/OTI02/010 to

identify additional controlling numbers of ELIN,

CLIN, call/order number (for use with contract

number) or suffix code (for use with document

number).

2. Use one of codes 1I, FQ, MF, NS, S6, WL, XD, or

ZZ to identify materiel in the same manner it was

identified in the transaction being rejected(e.g. if an

NSN was identified in the transaction being rejected,

that NSN should be identified in DLMS 824R

REF01/02.

2. Use one of codes 1I, FQ, MF, NS, S6, WL, XD, or

ZZ to identify materiel in the same manner it was

identified in the transaction being rejected(e.g. if an

NSN was identified in the transaction being rejected,

that NSN should be identified in DLMS 824R

REF01/02.

3. Use code SJ to identify the transaction set

number of the transaction being rejected to include

the variant code (e.g. 527R).

4. Use codes 17, 78, 8X, X7 ACC, and PRT to

provide beginning segment information, from the

transaction being rejected, when applicable, to

assist in uniquely identifying the rejected

transaction.

5. The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 19)

Code Name

0E Subject Property Reference Number

DLMS Note:

Use to identify the assigned local stock number (LSN).

17 Client Reporting Category

DLMS Note:

Use to identify the Report Type Code (Data Element 755) from the Beginning Segment of the

transaction being rejected, when applicable. A data maintenance action was approved in version 5050.

 The approved code/name is "X13 - Report Type Code ". 

1I Department of Defense Identification Code (DoDIC)

DLMS Note:
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

Code Name

004010F824R2RA16 15 August 23, 2023

1. Use to identify ammunition items when used in the transaction being rejected.

2. DLMS enhancement; see introductory DLMS note 6a.

78 Planning Package

DLMS Note:

Use to identify the Planning Schedule Type Code (Data Element 783) from the Beginning Segment of

the transaction being rejected, when applicable. A data maintenance action was approved in version

5050. The approved code/name is "X10 - Planning Schedule Type Code". 

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

DLMS Note:

Use to identify the ELIN associated with 2/OTI02/010 Code CT.

8X Transaction Category or Type

DLMS Note:

Use to identify the Inventory Transaction Type Code (Data Element 529) from the transaction being

rejected, when DLMS 947I is being rejected. A data maintenance action was approved in version 5050.

 The approved code/name is "X12 - Inventory Transaction Type Code”.

C7 Contract Line Item Number

DLMS Note:

Use to identify the CLIN associated with 2/OTI02/010 Code CT.

FQ Form Number

DLMS Note:

1. Use to identify the form stock number when used in the transaction being rejected. Enter the form

number in REF03. Refer to ADC 1287.

2. DLMS enhancement; see introductory DLMS note 6a.

MF Manufacturers Part Number

DLMS Note:

1. Use to identify the manufacturer's part number for nonstandard materiel when used in the transaction

being rejected. Enter the manufacturer’s part number in REF03. Refer to ADC 1287.

2. Authorized DLMS enhancement; see introductory DLMS Note 6e.

NS National Stock Number

DLMS Note:

Use NSN when used in the transaction being rejected.

S6 Stock Number

DLMS Note:

1. Use to identify the publication stock number when used in the transaction being rejected.

2. DLMS enhancement; see introductory DLMS note 6a.

SJ Set Number

DLMS Note:

Use to identify the transaction set number of the transaction being rejected to include the variant code

when applicable (e.g., 527R).

W8 Suffix

DLMS Note:

Use to identify the suffix code associated with 2/OTI02/010 Code TN. 

WL Federal Supply Classification Code

DLMS Note:

1. Use to identify the Federal Supply Classification number of nonstandard materiel when used in the

transaction being rejected. Use REF03 to provide the appropriate description.

2. DLMS enhancement; see introductory DLMS note 6a.

X7 Batch Sequence Number

DLMS Note:

Use to identify the batch control number from the beginning segment of the transaction being rejected,

when DLMS 517M is being rejected.
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

Code Name

004010F824R2RA16 16 August 23, 2023

XD Subsistence Identification Number

DLMS Note:

Use to identify subsistence items when used in the transaction being rejected.

ZZ Mutually Defined

DLMS Note:

1. Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be

determined (includes management control numbers and locally assigned control numbers) when used

in the transaction being rejected. 

2. DLMS enhancement; see introductory DLMS note 6a.

ACC Status

DLMS Note:

Use to identify the Status Report Code (Data Element 850) from the Beginning Segment of the

transaction being rejected, when applicable. A data maintenance action was approved in version 5050. 

The approved code/name is "X11 – Status Report Code ". 

PRT Product Type

DLMS Note:

Use to identify the Schedule Type Qualifier (Data Element 675) from the Beginning Segment of the

transaction being rejected, when applicable. A data maintenance action was approved in version 5040.

 The approved code/name is "XX7 - Schedule Type Code".

REF02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/30 Used

REF03 352 Description

Description: A free-form description to clarify the

related data elements and their content

DLMS Note: 1. Use with REF01 code WL to provide

a description of the materiel.

2. Use with REF01 codes FQ and MF. Refer to

ADC 1287.

X AN 1/80 Used

REF04 C040 Reference Identifier

Description: To identify one or more reference

numbers or identification numbers as specified by

the Reference Qualifier

O Comp Used

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 2)

Code Name

OQ Order Number

DLMS Note:

1. Use to identify the legacy four position call/order number associated with the CLIN in 2/REF01/020

Code C7.

2. Do not use for the PIID call/order number. The PIID call/order number is mapped to OTI02 Code CT.

 Refer to ADC 1161.

W7 Commercial and Government Entity (CAGE) Code

DLMS Note:

1. Use with REF01 code MF to uniquely identify the manufacturer's part number when cited in the

transaction being rejected.

2. Authorized DLMS enhancement; see introductory DLMS note 6e.
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 17 August 23, 2023

REF04-02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

M AN 1/30 Must use
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 18 August 23, 2023

DTM Date/Time Reference Pos: 030 Max: 2

Detail - Optional

Loop: OTI Elements: 3

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

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

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

DLMS Note:

Use this segment to identify the creation date of the transaction being rejected.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date or time,

or both date and time

DLMS Note: The following codes are authorized.

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 1)

Code Name

097 Transaction Creation

DTM02 373 Date

Description: Date expressed as CCYYMMDD

X DT 8/8 Used

DTM03 337 Time

Description: 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)

DLMS Note: Cite the time the reported transaction

set was originated, if known.

X TM 4/8 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 19 August 23, 2023

NM1 Individual or Organizational Name Pos: 065 Max: 9

Detail - Optional

Loop: OTI Elements: 4

User Option (Usage): Used

Purpose: To supply the full name of an individual or organizational entity

Syntax Rules: 

1. P0809 - If either NM108 or NM109 is present, then the other is required.

2. C1110 - If NM111 is present, then NM110 is required.

Semantics: 

1. NM102 qualifies NM103.

Comments: 

1. NM110 and NM111 further define the type of entity in NM101.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

NM101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 1)

Code Name

Z4 Owning Inventory Control Point

DLMS Note:

For use with 2/LQ01/086 qualifier ET (Reject Advice Code), code value ‘AB’ (Rejected, submitted to

incorrect manager), to identify the correct manager.

NM102 1065 Entity Type Qualifier

Description: Code qualifying the type of entity

DLMS Note: The following codes are authorized.

M ID 1/1 Must use

CodeList Summary (Total Codes: 14, Included: 1)

Code Name

6 Organization

NM108 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 2)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; See introductory DLMS note 6a.

M4 Department of Defense Routing Identifier Code (RIC)

NM109 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 20 August 23, 2023

TED Technical Error Description Pos: 070 Max: 1

Detail - Optional

Loop: TED Elements: 3

User Option (Usage): Used

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

Comments: 

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

DLMS Note:

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

2. This segment is a DLMS enhancement. See introductory DLMS note 6a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

TED01 647 Application Error Condition Code

Description: Code indicating application error

condition

DLMS Note: The following codes are authorized.

M ID 1/3 Must use

CodeList Summary (Total Codes: 162, Included: 2)

Code Name

848 Incorrect Data

DLMS Note:

Use to indicate that specific reject advice is conveyed under 2/LQ01/086. Qualifier ET.

OTH Other

DLMS Note:

1. DLA Transaction Services uses to provide narrative message reject information. Use with the

2/NTE/080 segment

2. DLMS enhancement. See introductory DLMS note 6a.

TED02 3 Free Form Message

Description: Free-form text

O AN 1/60 Used

TED07 724 Copy of Bad Data Element

Description: This is a copy of the data element in

error

DLMS Note: May be used to identify the erroneous

content of the data element.

O AN 1/99 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 21 August 23, 2023

NTE Note/Special Instruction Pos: 080 Max: 100

Detail - Optional

Loop: TED Elements: 2

User Option (Usage): Used

Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction

Comments: 

1. The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processable.

The use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

DLMS Note:

1. DLA Transaction Services uses to provide information previously provided by narrative message rejects. Use only with 2/TED01/070

code OTH-Other.

2. DLMS enhancement. See introductory DLMS note 6a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

NTE01 363 Note Reference Code

Description: Code identifying the functional area or

purpose for which the note applies

O ID 3/3 Used

CodeList Summary (Total Codes: 241, Included: 1)

Code Name

OTH Other Instructions

NTE02 352 Description

Description: A free-form description to clarify the

related data elements and their content

M AN 1/80 Must use
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 22 August 23, 2023

LM Code Source Information Pos: 085 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

DLMS Note:

Use the 2/LM/085 loop to identify coded information maintained in department or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LM01 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

M ID 2/2 Must use

CodeList Summary (Total Codes: 176, Included: 1)

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 23 August 23, 2023

LQ Industry Code Pos: 086 Max: 1

Detail - Mandatory

Loop: LQ Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

DLMS Note: The following codes are authorized.

O ID 1/3 Used

CodeList Summary (Total Codes: 558, Included: 2)

Code Name

0 Document Identification Code

DLMS Note:

1. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS

environment. Continued support of the DIC in a full DLMS environment will be assessed at a future

date.

2. The DIC is not to be applicable to every rejection transaction.

3. May use 2 iterations of LQ01 code 0 when the rejected transaction contained an LQ01 code 0. Use

one iteration with LQ02 code value DZG, when applicable, to represent DLMS 824R equated to

MILSTRAP DIC DZG in a mixed DLSS/DLMS environment. Use another iteration of LQ01 code 0 with

the code value from the transaction being rejected when applicable.

4. Future Streamlined data; See introductory DLMS note 6c.

1. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS

environment. Continued support of the DIC in a full DLMS environment will be assessed at a future

date.

2. The DIC is not to be applicable to every rejection transaction.

3. May use 2 iterations of LQ01 code 0 when the rejected transaction contained an LQ01 code 0. Use

one iteration with LQ02 code value DZG, when applicable, to represent DLMS 824R equated to

MILSTRAP DIC DZG in a mixed DLSS/DLMS environment. Use another iteration of LQ01 code 0 with

the code value from the transaction being rejected when applicable.

4. Future Streamlined data; See introductory DLMS note 6c.

ET Reject Advice Code

DLMS Note:

Use to identify reason original transaction was rejected.

LQ02 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

DLMS Note: Use to cite a code that is contained in

a code source list applicable to the qualifier code

cited in LQ01.

X AN 1/30 Used
DLMS Implementation Convention (IC) 824R

Reject Advice

ADC 160, 179, 248, 330, 436, 471, 1043A, 1043C, 1103, 1136, 1161, 1214A, 1226, 1287, 1367, 1412, 1420 and

1433 DLM 4000.25

004010F824R2RA16 24 August 23, 2023

SE Transaction Set Trailer Pos: 090 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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)

Comments: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SE01 96 Number of Included Segments

Description: Total number of segments included in

a transaction set including ST and SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: This is the number cited in ST02.

M AN 4/9 Must use