Attachment to ADC 459, Page 1

ADC 459

DLMS Transactions, Discrepancy Codes, SDR Type/Disposition Services Type Codes, 

and Associated Procedures to support SDRs under RBI

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Service/Agency: Defense Logistics Agency Disposition Services

b. Technical POC: DLA Logistics Information Service (LAR)

c. Functional POC: DLA Logistics Information Service (LAR) 

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Primary: Supply/Logistics DLA Disposition Services

b. Primary/Secondary Functional Process: Primary: Materiel Delivery Notification for DLA 

Logistics Information Services products

3. BACKGROUND: 

a. Reutilization Business Integration (RBI): The DLA Disposition Services (formerly Defense 

Reutilization and Marketing Service (DRMS)) is a worldwide presence within the Department of 

Defense, with disposal specialists in 14 foreign countries, two U.S territories, and 39 states. DLA 

Disposition Services’ mission is the execution of disposition solutions for excess military property. 

The Reutilization Business Integration (RBI) project will replace the DLA Disposition Services 

Automated Information System (DAISY) by integrating DLA Disposition Services business processes 

within the DLA enterprise suite of applications, including the Distribution Standard System (DSS) and 

the Enterprise Business system (EBS).

b. Recycling Control Point (RCP): Through an agreement with DLA Distribution, property 

identified as RCP property is held in place at the DLA Distribution Depot until disposition is 

determined and communicated by DLA Disposition Services electronically.

c. Data Element Background: 

(1) Under DLMS, the “Discrepancy Report Document Type Code,” hereafter referred to as 

“Document Type Code,” identifies the type of discrepancy report and type of shipment involved. An 

updated definition and code list is shown at Enclosure 1.

(2) A separate DLMS data element, the “DRMS SDR Type Code,” is re-named “Disposition 

Services SDR Type Code” and is hereafter referred to as “Disposition Services Type Code” (also 

sometimes referred to as a Sub-Type Code). This data element is used as a breakdown of the type of 

DLA Disposition Services shipment involved and is used in conjunction with a Document Type Code. 

It was established for use on SDRs input manually via DOD WebSDR.

d. Intent of the transaction: The SDR transaction with a new Document Type Code/Disposition 

Services Type Code will provide the DLA Disposition Services Field Offices improved capability to 

identify, communicate, and resolve discrepancies for all locations. Specific business rules are defined 

by the assigned “type codes.” 
Attachment to ADC 459, Page 2

e. Scenario for which the SDRs are used: Discrepancies may be identified in shipments 

between the Recycling Control Pont (RCP) and the DLA Disposition Services Field Office, between 

RCP and the customer, between the two DLA Disposition Services Field Offices, and between the 

DLA Disposition Services Field Office and the customer. The SDR may be reported by the receiving 

Field Office or by the receiving customer.

f. Procedures, transactions, data elements, processing details in use today:

(1) Recycling Control Point (RCP) SDRs Prepared via DOD WebSDR: Currently, DLA 

personnel at the DLA Disposition Services RCP (identified by Routing Identifier Code (RIC) S9W) 

receive and process discrepancies via DOD WebSDR for property shipped by the depot to various 

customers, the Controlled Property Centers, Demilitarization Centers, Long Term Storage facilities,

and Field Offices. Discrepancies include non-receipts, wrong item, wrong quantity, and missing 

documentation for hazardous items. SDRs may also be issued to manage due-ins over 60 days with 

no usable receipt/receipt acknowledgment. A document number must be input and SDR 

document/Disposition Services type of “7/P” selected for DLA Disposition Services Field Office SDR, 

depot shipment. The Web-prepared SDR is automatically pre-filled with shipping and requisition

information pulled from DLA Transaction Services Defense Automatic Addressing System (DAAS)

history files. At times, the user will overwrite the pre-filled information to correct the clear text 

address associated with the Disposition Services DoDAAC to the Depot/Shipper’s DoDAAC. The 

user will select the discrepancy code as applicable for the situation. The pre-populated RICs must be 

verified. The appropriate action code will be selected and remarks inserted. The distribution 

information is completed by typing “SC4402” to generate an email to the Disposition Services RCP

WebSDR Admin mail group. This sends an email to DLA Disposition Services Battle Creek RCP. 

There is a tracker located on a shared drive for Disposition Services to track all open SDRs. On day 

30, if a response has not been received by the Depot, a follow-up SDR is required. If no response is 

received after 25 days from the follow-up the following rules apply:

(a) For overages, return the property to the Depot it was received from using 

TAC/shipping information received from DLA Disposition Services Battle Creek RCP.

(b) For controlled property received by misshipment, contact the Depot directly to try and 

resolve the discrepancy prior to returning the property to the Depot.

(c) For total non-receipt of property shipped from a depot to DLA Disposition Services 

Field Office, process a loss transaction. 

(2) DLA Disposition Services Incoming Customer SDRs: SDRs submitted to DLA 

Disposition Services may be submitted by DOD customers using their Component SDR application or 

direct input via DOD WebSDR. SDRs are addressed to RIC S9D and are routed by WebSDR to the 

associated email address. SDRs directed to S9D are not copied automatically to DLA Enterprise 

Business System (RIC SMS). Non-DOD customers may report problem shipments to DLA 

Disposition Services via customer survey or email and the discrepancy is resolved offline.

(3) DLA Disposition Services Outgoing Discrepancy Reports: Currently, when a 

generating customer turns in excess property to the DLA Disposition Services Field Office, a report of 

discrepancy may be created using the DLA Disposition Services Form 917. If, based upon inspection 

of the property, it is determined that there are discrepancies with the paperwork/documentation, 

property, packaging (quantity or condition), or if the property cannot be accepted by DLA Disposition 

Services, per the DOD 4100.21-M manual Chapter 3, the DLA Disposition Services Field Office 

personnel creates the DLA Disposition Services Form 917. The DLA Disposition Services Field 

Office personnel will also contact the turn-in activity (the generator) to make arrangements to pick up 

any non-acceptable property. 
Attachment to ADC 459, Page 3

4. APPROVED CHANGE(S): This ADC documents requested modifications to SDR procedures 

and the DLMS 842A/W Standard SDR. 

a. Approved change in detail:

(1) Document Type Codes. A new Document Type Code D will be assigned to distinguish

all outgoing SDRs created by DLA Disposition Services Field Offices using DSS. Refer to Enclosure 

1. 

(2) Disposition Services Type Codes. The existing data element “Defense Reutilization and 

Marketing Service (DRMS) Supply Discrepancy Report (SDR) Type Code” is renamed, “DLA 

Disposition Services SDR Type Code” and revised as discussed below. Also refer to Enclosure 1. 

(a) RCP SDRs Prepared via DOD Web SDR: DLA Disposition Services RCP personnel 

will continue to leverage DOD WebSDR to input discrepancies for property shipped to various 

customers under selected processes. However, two Disposition Services Type Code values (L and P) 

will be eliminated (those eliminated are now consolidated under the outgoing SDR Disposition

Services Type Codes used by DSS). 

(b) DLA Disposition Services Outgoing SDRs (DSS/Automated Discrepancy 

Reporting System (ADRS): Upon deployment of RBI, DLA Distribution Services Field Offices will 

use the DSS SDR process to document and communicate supply discrepancies using the new SDR 

Document Type Code of D in association with new Disposition Services Type Codes. New values will 

be used to distinguish the following scenarios resulting in supply discrepancies:

1. Property turned in to the DLA Disposition Services Field Office by the turn-in 

activity,

2. Property shipped by the Distribution Depot to a DLA Disposition Services Field

Office, and

3. Redistribution of property between DLA Disposition Services Field Offices.

(c) Discrepancy Codes. Additional discrepancy scenarios are applicable for DLA 

Disposition Services receipts from the generating activity’s turn-in of excess property. Most of these 

discrepancy scenarios will be identified internal to DSS using a unique discrepancy code. However, 

to minimize impact to external DOD processing and procedures, most will be used to trigger specific 

remarks for the outgoing SDR, but the code itself will not be perpetuated. Instead, the associated 

standard DOD discrepancy code value will be used for distribution of the SDR. The internal codes 

will remain available in DSS for metrics and management reports. Because a few of the discrepancy 

scenarios specific to DLA Disposition Services are not related to existing discrepancy codes, new 

DOD discrepancy codes must be assigned. New codes are needed to identify the turn-in of 

unauthorized property and lack of specific documentation for hazardous materiel/hazardous waste. 

Refer to Enclosure 2 for new DOD discrepancy codes, which Component SDR applications must be 

able to accept. Enclosure 3 contains a cross reference between the internal DSS discrepancy code and 

associated text explanation to be passed in the SDR remarks with the corresponding DOD discrepancy 

code. 
Attachment to ADC 459, Page 4

(d) Action Codes. One new action code is required to support the RBI SDR process and 

the transition away from the Form 917. When the generator turns in property that cannot be accepted 

by the DLA Disposition Services Field Office, the Field Office will prepare an SDR using Action 

Code 3C indicating pick-up of unauthorized or unacceptable property is required. Refer to Enclosure 

2.

(e) Primary/Secondary Document Numbers: As with other RBI transaction exchanges, 

the SDR may require communication of two document numbers. The following rules apply:

1. Property Turned in by a Generating Activity: The value used for the Disposal 

Turn-in Document (DTID) Number/Suffix by the customer will be the primary document 

number/suffix identified in the SDR. If a Unique Control Number (UCN) was established by the Field 

Office upon receipt, it will not be perpetuated to the SDR.

2. Property Shipped by the DLA Distribution Depot to DLA Disposition Services 

Field Office: The document number used to ship the property will be the primary document number 

identified in the SDR. No secondary document number will be applicable.

3. Redistribution of Property between Disposition Services Field Offices: The 

redistribution document number will be the primary document number identified in the SDR. The 

DTID used by DLA Disposition Services to track materiel will be perpetuated in the SDR.

b. Approved procedures: DLA Disposition Services incoming customer SDRs will not be sent 

to EBS. No informational emails will be provided by DOD WebSDR. All tracking will be done via 

the SDR reports. Incoming SDRs will be sent to the Research Property area to be worked. SDR 

reports must be available within DSS for DLA Disposition Services personnel to research.

(1) DLA Disposition Services Incoming Customer SDRs: Incoming SDRs addressed to 

DLA Disposition Services (RIC S9D) or RCP (RIC S9W) will continue to be supported by conversion 

to email via DOD WebSDR. The generic email address for S9D will also be associated with all of the 

DLA Disposition Services Field Offices identified in Enclosure 5 for Document Type 7 only. This 

will allow customer SDRs to be forwarded to DLA Disposition Services pending implementation of 

enhancements to support processing of DLA Disposition Services customer SDRs within DSS. 

Replies will be created in DOD WebSDR.

(2) RCP SDRs Prepared via DOD WebSDR. RCP personnel will continue to log-in to DOD

WebSDR to create and submit SDRs using Document Type 7 and the related Disposition Services 

Type Code. SDR replies to the RCP web-entered SDRs will be directed to the existing DLA 

Disposition Services email address associated with RIC S9W.

(3) DLA Disposition Services Field Office Outgoing SDR (DSS/Automated Discrepancy 

Reporting System (ADRS))

(a) DLA Disposition Services Field Offices may initiate an SDR at any point in the 

receiving process via DSS. SDRs prepared by DLA Disposition Services will use the new Document 

Type Code D to identify SDRs as coming specifically from DLA Disposition Services.

1. SDRs applicable to DLA Disposition Services Field Office receipts from 

generating activity turn-in will identify a Disposition Services Type Code T (DLA Disposition 

Services Field Office Turn-In). 
Attachment to ADC 459, Page 5

2. SDRs applicable to DLA Disposition Services Field Office receipts from 

redistribution of property between Field Offices will identify a Disposition Services Type Code E 

(DLA Disposition Service Field Office Redistribution). Using SDR Document Type D for Field 

Office redistribution will allow WebSDR and DSS to bypass business rules associated with 

Distribution Depot redistribution receipts associated with Document Type Code R.

1

3. SDRs applicable to DLA Disposition Services Field Office receiving a shipment of 

property from Distribution Depots will identify a Disposition Services Type Code B (Property shipped 

by the Distribution Depot by to a DLA Disposition Services Field Office). For RCP receipts, the 

property goes through Reutilization/Transfer/Donation (RTD) screening while the property is 

physically located at the Depot. If the property is not requisitioned by the end of the screening period, 

the property is shipped to the co-located DLA Disposition Services Field Office, designated DEMIL 

Center, or the Commercial Venture (CV) partner for disposal processing. If the property is not eligible 

for RCP, the property is transferred from the Depot directly to the co-located Field Office/Centralized

DEMIL Center (CDC) for disposal processing. If the property is received with a discrepancy, then an 

SDR is created using Disposition Services Type Code B.

(b) Upon identification of the need to submit an SDR, the user will initiate the SDR 

process in DSS and select by Disposition Services Type Code: Receipt from Generating Activity or

Redistribution between DLA Distribution Services Field Offices or Receipt from DLA Distribution 

Depot. The receiver will identify the specific discrepancy from a listing including new subdiscrepancy codes internal to DSS (Enclosure 3). These sub-discrepancy codes will be mapped to the 

approved DOD SDR discrepancy codes that will be transmitted by DSS. The text explanation for the 

internal sub-discrepancy code will be mapped to the SDR remarks. Additional remarks may also be 

provided for clarification. DSS will create the DLMS 842A/R SDR Reply transaction.

(c) Procedures for SDRs associated with Turn-in of Discrepant Property 

1. Action Activity/Turn-in Activity Email/Distribution Rules 

a. SDRs resulting from discrepant turn-ins will be directed to the shipping 

activity DoDAAC identified in the turn-in document number. Staffing Note: The SDR should be 

directed to the shipping activity DoDAAC, available from the DTID (DD 1348-1A, Block 2). The 

DoDAAC in the document number may identify the activity that directed the shipment to disposal 

rather than the DoDAAC of the generator (for example, when an A5J is used to direct disposal action). 

b. SDRs citing the DLA Disposition Services Type Code T (Turn-In) will be 

sent directly to the activity responsible for the turn-in of property to the Field Office whenever 

possible. In order to ensure that electronic notification of generating customers is achieved, 

Disposition Services will provide the generator’s email address to DOD WebSDR. This email address 

will be used by DOD WebSDR for dissemination of the SDR. DSS will establish a global table to 

store generator email addresses. The generator’s email address will be captured from automated turnin web-based tools maintained by DLA Disposition Services. DSS will map the generator email 

address to the N1 loop used to identify the organization to receive the SDR (Qualifier ZD, Party to 

Receive Reports – citing the DoDAAC of the generator/activity identified by the DTID Number). The 

email address will be included in the PER segment (Qualifier CZ, Claim Recipient) identified in the 

 1 Refer to ADC 184, Redistribution Order (RDO)-based SDRs.
Attachment to ADC 459, Page 6

DLMS 842A/W.

c. Automatic distribution to DOD Component SDR applications based upon the 

existing DOD WebSDR or the Military Service of the customer will also be made either 

transactionally or via email address associated with the DoDAAC in WebSDR. Information copies 

will not be provided by DOD WebSDR for owner/manager distribution as this process is not 

applicable to turn-ins. However, DSS has the capability to identify additional distribution activities (as 

“party to receive copy”) within the SDR transaction if this is determined to be applicable. 

d. If generator email is not available, DOD WebSDR will follow standard SDR 

distribution rules by DoDAAC and Component SDR application. If the action activity DoDAAC is 

not associated with a Component application or SDR application, the SDR will be sent to an email 

account for unroutable SDRs established by DLA Disposition Services for each specific field activity. 

Using this process DLA Disposition Services will be able to monitor for any SDRs that never reached 

the intended recipient and pursue manual off-line follow-up if needed. 

e. SDRs citing the DLA Disposition Services Type Code B or E will be directed 

to the shipping activity and no information copies will be required.

2. SDRs Requiring Customer Pick-Up. When unauthorized or unacceptable 

property is turned in to the Field Office, Disposition Services personnel attempt to assign an internal 

DSS disposition status of research or reject the property. This property is then placed in a Frustrated

Property research area, and an SDR will be prepared to notify the generator to pick-up the property. If 

Disposition Services receives property where the owner is not known, or if the generator fails to 

respond to the SDR within 55 days (this is normal SDR time standard for response), or fails to pick up 

the property, the property may be mutilated and destroyed. As appropriate based upon the security and 

classification requirements of specific property, DLA Disposition Services may contact the generator 

in advance of standard SDR timeframes (which will be consistent with all host nation, Federal, State 

and local laws and regulations including DOD disposal policies). 

c. WebSDR Management Reports Selection Criteria: DOD WebSDR management reports 

for selection of SDR Document Type D and selection by DLA Disposition Services Type Code will 

need to be updated.

d. DLMS Supplement Revisions. Refer to Enclosure 4.

e. Alternatives: There are no other alternatives for this process.

5. REASON FOR CHANGE: With the addition of DLA Disposition Services business processes 

into the DSS system, data elements and transaction information need to be introduced in a DLMS 

transaction to provide the DLA Disposition Services customers a means to input, submit, receive 

information, and track transactions that they have previously entered in the DAISY system.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages (tangible/intangible): Eliminates non-DOD discrepancy process associated 

with the DRMS Form 917 without losing the capability to capture associated metrics.

b. Disadvantages: There are no disadvantages to adding the additional SDR codes to this 

transaction. No known disadvantages to revised procedures, except that SDRs reported to a DoDAAC 
Attachment to ADC 459, Page 7

will not be consolidated with SDRs reported to a corresponding RIC under the current WebSDR 

management reports tool configuration. 

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

DEVELOPMENT: Appropriate training will be provided to DLA personnel generating SDRs via 

DSS to understand use of new Document Type D and new discrepancy code procedures. DLA 

Disposition Services will need to monitor for SDRs that never reached the intended recipient when so 

notified by rejected SDR or failed SDR transmission and pursue manual off-line follow-up if needed.

8. NOTE ANY REGULATIONS OR GUIDANCE: (IF APPLICABLE): Refer to Defense 

Materiel Disposition Manual DOD 4100.21-M Chapter 3-B-2 and DRMS-I 4160.14 Section 2 Chapter 

1 and 9, Revised April 10, 2010.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: January 2012.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available.

11. IMPACT:

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

change. The existing data element for the DTID is added to the DLMS 842A/W SDR transaction.

b. Changes to DLMS Data Elements: Code value and name updates to existing data elements 

are required for: Discrepancy Report Document Type Code, DRMS SDR Type Code, Discrepancy 

Code, and SDR Action Code. Refer to Enclosures 1 and 2. 

 c. Publications: 

(1) Requires update to DLMS 842A/W and 842A/R as shown at Enclosure 4.

(2) Requires update to DOD 4000.25-M, DLMS as shown at Enclosure 6.

d. Automated Information Systems (AIS): 

(1) DLA: Impacts DSS. DLA RBI team indicated that SDRs applicable to DLA Disposition 

Services (RIC S9D) will not be recorded in DLA’s EBS.

(2) Military Service AIS: DOD Component SDR applications must be able to accept 

incoming SDRs with action activity DoDAACs and must be able to accept new discrepancy codes and 

the new action code as identified concurrent with DLA Disposition Services implementation.

(3) DOD WebSDR: 

(a) Applicable tables must be updated to include identified new code values and 

associated text changes (Enclosure 1 and Enclosure 2 (for DOD codes values only)). 

(b) Management report/query functionality must be updated to identify new Document 

Type and Disposition Services Type Code values associated with DLA Disposition Services. 
Attachment to ADC 459, Page 8

(c) DLA Disposition Services Field Offices must be recognized as new DSS sites by 

DOD WebSDR as identified in Enclosure 5.

(d) DOD WebSDR routing rules must be updated to accommodate SDRs associated 

with DLA Disposition Services Type Code T as described above (using the email address contained in 

the SDR, in addition to following standard distribution rules for the recipient). 

(e) SDRs identified by Document Type Code D shall be sent transactionally to DLA 

Field Offices. However, SDRs identified by Type Code 7 shall not be sent transactionally during 

initial deployment. Customer submission of SDRs directly to the Field Office RIC will be transmitted 

to the S9D email account.

(f) The new data element for the DTID must be accommodated, but need not be added 

to the metrics table or made available for WebSDR queries.

(g) Routable Email Distribution for Disposition Services Type T: If a generator 

email address was provided by the Field Office within the SDR transaction (PER segment with 

Qualifier CZ), and there is no email associated with the DoDAAC within the DOD WebSDR internal 

email distribution table and the Component is not supported by an SDR application, the action activity 

DoDAAC email should be suppressed. A second email SDR should not be directed to the default 

email address. 

(h) Unroutable Email Distribution for Disposition Services Type T: If a valid

generator email address is not provided within the transaction (PER segment with Qualifier CZ), and 

DOD WebSDR does not have internal email or SDR application routing rules for the SDR action 

activity, the resulting unroutable email transaction shall be directed to the DLA Disposition Services 

default email address. Personnel monitoring the default email address are responsible for further 

research for taking any appropriate action. At this time the default email address will be the S9D 

generic email.
Enclosure 1 to ADC 459, Page 1

Enclosure 1, SDR Type and Disposition Services Type Code Revisions

1. Discrepancy Report Document Type Code (Logistics Qualifier D): Revise existing DLMS 

data element Discrepancy Report Document Type Code (commonly referred to as Document Type

Code) as follows to define Document Type D for use on DLMS SDR transactions and make 

administrative updates.

Alias: Problem Type

Definition: Identifies the type of discrepant report and type of shipment involved. 

Remarks: This DLA/DOD WEB DLMS SDR data element is used to identify the type of discrepant 

report and type of shipment involved. Code list is based upon DLAH 4140.4, CDCS Handbook,

DAAS will fill the data code entry with doc 6 or doc 7 as depicted in the code list below when a code 

is not entered in the dlms supplement. Note: An ANSI data maintenance action was approved for 

implementation in version/release 5030. The approved DLMS qualifier code/name is "TDC -

Discrepancy Report Type Code". 

Source: DLAH 4140.4, CDCS Handbook and DoD 4140.25-M Defense Logistics Management 

Standards (DLMS) Manual

Available From: HQ Defense Logistics Agency 

Data Code Characteristics: Type: ID Min: 001 Max: 001 

Code Name/Definition 

NOTE: Phone calls and messages will normally be input in the appropriate hard copy document type 

format. for example, a message reporting an overage on a depot shipment would be input as a 

Document Type 7. Document Type 2 is only used when the usual hard copy reporting format cannot be 

determined. 

0 Category I Quality Deficiency Report (Not currently used in a DLMS transaction)

1 Category II QDR - SF 368, Phone Call or Message (Not currently used in a DLMS 

transaction)

2 Phone Call, Message, or Other (See Note) (Not currently used in a DLMS transaction)

3 SF 361 - Discrepancy In Shipment Report (DISREP) (Not currently used in a DLMS 

transaction)

4 DLA Quality Audit (Not currently used in a DLMS transaction)

5 DD FORM 1225 - Storage And Quality Control Report 

6 SDR - Customer Originated, Direct Vendor Delivery 

7 SDR - Customer Originated, Depot/Lateral Shipment 

Identifies a discrepant shipment resulting from a distribution depot shipment, lateral distribution (not 

under TAV rules), or other non-procurement source. 

8 SDR - Depot Originated, Depot Receipt from Non-Procurement Source (Other Than RDO) 

Used by Distribution Standard System (DSS) distribution depot. 

9 SDR - Depot Originated, Vendor Delivery To Depot Used By DSS Distribution Depot. 
Enclosure 1 to ADC 459, Page 2

A SDR - Storage Site Receipt, Customer Return/Other 

*** NOTE: Requires Authorization Prior To Use*** 

Identifies a discrepant receipt resulting from a customer return or other type receipt not specifically 

identified elsewhere. Receiving activity is a non-DSS distribution depot or the receiving activity is 

reporting a discrepant shipment of DLA-owned materiel to a Military Service activity under National 

Inventory Management Strategy (NIMS) business rules, or other authorized wholesale materiel storage 

site. This code may be processed in a manner comparable to Type 9. 

B SF 380 - Report And Processing Medical Materiel Complaints, Type I (Not currently used in a 

DLMS transaction) 

C SF 380, Report and Processing Medical Materiel Complaints, Type II (Not currently used in a 

DLMS transaction) 

D SF 380 - Report And Processing Medical Materiel Complaints, Type III 

D SDR - DLA Disposition Services Field Office originated. (Note: SDR prepared using DSS. 

Must be used in conjunction with Disposition Services Type Code to further distinguish the type of 

shipment scenario involved.)

E DD Form 1938 - Government/Industry Data Exchange Program (GIDEP) ALERT (Not 

currently used in a DLMS transaction)

F DD Form 1938 - Government/Industry Data Exchange Program (GIDEP) SAFE ALERT (Not 

currently used in a DLMS transaction)

N SDR - Storage Site Receipt, Depot Shipment (RDO) 

***NOTE: Requires Authorization Prior To Use.*** 

Identifies a discrepant receipt resulting from a distribution depot shipment to a non-DSS distribution 

depot or shipment of DLA-owned materiel to a Military Service under NIMS business rules, or other 

authorized wholesale materiel storage site. This code may be processed in a manner comparable to 

Type R. 

P SDR - Storage Site Receipt, Vendor Delivery (New Procurement) 

***NOTE: Requires Authorization Prior To Use*** 

Identifies a discrepant receipt resulting from a vendor shipment to a non-DSS distribution depot or 

shipment of DLA-owned materiel to a Military Service activity under the NIMS business rules, or 

other authorized wholesale materiel storage site. This code may be processed in a manner comparable 

to Type 9. 

R SDR - Depot Originated, Redistribution Order Receipt Used By DSS Distribution Depot 

V SDR - Customer Originated, Lateral Shipment under Total Asset Visibility (TAV) 

System assigned based upon TAV business rules. This code may be processed by the source of supply 

(SOS) in a manner comparable to type 7. 

W Transshipper Originated SDR 
Enclosure 1 to ADC 459, Page 3

2. DLA Disposition Services SDR Type Code (Logistics Qualifier ST): Revise existing DLMS 

data element DRMS SDR Type Code (commonly referred to as Disposition Services Type Code) to 

update the organization name and remove sub-types L and P and add sub-types B, E, and T, as follows:

Definition: A DLMS data element used to identify the type of DLA Disposition Services Supply 

Discrepancy Report and type of shipment involved.

Remarks: The DLA Disposition Services SDR Type Code is used as a sub-type code in conjunction 

with the SDR Document Type (DLMS Qualifier D). Codes applicable to Recycling Control Point 

(RCP) receipts input via DoD WebSDR are used with SDR Document Type Code 7. Codes 

applicable to DLA Disposition Services Field Office receipts input via Distribution Standard System 

are used with SDR Document Type Code D. 

Source: DoD 4000.25-M, Defense Logistics Management Standards (DLMS) Manual

Available from: Defense Logistics Management Standards 

Data code characteristics: Type: ID Min: 001 Max: 001 

Code Name/Definition 

The following values are applicable to SDRs prepared via the DoD WebSDR for use with 

Discrepancy Report Document Type Code 7:

D DLA Disposition Services Donated Materiel - Identifies discrepant property staged at the depot and 

released to state agency customer. 

F DLA Disposition Services Transferred Materiel - Identifies discrepant property shipped to a nonDoD federal agency customer by a distribution depot. 

L DRMS DEMIL identifies discrepant property shipped to a DEMIL Center from a distribution 

depot2

O Other DLA Disposition Services Shipment - Identifies any other discrepant DLA Disposition 

Services Field Office property shipment not applicable for identification by any other designated 

DLA Disposition Services Type Code (D, F, L , R, S, OR P)

P DRMO Submitted/Depot Shipment - identifies discrepant property shipped to a DRMO from a 

distribution depot.

3

R DLA Disposition Services Reutilization - Identifies discrepant property shipped to a DoD customer 

by a distribution depot (Applicable to Recycling Control Point (RCP) receipt).

S DLA Disposition Services Sale - Identifies discrepant property sold to a DLA Disposition Services

sales contractor and shipped by a distribution depot. 

 2 DLA Disposition Services is requesting removal of this sub-type code because discrepancies for property sent to the 

DEMIL will be entered via DSS using sub-type B. 3 DLA Disposition Services is requesting removal of this sub-type code because discrepancies for property sent to the CPC 

will be entered via DSS using sub-type B.
Enclosure 1 to ADC 459, Page 4

The following values are applicable to SDRs prepared via the Distribution Standard System for use 

with Discrepancy Report Document Type Code D4:

B Distribution Depot shipment to a DLA Disposition Services Field Office

E DLA Disposition Services Field Office Redistribution – Identifies discrepant property 

redistributed between DLA Disposition Services Field Offices

T DLA Disposition Services Field Office Turn-in – Identifies discrepant property turned in to a 

DLA Disposition Services Field Office from a generating activity

 4 WebSDR will not display Disposition Services Types B, E, T in the input selection drop box, since these are only 

authorized for DSS use.
Enclosure 2 to ADC 459, Page 1

Enclosure 2, SDR Discrepancy Code and SDR Action Code Revisions.

1. Shipping Packaging and Storage Discrepancy Code (Logistics Qualifier HA): Revise existing 

DLMS data element (commonly referred to as SDR Discrepancy Code) to add new values below. A 

user-friendly code list is available on the DOD SDR Subcommittee Web at: 

www.dla.mil/j-6/dlmso/Programs/Committees/ Supply/supplySDR.asp#sa. Applications receiving 

SDRs must have internal tables updated to recognize these codes by the RBI implementation date.

Documentation category:

D601 Hazardous Waste Profile Sheet omitted.

D602 Hazardous Waste Profile Sheet incomplete or incorrect.

D701 Hazardous Waste Manifest omitted.

D702 Hazardous Waste Manifest incomplete or incorrect

Other Discrepancies category: 

Z5 Property not authorized or not acceptable for turn-in to DLA Disposition Services.

2. SDR Requested Action Code (Logistics Qualifier HB): Revise existing DLMS data element 

(commonly referred to as SDR Action Code) to add new value 3C and administrative updates as 

follows:

Definition: Describes the type of action taken or requested applicable to a supply discrepancy reported 

on an SDR.

Remarks: Refer to DLMS discrepancy procedures.

Source: DLMS Manual 4140.25-M 

Data Code Characteristics: Type: ID Min: 002 Max: 002

Code Name/Definition 

1A Disposition instructions for discrepant materiel requested; financial action not applicable 

1B Materiel being retained 

1C Supporting supply documentation requested 

1D Materiel still required; expedite shipment. (Not applicable to Security Assistance) 

1E Local purchase materiel to be returned at supplier's expense unless disposition instructions to the 

contrary are received within 15 calendar days. (not applicable to security assistance or DLA

customers) 

1F Replacement shipment requested. (not applicable to Security Assistance) 

1G Reshipment not required. Item to be re-requisitioned 

1H No action required. Information only 

1Z Other action requested (see remarks) 

2A Disposition of materiel and financial adjustment (credit) requested 

2B Materiel being retained. Financial adjustment (debit) requested 

2C Technical documentation/data requested 
Enclosure 2 to ADC 459, Page 2

2F Materiel being held for disposition instructions, request funds citation. (Not applicable to 

Security Assistance.) 

2J Financial adjustment requested 

2K Evidence of shipment requested (Security Assistance only) 

2L Request billing status (Security Assistance only) 

2Z Additional information is being submitted off-line. (Use with electronic SDR submission only.) 

3A Transshipper (Aerial/water port or Consolidation and Containerization Point (CCP)) requests 

expedited response; shipment frustrated 

3B Discrepancy reported for corrective action and trend analysis. No reply required. 

3C Receiving activity not authorized to accept property. Pick-up by original owner required. 
Enclosure 3 to ADC 459, Page 1

Enclosure 3, DSS Discrepancy Code Cross Reference

The following new Discrepancy Codes will be made available internal to DSS to trigger specific predetermined text remarks on the outgoing SDR. The DSS internal discrepancy code will not appear on 

the SDR itself (only the DOD Discrepancy Code and the associated remarks will be provided on the 

SDR). Components receiving SDRs should not make any table updates to recognize the internally 

used code values. Staffing Note: Components were asked to review the remarks text during staffing 

to ensure that these remarks provide adequate explanation and identify any requiring clarification. No 

applicable comments were received.

DOD

SDR 

Code

Internal DSS 

Discrepancy 

Code Description of Discrepancy

D1 DA01 PROPERTY RECEIVED WITHOUT DTID (DD FORM 1348-1A)

D2 DB01 DATA ON DOCUMENT(S) IS NOT LEGIBLE OR NOT LEGIBLE ON ALL 

COPIES

D3 DC01 INSUFFICIENT COPIES OF DTID (MINIMUM 2 COPIES REQUIRED) 

D3 DC02 DOCUMENT FORMAT NOT IN ACCORDANCE WITH DOD 4000.25-1-M 

AND DOD 4160.21-M 

D3 DC03 NSN OR FSG/PART NUMBER (PN) IS MISSING OR INCORRECT (CC 8-

22) 

D3 DC04 UNIT OF ISSUE MISSING OR INCORRECT (CC 23-24) 

D3 DC05 QUANTITY MISSING. (CC 25-29) 

D3 DC06 DOCUMENT NUMBER MISSING OR INCOMPLETE (CC 30-43) 

D3 DC07 PRECIOUS METAL INDICATOR CODE MISSING (CC 62)

D3 DC08 AE IDENTIFICATION CODE MISSING (CC 63) (IF APPLICABLE) 

D3 DC09 DISPOSAL AUTHORITY CODE MISSING (CC 64) 

D3 DC10 DEMILITARIZATION CODE MISSING OR INCORRECT (CC 65)

D3 DC11 UNIT PRICE MISSING (CC 74-80) 

D3 DC12 SHIPPED FROM ADDRESS MISSING OR INCOMPLETE

D3 DC13 SHIPPED TO ADDRESS MISSING OR INCOMPLETE

D3 DC14 CATEGORY OF PROPERTY REQUIRING SPECIAL HANDLING 

MISSING OR INCORRECT

D3 DC15 EXTENDED VALUE MISSING 

D3 DC16 UNIT WEIGHT OR ESTIMATE MISSING

D3 DC17 UNIT CUBE OR ESTIMATE MISSING

D3 DC18 NOMENCLATURE MISSING

D3 DC19 "DLA DISPOSITION SERVICES USE ONLY" SECTION COMPLETED 

BY GENERATOR

D3 DC20 APPROPRIATION CITATION FOR DEPOSIT OF PROCEEDS MISSING, 

(SCRAP) 

D3 DC21 BASIC MATERIAL CONTENT MISSING OR INCORRECT (SCRAP) 

D3 DC22 ESTIMATED WEIGHT MISSING OR INCORRECT

D3 DC23 CERTIFICATIONS MISSING. EXAMPLE: AEDA, FREON, HARD DRIVE 

DISPOSITION
Enclosure 3 to ADC 459, Page 2

DOD

SDR 

Code

Internal DSS 

Discrepancy 

Code Description of Discrepancy

D3 DC24 AUTOMATION EQUIPMENT MISSING REQUIRED COPY OF SF 120 

WHICH INDICATES DOD CASE NUMBER AND/OR COPY OF DARIC 

LETTER AUTHORIZING THE WAIVING OF DARIC SCREENING

D3 DC25 ELECTRON TUBE MISSING REQUIRED CERTIFICATION ON DTID

D3 DC26 DANGEROUS PROPERTY MISSING REQUIRED INERT STATEMENT 

ON DTID

D3 DC27 LOST, ABANDONED, UNCLAIMED PRIVATELY OWNED PROPERTY 

MISSING BOARD OF OFFICERS APPOINTMENT LETTER, 

INVENTORY AND VALUE OF ITEM(S), WRITTEN FINDINGS, NAME 

OF OWNER OR "UNKNOWN" 

D3 DC28 MAGNETIC MEDIA MISSING REQUIRED CERTIFICATION OF 

UNCLASSIFIED OR DECLASSIFICATION BY THE SECURITY 

OFFICER

D3 DC29 SHELF LIFE PROPERTY NOT CORRECTLY IDENTIFIED OR MISSING 

THE EXPIRATION DATE 

D3 DC30 VEHICLE MISSING LIST AND VALUE OF MAJOR COMPONENTS 

THAT ARE MISSING OR HAVE BEEN RECLAIMED OR ONE TIME 

COST OF REPAIR (PARTS AND LABOR). VEHICLE MAINTENANCE 

RECORD

D3 DC31 INSTRUCTIONS FOR DEMILITARIZATION MUST ACCOMPANY 

TURN-IN 

D3 DC32 PROPERTY DEMILITARIZED PRIOR TO TURN-IN MISSING 

REQUIRED CERTIFICATION

D3 DC33 "FRIABLE ASBESTOS" REQUIRED IN DTID

D3 DC34 CANCELED, SUSPENDED, OR ADULTERATED PESTICIDES REQUIRE 

INFO IN BLOCK D OF DTID

D3 DC35 POLYCHLORINATED BIPHENYL (PCB) REQUIRES INDIVIDUAL LAB 

ANALYSIS OR GAS CHROMATOGRAPH ANALYSIS

D3 DC36 POLYCHLORINATED BIPHENYL (PCB) HERMETICALLY SEALED 

ITEMS SUBMITTED WITHOUT PARTS PER MILLION (PPM) 

INFORMATION MAY INCUR ADDITIONAL COST FOR DISPOSAL

D601 DG01 MISSING HAZARDOUS WASTE PROFILE SHEET

D602 DG02 HAZARDOUS WASTE PROFILE SHEET HAS DISCREPANCIES

D3 DC38 MISSING TEST RESULTS OF CHEMICAL ANALYSIS

D3 DC39 CONTAINER MISSING CERTIFICATION OF TRUE 

CONDITION/RELIABILITY

D3 DC40 DOT CONTAINER, SHIPPING NAME, HAZARD ID NO. NEEDED FOR 

OFF SITE SHIPPING

D701 DH01 HAZARDOUS WASTE MANIFEST NOT PROVIDED

D702 DH02 HAZARDOUS WASTE MANIFEST HAS DISCREPANCIES

D3 DC43 MISSING "HAZARDOUS MATERIAL" OR "HAZARDOUS WASTE" 

IDENTIFICATION (1348-1A BLOCK 27) 

D3 DC44 HAZARDOUS WASTE (HAZARDOUS WASTE) INCORRECTLY 

IDENTIFIED AS A HAZARDOUS MATERIAL (HAZARDOUS 

MATERIAL)

D3 DC45 LSN/FSC MISSING REQUIRED CHEMICAL NAME OF HAZARDOUS 

COMPONENTS/CONTAMINANTS
Enclosure 3 to ADC 459, Page 3

DOD

SDR 

Code

Internal DSS 

Discrepancy 

Code Description of Discrepancy

D3 DC46 MISSING OR INCORRECT HAZARDOUS NSN AND NOUN NAME

D3 DC47 MISSING OR INCORRECT NAME OF NON-HAZARDOUS 

CONTAMINANTS

D3 DC48 MISSING OR INCORRECT PERCENTAGE/RANGE OF 

CONTAMINANTS

D3 DC49 MISSING OR INCORRECT HAZARDOUS WASTE MILSBILLS FUND 

CODE. (CC 52-53) 

D3 DC50 MISSING OR INCORRECT HAZARDOUS WASTE BILLING DODAAC 

(1348-1A BLOCK 27)

D3 DC51 MISSING OR INCORRECT HAZARDOUS ITEM NUMBER (HIN) (1348-

1A) 

D3 DC52 MISSING OR INCORRECT HAZARDOUS WASTE TOTAL COST OF 

DISPOSAL (1348-1A) 

D3 DC53 MISSING OR INCORRECT HAZARDOUS CONTAINER 

CERTIFICATION (1348-1A) 

D3 DC54 HAZARDOUS WASTE DISPOSAL QUANTITY NOT CORRECT OR 

MISSING

D3 DC55 HAZARDOUS WASTE DISPOSAL UNIT OF ISSUE INCORRECT OR 

MISSING

D3 DC56 HAZARDOUS REMARKS SECTION IS MANDATORY (PRIOR TO 

SUBMISSION)

D3 DC57 SUPPLY CONDITION CODE MISSING OR INCORRECT (CC 71) 

H1 HA02 HAZARDOUS CONTAINER UNSAFE TO HANDLE/ WILL NOT 

WITHSTAND NORMAL HANDLING

H1 HA03 HAZARDOUS CONTAINER INADEQUATE (RUSTY, DENTED, 

OVERFILLED, BROKEN)

H1 HA04 LEAD ACID BATTERIES ARE LEAKING

H1 HA05 LEAD ACID BATTERIES LACK CAPS

H3 HC01 MISSING MATERIAL SAFETY DATA SHEET (MSDS)

Z5 ZE01 PROPERTY IS NOT RESPONSIBILITY OF THE DRMO, DOD 4160.21-M 

Z5 ZE02 RADIOACTIVE MATERIAL REQUIRES DISPOSAL IN ACCORDANCE 

WITH DLAM 4145.8/AR 700-64/NAVSUPINS 4000.34B/AFR 67-8/MCOP 

4400.105C

Z5 ZE03 PROPERTY MUST BE DEMILITARIZED PRIOR TO TRANSFER TO THE 

DISPOSITION SERVICES FIELD OFFICE

Z5 ZE04 TACTICAL PESTICIDE DISPOSAL IS THE RESPONSIBILITY OF THE 

OWNING MILITARY SERVICE

Z5 ZE05 CONFORMING STORAGE/MOST CONFORMING STORAGE IS 

UNAVAILABLE

Z5 ZE06 HAZARDOUS ITEM NOT IN ACCORDANCE WITH APPLICABLE 

REGULATORY GUIDANCE

P108 PA01 VEHICLE FUEL TANK CONTAINS MORE THAN 25% FULL OR IS 

LEAKING AND REQUIRES REPAIR OR DRAINING

P108 PA02 VEHICLE OR EQUIPMENT LEAKING FLUIDS AND REQUIRES 

DRAINING

P212 PB10 SAFE OR LOCKABLE CONTAINER IS NOT EMPTY OR UNLOCKED 

COMBINATION LOCK HAS NOT BEEN RESET TO 50-25-50 AND 

MARKED OR TAGGED 
Enclosure 3 to ADC 459, Page 4

DOD

SDR 

Code

Internal DSS 

Discrepancy 

Code Description of Discrepancy

P209 PB01 LAB PACK PROCEDURES FACILITATING TURN-IN OF SMALL 

QUANTITY CHEMICALS (LESS THAN 1 GALLON OR 7 POUNDS IN 

WEIGHT) NOT FOLLOWED

P209 PB02 ASBESTOS, FRIABLE - NOT PACKAGED TO MEET DOT STANDARDS.

P209 PB03 THERMAL BATTERIES IMPROPERLY PACKAGED

P209 PB04 MERCURY BATTERIES IMPROPERLY PACKAGED

P209 PB05 LITHIUM BATTERIES IMPROPERLY PACKAGED

P209 PB06 COMPRESSED GAS CYLINDERS MUST BE PREPARED IN 

ACCORDANCE WITH DLAR 4145.25/AR 700-68/NAVSUPINST 

4440.128C/AFR 67-12 MMCO 10330.2C

P209 PB07 POLYCHLORINATED BIPHENYL (PCB) ITEM MUST BE ENCLOSED, 

NON LEAKING AND SAFE TO HANDLE

P209 PB08 LIQUID PCB MUST BE PACKED MEETING DOT SPECIFICATIONS 

REFERENCE 40 CFR 716.65. ITEM MUST BE MARKED AS REQUIRED 

BY EPA IN 40 CFR 761.40 

P209 PB09 LEAD ACID BATTERIES ARE NOT PROPERLY PALLETIZED

P302 PC01 PESTICIDE CONTAINER IS IMPROPERLY LABELED
Enclosure 4 to ADC 459, Page 1

Enclosure 4, DLMS Supplement Revisions.

1. Revise DS 842A/W, Standard Supply Discrepancy Report (SDR), Follow-up, Correction, 

Cancellation, & Reconsideration Request, as follows:

# Location Change Table for 

DS 842A/W SDR

Reason

1. DLMS 

Introductory 

Note

Add ADC 459 to Introductory note 

- ADC 459, DLMS Transactions, Discrepancy Codes, SDR 

Type/Disposition Services Type Codes, and Associated Procedures 

to Support Supply Discrepancy Reports (SDRs) under Reutilization 

Business Integration (RBI)

To identify DLMS 

changes included 

in the DS

2. 1/PER01/1700 Revise DLMS Notes as shown:

CZ Claim Recipient

DLMS Note:

Use to identify the recipient of the SDR report or follow-on action 

transmitted by email. WebSDR will make email distribution of the 

SDR transaction to any party identified as a claim recipient. If both 

qualifiers CZ and ES are used, CZ will be considered the primary 

recipient and ES will be considered the alternate/backup recipient. 

(May be used with any 1/N101 addressee.) Refer to ADC 187 and 

ADC 459.

ES Electronic Submission Recipient

DLMS Note:

Use to identify the recipient of the SDR report or follow-on action 

transmitted by email. WebSDR will make email distribution of the 

SDR transaction to any party identified as an electronic submission 

recipient. If both qualifiers CZ and ES are used, CZ will be 

considered the primary recipient and ES will be considered the 

alternate/backup recipient. (May be used with any 1/N101 

addressee.) Refer to ADC 187.

Expands usage for 

RBI for email 

distribution of the 

SDR.

Administrative 

revision to add 

previous 

applicable ADC 

number for 

documentation 

purposes.
Enclosure 4 to ADC 459, Page 2

# Location Change Table for 

DS 842A/W SDR

Reason

3. 2/REF04-

01/0700

Add new code as shown:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the controlling document number for 

the transaction cited in REF01 code TN. 

2. The DTID number is used by DLA Disposition Services as a 

unique number to identify property that was turned into a DLA 

Disposition Service Field Office. The value of the DTID may be the 

original turn-in document number or may be a unique control 

number (UCN) assigned by the Field Office during receipt 

processing when the original DTID number is not adequate to 

uniquely identify the property. Applicable on the SDR for intraDLA use when the controlling document number for the shipment 

is not the DTID used for tracking the property. Refer to ADC 459.

Allows for a cross 

reference to the 

DTID.
Enclosure 4 to ADC 459, Page 3

# Location Change Table for 

DS 842A/W SDR

Reason

4. 2/LQ01/1050 Revise DLMS notes as shown:

D Court Document Type Code

DLMS Note:

1. Must use to identify the Discrepancy Report Document Type Code 

(also known as Problem Type). This is a DLA/DoD WebSDR data 

element used to identify the type of discrepancy report and type of

shipment involved. This data element is required for the DoD 

WebSDR interface.

2. Valid entries are for SDR types are:

• 6 - Customer originated, direct vendor delivery:

This type is used primarily for shipment of requisitioned materiel 

sourced by the item manger by contracted vendor shipment rather 

than from stock.

• 7 - Customer originated, depot/lateral shipment:

This type is used primarily for shipment of requisitioned materiel 

sourced by the item manager from

stock; may be used for other customer SDRs.

• V - Customer originated, lateral shipment under TAV: This type is 

used exclusively for customer reported discrepancies resulting from 

item manager directed lateral redistribution (initiated via MILSTRIP 

DIC Code A4_ with Distribution Code 2 or 3).

• 8 - Depot originated, depot receipt from non-procurement source 

(other than RDO)

• A - Storage site receipt, customer return/other (Note: Comparable to

Type 8, but originated outside DSS; requires authorization prior to 

use.)

• 9 - Depot originated, vendor delivery to depot

• D - DLA Distribution Field Office originated (Note: Used in 

conjunction with Disposition Services SDR Type Code to further 

distinguish the type of shipment scenario involved.)

• P - Storage site receipt, vendor delivery (new procurement) (Note: 

Comparable to Type 9, but originated outside DSS; requires 

authorization prior to use.)

• R - Depot originated, redistribution order receipt

• N - Storage site receipt, depot shipment (RDO) (Note: Comparable 

to Type R, but originated outside DSS; requires authorization prior to 

use.

• W - Transshipper originated SDR: This type is used exclusively by 

ports and CCPs for discrepancies discovered while materiel is 

intransit. Because this type of SDR may apply to a shipment unit 

(rather than a single document number), data element requirements 

different significantly from other SDR types.

3. For future consideration, a data maintenance action was approved 

in version 5030. The approved code/name is "TDC - Discrepancy 

Report Type Code".

Supports RBI –

allows for distinct 

identification of 

SDRs associated 

with DLA 

Disposition 

Services generated 

via DSS.
Enclosure 4 to ADC 459, Page 4

# Location Change Table for 

DS 842A/W SDR

Reason

5. 2/LQ01/1050 Revise DLMS Notes as shown:

ST Special Marketing Type Code

DLMS Note:

1. Use to identify the DRMS DLA Disposition Services SDR Type 

Code. This is a DLA/DoD WebSDR data element used to identify the 

type of discrepant report and type of shipment involved.

2. For SDRs prepared via DoD WebSDR for Recycling Control 

Point (RCP) receipts, this data element is used in conjunction with 

SDR Document Type Code 7:

 D - DLA Disposition Services Donated Materiel

 R - DLA Disposition Services Reutilization

 F - DLA Disposition Services Transferred Materiel

 S - DLA Disposition Services Sale

 L - DLA Disposition Services DEMIL

 P - DLA Disposition Services Field Office submitted, depot RCP

shipment

 O - Other DLA Disposition Services Shipment

3. For SDRs prepared via Distribution Standard System for DLA 

Disposition Field Office receipts, this data element is used in 

conjunction with SDR Document Type Code D. 

 T DLA Disposition Services Field Office Turn-in

 E DLA Disposition Services Field Office Redistribution

 B Distribution Depot shipment to a DLA Disposition Services 

Field Office

 

4. Refer to ADC 210 and ADC 459.

Supports RBI 

requirements to 

distinctly identify 

different scenarios 

related to DLA 

Disposition 

Services

2. Revise DS 842A/R, SDR Reply, as follows:

Item 

#

Location Change Table for 

DS 842A/R SDR

Reason

1. DLMS 

Introductory 

Note

Add ADC 459 to Introductory note 

- ADC 459, Supply Discrepancy Reporting (SDR) DLMS 

Transactions, Discrepancy Codes, DLA Disposition Services 

Type Codes, and Associated Procedures to Support Directed 

Discrepancy Reporting under Reutilization Business 

Integration (RBI)

To identify DLMS 

changes included 

in the DS
Enclosure 4 to ADC 459, Page 5

Item 

#

Location Change Table for 

DS 842A/R SDR

Reason

2. 2/LQ01/1050 Revise DLMS Notes as shown:

ST Special Marketing Type Code

DLMS Note:

1. Use to identify the DRMS DLA Disposition Services SDR 

Type Code. This is a DLA/DoD WebSDR data element used to 

identify the type of discrepant report and type of shipment 

involved in conjunction with the applicable SDR Document 

Type Code.

2. For SDRs prepared via DoD WebSDR for Recycling 

Control Point (RCP) receipts, this data element is used in 

conjunction with SDR Document Type Code 7: 

 D - DLA Disposition Services Donated Materiel

 R - DLA Disposition Services Reutilization

 F - DLA Disposition Services Transferred Materiel

 S - DLA Disposition Services Sale

 L - DRMO DEMIL

 P - DRMO submitted, depot RCP shipment

 O - Other DLA Disposition Services Shipment

3. For SDRs prepared via Distribution Standard System for 

DLA Disposition Field Office receipts, this data element is 

used in conjunction with SDR Document Type Code D: 

T - DLA Disposition Services Field Office Turn-in 

E - DLA Disposition Services Field Office Redistribution 

B - Distribution Depot shipment to a DLA Disposition Services 

Field Office

4. Refer to ADC 210 and ADC 459.

Supports RBI 
Enclosure 5 to ADC 459, Page 1

Enclosure 5, DLA Disposition Field Service Office DoDAACs/RICs

DAISY Site Name DODAAC

DAISY 

RIC+Suffix

New 

RIC New Site Name

Albany SYB124 SWMB SWL DLA DS Albany

Al Asad SG4420 SQ6C SQD DLA DS Al Asad

Anniston SY2054 SWEZ SWE DLA DS Anniston

Anniston CDC SYD184 SWED SW9 DLA DS Anniston CDC

Anaconda SG4410 SQ5B SU0 DLA DS Anaconda

Anchorage SZ362D SZVA SZV DLA DS Anchorage

Benning SY2124 SWMR SWM DLA DS Benning

Bliss SZB037 SZSC SZ0 DLA DS Bliss

Arifjan SG4310 SQ6A SQ6 DLA DS Kuwait

Campbell SYE434 SXVA/SXVR SXV DLA DS Campbell

Bagram SG4450 SQ5D SUI DLA DS Bagram

Bahrain SG4330 SQ6B SQH DLA DS Bahrain

Barstow SZ3129 SYMA SYM DLA DS Barstow

Columbus SX1465 SVXA SVX DLA DS Columbus

Columbus CPC SXV465 SVXV SV2 DLA DS Columbus CPC

Columbus LTS SXH465 SVXH SV3 DLA DS Columbus LTS

Corpus Christi SZ3637 SY6C SYE DLA DS Corpus Christi

Camp Victory SG4430 SQ5F SUK DLA DS Camp Victory

Crane SX1395 SVQR SVQ DLA DS Crane

Cannon SZB047 SZAC SXX DLA DS Cannon

Crane CDC SXE395 SVQE SV4 DLA DS Crane CDC

Duluth SXD455 SVKD SV5 DLA DS Duluth

Colorado Springs SZ3038 SYCA SYP DLA DS Colorado Springs

Dyess SZC557 SZ7C SZB DLA DS Dyess

Ellsworth SZ3108 SYKR SYI DLA DS Ellsworth

Forest Park SYF164 SWRF SWO DLA DS Forest Park

Gordon SYG164 SZQH SZH DLA DS Gordon

Great Lakes SXG345 SVKG SV6 DLA DS Great Lakes

Hood SZ3557 SZ7R SZ7 DLA DS Hood

Huntsville SYC054 SWEC SWQ DLA DS Huntsville

Huntsville CPC SYV054 SWEV SWY DLA DS Huntsville CPC

Knox SY2434 SXVK SXK DLA DS Knox

Leonard Wood SZ3536 SVKL S81 DLA DS Leonard Wood

Little Rock SZE407 SZ7L SZD DLA DS Little Rock

McAlester CDC SZB487 SY3B SYL DLA DS McAlester CDC

McConnell SZM586 SY4M S82 DLA DS McConnell

Emirates SG4360 SQ6E SQ7 DLA DS Emirates

Fairbanks SZ363D SZVF SZJ DLA DS Fairbanks

Fairchild SZD380 SZPD SZK DLA DS Fairchild
Enclosure 5 to ADC 459, Page 2

Minot SZ3708 SZ4A SZ4 DLA DS Minot

Offutt SZF586 SYKF SYO DLA DS Offutt

Oklahoma City SZ3487 SY3A SY3 DLA DS Oklahoma City

Polk SZ3717 SZ3A SZ3 DLA DS Polk

Great Falls SZ3718 SZ6A SZ6 DLA DS Great Falls

Riley SZR586 SY4R SY4 DLA DS Riley

Rock Island SX1345 SVKR SVK DLA DS Rock Island

Guam SH520C SSBA SSB DLA DS Guam

San Antonio SZ3547 SY6A SY6 DLA DS San Antonio

Hawaii SH510C SSAA SSA DLA DS Pearl Harbor

Hill SZ3028 SYBA SYB DLA DS Hill

Holloman SZ3037 SZAR SZA DLA DS Holloman

Scott SZS535 SVKC SV7 DLA DS Scott

Selfridge SXS465 SVXS SX0 DLA DS Selfridge

Sill SZ3707 SZ2A SZ2 DLA DS Sill

Sparta SX1705 ST8A ST8 DLA DS Sparta

Texarkana SZ3587 SY5A SY5 DLA DS RED RIVER

Iwakuni SHE400 SSEE SS2 DLA DS Iwakuni

Valdosta #N/A SWRV S83 DLA DS Valdosta

Warner Robins SY2164 SWRR SWR DLA DS Warner Robins

Whiteman SZW536 SVKW S84 DLA DS Whiteman

Wright-Patterson SXP465 SVXP SY8 DLA DS Wright-Patterson

Aberdeen SXC213 STWC STI DLA DS Aberdeen

Kandahar SG4470 SQ5G SUL DLA DS Kandahar

Bragg SY2714 SZ9A SZ9 DLA DS Bragg

Buchanan SY2652 SXGR SXC DLA DS Buchanan

Kirtland SZ3047 SZAK SZN DLA DS Kirtland

Cape Canaveral SY2354 SXGS SXE DLA DS Cape Canaveral

Korea (A'PO) SHK500 SSJK SSJ DLA DS Korea

Cherry Point SY2724 SZYA SZX DLA DS Cherry Point

Leatherneck SG4480 SQ5H SUM DLA DS Leatherneck

Drum SXD102 SVED SVI DLA DS Drum

Eglin SYE364 SXGF/SZ1A SZ1 DLA DS Eglin

Groton SXG041 STHG SXZ DLA DS Groton

Lewis SZ3380 SZPA SZP DLA DS Lewis

Guantanamo SYG313 SXGG SXI DLA DS Guantanamo

Homestead SY2304 SXGH SXJ DLA DS Homestead

Jackson SYJ194 SZQJ SZI DLA DS Jackson

Jacksonville SY2314 SXGA SXG DLA DS Jacksonville

Keesler SY2184 SWEK S85 DLA DS Keesler

Alpha SGC050 SQEC SQI DLA DS Alpha

Lejeune SYL024 SZQR SQZ DLA DS Lejune

Misawa SHD400 SSED SS4 DLA DS Misawa

Aviano SGP180 SQUP SQJ DLA DS Aviano
Enclosure 5 to ADC 459, Page 3

Mountain Home SZC020 SYBC SYQ DLA DS Mountain Home

Djibouti SG4370 SQ6F SQ0 DLA DS Djibouti

Nellis SZN129 SYMN SYW DLA DS Nellis

Germersheim SGG110 SQGG SQK DLA DS Germersheim

Grafenwoehr SGG120 SQGD SQO DLA DS Grafenwoehr

Letterkenny SXX293 SVEX SVL DLA DS Letterkenny

Okinawa SH5700 SSTA SST DLA DS Okinawa

Meade SX1213 STWA STW DLA DS Meade

Pacific CPC SHV400 SSEV SS5 DLA DS Pacific CPC

Pendleton SZP199 SYUP SYX DLA DS Pendleton

Incirlik SG4220 SQYA SQY DLA DS Incirlik

Mechanicsburg SX1293 SVEA SVE DLA DS Susquehanna

Port Hueneme SZ3189 SYTR SYT DLA DS Port Hueneme

Kaiserslautern SG4070 SQGA SQG DLA DS Kaiserslautern

Qatar SG4340 SQ6C SUN DLA DS Qatar

Kaiserslautern CDC SGT070 SQGT SQP DLA DS Kaiserslautern CDC

Kaiserslautern CPC SGV070 SQGV SQQ DLA DS Kaiserslautern CPC

Norfolk SX1493 ST1A ST1 DLA DS Norfolk

Norfolk CPC SXV493 ST1V SWI DLA DS Norfolk CPC

Kastel SG4050 SQEA SQE DLA DS Kastel

Lajes SGL260 SQ3L SQ2 DLA DS Lajes

Sagami SH5400 SSEA SSE DLA DS Sagami

Pensacola SY2364 SXGE S86 DLA DS Pensacola

San Diego SZ3199 SYUG SYU DLA DS San Diego

Livorno SG4180 SQUA SQU DLA DS Livorno

Portsmouth SX1081 STHZ STH DLA DS Portsmouth-Pease

Richmond SX1523 ST4A ST4 DLA DS Richmond

Sierra SZS319 SZCS SZO DLA DS Sierra

Molesworth SG4010 SQAA SQA DLA DS Molesworth

Rucker SYD124 SXGD SXO DLA DS Rucker

St Juliens SXG493 ST1J SVO DLA DS St. Juliens Creek

Speicher SG4460 SQ5E SUO DLA DS Speicher

Naples SGN180 SQUN SQR DLA DS Naples

Rota SG4260 SQ3A SQ3 DLA DS Rota

Stockton SZ3279 SZCA SZC DLA DS Stockton

Stockton CPC SZV319 SZCV SZU DLA DS Stockton CPC

Schweinfurt SGS120 SQGE SQT DLA DS Schweinfurt

Stewart SYS164 SWRS SXY DLA DS Stewart

Thailand SHB700 SSTB SS6 DLA DS Bangkok

Sigonella SGS180 SQUS SQX DLA DS Sigonella

Travis SZH279 SZCH SVN DLA DS Travis

Tucson SZ3419 SZSA SZS DLA DS Tucson

Tucson CDC SZD429 SZSD SZW DLA DS Tucson CDC

Twenty-nine Palms SZD129 SYMD SYY DLA DS Twenty-nine Palms
Enclosure 5 to ADC 459, Page 4

Tampa SYT354 SXGT SXT DLA DS Tampa

Vandenberg SZF189 SZCF SVR DLA DS Vandenberg

Vicenza SGV180 SQUV SUP DLA DS Vincenza

Tobyhanna SXT303 SVCT SVC DLA DS Tobyhanna

DEMAN Site SYG054 SWEG S80 #N/A

RCP SC4402 S9W* S9W

Yuma SZY429 SYUY SYZ DLA DS Yuma
Enclosure 6 to ADC 459, Page 1

Enclosure 6, DLMS Manual Revisions

Revise DLMS Manual, DOD 4000.25-M, Volume II, Chapter 17 and Chapter 16 as shown.

Chapter 17, Supply Discrepancy Reporting:

1. Revise text: C17.3.7. Reutilization and Marketing Shipment DLA Disposition Services 

Discrepancies

2. Add a new subparagraph:

C17.3.7.3. DLA Disposition Services and DLA Disposition Field Office SDR 

Procedures. During the receiving process, if the DLA Disposition Services Field Office 

identifies a supply discrepancy, an outgoing SDR will be generated consistent with Chapter 16, 

paragraph C16.7. 

Chapter 16, DLA Disposition Services:

Add a new section on SDRs using the following paragraphs as C16.7.

C16.7. Supply Discrepancy Reporting. Supply Discrepancy Reports (SDRs) and associated 

responses will be reported via the Disposition Services Field Office system or DOD WebSDR, 

using the DLMS 842A/W (Standard Supply Discrepancy Report (SDR), Follow-up, 

Correction, Cancellation, & Reconsideration Request) for the initial SDR and the 842A/R 

(Standard Supply Discrepancy Report (SDR) Reply) for the reply. Discrepancies may be 

identified in shipments between the DLA Distribution Depot and the DLA Disposition Services 

Field Office, between two DLA Disposition Services Field Offices, and between the Field 

Office and the generating customer, as well as between Distribution Depots and customers for 

Recycling Control Point (RCP) directed shipments. The SDR may be reported by the receiving 

Field Office or by the receiving customer.

C16.7.1. Outgoing SDR. During the receiving process, if the DLA Disposition 

Services Field Office identifies a supply discrepancy, an SDR will be generated via the Field 

Office system using Document Type Code D in conjunction with the appropriate SDR 

Disposition Services Type Code to distinguish the source of discrepant shipment (Generating 

Activity Turn-In = T, DLA Distribution Depot = B, and Redistribution between Field Offices = 

E). 

C16.7.1.1. Discrepancy Codes. The Disposition Services Field Office will 

describe the type of discrepant condition, in most instances using unique discrepancy codes 

within their internal system. For external DoD processing, these unique codes trigger specific 

remarks for the outgoing SDR, but the code itself will not be perpetuated. Instead, the 

associated standard DoD discrepancy code value will be used for distribution of the SDR thus 

allowing the internal codes to remain available in the Field Office system for metrics and 

managements reports. Unique DLA Disposition Services discrepant conditions, such as the 

turn-in of unauthorized property, or lack of specific documentation for hazardous 

materiel/hazardous waste may be identified by the applicable Shipping, Packaging, and 

Storage Discrepancy Code. 
Enclosure 6 to ADC 459, Page 2

C16.7.1.2. Action Codes. The DLA Disposition Services Field Office shall 

indicate the applicable action taken or requested on the SDR. When the generator turns in 

property that cannot be accepted by the Field Office, the Field Office shall prepare an SDR

using SDR Requested Action Code 3C, indicating pick-up of unauthorized or unacceptable 

property is required. 

C16.7.1.3. Primary/Secondary Document Numbers. The outgoing SDR may 

require communication of two document numbers. The following rules apply:

C16.7.1.3.1. Property Turned in by Generating Activity. The value used 

for the DTID/Suffix by the customer will be the primary document number identified in the 

SDR. If a Unique Control Number (UCN) was established by the Field Office upon receipt, it 

will not be perpetuated on the SDR.

C16.7.1.3.2. Property Shipped by the DLA Distribution Depot to the 

DLA Disposition Services Field Office. The document number used to ship the property will be 

the primary document number identified in the SDR. No secondary document number is 

applicable.

C16.7.1.3.3. Redistribution of Property between Disposition Services 

Field Offices. The redistribution document number will be the primary document number 

identified in the SDR. The DTID used by DLA Disposition Services to track materiel will be 

perpetuated in the SDR and will be available to the receiving Field Office in both the DLMS 

856S, Shipment Status and the DLMS 527D, PMR. 

C16.7.2. RCP SDRs Prepared via DOD WebSDR. DLA Disposition Services RCP 

personnel will receive and process discrepancies for property shipped by the DLA Distribution 

Depots to various customers. RCP personnel will log in to WebSDR to create and submit 

SDRs on behalf of the customer using Document Type Code 7 and the related DLA 

Disposition Services SDR Type Code to distinguish customer type, as follows:

• D = DLA Disposition Services Donated Materiel – Identifies discrepant 

property staged at the depot and released to a state agency customer.

• F = DLA Disposition Services Transferred Materiel – Identifies 

discrepant property shipped to a non-DOD federal agency customer by a distribution depot.

• O = Other DLA Disposition Services Shipment – Identifies any other 

discrepant DLA Disposition Services Field Office property shipment not applicable for

identification by any other designated Disposition Services Type Code.

• R = DLA Disposition Services Reutilization – Identifies discrepant 

property shipped to a DOD customer by a distribution depot (applicable to RCP receipt).

• S = DLA Disposition Services Sale – Identifies discrepant property sold 

to a DLA Disposition Services sales contractor and shipped by a distribution depot.

C16.7.3. Incoming Customer SDRs: SDRs addressed to DLA Disposition Services 

(RIC S9D) or RCP (RIC S9W) will be supported by conversion to email via DOD WebSDR. 

RCP SDRs will be processed in accordance with paragraph C16.7.2. The generic email 
Enclosure 6 to ADC 459, Page 3

address for S9D will be associated with all the DLA Disposition Services Field Offices for 

Document Type 7 SDR only, allowing customer generated SDRs to be forwarded to DLA 

Disposition Services. Replies will be created in DoD WebSDR. Incoming Customer SDRs will 

not be sent to the DLA Disposition Services ICP system. 

C16.7.4. Distribution of Document Type Code D SDRs Generated During the 

Receiving Process at the DLA Disposition Services Field Office.

C16.7.4.1. SDRs resulting from discrepant turn-ins will be directed to the

shipping activity DoDAAC (also known as the generator) identified on the turn-in document 

(DD 1348-1A, Block 2). 

C16.7.4.2. SDRs citing DLA Disposition Services SDR Type Code T will be sent 

directly to the activity responsible for the turn-in of property whenever possible. In order to 

ensure electronic notification of generating activity, DLA Disposition Services will provide the 

generator’s email address to DoD WebSDR. This email address will be used by WebSDR for 

dissemination of the SDR.

C16.7.4.2.1. Generator Email Address. The Disposition Services Field 

Office system will establish a global table to store generator email addresses. The generator’s 

email address will be captured from automated turn-in web-based tools maintained by DLA 

Disposition Services. The Field Office system will map the generator email address as 

indicated by the DLMS Supplement 842A/W. DoD WebSDR shall use this email address for 

distribution to the identified address in addition to any other applicable distribution business 

rules.

C16.7.4.2.2. DoD Component Distribution. The SDR will automatically 

be sent to SDR applications based upon the existing DoD WebSDR or the Military Service of 

the customer either transactionally or via email address associated with the DoDAAC in 

WebSDR. DLA Disposition Services shall monitor for SDRs that never reached the intended 

recipient when so notified by rejected SDR or failed SDR transmission and pursue manual 

off-line follow-up if needed.

C16.7.4.3. SDRs citing the DLA Disposition Services SDR Type Code B or E. 

SDRs with Type Code = B or E will be directed to the shipping activity and no information 

copies required.

C16.7.5. Property Requiring Customer Pick-Up. When unauthorized or unacceptable 

property is turned in to the Field Office, property will be placed in a Frustrated Property 

research area and an SDR prepared with the Discrepancy Code Z5 and Action Code 3C to 

notify the generator to pick-up the property. If the Field Office received property where the 

owner is not known or if the generator fails to respond to the SDR within 55 days or fails to 

pick up the property, the property may be mutilated and/or destroyed, consistent with 

Demilitarization Code requirements, local policies, laws, and regulations. As appropriate 

based upon the security and classification requirements of specific property, DLA Disposition 

Services may contact the generator in advance of the 55 day SDR time standard (which is 
Enclosure 6 to ADC 459, Page 4

consistent with all host nation, Federal, State, and local laws and regulations including DoD

disposal policies). 
Enclosure 7 to ADC 459, Page 1

Enclosure 7, Response to PDC Staffing

Originator Response/Comment Disposition

1. Navy The Navy concurs with comment Noted.

NAVSUP SDR (NSDRS) Team comments: The 

proposed implementation date is Jan 2012, which is 

also that date NSDRS is supposed to migrate to 

PDREP. If the latter date slips past 1/2012, 

NSDRS will need to make a few additions to the 

database to accommodate the unlikely event that 

this type of SDR would flow to NSDRS. I can 

only assume that PDREP will need to make the 

same additions to their database.

1. Ensure that all of the Discrepancy Report 

Document Type Codes used in DLMS transactions 

are in the SDRT_DOC_TYPE table and that 

PDREP incorporates all of these as well.

2. Ensure that the new Action Codes and 

Discrepancy Codes are added to 

MATERIAL_ACTION_CODE and 

MATERIAL_DISCREPANCY_CODE 

respectively.

Action Code:

3C Receiving activity not authorized to accept 

property. Pick-up by original owner required.

Discrepancy Codes:

D601 Hazardous Waste Profile Sheet omitted.

D602 Hazardous Waste Profile Sheet incomplete or 

incorrect.

D701 Hazardous Waste Manifest omitted.

D702 Hazardous Waste Manifest incomplete or 

incorrect

Z5 Property not authorized or not acceptable for 

turn-in to DLA Disposition Services.

3. The DLA Disposition Services SDR Type Code 

will simply be ignored in the XML and will not be 

propagated back to WebSDR.

Noted.

1-2. The expectation is that DLA 

Disposition Services Field Offices 

will identify Navy turn-in activities 

as the intended recipient of the 

SDR. Therefore, these new values 

for Document Type, Discrepancy 

Code, and Action Code, must be 

recognized by Navy SDR systems.

3. It is acceptable if the DLA 

Disposition Services SDR Type 

code is not perpetuated to the SDR 

reply (since it will be noted in the 

source system).

PDREP SDR Team (NAVSEALOGCENDET 

Portsmouth) comments: PDREP agrees with 

NSDRS. We concur with PDC 454 as written and 

have no additional comments, changes or 

See above.
Enclosure 7 to ADC 459, Page 2

Originator Response/Comment Disposition

amendments.

2. Army HQDA DCS G-44(S) concurs with proposed 

change.

There is a "Potential Impact" with GCSS-Army as 

the SDR process discussed in this PDC is critical to 

DOL mission that GCSS-Army subsumes as part of 

the

GCSS-Army mission in upcoming work streams 

and future deployments of the system.

The Navy comments and response 

are applicable to the Army as well. 

See above. This change impacts 

Army Logistics Modernization 

Program (LMP) SDR processing as 

well as GCSS-Army.

3. Marine Corps This Headquarters has reviewed the subject PDC 

and concurs as written.

Refer to response above for Navy 

PDREP.

4. DLA DLA concurs provided the below issues from our 

SDR POCs are addressed:

1. Page 4 references a new Action Code 3C. I want 

to ensure this is only available for use by RBI. If 

use isn't restricted people will try to use it on SDRs 

being directed to other places and it will cause 

failure in systems that aren't set up to accept it. 

2. Also, on Pg. 4 it states "DLA Disposition 

Services Incoming Customer SDRs are not required 

to be sent to EBS." We would like to see this 

worded "...will not be sent to EBS." And have a 

filter in WebSDR to prevent them from being sent 

to EBS. EBS is not set up to receive an SDR w/ 

Type D. Any strays directed to SMS would fall on 

the floor and require manual processing.

3. Need clarification on the definition of 

"generator". 

4. The position is that under no circumstance will 

the ICP accept any SDR from Field Office. If there 

is a discrepancy of a shipment from the depot to 

Field Office, under no circumstance will Field 

Office or the depot try and forward that SDR on to 

the ICP for action."

Noted.

1. All Component applications will 

be required to recognize Action 

Code 3C. Its use is currently 

restricted to DLA Disposition 

Services, but future SDR process 

enhancements may consider use of 

this code.

2. Updated.

3. The generator is the activity 

turning in property to DLA 

Disposition Services. Language 

has been updated in the ADC to 

make this clear.

4. The business rules for depot and 

Field Office generated SDRs do not 

include sending action or 

information transactions to the ICP. 

DoD WebSDR will distribute the 

SDR according to the information 

provided by the Field Office. 

5. Air Force If this section of the PDC is to be incorporated into 

DOD4000.25-M, respectfully request that “DLA 

Distribution Services Field Offices” is changed to 

“DLA Disposition Services Field Offices” 

Rationale: DLA Disposition Services Field Offices 

is in line with the content of the document. 

All updates to the office name have 

been made.
Enclosure 7 to ADC 459, Page 3

Originator Response/Comment Disposition

If this section of the PDC is to be incorporated into 

DOD400.25-M, respectfully request that “for 

example, e when” is change to “for example, when” 

Rationale: “e” appears to be a typographical error.

Fixed.

Request additional information regarding SDRs 

resulting from discrepant turn-ins. See staffing 

note in Yellow.

Rationale: Current example provided needs 

additional clarification as does not appear to be 

conveyed.

This ADC attempts to provide 

sufficient clarification of planned 

procedures. Specific questions may 

be addressed to the SDR System 

Administrator. 

No impact; ECSS does not currently use the 842A 

transaction in release 1.

Noted.

If PDC 454 requires software changes to the D035 

Stock Control System (SCS), the proposed 

implementation date of Jan 2012 cannot be met. 

Software change requirements documents (CSRDs) 

must go through AFMC and Air Staff requirements 

boards for approval as well as through the National 

Defense Authorization Act (NDAA) workload 

approval process before any development workload 

can be put on contract. 

The future impact for the Air Force 

SDR system will be applicable to

Integrated Logistics SupportSupply (ILS-S) Enterprise SolutionSupply (ES-S). This system 

maintains a two-way 

communication with DOD 

WebSDR for AF-generated SDRs, 

does not currently accept incoming 

SDR transactions prepared by 

outside sources. A system upgrade 

will be required to accept DLA 

Disposition Services SDRs and 

others.

6. USTRANSCOM Abstain Noted.