DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J . KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

August 20, 2014 

MEMORANDUM FOR SUPPLY AND FINANCE PROCESSS REVIEW COMMITTEES 

(PRCs) 

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1103, 

Revise DLMS 824R, Reject Advice, to Include Rejections of Logistics Bills, 

Clarify use for Rejection ofDLMS MILSTRIP Transactions, and Document 

Administrative Updates (Finance/Supply) 

The attached change to DLM 4000.25, Defense Logistics Management System is 

approved for staggered implementation. 

Addressees may direct questions to Mr. Robert Hammond, Chair, Finance PRC, email 

finance@hq.dla.mil; Ms. Ellen Hilert, Co-Chair, Supply PRC, email: ellen.hilert@dla.mil or; 

Ms. Heidi Daverede, DOD MILSTRIP Alternate, 703-767-5111 ; DSN 427-5111 , e-mail: 

heidi.daverede@dla.mil. Others must contact their Component/ Agency designated 

representative shown at : https://www2.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

(DOD Common Access Card restricted). 

Attachment 

As stated 

cc: 

ODASD (SCI) 

~p~ Director 

Defense Logistics Management 

Standards Office 
Attachment to 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

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Defense Logistics Management Standards Office (DLMSO)

b. Functional POC: DLMSO

(1) Finance: Robert Hammond, Chair, Finance PRC, email: finance@hq.dla.mil

(2) Supply: Ellen Hilert, Co-Chair, Supply PRC, email: ellen.hilert@dla.mil

2. FUNCTIONAL AREAS: Finance and Supply

3. REFERENCES:

a. Approved DLMS Change (ADC) 179, Revision to DLMS Supplement 824R, Reject 

Advice, to Include DAASC Narrative Rejects, and Expansion for Rejection of Additional DLMS 

Transactions, dated September 13, 2005

b. Approved Addendum to ADC 1043 (ADC 1043A), Revised Procedures for 

Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification 

to Support Transaction Rejection Requirements, dated August 20, 2014

c. ADC 1043, Revisions for Department of Defense (DOD) Standard Line of

Accounting (SLOA)/Accounting Classification (Finance/Supply), dated September 18, 2013

d. ADC 400, Elimination of the DLMS-MILSTRAP Logistics Asset Support Estimate 

(LASE) Process no Longer Required by the DOD Components, dated April 11, 2012

e. DLM 4000.25, Defense Logistics Management System, linked at 

www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp

f. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP), 

linked at www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp

g. DLM 4000.25-2, Military Standard Transaction Reporting and Accountability 

Procedures (MILSTRAP), linked at www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp

4. APPROVED CHANGE(S):

a. Brief Overview: This change modifies the DLMS 824R to expand the scope to 

include rejection of logistics bills and make administrative adjustments to convert the 

Attachment, ADC 1103

page 1
supplement into an implementation convention (IC) and to reflect current element use by DLA 

Transaction Services. Significant modifications to this DLMS change since staffing the PDC are 

highlighted in green.

b. Background:

(1) DLMS 824R was initially developed for rejection of DLMS transactions 

associated with MILSTRAP providing legacy Document Identifier Code DZG functionality, 

with specific reject advice codes. However, the 824R scope was expanded under the DLMS 

concept of operations and was authorized for use with other DLMS supply transactions 

(Reference 3.a.). In practice, it was also being used for DLMS Finance transactions with 

narrative messages citing the reason for rejection. DLMS 824R is specifically intended to be 

used by DLA Transaction Services for narrative message type rejects for DLMS transactions 

subject to rejection by Defense Automatic Addressing System (DAAS) narrative messages, as 

well as coded rejects using the Reject Advice Code in the 2/LQ/086 segment.

(2) This change was developed concurrent to ADC 1043A (Reference 3.b.). ADC 

1043A defines the DLMS 824R as the common means for communicating when a DLMS 

transaction fails a new edit established under ADC 1043 (reference 3.c.), relevant to specific 

supply and finance DLMS transactions.

c. Procedures, Transactions, Data Elements, and Processing Details in Use Today

(Finance): Logistics Bills, DLMS 810L (MILSBILLS legacy DIC F-series/G-series), are 

rejected by returning the rejected bill with a narrative reason for rejection. DLA Transaction 

Services rejects bills using the DLMS 824R with the appropriate narrative, but there are no 

rejection code qualifiers to facilitate automation and analysis and use of DLMDS 824R was not 

previously documented in DLMS for this purpose.. DLA Transaction Services also includes a 

one record position reject reason code in RP 4 of the legacy Summary Bill and in MILSINQ.

Currently used codes and reasons for rejection include:

V - Unauthorized "Bill To"

• ADDR BILL TO NOT AUTHORIZED FOR INTERFUND USE

• BILL OFC ADDR NOT AUTHORIZED FOR INTERFUND USE

• VALIDATE VALUE OF FE/GE ENTRY

W - F3885 Not Authorized

• ACCOUNT UNAUTHORIZED FOR USE IN INTERFUND BILL

X - Dollar Value Summary not equal to Details

• DOLLAR VALUE OF DETAIL NOT EQUAL TO SUMMARY

Y - Card Count Summary not equal to Details

• DOC COUNT NOT EQUAL TO COUNT IN RP 5-7 OF SBR

Attachment to ADC 1103

Page 2
Z - Invalid "Bill To"

• BILLING ADDRESS IN RP 30-35 NOT IN DAAS RECORDS

• ADDR BILL TO IS INVALID FOR DOCUMENT ID

STAFFING NOTE: DLA Transaction Services has shortened all legacy transaction reject 

narratives to a maximum of 53 characters to accommodate internal DLA Transaction business 

processes. For example, MILSBILLS reject narrative for reject code Y was changed from " DOC 

COUNT NOT EQUAL TO COUNT IN RP 5-7 OF SUMMARY BILL" to "DOLLAR VALUE 

OF DETAIL NOT EQUAL TO SUMMARY". It was not anticipated that these changes impact 

legacy systems; however, Components were asked to identify any known potential impacts. No 

impacts were reported during staffing.

d. Approved Change in Detail: 

(1) Document finance as within the scope of the 824R and the existing narrative 

messages.

(2) Establish Reject Advice Codes BV, BW, BX, BY, and BZ to accommodate 

current reasons for rejection of the DLMS 810L, Logistics Bill.

(3) Document the existing capability at DAAS to reject finance transactions 

using DLMS 824R with narrative messages.

(4) In accordance with new DLMS naming conventions, update previous 

references to “DLMS Supplements” with “DLMS Implementation Conventions”.

(5) Transition notes from Federal Notes to DLMS Notes as appropriate and 

remove all Federal Notes.

(6) Document current usage of BGN04 and BGN05 by DLA Transaction 

Services.

(7) Document transaction rejection applicability to supply transactions 

(MILSTRIP/MILSTRAP) in DLM Supply Volume.

e. Revisions to DLM 4000.25 Manuals:

(1) Modify DLM 4000.25, Volume 1, Chapter 4 to better represent existing 

procedures and to indicate that the 824R is applicable to DLMS finance transactions.

“C4.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:

C4.2.2.1. DLA Transaction Services Transaction Reject. In this case Defense 

Automatic Addressing System (DAAS) shall uses the DLMS 824R, Reject Advice Transaction, 

Attachment to ADC 1103

Page 3
to report the error back to the originating activity, which must correct and retransmit the 

transaction. 

C4.2.2.1.1. The Reject Advice Transaction reports the unique document number 

of the erroneous transaction and/or other pertinent information to identify the erroneous 

transaction including reject advice codes (when available) identifying one or more specific error 

conditions.

C4.2.2.1.2. Where specific reject advice codes are not established to identify the 

error condition causing the transaction to fail, DLA Transaction Services uses the DLMS 

824R to provide narrative message rejection of any DLMS transaction using procedures 

described in paragraph C4.2.4.2.

C4.2.2.1.3. A combination of reject advice codes and clarifying narrative may 

be used to facilitate interpretation of the error condition.

C4.2.2.2. Activity Transaction Reject fromto DAAS. A potential future enhancement 

will allow aAn activity receiving a transaction from DAAS shallto report the error back to the 

transaction originator using DLMS 824R.1 Under the planned enhancement DAAS shallwill

compare the rejected information to an image of the transaction as they received it from the 

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

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

DAAS shallwill initiate another Reject Advice Transaction back to the originating activity, as in 

the first scenario.

C4.2.3. Application Program Use of DLMS 824R, Reject Advice. If a DoD Component 

application program cannot process a received transaction, it shallwill send a DLMS 824R, 

Reject Advice Transaction back to the sending activity. The Reject Advice Transaction reports 

the unique document number, and/or other pertinent information to identify of the erroneous 

transaction, and codes identifying one or more specific error conditions.

C4.2.3.1. Rejection by Specific Reject Advice Code 

C4.2.3.1.1 Initially, DLMS 824R was developed to provide the functionality of 

legacy Military Standard Transaction Reporting and Accountability Procedures (MILSTRAP) 

Document Identifier Code (DIC) DZG, Transaction Reject. As such it rejects the following 

DLMS transactions with legacy MILSTRAP functionality: DLMS Transactions 527D, 527R, 

536L, 830R, 830W, 846A, 846D, 846F, 846I, 846P, 846R, 846S, 867D, 867I, 870L, 888I, and 

947I, citing specific reject advice codes in the LQ segment. 

C4.2.3.1.2. Additionally, the DLMS 824R is authorized for use with other DLMS 

supply (including MILSTRIP transactions), finance, and contract administration transactions 

that are not specifically identified in this chapter.

C4.2.3.2. However, uUse of DLMS 824R does not supersedereplace procedures for 

error identification addressed by DLMS 140A, Small Arms and Light Weapons (SA/LW),

DLMS 870S, Supply Status, or DLMS 842A/R, DoD Supply Discrepancy Report Reply. DLMS 

824R codes may be expanded in the future as requirements are identified and implemented.

Attachment to ADC 1103

Page 4
---------------------------------------------

1 Not available for use without prior coordination.

 C4.2.3.2. DAAS Rejects. DLA Transaction Services uses the DLMS 824R to 

provide narrative message rejection of any DLMS transaction as described in paragraph 

C4.2.4.3.

C4.2.4. Characteristics of Use

C4.2.4.1. Application Identified Error Examples. Even with stringent editing 

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

application program edits can identify. These errors may include:

C4.2.4.1.1. Invalid item identification.

C4.2.4.1.2. Quantity of zero when a nonzero quantity is required.

C4.2.4.1.3. Invalid DLMS code received in the LQ02 Segment. The DLMS

824R applies only when a received transaction fails to comply with the application-level 

rules/formats specified in the DLMS Supplement implementation convention.

C4.2.4.2. Violations of DoD Business Process Rules Where Reject Advice Codes Are 

Identified

C4.2.4.2.1. Exceptions. DLMS 824R does not apply when specifying violation 

of an internal DoD Component or activity business policy. 

C4.2.4.2.2. Reporting. Receivers of transactions containing these types of errors 

shall report the errors back to the sender using the DLMS Supplement specified in the 

appropriate functional volume. Frequently, the same DLMS Supplement number used in the 

erroneous transaction set is also used to report back the errors.

C4.2.4.23. DLA Transaction Services Receipt and Generation of DLMS 824R Reject 

Advice”

{Renumber subparagraphs of current C4.2.4.3. to C4.2.4.2.}

(2) Revise DLM 4000.25, Volume 2, Chapter 1 to document applicability of 

DLMS 824R to the supply functional area and update table of contents.

“C1.9 TRANSACTION REJECTION. DLMS Volume 1, Chapter 4 prescribes the 

procedures for the use of the DLMS 824R Reject Advice Transaction to exchange information 

about functional errors not covered by DLMS status or other type of supply transaction, 

including MILSTRIP and MILSTRAP functional areas. The Reject Advice Transaction 

reports the unique document number, and/or other pertinent information to identify the 

rejected transaction, and codes identifying one or more specific error conditions. Where 

specific reject advice codes are not established to identify the error condition causing the 

transaction to fail, DLA Transaction Services may use the Reject Advice Transaction to 

Attachment to ADC 1103

Page 5
provide narrative message rejection of the erroneous DLMS transaction. A combination of 

reject advice codes and clarifying narrative may be used to facilitate interpretation of the error 

condition.”

(3) Modify DLM 4000.25-2, MILSTRAP Appendix 2.8 Reject Advice Codes to 

include codes supporting existing DAAS logistics bill reject codes.

BV Rejected. DoDAAC in the transaction does not have the appropriate authority code for 

its intended use

BW Rejected. Suspense account is not authorized for Interfund use 

BX Rejected. Total dollar value detail of bills is not equal to total dollar value of the 

summary bill

BY Rejected. Count of detail bills is not equal to the count in the summary bill (MILS RP 

5-7, DLMS 810L 3/CTT01/070)

BZ Rejected. DoDAAC is not valid in DAAS

(4) Modify DLM 4000.25, Volume 4, Appendix 2.11 to add a listing for “Reject 

Advice Code” with DLM 4000.25-2 as the authoritative source.

(5) Modify DLM 4000.25, Volume 4, Chapter 2 to document use of DLMS 824R

to reject logistics bills.

C2.2.3.2.6. DLA Transaction Services will reject bills when they fail any of the 

edits. See Chapter 6.2 for information about the routing and editing of bills processed through 

DLA Transaction Services. Rejected bills will be reported back to the originating activity using 

DLMS 824R (Reject Advice Transaction) citing the applicable Reject Advice Code from DLM 

4000.25-2, MILSTRAP, Appendix 2.8. Rejected bills may include will be returned to the 

originating communications center with a narrative description indicating the reason for rejection

in addition to the Reject Advice Code. Billing offices will correct the rejected bills and resubmit 

them to the DLA Transaction Services. Billing offices will ensure that all appropriate 

adjustments for rejected billings and interfund collections are made to seller accounting records.

(6) Revise DLM 4000.25, Volume 4, Chapter 6 to document use of DLMS 824R 

as the transaction for DAAS to report back rejected bills to the originator or originating 

communications center:

“C6.2.2. Bill Editing and Billed Error Rejection

C6.2.2.1. DAAS shall will edit and reject any bill that fails any of the following edits:

....[intervening text not shown]

C6.2.2.2 Rejected bills will be reported back to the originating activity using DLMS 

824R (Reject Advice Transaction) citing the applicable Reject Advice Code from DLM 

Attachment to ADC 1103

Page 6
4000.25-2, MILSTRAP, Appendix 2.8. Rejected bills shall be returned to the originator or 

originating communications center and may include a narrative description indicating the reason 

for rejection in addition to the Reject Advice Code. In addition, the second record position of 

the Reject Advice Code will be inserted in rp4 of the MILSBILLS legacy DIC FS_/GS_ 

Summary Bill and displayed in MILSINQ, hyperlinked to the narrative reason for rejection.”

(7) Update DLM 4000.25 Volume 4, Appendix 3 Record Format:

DIC FS1/FS2/GS1/GS2 FORMAT

SUMMARY BILLING RECORD

Field Legend Position(s) Entry and Instructions

DI Code 1-3 Enter 

FS1 or GS1 (net charge)

FS2 or GS2 (net credit).

Internal Service Use 4 Reserved for internal billed office use. 

Billing office will leave blank. Used by DAAS

to indicate reason for bill rejection based on 

the second character of the applicable reject 

advice code; see DLM 4000.25-2, 

MILSTRAP, Appendix 2.8[1]

1 See ADC 1103.

(8) Revise DLMS 824R as shown in Enclosure 1.

f. Alternatives: None identified.

g. Proposed DLMS Change (PDC) 1103 Staffing Response/Comment Resolution: 

Concurrence and resolution of comments is shown at Enclosure 2.

5. REASON FOR CHANGE: Documents expanded use of DLMS 824R to reject logistics 

bills for functional business rules reasons, administrative updates, and clarification of procedures 

and use.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Formally documents the approach for reporting rejections of finance 

using narrative message and enables the use of the coded means for better analysis.

b. Disadvantages: None identified.

Attachment to ADC 1103

Page 7
7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Staggered implementation 

will be permitted after DLA Transaction Services target implementation to support September 

30, 2014 SLOA implementation.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

9. IMPACT:

a. DLMS Data Elements/LOGDRMS: Update Reject Advice Codes as described 

above.

b. Automated Information Systems (AIS): DLMS-compliant Service systems must be 

able to receive/create the 824R Reject Advice as documented in this ADC. Applicable to supply 

and finance systems.

c. DLA Transaction Services:

(1) Since reject advice codes are two character codes, DAAS will have to 

program for MILSINQ to ignore the first character in inserting the reject code in rp 4. The 

second character of the reject advice codes are the same as the existing single character codes 

used at DAAS.

(2) Update mapping for DLMS 824R according to changes to the REF and LQ 

segments as shown in Enclosure 1.

Attachment to ADC 1103

Page 8
ENCLOSURE 1

Revisions to DLMS 824R

# Location DLMS 824R Reject Advice Reason

1. Introductory 

Notes

Transition existing Federal Notes 1 & 2 to DLMS 

Notes, remove the remaining Federal Note, modify

existing DLMS Note 2, renumber all existing DLMS 

Notes and update references within the IC:

Federal 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. DoD logistics users should refer to the Defense 

Logistics Management System (DLMS) Supplement to the 

Federal Implementation Convention (IC) available at 

URL: http://www.dla.mil/j-6/dlmso. The DLMS 

Supplement provides specific business rules, conditions, 

and authorized codes necessary for appropriate use of this 

IC within the DLMS.

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.

31. Used by the processing activity to reject select 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 (DI) 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

42. DLMS 824R was initially developed for use for

rejection of MILSTRAP related DLMS transactions

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

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

870L, 888I, 947I, providing specific reject advice codes. 

Transition Federal 

Notes to DLMS Notes 

that are still relevant 

to DLMS 824R

transition from a 

supplement to an 

implementation 

convention (IC).

Administrative update 

to reference 

MILSTRAP related 

DLMS transactions 

generically, rather 

than identify those 

transactions 

individually.

Enclosure 1, ADC 1103

page 1
# Location DLMS 824R Reject Advice Reason

However the DLMS 824R scope is expanded and it is 

authorized for use with other DLMS supply, and contract 

administration and logistics bills transactions not 

specifically identified, but does not replace supersede

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.

(continue renumbering existing DLMS Notes not shown

and update references within the IC back to the proper 

DLMS Notes.)

2. Introductory 

Notes

Add ADC 1103 to current DLMS Introductory Note 6

(As noted above, this ADC is renumbering this note to 

DLMS Introductory Note 8):

- 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

Identifies changes 

included in DLMS 

IC.

3. 1/ST02/010 Transition existing Federal Note to DLMS Note:

Federal Note: Use to identify a unique number assigned 

by the originator of the transaction set. This number may 

be system generated.

DLMS Note: Use to identify a unique number assigned by 

the originator of the transaction set. This number may be 

system generated.

Transition Federal 

Notes to DLMS Notes 

that are still relevant 

to DLMS 824R 

transition from a 

supplement to an 

implementation 

convention (IC).

4. 1/BGN07/020 Modify existing DLMS Note for code ZT:

ZT Report of rejection or Return of Work Candidate

DLMS Note: Use to identify a Reject Advice 

transaction. (MILSTRAP DIC DZG functionality; but 

also used for expanded DLMS reject capability beyond 

the scope of legacy MILSTRAP DZG.)

824R Reject Advice 

is not limited to 

legacy DZG 

capability. 

Elimination of the 

reference to DZG will 

eliminate confusion 

with limited DZG 

capability. The DZG 

relationship is 

addressed in the 

DLMS introductory 

notes.

Enclosure 1 to ADC 1103

Page 2
# Location DLMS 824R Reject Advice Reason

5. 1/BGN04/020 Open element, mark as used, and add DLMS Note:

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.

Administrative update 

to document existing 

usage.

6. 1/BGN05/020 Open element, mark as used, and add code “UT”:

UT Universal Time Coordinate

Administrative update 

to document usage. 

DAAS had been 

coded to GM, but 

when discussing 

documenting the use 

of BGN05 agreed to 

adjust to common 

DLMS approach of 

using UT.

7. 1/N1/030 Modify existing segment level DLMS Note:

DLMS Note:

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. For transactions other 

than the existing authorized DZG functionality, the 

only currently authorized RIC-From is SGA pending 

future functionality to support Component system 

origination.

DZG functionality is 

currently the only 

authorized use from 

Component systems. 

All other rejections 

are originating during 

processing at DLA 

Transaction Services. 

Future PDC may 

propose Component 

systems origin 

beyond DZG.

8. 1/N101/030 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

9. 2/OTI01/010 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transition from a 

supplement to an 

implementation 

convention (IC).

Enclosure 1 to ADC 1103

Page 3
# Location DLMS 824R Reject Advice Reason

10. 2/OTI02/010 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

11. 2/REF/020 Modify existing segment level DLMS Note 2.

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, Mmust 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.

At least one iteration 

is required to identify 

the transaction set of 

the transaction being 

rejected using a reject 

advice code for 

automation.

12. 2/REF01/020 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

13. 2/REF01/020 Modify existing DLMS Note 4 for the data element:

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.

Include a clarification 

for the use of code 

8X, as is provided for 

the other codes. Add 

explanations for 

coding the segment to 

ensure unique 

identification of 

rejections of 517M 

transactions.

14. 2/REF01/020 Add the following new code and DLMS Note:

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

Ensures unique 

identification of the 

particular transaction 

being rejected when a 

DLMS 517M 

containing a batch 

control number is 

rejected.

Enclosure 1 to ADC 1103

Page 4
# Location DLMS 824R Reject Advice Reason

15. 2/REF04-

01/020

Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

16. 2/REF04-03 to 

-06/020

Close four elements of composite C040:

REF04-03 Not Used

REF04-04 Not Used

REF04-05 Not Used

REF04-06 Not Used

No indication that 

these elements are 

used for any purpose.

17. 2/DTM01/030 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

18. 2/NM101/065 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

19. 2/NM102/065 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

Enclosure 1 to ADC 1103

Page 5
# Location DLMS 824R Reject Advice Reason

20. 2/TED01/070 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

21. 2/TED01/070 Revise DLMS note for code 848:

848 Incorrect Data

DLMS Note: Use to indicate that specific reject advice 

is conveyed under 2/LQ01/086. Qualifier ET or 81.

Administrative update 

for consistency with 

removal of code 81 at 

2/LQ01/086.

22. 2/LQ01/086 Remove Federal Note for the data element:

Federal Note: Use any code.

Removing 

unnecessary Federal 

Notes as DLMS 824R 

transitions from a 

supplement to an 

implementation 

convention (IC).

23. 2/LQ01/086 Remove code 81:

81 Status Code

DLMS Note: Use to identify the supply status code ‘CJ’. 

Use only when rejecting DLMS 846L Logistics Asset 

Support Estimate inquiry submitted for an 

obsolete/inactive NSN which cannot be supported.

Administrative edit to 

reflect elimination of 

DLMS 846L per 

ADC 400 (Reference 

3.d.).

24. 2/LQ01/086 Revise DLMS note 1, add new note 2, and renumber 

existing notes 2 and 3 for code 0:

0 Document Identification Code

DLMS Note: 

1. The DLSS DI Code is retained in the DLMS to facilitate 

transaction conversion in a mixed DLSS/DLMS 

environment. Continued support of the DI Code in a full 

DLMS environment will be assessed at a future date.

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

transaction.

Administrative update 

to change DI Code to 

DIC and add 

clarification of usage.

Enclosure 1 to ADC 1103

Page 6
# Location DLMS 824R Reject Advice Reason

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

34. Future Streamlined data; See introductory DLMS note 

4c.

25. 2/SE02/090 Transition existing Federal Note to DLMS Note:

Federal Note: Use to identify a unique number assigned 

by the originator of the transaction set. This number may 

be system generated.

DLMS Note: Use to identify a unique number assigned 

by the originator of the transaction set. This number may 

be system generated.

Transition Federal 

Notes to DLMS Notes 

that are still relevant 

to DLMS 824R 

transition from a 

supplement to an IC.

Enclosure 1 to ADC 1103

Page 7
ENCLOSURE 2

Coordination Comment Disposition

# Component/

Agency

Response/Comment Disposition

1 Air Force AF concurs with comments:

(1) Document finance as within the scope of 

the 824R and the existing narrative 

messages.

(2) Establish Reject Advice Codes BV, BW, 

BX, BY, and BV to accommodate current 

reasons for rejection of the DLMS 810L, 

Logistics Bill. The second 'BV' should be a 

'BZ'.

Noted.

Provided in DLMS 824R introductory 

notes.

Typo corrected above.

2 Army Concur. Noted.

3 Marine Corps Concur. Noted.

4 AFAFO Concur. Noted.

Enclosure 2, ADC 1043A

page 1
# Component/

Agency

Response/Comment Disposition

5 DLA Concur with comment.

DLA would like the DLMS 824R transaction 

authorized for a new advice code that would 

allow DSS to reject A_, B_ or C_ violation 

reason codes back to the ICP/Customer.

The most common violation reason codes 

are:

VRC Definition 

A4 / SHIPMENT TO ICP WILL NOT BE 

MADE

AD / NO VALID OWNER FOR 

TRANSFER-SHIP TO SELF

AE / ADVICE CODE INVALID

AF / CONDITION CODE INVALID OR 

BLANK

AM / UNIT PRICE INVALID

AN / UNIT OF ISSUE INVALID

AS / QUANTITY INVALID OR BLANK

AT / FUND CODE INVALID

AU / SIGNAL CODE INVALID OR 

BLANK

BA / MEDIA STATUS CODE INVALID

BJ / SUPPLEMENTARY ADDRESS 

INVALID

BZ / INVENTORY CONTROL DATA 

INVALID

C7 / SUPPL-ADD REQUIRED WITH SIGCD

Noted.

DLMSO supports the ability for end 

applications to utilize the 824R for sending 

functional rejects back to the original 

sender. In preparing to staff this change, 

DLMSO discussed the capability with 

DLA Transaction Services, which made 

clear that an implementation needs more 

thought. Since the immediate subject of 

the change did not rely on such a 

capability, it was agreed to defer 

application generated 824Rs beyond 

existing MILSTRAP for a future PDC. 

DLA’s requested additional reject 

capability will be forwarded for 

consideration as part of the future PDC.

Enclosure 2 to ADC 1103

Page 2
# Component/

Agency

Response/Comment Disposition

6 DLA Transaction 

Services

Concur with comment:

Pg 4, Attachment to PDC 1103, para 

C4.2.2.2 - Any X12 type errors that would be 

encountered by DLA Transaction Services 

trading partner should be handled as part of 

997 process. Functional data errors should 

be returned to the originator to be corrected. 

Having said that, it is still not clear how such 

a process could be implemented without a 

manual processing requirement at DLA 

Transaction Services which would not be 

practical. Any enhancement regarding this 

type of process would need to be extensively 

studied before moving forward.

Noted.

The subject 824R errors are for data 

content errors caught during edits at DLA 

Transaction Services, rather than syntax 

errors handled by 997. Per discussions in 

drafting this DLMS change it is understood 

that the current process of Volume 1, 

C4.2.2.2. is NOT implemented and would 

be significantly difficult to develop as 

written. Therefore, the language is being 

converted to , at best, allow for the 

capability to be considered for a future 

DLMS enhancement.

7 Pg 4, Attachment to PDC 1103, para C4.2.3 -

not aware of any implementation of this 

process, other than DZG

It is correct, to our knowledge, that the 

only implemented use of the 824R by 

supply applications is for DZG 

functionality. That doesn't negate that 

DLMS intends to allow expanded use for 

supply and finance situations as well where 

appropriate.

8 Pg 3 , Enclosure 1 to PDC 1103 - 7. 

1/N1/030 - 824R/DZG would contain two 

iterations of the N1 loop but neither would 

be SGA and DLA Transaction Services does 

not use any N1 segments when returning 

DAAS Narrative rejects to customers. SGA 

is not used at all here that I am aware

The N1 was included to ensure clarity as to

the originator of the transaction If DLA 

Transaction Services isn't currently using 

the N1/From in their 824R they are not 

following one of the basic tenants of the 

DLMS which is to identify the transaction 

originator in the transaction (not just 

enveloping). DLA Transaction Services

should consider this one of the updates to 

the process for their implementation.

However, the DLMS note has been 

modified to recognize that for MILSTRAP 

DIC DZG functionality, the originator will 

be rejecting application as opposed to DLA 

Transaction Services.

7 Pg 4, Enclosure 1 to PDC 1103 - 11. 

2/REF01 /020 DLA Transaction Services 

does not include any REF segment when 

returning DAAS Narrative rejects to 

customers.

The REF is important for automation at the 

recipient of an 824R. Modifying the 

second DLMS note of the 2/REF/20 

segment above to require at least one 

iteration of the REF to identify the rejected 

transaction when including a reject advice 

code. 

Enclosure 2 to ADC 1103

Page 3