DEFENSE LOGISTICS AGENCY HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

April 01, 2020

MEMORANDUM FOR SUPPLY DISCREPANCY REPORT (SDR) PROCESS REVIEW 

COMMITTEE (PRC) MEMBERS

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 

1052A, Addendum to ADC 1052, DOD Web Supply Discrepancy Report 

(WebSDR) Processes Enhancement and Interface with Electronic Document 

Access (EDA) System (Supply/SDR)

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

approved for implementation. 

Addressees may direct questions to EBSO.SDR@dla.mil. Others must contact their 

designated SDR PRC available at: 

https://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. 

TERESA W. SMITH

Director, Strategic Data Services

 DLA Information Operations

Attachment

As stated 

cc: 

ODASD(Logistics)
Attachment, ADC 1052A

Page 1

Attachment to ADC 1052A, 

Addendum to ADC 1052, DOD Web Supply Discrepancy Report 

(WebSDR) Processes Enhancement and Interface with Electronic 

Document Access (EDA) System (Supply/SDR)

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

Ben Breen, DOD Discrepancy/Deficiency Administrator, Email: EBSO.SDR@DLA.MIL.

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: 

a. Primary/Secondary Functional Area: SDR

b. Logistics and Transaction Changes (Check All That Apply): 

 Category  Category  Category

Billing Physical Inventory Contract Admin

X Discrepancies / Deficiencies MILSTRAP DoDAAD

Serialization MILSTRIP MAPAD

Small Arms/Light Weapons MRA LMARS

pRFID Disposition X DLM Publications

GFP DOD BRAC

3. REFERENCES:

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

b. ADC 1052 DOD Web Supply Discrepancy Report (WebSDR) Processes 

Enhancement and Interface with Electronic Document Access (EDA) System, May 03, 2013

4. REQUESTED CHANGE(S):

a. Brief Overview of Change:

(1) This change amends ADC 1052. To prevent automated SDR rejections, 

WebSDR will no longer overlay or update the PIID, Call Order, CLIN based on the data received 

from existing interface between the EDA System and the DOD WebSDR application when 

values are present on the original submission. The EDA and WebSDR interface will continue to 

identify and populate the contract administration office (CAO) DOD activity address code 

(DoDAAC) and the vendor/ contractor commercial and government entity (CAGE) code for the 

discrepant shipment when the contract number/PIID is provided, only when the CAO and CAGE 

fields are blank in the SDR by the submitter.
Attachment, ADC 1052A

Page 2

b. Background:

(1) Several components/SDR systems reported that WebSDR was rejecting SDRs 

with Reply Code 940 for PIID Call Order Missing or in the Wrong Location. Further research 

revealed, an issue with the interface issue between WebSDR and EDA where data was either 

missing or populated in the wrong location in the transaction

(2) ADC 1052 established an interface between the EDA System and the DOD 

WebSDR application to obtain essential information for populating SDR records. When 

information is originally populated by the submitter with different information than identified in 

EDA records, this interface identifies and overwrites the CAO DoDAAC and the 

vendor/contractor CAGE code for the discrepant shipment when the contract number is provided 

in the SDR by the submitter or action activity. 

c. Requested Change in Detail:

(1) DOD WebSDR will continue to initiate the EDA interface for all SDRs 

containing a PIID, Call Order, CLIN. The PIID, Call Order, or CLIN is mandatory in SDRs 

prepared using SDR Document Type 9 and P. Document Type 6 SDRs should identify the 

contract number, but it may not be provided on the initial report. If missing on the initial report, 

the action activity is expected to provide the contract number when preparing the SDR reply. 

Through the EDA System interface, EDA will use the PIID, or Call Order provided by WebSDR 

to find the matching contract number records and extract the DoDAAC of the CAO and CAGE 

code (applicable to the prime contractor) and return these values to WebSDR. WebSDR will 

only populate these values if on the original 00 SDR submission they were blank. Therefore, if 

the original 00 SDR populates any data in the Cage/CAO or PIID or Call Order number, 

WebSDR will NOT overwrite these values via the EDA interface when different from the 

original submitting entry. 

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

as shown in the enclosure.

e. Approved Transaction Flow: When values are present on the original submission, 

WebSDR will no longer overlay or update the PIID, Call Order, CLIN, CAO or CAGE based on 

the data received from existing interface between the EDA System and the DOD WebSDR 

application. 

f. Alternatives: None

5. REASON FOR CHANGE: Several Components identified issues with WebSDR rejecting 

SDRs citing Reply Code 940. Further research revealed an issue with the interface between 

WebSDR and EDA when overwriting.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Prevent further systemic SDR rejections.

b. Disadvantages: None.
Attachment, ADC 1052A

Page 3

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

DEVELOPMENT: EDA data should not overwrite submitter data.

8. ADDITIONAL COMMENTS TO CONSIDER: WebSDR reprocessed all the affected 

SDRs that were rejected, with the exception of the info only SDRs (Action Code 1H/3B) since 

these did not require a response. 

9. ADDITIONAL FUNCTIONAL REQUIREMENTS: TBD

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Upon approval

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: No specific data is available.

12. IMPACT: 

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

under this change.

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS): None

d. Defense Automatic Addressing System (DAAS): Eliminate the WebSDR overlay 

of EDA data when already present in the original SDR submission. If the original 00 SDR 

populates any data in the Cage/CAO or PIID or Call Order number, WebSDR will NOT 

overwrite these values via the EDA interface when different from the original submitting entry.

e. Non-DLM 4000.25 Series Publications: None
Enclosure, ADC 1052A

Page 1

Enclosure, DLMS Manual Revisions

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

Intervening text not shown

C17.3.20.1.2.4. SDRs that contain a contract number (not including the 

contract reference number) will be edited to ensure that the shipper is populated correctly. DoD 

WebSDR will match the contract number against the Electronic Document Access (EDA) 

System contract files to identify the vendor/contractor CAGE code and the applicable CAO 

DoDAAC. If a match is found, these values from the EDA contract information will update in 

the SDR record. If the submitting system for the original 00 SDR populates any data in the 

Cage/CAO or PIID or Call Order number, WebSDR will not overwrite these values when 

different from the original submitting entry.

 User input will be overridden by the EDA values if different.1

 1 Ibid.