DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 2206<>-6221 

June 30, 2015 

MEMORANDUM FOR SUPPLY DISCREPANCY REPORT (SOR) PROCESS REVIEW 

COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Addendum to Approved Defense Logistics Management Standards 

(DLMS) Change (ADC) 1066A, SDR Process Enhancements for Source of Supply 

(SoS) Notification of SDR Updates 

The attached change to DLM 4000.25, Defense Logistics Management Standards, is approved for 

implementation by October 1

51

, 2015. 

Addressees may direct questions to Ms. Ellen Hilert, DOD SDR System Administrator, e-mail: 

ellen.hilert@dla.mil, or Mr. Ben Breen, SDR Alternate, e-mail benjarnin.breen@dla.mil. Others 

must contact their Component designated SDR PRC representative available at: 

https://www2.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: ODASD (SCI) 

Director 

Defense Logistics Management 

Standards Office 
Attachment, ADC 1066A

Page 1

Attachment to ADC 1066A

SDR Process Enhancements for Source of Supply (SoS) 

Notification of SDR Updates

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Functional POC: DLA HQ and DLA Land and Maritime

b. Technical POC: DOD SDR System Administrator, Defense Logistics Management 

Standards Office, e-mail: ellen.hilert@dla.mil and benjamin.breen@dla.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply Discrepancy Reporting

b. Primary/Secondary Functional Process: DOD WebSDR Processing

3. REFERENCES:

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

b. Approved DLMS Change (ADC) 1066, SDR Process Enhancements: Follow-up 

Time Standards, SDR Forwarding, Source of Supply (SoS) Notification, Discrepancy Code D4 

for Missing Quality Assurance Representative (QAR) Signature, use of Unique Item Tracking 

(UIT) Designator Code for Management Report Selection Criteria, January 9, 2014

c. ADC 1126, Revised Routing Rules for Non-Manager-Owned Suspended Stock 

Identified at Time of Receipt at DLA Distribution Centers and Improved Identification of Owner 

and Manager on SDR Transactions, December 16, 2014

4. APPROVED CHANGE(S):

a. Brief Overview of Change:

(1) This approved addendum updates DOD WebSDR processing to enable SoS 

systems to properly process transactions used for SoS notification of relevant SDR information. 

This update includes the below two new rules for WebSDR processing.

(2) WebSDR will be required to suppress the distribution copy of the SDR reply

(Transaction Purpose Set Code 11) when an SDR is forwarded to a new action activity (which is 

other than the SoS) via Reply Code 504 (SDR forwarded to new action activity). Instead, the 

SoS will only receive a correction transaction (Transaction Purpose Set Code CO) containing the

new action activity so that the existing SDR record can be updated (under ADC 1066 

procedures). 
Attachment, ADC 1066A

Page 2

(3) Upon processing a change to the SoS RIC reflected in the action activity SDR 

reply transaction, WebSDR will be required to perform an edit check to determine if the new 

SoS has already received an information copy (Transaction Purpose Set Code 22) of the SDR. If 

not, WebSDR will send an information copy to the new SoS. This will allow any subsequent 

transactions to process successfully.

b. Background:

(1) Suppress SoS Copy of Reply Transaction. ADC 1066 (Reference 3.b.) 

identified a processing problem occurring with forwarded SDRs. When an SDR is forwarded to 

a new action activity using Reply Code 504, WebSDR sends a copy of the reply to the submitter 

and generates a new original SDR transaction (Transaction Purpose Set Code 00) for the new 

action activity. When this occurs WebSDR simultaneously distributes an information copy of 

the new SDR to the SoS. If the SoS is unchanged, the SoS already received an information copy 

of the initial submission, and this could cause the second SDR information copy identifying the 

new action activity to be rejected by the SoS as a duplicate. Under ADC 1066, if a second 

information copy is required after the Reply Code 504 forwarding action, it will be prepared as a 

correction so that the SoS record can be updated accordingly. This change was successfully 

implemented per ADC 1066; however, implementation highlighted an additional problem 

associated with this scenario. The SoS also receives a copy of all reply transactions prepared by 

other parties, including the reply transaction prepared by the original action activity containing 

the forwarding information. This transaction is redundant to the SoS information copy that now 

processes successfully as a correction. When the forwarding reply transaction processes prior to 

the correction in the SoS system, it cannot be properly processed. Since failed transactions 

require manual research to sort out the problem, DLA supply chains have asked that this

forwarding reply be suppressed by WebSDR as it is redundant.

(2) Information Copy to New SoS

(a) Under ADC 1066 (Reference 3.b.), WebSDR established new rules 

associated with changes to the value of the SoS Routing Identifier Code (RIC). The SoS RIC 

may be updated by a storage activity reply transaction on a Document Type 7 (customer SDR),

non-quality-related Document Type R (DLA distribution center SDR after redistribution between 

storage activities), or non-quality-related Document Type N (WebSDR-entered, comparable to 

Type R) SDR. The most common source of SoS corrections occur when the distribution center

processes a customer SDR and overlays an erroneous SoS entry provided by the submitter with 

the actual SoS known by the Distribution Standard System (DSS) to have directed the shipment. 

A similar situation could occur when a storage activity generates an SDR to the shipping activity 

after an owner/manager-directed redistribution and identifies an incorrect RIC in the SoS field. 

The shipping activity may overlay the incorrect owner/manager in its reply transaction. Under 

the new rules, upon processing a change to the SoS RIC, WebSDR will notify the original SoS to 

consider the SDR closed for that activity only (the SDR itself will remain open). The 

notification to the original SoS will take the form of an SDR reply from the DLA Transaction 

Services RIC, SGA, citing new Reply Code 450 (administrative closure notification). However, 

during discussion of this scenario, it was not recognized that the new SoS may not be able to 

process the reply transaction containing the updated SoS because that activity’s SDR system has 

no record of the original SDR. An information copy of the SDR must be provided to the 
Attachment, ADC 1066A

Page 3

correct/new SoS prior to transmitting the storage activity reply to ensure that these will process 

successfully.

Staffing Note: Until SDR systems are modified to separately identify the SoS, owner/manager 

(under ADC 1126, Reference 3.c.), the document type code is used to interpret the contents of 

the data field referred to as the “SoS.” For customer SDRs (Document Type 7), this field will 

contain the SoS responsible for directing the shipment to the customer. For redistribution SDRs

(Document Type R or N), this field will contain the owner/manager responsible for directing the 

shipment to the storage activity.

(b) The above process is not applicable to SDRs generated by storage 

activities when the action is directed to the owner/manager (e.g., Document Type 8, 9, or qualityrelated Type R or N). When these are generated with the incorrect owner/manager RIC, the SDR 

must be cancelled and resubmitted correctly. 

Staffing Note: DLA Distribution should review procedures to ensure that correction 

transactions are not used to update the owner/manager RIC when the intended action activity is 

the owner/manager. Instead, the SDR should be cancelled and resubmitted so that both the 

action activity and the owner/manager RIC values are the same. 

c. Approved Change in Detail:

(1) Suppress SoS Copy of Reply Transaction. WebSDR will suppress the 

SoS copy of the SDR reply (Transaction Set Purpose Code 11) when processing a forwarding 

reply containing Reply Code 504. If the SoS is unchanged, the SoS will receive a correction to 

update the record previously established by receipt of an information copy of the original SDR 

(same SoS, but different shipping activities identified as initial action activity).

(2) Information Copy to New SoS. Upon processing a change to the SoS RIC 

by a SDR reply (Transaction Set Purpose Code 11), WebSDR will perform an edit check to 

determine if an information copy (Transaction Set Purpose Code 22) has been previously sent to 

the new SoS. If the SoS has not received an information copy, WebSDR will send an

information copy to the new SoS RIC. This information copy must contain the updated SoS RIC 

rather than that contained on the original submission.

d. Revisions to DLM 4000.25 Manuals: Update DLM 4000.25 Volume 2, Chapter 17, 

Supply Discrepancy Reporting, to incorporate revised procedures. Insert procedures and revise 

paragraph numbering as follows:

“C17.3.20.4. DAAS will provide the support to SDR transaction 

exchange to facilitate DLMS processes.

C17.3.20.4.1. WebSDR will facilitate appropriate distribution 

when the action party receiving the initial distribution employs the Distribution/Status (Reply) 

Code 504 indicating the SDR must be forwarded to a new action activity. WebSDR will prepare 

the forwarded SDR in an original SDR format (Transaction Set Purpose Code 00) retaining all 

the information provided in the initial transmission plus the unique data fields applicable to the 

forwarding action per the DLMS 842A/W. The submitter will receive the reply transaction as 

notification of interim status. If an information copy of the initial SDR was provided to the SoS 
Attachment, ADC 1066A

Page 4

based upon Component rules, WebSDR will prepare an information copy of the forwarded 

transaction using the correction format (Transaction Set Purpose Code CO). When the SoS 

identified in the SDR correction is the same activity identified to receive the SoS copy of the 

SDR reply (Transaction Set Purpose Code 11), this reply transaction will be suppressed as 

redundant to the correction. WebSDR will update the SDR database to reflect the current 

action activity after this type of forwarding action and ensure that subsequent transactions are 

properly transmitted to the new action activity (rather than the original action activity). 1 

C17.3.20.4.2. If an SDR SoS is updated to identify a different SoS

(based upon action activity reply) after an information copy was provided to the original SoS, 

an SDR closure notification (Reply Code 450) will be generated by WebSDR to the originally

identified SoS so that the open record can be administratively closed. WebSDR will also provide 

an information copy (Transaction Set Purpose Code 22) of the original SDR to the newly 

identified SoS (the information copy will contain the updated RIC value rather than 

perpetuating the original value).

2”

______________________

1 Refer to ADC 1066/1066A. 2 Ibid 

e. Approved Transaction Flow: Refer to the enclosure.

f. Alternatives: None identified. 

5. REASON FOR CHANGE:

a. Suppress SoS Copy of Reply Transaction. This change will require DOD WebSDR 

to suppress the SoS copy of the SDR reply (Transaction Set Purpose Code 11) when an original 

SDR (Transaction Set Purpose Code 00) is generated as a result of a Reply Code 504 forwarding 

action. Currently the SDR reply is failing in EBS because it is being received prior to the 

correction (Transaction Set Purpose Code CO) reflecting the new action activity. There is no 

requirement to receive a copy of the reply transaction and the correction.

b. Information Copy to New SoS. Currently, when DLA Enterprise Business System 

(EBS) system receives a SDR reply (Transaction Set Purpose Code 11) without having already 

received an information copy (Transaction Set Purpose Code 22) transaction, EBS will fail the 

SDR reply transaction since there is no record on file. This change will allow for an information 

copy to be sent to EBS when the SoS RIC is changed as a result of a storage activity SDR Reply 

(Transaction Set Purpose Code 11). 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: These new rules will ensure Component systems can receive and 

properly process SDR transactions resulting in less manual effort for research and ensuring there 

are no gaps in communication of SDRs.

b. Disadvantages: None identified.
Attachment, ADC 1066A

Page 5

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The target implementation 

date is October 1st, 2015.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not able to quantify. 

9. IMPACT:

a. New DLMS Data Elements: There are no new data elements.

b. Changes to DLMS Data Elements: There are no revised data elements.

c. Automated Information Systems (AIS): There is no intended impact to Component 

SDR systems.

d. DLA Transaction Services:

(1) WebSDR will suppress the SoS copy of the SDR reply (Transaction Set 

Purpose Code 11) when processing a forwarding reply containing Reply Code 504 per above 

procedures. 

(2) WebSDR will send an information copy to the new SoS RIC per above 

procedures.

e. Non-DLM 4000.25 Series Publications: None identified.

10. PROPOSED ADDENDUM TO DLMS CHANGE 1066A STAFFING 

RESPONSE/COMMENT RESOLUTION:

Originator Response/Comment Disposition

1. DLA Concur

DLA Distribution provided the following 

feedback: 

We will be submitting a change request for DSS 

to prevent the users from updating owner and 

manager RICs on SDRs in the Automated 

Discrepancy Reporting System (ADRS) used for 

creation of SDRs within the Distribution 

Standard System (DSS). If the user tries to 

change the owner/manager RIC, DSS will 

systemically not allow them to do this, but it will 

not systemically force them to cancel the SDR. 

The cancellation process will not be systemic, it 

will be procedural.

Noted.

This proposed change to ADRS 

will reduce miscommunication of 

SDRs, but does not impact this 

ADC. The improved WebSDR 

processing described in this 

change will support corrections to 

the owner/manager which occur 

in the Incoming SDR (ISDR) 

application within DSS.
Attachment, ADC 1066A

Page 6

Originator Response/Comment Disposition

2. Army Concur Noted.

3. Navy No response received.

4. Marine Corps Concur Noted.

5. Air Force No response received.
Enclosure, ADC 1066A

Page 1

Enclosure, Transaction Flow Diagrams
Enclosure, ADC 1066A

Page 2