OFFICE OF THE ASSISTANT SECRETARY OF DEFENSE

 3500 DEFENSE PENTAGON

 WASHINGTON, DC 20301-3500

 

 SUSTAINMENT

MEMORANDUM FOR SUPPLY DISCREPANCY REPORT PROCESS REVIEW 

COMMITTEE

SUBJECT: Approved Defense Logistics Management Standards Change 1444, Update 

WebSDR Processing Rules for Supply Condition Code and Document Number 

Values

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

approved for implementation.

Addressees may direct questions to Mr. 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 1444

Page 1

Approved Defense Logistics Management Standards Change 1444

Update WebSDR Processing Rules for Supply Condition Code and 

Document Number Values

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Technical POC: 

Ben Breen, Discrepancy/Deficiency Administrator, email: DEDSO.SDR@DLA.MIL.

2. REASON FOR CHANGE: Significant changes after staffing the proposed change are in 

green shade.

a. Bottom Line Up-Front: This change updates Defense Automatic Addressing System 

(DAAS) WebSDR business rules by the following:

(1) Requires that the Department of Defense (DoD) Supply Condition Code 

(SCC) be present in the Defense Logistics Management Standard (DLMS) 842A/W Supply 

Discrepancy Report (SDR) transaction at position 2/LQ01/3340 Qualifier 83 (SCC of discrepant 

materiel) when transmitting new original SDR submissions. SDRs reporting wrong item 

received discrepancies must provide the SCC in position 2/LQ01/3340 Qualifier BG. Type 5 

SDRs, must provide both the SCC “From” in position 2/1050/LQ01 Qualifier 83 and the SCC 

“To” in position 2/1050/LQ01 Qualifier BG. The SCC must be populated with values equal to:

A, B, C, D, E, F, G, H, J, K, L, M, N, P, Q, R, S, T, V, W, or X.

(2) The Document Number on new SDR submissions must not be changed on 

any subsequent transaction.

b. Background: 

(1) WebSDR currently does not prevent a DLMS 842A/W SDR transaction from 

processing and being routed to the action activity when an invalid or missing SCC value is in the 

transaction. Action activities in receipt of SDRs with no SCC or invalid SCC result in 

subsequent rejections and errors in SDR processing systems. 

(2) WebSDR does not currently edit SDRs for subsequent changes to the original 

document number which is causing errors. The original SDR is populated with the document 

number input by the submitter, any subsequent transaction by the submitter or action activity 

trying to change the document number causes systems errors and confusion by end users trying 

to work the SDR. The document number must be static throughout the life of the SDR and must 

not be changed. 

3. CHANGE IN DETAIL: 

a. Technical Details: 

(1) Update WebSDR to require a valid SCC value be populated in the DLMS 

842A/W SDR transaction as follows: 

(a) SCC must be present at position 2/LQ01/3340 Qualifier 83 (SCC of 
Attachment, ADC 1444

Page 2

discrepant materiel) when transmitting new original SDR submissions.

(b) SDRs reporting wrong item received discrepancies must provide the 

SCC in position 2/LQ01/3340 Qualifier BG. Type 5 SDRs, must provide both the SCC “From” 

in position 2/1050/LQ01 Qualifier 83 and the SCC “To” in position 2/1050/LQ01 Qualifier BG.

(c) The SCC must be populated with values equal to: A, B, C, D, E, F, G, 

H, J, K, L, M, N, P, Q, R, S, T, V, W, or X. 

(d) If the SCC is not valid or populated with one of these values, 

WebSDR will reject with Reply Code- 928 Transaction rejected. Missing or invalid condition 

code.

(e) WebSDR will insert remarks/narrative comments stating the 

following: “Original SDR doesn’t contain a valid Supply Condition Code, resubmit your SDR, 

do not submit a cancellation of this SDR as it will be rejected as well.”

(2) Update WebSDR to reject transactions changing the document number in 

SDR transactions.

(a) If any transaction attempts to process or update a SDR with a different 

document number other than what was on the original (00) SDR, then WebSDR will reject the 

transaction with Reply Code- 910 Transaction rejected. Missing or invalid document number (or 

document number/suffix). 

(b) WebSDR will insert remarks/narrative comments stating the 

following: “Your Transaction has a different Document Number than the one provided on the 

original 00 SDR submission. Document numbers must match. Please resubmit your transaction 

with the correct document number.”

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

4. IMPLEMENTATION TARGET: This change will be implemented across the DoD SDR 

systems listed in paragraph 5.b. no later than August 1, 2023.

5. TECHNICAL IMPACT: 

a. Additions or Changes to Data Elements: Not applicable.

b. Automated Information Systems (AIS): Component systems will make required 

updates to ensure the SCC is present on new SDR submissions. Also, SDR systems must be 

updated to not allow users to change the document number on the SDR once it has been 

submitted. At a minimum the following SDR systems must make updates: Product Deficiency 

Reporting and Evaluation Program (PDREP), General Service Administration (GSA) Vision, 

DLA Distribution Standard System (DSS) and Warehouse Management System (WMS), Army 

Logistics Modernization Program (LMP), Air Force Security Assistance and Cooperation 

(AFSAC), Air Force Wholesale D035K, Air Force Integrated Logistics System Supply (ILS-S) 

and DLA Enterprise Business System (EBS). 
Attachment, ADC 1444

Page 3

c. Defense Automatic Addressing System (DAAS): See paragraph 3.

6. PUBLICATION/POLICY IMPACT: 

a. Defense Logistics Manual (DLM) 4000.25: Update Volume 2, Chapter 17 as shown 

in the enclosure.

b. Non-DLM 4000.25 Publications: Components to update internal guidance with 

these changes.

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

8. END-TO-END TESTING REQUIREMENTS: DAAS will ensure transactions are rejected 

for missing or invalid SCC and transactions trying to change the document number prior to 

releasing this change to production.

9. REFERENCE: DLM 4000.25, Volume 2, Chapter 17, Supply Discrepancy Reporting.

10. PROPOSED DLMS CHANGE (PDC) 1444 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. Army 

USASAC (FMS)

Concur.

Concur.

As noted.

2. Navy Concur with comments.

Comments:

1. Condition Code H and T need added to the list of 

acceptable condition codes. The US Navy Ordnance 

community requires these two condition codes.

2. The PDC needs to clarify the “TO” (code BG) will 

be mandatory.

DEDSO Response:

1.Condition Codes H and T added 

to the list of acceptable codes as

required by US Navy Ordinance. 

WebSDR already has SCC H 

included in the SCC drop down list.

2. Per discussions with the Navy, 

the correct qualifier for the SCC is 

TO is 83. ADC has been updated to 

clarify the correct qualifiers. 

3. Marine Corps Concur. As noted.

4. Air Force Concur. As noted.

5. DLA Concur. As noted.
Attachment, ADC 1444

Page 4

6. DAAS Concur with comment.

Comment:

1. This PDC states the non-Type-5 SDR’s should 

have the SCC in 2/1050/LQ01=83 position. I thought 

only the Type-5s should be mapped at that position 

and that the Discrepant SCC for all other Doc types 

should be in position 2/3340/LQ01=83.

As noted and ADC has been 

updated. 

7. USTRANSCOM Abstains. Abstains.
Enclosure, ADC 1444

Page 1

Enclosure

Update DLM 4000.25, Volume 2, Chapter 17 as shown below: 

Changes are identified in red bold italics. All existing Tables and referential text related to the 

existing tables will be updated when the change to Chapter 17 is made but are not specifically 

marked in this change.

Preceding text not shown.

C17.3.18. Defense Automatic Addressing System (DAAS) SDR Processing

C17.3.18.1. Under DLMS, SDRs are integrated with standard logistics 

transaction processing through DAAS. DLMS transaction formats are available in ASC 

X12 EDI or EDI-based XML. Guidance for transaction content is provided in DLMS ICs 

available on the DLMS IC page. DoD WebSDR will perform the following actions:

Intervening text not shown

C17.3.18.1.2.15. WebSDR will reject with Reply Code 928

any transaction with invalid or missing SCC on an SDR. SDR must be populated 

with values equal to: A, B, C, D, E, F, G, H, J, K, L, M, N, P, Q, R, S, T, V, W, or X. 

WebSDR will insert remarks/narrative comments stating the following: “Original 

SDR doesn’t contain a valid Supply Condition Code, resubmit your SDR, do not 

submit a cancellation of this SDR as it will be rejected as well.”

C17.3.18.1.2.16. WebSDR will reject with Reply Code 910

any transaction attempting to change the original document number on a SDR

after the original submission. WebSDR will insert remarks/narrative comments 

stating the following: “Your Transaction has a different Document Number than 

the one provided on the original 00 SDR submission. Document numbers must 

match. Please resubmit your transaction with the correct document number.”