ADC 425 Attachment Page 1

ADC 425

Revised SDR Codes and Procedures including Incorrect Part Number 

Discrepancy Codes and DoD WebSDR Data Edits and Forwarding Enhancements

1. ORIGINATOR:

a. Originator (for Discrepancy Code W8 and removal of double mapping for unidentifiable 

stock numbers): Defense Logistics Agency (DLA), Sub-Process Owner SDR Process, 614-692-

4631; DSN 850-4631

b. Originator: DoD SDR Administrator, Ms. Ellen Hilert, e-mail: ellen.hilert@dla.mil 

2. FUNCTIONAL AREA: Primary: Supply/DoD WebSDR

3. PROPOSED CHANGE:

a. This change establishes/documents enhanced procedures for improving data integrity and

facilitating proper identification of activities and communication of information.

(1) DoD WebSDR will attempt to populate the transactional SDRs with the correct 

owner/manager and shipping activity using logic comparable to that currently applied to webentered SDR automatic pre-fill.

(2) DoD WebSDR will establish edits to prevent user misidentification of DLA 

Distribution Depots and Consolidation and Containerization Points (CCPs) as the 

owner/manager on both web-input and transactional SDRs.

(3) DoD WebSDR will establish edits to prevent user misidentification of owner/managers 

as shipping activities on both web-input and transactional SDRs.

(4) A new disposition/reply code will be made available to reject SDRs that cannot be 

routed electronically. 

(5) DoD WebSDR will permit identification of the responding activity as other than the 

original action activity via direct web input when Disposition/Reply Code 504 is used to forward 

an SDR to a new action activity.

b. This change replaces existing Discrepancy Code T8, Incorrect Part Number, with two new

Discrepancy Codes. Discrepancy Code W7 will be assigned for identification of a part number 

that is unmatched to cataloging data/Federal Logistics Data (FED LOG). Discrepancy Code W8 

will be assigned for identification of a part number not associated with the NSN received. Under 

the W-series discrepancy codes, inclusion of discrete data elements to identify the incorrect (or 

wrong) item received becomes mandatory.

c. This change harmonizes data content associated with incorrect item identification among 

DoD Component SDR applications and DoD WebSDR. This change also documents DoD 
ADC 425 Attachment Page 2

WebSDR procedures for mediating the differences related to incorrect item reporting among the 

various Component SDR applications.

 d. Background: 

 (1) The majority of the changes described in this ADC were previously staffed under PDC 

403, but have been segregated so that these changes can move forward as approved changes 

without further delay. The remaining process changes contained in PDC 403 will be updated 

based upon comments received during staffing and will be re-staffed as PDC 403A. The 

transition of the Discrepancy Code T8 to W8 was discussed during multiple SDR conference 

calls. It was agreed during the SDR Committee Meeting 11-1 that the code change should be 

incorporated in this ADC. Code W7 was added to make a distinction between a wrong part 

number being associated with a national stock number (NSN) and a part number that cannot be 

matched to catalog data. 

 (2) DoD WebSDR does not currently have capability to identify the “From” activity on an 

SDR reply as an activity other than the originally intended action activity. This causes confusion 

when an authorized responder from another organization employs a Disposition/Reply Code 504 

to forward an SDR to a new action activity, e.g. the DoD SDR Administrator or the designated 

DoD Component representative attempting to forward an SDR that could not be transmitted to 

the original action activity identified by the submitter. Not all SDRs submitted via DoD 

WebSDR or Component SDR applications can be forwarded electronically to the designated 

action activity. This happens for several reasons, most often it occurs because the SDR is 

directed by the submitter to an activity that is not supported by an SDR interface or the intended 

action is not appropriate under DoD/Component business rules. DoD WebSDR reply screens 

must be updated to expand the information requested when Disposition/Reply Code 504 is 

selected. 

(3) Discrepancy Code T8, Incorrect Part Number, was established under the T-series 

which identifies discrepancies associated with technical data markings (name plates, log books, 

operating handbooks, special instructions). The T-series discrepancies use a combination of the 

discrepancy code and narrative remarks to explain the discrepancy. Use of the T-series for a 

customer complaint about receiving the wrong part number is misleading and doesn’t support the 

data requirements of the action activity for discrete identification of the part received. Selection 

of a W-series discrepancy code associated with incorrect (wrong) items requires the user to 

provide the necessary detail about the wrong item received. The additional information is 

necessary so that the action activity will be able to research and provide an accurate and timely 

disposition.
ADC 425 Attachment Page 3

4. Detailed Procedures

a. Enhanced DoD WebSDR Procedures for Identification of Relevant Organizations. 

(1) DoD WebSDR will attempt to populate the transactional SDRs with the correct 

owner/manager and shipping activity, using existing rules applied to WebSDR-entered pre-fill 

logic. DoD Component SDR applications are encouraged to perform pre-fill for internal 

Service/Agency users under modernization or where direct interface/integration with a 

Component ERP is feasible. DoD Component SDR applications are encouraged to perform up 

front edits for appropriate data input. The following procedures apply to SDRs transactions:

(a) DoD WebSDR will attempt to populate the shipping activity when blank.

(b) DoD WebSDR will replace or blank out the shipping activity when identified as 

the Owner/Manager. For the purposes of this edit, the values listed in Enclosure 3 as 

Owner/Managers will be used to block inappropriate use as a shipping activity.

(c) DoD WebSDR will attempt to populate the owner/manager when blank.

(d) DoD WebSDR will replace or blank out the owner/manager when identified as a 

DLA Distribution Depot. For the purposes of this edit, the values listed in Enclosure 3 as 

distribution depots and CCPs will be used to block inappropriate use as an owner/manager. If the 

value used for the owner/manager in transactional SDRs is provided by the user, it will be edited 

against the list of depot/CCP values. If a Distribution Depot is identified as the owner/manager, 

it will be moved to/overlay the shipping activity field. If a CCP is identified, it will only be 

moved to the shipper field if no other value is provided (because the original shipping depot,

when available, is preferable to identification of the CCP). 

(2) On-line DoD WebSDR users identifying a DLA Distribution Depots or CCP as the 

owner/manager will receive notification that the activity identified is not valid for use as the 

owner/manager. The customer will be required to correct the input prior to proceeding.

(3) On-line DoD WebSDR users identifying an owner/manager as a shipping activity 

will receive notification that the activity identified is not valid for use as the shipping activity. 

The customer will be required to correct the input prior to proceeding. The user will, however, 

be given the option of proceeding with a blank entry if shipping activity is unknown or the

appropriate code is not available.

b. Enhanced DoD WebSDR Forwarding Capability. Upon selecting Disposition/Reply 

Code 504, SDR forwarded to new action activity as shown, DoD WebSDR currently will prompt 

the web user to identify the RIC-To for the new action activity and will now allow optional input 

of a new RIC-From for the reply transaction. The capability to identify a new responding activity 

when forwarding a SDR to a new action activity will allow the resulting SDR reply to 

appropriately identify this activity (rather than perpetuating the original action activity to the 

reply as the responding activity). Although this capability is already available to DoD 

Component SDR applications, web input is not as flexible (by original intent) when creating the 

SDR reply. The identification of the responding activity is necessary for WebSDR users since 

SDRs that are transmitted to the incorrect action activity by the submitter may be forwarded by 

support personnel from different offices. DoD WebSDR must ensure that the new RIC-From is 
ADC 425 Attachment Page 4

consistent with the Service/Agency of the user (if feasible, this option to identify a new RICFrom should be restricted to users with an unrestricted/ Component wide user access role). If the 

user attempts to designate a RIC associated with a Service/Agency other than his/her own, an 

error notification will be provided. Note: If the SDR is forwarded via the 504 process by the 

SDR System Administrator’s office, the DLA Transaction Services Routing Identifier SGA will 

be used for the reply. 

c. New Disposition/Reply Code 941. If research is unable to determine a more appropriate 

routing for an incorrectly routed SDR, a new reject reply code is needed to return the SDR to the 

submitter for resubmission to a different action activity. Note: Rejection of the incorrectly 

routed SDR is not the preferred alternative and should only be used when all attempts by the 

responsible activity to research and re-route the SDR have failed. A new disposition/reply code 

will be established as follows:

941 SDR failed during processing. SDR cannot be transmitted electronically to the 

designated action activity. 

When Disposition/Reply Code 941 is selected via WebSDR, the following text will be autopopulated in the remarks field (over-ride/editing of remarks will be allowed): Your SDR failed 

to reach the intended recipient. Please research for alternative/corrected action activity 

identification. For example, re-direct to the source of supply, rather than the shipping activity

or other relevant organization. Resubmit your SDR as a new (not corrected) SDR. If an 

alternative action activity cannot be identified for resubmission, contact your Service/Agency 

SDR representative for guidance.

d. New Discrepancy Codes and Procedures for Part Number Discrepancies

(1) SDR submitters will report receipt of a part numbers which is unmatched to cataloging 

data or an incorrect part number for the NSN received using new Discrepancy Code W7 and W8, 

respectively. Component SDR applications and DoD WebSDR must require that the item 

received be properly identified using discrete data elements (vice remarks text). 

(2) During development of this ADC it became apparent that disconnects among planned 

and implemented incorrect item identification were causing numerous miscommunications and 

transaction failures resulting in unresolved SDRs and extensive manual intervention. In order to 

better align DLMS requirements with existing system requirements, DLMS data requirements 

and guidance are revised and clarified by this ADC. Refer to Enclosure 4 for a stratification of 

data requirements by application. Incorrect item (including unmatched part number)

identification data requirements for W-series discrepancies are as follows:

(a) Item Identification: Wrong Item NSN, and/or Wrong Item Part Number/

Commercial and Government Entity (CAGE) Code, and/or Wrong Item Description. 

Wrong item identification is required input. If the user does not know the NSN or part number, 

the SDR application must require the designation of “UNKNOWN” in the part number data 

field. Note 1: If the part number is populated, DoD WebSDR will edit transactions and direct 

web-input to ensure that the CAGE Code is also populated. If the CAGE is left blank by the 

submitter/submitting system, DoD WebSDR will populate the CAGE with all zeros (“00000”). 

Note 2: If the description is populated, the NSN or part number must also be filled. DoD 
ADC 425 Attachment Page 5

WebSDR will fill the part number field with “UNKNOWN” if left blank by the submitter. 

Additionally, due to inability to implementation this field in the near term within the DLA 

Enterprise Business System, to which a high volume of these discrepancies are reported, when 

the SDR is directed to Routing Identifier SMS and the part number and description are 

populated, DoD WebSDR will repeat the description at the end of the user-provided remarks 

text. It will be introduced by: “Item Description:” 

(b) Incorrect Item Manufacturer's Name. This field is currently considered 

optional for use when the CAGE Code is not known, but a manufacturer’s name is available. 

Note 1: Due to limited implementation of this capability within Component applications, DoD 

WebSDR will repeat the manufacturer’s name at the end of the user-provided remarks text. It 

will be introduced by: “Wrong Item Manufacturer:” Note 2: Component SDR applications 

must be enhanced when feasible to provide capability to submit and receive wrong item 

manufacturer’s name.

(c) Incorrect Item Quantity Received and Unit of Issue (UI) (required)

(d) Incorrect Item Supply Condition Code (SCC) (recommended)

(e) Incorrect Item Controlled Inventory Item Code (CIIC) (recommended)

(f) Incorrect Demilitarization (DEMIL) Code (recommended)

(g) Incorrect Item Manager (optional)

(3) SDR Discrepancy Code Revisions. 

(a) Revise narrative associated with Discrepancy Code T8 as follows:

TECHNICAL DATA MARKINGS (NAME PLATES, LOG BOOKS, 

OPERATING HANDBOOKS, SPECIAL INSTRUCTIONS)

T1 Technical data markings missing.

T2 Technical data markings illegible or mutilated.

T3 Precautionary operational markings missing.

T4 Inspection data missing or incomplete.

T5 Serviceability operating data missing or incomplete.

T6 Warranty data missing.

T7 Missing part number on bare item.

T8 Incorrect part number Discrepancy Code discontinued; see W7 and W8.

T9 Operating handbooks, log books, and/or special instructions missing.

(b) Add new Discrepancy Codes W7 and W8 as follows: 

INCORRECT ITEM

W1 Incorrect item received.

W2 Unacceptable substitute received.
ADC 425 Attachment Page 6

W3 Incorrect item received, but not identifiable to an NSN or part number.

W4 Misidentified item received.

W5 Mixed stock received.

W6 Incorrect item discovered upon opening a sealed vendor's pack. Not applicable to 

Security Assistance.

W7 Part number unmatched to FEDLOG/FLIS

W8 Incorrect part number for NSN received

(4) Implementation Procedures for Discrepancy Codes W7 and W8:

(a) As of November 15, 2011, the values W7 and W8 will be authorized and DLA 

Transaction Services will update WebSDR input screens to remove T8 and add W7/W8. 

Selection of W7 and W8 will trigger display of the additional screen for wrong item 

identification. As soon as possible, WebSDR pre-fill (when available) will be modified to 

identify the source of supply that directed shipment as the action activity (rather than the 

shipping activity).

(b) WebSDR Report Selection Criteria will be updated to add W7 and W8. User 

selection of SDRs by W-series will include existing T8 SDRs. This will maintain visibility of 

existing SDRs in WebSDR reports. 

(c) Beginning November 15, 2011 (or as soon as automated rejection capability is 

available), DoD WebSDR will stop accepting Discrepancy Code T8 (due to the lack of 

associated data elements). Transactions containing T8 will be subject to rejection due inclusion 

of an invalid discrepancy code.

(5) Reporting of Mixed Stock Receipts (Discrepancy Code W5). The original DLMS 

requirement for SDRs included capability to identify multiple wrong items received under a 

single document number using discrete data elements. As a result, DoD WebSDR and the Air 

Force Security Assistance Command (AFSAC) SDR-Automation (SDR-A) make two iterations 

of wrong item information available on input screens; however, this capability was not 

implemented by any action activity applications. To remove an opportunity for 

miscommunication, DoD WebSDR will remove visibility of this capability for the second 

occurrence. AFSAC is requested to take appropriate action. The DLMS manual guidance will 

clarify that only one incorrect item is to be identified by discrete data elements and the remarks 

text must be used to clarify shipment contents for mixed stock receipts. See Enclosure 1. The 

DLMS Supplement 842A/W will be revised to reserve this capability for future enhancement. 

See Enclosure 2. 

(6) Materiel Identification Mapping Change. When SDRs are created using DoD 

WebSDR and the automated pre-fill for materiel identification pulled from Defense Automatic 

Addressing System (DAAS) history does not conform to minimal edits for a valid NSN (not 

equal to13 positions and all numeric), WebSDR will map the value as a generic stock number 

using the ZZ qualifier. Note: DoD WebSDR will discontinue the current practice of repeating 

non-national stock number (NSN) values using a dual mapping technique whereby the same 

value is mapped to the FS, National Stock Number, and the ZZ, Mutually Defined, data fields. 
ADC 425 Attachment Page 7

(7) Alternatives: Establish one new Discrepancy Code W8 to replace T8 and use for 

both incorrect and unmatched part number discrepancies.

5. REASON FOR CHANGE:

 a. Use of the requested new Disposition/Reply Code will facilitate capture of appropriate 

metrics and improve communication between SDR submitters and action activities. 

 b. The capability to identify the responding activity as other than the initial action activity 

when using Disposition/Reply Code 504 is necessary because this forwarding action is often 

used by other parties when an SDR fails to reach the original action activity. When this happens, 

the SDR still appears to have been forwarded by the original activity which can be confusing to 

the customer (since the SDR never reached the original action activity).

 c. Customer SDRs for incorrect part number frequently neglect to sufficiently identify the 

detail associated with the item received. Switching the discrepancy code to the W-series is a 

relatively simple fix since the programming to support wrong item identification in a standard 

format is already required for the W-series. Use of discrete data elements ensures 

standardization and ease of use for customer and action activity. (Note: This change was 

originated by DLA to improve reporting requirements and reduce the number of failed 

transactions submitted to the Enterprise Business System (EBS) that must be worked manually.)

 d. Identification of stock numbers as NSNs when they value does not conform to basic NSN 

edits causes the transaction to fail in DLA EBS and requires manual update for reprocessing. 

(Note: The double mapping was originally requested by DLA for EBS processing, but is no 

longer considered appropriate and DLA has asked that this practice be terminated and stock 

numbers that do not conform to business rules be transmitted using the ZZ qualifier only.)

 e. Use of inappropriate or invalid identification of various organizations applicable to SDR 

reporting impedes preparation of management reports and may prevent processing of some

SDRs.

 f. Incomplete DLMS implementation among Component applications leads to 

miscommunication and unnecessary manual effort. DoD WebSDR can be enhanced to mediate 

between submitting and receiving applications.

6. ADVANTAGES AND DISADVANTAGES:

 a. Advantages: Reduces processing time of SDRs because pertinent data on wrong material 

received is contained in the SDR. Improves data integrity by blocking invalid or inappropriate 

activity identification. Improves WebSDR data mapping for stock numbers presumed to be valid 

but identified using wrong qualifier. Increases the flexibility and usability of DoD WebSDR.

 b. Disadvantages: When DAAS history is used to pre-populate an SDR, the original 

qualifier used for the stock number is no longer available for perpetuation to the DLMS 842A/W 

transaction. Without the original qualifier stock numbers cannot always be properly interpreted 

and may be passed using the ZZ, Mutually Defined, rather than a more appropriate code value.
ADC 425 Attachment Page 8

7. TIME LINE/IMPLEMENTATION TARGET: New Disposition/Reply Code 941 and new 

Discrepancy Codes W7 and W8 are authorized for use as of November 15, 2011. The preferred 

implementation date for new procedures and WebSDR processing is within 6 months of this ADC.

8. IMPACT:

a. Publications: Requires update to DOD 4000.25-M, DLMS, Volume 2 (see Enclosure 1).

b. Automated Information Systems (AIS): Component SDR applications accept/apply new

code values established in this change as of November 15, 2001. Component applications must be 

upgraded to support full DLMS data content for phased implementation.

c. Training: DLA Distribution and Components shall provide training to ensure users are

aware of the approved incorrect item reporting guidance.

d. DoD WebSDR: Refer to detailed requirements above to include the following:

• Enhance the forwarding to new action activity process (Disposition/Reply Code 

504) to include identification of a new Routing Identifier-From as a high priority 

change. 

• Remove visibility for on-line users of second iteration of discrete data elements for 

incorrect item information. Note: Original program logic should be reserved to 

keep this option available for future consideration.

• Allow DoD WebSDR user selection of new Disposition Reply Code 941 (with predetermined text) for expedited implementation November 15, 2011. 

• Revise Discrepancy Code T8 text (and prevent further use); add new Discrepancy 

Codes W7 and W8 for expedited implementation November 15, 2011.

• Populate incorrect item information with zero-filled (“00000”) CAGE Code value 

and part number “UNKNOWN” when required due to missing content, as a high 

priority change.

• Map incorrect item manufacturer name and description to remarks text when 

populated on SDRs sent to DLA EBS.

• Revise mapping of stock numbers which do not pass NSN edits and remove double 

mapping of the value found in DAAS history.

e. DLMS Data. No new DLMS data elements are established. Discrepancy and 

Disposition/Reply Code revisions are identified above. 

f. Missing Component Data Content. A separate review of component capability to identify 

missing components by discrete data content is recommended as follow-on action.
Enclosure 1, DLMS Manual

Page 1

Enclosure 1, SDR Procedures, DLMS Manual, Chapter 17 Revisions

DoD 4000.25-M, Volume 2

(as revised by published ADCs)

Revise as follows and renumber subsequent paragraphs.

C17.3.2.10. Technical Data. Report missing and/or incomplete item technical 

information, e.g., name plate, operating handbook, logbook, precautionary markings, warranty 

data, engineering drawings and associated lists, specifications, standards process sheets, 

manuals, technical reports, catalog item identifications, and related information that are missing, 

illegible, incomplete and/or incorrect regardless of dollar value. When reparables are returned 

and the appropriate historical information/documentation, operator/maintenance logbooks, 

engine oil analysis, etc., as required by Government regulations, and/or technical manuals are not 

included, the receiving activity shall submit an SDR regardless of dollar value. Any additional 

costs incurred by the repairing depot/arsenal because of the missing data shall be charged to the 

originating activity. Submitter will ensure that the specific description of what documentation is 

missing is included in the remarks section. Report as an incorrect part number when technical 

data markings for the part number appear to be inconsistent with the specified NSN. Incorrect 

part discrepancies shall be submitted directly to the item manager. (Do not use to report an 

incorrect item received as described below. Refer to W-series discrepancy codes for most 

appropriate discrepancy code.)

C17.3.2.11. Incorrect Item

C17.3.2.11.1. Report incorrect or misidentified materiel or unacceptable 

substitutes regardless of dollar value. However, unless the requisition contains an appropriate 

advice code in accordance with Chapter 4, limiting the request to a specific item, automatic 

shipment of an interchangeable or substitute item is allowed by policy. See I&S guidance above. 

Report wrong item receipts of controlled inventory, arms, arms parts, and explosives within 24 

hours.

C17.3.2.11.2. Incorrect item discrepancies discovered while opening a sealed 

vendor pack shall be reported regardless of dollar value or shipper. These reports must contain 

the contract number from the packaging and, if available, the lot number and the original 

document number. A constructed document number will be provided when the original number 

is not known. When using a constructed document number in an SDR, include fund code and 

credit-to/bill-to DoDAAC to ensure that credit/billing is appropriate. When known, include 

identity of the incorrect item received in the discrepancy report.

C17.3.2.11.3. Report part number discrepancies when the part number 

marking appears to be inconsistent with the specified NSN. This includes when the part 

number received is not associated with the applicable NSN or when the part number cannot be 

matched to FLIS catalog data/FEDLOG. The SDR must include the part number and 

manufacturer’s CAGE Code for the item received. Part discrepancies shall be submitted 

directly to the item manager. 
Enclosure 1, DLMS Manual

Page 2

C17.3.2.11.4 DoD WebSDR requires identification of the incorrect item 

received using discrete data elements (refer to the DLMS Supplement 842A/W). If multiple 

incorrect items are received under the same document number, use the appropriate 

discrepancy code for mixed stock and identify the first (highest quantity or controlled item) 

and use the remarks text to explain the mixed content shipment.

---------------

C17.3.21. DAAS SDR Processing

---------------

C17.3.21.1.2. Edit SDR transactions in accordance with business rules specified 

below. Additionally, DoD WebSDR will edit SDRs to improve data consistency and the 

appropriateness of data content as follows:

C17.3.21.1.2.1 The owner/manager may not be identified by a routing 

identifier associated with a Distribution Depot or a CCP as identified by the SDR 

System Administrator. 

C17.3.21.1.2. 2 The shipping activity may not be identified by the routing 

identifier associated with an inventory control point/item manager as identified by the 

SDR System Administrator. 

C17.3.21.1.2.3 Inappropriate entries will be overlaid with the correct 

value, if available, from DAAS history.1

1Refer to ADC 425.
Enclosure 2, DLMS Manual

Page 1

Enclosure 2, DLMS Supplement Revisions

# Location CHANGE TABLE for 

DS 842A/W Standard SDR

Reason

1. DLMS 

Introductory 

Note

Add ADC 425 to Introductory note 

ADC) 425, Revised SDR Codes and Procedures 

including Incorrect Part Number Discrepancy Codes 

and DoD WebSDR Data Edits and Forwarding 

Enhancements

To identify DLMS changes 

included in the DS

2. 2/LIN04/0200 Revise the DLMS note as follows:

ZZ Mutually Defined

DLMS Note:

Use to identify material by an unspecified stock 

number. This field is used administratively by DoD

WebSDR when the originating system or original 

order contained materiel identification that does not

meet standard edits for a valid NSN. when the 

primary materiel identification indicates an NSN 

(qualifier FS). The original information will be 

perpetuated and the value repeated using the ZZ 

qualifier.

Corrects DAAS mapping as 

requested by DLA. This 

change terminates 

transmission of the materiel 

identification under two 

qualifiers. If the stock 

number pulled from DAAS 

history cannot be interpreted 

as an NSN it will be mapped 

to the ZZ, Mutually Defined, 

as the primary value with no 

secondary value. 

3. 2/NCD03/2300 Revise the DLMS note as follows:

Assigned Identification

DLMS Note:

1. Use as a counter to satisfy ANSI syntax. Cite 

numeric 1 EXCEPT where additional NCD loops are 

used to report multiple incorrect (wrong) items or

missing component parts or when providing unique 

identification of discrepant items. In these instances, 

Increase incrementally by 1 for each wrong item,

missing component, or uniquely identified item 

identified. 

2. Use of this looping structure to describe multiple 

incorrect items received in association with 

Discrepancy Code W5, Mixed Stock, is reserved for 

future implementation.

Removes usage to identify 

multiple incorrect items

using discrete data elements

pending future 

implementation.
Enclosure 2, DLMS Manual

Page 2

# Location CHANGE TABLE for 

DS 842A/W Standard SDR

Reason

4. 2/REF01/2600

XA Substitute National Stock Number

DLMS Note:

1. Use to identify the incorrect (wrong) item received 

by NSN. If description is provided, include in REF03.

If multiple incorrect items are received under a 

single document number (Discrepancy Code W5), 

identify the first item and use the remarks text to 

clarify shipment contents.

2. For XA: WebSDR field length = 13

XB Substitute Manufacturer's Part Number

DLMS Note:

1. Use to identify the incorrect (wrong) item received 

by part number. If neither part number nor the NSN 

are identified enter the word "UNKNOWN" as the 

reference information field (REF02) and provide a 

description of the item in REF03. When a value is 

passed in the part number field, also include the 

manufacture’s CAGE Code (2/N101/2800, Qualifier 

SU). 

2. If multiple incorrect items are received under a 

single document number (Discrepancy Code W5), 

identify the first item and use the remarks text to 

clarify shipment contents.

3. For XB: WebSDR field length = 32

A description is not 

necessary or appropriate 

when an NSN is provided.

Provides guidance for mixed 

stock shipments

Provides guidance for 

inclusion of the CAGE code 

and for mixed stock

shipments.

5. 2/N101/2800 Revise the DLMS note as follows:

SU Supplier/Manufacturer

DLMS Note:

1. Use with REF01 XB to identify the name or CAGE 

code of the manufacturer of the incorrect (wrong) item 

received. This is a mandatory entry associated with 

the part number field incorrect. CAGE value may be 

zero-filled to satisfy application edit rules.

2. For SU: WebSDR field length = 5 for CAGE; 20 if 

clear text is used.

Supports Component 

application requirements to 

have the CAGE code data 

field populated when used 

with a part number entry.
Enclosure 3

Page 1

Enclosure 3, Distribution Depot, CCP, and Inventory Control Point/Item Manager Values

The following values may not be used to identify the materiel owner/manager on SDRs. This list 

may not be definitive and may be updated over time. Updates may be provided to the DoD SDR 

System Administrator.

DEPOT RIC 

Albany SDA

Anniston BA4

Barstow SG2

Cherry Point SDH

Columbus SCC, SCE, SCG, SCI, SCM, SCT, SCS

Corpus Christi B52

Germersheirm SDQ

Guam SCN

Hill SDT

Jacksonville SDM, SHV

Kandahar SFW

Korea S5J

Kuwait II SE7

Mapping Activity SAH

Norfolk SDF

Oklahoma SDU

Okinawa SNJ

Pearl Harbor SCJ

Puget SEB

Red River BR4

Richmond SRR, SCR, SRE, SRG, SRI, SRM, SRT, SRS, SR3 

San Diego SDX

San Joaquin AQ5, SPB

Sasebo SCH

Sigonella SLM

Susquehanna AN5, SNC, SNE, SNG, SNI, SNM, SNT, SNS, SN5, SA2

Tobyhanna BY6, SDC

Warner Robins SDD

Yokosuka SCF

CCPs

Susquehanna SAW

San Joaquin SBV

Warner Robbins SLF
Enclosure 3

Page 2

The following values may not be used to identify the materiel shipping activities in DoD 

WebSDR. This list is not definitive and may be updated over time. Updates may be provided to 

the DoD SDR System Administrator.

DLA:

SMS

Army:

AKZ, A12, A35, AJ2, B14, B16, B17, B46, B64, B69, AJ2

Navy:

NRP, N32, N35, N65, NMZ 

Air Force:

FGB, FGZ, FHB, FHZ, FLB, FLZ 

Marine Corps:

MPB

General Services Administration:

GSA
Enclosure 4

Page 1

Enclosure 4, Incorrect Item Data Stratification by System

The tables below stratify the incorrect item data elements identified as distinct data fields in DoD 

WebSDR, Component applications, and DLMS transactions. This ADC includes selected 

enhancements to mediate some gaps in implementation status. Components are requested to 

address deficiencies in the systems identified or their modernization programs. 

Incorrect Item Data Content

System1 NSN

CAGE 

Code

Part

No.

Part No. 

Description

Manufacturer’s

Name 

Quantity 

Received2 SCC UI CIIC DEMIL

Wrong 

Item 

Manager

DLMS Field 

Length: (13) (5) (32) (80) (20) (7) (1) (2) (1) (1) (3)

WebSDR Y Y Y Y Y Y Y Y Y3 Y4

EBS Y Y Y Y Y Y

NSDRS Y Y Y Y Y Y

PDREP Y Y Y Y Y

ISDR5 Y Y Y Y Y Y Y Y

ADRS6 Y Y Y Y Y Y Y Y

VISS Y Y Y

ES-S Y Y Y Y Y Y Y Y

SDR-A Y Y Y Y Y Y Y Y

Army WBT7 Y Y Y8

LMP Y Y Y

 1 Systems:

DoD WebSDR

DLA Enterprise Business System (EBS)

Navy SDR System (NSDRS)

Product Data Reporting and Evaluation Program (PDREP)

DLA Distribution Standard System Incoming SDR (ISDR) System DLA Distribution Standard System 

Automated Discrepancy Reporting System (ADRS) 

GSA Virtual Information Service System (VISS) 

Air Force Enterprise Solution-Supply 

Air Force Security Assistance Command (AFSAC) SDR Application (SDR-A)

Army Web-Based Tool (WBT)

Army Logistics Modernization Program (LMP) 2 This a separate data field from the discrepant quantity received. It would be applicable to the specific incorrect 

item identified (which could be only a portion of the total discrepant quantity, particularly if multiple iterations of 

wrong item information were provided).

3 Not shown on screens, but populated in transactions based upon cataloged NSN 4 Not shown on screens, but populated in transactions based upon cataloged NSN 5 ISDR receives incoming SDRs from customers receiving depot shipments 6 ADRS prepares outgoing SDRs for depot receipts

7 Army WBT is supported by one-way UDF for new SDRs; where data fields are not available, WebSDR maps 

contents to remarks 

8 Description and other remarks
Enclosure 4

Page 2

DLMS Supplements

Transactions8 NSN

CAGE 

Code

Part

No.

Part No. 

Description

Manufacturer’s

Name 

Quantity 

Received SCC UI CIIC DEMIL

Wrong 

Item 

Manager

DLMS Field 

Length: (13) (5) (32) (80) (20) (7) (1) (2) (1) (1) (3)

842A/W Y Y Y Y Y Y Y Y Y Y

842A/R Y Y Y Y Y Y Y

 8 Transactions:

DLMS 842A/W = SDR Report, Follow-up, Correction, Cancellation, & Reconsideration Request

DLMS 842 A/R = SDR Reply