DEFENSE LOGISTICS AGENCY HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

January 19, 2021

MEMORANDUM FOR SUPPLY DISCREPANCY REPORTING (SDR) PROCESS REVIEW 

COMMITTEE (PRC) 

SUBJECT: Approved Standards Change (ASC) 1396, Eliminate Information Copy for 

Document Type Code 7 SDRs WebSDR Owner/Manager/Source of Supply Field

(SDR)

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 1396

Page 1

ASC 1396

Eliminate Information Copy for Document Type Code 7, R, and N SDRs 

WebSDR Owner/Manager/Source of Supply Field

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Mr. Ben Breen, DoD Discrepancy/Deficiency Administrator, email: EBSO.SDR@dla.mil

b. Functional POC: DAAS WebSDR Team

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: Supply 

Discrepancy Reporting (SDR)

3. REFERENCES:

a. Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1066, 

SDR Process Enhancements, January 09, 2014

b. ADC 1066B, Update Supply Discrepancy Reports (SDR) Rule Changes to Owner, 

Manager, and Source of Supply Data for Document Type Code 7 SDRs, March 21, 2019

c. ADC 1066C, Update Supply Discrepancy Reports (SDR) Rule Changes to Owner, 

Manager, and Source of Supply Data for Document Type Code 7 SDRs, September 06, 2019

d. DLM 4000.25, Defense Logistics Management Standards, Volume 2, Chapter 17 

Supply Standards and Procedures

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change eliminates WebSDR from generating an 

information copy (transaction set purpose code 22) when the customer populates the 

owner/manager/source of supply field on a SDR document type code 7, R and N at time of 

submission (Reference 3.a., 3.b., and 3.c.)

b. Background:

(1) Currently when a customer submits a Document Type Code 7 SDR, the 

submitter can populate the owner/manager/source of supply field with the RIC or they can leave 

this field blank. If the customer populates this field on the SDR, WebSDR generates an 

information copy SDR to the RIC input by the customer. The information copy SDR is not

actionable by the RIC identified by the submitter, because when DLA Distribution receives the 

SDR and researches the material release order (MRO) history, DLA Distribution will update the 

owner/manager/source of supply field with the appropriate RIC that directed the shipment. 

(Reference 3.d.)
Attachment, ASC 1396

Page 2

(2) ADC 1066B addressed this issue by having WebSDR generate a Reply Code 

450 for Document Type 7, and R SDRs. Activities in receipt of an information copy SDR are 

not authorized to respond to the SDR. However, there are instances where the activity receiving 

the information copy SDR responds to the SDR and this creates issues processing the SDR.

(3) When a storage activity receives a shipment based upon a redistribution order

(RDO) and the materiel is short, over, wrong, quality deficient, or otherwise discrepant, the 

receiving activity will generate an SDR Document Type R or N. The storage activity can also 

populate the SDR to identify the activity to receive an information copy of the SDR. This 

scenario creates the unnecessary generation of information copy SDRs to activities which do not 

need to receive a copy of the SDR. 

c. Approved Change in Detail: WebSDR will not create an information copy SDR for 

Document Type Code 7, R and N SDRs regardless if the owner/manager/source of supply field is 

populated by the submitter on the original SDR. WebSDR will generate the information copy 

SDR when shipping activity determines the appropriate source of supply and needs to forward 

the SDR using the appropriate 300 series forwarding reply code to the source of supply that 

directed the shipment. This will eliminate unnecessary information copy SDRs being generated

to activities that should not receive the SDR. This will also allow the source of supply 

(identified by shipping activity on their reply) to receive an information copy of the original SDR 

as most SDR systems require this prior to being able to process the reply.

d. Revisions to Defense Logistics Manual: As shown in the enclosure.

e. Approved Transaction Flow: Standard SDR transaction flow applies.

f. Alternatives: None identified. 

5. REASON FOR CHANGE: Eliminates the unnecessary generation of information copy 

SDRs to activates which do not need to receive them. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: This change will ensure only the activity that directed the shipment will 

receive the SDR based on MRO history.

b. Disadvantages: None identified. 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: FY 2021. 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: At this time, a cost savings cannot be quantified 

with this change. 

9. IMPACT: 

a. New/changes to Data Elements: N/A
Attachment, ASC 1396

Page 3

b. Changes to DLMS Data Elements: N/A

c. Automated Information Systems (AIS): This change impacts WebSDR generation 

of information copy (22) SDRs. However, Product Deficiency Reporting and Evaluation 

Program (PDREP), 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 DO35K, Air Force 

Integrated Logistics System Supply (ILS-S) SDR systems should ensure the proper source of 

supply is identified at time of submission for Document Type 7 and N SDRs. 

d. Defense Automatic Addressing System (DAAS): WebSDR will make the identified 

changes noted above. 

e. Non-DLM Publications: None identified. 

10. PSC 1396 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. DAAS Concurs as written. As noted. 

2. DLA Concurs without comment. As noted.

3. ODASD(Logistics) Concurs as written. As noted.

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

5. US Army Concurs as written. As noted.

6. USMC None. None.

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

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, and deletions 

are shown with double strikethrough text.

Chapter 17, Supply Discrepancy Reporting. 

Preceding text not shown

C17.3.12.1.2.2.1. When the SDR is routed to the ICP as the 

action activity rather than the shipping depot under Army SDR routing rules, it may 

subsequently be transferred (Transaction Set Purpose Set Code 47) to the shipping 

activity as a secondary action activity. The shipping activity will use the status update to 

provide results of storage activity research and a recommended disposition. The status 

update is not copied to the SDR submitting activity by DoD WebSDR, as would be 

applicable when using a standard reply format (Transaction Set Purpose Set Code 11).

Intervening text not shown

C17.3.19.10.2. WebSDR will not create an information copy 

SDR for Document Type Code 7, R and N SDRs regardless if the owner/

manager/source of supply field is populated by the submitter on the original SDR. 

WebSDR will generate the information copy SDR when the shipping activity 

determines the appropriate source of supply and forwards the SDR using the 

appropriate 300 series forwarding reply code to the source of supply that directed 

the shipment. This will eliminate unnecessary information copy SDRs being 

generated to activities that should not receive the SDR. This will allow the source 

of supply (identified by the shipping activity on their reply) to receive an 

information copy of the original SDR as most SDR systems require this prior to 

processing the reply. If an SDR source of supply is updated to identify a different 

source of supply (based upon DLA Distribution updating the owner, manager, or source 

of supply field using a reply) after an information copy was provided, an SDR closure 

notification (Reply Code 450 - Administrative Closure Notification. SDR information copy 

sent to wrong source of supply) will be generated by WebSDR to the originally identified 

source of supply so that the open record can be administratively closed. WebSDR will 

suppress any future Party to Receive (Qualifier/Code PK) distribution copies 

(Transaction Set Purpose Code 22) to an activity that received the Reply Code 450 for 

only Document Type 7 and R SDRs. WebSDR will also provide an information copy 

(Transaction Set Purpose Code 22) of the original SDR to the newly identified source of 

supply (the information copy will contain the updated RIC value rather than perpetuating 

the original value).

Preceding text not shown

C17.3.19.10.5.1. WebSDR will ensure DLA Enterprise 

Business System (EBS) receives an information copy of all SDRs routed to a 

distribution center for initial action where EBS is the source of supply.