OFFICE OF THE ASSISTANT SECRETARY OF DEFENSE

 3500 DEFENSE PENTAGON

 WASHINGTON, DC 20301-3500 

SUSTAINMENT 

MEMORANDUM FOR SUPPLY DISCREPENCY REPORTING PROCESS REVIEW 

COMMITTEE 

SUBJECT: Approved Defense Logistics Management Standards 1436, Receipt of Document 

Type 7 Supply Discrepancy Reporting Information Copy and Distribution Center 

Reply Business Rules and Remove Discrepancy Code Z6 from Defense Logistics 

Manual Volume 2 Appendix 7.28 

 The Defense Logistics Management Standards change, as outlined in the attachment, is 

approved for implementation. 

 Addressees may direct questions to Ben Breen, e-mail: DEDSO.SDR@dla.mil. Others 

must contact their designated Process Review Committee representative available at 

https://www.dla.mil/Defense-Data-Standards/Committees/Contacts/. 

 Leigh E. Method, SES 

 Deputy Assistant Secretary of Defense 

 for Logistics 

Attachments: 

As stated 

cc: 

OUSD(C) 

DLA J6DS 
 

Attachment, ADC 1436 

Page 1 

Approved Defense Logistics Management Standards Change 1436 

Receipt of Document Type 7 Supply Discrepancy Reporting Information 

Copy and Distribution Center Reply Business Rules and Remove 

Discrepancy Code Z6 from Defense Logistics Manual Volume 2 Appendix 

7.28 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Functional/Technical POC: Ben Breen, Defense Enterprise Data Standards Office 

(DEDSO), DoD Deficiency Report Administrator, email: Benjamin.Breen@dla.mil. 

2. REASON FOR CHANGE: 

a. Bottom Line Up-Front: This change will enhance the Defense Automatic 

Addressing System (DAAS) WebSDR application to reject the Supply Discrepancy Reporting 

(SDR) Document Type 7 reply transaction when a 300 series Discrepancy Code is used and 

addressed to an incorrect Routing Identifier Code (RIC) TO activity. For example, when Reply 

Code 307 is used to forward the record to DLA, the RIC TO must be SMS, or when Reply Code 

305 is used to forward the record to the Navy Product Data Reporting and Evaluation Program 

(PDREP) system the record must be addressed with a valid Navy RIC as the RIC TO field. 

(1) This change creates a new rule in WebSDR to reject SDRs when the replying 

activity inputs a 300 series Reply Code in conjunction with a Reply Code 504.

(2) This change also removes Discrepancy Code Z6 (Report reopened following 

inappropriate cancellation/completion (must use in combination with other discrepancy codes; 

must appear as first discrepancy code in transactions)) from DLM 4000.25, Volume 2, Appendix 

7.28, Supply Discrepancy Report Relevant Data Elements in support of ADC 1374. ADC 1374 

removed procedures allowing a SDR Correction (CO) to reopen an SDR with Discrepancy Code 

Z6.

(3) DAAS WebSDR will suppress informational copies of Completion Notices 

(CN) to the activity identified in the Owner/Manager/Source of Supply (OMS) field on the 

original (00) SDR for all SDR Document Type Codes. 

b. Background: 

(1) SDR records were identified where users were directing Reply Code 300-

series forwarding responses to activities outside of the 300-series code specific Service 

requirement. Each 300-series code is designed to forward the SDR to a specific Service as 

shown in the below listing: 

The 300-series codes indicate storage activity or initial action activity status on SDRs forwarded 

to the owner/manager for action: 

301 Interim reply; SDR forwarded to USA for disposition instructions or final resolution. 
 

Attachment, ADC 1436 

Page 2 

302 Interim reply; SDR forwarded to USAF for disposition instructions or final resolution. 

303 Interim reply; SDR forwarded to USMC for disposition instructions or final resolution. 

304 Interim reply; SDR forwarded to USCG for disposition instructions or final resolution. 

305 Interim reply; SDR forwarded to USN for disposition instructions or final resolution. 

306 Interim reply; SDR forwarded to GSA for disposition instructions or final resolution. 

307 Interim reply; SDR forwarded to DLA for disposition instructions or final resolution. 

(2) DEDSO was also notified of SDR transactions failing in Component systems 

because the reply activity responded with a 300-series reply code but also used a reply code 504 

at the same time. The use of Reply Code 504 with the 300-series resulted in failed transactions 

because Reply Code 504 creates a new SDR record and sends it to the activity identified as the 

RIC TO. Essentially this was creating two SDR records in the component system and one was 

being rejected as a duplicate. 

(3) ADC 1374 removed the logic that would allow a SDR correction to reopen an 

SDR using Discrepancy Code Z6 once the submitter has generated a Completion Notification 

(CN) on the SDR, but it did not remove Discrepancy Code Z6 from the Appendix 7.28 and DoD 

SDR system code lists. 

(4) DAAS WebSDR currently perpetuates copies of all transactions on an SDR 

when an activity is identified in the OMS field. Subsequently, when the submitter transmits the 

CN for the SDR, WebSDR will perpetuate a copy of this CN to the activity identified in the 

OMS field. Currently, this is causing DLA’s Enterprise Business System (EBS) to fail these 

transaction as they are not required or needed for EBS. This change will allow WebSDR to 

suppress these transactions from being sent for all SDR Document Type Codes. 

3. CHANGE IN DETAIL: 

a. Technical Details: 

(1) WebSDR will reject 300-Series Reply Codes incorrectly addressed (RIC TO) 

or formatted SDRs with Reply Code 944 (Transaction rejected. Forwarding transaction not 

properly formatted). 

(2) WebSDR will insert remarks/narrative comments stating the following: “The 

300 series reply code used does not match with the correct corresponding RIC TO. Please 

resubmit your reply (11) with the correct values.” 

(3) WebSDR will reject SDRs using 300-Series Reply Codes in conjunction with 

Reply Code 504 with Reply Code 944 (Transaction rejected. Forwarding transaction not properly 

formatted). 

(4) WebSDR will insert remarks/narrative comments stating the following: “A 

300-Series Reply Code and 504 Reply Code cannot be used in conjunction, please resubmit your 

reply (11) properly formatted.” 

(5) Remove discrepancy code Z6 from DLM 4000.25 Volume 2 Appendix 7.28 

as shown in enclosure 2. 
 

Attachment, ADC 1436 

Page 3 

(6) DAAS WebSDR will suppress informational copies of Completion Notices 

(CN) to the activity identified in the Owner/Manager/Source of Supply (OMS) field on the 

original (00) SDR for all SDR Document Type Codes. 

b. Revised Transaction Flow: No changes to standard SDR transaction flow. 

4. IMPLEMENTATION TARGET: DAAS WebSDR will provide implementation timeline 

in response to this PDC. 

5. TECHNICAL IMPACT: 

a. Additions or Changes to Data Elements: None identified. 

b. Automated Information Systems (AIS): 

(1) SDR systems must remove Discrepancy Code Z6 from their SDR system 

applications discrepancy code list. 

(2) SDR systems must ensure 300 Series Reply Codes are properly formatted to 

the correct action activity. 

(3) SDR Systems must ensure a 300 Series Reply Code is not used in conjunction 

with a 504 Reply Code. 

c. Defense Automatic Addressing System (DAAS): 

(1) WebSDR will reject 300-Series Reply Codes incorrectly addressed (RIC TO) 

or formatted SDRs with Reply Code 944 (Transaction rejected. Forwarding transaction not 

properly formatted). 

(2) WebSDR will insert remarks/narrative comments stating the following: “The 

300 series reply code used does not match with the correct corresponding RIC TO. Please 

resubmit your reply (11) with the correct values.” 

(3) WebSDR will reject SDRs using 300-Series Reply Codes in conjunction with 

Reply Code 504 with Reply Code 944 (Transaction rejected. Forwarding transaction not properly 

formatted). 

(4) WebSDR will insert remarks/narrative comments stating the following: “A 

300-Series Reply Code and 504 Reply Code cannot be used in conjunction, please resubmit your 

reply (11) properly formatted.” 

(5) Remove discrepancy code Z6 from DLM 4000.25 Volume 2 Appendix 7.28 

as shown in enclosure 2. 

(6) DAAS WebSDR will suppress informational copies of Completion Notices 

(CN) to the activity identified in the Owner/Manager/Source of Supply (OMS) field on the 

original (00) SDR for all SDR Document Type Codes. 
 

Attachment, ADC 1436 

Page 4 

6. PUBLICATION/POLICY IMPACT: 

a. Defense Logistics Manual (DLM) 4000.25: Update DLM 4000.25, Volume 2, 

Chapter 17 and Appendix 7.28 as shown in enclosures 1 and 2. 

b. Non-DLM 4000.25 Publications: Components will update their publications as 

needed. 

7. ASSUMPTIONS: None identified.

8. FINANCIAL IMPROVEMENT AND AUDIT REMEDIATION (FIAR), MATERIAL 

WEAKNESS, AND AUDIT-RELATED INFORMATION: 

a. Notices of Findings and Recommendations (NFR): None identified.

b. Corrective Action Plan (CAP) References: None identified.

c. Other FIAR, Material Weakness, and Audit-Related Information: None 

identified.

9. END-TO-END TESTING REQUIREMENTS: 

a. DEDSO will coordinate with DLA Warehouse Management System (WMS) and 

Distribution Standard System (DSS) to ensure the new 300 series reply code rejection is properly 

implemented.

b. DEDSO will coordinate with DAAS WebSDR to validate the CN transactions are 

suppressed for activities identified in the OMS field.

10. REFERENCES: 

a. DLM 4000.25, Volume 2, Chapter 17, Supply Discrepancy Reporting

b. DLM 4000.25, Volume 2, Appendix 7.28, Supply Discrepancy Report Relevant Data 

Elements 

c. ADC 1374 Allowable Updates to SDR Corrections, June 11, 2020

11. Proposed DLMS CHANGE (PDC) 1436 RESPONSE/COMMENT RESOLUTION: 

 Component Response/Comment Disposition 

1. Army Concur As noted. 

2. Navy Concur As noted. 

3. Marine Corps No response. No response.

4. Air Force Concur As noted. 

5. DLA Concur As noted. 
 

Attachment, ADC 1436 

Page 5 

6. DAAS Concur As noted. 

7. USTRANSCOM Abstain As noted. 
 

Enclosure 1, ADC 1436 

Page 1 

Enclosure 1 

Update DLM 4000.25 Volume 2 Chapter 17 Supply Discrepancy Reporting as follows: 

Make the following changes to Volume 2. Additions are shown in red bold italics. Deletions 

are shown by double strikethrough text.

Preceding text not shown 

 

C17.3.18.1.2.15. WebSDR will reject incorrectly 

addressed (RIC TO) or formatted SDRs with Reply Code 944 (Transaction 

rejected. Forwarding transaction not properly formatted) with remarks/narrative 

comments stating: The 300 series reply code used does not match with the 

correct corresponding RIC TO. Please resubmit your reply (11) with the correct 

values. 

 C17.3.18.1.2.16. WebSDR will reject SDRs using 300-

Series Reply Codes in conjunction with Reply Code 504 with Reply Code 

944.WebSDR will insert remarks/narrative comments stating: A 300-Series Reply 

Code and 504 Reply Code cannot be used in conjunction, please resubmit your 

reply (11) properly formatted. 

 C17.3.18.1.2.17. WebSDR will suppress informational 

copies of Completion Notices (CN) to the activity identified in the 

Owner/Manager/Source of Supply (OMS) field on the original (00) SDR for all SDR 

Document Type Codes. 

 
 

Enclosure 2, ADC 1436 

Page 1 

Enclosure 2 

Update DLM 4000.25 Volume 2 Appendix 7.28 Supply Discrepancy Report Relevant Data 

Elements as follows: 

Deletions are shown with a double strikethrough. 

AP7.28 APPENDIX 7.28 

SUPPLY DISCREPANCY REPORT RELEVANT DATA ELEMENTS 

Other Discrepancies 

Z1 Other discrepancy - see remarks 

Z2 Repetitive discrepancy (must use in combination with other codes or 

describe in remarks) 

Z3 Distribution Center receipt not due-in; no prepositioned materiel receipt 

(PMR) 

Z4 No record exists for document number cited on supply document (not used 

by distribution center; not applicable to Security Assistance) 

Z5 Immediate resolution/replacement of discrepant item under inter-Service 

support agreement (restricted use per Service guidance)1

Z6 Report reopened following inappropriate cancellation/completion (must use 

in combination with other discrepancy codes; must appear as first 

discrepancy code in transactions ) 

Z7 Property not authorized or not acceptable for turn-in to DLA Disposition 

Services 

Z8 Materiel unidentifiable; stock number missing or damaged. 

 

1

 Refer to ADC 1062 Non-Inventory Control Point/Integrated Materiel Manager (ICP/IMM)-Directed Inter-Service 

Lateral Support via Retail Level Passing Order and ADC 1174 WebSDR Process Enhancements and 

Administrative Updates including SDR Reply Screen and Management Report Functionality, New/Revised 

Reply Codes, and Standardized Identification of the Submitting Customer. Not authorized for use by DLA 

Distribution Centers.