DPAS SCR: 02325

• SCR Number
  02325
• Title
  Supply Discrepancy Report (SDR) Capability Implementation
• DPAS Module
  Materiel Management
• Reporting Organization
  USMC
• State
  New
• History
  7/22/2026
• Description
  Change Request: 

  Policy / Regulatory
  
  

  Description: 
  

  ELMS requires a compliant, integrated SDR capability to support the complete SDR lifecycle. The attached SDR requirements matrix and process flows identify required functionality for reportability determination, SDR case creation, discrepancy coding, requested action coding, mandatory field validation, attachments, DLMS 842A/W generation, DAAS transmission, WebSDR control-number capture, DLMS 842A/R response processing, follow-up processing, financial adjustment tracking, audit history, and final closure. Without this capability, SDR processing would rely on manual or external processes that do not provide complete lifecycle control, transaction traceability, or audit-ready evidence.
  

  The capability impacts warehouse, materiel management, ICP, supply, action activity, quality control, and program office users who must identify, submit, route, respond to, follow up on, and close SDRs. Failure to implement creates operational, audit, data integrity, accountability, and policy compliance risk by limiting ELMS visibility into shipment, packaging, documentation, quantity, condition, materiel, and financial discrepancy resolution.

  The attached SDR artifacts define three related process areas: SDR Generation, SDR Response, and SDR Follow-Up. The requirements matrix contains developer-ready SHALL statements mapped to DLM 4000.25, Volume 2, Chapter 17 and Appendix 7.28. The flowchart package depicts the operational sequence for determining reportability, creating and validating SDRs, transmitting 842A/W transactions through DAAS, receiving 842A/R responses, monitoring open cases, generating authorized follow-ups, and closing cases only after final adjudication and required actions are complete.
  
  

  Recommended: 

  Implement ELMS SDR functionality to create, validate, transmit, track, respond to, follow up on, financially monitor, audit, and close SDRs. The expected outcome is an audit-ready SDR capability that preserves source transaction links, code selections, remarks, attachments, DAAS/WebSDR acknowledgments, response history, follow-up history, financial adjustment status, final disposition, and closure records throughout the SDR lifecycle.
  Implement the complete ELMS SDR Generation capability. ELMS shall determine reportability; route non-reportable discrepancies to authorized local correction; create unique SDR cases; link source transactions; capture discrepancy details; support Chapter 17 and Appendix 7.28 code families; validate discrepancy, document type, and requested action codes; require Z1 and 1Z explanations when applicable; capture mandatory document, shipment, procurement, remarks, attachment, and code-dependent data; validate all mandatory fields before release; generate and transmit original DLMS 842A/W transactions through DAAS; process DAAS/WebSDR acknowledgments; preserve WebSDR control numbers; maintain open cases during research; enforce role-based access; preserve data; and maintain immutable audit history. See attached requirements matrix for complete SDR-GEN, SDR-RSP, SDR-FU requirements statements and acceptance.
  
  

  Mission Critical: 
  

  N/A
  
  

  Benefits: 
  Summary:
  

   

  The three ELMS Supply Discrepancy Report (SDR) process flows define the end-to-end lifecycle of an SDR after its submission. Collectively, they establish how ELMS receives and processes SDR responses, maintains accountability throughout the adjudication process, and manages follow-up activities until final resolution. The flows ensure that all inbound and outbound transactions are validated, matched to the correct SDR, processed in accordance with DLM 4000.25, Volume 2, Chapter 17, and retained with a complete audit trail.

   

  Specifically, the SDR Generation Process Flow depicts the overall life-cycle from SDR submission through final closure; the SDR Response Process Flow defines how ELMS receives, validates, classifies, and processes 842A/R response transactions while preventing premature case closure and maintaining auditability; and the SDR Follow-Up Process Flow governs aging, due-date monitoring, financial tracking, escalation, and generation of authorized follow-up transactions to ensure unresolved SDRs remain active until a final adjudication and all required corrective actions have been completed. Together, these flows provide standardized processing, support audit readiness, improve operational visibility, ensure policy compliance, and maintain complete accountability for every SDR throughout its life-cycle
  
  

  Frequency: 
  Daily
  
  

  Users: 
  N/A