ADC 225 

DOD WebSDR Requirement for Information Copy 

1. Originator 

 a. Service/Agency: Defense Logistics Agency (DLA) 

 b. Originator: DLA/J-3731, phone: DSN 427-2527 / Commercial 703-767-2527 

2. Functional Area: Primary: Supply

3. Requested change 

 a. Title: DOD WebSDR Requirement for Information Copy 

 b. Description of Change: This change establishes procedures for WebSDR/DAAS creation/ 

transmission of an information copy of an SDR in response to an SDR reply reject code sent to DAAS. 

The reject condition is applicable when the Distribution Depot (DD) is the action activity, and the source 

of supply (SoS), e.g., DLA (Routing Identifier SMS), cannot process the DD reply due to lack of a record 

establishing the basic report. This is an expansion of current information copy requirements already 

implemented under DOD WebSDR.

 c. Background: 

 (1) DLA Business Systems Modernization (BSM) design for SDR processing requires a basic 

report to be posted before a reply can be accepted. WebSDR currently sends an information copy of the 

original report when the SDR is created on-line and the SoS is known to be “SMS.” Due to a lack of 

available historical data at DAAS, WebSDR cannot always identify the SoS and provide the required 

information copy as was originally planned when WebSDR was implemented. DLA has taken action to 

overcome this gap by programming the Distribution Standard System (DSS) (DSS/ISDR programs) to fill 

in the missing SoS on SDRs replies when that information is available in DSS. WebSDR will then create 

an information copy of the reply for the SoS. However, when DSS sends a reply to WebSDR for BSM 

managed material with the added SoS, the replies are rejecting. BSM will reject responses where 

WebSDR did not send an original (DLMS transaction Beginning Segment code 00 or 22). 

 (2) BSM has no way to correct this problem without a major system overhaul, as the current 

processing is deeply imbedded in the system. Many examples have been provided to DAAS which 

indicate the A5_ transactions are passing through DAAS, however for some reason DAAS does not 

always capture that A5_ information. Therefore, DAAS is not always providing prefilled shipping 

information as was expected by DLA system programmers. Due to BSM systems limitations, DLA is 

requesting DAAS/WebSDR develop programming to correct this transaction exchange gap. 

(3) This same issue will be applicable to SDRs which do not originate on WebSDR, but are 

originated within a Service application and may be transmitted electronically without the SoS. Since the 

number of these is expected to grow over time, this requirement will support the long-term process. 

 d. Procedures: 

(1) Requested programming changes include the following: 
 (a) SDR applications may establish a capability to request an information copy of a basic 

SDR report. This may be needed in order for the source of supply to accept and process an SDR reply 

transaction provided by an external organization which is unmatched to the internal data base. For 

example, this situation may apply to an SDR reply from a DD action activity provided to DLA BSM with 

recommended resolution following depot research. 

 (b) To obtain an information copy, the SoS may reject the SDR transaction using the 

SDR reply transaction format and Reply Code 926 (no record found) and forward to the DAAS Routing 

Identifier (SGA) (vice the RIC of the SDR action activity generating the reply) with clarifying comments 

“SDR transaction cannot be processed because original report is not on file; request information copy be 

provided.”

 (c) When DAAS receives a 926 reply code which is directed to DAAS (and not the 

customer or submitting system), DAAS will look to see if there is a record in history. If a record is found 

DAAS will create an information copy (beginning segment=22) and forward it to the organization which 

created the reject. 

 (d) The source of supply will then be the responsibility for re-processing the failed 

transaction after the information copy of the original report has been received and accepted. 

 (e) If DAAS receives a request for an information copy as described above and it is 

found to be unmatched to the DAAS database, DAAS will reject the transaction to the submitter. This 

will be accomplished using a DAAS generated reply transaction with a Reply Code 926 (no record found) 

and clarifying remarks, "Requested SDR not found in history; WebSDR cannot provide an information 

copy." Pending implementation of full DAAS reject functionality, DAAS may identify unmatched 

requests using off-line notification. 

(2) Insert the following subparagraph into the joint Component guidance and DLMS manual in 

the existing section for DAAS processing business rules: 

DAAS SDR Processing. 

 Under DLMS, SDRs shall be integrated with standard logistics transaction processing through 

DAAS. DAAS shall perform the following actions ............... 

 DAAS will respond to DAAS-directed rejected reply transactions indicating no 

matching original report or information copy of the SDR is found in the automated application (Reply 

Code 926), by providing an information copy of the original report to the activity which rejected the 

reply. Unmatched requests for an information copy will be returned by DAAS reject (Reply Code 926) 

to the sending organization. 

 e. Alternatives: 

(1) Automated DAASC: WebSDR could check for prior transmission of an original report when 

sending a reply to BSM. If no record of having forwarded previously, generate an information copy of 

the report and transmit at same time the reply is forwarded. 

 

(2) Manual DLA: BSM currently receives a significant number of DLMS 842A/R transactions 

that are rejecting due to the situation described in this proposed change. The work around for processing 

the rejected SDRs into BSM is all manual and very labor intensive. 
4. Reason for change: 

 a. BSM currently does not have capability to make a system change at this time to eliminate this gap. 

Providing pre-filled information on the original SDR report was identified as a DAAS responsibility and a 

significant number of examples indicate issues on missing A5_ information are a DAAS problem. DAAS 

also appears to be better able to make the necessary system changes to eliminate the gap. 

 b. This change will improve DAAS/WebSDR processing/business rules by ensuring WebSDR sends 

the original report or information copy to BSM on all SDRs where the SoS is SMS. This will eliminate 

the current labor intensive process in BSM of manual look-up on SDRs that reject in BSM for missing 

report. It will turn this manual process into an automated process. 

 

5. Advantages and Disadvantages: 

 a. Advantages: This will improve SDR processing by eliminating manual processing in BSM for 

those SDRs which are rejecting in BSM due to receiving a reply where no original was received. This 

will save DLA manpower and time. Currently BSM is receiving approximately 75-100 transactions per 

month which fall into this scenario. 

 b. Disadvantages: None specifically identified. 

6. IMPACT: 

 a. Data Content/Procedures: This change request will impact DAAS/WebSDR, as it will require 

changes to WebSDR/DAAS processing in response to the DLA reject notice. This change will also 

require program change to BSM to provide the reply rejection to DAAS. 

 b. Publications: Impact to DOD 4000.25-M, DLMS publication