DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

August 14, 2019

MEMORANDUM FOR SUPPLY AND SUPPLY DISCREPANCY REPORT (SDR) PROCESS 

REVIEW COMMITTEE (PRC) MEMBERS

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

1342, Elimination of Transaction Set (TS) 49 Supply Discrepancy Reports (SDRs) 

Transmitting from Product Data Reporting Evaluation Program to WebSDR.

The attached change to DLM 4000.25, Defense Logistics Management Standards (DLMS), 

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

DREXEL K. ROSS

Acting Director

Enterprise Business Standards Office

Attachment

As stated

cc: 

ODASD(Logistics)
Attachment, ADC 1342

Page 1

Attachment to PDC 1342

Elimination of Transaction Set (TS) 49 Supply Discrepancy Reports 

(SDRs) Transmitting from Product Discrepancy Reporting Evaluation 

Program to WebSDR

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Brandon Richardson, Naval Sea Command, Comm. 207-438-6491 

or e-mail: brandon.richardson@navy.mil 

b. Functional POC: Simon A Hernandez, Navy Supply Head Quarters, Comm. (717) 

605-1425, DSN 430-1425 or e-mail: simon.hernandez3@navy.mil.

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: 

a. Primary/Secondary Functional Area: SDRs

b. Primary/Secondary Functional Process:

c. 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. SECNAV Instruction 4855. 3C, Product Data Reporting Evaluation Program, June 27, 

2014. 

b. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2, Supply 

Standards and Procedures, Chapter 17, Supply Discrepancy Reporting

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: Terminate the use of historical SDRs, (identified by

Transaction Set Purpose Code 49), from the Product Data Reporting and Evaluation Program 
Attachment, ADC 1342

Page 2

(PDREP) system to WebSDR and follow standard Supply Discrepancy Report (SDR)

transactional routing conventions.

b. Background: During the design for WebSDR, Components using internal SDR 

systems identified a need for a business process that would allow SDRs to be worked internal to 

the Component or internal to the Component’s SDR application without providing standard 

transaction/e-mail outputs from WebSDR. Historical SDRs (identified by Transaction Set 

Purpose Code 49) were established for this purpose. Historical SDRs are currently used by 

PDREP, and are entirely internal to the PDREP. These SDRs are created and resolved within the 

PDREP system. For example, the Navy creates an SDR and routes the SDR to another Navy or 

United States Marine Corp (USMC) action point to resolve. When an SDR is created and routed 

to a Navy or Marine Corps action point, PDREP stamps these SDRs in the background of the 

system as Purpose Code 49 SDRs. PDREP sends a copy of these SDRs to WebSDR for 

inclusion in reporting and metrics. WebSDR does not apply any business rules or edits to 

PDREP SDRs with Purpose Code 49, but allows them to be recorded into WebSDR. Normally, 

WebSDR would not process these SDRs due to missing data content. Also, if for any reason, an

SDR with Purpose Code 49 needs to re-routed to an action point outside of PDREP, that SDR 

cannot be properly routed because Component SDR systems are not configured to receive SDRs 

with Purpose Code 49, since they were initially designed to remain internal to PDREP. This 

results in SDRs with Purpose Code 49 not being routed correctly, being rejected, and ultimately 

not supporting the warfighter adequately, by ensuring SDRs are created, processed, and resolved

in a timely manner. 

c. Requested Change in Detail: This proposed change will require PDREP to generate 

all new SDR transactions with TS Purpose Code 00, and exit these transactions to WebSDR 

regardless if the initiator and responder is Navy or USMC. This will enable PDREP to follow 

standard SDR processes and routing regardless of what activity initiates and responds to the 

SDR. This change will eliminate any historical (Transaction Set Purpose Code 49) SDR from 

being generated in PDREP.

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

Supply Discrepancy Reporting, as shown in Enclosure.

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

f. Alternatives: None noted. 

5. REASON FOR CHANGE: WebSDR does not apply business rules to SDRs with Purpose 

Code 49. The classification of SDRs with Purpose Code 49 is transparent to the PDREP users. 

However, when the communication problem between PDREP and WebSDR occurs due to the 

Purpose Code 49 in an SDR, the PDREP user must manually work the SDR with Transaction Set 

Purpose Code 49 to cancel it and resubmit or contact the SDR Functional Lead-NSLC 

Portsmouth, ME to manually re-route it. Therefore, SDR Functional Lead-NSLC Portsmouth,

ME receives a high volume of customer service calls. Simultaneously, this issue increases the 

number of the days it takes to close SDRs, resulting in longer customer wait time. 
Attachment, ADC 1342

Page 3

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Eliminates manual work by the SDR user and the SDR Functional 

Lead-NSLC Portsmouth, ME.

b. Disadvantages: None noted.

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

DEVELOPMENT: This will allow SDRs to follow normal SDR processing rules and 

standards. 

8. ADDITIONAL COMMENTS TO CONSIDER: None

9. ADDITIONAL FUNCTIONAL REQUIREMENTS: None

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: TBD by the PDREP 

program office. 

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Cost avoidance cannot be quantified at this time, 

however, this change will prevent component systems from receiving SDRs with Purpose Code 

49, which ultimately end up failing or being rejected since the receiving systems are not 

programmed to receive them. 

12. IMPACT: 

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS): PDREP will need to be updated as stated 

above. 

d. Defense Automatic Addressing System (DAAS): WebSDR will need to remove 

any specific programming linked to processing SDRs with Purpose Code 49, since PDREP will 

no longer be transmitting them. 

e. Non-DLM 4000.25 Series Publications: None

13. PROPOSED DLMS CHANGE (PDC) 1342 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. ODASD(Logistics) Concur without comment Noted.

2. DLA Concur without comment Noted.

3. Navy Concur without comment Noted

4. Air Force None
Attachment, ADC 1342

Page 4

5. US Army Concur without comment Noted.

6. USMC None

7. DAAS Concur without comment Noted.

8. USTRANSCOM Abstains Noted.

9. AFSAC None

10. DCMA None

11. DSCA Concurs without comment. Noted.
Enclosure, ADC 1342

Page 1

Enclosure, Defense Logistics Manual (DLM) 4000.25, Volume 2, Revisions

Revise Chapter 17 as shown. Deletions are shown in double-strikethrough. 

(Preceding text not shown)

C17.3.17. Historical SDR Purpose and Procedures. During the design for 

WebSDR, Components using internal SDR systems identified a need for a business process 

that would allow SDRs to be worked internal to the Component or internal to the 

Component’s SDR application without providing standard transaction/e-mail outputs from 

WebSDR. Historical SDRs (identified by Transaction Set Purpose Code 49) were 

established for this purpose. Historical SDRs are currently employed by two one systems: 

the Product Data Reporting and Evaluation Program (PDREP).