DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

January 19, 2021

MEMORANDUM FOR SUPPLY DISCREPANCY REPORT (SDR) PROCESS REVIEW 

COMMITTEE (PRC)

SUBJECT: Approved Standards Change (ASC) 1398, WebSDR Reject Transactions Subsequent 

to the SDR Cancellation

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

approved for implementation.

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

Others must contact their designated 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, ASC 1398

Page 1

ASC 1398

WebSDR Reject Transactions Subsequent to the SDR Cancellation

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Mr. Ben Breen, 

Enterprise Business Standards Office (EBSO) Discrepancy/Deficiency Administrator, e-mail: 

EBSO.SDR@dla.mil. 

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: SDR

3. REFERENCES: DLM 4000.25, Defense Logistics Management Standards, Volume 2,

Chapter 17 Supply Discrepancy Reporting and Appendix 7.28. Supply Discrepancy Report 

Relevant Data Elements

4. APPROVED CHANGE(S): Significant changes subsequent to staffing are highlighted in 

green.

a. Brief Overview of Change: This change updates WebSDR programming to 

automatically reject any subsequent transactions submitted when an SDR record is cancelled 

using Reply Code 907 (reference 3.a.). The only exception to this rule is when an SDR reply 

citing Reply Code 101 or 118 is processed after the cancellation to debit or credit the customer.

Users will submit a new SDR, as needed, to report existing or open supply discrepancies. 

b. Background: Currently, WebSDR only rejects SDR transactions once the SDR has 

been canceled in a few scenarios. As a result, subsequent transactions can process after the 

cancellation transaction has processed. This creates confusion for users and system issues 

allowing further transactions to process after the SDR has been canceled. 

c. Approved Change in Detail: WebSDR programming will automatically reject any 

transactions submitted when a SDR record is canceled. The only exception to this rule is when 

an SDR reply citing Reply Code 101 or 118 is processed after the cancellation to debit or credit 

the customer. A new SDR is to be submitted to address the initial, open, or unresolved supply 

discrepancy as needed by the originating activity. WebSDR will use the existing SDR Reply 

Code 907 (Transaction Rejected. Discrepancy report canceled). WebSDR will input in the 

narrative comments section of the rejection: “SDR has been canceled, please submit a new SDR 

to report unresolved discrepancies. Ensure the new SDR submission will not be rejected as a 

duplicate of the first submission.”

d. Revisions to Defense Logistics Manuals: Revisions to DLM 4000.25, Defense 

Logistics Management Standards, Volume 2, Supply, Chapter 17, as shown in the enclosure.

e. Approved Transaction Flow: Existing WebSDR flow.

5. REASON FOR CHANGE: This change will prevent ongoing SDR transactions from 

processing and disrupting reporting and metrics when an SDR cancellation transaction has 

processed. 
Attachment, ASC 1398

Page 2

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Users will be notified to submit a new SDR for open discrepancies 

when the initial SDR has already been cancelled.

b. Disadvantages: None identified.

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

DEVELOPMENT: WebSDR will edit incoming transactions and review records for a 

cancellation already on file.

8. ADDITIONAL COMMENTS TO CONSIDER: None

9. ADDITIONAL FUNCTIONAL REQUIREMENTS: None

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: WebSDR team projects 

implementation date of February 26, 2021

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: No specific cost savings can be calculated.

12. IMPACT: 

a. New/Changes to Data Elements: None identified. 

b. Automated Information Systems (AIS): Product Deficiency Reporting and 

Evaluation Program (PDREP), GSA Vision, DLA Distribution Standard System (DSS), Army 

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

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

and DLA Enterprise Business System (EBS) must be updated to prevent subsequent transactions 

from being transmitted once an SDR cancellation has been processed. Also, these systems must 

be able to accept an incoming Reply Code 101 or 118 after the SDR has been cancelled. 

c. Defense Automatic Addressing System (DAAS): WebSDR will reject any inbound 

SDR transaction after the initial SDR has been cancelled as stated above. 

d. Non-DLM Publications: N/A. 

13. PDC 1378 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. DAAS Concurs without comment As noted. 

2. DLA Concurs with comment

Comments:

1.This could cause issues if a cancellation 

is received for SDR Types 6, 7 and V if 

they are already in a completed status, and 

Comment resolution:

1. EBSO added an 

exception to the ADC 

to only allow for a 

reply (11) with Reply 
Attachment, ASC 1398

Page 3

there is financial impact (reply codes ‘101’ 

or ‘118’). Example: for SDR types 6, 7, 

and V, the SDR is put into process and a 

EBS workflow is created. When that SDR 

is re-completed, an outbound disposition 

transaction is created and sent containing 

last 3 SDRROD tasks. With the 

implementation of this PSC, the outbound 

transaction from EBS will be rejected by 

WebSDR.

2, If DLA received an item using 

document A, and submit a SDR it gets 

cancelled, and I choose to submit it again 

because I am still not satisfied, using the 

same document number, WEBSDR will 

assign another one of those control 

numbers’ right? 

Code 101 or 118 to 

process after a 

cancellation (01).

2. The duplicate logic 

in WebSDR checks to 

see if the previous SDR 

was cancelled, 

therefore the 

subsequent SDR should

not be rejected as a 

duplicate. 

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

4. US Air Force Concurs as written. As noted.

5. US Army Concurs as written. As noted.

6. USMC Concurs. As noted.

7. US Navy Concurs without comment As noted.
Enclosure, ASC 1398

Page 1

Enclosure

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

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

Chapter 17, Supply Discrepancy Reporting 

Preceding text not shown

C17.3.16. Cancellation of an Original Report. When an SDR originator discovers 

a previously reported SDR is not valid or appropriate for any reason and should be 

withdrawn, a new SDR cancellation must be prepared to cancel the original. Forward to 

all parties that received the original submission. Cite the original report number. SDR 

applications will include the WebSDR-assigned control number when known. Point of 

Contact (POC) information applicable to the cancelled SDR is required. A brief 

narrative description of the reason for cancellation must be included. WebSDR 

programming will automatically reject any subsequent transactions submitted 

when an SDR record is cancelled using Reply Code 907. The only exception to 

this rule is when an SDR reply citing Reply Code 101 or 118 is processed after the 

cancellation to debit or credit the customer.