DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

April 9, 2021

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC)

SUBJECT: Approved Standards Change (ADC) 1378A, Enhanced DLMS 940R Validations for 

Defense Logistics Agency (DLA) Warehouse Management System

The attached change to DoD Enterprise Business Standards, as outlined in the 

attachment, is approved for implementation. This update replaces ADC 1378 in its entirety

Addressees may direct questions to Ms. Tonja Carter, e-mail: EBSO.Supply@dla.mil. 

Others must contact their designated Supply PRC representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/

THOMAS A. DELANEY 

Director, Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD(Logistics)

OUSD(C) 

OUSD(A&S/DPC)
Attachment, ADC 1378A

Page 1

ADC 1378A

Enhanced DLMS 940R Validations 

for DLA Warehouse Management System

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Erin Fowles, DLA Information Operations J6 Project Management, 

Erin.Fowles@dla.mil

b. Functional POC: Wendy Evans, DLA Distribution HQ J4 Transportation, 

Wendy.Evans@dla.mil

2. REFERENCES:

a. Defense Logistics Manual (DLM) 4000.25, Volume 2, Chapter 4, Requisitioning

b. DLM 4000.25, Volume 2, Appendix 2.8, Reject Advice Codes

3. APPROVED CHANGE(S): Substantive updates subsequent to PDC 1378 staffing are 

highlighted in green. Updates for ADC 1378A are highlighted in blue.

a. Brief Overview of Change: This change approves that the Defense Automatic 

Addressing System (DAAS) perform additional validations on DLMS 940R Materiel Release 

Orders and Redistribution Orders addressed to DLA’s new warehouse management system.

b. Background:

(1) DLA is developing an application called the Warehouse Management System 

(WMS), which will replace the DLA Distribution Standard System (DSS). As part of the 

implementation, DLA is planning to leverage DAAS transaction validations to prevent erroneous 

transaction data from entering WMS and notify the sender when rejection occurs. Through the 

process of developing the transition of these validations from DSS to DAAS, DSS Audit agreed 

to integrate these validations to apply to the legacy DSS system, as well.

(2) DAAS performs extensive validations on transactions received from 

requisitioning activities, but applies minimal validations to the DLMS 940R, materiel release 

orders and redistribution orders. While materiel release and redistribution orders perpetuate data 

from requisitions, these transactions occasionally contain erroneous information. Consequently, 

DLA Distribution personnel must manually review erroneous information sent to DSS and use 

offline methods such as e-mails or phone calls to notify the sender to correct and resubmit failed 

transactions. If attempts to communicate with the sender fail, the transactions stall in the system 

and fail to process.

(3) To help DLA automate error handling, this change approves enhanced 

validations on DLMS 940R Materiel Release Orders and Redistribution Orders addressed to 

WMS or DSS as shown in paragraph 3.c. If a transaction fails validation, DAAS will reject the 
Attachment, ADC 1378A

Page 2

transaction and send a DLMS 824R Reject Advice transaction with a reject advice code to the 

sender. The sender must then correct and resubmit the transaction. By leveraging DAAS, WMS 

and DSS will minimize the time and effort that DLA Distribution personnel spend processing 

erroneous transactions.

(4) After PDC 1378 staffing, DLA noted that Enterprise Business System (EBS)-

generated DLMS 940Rs should be excluded from the proposed DAAS edit. EBS has no inbound 

interface to process an 824R rejection transaction. DLA found that developing a new DLMS 

824R interface is unnecessary in light of DLA's project to migrate EBS to the cloud to facilitate a 

single enterprise resource planning (ERP) instance that integrates with WMS without the need 

for electronic data interchange (EDI) transactions.

c. Approved Change in Detail:

(1) DAAS will validate non-DLA originated DLMS 940R Materiel Release 

Orders and Redistribution Orders addressed to DLA’s WMS or DSS systems. If a transaction 

fails validation, DAAS will send a DLMS 824R Reject Advice transaction to the originator 

citing the applicable reject advice codes contained in DLM 4000.25, Appendix 2.8, Reject 

Advice Codes (Reference. 2.b.).

(2) This change also establishes two new reject advice codes for invalid advice 

and suffix codes, as shown Enclosure 1.

(3) The table below contains the validation criteria that will be used on the 

DLMS 940R and reject advice codes that will be sent from DAAS to the component on the 

DLMS 824R. The validations in this ADC are only applicable to 940R transactions addressed to 

the DLA Warehouse Management System or Distribution Standard System. The respondents to 

the proposed change were asked to use the following criteria to determine the appropriate 

response for their respective Service/Agency (S/A) :

1. Concur if your S/A concurs with the change as written. 

2. Concur with comment if your S/A concurs with the change and would 

like DAAS to perform the enhanced validations for DLMS 940R transactions created or received 

within your respective S/A.
Attachment, ADC 1378A

Page 3

DAAS Validations on the 940R

Location Data Element Criteria Reject Advice 

Code and 

Definition

2/W01/0200 Quantity 

Ordered

Reject if blank or invalid DD – Rejected. 

Quantity 

Missing/Invalid

2/N901/0400

Qualifier TN

Transaction 

Reference 

Number 

Reject if the authority code does not authorize 

the DoDAAC to perform the action indicated. 

This is the requisitioner, identified as the 

first six positioners of the document 

number

Reject if Invalid

BV – Rejected. 

DoDAAC in the 

transaction does not 

have the 

appropriate 

authority code for 

its intended use

BZ – Rejected. 

DoDAAC or 

MAPAC is not 

valid in DAAS

2/N907-

01/0400

Qualifier W8

Suffix Code Reject if 0,1, I, N, O, P, R, S, or Z DM – Rejected. 

Suffix Code invalid

2/LQ01/1300

Qualifier A9

Supplemental

Data 

Reject if the authority code does not authorize 

the DoDAAC to perform the action indicated

by the signal code

BV – Rejected. 

DoDAAC in the 

transaction does not 

have the 

appropriate 

authority code for 

its intended use

Reject if signal code passed = J, K, L, M, X

(Volume 2, Appendix 7.10)

AND

if the supplementary address is missing or 

invalid

AND

the requisitiontioner service/agency code is 

not B, D, K, P, or T (Security 

Assistance/MAPAC) (Volume 2, Appendix 

7.2).

BZ – Rejected. 

DoDAAC or 

MAPAC is not 

valid in DAAS

Reject if signal code passed = A, B, C, D, J, 

K, L, M, W, or X (Volume 2, Appendix 7.10)

AND if the supplementary address is missing 

AND

requisitioner service/agency code = B, D, K, 

P, or T (Security Assistance Use 

Only/MAPAC) Appendix 7.2 and 8.3

BZ – Rejected. 

DoDAAC or 

MAPAC is not 

valid in DAAS
Attachment, ADC 1378A

Page 4

d. Revisions to DLM 4000.25 Manuals: Update DLMS Volume 2, Appendix 

AP2.8, as identified in Enclosure 1. 

e. Approved Transaction Flow: This change does not modify the existing DLMS 

940R transaction flows. DAAS will continue to use the DLMS 824R Reject Advice transaction 

to notify the sender if a transaction fails one or more semantic validations.

f. Alternatives: None identified.

4. REASON FOR CHANGE: Automated error handling and removing manual intervention is 

a top priority for DLA.

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

(1) This change will prevent materiel release orders and redistribution orders

with invalid data from entering the DLA WMS or DSS systems. DLA Distribution personnel 

will no longer need to manually review failed transactions and notify the sender. Instead, DAAS 

will automatically notify the sender of the erroneous transaction and provide a reject advice 

code.

(2) This change will also expand the use of reject advice codes as an alternative 

to DAAS narrative rejects. DAAS narrative rejects provide an abbreviated narrative explanation 

for the rejection. These narratives are difficult to understand and the DLMS trading partners 

have no visibility of the associated exception code. In contrast, reject advice codes are available 

in the DLM 4000.25, Volume 2, Appendix 2.8 (Reference 2.b.), and they provide a clear reason 

for rejection. 

b. Disadvantages: None identified.

6. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT: This change assumes that DAAS will continue to catch syntax errors and 

provide a DLMS 997 Functional Acknowledgement to the sender.

2/LQ01/1300

Qualifier DE

Signal Code Reject if signal code is other than A, B, C, D, 

J, K, L, M, W, X, or blank for legacy 80 

record position MILS transactions only

AH – Required 

Signal Code invalid 

or blank 

2/LQ01/1300 Advice Code Reject if invalid DN – Rejected. 

Advice Code 

invalid

2/LQ01/1300

Qualifier 83

Supply 

Condition 

Code 

Reject if blank or invalid AM – Rejected. 

Supply condition 

code invalid or 

blank
Attachment, ADC 1378A

Page 5

7. ADDITIONAL COMMENTS TO CONSIDER: DLA supports the DLMS compliant and 

standard use of the 824R for its ability to notify DLA systems of errors and invalid data in its 

outbound transactions. DLA leverages both an inbound and outbound transaction in its business 

processes and technical solution to avoid impacting external customers and ensure data integrity 

through the Supply Chain and Materiel Lifecycle. 

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: 01/31/2021

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available.

10. IMPACT: 

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: Update the DLMS data dictionary and 

LOGDRMS to include the following reject advice codes values in the DLMS 824R, LQ02, Data 

Element 1271 identified in Enclosure 1:

c. Automated Information Systems (AIS): This change impacts the following 

information systems:

(1) DLA: Warehouse Management System

(2) DLA: Distribution Standard System

(3) Non-DLA: DLMS-capable systems that send transactions to DLA distribution 

centers.

d. Defense Automatic Addressing System (DAAS): Implement the validations 

contained in paragraph 3.c. and use the provided reject advice codes.

(1) The validations are applicable transactions that meet the following criteria:

(a) DLMS 940R (DIC A5_ (including A5J)) and (DIC A2_)

(b) Destination Communication Routing Identifier (COMMRI) identifies 

WMS

(c) Destination COMMRI identifies DSS

(d) Originating COMMRI does not identify EBS

(2) Use the translation table to determine if the sender is DLMS-capable. If the 

sender is DLMS-capable, provide the applicable reject advice code. If the sender is not DLMScapable, DAAS will reject using DIC DZG per Volume 2, Appendix 2.8. 

e. Non-DLM 4000.25 Series Publications: Participating services/agencies should 

update their respective publications to address the additional validations and reject advice codes.
Attachment, ADC 1378A

Page 6

11. PDC 1378 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. DAAS Concurs without comment As noted. 

2. DLA Concurs with comment See Enclosure 2

3. ODASD(Logistics) Concurs without comment As noted.

4. US Air Force Concurs without comment As noted.

5. US Army None As noted.

6. USMC Concurs without comment As noted.

7. US Navy Concurs without comment As noted.
Enclosure 1, ADC 1378A

Page 1

Enclosure 1

Defense Logistics Manual (DLM) 4000.25, Volume 2, Supply Standards and Procedures

Make the following change to Volume 2. Additions are shown in red bold italics text. 

Appendix 2.8. Reject Advice Codes

Add the two new codes to Appendix 2.8

CODE EXPLANATION 

BZ Rejected. DoDAAC or MAPAC is not valide in DAAS

DM Rejected. Suffix Code Invalid

DN Rejected. Advice Code Invalid
Enclosure 2, ADC 1378A

Page 1

Enclosure 2

DLA Reviewer Input 

Para

Critical or 

Substantive Comment Recommended Changes Commentor EBSO Response

4.C.3 Substantive

The table containing the proposed 

change states that the Signal Code 

must not be blank or must contain 

a list of specific fields. This is 

contrary to the current DLMS 940R 

IC which states that this field will 

only remain until full DLMS 

compliancy is reached or the 

components may coordinate an 

early termination of this field with 

EBSO (DLMS IC Para 4c. It is 

unknown by this office if any of the 

components have terminated it use 

already. We believe DSS / WMS is 

/ should be DLMS compliant and 

should not be relying on this field.

The request for

change should 

be sent back for 

rework, or the 

DLMS IC should 

be modified to 

remove the 4c 

comment from 

the Industry 

Code - Signal 

Code, if it is to 

remain

mandatory.

R. Reed -

DPAS

EBSO had updated 

the Signal Code in 

this ADC to reflect 

this is mandatory 

under MILS, 

however, optional 

under DLMS.

Substantive

Was consideration given to the 

number of DLA EBS companion 

RFCs which will be required in

order to implement the change?

John 

Austin, 

DLA Land 

and 

MaritimeBAOA

This change no 

longer affects EBS.

Substantive

DLA EBS logic currently uses 

DoDAAC Y00001 for processing all 

returns of litigated material to 

vendors. If the change is 

implemented, DLA EBS will receive 

a rejection and not be able to 

process return shipments.

DAAS logic 

should ignore 

transactions sent 

from DLA EBS to 

DLA WMS

John 

Austin, 

DLA Land 

and 

MaritimeBAOA

This change no 

longer affects EBS.

Substantive

DLA EBS logic currently leaves the 

Supplementary Address blank on 

disposal release orders. If the 

change is implemented, DLA EBS 

will receive a rejection and not be 

able to process disposal orders.

DAAS logic 

should ignore 

transactions sent 

from DLA EBS to 

DLA WMS

John 

Austin, 

DLA Land 

and 

MaritimeBAOA

This change no 

longer affects EBS.