DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

September 27, 2017

MEMORANDUM FOR SUPPLY DISCREPANCY REPORT (SDR) PROCESS REVIEW 

COMMITTEE (PRC) MEMBERS

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

1217, WebSDR Process Enhancement for Source of Supply Disposition Response 

to Storage Activity on Customer-Initiated SDRs (SDR/Supply)

The attached change to DLM 4000.25, Defense Logistics Management Standards, is 

approved for implementation. Reply code value updates are scheduled for implementation March 

2018. Refer to the attachment for joint and staggered implementation target dates.

Addressees may direct questions to Ms. Ellen Hilert, DOD SDR System Administrator, or 

Mr. Ben Breen, SDR Alternate, e-mail DLMSSDR@dla.mil. All others must contact their 

Component designated Supply PRC representative or SDR PRC representative available at: 

http://www.dla.mil/HQ/InformationOperations/DLMS/DLMSPrograms/sdr/. 

 

HEIDI M. DAVEREDE

Program Manager 

Enterprise Business Standards Office

Attachment

As stated

cc: 

ODASD (SCI)
Attachment, ADC 1217

Page 1

Attachment to ADC 1217

WebSDR Process Enhancement for Source of Supply Disposition Response to 

Storage Activity on Customer-Initiated SDRs

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Ellen Hilert, DOD SDR System Administrator, DLMS Program Office, e-mail: 

ellen.hilert@dla.mil

b. Ben Breen, DOD SDR System Alternate, DLMS Program Office, email: 

benjamin.breen@dla.mil

2. FUNCTIONAL AREA:

a. Primary Functional Area: Supply Discrepancy Reporting (SDR)

b. Secondary Functional Process: SDR Disposition 

3. REFERENCES:

a. Defense Logistics Manual (DLM) 4000.25, Defense Logistics Management Standards 

(DLMS), Volume 2, Chapter 17, Supply Discrepancy Reporting

b. ADC 1160, Procedures for Recommending and Authorizing Credit for Validated 

SDRs, Associated Reply Code Revisions, and Required use of the Reason for Reversal Code in 

Issue Reversals, January 19, 2016 

c. ADC 1126, Revised SDR Routing Rules for Non-Manager Owned Suspended Stock 

Identified at Time of Receipt at DLA Distribution Centers and Improved Identification of Owner 

and Manager on SDR Transactions, dated January 13, 2015

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change establishes new procedures for directing 

disposition instructions to storage activities subsequent to storage activity reply and closure of 

the SDR within the storage activity SDR system. The new procedures will cause the source of 

supply response to trigger reopening of the SDR in the storage activity system so that the source 

of supply can communicate disposition instructions (e.g., request for issue reversal or inventory 

adjustment) to the storage activity systemically, thus providing an audit history for the resulting

action.

b. Background: Under current procedures for customer SDRs (Document Type 7), the 

submitter normally directs their SDR to the storage activity, such as a DLA Distribution Center, 

which shipped the materiel. This is applicable to most discrepancy scenarios and for the 

Services and DLA, but is not applicable to Army-directed DLA Distribution Center shipments. 

(currently, customers generally submit Army-directed shipment SDRs directly to the source of 

supply.) The storage activity reviews the SDR and investigates the reported discrepancy. The 

storage activity prepares a response, and transmits it concurrently to the submitter and source of 

supply (normally the item manager). The storage activity’s transmission of the outgoing reply 
Attachment, ADC 1217

Page 2

will normally close the SDR in the storage activity system, (e.g., DLA’s Distribution Standard 

System (DSS) Incoming SDR (ISDR)), since that activity’s open action has been completed. If

the storage activity cannot resolve the discrepancy or provide an appropriate recommendation to 

the source of supply, the storage activity forwards the SDR to the source of supply for action. 

The current SDR transaction flow does not accommodate the source of supply returning

disposition instructions to the storage activity via SDR reply after the storage activity has 

responded. The source of supply will direct their reply to the submitting customer; there is no 

forwarding process that returns the SDR to storage activity while retaining visibility of the reply

remarks. The source of supply must communicate off-line with the storage activity when 

necessary. 

c. The new process requested in this change is modeled after an existing forwarding 

process. Action activities use the existing forwarding process by identifying the new action 

activity in an SDR reply using Reply Code 504 (SDR forwarded to new action activity as 

shown). The source of supply often applies this forwarding technique when the submitter directs 

an SDR to the source of supply bypassing the storage activity. In response to the source of 

supply’s forwarding reply containing Reply Code 504, WebSDR generates a new original SDR 

for the storage activity that does not include the source of supply remarks from the forwarding 

reply transaction informing the customer that the SDR was forwarded.

d. Approved Change in Detail: Green highlighting identifies substantive revisions 

subsequent to staffing.

(1) Update SDR guidance, DOD WebSDR, and Component SDR systems to 

allow a reply from the source of supply containing disposition instructions for the storage 

activity to be returned to the previous action activity with a copy to the submitting customer. To 

accomplish this, the SDR reply (Transaction Set Purpose Code 11) must identify the previous

action activity by routing identifier code (RIC) as the “Transfer-To” activity. WebSDR will 

recognize all addresses in the transaction and make appropriate distribution based upon inclusion 

of the SDR reply code associated with this requirement. 

Staffing Note: A separate DLMS change is currently in development to authorize the use of a 

DOD activity address code (DoDAAC) in forwarding actions such as this and other SDR 

procedures. 

(2) Establish two new disposition reply codes to identify the reason for reopening 

SDRs at the storage activity. Activities will use new Reply Code 526 when the source of supply 

wants the storage activity to provide credit by reversing the original issue. New Reply Code 527 

is more generic and is provided to satisfy any other conditions requiring return of an SDR to the 

storage activity for additional action. Activities may use these codes in conjunction with other 

SDR reply codes including codes directing customer return of discrepant materiel. Standard 

procedures for this scenario apply (see Reference 3.b.). The new codes will be established in the 

500-series for interim reply series as follows:

526 Credit authorized; issue reversal requested.

527 SDR returned to storage/initial action activity for action; see remarks.

(3) The storage activity system (e.g. DSS) must reopen the SDR upon receipt of 

the incoming source of supply reply. The storage activity will respond as appropriate to the 

requested disposition instructions and provide a reply addressed to the customer (current 

functionality in DSS). The new reply will include Reply Code 151 (Replacement/revised 
Attachment, ADC 1217

Page 3

disposition/status; prior response is superseded). WebSDR will provide a copy of the storage 

activity reply to the source of supply (current functionality in WebSDR).

(4) If the storage activity is unable to complete the disposition, the storage 

activity will forward the SDR back to the source of supply using the applicable 300-series 

forwarding reply code. In addition, this change establishes a new reply code to recognize 

systemically when a storage activity responds that it is unable to perform the issue reversal (e.g.,

due to aged records no longer being available). The storage activity will use remarks to explain 

the reason it is unable to act upon the source of supply instructions and must include the 

applicable 300-series forwarding reply to return the SDR to the source of supply for final reply. 

The new code will be established in the 500-series for interim reply series as follows:

530 Storage activity unable to perform requested issue reversal; see remarks.

Staffing Note: This change establishes new procedures to open a systemic/transactional 

communication path between the source of supply and the initial action activity. These 

procedures do not modify existing DLA Distribution guidance for determining eligibility of an 

issue transaction for reversal.

(5) Establish a new reply code to reject an improperly forwarded SDR containing 

Reply Code 526 or 527. WebSDR will implement this code to ensure that the identified new 

action activity previously received and responded to the original SDR. This will prevent 

transaction failure in DSS since the original SDR record must be present prior to processing a 

follow-on transaction. WebSDR will reject with Reply Code 945 and remarks: “Transfer-To 

activity must have received and responded to the original SDR submission per SDR history prior 

to this forwarding action. Research correct Transfer-To activity and SDR processing history.” 

The new code will be established in the 900-series for system/application rejections as follows:

945 Transaction rejected. Forwarding action cannot be processed; see remarks. 

e. Revisions to DLM 4000.25 Manuals:

(1) Revise DLM 4000.25, Volume 2, Chapter 17, Supply Discrepancy Reporting, 

as shown in Enclosure 1.

(2) Revise DLM 4000.25, Volume 2, Appendix 7.28, Supply Discrepancy Report 

Relevant Data Elements, as shown in Enclosure 2.

(3) Update DLMS IC 842A/W Standard SDR, Follow-up, Correction, 

Cancellation, & Reconsideration Request and 842A/R SDR Reply as shown in Enclosure 4.

f. Transaction Flow: Standard SDR transaction flows apply with the exception of a 

new flow to return the SDR for action to the storage activity with disposition instructions (after 

prior processing of the SDR by the storage activity). Refer to Enclosure 3 for transaction flow 

diagram.

g. Alternatives: None identified. 

5. REASON FOR CHANGES: Supports Component requested functional enhancement to 

allow for returning the SDR reply to the storage activity to request additional research or other 

action subsequent to initial action activity response.
Attachment, ADC 1217

Page 4

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Provides additional capability to WebSDR responders and retains an 

audit trail for communications between action activities.

b. Disadvantages: None noted.

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

DEVELOPMENT: The processing described in this change is not applicable to Army-directed 

shipments under current Army policy. The shipping activity is not the initial action activity for 

Army-directed shipments; customers are instructed to direct SDRs to the source of supply. No 

system edits will prevent use of this process should Army policy for initial action activity 

determination change in the future. 

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: 

a. Sources of supply will be authorized use of the new “backward flow” described in this 

change for return of an SDR reporting nonreceipt to a Consolidation and Containerization Point 

(CCP) when proof of delivery is available. Separate DLMS Change 1241 will being published

for this process.

b. EBSO anticipates further coordination with the Army to implement this change to 

improve transactional exchange between Army Logistics Management Program (LMP) and the 

receiving distribution center. For this to occur the Army will also need to allow new SDR 

submissions applicable to distribution center shipments to be routed directly to the distribution 

center. This is necessary so the original SDR will be available when the Army manager requests 

distribution center action via the SDR reply. Upon joint Army/DLA agreement, business rules 

applicable to the procedural change described here will be documented separately.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Components must update 

reply code values jointly with WebSDR functionality for “backward flow” and the associated 

WebSDR edit. Target date for implementation is no later than (NLT) March 2018. DLA 

Distribution must be able to accept backward flow reply transactions from the source of supply 

NLT March 2018. Component implementation cannot precede WebSDR implementation. 

Components are authorized to implement on a staggered basis beginning March 2018. This 

change is optional for Army and is otherwise required for DLMS compliance by December 

2019.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available. This change supports a systemic 

audit trail for off-line coordination and provides more timely support to customers when 

successful communication with the storage activity results in issue reversal.

11. IMPACT:

a. New DLMS Data Elements: None identified.

b. Changes to DLMS Data Elements: Add SDR reply codes as shown in Enclosure 2.
Attachment, ADC 1217

Page 5

c. Automated Information Systems (AIS): As applicable:

(1) Component SDR systems supporting the source of supply are authorized to

adopt the new capability and identify the storage activity/initial action activity to return the SDR 

to that activity with disposition instructions as described in this change. This process will be 

similar to current “redirecting” of the SDR using Reply Code 504. Use of these procedures will 

be optional by Components as needed.

(2) Component SDR systems supporting the storage activity (e.g., DSS) must 

ensure SDR processing will support reopening a customer SDR based upon the incoming SDR 

reply from the source of supply containing Reply Code 526 or 527. This requirement is required 

when the applicable records are available in the Component system.

(3) Update reply code tables for new reply codes.

d. DAAS: Significant changes to DOD WebSDR include:

(1) When the on-line user selects Reply Code 526 or 527, WebSDR must display 

a new input box to identify the initial action activity. The value should be prepopulated by 

WebSDR from SDR history (there is no known circumstance where WebSDR would not have 

access to the correct action activity). Current functionality employs a RIC for identification of 

the Transfer-To activity. Future functionality will be DoDAAC-based.

(2) Update WebSDR database and management reports functionality as needed to 

recognize the current action activity will be the initial action activity based upon Reply Code 526 

or 527 (additional reply codes may be identified by users during staffing). Subsequent to 

processing the returned SDR (and prior to a storage activity reply), WebSDR must forward any 

customer-initiated transactions (e.g., follow-ups and corrections) to the storage activity with a 

copy to the source of supply.

(3) WebSDR must edit transactions containing Reply Code 526 or 527 to ensure 

that the identified new action activity previously received and responded to the original SDR. 

(4) Update reply code tables for new Reply Codes 526, 527, 530, and 945.

e. Non-DLM 4000.25 Series Publications: Process revisions require updates to internal 

operating procedures and other published SDR guidance.

12. PROPOSED DLMS CHANGE (PDC) 1217 STAFFING RESPONSE/COMMENT 

RESOLUTION:

Originator Response/Comment Disposition

1. Army Concur Noted.

2. Navy Concur

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

Preliminary Navy Questions/Concerns:

1. If a disposition response is received by the SDR Originator from the 

storage activity, and then subsequently rejected by the source of supply 

Noted.

See inserts for DLMS 

Program Office 

response to specific 

comments.
Attachment, ADC 1217

Page 6

Originator Response/Comment Disposition

(SoS) and revised disposition is provided, there is possible confusion as 

to what disposition should be followed and whether or not credit has 

truly been authorized. In addition, there may be confusion as to who is 

responsible for processing any credit actions.

DLMS Response: See below.

2. If the SoS uses a 526 (credit authorized; issue reversal requested) in 

conjunction with a 105, and the SDR Originator receives that response 

and promptly returns the material as directed for credit action, what 

recourse does the customer have if the storage activity responds with a 

530 (storage activity unable to perform requested issue reversal) or a 

945 (transaction rejected). What is the timeframe for responding to 

these Action Response Codes? Can the SoS respond to a 530/945 

response to reopen the SDR in DSS ISDR? Will the Action Point POC 

be required to enter remarks when a 530/945 is utilized and will those 

remarks carry over into PDREP?

DLMS Response: See below. Also, Reply Code 945 would be used by 

WebSDR rather than the source of supply. Remarks are required for all 

replies and are expected to be viewed in PDREP.

3. Are there systemic limitations to the number of Action Response 

Codes entered? Multiple Action Response Codes may cause confusion. 

How can this be remedied? Will PDREP retain a history of Action Code 

Responses by date and Action Point POC?

DLMS Response: See below. Also, SDR Replies can carry up to three 

reply codes per transaction.

4. Enclosure 3 (flow diagram) raises some questions/concerns:

After the SoS places a 526/105 on the SDR, the SDR is reopened based 

on the incoming SDR reply. The Originator will return the discrepant 

material prior to a determination as to whether or not DSS will support 

the SoS request to process the issue reversal. 

a. If a 503 or 945 response is issued after discrepant 

material is returned, will DLA process a receipt for the 

discrepant return under the same SDR doc#? 

b. Do the Originators need to be instructed to wait to 

follow SoS disposition (526/105) until the storage activity 

places a 152/151 Action Response Code on the SDR?

c. It appears the SDR Originator will receive multiple 

reply copies throughout this flow. Should any of those copies 

be suppressed? Should final disposition be the only copy sent to 

the SDR Originator to avoid confusion?

d. If the storage activity agrees to process the issue 

reversal (152/151), what is the required timeframe to process the 

authorized issue reversal? 

DLMS Response: See below.
Attachment, ADC 1217

Page 7

Originator Response/Comment Disposition

Navy Recommendations:

1. Retention of all Action Code Responses and remarks must be 

maintained within SDR History in PDREP.

DLMS Response: Concur. Action for PDREP.

2. Timeframes must be established in order to ensure material 

disposition is not prolonged. In addition, there should be a systemic 

“flag” to notify SoS of when a follow-up should be generated (i.e., 25 

days or 30 days) within PDREP.

DLMS Response: Standard timeframes apply. Automated follow-up 

reminders within PDREP (and all Component SDR applications) are be 

appropriate.

3. Any rejection or inability to process an issue reversal must include 

additional remarks to the SoS. A valid DLA POC (name/contact 

information) must accompany all Action Response Codes/remarks 

received.

DLMS Response: POC info is already required on SDR replies. 

Procedures will direct that SDR remarks explain the reason an issue 

reversal cannot be executed.

4. A clear Action Code Response should be established to let the SDR 

Originator know that final disposition has been entered. This will ensure 

there is no confusion as to what disposition should be followed and/or 

whether or not credit has been authorized (and who is responsible for 

processing that credit action – storage activity or SoS).

DLMS Response: There are too many scenarios making it impossible to 

know for sure which reply will be the final one. We are doing what we 

can to deal with this concern, (e.g., establishing separate codes for 

storage activity and source of supply credit and trying to use Reply Code 

151 to indicate an “override” of previous reply). A major redesign for 

the communications between the storage activity and the source of 

supply would be necessary to make significant improvement. There is 

no current plan at this time for such a redesign (e.g., using a different 

beginning segment code in the transaction to restrict the flow between 

the distribution center and the source of supply without sending a copy 

to the customer).

Re Comment 2 above: This is a situation we are addressing in the 

procedures. Although we could require that the codes be used 

sequentially (one at a time, waiting for confirmation that the storage 

activity can process an issue reversal before directing the customer to 

return the materiel), I do not think the delay is necessary. If the storage 

activity cannot process an issue reversal (which may well be the case), 

the source of supply will need to issue credit instead. Although the Navy 

has strong preference for issue reversal due to internal financial 

processes, when DLA Distribution indicates that this approach is not 

available, the only option is to provide credit via MILSBILLS. Since the 

issue reversal would not actually occur until the materiel is physically 

returned, there is no reason to delay the return shipment. Best approach 

is to return materiel expecting an issue reversal until such time as 

additional replies are received indicating no issue reversal (530) 

followed by source of supply reply for credit (101).
Attachment, ADC 1217

Page 8

Originator Response/Comment Disposition

3. Air Force Concur Noted.

4. Marine Corps Concur Noted.

5. DLA Concur

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

Preliminary DLA Distribution Questions/Concerns:

DLA questioned the intended impact of this change to existing policy 

and procedures for authorization to use an issue reversal. 

DLMS Response: EBSO inserted a staffing note to clarify that this ADC 

only establishes the mechanism needed for a backward transaction flow 

so the source of supply can send a reply to the distribution center to 

reopen a closed SDR for further review or action. The functionality to 

support this communication exchange does not revise existing policy. If 

the issue transaction is not eligible for reversal, the distribution center 

will respond accordingly with the new reply code and narrative 

explanation. 

Noted.
Enclosure 1, ADC 1217

Page 1

Enclosure 1, Defense Logistics Manual (DLM) Chapter Revisions

Revise DLM 4000.25, Defense Logistics Management Standards, Volume 2, Chapter 17, Supply 

Discrepancy Reporting, as shown. 

Changes are identified by bold red italics and strike-though text. Intervening text between 

updated paragraphs is not shown. Paragraphs will be renumbered as appropriate due to 

identified revisions.

C17.3.11. Follow-Up on Original SDR

C17.3.11.1. Submitter Responsibility. When the action activity does not respond 

to an SDR within the prescribed timeframe specified in this chapter, the submitting activity must

provide an SDR follow-up. Follow-ups must be directed to the last identified action activity 

when the original SDR was forwarded by the original recipient. Cite the SDR report number of 

the original report. For transactional exchange, include the WebSDR-assigned control number 

when known. Follow-up transactions should include all data that was in the previous SDR 

submission. POC information for the follow-up and the follow-up date are required. A narrative 

entry is required to provide clarification for the follow-up. The submitter or DoD WebSDR must 

forward the follow-up to the new current action activity when SDR history indicates a new or 

updated action activity has been identified (such as based upon prior Reply Code 504, 526, 527

or a 300-series reply code).

C17.3.11.1.1 SDR submitters may follow-up on SDRs sent to DLA 

Distribution Centers after 31 days from the submission date have elapsed. This will not ensure 

full resolution of the SDR, but will help identify a communication problem before the entire 

SDR response period has elapsed (i.e. depot and SoS processing time).

C17.3.11.1.2. Routine SDR follow-ups (e.g. not applicable to controlled 

inventory items) must be submitted no sooner than 55 days from the original submission date 

when no response has been provided. 

C17.3.11.1.3. Submitters must follow up to the current action activity 

after receipt of an interim reply but no further response within 55 days of the initial reply.

(Intervening text not shown)

C17.3.12.1.2.1. Interim Replies 

(Intervening text not shown)

C17.3.12.1.2.1.4. Source of Supply Returning SDR Disposition 

Instructions to Storage Activity/Initial Action Activity after Storage Activity Response.

1 

C17.3.12.1.2.1.4.1. Following initial action activity 

reply/forwarding and closure of the SDR by the initial activity system, the source of supply for 

 1 Refer to ADC 1217.
Enclosure 1, ADC 1217

Page 2

the shipment may need to return the SDR to the storage activity/initial action activity to reopen 

the SDR and perform directed disposition instructions. To accomplish this, the SDR reply 

must identify the storage activity/initial action activity as the Transfer-To party and the 

appropriate interim reply code: Reply Code 526 (Credit authorized; storage activity issue 

reversal requested) or Reply Code 527 (SDR returned to storage activity/initial action activity

for additional action (see remarks)). WebSDR will recognize this construct and make 

distribution to the SDR submitter and the identified action activity (or reject inappropriately 

forwarded SDRs with Reply Code 945). 

C17.3.12.1.2.1.4.2. The storage activity/initial action activity

system must reopen the SDR upon receipt of the incoming reply. Storage activity/initial action 

activity personnel will review the requested disposition and respond as appropriate within 25 

days. If the storage activity/initial action activity is able to complete the requested action, that 

activity will provide a new reply to the customer citing applicable reply codes including Reply 

Code 151 (Replacement/revised disposition/status; prior response is superseded). WebSDR 

will distribute the reply to the SDR submitter and to the source of supply based upon inclusion 

of the source of supply in the owner/manager/source of supply field2. If the storage 

activity/initial action activity is unable to complete the requested deposition for issue reversal, 

it may forward the SDR to the source of supply for action using Reply Code 530 (Storage 

activity unable to perform requested issue reversal) and the appropriate 300-series forwarding 

reply code. If the storage activity/initial action activity is otherwise unable to complete the 

requested disposition, the 300-series forwarding reply applies. The source of supply should 

contact DLA Distribution if it does not receive a response to the returned SDR within 30 days.

(Intervening text not shown)

C17.3.20.1.1.6. DoD WebSDR will route submitter transactions for

corrections and follow-up to the new current action activity when SDR history indicates a new 

or updated action activity has been identified (such as based upon prior Reply Code 504, 

526/527 or a 300-series reply code). WebSDR will disseminate other transaction types based 

upon the identified action activity (current action activity after Reply Code 504 forwarding) 

and SDR distribution rules.

(Intervening text not shown)

C17.3.20.2.22. WebSDR will reject attempted return of SDRs to the storage 

activity/initial action activity using Reply Code 526/527 when the identified Transfer-To party 

is not identified or consistent with SDR history (must be same action activity that received and 

processed the original SDR response) using Reply Code 945.

3

 2 Current processing uses a single multi-purpose field. Upon implementation of ADC 1126, separate discrete 

data fields will identify the owner, manager, and source of supply. 3 Refer to ADC 1217.
Enclosure 2, PDC 1217 

Page 1

Enclosure 2, DLM Appendix Updates

Revise DLM 4000.25, Volume 2, Appendix 7.28, Supply Discrepancy Report Relevant Data 

Elements, as shown. 

AP7.28.4 Discrepancy Status or Disposition (Reply) Codes

(Intervening text not shown)

The 500-series (and some 100-series) codes indicate an interim reply:

526 Credit authorized; issue reversal requested

527 SDR returned to storage/initial action activity for action; see remarks

530 Storage activity unable to perform requested issue reversal; see remarks (must use with 

300-series forwarding reply code)

(Intervening text not shown)

The 900-series codes are intended for system/application use in processing transactions. When 

SDRs are processed manually, these codes may be user assigned as appropriate:

(Intervening text not shown)

945 Transaction rejected. Forwarding action not authorized; see remarks
Enclosure 3, ADC 1217

Page 1

Enclosure 3, Flow Diagram

The following diagram depicts a sample scenario for SDR processing under the approved

change. Process and specific codes identified would differ for other similar scenarios. Refer to 

ADC 1160 (Reference 3.b.) for additional information on issue reversal procedures applicable to 

customer reported discrepant receipts.
Enclosure 4, ADC 1217

Page 1

Enclosure 4, DLMS IC Updates

A. Revise the DLMS 842A/R IC 842A/R Standard Supply Discrepancy Report (SDR) Reply as

follows:

# Location Change Table for 

842A/R Standard Supply Discrepancy Report (SDR) Reply

Reason

1. DLMS 

Introductory 

Note

Add PDC 1217 to DLMS Introductory note on the cover page of the IC: 

- PDC 1217, WebSDR Process Enhancement for Source of Supply 

Disposition Response to Storage Activity on Customer-Initiated SDRs

To identify DLMS 

changes included in 

the DLMS.

2. 2/N101/4100 Revise DLMS Note for existing Codes HA, KA, TT, and SUS:

HA Owner

DLMS Note: 

1. Use as applicable to identify the materiel owner by RIC. Must use for 

storage activity SDRs (Document Type 8, 9, R, A, N, and P).

2. For DLA Disposition Services prepared SDRs (Document Type D), use 

to identify DLA Disposition Services as the owner for materiel turn-ins 

with the exception of materiel that was not accepted. For this situation, 

the owner may be left blank and the original owner of the materiel will be 

understood to be the current owner.

3. Delayed implementation. Use Code SUS Supply Source for owner 

identification pending implementation of ADC 1126 no later than 2018.

KA Item Manager 

DLMS Note:

1. Use as applicable to identify the item manager by RIC. Must use for 

use for storage activity SDRs (Document Type 8, 9, R, A, N, and P). 

2. Delayed implementation. Use Code SUS Supply Source for manager 

identification pending implementation of ADC 1126 no later than 2018.

TT Transfer To

DLMS Note:

1. The responding activity uses to designate the Routing Identifier Code 

(RIC) of the new action activity to which the original SDR is to be 

forwarded (use with Reply Code 504 (2/LQ01/4650/HD)).

2. The source of supply uses to designate the storage activity (initial 

action activity) to which the SDR is being returned to be reworked with 

disposition instructions provided by the source of supply (use with Reply 

Code 526 or 527 (2/LQ01/4650/HD)). Refer to PDC 1217.

3. DoD WebSDR uses in the reply transaction forwarded by WebSDR to 

the submitter to identify the RIC of the new action activity to which the 

SDR has been forwarded by the shipping activity for disposition and/or 

financial resolution (used with 300-series reply codes 

(2/LQ01/4650/HD)). The new action activity will provide a subsequent 

reply.

4. Identify the “Transfer To” party using a RIC pending future 

transition to processing based upon the activity’s DoDAAC.

Documents expanded 

use of the Transfer 

To activity to support 

return of the SDR for 

reopening at the 

storage activity.

Administrative 

update for 

clarification of 

delayed 

implementation status 

for ADC 1126.
Enclosure 4, ADC 1217

Page 2

B. Revise the DLMS 842A/W IC Standard Supply Discrepancy Report (SDR), Follow-up, 

Correction, Cancellation, & Reconsideration Request as follows:

# Location Change Table for 

842A/R Standard Supply Discrepancy Report (SDR) Reply

Reason

SUS Supply Source

DLMS Note:

1. Use as applicable to identify the source of supply (SoS) by Routing 

Identifier Code (RIC). Must use for customer SDRs (Document Type 6, 7, 

and V); this is the party that directed the shipment. 

2. For transshipper prepared SDRs (Document Type W), use to identify 

the party that directed the shipment.

3. Pending delayed implementation of ADC 1126, also use this field to 

identify the owner/manager.

# Location Change Table for 

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

Correction, Cancellation, & Reconsideration Request

Reason

1. DLMS 

Introductory 

Note

Add PDC 1217 to DLMS Introductory note on the cover page of the IC: 

- PDC 1217, WebSDR Process Enhancement for Source of Supply 

Disposition Response to Storage Activity on Customer-Initiated SDRs

To identify DLMS 

changes included in 

the DLMS.

2. 2/N101/2800 Revise DLMS Note for existing Qualifier HA, KA, and SUS:

HA Owner

DLMS Note: 

1. Use as applicable to identify the materiel owner by RIC. Must use for 

storage activity SDRs (Document Type 8, 9, R, A, N, and P).

2. For DLA Disposition Services prepared SDRs (Document Type D), use 

to identify DLA Disposition Services as the owner for materiel turn-ins 

with the exception of materiel that was not accepted. For this situation, 

the owner may be left blank and the original owner of the materiel will be 

understood to be the current owner.

3. Delayed implementation. Use Code SUS Supply Source for owner 

identification pending implementation of ADC 1126 no later than 2018.

KA Item Manager 

DLMS Note:

1. Use as applicable to identify the item manager by RIC. Must use for 

use for storage activity SDRs (Document Type 8, 9, R, A, N, and P). 

2. Delayed implementation. Use Code SUS Supply Source for manager 

identification pending implementation of ADC 1126 no later than 2018.

SUS Supply Source

DLMS Note:

1. Use as applicable to identify the source of supply (SoS) by Routing 

Identifier Code (RIC). Must use for customer SDRs (Document Type 6, 7, 

and V); this is the party that directed the shipment. 

Administrative 

update for 

clarification of 

delayed 

implementation 

status for ADC 

1126. 
Enclosure 4, ADC 1217

Page 3

# Location Change Table for 

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

Correction, Cancellation, & Reconsideration Request

Reason

2. For transshipper prepared SDRs (Document Type W), use to identify 

the party that directed the shipment

3. Pending delayed implementation of ADC 1126, also use this field to 

identify the owner/manager.