1

Approved DLMS Change (ADC) 114,

 DS 842A/R DOD Standard SDR Reply

and Additional Data Content for the SDR Report

1. ORIGINATOR:

a. Service/Agency: Defense Logistics Agency

b. Sponsor: Supply Process Review Committee, Chair: Ellen Hilert, DLA DLMSO/J-6411, 

Defense Logistics Management Standards Office (DLMSO), 703-767-0676 (DSN 427), 

ellen.hilert@dla.mil

2. FUNCTIONAL AREA: Primary: Supply

3. REFERENCES: 

a. The DOD WebSDR is an internet-based Supply Discrepancy Report (SDR) submission 

program currently under development. Images of all input screens are posted at 

https://day2k1.daas.dla.mil/websdr/demo_files/demo.htm. To obtain access to the test version of the 

system contact the PDC sponsor. Phase I initial operating capability of the DOD WebSDR is now 

projected for the February-March 2004 timeframe.

b. The official guidance for submission of SDRs is published in DLAI 4140.55/

AR 735-11-2/SECNAVINST 4355.18A/AFJMAN 23-215. The joint service publication is 

available at http://www.dla.mil/j-6/dlmso/Manuals/Default.htm. 

c. DOD 4140.1-R, May 23, 2003, DOD Supply Chain Materiel Management Regulation. This 

regulation requires automated SDR processing. This regulation is available at 

http://www.acq.osd.mil/log/logistics_materiel_readiness/organizations/sci/assetts/executive_info/drid/p41

401r.pdf. Refer to paragraph C3.8.1.6.4.

4. REQUESTED CHANGE:

a. Title: ADC 114, DS 842A/R DOD Standard SDR Reply and Additional Data Content for 

the SDR Report

b. Description of Change: This change provides a means to transmit responses to the 

complaints based upon the Standard Form (SF) 364, Supply Discrepancy Report. The DS, referred 

to here as 842A/R, SDR Reply, is provided at Enclosure 1. This DS 842A/R uses ANSI ASC X12 

Version 4030. It will serve as the basis for standard SDR EDI transaction exchanges. This change 

also identifies revisions to the 842 A/W, Standard SDR, to provide additional data content that was 

identified subsequent to publication (Enclosure 2.

c. Procedures: All data which may be communicated to the customer in response to an SDR 
2

submission is mapped to the DS 842A/R. Component’s ability to interpret/process this data as 

reflected in the DS may vary. Implementing Components should allow for identification of data not 

specifically mapped to their automated processing systems within a narrative remarks section until full 

implementation of the DLMS. Data requirements are specifically modeled to the SF 364, Report of 

Discrepancy, the DOD WebSDR program, and other implemented web capabilities as identified by 

the Components. In order to support any existing data mapping to the checkboxes on the reverse of 

the SF 364, these have been accommodated using a code list provided at Enclosure 3. This an interim 

work-around to accommodate existing Component system design. The objective is to transition to 

approved data elements to communicate the checkbox information.

5. REASON FOR CHANGE: This change is provided to support DOD implementation of the 

DLMS. Additionally, this DS provides a greatly simplified use of the complex 842 transaction as 

previously represented in the Version 4010 Federal Implementation Convention (IC) 842D. 

Components may use this transaction to communicate to the customer/Component system via DAAS. 

DAAS any-to-any conversion/translation capability will be employed to route the response to the 

customer/Component system via transaction/email or it may be accessed within the DOD WebSDR 

application. DAAS translation will be phased out as the Components adopt the DLMS format.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Supports DLMS implementation. 

b. Disadvantages: None identified. 

7. IMPACT:

a. Data Content/Procedures: The capability to provide SDRs in the DLMS format must be 

incorporated in the Component system design. 

b. Publication(s): 

(1) The Federal IC 842A will serve as the basis for the new DS 842A/R. The DS 

842A/R and 842 A/W will be updated as indicated.

(2) DOD 4000.25-M, DLMS

Enclosures
SF 364 Check Boxes

Proposal Background: The information provided by the SF 364 check boxes is

generally duplicative of the SDR Response Codes authorized under the joint Component

guidance and other information already contained within the SDR Reply. However, at

lease one Service relies on the check-box information in an electronic form (in addition to

the response codes). Therefore, a method is being provided to pass the check box

information as codes. Checkboxes are difficult to map in ANSI X12 and rather than

create separate data elements for each box, a code value under a single data element is

assigned to each box for transaction exchange. These codes are only to be used during

SDR transmission and would not be used to communicate with the customer. Repeat the ANSI 

qualifier as many times as needed to identify each individual checked box. This data element should be 

phase out as the 842 and associated reply codes are adopted.

Mapping Plan: The DOD code list will use an existing ANSI qualifier for Form Type

Code to identify the checkboxes. The applicable code values will be contained in the

dictionary of DLMS Qualifiers. The LQ01, DE 1270, Code List Qualifier Code, will

reflect Qualifier AS with a DLMS Note: This code list equates to the check boxes on the

reverse side of the SF-364. Associated information is specifically identified and carried

elsewhere in the transaction.

Form Type Code (Qualifier AS)

Code - Explanation

01 - Materiel Has Been Shipped

02 - Materiel will be Shipped

03 - No Record of Shipment - Resubmit Report to Proper Office

04 - Adjustment Billing Credit

05 - Adjustment Billing Debit

06 - Invoice/Bill Attached

07 - Proof Of Delivery Enclosed

08 - SDR Not Processed - Exceeds Time Frame

09 - SDR Not Processed - Dollar Value Not Met

10 - Prescribing Regulation – GSA Handbook GSACH5

11 - Prescribing Regulation – MILSBILLS/LOA

12 - Disposition - Process for Disposal

13 - Disposition – Retain at No Charge

14 - Representative Will Call

15 - Materiel will be Picked Up

16 - Ship Materiel to Specified Location

17 - GBL Chargeable as Identified

18 - Charge Collection Type - Freight

19 - Charge Collection Type - Express

20 - Charge Collection Type - Parcel Post

21 - Parcel Post Label Attached

22 - Freight Prepaid

23 - Other Disposition – See Comment

24 - New Requisition Required

25 - Replacement will be Provided
1

DS 842A/W, Standard SDR

Additional Data Content

Location Revision Comment

1/N101/1200 Add qualifier and note:

41 Submitter

DLMS Note: Use to identify the DoDAAC of organization 

submitting the SDR transaction. (If this is other than the 

customer originating the SDR, identify the customer at 

2/N101/2800 Code LW.)

ZS Monitoring Party

DLMS Note: Use to identify the International Logistics 

Control Office (ILCO).

Z6 Transferring Party

DLMS Note: Use with BGR01 Code 47 to indicate the action 

activity forwarding the SDR.

Additional codes are 

needed to identify the 

transaction submitter when 

other than DAAS.

1/N103/1200 Add qualifier and note:

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

May be used for the customer DoDAAC only.

Supports identification of 

customer.

2/DTM01/0600 Revise note:

881 Request

DLMS Note:

Use to identify the date of the customer's request for 

reconsideration.

Clarification.

2/REF01/0700 Add qualifier and note:

XY Other Unlisted Type of Reference Number

DLMS Note: 

Use to identify other unlisted type of transportation number.

Dropped off a previous

version.

2/N101/2800 Replace code 41, Submitter and revise DLMS note:

LW Customer

DLMS Note: Use to identify the SDR report initiator by 

DODAAC/MAPAC and/or clear text address. 

Clarification. Distinguishes 

customer from 842 

submitter identified in the 

beginning segment. 

MAPAC allows for 

identification of the SA 

structured address if 

needed.

2/N103/2800 Add qualifier and note:

A2 MAPAC

DLMS Note: Use to identify the structured MAPAC.

MAPAC allows for 

identification of the SA

customer.

2/LQ01/1050 Add qualifier and note: Supports DLA 
2

D Court Document Type Code 

DLMS Note: Use to identify the Type Document Code. This 

is a DLA unique data element. Code list is available in DLAH 

4140.4, CDCS Handbook. DAAS will fill as follows when not 

shown on transaction:

6 – SDR for Direct Vendor Delivery

7 - SDR for Depot to Customer

An ANSI data maintenance action will be taken to obtain a 

more appropriate code for use in a future version/release. 

requirement.

2/NTE01/2400 Add qualifier and note:

TPO Third Party Organization Notes

DLMS Note: Use to identify remarks provided by the ILCO.

An ANSI data maintenance request has been prepared to 

request a new data element 1270 code qualifier.

Provides identification of 

ILCO narrative comments.

2/PER01/3300 Add qualifier and note:

SE Service Organization

DLMS Note: Use to identify the ILCO POC. An ANSI data 

maintenance request has been prepared to request a new data 

element 1270 code qualifier.

Provides identification of 

ILCO Point of Contact.

1/BNR01/0200 Revise BNR01 data element note 2 as indicated:

2. For BNR01 codes 01, 15, 22, 50, provide point of contact 

information, action date, and narrative comments. Do not 

repeat information provided in the original SDR or use 

specific data fields to adjust information from original SDR 

unless coordinated with DAAS/DLMSO.

Support ILCO requirement 

to forward fully automated 

transactions in conjunction 

with DAAS process to 

convert to acceptable 

format of receiver. 

2/LQ01/1050 Add qualifiers and notes:

A4 Case Designator Number

DLMS Note: 

Must use in SA SDRs to identify the FMS case number. 

85 Country and Activity Code

DLMS Note:

Use in SA SDRs.

TG Title Document Code List

DLMS Note:

Use on SA SDR to identify the Document Number Type as one 

of the following:: Follow-on Support Requirement, 

Government Furnished Equipment/Materiel, System Sale, 

Repair/Replace Requirement, Repair/Return. Requirement or 

World Wide Redistribution System Requirement.

An ANSI data maintenance action will be taken to obtain a 

more appropriate code for use in a future version/release.

Supports Security

Assistance SDRs.
3

KW Report Source Code

DLMS Note:

Use on SA SDR to identify Portal Submission Indicator

indicating the activity submitting SDRs as authorized by SA 

customers, e.g., SA Customer Submission, STARR PC 

Submission, ILCO Submission (mailed copy submissions), Freight 

Forwarder Submission - as authorized by SA customer or Other 

Activity as authorized by SA customer.

An ANSI data maintenance action will be taken to obtain a 

more appropriate code for use in a future version/release.

TR Report Code

DLMS Note: Use for SA SDR to identify the SDR initiating 

office (SIO). 

2/NTE01/2400 Add qualifier and note:

POL Property Owner Location Information

DLMS Note:

Use to identify the location of discrepant/deficient material.

An ANSI data maintenance action will be taken to obtain a 

more appropriate code for use in a future version/release.

Provides additional note.

2/REF01/2600 Add qualifier and note:

MI Material Storage Location

DLMS Note: 

Use on SA SDR to identify the storage location where the 

discrepant material is being held. This information will be 

needed to calculate a transportation reimbursement to the 

customer, if applicable and provide adequate disposition 

instructions for the return of materiel. 

Coded entry identifies: in-country depot, freight forwarder, 

USG facility or contractor facility.

For SA SDR.

2/ REF04/2600 Delete

ZM Manufacturer Number

Deleted. Remapped to 

N101/2800

2/QTY01/2700 Add qualifier and note:

OT Number of Operating Periods at Failure

DLMS Note:

Use to indicate the operating time at the time of failure of the 

discrepant item. Expressed as 4 position hours and 2 number 

minutes.

For SA SDR.
4

2/N101/2800 Add qualifiers and notes:

SU Supplier/Manufacturer

DLMS Note:

Use with REF01 XB to identify the name or CAGE of the 

manufacturer of the incorrect (wrong) item received.

42 Component Manufacturer

DLMS Note: Use with REF01 PM to identify the CAGE code 

of the manufacturer of the missing component.

Corrected mapping and 

clarification.