1 of 9 

ADC 179 

Attachment 

ATTACHMENT TO ADC 179 

Revisions to DLMS Supplement 824R, Reject Advice, to include DAASC Narrative Rejects, and 

Expansion for Rejection of Additional DLMS Transactions (Contract Administration/Supply) (Staffed 

by PDC 171) 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

b. Points of Contact: DLMSO, Ms. Mary Jane Johnson (Supply), email: 

Mary.Jane.Johnson@dla.mil; and Ms. Ellen Hilert (Supply and Contract Administration), email: 

Ellen.Hilert@dla.mil. 

c. Functional Area: Contract Administration and Supply

2. REQUESTED CHANGE: 

a. Title: Revisions to DLMS Supplement 824R, Reject Advice, to include DAASC Narrative 

Rejects, and Expansion for Rejection of Additional DLMS Transactions (Contract 

Administration/Supply) (Staffed by PDC 171)

b. Description of Change: 

(1) This change expands the scope of DS 824R, Reject Advice, to provide for use with

(a) DAASC narrative message type functional rejects; 

(b) Functional rejection of DLMS contract administration related transactions including 

but not limited to DS 861 (Acceptance Report), DS 856 (Advance Shipment Notice); and DS 567C 

(Contract Completion Status);

(c) Functional rejection of additional supply functional area transactions not to include 

procedures for error identification addressed by the DS 140A Small Arms Reporting, DS 870S Supply 

Status or DS 842A/R DoD Supply Discrepancy Report Reply.

(2) This change revises DS 824R to add DLMS notes to the “Original Transaction 

Information” (OTI) segment to clarify entries. The OTI segment and OTI loop provide information 

used to assist in unique identification of the transaction being rejected. 

(3) This change adds codes to the 2/REF/020 segment of the OTI loop, to address additional 

beginning segment information which is used by some DLMS transactions but that is not covered by 

the 2/OTI/010 segment. The OTI segment provides for beginning segment codes for data element 

640-Transaction Type Code; 306-Action Code; and 641-Status Reason code. However, not all DLMS 

transactions have these codes in the beginning segment. The following beginning segment data 

elements used in DLMS transactions within the scope of DS 824R scope for rejection are not 

addressed in the OTI segment: 675 - Schedule Type Qualifier; 755 - Report Type Code; 783 – 

Planning Schedule Type Code; and 850 Status Report Code. A means to provide this beginning 

segment information, to assist in uniquely identifying the transaction being rejected, is being added to 
2 of 9 

ADC 179 

Att 

the REF segment by this change. Data element 529 – Inventory Transaction Type Code, is also being 

added to the REF segment to assist in uniquely identifying DS 947I transactions being rejected. 

(4) DLMSO is evaluating the requirement for a complementary PDC to expand the ANSI data 

element 1270 qualifier EX, Reject Advice Code, to incorporate additional codes which equate to the 

reasons for narrative message rejects currently used by DAASC. 

c. Alternative: 

 (1) As part of PDC 171 staffing, DLMSO requested that the Components evaluate the DS 

824R Original Transaction Identifier (OTI) segment, and in particular conduct a thorough evaluation 

of the need for OTI12, OTI13, OTI15, and OTI17. These OTI reference identifiers provide beginning 

segment information from the transaction being rejected to assist in identifying the transaction being 

rejected. DLMSO requested the Components advise whether this information was necessary, or can 

the identification of the rejected transaction be accomplished using the control numbers from the GS 

and SE segments of the rejected transaction. The GS and SE control numbers of the rejected 

transaction are carried in DS 824R OTI08 and OTI09 respectively. No comments were received as a 

result of the request. 

 (2) In PDC 171 DLMSO noted that if the GS and SE control numbers were sufficient to 

identify the transaction being rejected, DLMSO recommended making OTI12, OTI13, OTI15, and 

OTI17 not used. Further, it would not be necessary to add the other beginning segments codes to 

2/REF01/020 as proposed at item #10 in the DS 824R change table below. However no comments 

were received in response to staffing indicating that the GS and SE control numbers were sufficient to 

identify the original transaction being rejected. 

d. Procedures (NOTE: No comments were received to PDC 171): 

(1) Revise DoD 4000.25-M, DLMS, Volume 1, Chapter 7 as shown at Enclosure 1. This 

revision will be published in DLMS Change 3. Existing DLMS reject advice codes are shown at 

Enclosure 2 for background information. Reject advice codes are available from the DLMSO website 

at: https://www.dla.mil/j-6/dlmso/

(2) Revise DS 824R, Reject Advice, as follows (changes from PDC 171 are highlighted at 

rows 2 and 19): 

Item 

# 

Location DS 824R (Reject Advice) Revision Reason

Federal 

IC 

Impact
3 of 9 

ADC 179 

Att 

Item 

# 

Location DS 824R (Reject Advice) Revision Reason

Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Revise DLMS introductory note 2:

2. Initially developed for use for rejection of 

DLMS Supplements (DS) 140B, 527D, 527R, 

536L, 650A, 650C, 830R, 830W, 846A, 846D, 

846F, 846I, 846L, 846P, 846R, 846S, 867D, 

867I, 870L, 888B, 888I, 947I, providing 

specific reject advice codes. However the 

DS 824R scope is expanded and it is 

authorized for use with other DLMS supply 

and contract administration transactions not 

specifically identified, but does not 

supersede procedures for error 

identification addressed by the DS 140A 

Small Arms Reporting, DS 870S Supply 

Status or DS 842A/R DoD Supply 

Discrepancy Report Reply. Also used by 

DAASC for narrative message type rejects 

for all DLMS transactions subject to 

rejection by DAASC narrative messages. 

To expand DS 824R 

for use with DLMS 

contract 

administration 

transactions and other 

supply transactions 

beyond those 

originally identified. 

Initially DS 824R was 

developed as a DLMS 

equivalent for 

MILSTRAP DI Code 

DZG Reject transaction 

for use with MILSTRAP 

related DLMS 

transactions. However 

use is being expanded 

for all supply DS, as 

well as contract 

administration, except 

that 824R use does not 

supersede procedures 

for functional error 

identification addressed 

by the DS 140A Small 

Arms Reporting, DS 

870S Supply Status or 

DS 842A/R DoD Supply 

Discrepancy Report 

Reply, as noted in the 

introductory DLMS 

notes and in the 

procedures.

No impact. 

2. DLMS

Introductory 

Notes

Add ADC 178 to DLMS introductory note 6: 

-- ADC 178, Revisions to DS 824R, Reject 

Advice, to include DAASC Narrative Rejects, 

and Expansion for Rejection of Additional 

DLMS Transactions (Contract 

Administration/Supply) 

To identify DLMS 

changes included in 

the DS. 

No impact. 

3. 2/OTI10/010 Add DLMS note:

DLMS Note: Use to identify the Transaction Set 

Number of the transaction being rejected. 

Administrative update 

clarifying use. 

No impact. 
4 of 9 

ADC 179 

Att 

Item 

# 

Location DS 824R (Reject Advice) Revision Reason

Federal 

IC 

Impact

4. 2/OTI12/010 Add DLMS note:

DLMS Note: Use to identify the Transaction Set 

Purpose Code from the Beginning Segment of 

the transaction being rejected.

Administrative update 

clarifying use. 

No impact. 

5. 2/OTI13/010 Add DLMS note:

DLMS Note: Use to identify the Transaction 

Type Code from the Beginning Segment of the 

transaction being rejected.

Administrative update 

clarifying use. 

No impact. 

6. 2/OTI15/010 Add DLMS note:

DLMS Note: Use to identify the Action Code 

from the Beginning Segment of the transaction 

being rejected, when applicable. 

Administrative update 

clarifying use. 

No impact. 

7. 2/OTI17/010 Add DLMS note:

DLMS Note: Use to identify the Status Reason 

Code from the Beginning Segment of the 

transaction being rejected, when applicable. 

Administrative update 

clarifying use. 

No impact. 

8. 2/REF/020 Add new segment level DLMS note 2:

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

Note identifying 

requirement to identify 

the transaction set 

number to include the 

variant code. 

No impact. 

9. 2/REF01/020 Add new DLMS note 3 and 4, and renumber 

existing note 3 as note 5:

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, AAC, and PRT to provide 

beginning segment information, from the 

transaction being rejected, when applicable, to 

assist in uniquely identifying the rejected 

transaction. 

Note identifying 

requirement to identify 

the transaction set 

number to include the 

variant code. 

No impact. 
5 of 9 

ADC 179 

Att 

Item 

# 

Location DS 824R (Reject Advice) Revision Reason

Federal 

IC 

Impact

10. 2/REF01/020 Add the following date element 128 qualifiers

with DLMS notes:

8X Transaction Category or Type 

DLMS Note: Use to identify the Inventory 

Transaction Type Code (Data Element 529) 

from the transaction being rejected, when DS 

947I is being rejected. 

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. 

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.

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. 

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. 

To provide beginning 

segment codes from 

rejected transactions 

not covered by the 

2/OTI/010 segment. 

These codes will 

assist in uniquely 

identifying the 

transaction being 

rejected. 

DLMSO is submitting 

data maintenance to 

request these 

beginning segment 

data elements be 

added to the OTI 

(Original transaction 

Information) segment.

No impact. 

11. 2/REF01/020 Add code ‘SJ-Set Number’ with DLMS note:

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

Provides a means to 

indicate the full 

transaction set 

number to include the 

variant code since the 

OTI segment only 

provides for entry of a 

3 position transaction 

set number. 

No impact. 
6 of 9 

ADC 179 

Att 

Item 

# 

Location DS 824R (Reject Advice) Revision Reason

Federal 

IC 

Impact

12 2/TED/070 Delete DLMS segment level note 2:

DLMS Note 2: Use multiple repetitions of this 

segment to identify multiple errors within the 

reported transaction set.

AS currently designed, 

the LQ segment which 

contains the Reject 

Advice Code is not an 

embedded loop within 

the TED loop. 

Accordingly the Reject 

Advice Code cited in 

LQ could not be linked 

to the specific TED 

information if multiple 

iterations of TED were 

used. 

NOTE: Multiple errors 

can be identified as 

follows: 

(1) multiple iterations 

of TED can be used 

with narrative 

message rejects 

(TED01 code OTH). 

(2) Multiple iteration 

of the LQ segment can 

be used to provide 

multiple reject advice 

codes (used with 

TED01 code 848). 

No impact. 

13 2/TED01/070 Add Code OTH-Other: 

OTH Other 

DLMS Note: 1. DAASC uses to provide 

narrative message reject information. Use with 

the 2/NTE/080 segment. 

2. DLMS enhancement. See DLMS 

introductory note 4.a. 

Expands capability to 

accommodate DAASC 

use of 824R to provide 

narrative message 

reject information. 

No impact 
7 of 9 

ADC 179 

Att 

Item 

# 

Location DS 824R (Reject Advice) Revision Reason

Federal 

IC 

Impact

14 2/TED08/070 Change TED08, Data Element New Content, to

NOT used. 

DS 824R is intended 

to provide reject 

advice only. TED08 

would apply when 

using an 824 

Application Advice 

transaction to accept 

a transaction with data 

content change. DS 

824R is not used for 

this purpose. 

Revision 

required. 

15 2/NTE/080 Open the NTE segment.

Add DLMS Segment level notes: 

1. DAASC uses to provide information 

previously provided by narrative message 

rejects. Use only with 2/TED01/070 code OTHOther. 

2. DLMS enhancement. See DLMS 

introductory note 4.a. 

To document DAASC 

process for providing 

narrative message 

rejects using DS 

824R. 

Revision 

required. 

16 2/NTE01/02/

080 

Open NTE01 and NTE02. Add Code OTH to 

NTE01:

OTH Other Instructions 

To provide for 

narrative message 

reject information. 

Revision 

required. 

17 2/LM/085 Revise segment level DLMS note to remove the 

word “Must”.

Use is not required 

when DAASC 

provides narrative 

message type reject 

information in the TED 

loop using the NTE 

segment. 

No impact. 
8 of 9 

ADC 179 

Att 

Item 

# 

Location DS 824R (Reject Advice) Revision Reason

Federal 

IC 

Impact

18 Revise DLMS note 2 for code 0: 

0 Document Identification Code 

DLMS Note 2: 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 DS 824R equated to DI Code 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.

Revise note as necessary 

since DS 824R use is 

expanded beyond scope 

of MILTSRAP DI Code 

DZG. 

No impact. 

19 2/LQ01/086 Revise DLMS note for code ET to remove 

specific DS. 

ET Reject Advice Code 

DLMS note: Use to identify reason original 

transaction was rejected. Use for rejection of 

the following transaction sets: 140B, 527D, 

527R, 536L, 650A, 650C, 830R, 830W, 846A, 

846D, 846F, 846I, 846L, 846P, 846R, 846S, 

867D, 867I, 870L, 888B, 888I, and 947I.

Initially DS 824R was 

developed as a DLMS 

equivalent for MILSTRAP 

DI Code DZG Reject 

transaction for use with 

MILSTRAP related DLMS 

transactions. However use 

is expanded for contract 

administration and all 

supply DS except that 

824R use does not 

supersede procedures for 

functional error 

identification addressed by 

the DS 140A Small Arms 

Reporting, DS 870S 

Supply Status or DS 

842A/R DoD Supply 

Discrepancy Report Reply, 

as noted in the introductory 

DLMS notes and in the 

procedures. 

No impact. 

3. REASON FOR CHANGE: This change expands the scope of DS 824R to provide for its use for

DAASC narrative message reject and for functional rejection of additional DLMS transactions 

including contract administration and supply functional areas. This change also provides updates 

clarifying use of the Original Transaction Information (OTI) segment; provides for entry of the 

original transaction set number to include the variant code; and provides for other data to assist in 

uniquely identifying the transaction being rejected. 

4. ADVANTAGES/DISADVANTAGES:

a. ADVANTAGES 

(1) Supports DS 824R for DAASC narrative message type rejects and supports functional 

reject of DLMS contract administration related transactions and additional supply transactions. 
9 of 9 

ADC 179 

Att 

(2) Adds data to assist in uniquely identifying the transaction being rejected.

b. Disadvantages: None identified.

5. INTERFACE/IMPACT: 

a. Data Content/Procedures: Component systems must incorporate additional DS 824R 

capability.

b. Publication(s): DLMS manual and DS 824R.

2 Enclosures
C7-1 

ADC 179 

Enclosure 1 

DLMS Vol 1, Chapter 7 

ENCLOSURE 1 to ADC 179 

Revisions to DLMS Supplement (DS) 824R, Reject Advice, to include DAASC Narrative Rejects, 

and Expansion for Rejection of DS 861, DS 856, and DS 567C (Contract Administration/Supply) 

C7. CHAPTER 7

FUNCTIONAL APPLICATION ERRORS

C7.1. INTRODUCTION

C7.1.1. Purpose. A variety of different application systems used by the DoD Components, 

Federal agencies, contractors, and foreign governments will exchange DSs to Federal ICs. The 

primary purpose of this manual is to establish standards through which all of these varied systems can 

work in unison. This unison will be both on a technical and functional basis. If systems comply fully 

with these standards, errors should not occur. Nonetheless, errors will occur due to various 

circumstances and a mechanism must exist for dealing with them. This chapter describes use of DS to 

Federal IC 824R, Reject Advice, for functional errors not covered by DLMS status transactions. 

DS 824R is not used to reject a transmission due to ASC X12 syntactical errors. A Federal IC 

997, Functional Acknowledgment, transaction is used for that purpose (reference Chapter 6 this 

volume). 

 C7.1.2. Error Reduction. The primary means for reducing errors is for each DoD Component to 

ensure that outbound transactions are thoroughly edited to fully comply with these standards as well as 

complying with any DoD Component-unique requirements. Still, receiving applications will likely 

perform edits to preclude processing erroneous transactions that may cause incorrect actions, disrupt 

the integrity of other data, or even disrupt the operation of the system as a whole. 

 C7.1.3. Error Reporting. When receiving applications apply edit checks and discover functional

errors, the errors may be reported back to the originating activity using DS 824R, Reject Advice.

C7.2. DS 824R, REJECT ADVICE

 C7.2.1. Implementation Convention Content. The reject DS shall convey the following 

information when reporting errors to the originator: 

 C7.2.1.1. Table 1 data: identifies the originator of DS 824R and the recipient, which is 

the originator of the erroneous transaction being rejected. 

 C7.2.1.2. Table 2 data includes: 

 C7.2.1.2.1. Transaction identification of the erroneous transaction to include: 

 C7.2.1.2.1.1. Transaction number or contract number. 

 C7.2.1.2.1.2. Transaction set control number. 
DLMS Vol 1, Chapter 7 

ADC 179 

Encl 1 

C7-2

 C7.2.1.2.1.3. Transaction set identifier code. 

 C7.2.1.2.1.4. Beginning segment information as applicable to include 

transaction set purpose code, transaction type code, report type code, action code, etc. 

 C7.2.1.2.1.5. Identifying material number (e.g., National Stock Number; part 

number/CAGE, etc.). 

 C7.2.1.2.1.6. Transaction creation date. 

 C7.2.1.2.2. The Application Error Condition Code identifying the type of error. 

 C7.2.1.2.3. Option of providing a copy of the bad data element. 

 C7.2.1.2.4. A free-form text message describing the error, which the rejecting 

software can add as an option. 

C7.2.2. Reject-Error Routing. Routing of the reject is from the rejecting activity to the sending 

activity. This will typically lead to one of two scenarios: 

 C7.2.2.1. DAASC Transaction Reject. In this case DAAS, using the DS 824R, shall report 

the error back to the originating activity which must correct the transaction and retransmit it. 

 C7.2.2.2. Activity Transaction Reject from DAAS. An activity receiving a transaction 

from DAAS shall report the error back to the transaction originator via DAAS using DS 824R. 

DAAS will compare the reject information to an image of the transaction as they received it from the 

originating activity. If DAAS determines it caused the error, DAAS shall correct and retransmit the 

transaction. If DAAS determines the originating activity caused the error, then DAAS shall initiate 

another reject back to the originating activity, as in the first scenario. 

C7.2.3. Use of DS 824R, Reject Advice. 

 C7.2.3.1. Rejection by Specific Reject Advice Code. Initially, DS 824R was developed to 

reject DSs 140B, 527D, 527R, 536L, 650A, 650C, 830R, 830W, 846A, 846D, 846F, 846I, 846P, 

846R, 846S, 867D, 867I, 870L, 888B, 888I, and 947I citing specific reject advice codes in the LQ 

segment.. However DS 824R is also authorized for use with other DLMS supply and contract 

administration transactions not specifically identified, but does not supersede procedures for error 

identification addressed by the DS 140A Small Arms Reporting, DS 870S Supply Status or DS 

842A/R DoD Supply Discrepancy Report Reply. DS 824R reject advice codes may be expanded in 

the future as requirements are identified and put in place. 

 C7.2.3.2. DAAS Rejects. DAASC uses DS 824R to provide narrative message rejection 

of any DLMS transaction as described under DAASC Receipt and Generation of DS 824R.

C7.2.4. Summary of Use. The DoD Component application programs shall use DS 824R to 

reject a received transaction which the application program cannot process back to the sending 

activity. The reject DS reports the unique transaction number of the erroneous transaction and codes 

identifying one or more specific error conditions. 

C7.2.5. Characteristics of Use
DLMS Vol 1, Chapter 7 

ADC 179 

Encl 1 

C7-3

 C7.2.5.1. EDI Translator-Identified Errors - Use of DS 824R. In some cases this closely 

parallels generation of rejects by the receiving activity's EDI translator. The translator should identify 

any of the following types of errors: 

 C7.2.5.1.1. Errors in the ISA/IEA envelope segments. 

 C7.2.5.1.2. Errors in the GS/GE functional groups segment. 

 C7.2.5.1.3. Errors in a transaction set. Typical of this type of error is: 

 C7.2.5.1.3.1. Failure to use an ASC X12-mandatory or DLMS required segment 

or data element. 

 C7.2.5.1.3.2. Use of an ASC X12 code that is not included in the DS. 

 C7.2.5.1.3.3. A data error which prevents DAASC from proper conversion 

during translation. Examples include where the number of characters exceed or are less than 

number authorized, e.g., DoDAAC greater or less than six, port code greater than three, etc. 

 C7.2.5.1.3.4. A data error that prevents DAASC from routing the transaction 

correctly. Examples include invalid “TO Addressee,” invalid MCA, etc.

 C7.2.5.2. Application Identified Errors - Possible Errors. Even with stringent editing 

performed by the EDI translator, some error conditions will occur which only the more complex 

application program edits can identify. Such errors could include: 

 C7.2.5.2.1. Invalid item identification. 

 C7.2.5.2.2. Quantity of zero when a quantity is required. 

 C7.2.5.2.3. Invalid DLMS code received in LQ02. DS 824R applies only when a 

received DS fails to comply with the rules/format specified in the DS.

 C7.2.5.3. Violations of DoD Business-Process Rules for which reject advice codes have 

been identified.

 C7.2.5.3.1. Exceptions. DS 824R does not apply when specifying violation of a DoD 

Component or activity business policy.

 C7.2.5.3.2. Reporting. Reporting these types of errors is accomplished through the 

DS specified in the appropriate functional volume. Frequently, the same DS number used in the 

erroneous transaction set applies for reporting back the errors. 

 C7.2.5.4. DAASC Receipt and Generation of DS 824R

 C7.2.5.4.1. Processing Data. As DAAS receives DLMS interchange envelopes it will 

process the data through an EDI translator and then break the contents down to the transaction level. 

DAAS shall apply applicable DLMS and the DoD Component edit checks on received transactions. 

 C7.2.5.4.1.1. If DAAS software detects a non-business-process error, it will 
DLMS Vol 1, Chapter 7 

ADC 179 

Encl 1 

C7-4

reject the transaction back to the sender using Federal IC 997, or DS 824R, as applicable. 

 C7.2.5.4.1.2. If DAASC detects data errors preventing the correct routing or 

processing of the transaction, DAASC will reject the transaction back to the originator with a DS 

824R containing a narrative message in the NTE segment identifying the error(s) which prevented 

the routing/processing. DAASC will also use the NTE segment to identify the GS sender 

identification, the GS control number, and the ST control number 

 C7.2.5.4.2. Loading Transactions. DAAS shall load transactions which do not 

contain errors into the Logistics Online Tracking System. 

 C7.2.5.4.3. Detecting Non-Business Process Errors. Application software which 

receives data sent from DAAS and detects non-business-process errors in a transaction shall use DS 

824R to reject the transaction. DAAS shall access the transaction identified in the reject and compare 

the image DAAS received from the originator to the image DAAS retransmitted. If the two images are 

different, then DAAS will correct the transaction and retransmit it. If the two images are the same, 

DAAS will forward the reject to the originating activity. 

C7.2.6. Levels of Errors

 C7.2.6.1. Substantial Errors. Organizations receiving DLMS transactions shall use DS 

824R to report errors only when the error is so substantial that the receiving application software 

cannot process the transaction. The receiving translator (or application software if the translators do 

not detect the error) shall reject a transaction whenever segment(s) or data element(s) identified as 

mandatory or required by DS are not present (see Chapter 6 of this volume on use of Federal IC 997). 

 C7.2.6.2. Non-Fatal Errors. Other "non-fatal" errors, such as failing to transmit 

recommended data elements, that still allow the transaction to be processed, are not subject to reject. 

Receiving organizations which identify a high number of "non-fatal" errors originating from a single 

activity shall notify that activity in writing and send a copy of the correspondence to their own, and the 

offending organization's, functional area Process Review Committee (PRC) representative and to the 

appropriate DLMS PRC Chair. 

 C7.2.6.3. Optional Data Elements. Segments and data elements listed as optional in DSs

are optional at the discretion of the transmitting activity. The receiving translator or application 

software shall never reject a transaction based on omission of optional segments or elements. 
1 of 2 

ADC 179 

Enclosure 2 

ENCLOSURE 2 to ADC 179 

Revisions to DLMS Supplement (DS) 824R, Reject Advice, to include DAASC Narrative Rejects, and Expansion for 

Rejection of DS 861, DS 856, and DS 567C (Contract Administration/Supply) 

Data Element 1270 Qualifier ET

REJECT ADVICE CODES

EXPLANATION: Identifies to the originator of a transaction, the reason for rejection, and indicates 

return of the transaction for correction and resubmission.

Codes are available on-line at: http://www.dla.mil/j-6/dlmso/eApplications/Logdrms/logview/LQVSearch.asp 

CODE EXPLANATION

AA Rejected. Document identifier code invalid. (For use in mixed DLSS/DLMS environment. To be 

streamlined out) 

AB Rejected. Submitted to incorrect manager; routing identifier code of correct manager indicated, if 

known. 

AC Rejected. Type of physical inventory code invalid or blank. 

AD Rejected. Stock or part number unidentifiable. 

AE Rejected. Quantity field invalid. 

AF Rejected. Transaction number invalid. 

AG Rejected. Ship-to address unidentifiable. 

AH Rejected. Required signal code invalid or blank. 

AJ Rejected. Required fund code invalid or blank. 

AK Rejected. Ownership/purpose code invalid or blank. 

AL Rejected. Cumulative total of all reversals exceeds the original transaction quantity. (Approved by 

MILSTRAP AMCL 13.) 

AM Rejected. Supply condition code invalid or blank. 

AN Rejected. No record of original transaction or contract number matching the attempted reversal 

action. (Approved by MILSTRAP AMCL 13.) 

AP Rejected. Required management code invalid or blank. 

AQ Rejected. Processing/count date invalid or blank. Location Reconciliation Request cutoff date 

invalid. 

AR Rejected. Unit of issue incorrect. 

AS Rejected. Support date invalid. Location Reconciliation Request and/or Transaction History 

Transmittal received past scheduled deadline. 

AT Rejected. Asset support request code invalid or blank. 
2 of 2 

ADC 179 

Encl 2 

CODE EXPLANATION

AU Rejected. Asset support request is for an item not centrally managed and stocked (Acquisition 

Advice Codes F, L, P, or W). 

AV Rejected. Activity is not authorized to submit LASE transactions. 

FROM Activity identified in Location Reconciliation Request is not valid. 

AW Rejected. Logistic Reassignment (LR) Transfer and Decapitalization Transaction, or LR 

Memorandum Due-in, received more than 1 year after the ETD. (The LR Memorandum Receipt 

will be rejected if no memorandum due-in is on record at the GIM to indicate it is a valid 

procurement receipt.) 

AX Rejected. GSA is SOS for requested LASE or SPR. GSA does not participate in MILSTRAP 

LASE and SPR procedures. If required, submit funded DoD requisition citing applicable required 

delivery date. 

AY Rejected. Location Reconciliation Request and/or Transaction History Transmittal does not equal 

the number of transactions recorded in the Location Reconciliation Notification and/or Location 

Reconciliation History Notification. 

AZ Rejected. Number of Location Reconciliation Requests received from storage activity exceed 

reasonable variance from owner/manager.