DEFENSE LOGISTICS AGENCY HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

February 1, 2021

MEMORANDUM FOR SUPPLY DISCREPANCY REPORT (SDR) PROCESS REVIEW 

COMMITTEE (PRC)

SUBJECT: Approved Standards Change (ADC) 1377A, Addendum to ADC 1377 Transmitting 

Storage Quality Control Reports (SQCRs) Using DLMS 842 A/R and A/W Supply 

Discrepancy Report (SDR) Transmission

The attached change to DoD Enterprise Business Standards, as outlined in the attachment, is 

approved for implementation. 

Addressees may direct questions to Benjamin Breen, e-mail: EBSO.SDR@dla.mil. Others 

must contact their designated PRC representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. 

THOMAS A. DELANEY

Director, Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD(Logistics)

OUSD(C) 

OUSD(A&S/DPC)
Attachment, ASC 1377A

Page 1

ADC 1377A

Addendum to ADC 1377 Transmitting SQCRs

Using DLMS 842 A/R and A/W SDR Transmission

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Mr. Ben Breen, Defense Logistics Standards Office (DLSO) SDR 

Administrator, e-mail: EBSO.SDR@dla.mil. 

b. Functional POC: Ms. Jennifer Smith, J344, e-mail: Jennifer.Smith2@dla.mil 

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: SDR

3. REFERENCES:

a. ADC 1377 Transmitting Storage Quality Control Reports (SQCRs) Using DLMS 842 

A/R and A/W Supply Discrepancy Report (SDR) Transmission October 1, 2020

b. DLM, Defense Logistics Enterprise Standards, Volume 2, Chapter 17 and Appendix 

7.28. Supply Discrepancy Report Relevant Data Elements

4. APPROVED CHANGE(S): 

a. Brief Overview of Change: This change amends ADC 1377 in support of the SQCR 

to SDR transition automation and supports detailed programming requirements for SDR 

Document Type 5 SQCR processing using the existing DLMS 842 SDR exchange (reference 

3.a.).

(1) Background: ADC 1377 established the initial intent and transition of the 

SQCR transactions (DLMS 842SQ/SR) and process over to the SDR transaction exchange, 

DLMS 842A/W SDR and 842A/R SDR Reply. This and all other DLES changes related to the 

SQCR to SDR exchange transition, are planned to coincide with the initial DLA Distribution 

Warehouse Management System (WMS) timeline with the initial implementation and launch 

scheduled for the FY21. DLA Distribution Standard System (DSS) will continue to support the 

current DLA warehousing SQCR process until such a time when the DLA WMS is fully 

implemented across all DLA Distribution Centers (reference 3.a.).

b. Approved Change in Detail: This change will incorporate the DLMS ICs 842SQ/SR 

SQCR data into the existing DLMS 842A/W and 842A/R SDR transactions, and 

(1) Adds required DLMS data elements and notes in support of the SDR 

Document Type 5 SQCR processing requirements.

(2) Updates the SDR discrepancy code list (DLM Volume 2, Appendix 7.28 SDR 

Code Lists to include the existing SQCR codes in the current SQCR exchange. 
Attachment ASC 1377A 

Page 2

c. Revisions to DLM: Revisions to Defense Logistics Enterprise Standards, Volume 2, 

Supply, Appendix 7.28 SDR Codes and Data Elements.

d. Approved Transaction Flow: As DLA Distribution sites migrate to WMS, these 

sites will transmit the SQCR using the 842A/W and 842A/R transactions. DLA Distribution will 

continue the legacy practice of emailing SQCRs for Services at sites still using DSS, and 

continue to send the 842S/Q to DLA EBS. 

e. Alternatives: DLA Distribution can continue to e-mail SQCRs to the Services and 

systemically transmit SQCRs only to EBS. 

f. REASON FOR CHANGE: This change continues to document the requirements to 

transition the SQCR to using the DLMS SDR transaction.

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Eliminates an outdated, manual process and will implement an efficient 

systemic process to exchange SQCRs and incorporate DOD Component systems into the SQCR 

exchange.

b. Disadvantages: None

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

DEVELOPMENT: WebSDR will not edit SDR document type code 5 transactions to ensure 

the proper discrepancy and reply codes are used. These edits should be implemented in WMS 

and the SDR system providing the replies. 

7. ADDITIONAL COMMENTS TO CONSIDER: None

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: None

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The estimated timeline 

will be very aggressive as the implementation begins, and will be done in phases. The initial 

plan will begin with DLA Distribution Center, Corpus Christi, with a deployment date estimated 

for October 2021.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: The cost savings for less customization in WMS 

cannot be quantified at this time. Furthermore, trying to quantify the manual effort for the 

Services and DLA Distribution to process SQCRs and replies via e-mail is not feasible at this 

time. 

11. IMPACT: 

a. New/Changes to Data Elements: Refer to Enclosure 1. 

b. Automated Information Systems (AIS): Product Deficiency Reporting and 

Evaluation Program (PDREP), GSA Vision, DLA Distribution Standard System (DSS), Army 

Logistics Modernization Program (LMP), Air Force Security Assistance and Cooperation 

(AFSAC), Air Force Wholesale DO35K, Air Force Integrated Logistics System Supply (ILS-S) 
Attachment ASC 1377A 

Page 3

and DLA Enterprise Business System (EBS) SDR systems must be updated to reflect the 

enhancements associated with this change.

c. Defense Automatic Addressing System (DAAS): DAAS will need to configure 

WebSDR to incorporate the changes outlined in this document.

d. Non-DLM Publications: Components will need to update internal operating 

procedures.

12. PROPOSED DLMS CHANGE (PSC) 1377A RESPONSE/COMMENT 

RESOLUTION:

Component Response/Comment Disposition

1. DLA Concur with Comment.

Comment:

This PDC will require programming changes to EBS. 

DLA does not have an EBS implementation yet.

As noted.

1. Navy/PDREP Concur with Comment.

Comments:

In order to ensure proper system implementation of PDC 

1377A we request answering the following questions:

1. What data elements are mandatory for a SQCR?

2. Are SQCR Discrepancy Codes limited to A1 thru A6 

and P207?

3. Are SQCR Discrepancy Codes A1 thru A6 also 

applicable to SDRs?

4. Is the HA Entity Identifier Code required in the TO 

segment for SQCRs?

5. How to utilize the following elements?

 Product/Service ID

 Date Time Period

 Internal Order Number

 Preliminary Work Candidate Number

 Information Contact

 Product/Service ID Qualifier

As noted.

Response:

1. See enclosures 1 and 2 

below.

2. See enclosure 3 below.

3. No, SQCR Discrepancy 

Codes A1 thru A6 are NOT 

applicable to SDRs.

4. See enclosures 1 and 2 

below.

5. See enclosures 1 and 2 

below.

2. Air Force Concur with Comment. As noted.

3. US Army Concur without Comment. As noted.

4. USMC Concur without Comment. As noted.

5. DAAS Concur without Comment. As noted.

6. USTRANSCOM None. None.

7. GSA None. None.

8. ODASD Concurs as written. As noted.
Enclosure 1, ASC 1377A

Page 1

Enclosure 1

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

& Reconsideration Request as shown in yellow highlight, and deletions by single strike-through text.

842 Nonconformance Report

Functional Group=NC

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Nonconformance Report Transaction 

Set (842) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report products and 

processes that do not fulfill specifications or requirements. The Nonconformance Report Transaction Set provides the ability for the sender to 

report the nonconformance at the level of detail that is required. It also provides the ability to report the specific nonconformances of a 

component/part while identifying the assembly as the product that is in nonconformance. The Nonconformance Report Transaction Set may be 

used to report, initiate, or request actions related to the nonconformance being reported. Financial and accounting information is provided for 

reporting purposes only. The Nonconformance Report Transaction Set has the capability to report the cause of the nonconformance and to state 

the proposed action to be followed to prevent a repetition of the problem.

DLMS Note:

1a. Use a single occurrence of this transaction set to transmit single complaint transaction to a single or multiple organizations. 

b. This DLMS Implementation Convention (IC) provides the DOD standard format for SDR submission. In addition, it is specifically designed 

to transmit complaint transactions originated in the DoD WebSDR program to the appropriate action activity and distribution copy recipients.

2. The reply to the SDR/SQCR will be carried in the DS 842A/R.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table which can be found on the Enterprise Business Standards Office (EBSO) Web site at www.dla.mil/does/DLMS

4. This transaction may be used to provide item unique identification (IUID) information in accordance with DLMS procedures and OSD 

Supply Policy. Refer to the IUID web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

5. This 842A/W DLMS Implementation Convention contains: Data associated with a DLMS enhancement authorized for implementation by 

modernized systems under DLMS migration. This data (including expanded field sizes) should be adopted during, or subsequent, to 

modernization when applicable to the Component’s business process. Prior coordination is not required. Components should ensure that 

inclusion of this data in a DLMS transaction does not cause inappropriate rejection of the transaction.

6. This DLMS IC incorporates the Proposed DLMS Change and Approved DLMS Change (ADC) listed. PDC/ADCs are available from the

EBSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 101, DLMS mapping for Standard SDR/DOD WebSDR Output, DS 842A/W 

- ADC 114, DLMS Supplement (DS) 842A/R DOD Standard SDR Reply and Additional Data Content for the SDR Report

- ADC 128, Revisions for SDR Transaction Exchange (Formats, Codes, and UID)

- ADC 137, Revisions for SDR Transaction Exchange Supporting SA and Miscellaneous Administrative Changes

- ADC 144, SDR Transaction Exchange Business Rules

- ADC 174, Inclusion of Data Supporting UID of Items in DS 842A/W, SDR, WebSDR

- ADC 184, Redistribution Order (RDO)-based Supply Discrepancy Reports (SDRs)

- ADC 187, Revise SDR Reply Procedures for Forwarding SDRs to New Action Activity, Email Addresses, and Source of Supply (SoS)

- ADC 210, Defense Reutilization and Marketing Service (DRMS) and National Inventory Management Strategy (NIMS) Shipment Types 

Identified for SDR Processing under DLMS

- ADC 210B, Identification of SDR Document Type (includes NIMS and Non-DSS Receipts) This change publishes in the DS additional notes 

for the WebSDR field length where needed for clarification because the authorized DLMS length differs from the X12 field size and where the 

field length might not otherwise be published by an authoritative source.

- ADC 245, Supply Discrepancy Report (SDR) Notification to United States Air Force (USAF) for Distribution Depot (DD) Product Quality 

Deficiency Report (PQDR) Exhibit Receipt

- ADC 245B, Addendum to ADC Notification for Distribution Depot (DD) Product Quality Deficiency Report (PQDR) Exhibit Receipt 

(Supply/SDR)

- ADC 245C, Notification for Distribution Depot Product Quality Deficiency Report (PQDR) Exhibit Receipt - Product Data Reporting and 

Evaluation Program-Automated Information System (PDREP-AIS) Interface 

- ADC 282, Consolidation Containerization Points (CCP)-Originated Supply Discrepancy Reports (SDRs) including Non-compliant Wood 

Packaging Material (WPM)
Enclosure 1, ASC 1377A

Page 2

- ADC 293, Revised Time Standards, Codes, and Procedures for Reporting and Processing of Supply Discrepancies

- ADC 311, SDR Attachment Interface

- ADC 317, Revised Business Rules for Transshipper-Prepared Supply Discrepancy Reports (SDRs) (Supply/SDR)

- ADC 322, Addition of Local Catalog ID qualifier to Support Requirements for Theater Enterprise-Wide Logistics System (TEWLS) 

Requisitions (Supply)

- ADC 334, Supply Discrepancy Report Process for AF Retail Storage Activity Denials (Supply/SDR)

- ADC 357, Revisions to DLMS SDR to Add BDN

- ADC 358, SDR Transaction Content/Business Rule Revisions/Clarification

- ADC 371, Marine Corps SDR Distribution Rules and Navy and Marine Corps SDR and Storage Quality Control Report (SQCR) Procedures 

and Data Content under BRAC

- ADC 381, Procedures and Additional Data Content supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy 

BRAC SS&D/IMSP

- Approved Addendum ADC 381A, Procedures and Additional Data Content supporting Unit of Use Requirements under Marine Corps BRAC 

Storage and Distribution

- ADC 386, Revised Data Content for DLMS Inventory Adjustment and SDR Supporting Mapping Enterprise Business System (MEBS) and 

NGA Product Code Update

- ADC 425, Revised SDR Codes and Procedures including Incorrect Part Number Discrepancy Codes and DoD WebSDR Data Edits and 

Forwarding Enhancements

- ADC 435, DLMS Revisions for SFIS Compliance

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their 

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries

and their Subdivisions

- 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)

- ADC 466, Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA Disposition Services under 

Reutilization Business Integration (RBI)

- ADC 1022, Revised Procedures for Processing Depot Returns (including Receipt, SDR, and Proposed Revision to Time Standard for 

Reclassification of Supply Condition Code J and K Assets)

- ADC 1030, Implementation of Item Unique Identification (IUID) in the DLMS Shipment Status Supporting DoD IUID Supply Policy 

Procedures and Associated Supply Discrepancy Report Procedures

- ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of Accounting (SLOA)/Accounting Classification

- ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

- ADC 1043B, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Modify Business Rules for Beginning Period of Availability

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1044, Enhanced Interim SDR Reply Capability, Status Update, and Completion Notification

- ADC 1052, DOD WebSDR Processes Enhancement and Interface with Electronic Document Access (EDA) System. 

- ADC 1059, Mandatory Use of Four-Character Packaging Discrepancy Codes on SDRs and Storage Quality Control Reports (SQCRs)

- ADC 1066, SDR Process Enhancements: Follow-up Time Standards, SDR Forwarding, Missing Quality Assurance Representative (QAR) 

Signature, use of Unique Item Tracking (UIT) Designator Code for Management Report Selection Criteria, and Administrative Updates

- ADC 1068, Enhanced Procedures for Requisitioning via DOD EMALL and GSA Internet Ordering: Component Verification of Funds 

Availability and Materiel Identification using the Supplier-Assigned Part Number and/or Supplier Commercial and Government Entity (CAGE) 

Code

- ADC 1126, Revised 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

Organizational Name and Other Non-Substantive (Administrative) Updates Completed on August 25, 2014

- ADC 1127, Enhanced SDR Guidance for Foreign Military Sales (FMS), SDR Time Standards for Controlled Inventory Items, SDR 

Forwarding after Logistics Reassignment (LR), Packaging SDRs, and Administrative Updates

- ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

- ADC 1153, SDR Enhancements for Visibility of Discrepancies in Hazardous Materiel Shipments

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions 

and DLMS Manuals (Supply/Contract Administration)

- ADC 1174, WebSDR Process Enhancements and Administrative Updates including SDR Reply Screen and Management Report 

Functionality, New/Revised Reply Codes, and Standardized Identification of the Submitting Customer

- ADC 1198, Establishing Visibility of Capital Equipment for Service Owned Assets Stored at DLA Distribution Centers.

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 19, 2016

- ADC 1203, SDR Procedures for Packaging Discrepancies at FMS Freight Forwarder or Component Retail/Tactical Level Activities including 

Estimated/Actual Repackaging Cost

- ADC 1217, WebSDR Process Enhancement for Source of Supply Disposition Response to Storage Activity on Customer-Initiated SDRs

- ADC 1236, Miscellaneous SDR Enhancements Including Reconsideration Requests, Edit Use Of Reply Code 504, And Remove AFSAC 

Historical Procedures

- ADC 1244, Establishing Visibility of Unique Item Tracking (UIT) Program Items for Service-Owned Assets Stored at DLA Distribution 

Centers and Corresponding Revisions to Inventory Procedures Related to Capital Equipment

- ADC 1268, SDR Enhancements for Procurement Instrument Identifier (PIID)-Related Functionality Including Base Contract Number for 

WebSDR and Contract Number and Secondary Document Number in Prepositioned Materiel Receipt (PMR)/Receipt/SDR for Commercial 

Returns
Enclosure 1, ASC 1377A

Page 3

- ADC 1310, Consolidation Containerization Points (CCP)-Originated Supply Discrepancy Reports (SDRs) including Noncompliant Wood 

Packaging Materiel (WPM) with Cost Breakdown and New Procedures for Closing WPM and Passive RFID

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on 

September 27, 2018

Withdrawal of ADC 1092, DLMS Supply Discrepancy Report (SDR) Interface with the Security Cooperation Enterprise Solution (SCES) 

(Supply/SDR)

- ADC 1331, Documenting and Expanding DAAS Rejection Criteria for Supply Discrepancy Reports (SDR)

- ADC 1331A, Addendum to ADC 1331 Documenting and Expanding DAAS Rejection Criteria for Supply Discrepancy Reports 

- ADC 1354, Update to Allow Both the FedMall Indicator and Document Number Suffix to be Associated with the Document Number in a 

DLMS 842 A/W SDR Report (SDR)

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions 

- ADC 1374, Allowable Updates to SDR Corrections

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BNR Beginning Segment For 

Nonconformance Report

M 1 Must use

* 0300 REF Reference Identification O >1 Not Used

* 0400 DTM Date/Time Reference O >1 Not Used

* 0500 PID Product/Item Description O >1 Not Used

* LOOP ID - MEA >1

* 0600 MEA Measurements O 1 Not Used

* 0700 DTM Date/Time Reference O >1 Not Used

* 0800 REF Reference Identification O >1 Not Used

* LOOP ID - PWK >1

* 0900 PWK Paperwork O 1 Not Used

* 1000 REF Reference Identification O >1 Not Used

* 1100 DTM Date/Time Reference O >1 Not Used

LOOP ID - N1 >1

1200 N1 Name O 1 Used

* 1300 N2 Additional Name Information O 2 Not Used

* 1400 N3 Address Information O 2 Not Used

* 1500 N4 Geographic Location O 1 Not Used

* 1600 REF Reference Identification O >1 Not Used

1700 PER Administrative Communications 

Contact

O >1 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL >1 N2/0100L

0100 HL Hierarchical Level M 1 N2/0100 Used

0200 LIN Item Identification O 1 Used

* 0300 PID Product/Item Description O >1 Not Used

* 0400 PRS Part Release Status O >1 Not Used

* 0500 CID Characteristic/Class ID O >1 Not Used

0600 DTM Date/Time Reference O >1 Used

0700 REF Reference Identification O >1 Used

0750 CS Contract Summary O 1 Used

* 0800 QTY Quantity O >1 Not Used

* 0900 TMD Test Method O 1 Not Used

* 1000 PSD Physical Sample Description O 1 Not Used

1020 PWK Paperwork O >1 Used

LOOP ID - LM >1

1040 LM Code Source Information O 1 Used

1050 LQ Industry Code M >1 Used

* LOOP ID - MEA >1

* 1100 MEA Measurements O 1 Not Used

* 1200 DTM Date/Time Reference O >1 Not Used

* 1300 REF Reference Identification O >1 Not Used
Enclosure 1, ASC 1377A

Page 4

LOOP ID - FA1 >1

1350 FA1 Type of Financial Accounting Data O 1 Used

1360 FA2 Accounting Data M >1 Must use

* LOOP ID - SPS >1

* 1400 SPS Sampling Parameters for 

Summary Statistics

O 1 Not Used

* 1500 REF Reference Identification O >1 Not Used

* 1600 PSD Physical Sample Description O 1 Not Used

* LOOP ID - MEA >1

* 1700 MEA Measurements O 1 Not Used

* 1800 DTM Date/Time Reference O >1 Not Used

* 1900 REF Reference Identification O >1 Not Used

LOOP ID - STA >1

* 2000 STA Statistics O 1 Not Used

* 2100 DTM Date/Time Reference O >1 Not Used

* 2200 REF Reference Identification O >1 Not Used

LOOP ID - NCD >1

2300 NCD Nonconformance Description O 1 Used

2400 NTE Note/Special Instruction O >1 Used

2500 DTM Date/Time Reference O >1 Used

2600 REF Reference Identification O >1 Used

2700 QTY Quantity O >1 Used

2730 AMT Monetary Amount O >1 Used

* 2740 MEA Measurements O >1 Not Used

* 2750 RC Root Cause O >1 Not Used

* LOOP ID - EFI >1

* 2760 EFI Electronic Format Identification O 1 Not Used

* 2770 BIN Binary Data M 1 Not Used

LOOP ID - N1 >1

2800 N1 Name O 1 Used

* 2900 N2 Additional Name Information O 2 Not Used

* 3000 N3 Address Information O 2 Not Used

* 3100 N4 Geographic Location O 1 Not Used

* 3200 REF Reference Identification O >1 Not Used

3300 PER Administrative Communications 

Contact

O >1 Used

LOOP ID - LM >1

3330 LM Code Source Information O 1 Used

3340 LQ Industry Code M >1 Used

LOOP ID - NCA >1

3400 NCA Nonconformance Action O 1 Used

* 3500 NTE Note/Special Instruction O >1 Not Used

* 3600 DTM Date/Time Reference O >1 Not Used

* 3700 REF Reference Identification O >1 Not Used

* LOOP ID - PWK >1

* 3800 PWK Paperwork O 1 Not Used

* 3900 REF Reference Identification O >1 Not Used

* 4000 DTM Date/Time Reference O >1 Not Used

LOOP ID - N1 >1

4100 N1 Name O 1 Used

* 4200 N2 Additional Name Information O 2 Not Used

* 4300 N3 Address Information O 2 Not Used

* 4400 N4 Geographic Location O 1 Not Used

* 4500 REF Reference Identification O >1 Not Used

* 4600 PER Administrative Communications 

Contact

O >1 Not Used
Enclosure 1, ASC 1377A

Page 5

LOOP ID - LM >1

* 4640 LM Code Source Information O 1 Not Used

* 4650 LQ Industry Code M >1 Not Used

* LOOP ID - FA1 >1

* 4660 FA1 Type of Financial Accounting Data O 1 Not Used

* 4670 FA2 Accounting Data M >1 Not Used

4700 SE Transaction Set Trailer M 1 Used

Notes: 

2/0100L The HL levels are item, component, product characteristic, report, and serial number. Valid HL Parent-Child relationships are 1) item 

- component, 2) item - product characteristic, 3) component - product characteristic, 4) report - item, 5) item - serial number, and 6) 

component - serial number.

2/0100 The HL levels are item, component, product characteristic, report, and serial number. Valid HL Parent-Child relationships are 1) item 

- component, 2) item - product characteristic, 3) component - product characteristic, 4) report - item, 5) item - serial number, and 6) 

component - serial number.
Enclosure 1, ASC 1377A

Page 6

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Must use

Purpose: To indicate the start of a transaction set and to assign a control number

Semantics: 

1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction 

set definition (e.g., 810 selects the Invoice Transaction Set).

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate 

implementation convention to match the transaction set definition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

 

Description: Code uniquely identifying a 

Transaction Set

M ID 3/3 Must use 1

Code Name

842 Nonconformance Report

ST02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set

DLMS Note: A unique number assigned by 

the originator of the transaction set, or the 

originator's application program.

M AN 4/9 Must use 1

ST03 1705 Implementation Convention Reference

 

Description: Reference assigned to identify 

Implementation Convention

DLMS Note: Use to indicate this 

transmission uses the 842AW DLMS 

Implementation Convention (IC). Enter the 

DLMS IC 004030F842A0WA00

O AN 1/35 Used 1
Enclosure 1, ASC 1377A

Page 7

BNR Beginning Segment For 

Nonconformance Report

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 5

User Option (Usage): Must use

Purpose: To indicate the beginning of a Nonconformance Report Transaction Set

Semantics: 

1. BNR02 is the nonconformance report identifier number.

2. BNR03 is the date that the nonconformance report was created.

3. BNR04 is the time that the nonconformance report was created.

Comments: 

1. BNR05 indicates the status or intention of the nonconformance report.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BNR01 353 Transaction Set Purpose Code 

Description: Code identifying purpose of 

transaction set

DLMS Note: 1. The following codes are 

authorized.

2. Cancellation, Request for 

Reconsideration, Follow-Up, 2nd Request 

for Reconsideration for FMS, and Correction 

(BNR01 Codes 01, 15, 45, 50, and CO, 

respectively) require point of contact 

information, action date, and narrative 

comments. Cancellation, Correction, 

Follow-up, and Requests For 

Reconsideration must perpetuate data from 

the original SDR with updates as applicable. 

SDR transactions identified by these 

transaction types require an original SDR to 

be recorded in DoD WebSDR and the 

recipient’s SDR system for successful 

processing.

3. For SQCR, use Codes 00, 01, 15, 45, 

and CO.

M ID 2/2 Must use 1

Code Name

00 Original 

DLMS Note:

1. Use to identify a new submission.

2. Transaction Set Purpose Code 00 is also used on WebSDR-forwarded SDRs where the 

original SDR was directed to the wrong action activity (associated with disposition/status reply 

code 504). It will appear as a new SDR to the new action activity, but will include identification 

of the forwarding activity and date forwarded (Qualifier 514).

01 Cancellation

15 Re-Submission 

DLMS Note:

1. Use to request reconsideration on a SDR/ SQCR resolution/disposition (SDR/SQCR must 

include additional information/justification). Can be used only after having received a reply 

from the action activity.

2. Use of request for reconsideration is valid for all SDR Document Type Codes. 

22 Information Copy 

DLMS Note:

Use to indicate SDR is information copy dissemination to non-action activities. (Use of this 

code is not comparable to SDR Action Code 1H which informs the action activity that the SDR 
Enclosure 1, ASC 1377A

Page 8

is provided for information only).

45 Follow-up

DLMS Note:

Storage Submitters activities use to follow-up on open SDR/SQCR.

49 Original - No Response Necessary 

DLMS Note:

1. Reserved - not authorized for use.

50 Register 

DLMS Note:

FMS customers use to contest the U.S. Government decision subsequent to reconsideration 

request.

CO Corrected 

DLMS Note:

1. Document Number and Suffix may not be modified from the original submission. If these 

were identified in error the SDR must be cancelled and resubmitted.

2. Only allowable changes include narrative comments, to include the International Logistics 

Control Office (ILCO) comments section, update the repackaging corrective action cost, 

quantity, supply condition code, upload an attachment as evidential matter, and action code 

for Disposition Service Type D with any subcategory. All other changes must be corrected in 

a new SDR submission. Invalid data changes will be rejected. Refer to ADC 1374.

BNR02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

DLMS Note: 1. Enter "U" to identify the Unit 

of Use Indicator. When included, the 

quantity and unit of measure values 

associated with this transaction are 

applicable to the unit of use. This applies 

when the materiel identification is by Local 

Stock Number assigned for unit of use. This 

is an Authorized DLMS enhancement under 

DLA industrial activity support agreement. 

Refer to ADC 371. 

2. When not used for Unit of Use Indicator, 

must enter Z to satisfy ANSI syntax. 

M AN 1/50 Must use 1

BNR03 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year

DLMS Note: This date corresponds to the 

Universal Time Coordinate (UTC).

M DT 8/8 Must use 1

BNR04 337 Time

 

Description: Time expressed in 24-hour 

clock time as follows: HHMM, or HHMMSS, 

or HHMMSSD, or HHMMSSDD, where H = 

hours (00-23), M = minutes (00-59), S = 

integer seconds (00-59) and DD = decimal 

seconds; decimal seconds are expressed as 

follows: D = tenths (0-9) and DD = 

hundredths (00-99)

DLMS Note: 1. Express the originating 

activity's time in Universal Time Coordinate 

(UTC).

2. Express time in a four-position (HHMM) 

format.

O TM 4/8 Must use 1

BNR06 640 Transaction Type Code

 

O ID 2/2 Used 1
Enclosure 1, ASC 1377A

Page 9

Description: Code specifying the type of 

transaction

Code Name

C1

 

Claim Information 

DLMS Note:

Use to indicate transaction reflects a DoD SDR/SQCR prepared standard transaction.
Enclosure 1, ASC 1377A

Page 10

N1 Name Pos: 1200 Max: 1

Heading - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. P0304 - If either N103 or N104 is present, then the other is required.

2. R0203 - At least one of N102 or N103 is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

Must use to identify the organizations sending and receiving the transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

DLMS Note: The following codes are 

authorized. 

M ID 2/3 Must use 1

Code Name

41 Submitter 

DLMS Note:

1. Use to identify the DoDAAC of organization submitting the SDR transaction. (The customer 

will be identified as the submitter unless using N101 Code Z6 or ZS.)

2. For Type 5 SQCRs this signifies the storage activity.

PK Party to Receive Copy 

DLMS Note:

Use to identify the organization to receive a distribution copy of the SDR.

ZD Party to Receive Reports 

DLMS Note:

1. Use to identify the organization to receive action copy of the SDR.

2. For Type 5 SQCRs this signifies the material owner.

ZS Monitoring Party 

DLMS Note:

Use to identify the (DoDAAC) of the International Logistics Control Office (ILCO). (Identify the 

customer at 2/N101/2800 Code LW.)

N102 93 Name

 

Description: Free-form name

X AN 1/60 Used 1

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

Identification Code (67)

X ID 1/2 Used 1

Code Name

10 Department of Defense Activity Address Code (DODAAC) 

DLMS Note:

1. Used for the customer DoDAAC.

2. May be used for identification of other activities in accordance with Component SDR 
Enclosure 1, ASC 1377A

Page 11

application rules for the DoD WebSDR interface.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

 

Description: Code identifying a party or 

other code

X AN 2/80 Used 1

N106 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

O ID 2/3 Used 1

Code Name

FR

 

Message From 

DLMS Note:

1. Use to indicate the organization cited above is originating the transaction set.

2. For SDR/SQCR, use with Code 41 to indicate the organization cited above is originating the 

transaction set.

TO Message To 

DLMS Note:

1. Use to indicate the organization cited above is receiving the transaction set.

2. For SDR/SQCR, use the Code ZD to indicate the organization cited above is receiving the 

transaction set.
Enclosure 1, ASC 1377A

Page 12

PER Administrative Communications 

Contact

Pos: 1700 Max: >1

Heading - Optional

Loop: N1 Elements: 9

User Option (Usage): Used

Purpose: To identify a person or office to whom administrative communications should be directed

Syntax Rules: 

1. P0304 - If either PER03 or PER04 is present, then the other is required.

2. P0506 - If either PER05 or PER06 is present, then the other is required.

3. P0708 - If either PER07 or PER08 is present, then the other is required.

DLMS Note:

Use a second repetition if needed to identify additional communication numbers. Must provide email address and at least one phone number.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PER01 366 Contact Function Code

 

Description: Code identifying the major 

duty or responsibility of the person or group 

named

M ID 2/2 Must use 1

Code Name

CB Changed By 

DLMS Note:

Use to identify the preparing official's information as associated with modified SDR.

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.

PI Preparer 

DLMS Note:

1. Use to identify the preparing official's information as associated with cancelled SDR/SQCR.

An ANSI data maintenance request has been prepared to request a new data element 1270 

code qualifier.

PU Report Preparer 

DLMS Note:

Use to identify the preparing official's information as associated with a new SDR/SQCR

submission.

RQ Requestor 

DLMS Note:

Use to identify preparing official's information as associated with a contested SDR (ILCO POC 

for contested SDR or request for reconsideration is identified using Qualifier SE).

SE Service Organization 

DLMS Note:

Use to identify the ILCO POC. 

A data maintenance action was approved in version 5030. The approved code/name is "IL -
Enclosure 1, ASC 1377A

Page 13

International Logistics Control Office Point of Contact".

SM Submitting Contact 

DLMS Note:

Use to identify submitting contract as associated with an SDR followup.

PER02 93 Name

 

Description: Free-form name

DLMS Note: WebSDR field length = 25

O AN 1/60 Used 1

PER03 365 Communication Number Qualifier 

Description: Code identifying the type of 

communication number

X ID 2/2 Used 1

Code Name

AU Defense Switched Network 

DLMS Note:

For AU: WebSDR field length = 8

EM Electronic Mail 

DLMS Note:

For EM: WebSDR field length = 50

FX Facsimile 

DLMS Note:

1. Use to identify the commercial FAX number.

2. For FX: WebSDR field length = 16

TE Telephone 

DLMS Note:

1. Use to identify the commercial number.

2. For TE: WebSDR field length = 16

WF Work Facsimile Number 

DLMS Note:

1. Use to identify the DSN FAX number.

2. For WF: WebSDR field length = 8

PER04 364 Communication Number

 

Description: Complete communications 

number including country or area code when 

applicable

X AN 1/256 Used 1

PER05 365 Communication Number Qualifier

 

Description: Code identifying the type of 

communication number

DLMS Note: Use to identify an alternate 

communications number which can be used 

to contact the specified point of contact.

X ID 2/2 Used 1

Code Name

AU Defense Switched Network 

DLMS Note:

For AU: WebSDR field length = 8

EM Electronic Mail 

DLMS Note:

For EM: WebSDR field length = 50

FX Facsimile 

DLMS Note:

1. Use to identify the commercial FAX number.

2. For FX: WebSDR field length = 16

TE Telephone 

DLMS Note:

1. Use to identify the commercial number.

2. For TE: WebSDR field length = 16
Enclosure 1, ASC 1377A

Page 14

WF Work Facsimile Number 

DLMS Note:

1. Use to identify the DSN FAX number.

2. For WF: WebSDR field length = 8

PER06 364 Communication Number

 

Description: Complete communications 

number including country or area code when 

applicable

X AN 1/256 Used 1

PER07 365 Communication Number Qualifier

 

Description: Code identifying the type of 

communication number

X ID 2/2 Used 1

Code Name

AU Defense Switched Network 

DLMS Note:

For AU: WebSDR field length = 8

EM Electronic Mail 

DLMS Note:

For EM: WebSDR field length = 50

FX Facsimile 

DLMS Note:

1. Use to identify the commercial FAX number.

2. For FX: WebSDR field length = 16

TE Telephone 

DLMS Note:

1. Use to identify the commercial number.

2. For TE: WebSDR field length = 16

WF Work Facsimile Number 

DLMS Note:

1. Use to identify the DSN FAX number.

2. For WF: WebSDR field length = 8 

PER08 364 Communication Number

 

Description: Complete communications 

number including country or area code when 

applicable

X AN 1/256 Used 1

PER09 443 Contact Inquiry Reference

 

Description: Additional reference number or 

description to clarify a contact number

DLMS Note: 1. Use as needed to identify 

the office symbol or activity code for the 

party identified.

2. Also may reflect position title of the point 

of contact.

O AN 1/20 Used 1
Enclosure 1, ASC 1377A

Page 15

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment 

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL 

segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the 

transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to 

shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

HL01 628 Hierarchical ID Number

 

Description: A unique number assigned by 

the sender to identify a particular data 

segment in a hierarchical structure

DLMS Note: In the first 2/HL/0100 loop 

iteration, cite numeric 1. In each 

subsequent loop iteration, increase 

incrementally by 1.

M AN 1/12 Must use 1

HL03 735 Hierarchical Level Code

 

Description: Code defining the 

characteristic of a level in a hierarchical 

structure

M ID 1/2 Must use 1

Code Name

I Item 

DLMS Note:

For SDR/SQCR, Use to identify IUID data consistent with IUID data requirements or materiel 

identification by batch/lot number. The IUID data is carried in the REF segment (UII and Serial 

Number). When providing batch/lot number(sz0, the storage location may also be provided. 

The NCD segment is required by ANSI syntax and is used to indicate if an item is received or 

not received. Must use a separate IUID loop for each item or each batch/lot number. Skip this 

level when not applicable. IUID data is a DLMS enhancements; these data elements may or 

may not be received or understood by the recipient’s automated processing system. Use only 

the REF, N1, and NCA Segments in this loop. Skip this level when not applicable.

2. 

RP Report 

DLMS Note:

1. Use in SDR/SQCR all transactions to satisfy ANSI syntax requirement.
Enclosure 1, ASC 1377A

Page 16

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 8

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., 

ISBN No., Model No., or SKU.

DLMS Note:

1. For SQCR, use this segment to cite the National Stock Number, when available, or other primary materiel identification.

2. Use remaining LIN segment to further identify an item.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LIN02 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: Use for materiel identification.

M ID 2/2 Must use 1

Code Name

A3 Locally Assigned Control Number 

DLMS Note:

1. Defense Medical Logistics Standard Support (DMLSS)/Theater Enterprise-Wide Logistics 

System (TEWLS) use to cite the Local Catalog Identification.

2. DLMS enhancement; see introductory DLMS Note 3a. Refer to ADC 322.

3. Under DLMS, field length is restricted to a maximum of 30 positions.

FS National Stock Number 

DLMS Note:

1. Use to identify the NSN for the materiel.

2. For FS: WebSDR field length = 13.

MG Manufacturer's Part Number 

DLMS Note:

1. Use to identify the part number for the item.

2. May be used to identify the supplier-assigned part number when applicable to a DoD 
Enclosure 1, ASC 1377A

Page 17

EMALL or GSA Advantage/Global internet order from a vendor catalog. When used for 

supplier part number, identify the associated CAGE at 2/LIN04. Refer to ADC 1068.

3. For MG: WebSDR field length = 32.

SW Stock Number 

DLMS Note:

1. Use to identify the local stock number (LSN).

2. When used for a unit of use LSN applicable to NSN materiel, the applicable NSN will be 

included for cross-reference.

3. When used for a unit of use LSN applicable to part numbered items, the original partnumbered item LSN will also be included for cross-reference.

4. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to 

ADC 381/Approved Addendum 381A.

ZZ Mutually Defined 

DLMS Note:

1. Use to identify materiel by other than NSN or part number (includes management control 

number or locally assigned materiel identification control numbers).

2. Discrepancies reported by transshippers may use “UNKNOWN” or “MIXED” when specific 

materiel identification is not available or the shipment level SDR applies to mixed content.

3. For ZZ: WebSDR field length = 15.

LIN03 234 Product/Service ID

 

Description: Identifying number for a 

product or service

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: 1.Use for materiel 

identification. Use multiple Product/Service 

ID pairs as needed. The sequence of data 

content for secondary materiel identification 

is dependent upon the applicable primary 

materiel identification. The preferred 

sequence of secondary information is: 

manufacturer's (or supplier’s) part number; 

manufacturer’s (or supplier’s) CAGE; 

nomenclature. However, part number, 

manufacturer’s CAGE, and nomenclature 

may be cited in any order without causing 

transaction failure.

X ID 2/2 Used 1

Code Name

CN Commodity Name 

DLMS Note:

1. Use to identify the nomenclature associated with the item identified.

2. For CN: WebSDR field length = 25.

F7 End-Item Description 

DLMS Note:

1. Use to identify the end item associated with the Security Assistance (SA) product quality 

deficient materiel. 

2. For F7: WebSDR field length = 32

3. Not applicable for SQCRs

F8 Next Higher Used Assembly 

DLMS Note:

1. Use to identify the next higher assembly associated with the Security Assistance (SA) 

product quality deficient materiel.

2. For F8: WebSDR field length = 50
Enclosure 1, ASC 1377A

Page 18

3. Not applicable for SQCRs

FS National Stock Number 

DLMS Note:

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator is included and the 

Local Stock Number (LSN) is identified as the primary materiel identification. Authorized 

DLMS enhancement under DLA industrial activity support agreement. 

MG Manufacturer's Part Number 

DLMS Note:

1. . For SDR/SQCR, use to identify the manufacturer’s part number when the primary materiel 

identification is provided by NSN or LSN

2. For MG: WebSDR field length = 32.

SW Stock Number 

DLMS Note:

1. Use to identify the local stock number (LSN).

2. The LSN is provided as a cross-reference when unit of use indicator is included and the 

unit of use LSN is identified as the primary materiel identification. Authorized DLMS 

enhancement under DLA industrial activity support agreement.

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

1. Use to identify manufacturer (or supplier) associated with a previously identified part 

number.

2. May be used to identify the supplier CAGE when applicable to a DoD EMALL or GSA 

Advantage/Global internet order from a vendor catalog. 

ZZ Mutually Defined 

DLMS Note:

Use to identify materiel 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.

LIN05 234 Product/Service ID

 

Description: Identifying number for a 

product or service

X AN 1/48 Used 1

LIN06 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: Use to further identify an item. 

Use multiple Product/Service ID pairs as 

needed. 

X ID 2/2 Used 1

Code Name

CN Commodity Name 

DLMS Note:

1. Use to identify the nomenclature associated with the item identified.

2. For CN: WebSDR field length = 25.

MG Manufacturer's Part Number 

DLMS Note:

1. For SDR/SQCR, use to identify the part number when primary materiel identification is 

previously identified provided by NSN or LSN

2. For MG: WebSDR field length = 32.

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

Use to identify manufacturer associated with a previously identified part number.

LIN07 234 Product/Service ID

 

X AN 1/48 Used 1
Enclosure 1, ASC 1377A

Page 19

Description: Identifying number for a 

product or service

LIN08 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: Use to further identify an item. 

Use multiple Product/Service ID pairs as 

needed.

X ID 2/2 Used 1

Code Name

CN Commodity Name 

DLMS Note:

1. Use to identify the nomenclature associated with the item identified.

2. For CN: WebSDR field length = 25.

MG Manufacturer's Part Number 

DLMS Note:

1. Use to identify the part number when primary materiel identification is previously identified.

2. For MG: WebSDR field length = 32.

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

Use to identify manufacturer associated with a previously identified part number.

LIN09

 

234 Product/Service ID

 

Description: Identifying number for a 

product or service

X AN 1/48 Used 1

LIN10 234

MN 

Product/Service ID 

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

Model Number

X ID 2/2 Used 1

LIN11 234 Product/Service ID 

Description: Identifying number for a 

product

X AN 1/48 Used 1
Enclosure 1, ASC 1377A

Page 20

DTM Date/Time Reference Pos: 0600 Max: >1

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. C0403 - If DTM04 is present, then DTM03 is required.

2. P0506 - If either DTM05 or DTM06 is present, then the other is required.

3. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

DLMS Note:

Use multiple repetitions as needed to identify dates associated with the complaint. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

 

Description: Code specifying type of date 

or time, or both date and time

DLMS Note: The following codes are 

authorized. 

M ID 3/3 Must use 1

Code Name

003 Invoice 

DLMS Note:

Use to identify the date of the invoice for billing/financial discrepancies.

007 Effective 

DLMS Note:

Use for receipt of mapping products to identify the map effective date. Authorized DLMS 

enhancement.

043 Publication 

DLMS Note:

Use for receipt of mapping products to identify the map edition date. Authorized DLMS 

enhancement.

094 Manufacture 

DLMS Note:

For SDR/SQCR, use to identify the date of manufacture for expired shelf-life discrepancies.

119 Test Performed 

DLMS Note:

Use to identify the test date for Type II (extendible) expired shelf-life discrepancies.

177 Cancellation 

DLMS Note:

Use to identify the date of the customer's request to cancel a previously submitted SDR.

328 Changed 

DLMS Note:

Use to identify the date of the customer's request to change a previously submitted SDR.

510 Date Packed 

DLMS Note:

For SDR/SQCR, use to identify the date the materiel was packed for expired shelf-life 

discrepancies.

511 Shelf Life Expiration 

DLMS Note:

For SDR/SQCR, use to identify the expiration date for Type 1 (non-extendible) expired shelflife discrepancies.

513 Overhauled 

DLMS Note:

Use to identify the overhaul/rebuilt date for product quality deficiencies.

514 Transferred 

DLMS Note:
Enclosure 1, ASC 1377A

Page 21

Use on forwarded SDRs to identify the date the SDR was forwarded to a new action party by 

the action party designated on the original submission.

516 Discovered 

DLMS Note:

Use to identify the date a product quality deficiency was discovered.

517

565

Inspected 

DLMS Note:

Use to identify the date inspected for Type II (extendible) expired shelf-life discrepancies.

Date of Property Inspection

DLMS Note:

Use to indicate date Inspection was completed.

868 Last Follow-up 

DLMS Note:

Use to identify the date of the customer's follow-up for status of a previously submitted SDR.

881 Request 

DLMS Note:

1. Use to identify the date of the submitter’s request for reconsideration.

909 Contestability 

DLMS Note:

Use to identify the date on which the FMS customer contested the action activities response 

to an SDR subsequent to a reconsideration request.

947 Preparation 

DLMS Note:

1. For SDR/SQCR, use to identify the customer's preparation date of the SDR.

2. This date must be the same or later than the date of the inspection (identified by Qualifier 

565)

DTM02 373

 

Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year

:

X

X

DT

 ID 

8/8

2/3 

Must use

 Used

1

 
Enclosure 1, ASC 1377A

Page 22

REF Reference Identification Pos: 0700 Max: >1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

Must use to identify the requisition document number. Use multiple repetitions as needed to identify additional reference numbers associated 

with a discrepancy.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

DLMS Note: The following codes are 

authorized.

M ID 2/3 Must use 1

Code Name

08 Carrier Assigned Package Identification Number 

DLMS Note:

For 08: WebSDR field length = 17

17 Client Reporting Category 

DLMS Note:

1. Use to identify SA product quality deficiencies as either Category I or II.

2. Enter value as “I” or “II” when applicable.

6E Map Reference 

DLMS Note:

1. Use for receipt of mapping products to identify the National Geospatial-Intelligence Agency 

(NGA) Reference Number (NRN). Authorized DLMS enhancement.

2. For 6E: WebSDR field length = 15.

6G Map Number 

DLMS Note:

1. Use for receipt of mapping products to identify the map edition number. Authorized DLMS 

enhancement. 

2. For 6G: WebSDR field length = 3.

86 Operation Number 

DLMS Note:

1. Use to identify the Key Operation (KO) Number associated with the JO.

2. Authorized DLMS enhancement for industrial activity support. Refer to ADC 371.

87 Functional Category 

DLMS Note:

Use to identify the type of SDR. Select one of the following: S (Shipping/Item), P 

(Packaging), or D (Dual Action).

9R Job Order Number 

DLMS Note:

1. For SDR/SQCR, use to identify Job Order (JO) Number.

2. Authorized DLMS enhancement for industrial activity support. Refer to ADC 371 and ADC 

381.
Enclosure 1, ASC 1377A

Page 23

3. For DoD SLOA/Accounting Classification compliance the Job Order Number may be 

repeated as a Work Order Number (FA201 Qualifier WO). Refer to ADC 1043.

4. For 9R: WebSDR field length = 10

BL Government Bill of Lading 

DLMS Note:

For BL: WebSDR field length = 17

BM Bill of Lading Number 

DLMS Note:

1. Use to identify the shipment unit commercial bill of lading number.

2. For BM: WebSDR field length = 17

BY Repair Category Number 

DLMS Note:

1. Use to identify SA product quality deficient item as new or repaired/overhauled (N=New, 

R=Repaired/Overhauled).

2. Use for SDRs for discrepant shipments from commercial repair reported on Document Type 

9/P to distinguish from new procurement. Enter or perpetuate Code R for commercial returns 

from repair, non-destructive test/evaluation, assembly, disassembly, reclamation, and 

conversion/modification. Refer to ADC 1268.

F8 Original Reference Number 

DLMS Note:

1. Use to identify the SDR Customer Reference Number when provided separately. 

Component SDR applications maintain this number and perpetuate to outgoing transactions. 

Must use alphanumeric characters only with no special characters or DAAS will reject as 

DAAS Reject upon submission. Refer to ADC 1331A.

2. May be used when a manually assigned reference number is to be retained as a crossreference to a system assigned number.

3. Used for FMS SDRs to ensure visibility of the ILCO assigned control number within 

Component SDR applications.

4. Use to identify the Air Force maintenance document number/suffix associated with an SDR 

resulting from depot denial under DLA/AF industrial activity support agreement. The number is 

constructed with

the M-series maintenance site identifier in the first six positions of the document number. 

Refer to ADC 334.

5. Use to identify the Navy maintenance document number/suffix associated with an SDR 

resulting from DLA stock positioning/procurement action/requisitioning from another 

Component source of supply. The Navy document number/suffix (normally applicable to the 

requisition alert) will be perpetuated from the Prepositioned Materiel Receipt Document 

(PMRD) provided by DLA under DLA/Navy industrial activity support agreement. Refer to ADC 

371.

6. For F8: WebSDR maximum field length = 18.

GO Exhibit Identifier 

DLMS Note:

1. Use to identify the Deficiency Report Unique Identifier (DRUI) assigned to the PQDR 

exhibit for USAF in conjunction with discrepancy code Q11. Refer to ADC 245C.

2. For GO: WebSDR field Length = min 6; max 7

HN Hazardous Certification Number 

DLMS Note:

1. Use to provide the Hazardous Materiel Indicator specifying if the shipment contains 

hazardous materiels (including explosives/ ammunition). Indicate “yes” or “no” as applicable 

in the REF02. 

2. This is a mandatory entry for SDRs originated by aerial or water ports.

IK Invoice Number 

DLMS Note:

For IK: WebSDR field length = 15 
Enclosure 1, ASC 1377A

Page 24

IL Internal Order Number

DLMS Note:

1. For SQCR, use to identify the internal order number (ION)

2. For IL: WebSDR field length is 10 

IZ Insured Parcel Post Number 

DLMS Note:

For IZ: WebSDR field length = 17

K2 Certified Mail Number 

DLMS Note:

For K2: WebSDR field length = 17

K3 Registered Mail Number 

DLMS Note:

For K3: WebSDR field length = 17

KL Contract Reference 

DLMS Note:

1. Storage activities use to provide a Contract Reference when reporting non-procurement 

materiel receipts in a suspended condition. Cite “NONE” when unavailable.

 

2. Enter the contract number retained on the packaging/labeling from the original shipment of 

the materiel by the vendor. Do not enter the contract number applicable to the physical 

shipment. The contract number applicable to new procurement receipts or direct vendor 

deliveries is carried at 2/CS01/0750. Refer to ADC 1022.

NN Nonconformance Report Number 

DLMS Note:

1. Use to identify the submitting system’s SDR/SQCR report control number. This will be the 

originator's system assigned number. Identify the originating system in REF03 (see REF03 for 

values).

2. If the SDR was originated using the DoD WebSDR, this will be the web-generated control 

number. A WebSDR control number will also be assigned to transactions during processing. 

WebSDR transaction

processing will repeat the REF segment to include each previously identified SDR/SQCR

report control number on the outgoing transaction.

3. Must use alphanumeric characters only with no special characters or DAAS will reject as 

DAAS Reject upon submission. Refer to ADC 1331A.

4. For NN: WebSDR maximum field length = 20 (actual length for originating applications will 

differ)

5. For SQCR, use multiple occurrences as needed to identify applicable report control 

numbers.

PO Purchase Order Number 

DLMS Note:

For PO: WebSDR field length = 13

QR Quality Report Number 

DLMS Note:

1. For SDR/SQCR, use to identify the PQDR Report Control Number (RCN) for cross 

reference to the PQDR exhibit when the discrepancy code is Q11. Refer to ADC 245C.

2. For QR: WebSDR field length =15

3. For SQCR, use to identify the PQDR Report Control Number (RCN) when stock screening 

resulting in SQCR was associated with a PQDR. Up to 5 PQDR RCNs may be entered.

S2 Data Source 

DLMS Note:

1. 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. If other, use 

REF03 to provide an explanation.

2. For S2: WebSDR field length = 50
Enclosure 1, ASC 1377A

Page 25

SI Shipper's Identifying Number for Shipment (SID) 

DLMS Note:

This is the contractor-assigned shipment number, e.g. vendor shipments invoiced via the 

Mechanization of Contract Administration Services (MOCAS) system are identified by a 

shipment number formatted as three alpha and four numeric characters (may include 1 

position shipment number suffix).

For SI: WebSDR maximum field length = 22

TG Transportation Control Number (TCN) 

DLMS Note:

For TG: WebSDR field length = 17

TN Transaction Reference Number 

DLMS Note:

1. Use to indicate the requisition document number. This entry is required in DoD WebSDR.

2. The document number cited on SDRs prepared by the Distribution Depot for new 

procurement receipts (document type 9) and by the CCP (document type W), will be assigned 

for this purpose based upon the current date and the DoDAAC of the receiving depot or CCP.

3. For TN: WebSDR field length = 14

4. For SQCR, use to identify the applicable document number. (The SQCR document number 

can be a system-generated/assigned by the storage activity when a document number is no 

longer associated with the materiel in storage; field length = 14.

W4 Procurement Request Number 

DLMS Note:

1. Use to identify the purchase request number.

2. For W4: WebSDR field length = 13

WO Work Order Number 

DLMS Note:

1. Use to identify the Build Directive Number (BDN) for medical/surgical or other component 

assembly/kit. 

2. For future consideration, a data maintenance action was approved in X12 version 5010. 

The approved code/name is “BDN – Build Directive Number.”

XY

YM

‘

PGC

Other Unlisted Type of Reference Number 

DLMS Note:

1. Use to identify other unlisted type of transportation number.

2. For XY: WebSDR field length = 17 

Resource Screening Reference

DLMS Note:

1. Use to perpetuate the reference number (e.g., quality notification number) provided by the 

originating system to identify the stock screening request which resulted in this SQCR.

2. For YM: WebSDR field length = 14

Packing Group Code

DLMS Note:

For SQCR, use to indicate Condition of Packaging. Indicate packaging satisfactory with an “S” 

in REF02. Indicate packaging not satisfactory with a “U”. 

PGD

PWC

Downstream Package Identifier 

DLMS Note:

Storage activities must use to indicate original unopened packaging (yes/no) when reporting 

non-procurement materiel receipts in a suspended condition. Enter Y or N as applicable. 

Refer to ADC 1022.

Preliminary Work Candidate Number

DLMS Note:

1. For SQCR, use to identify a Requisition Alert Document Number to protect materiel for use 

by authorized local users at industrial work sites.

2. For SQCR, Authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381.

3. For PWC: WebSDR field length is 15
Enclosure 1, ASC 1377A

Page 26

REF02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

X AN 1/50 Must use 1

REF03 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: Use to identify the generatingsystem associated with the SDR report 

control number identified in the

REF01:

• WEBSDR - The DoD WebSDR control 

number must be perpetuated to all 

transactions once assigned

• ISDR - Distribution Standard System (DSS) 

Incoming SDR 

• ADRS - DSS Automated Discrepancy 

Reporting System

• BSM - DLA Enterprise Business System 

(EBS) (formerly Business System 

Modernization)

• LMP - Army Logistics Modernization 

Program)

• NAVSEA-PDREP - Product Data Reporting 

and Evaluation Program Automated 

Information System (Navy-sponsored multiService use)

• D035K - Air Force Stock Control System

• ESS - Air Force Enterprise Solution-Supply 

• ILCO - Air Force Security Assistance and 

Cooperation Directorate SDR-Automation 

(SDR-A) 

• GSA - GSA Vision system

• WMS- Warehouse Management 

System

2. Use with originator’s SQCR report 

control number (REF01=NN) to identify 

the generating-system.

X AN 1/80 Used 1

REF04 C040 Reference Identifier

 

Description: To identify one or more 

reference numbers or identification numbers 

as specified by the Reference Qualifier

DLMS Note: Must use to identify the 

requisition document number. Use multiple 

Reference Identification pairs as needed.

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

M ID 2/3 Must use 1

Code Name

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 intra-DLA use when the 

controlling document number for the shipment is not the DTID used for tracking the property. 

Refer to ADC 459.
Enclosure 1, ASC 1377A

Page 27

3. When there is no Suffix Code (REF04 Code W8), associated with the controlling Document 

Number, enter the correlating DTID in the REF04-02. If there is a Suffix Code, then enter the 

DTID in the REF04-04. DLMS enhancement, see ADC 466.

W8 Suffix 

DLMS Note:

1. When citing the requisition number (using Transaction Reference Number, Code TN), use 

to identify the document number suffix if one is provided.

2. For W8: WebSDR field length = 1

3. For SQCR, when used in association with the Requisition Alert Document Number 

(Qualifier PWC, above), this will be the requisition alert document suffix. The Requisition Alert 

Document Number Suffix is an Authorized DLMS enhancement under DLA industrial activity 

support agreement. Refer to ADC 381 .

PSM Credit Card 

DLMS Note:

Only send this value when citing the requisition number (using Transaction Reference 

Number, Code TN) and enter a "Y" indicator to indicate payment by either Government 

purchase card or commercial credit card. 

URL Uniform Resource Locator 

DLMS Note:

1. Only send this value when citing the requisition number (using Transaction Reference 

Number, Code TN) and enter a "Y" indicator to indicate payment by either Government 

purchase card or commercial credit card.

2. When a FedMall Indicator is needed following a Document Number Suffix, use W8 at this 

position and supply the FedMall Indicator in the following 2/REF04-03/0700. Refer to ADC 

1354.

REF04-02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

M AN 1/50 Must use 1

REF04-03 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

X ID 2/3 Used 1

Code Name

60 Account Suffix Code 

DLMS Note:

1. Use in conjunction with the DTID Number (REF04 Code W1) to identify the DTID Number 

Suffix Code, when applicable. 

2. When the DTID Number is provided in REF04-02, enter the correlating DTID Suffix using 

this location. DLMS enhancement, see ADC 466.

W1 Disposal Turn-In Document Number 

DLMS Note:

1. Use in conjunction with the controlling document number (REF01 Code TN) to identify the 

applicable DTID Number. Applicable on the SDR for intra-DLA use when the controlling 

document number for the shipment is not the DTID used for tracking the property. 

2. When there is no Suffix Code (REF04 Code W8), associated with the controlling Document 

Number, enter the correlating DTID in the REF04-02. If there is a Suffix Code, then enter the 

DTID in the REF04-04. DLMS enhancement, see ADC 466.

URL Uniform Resource Locator 

DLMS Note:

Use to provide the FedMall Indicator when following a Document Number Suffix (qualifier W8 

at 2/REF04-01/0700). Refer to ADC 1354.

REF04-04 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

X AN 1/50 Used 1
Enclosure 1, ASC 1377A

Page 28

Qualifier

REF04-05 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

X ID 2/3 Used 1

Code Name

60 Account Suffix Code 

DLMS Note:

1. Use in conjunction with the DTID Number (REF04 Code W1) to identify the DTID Number 

Suffix Code, when applicable. 

2. When the DTID Number is provided in REF04-04, enter the correlating DTID Suffix using 

this location. DLMS enhancement, see ADC 466.

REF04-06 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

X AN 1/50 Used 1
Enclosure 1, ASC 1377A

Page 29

CS Contract Summary Pos: 0750 Max: 1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To provide information about a contract

Syntax Rules: 

1. P0405 - If either CS04 or CS05 is present, then the other is required.

Semantics: 

1. CS09 is the permissible overage as a percentage of the total contract line item number (CLIN) quantity.

2. CS10 is the permissible shortage as a percentage of the total contract line item number (CLIN) quantity.

3. CS11 is the permissible overage dollar value specified by the contract above which discrepancy action is taken.

4. CS14 is the Unit of Measure stipulated in the contract.

5. CS15 is the contract line item number (CLIN) unit price specified in the contract.

6. CS17 conveys the Critical Application Indicator. A "Y" indicates that a Critical Application Indicator is specified in the contract; an "N" 

indicates that no Critical Application Indicator is specified in the contract.

7. CS18 conveys the Special Requirements Indicator. A "Y" indicates that a Special Requirements Indicator (requiring special testing and or 

evaluation) is specified in the contract; an "N" indicates that no Special Requirements Indicator is specified in the contract.

Comments: 

1. CS04 may be used to identify the Contract Line Item Number (CLIN) or Extended (or Exhibit) Line Item Number (ELIN).

2. CS07 and CS13 can be used to indicate two different types of special services required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CS01 367 Contract Number

 

Description: Contract number

DLMS Note: Use to identify the procurement 

instrument identifier (PIID). Use the legacy 

procurement instrument identification 

number (PIIN) pending transition to the PIID. 

When a contract is issued under a PIID 

call/order number (F or M in 9th position), 

provide the value in the PIID field. 

O AN 1/30 Used 1

CS03 328 Release Number

 

Description: Number identifying a release 

against a Purchase Order previously placed 

by the parties involved in the transaction

DLMS Note: 1. Use to identify the call or 

order number if applicable.

2. Use to identify the legacy four-position 

call/order number associated with the PIIN. 

3. Do not use for the PIID call/order number. 

The PIID call/order number is mapped to 

CS01. Refer to ADC 1161.

O AN 1/30 Used 1

CS04 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

X ID 2/3 Used 1

Code Name

C7 Contract Line Item Number 

DLMS Note:

Use as needed to identify the CLIN or the CLIN including the SUBCLIN, as appropriate.

CS05 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

X AN 1/50 Used 1
Enclosure 1, ASC 1377A

Page 30

PWK Paperwork Pos: 1020 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To identify the type or transmission or both of paperwork or supporting information

Syntax Rules: 

1. P0506 - If either PWK05 or PWK06 is present, then the other is required.

Comments: 

1. PWK05 and PWK06 may be used to identify the addressee by a code number.

2. PWK07 may be used to indicate special information to be shown on the specified report.

3. PWK08 may be used to indicate action pertaining to a report.

DLMS Note:

Use a separate PWK segment for each attachment identified by filename. Repeat up to five times..

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PWK01 755 Report Type Code

 

Description: Code indicating the title or 

contents of a document, report or supporting 

item

DLMS Note: The following codes are 

authorized. 

M ID 2/2 Must use 1

Code Name

AE Attachment 

DLMS Note:

1. Use to indicate that supporting documentation has been provided electronically in the form 

of images or files and is available for download from the DoD WebSDR.

2. Use with Code FT (PWK02) when a file is transmitted electronically between the DoD 

WebSDR and the interfacing application.

R6 Miscellaneous Information 

DLMS Note:

Use to indicate that additional information is being submitted to the action activity off-line. 

PWK02 756 Report Transmission Code

 

Description: Code defining timing, 

transmission method or format by which 

reports are to be sent

O ID 1/2 Used 1

Code Name

FT File Transfer 

DLMS Note:

1. Use to indicate attachment is being sent electronically in a separate transmission.

2. Up to five attachments may be sent per transaction.

3. Information copies generated by WebSDR/DAAS (BNR01=22) will carry the attachments 

associated with the original report.

PWK07 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: 1. Use to indicate the SDR 

Attachment File Name being sent 

electronically in a separate transmission. 

Refer to ADC 311.

2. WebSDR field length = 50.

O AN 1/80 Used 1
Enclosure 1, ASC 1377A

Page 31

LM Code Source Information Pos: 1040 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use to identify coded information maintained in department or agency documentation. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
Enclosure 1, ASC 1377A

Page 32

LQ Industry Code Pos: 1050 Max: >1

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Used

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

 

Description: Code identifying a specific 

industry code list

DLMS Note: The following codes are 

authorized. 

O ID 1/3 Must use 1

Code Name

D Court Document Type Code 

DLMS Note:

1. Must use to identify the Discrepancy Report Document Type Code 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:

• 5- Storage Quality Control Report (SQCR)

• 6 - Customer originated, direct vendor/contractor 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/other. 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 procurement source receipt

• 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 procurement source receipt (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 

differ significantly from other SDR types.

I 40 Type Pack Code 

DLMS Note:

1. Use to identify the DoD Type of Pack Code. May be provided when reporting packaging 

discrepancies. Required for CCP-originated discrepancies.

2. For 40: WebSDR field Length = 2

83 Supply Condition Code 

DLMS Note:

1. Use to identify the condition of the materiel as intended for shipment. Applicable to 

condition code discrepancies where the condition upon receipt is later specified.

2. For SQCR, reclassification condition code (Condition Code To) is identified using Qualifier 

BG.
Enclosure 1, ASC 1377A

Page 33

85 Country and Activity Code 

DLMS Note:

1. Use to identify the Security Cooperation Customer Code.

2. For 85: WebSDR field length = 2

A4 Case Designator Number 

DLMS Note:

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

A9

BG

Supplemental Data 

DLMS Note:

1. Use to identify supplemental address/data.

2. During the DLSS/DLMS transition, this field will be used to perpetuate/populate the DLSS 

Supplemental Address (SUPAAD) field. During this time, field size is restricted to 6 positions.

3. For A9: WebSDR field length = 6 

Condition

DLMS Note:

For SQCR, use for supply condition code after reclassification (Supply Condition Code-To)

DE Signal Code

DG Fund Code

EQ

EZ 

Controlled Inventory Item Code

Type Inspection Code

DLMS Note:

For SQCR must use to indicate type of inspection.

C= Visual (COSIS) Inspection

F=Safety of Flight (SOF) Inspection (includes Aviation Safety Action Message (ASAM)

P=Special Inspection at Single Location

Q=Quality Related Inspection

R=Reimbursement Special Inspection

S=Shelf life Inspection

U=Safety of Use Inspection

X=Critical Safety Item (CSI) Inspection

Z=Suspect Counterfeit Inspection

FD Demilitarization Code

GQ Group Qualifier Code 

DLMS Note:

Use to identify the Material Management Aggregation Code (MMAC) for NSNs to be managed 

by a specific manager (i.e., System, program, aggregation, selected FSC, technology group). 

This is an Air Force-unique data element meaningful to the Air Force only. Non-Air Force 

components perpetuate without action.

A data maintenance action was approved in version 5010. The approved code/name is "MAC 

– Material Management Aggregation Code". The code source is identified as the Air Force 

Manual (AFMAN) 23-110, Volumes 1 and 2.

HB

 

Discrepancy Advice Code 

DLMS Note:

1.Use to identify the SDR Action Code indicating the initiator's requested action.

2. For SQCRs only authorized Action Code is 1A.

 

ST Special Marketing Type Code 

DLMS Note:

1. Use to identify the DLA Disposition Services SDR Type Code 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
Enclosure 1, ASC 1377A

Page 34

 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.

TG Title Document Code List 

DLMS Note:

1. Use on SA SDR to identify the SA Document Number Requirement Type as one of the 

following: Follow-on Support Requirement (FSR), Government Furnished Equipment/Materiel 

(GFE), System Sale (SYS), Repair/Replace Requirement (RRP), Repair/Return Requirement 

(RPT), or World Wide Redistribution System Requirement (WWR). An ANSI data 

maintenance action will be taken to obtain a more appropriate code for use in a future 

version/release.

2. For TG: WebSDR field length = 3

TR Report Code 

DLMS Note:

1. Use for SA SDR to identify the SDR initiating office (SIO).

2. For TR: WebSDR field length = 1

COG Cognizance Symbol 

DLMS Note:

Use to identify the materiel cognizance symbol (COG) of the end item. Applicable to US Navy 

only.

LQ02 1271 Industry Code

 

Description: Code indicating a code from a 

specific industry code list

X AN 1/30 Must use 1
Enclosure 1, ASC 1377A

Page 35

FA1 Type of Financial Accounting Data Pos: 1350 Max: 1

Detail - Optional

Loop: FA1 Elements: 1

User Option (Usage): Used

Purpose: To specify the organization controlling the content of the accounting citation, and the purpose associated with the accounting citation

Semantics: 

1. FA101 Identifies the organization controlling the assignment of financial accounting information.

2. FA102 Identifies the purpose of the accounting allowance or charge information.

DLMS Note: 

Not Used in SQCR

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA101 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values

DLMS Note: This data element is required 

for X12 syntax. Select the code that 

corresponds to the organization that is 

responsible for the assignment of the 

DoDAAC used to construct the controlling 

document number for the transaction.

M ID 2/2 Used 1

Code Name

DF Department of Defense (DoD) 

DLMS Note:

Use to indicate that the Component is a Department of Defense agency, including Defense 

Logistics Agency. Refer to ADC 1043.

DN Department of the Navy 

DLMS Note:

Includes the United States Marine Corps.

DY Department of Air Force

DZ Department of Army

FG Federal Government
Enclosure 1, ASC 1377A

Page 36

FA2 Accounting Data Pos: 1360 Max: >1

Detail - Mandatory

Loop: FA1 Elements: 2

User Option (Usage): Must use

Purpose: To specify the detailed accounting data

DLMS Note:

1. Use this segment to comply with the DoD SLOA/Accounting Classification only when submitting an SDR using a constructed document 

number (not applicable to Security Assistance). Cost object elements Project Identifier, Funding Center Identifier, Functional Area, Cost 

Element Code, Cost Center Identifier, Activity Identifier, and Work Order Number are used as appropriate for the system.

2. Not used in SQCR

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA201 1196 Breakdown Structure Detail Code 

Description: Codes identifying details 

relating to a reporting breakdown structure 

tree

M ID 2/2 Used 1

Code Name

89 Budget Line Item Identification 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Budget Line Item”. Refer to ADC 

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

90 Project/Task 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Project Identifier”. Refer to ADC 

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

A1 Department Indicator 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Department Regular”. Refer to 

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

A2 Transfer from Department 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Department Transfer”. Refer to 

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

A4 Basic Symbol Number 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Main Account”. Refer to ADC 

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

A5 Sub-class 

DLMS Note:

1. Reserved for DoD SLOA/Accounting Classification use to identify “Sub Class”. Refer to 

ADC 1043.

2. Sub Class is a potential future DLMS enhancement. Components must coordinate 

requirements and business rules with EBSO prior to use.

A6 Sub-Account Symbol 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Sub Account”. Refer to ADC 

1043.
Enclosure 1, ASC 1377A

Page 37

2. Authorized DLMS enhancement; see introductory DLMS note 5.

AI Activity Identifier 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Activity Identifier”. Refer to ADC 

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

3. Qualifier AI is a migration code approved for use in X12 version 7020.

B2 Budget Sub-activity Number 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Sub-Allocation (formerly known as 

Limit/Subhead)”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

BE Business Event Type Code 

DLMS Note:

1. Reserved for DoD SLOA/Accounting Classification use to identify “Business Event Type 

Code”. Refer to ADC 1043.

2. Business Event Type Code is a potential future DLMS enhancement. Components must 

coordinate requirements and business rules with EBSO prior to use.

3. Qualifier BE is a migration code approved for use in X12 version 7020.

C3 Budget Restriction 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Availability Type”. Refer to ADC 

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

CC Cost Center Identifier 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Center Identifier”. Refer to 

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

3. Qualifier CC is a migration code approved for use in X12 version 7020.

F1 Object Class 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Object Class”. Refer to ADC 

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

FA Functional Area 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Functional Area”. Refer to ADC 

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

3. Qualifier FA is a migration code approved for use in X12 version 7020.

FC Funding Center Identifier 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Funding Center Identifier”. Refer 

to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

3. Qualifier FC is a migration code approved for use in X12 version 7020.

FT Funding Type 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Reimbursable Flag”. Refer to 
Enclosure 1, ASC 1377A

Page 38

ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 5.

H1 Cost Code 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to 

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

L1 Accounting Installation Number 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Agency Accounting Identifier”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 5.

P1 Disbursing Station Number 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Agency Disbursing Identifier 

Code”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

WO Work Order Number 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Work Order Number”. Refer to 

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 5.

3. Qualifier WO is a migration code approved for use in X12 version 7020.

YB Beginning Period of Availability 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Beginning Period of Availability 

Fiscal Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer 

to ADC 1043B.

3. Authorized DLMS enhancement; see introductory DLMS note 5.

4. Qualifier YB is a migration code approved for use in X12 version 7020.

YE Ending Period of Availability 

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Ending Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 5.

3. Qualifier YE is a migration code approved for use in X12 version 7020.

FA202 1195 Financial Information Code

 

Description: Code representing financial 

accounting information

M AN 1/80 Used 1
Enclosure 1, ASC 1377A

Page 39

NCD Nonconformance Description Pos: 2300 Max: 1

Detail - Optional

Loop: NCD Elements: 2

User Option (Usage): Used

Purpose: To describe the nonconformance condition

Syntax Rules: 

1. R0102 - At least one of NCD01 or NCD02 is required.

DLMS Note:

1. Use to reflect information related to the nonconformance condition and identify related organizations.

2. Must use one NCD loop for in each IUID loop. Use a new IUID loop for each item.

3. The IUID content is an authorized DLMS enhancement; refer to introductory DLMS Note 5 on the IC cover page.

4. For SQCR, use this segment to satisfy X12 syntax requirements.

5. For SQCR, being a new NCD loop for each IUID. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

NCD02 888 Nonconformance Determination Code

 

Description: Code indicating whether a 

nonconforming condition was the reason for 

submitting or the basis upon which a 

nonconformance report is initiated

X ID 1/1 Must use 1

Code Name

5 Discrepant 

DLMS Note:

For SDR/SQCR for all transactions, use to satisfy ANSI requirement.

NCD03 350 Assigned Identification

 

Description: Alphanumeric characters 

assigned for differentiation within a 

transaction set

DLMS Note: 1. Use as a counter to satisfy 

ANSI syntax. Must cite numeric 1 pending 

future enhancement to support additional 

NCD loops for multiple missing component 

parts or multiple incorrect items received.

2. When providing item unique identification 

due to a mismatch (including 

shortage/overage) resulting from 

comparison between shipping notice, due-in, 

or documentation, and the packaging or 

item, follow the numeric counter by an 

indicator to distinguish the item(s) received 

from the anticipated item(s) not received. 

Suffix the counter by the letter R for items 

received and N for items not received. See 

ADC 1030.

3. Use of this looping structure to describe 

multiple incorrect items received in 

association with Discrepancy Code W5, 

Mixed Stock, is reserved for future 

implementation. 

4. Use of this looping structure to describe 

multiple missing component parts is 

reserved for future implementation.

O AN 1/20 Must use 1
Enclosure 1, ASC 1377A

Page 40

NTE Note/Special Instruction Pos: 2400 Max: >1

Detail - Optional

Loop: NCD Elements: 2

User Option (Usage): Used

Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction

Comments: 

1. The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processible. The 

use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

DLMS Note:

Use any code listed for SDR. For SQCR, only use Code RPT 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

NTE01 363 Note Reference Code

 

Description: Code identifying the functional 

area or purpose for which the note applies

DLMS Note: The following codes are 

authorized.

O ID 3/3 Must use 1

Code Name

ACI Additional Claim Information 

DLMS Note:

Use to identify the narrative comments associated with a contested SDR or request for 

reconsideration.

ACN Action Taken 

DLMS Note:

Use to identify the narrative comments which describe the action taken by the initiator in 

regard to an SA product quality deficiency.

APS Appropriation Specifications 

DLMS Note:

Use to identify funding and accounting information provided by the submitter.

CIR Circumstances Prior to Difficulty 

DLMS Note:

Use to identify the narrative comments which describe the circumstances prior to difficulty in 

regard to an SA product quality deficiency.

COD Corrected Data 

DLMS Note:

Use to identify the narrative comments associated with and SDR correction/change.

DGN Diagnosis Description 

DLMS Note:

Use to identify the narrative comments which describe the suspected cause identified by the 

initiator in regard to an SA product quality deficiency.

EBK Other Reason for Withdrawal 

DLMS Note:

Use to identify the narrative comments associated with cancellation of an SDR.

ODD Originator Deficiency Description 

DLMS Note:

Use to identify the narrative comments which describe the deficiency by the initiator in regard 

to an SA product quality deficiency.

POL Property Owner Location Information 

DLMS Note:

Use to identify the location of discrepant/deficient materiel.

REC Recommendation 

DLMS Note:

Use to identify the narrative comments which describe the initiator's recommendation in 

regard to an SA product quality deficiency.
Enclosure 1, ASC 1377A

Page 41

RPT Report Remarks 

DLMS Note:

1. Use to identify the narrative comments associated with the SDR. Narrative comments are 

mandatory for New Original (00) SDRs, with the exception being New Original (00) SDRs 

submitted with Action Code 1H or 3B do not require narrative comments.

2. CCP-generated SDRs prepared at the TCN level may use the remarks block to identify 

specific document numbers consolidated on the shipment or other detailed information where 

available.

3. Use to indicate findings and recommendations form SQCR. Provide details of cause and 

nature of defect, malfunction, or repair. (Total field size for remarks is restricted to 750 

characters).

RST Place Where a Report was Submitted 

DLMS Note:

1. Use to identify remarks provided by the action activity to which the SDR was originally 

submitted. This is an additional separate remarks block for the purpose for relaying the 

original action activity’s reply remarks when the SDR has been forwarded to a new activity 

using forwarding Reply Code 504. 

2. Remarks will be perpetuated to new original report as originally provided on the reply 

transaction (limited to 500 positions).

3. This is an enhancement for future implementation planned for _______________.

SSC Status Comment 

DLMS Note:

Use to identify the narrative comments associated with an SDR followup.

TPO Third Party Organization Notes 

DLMS Note:

Use to identify remarks provided by the ILCO. 

A data maintenance action was approved in version 5020. The approved code/name is "ILC -

International Logistics Control Office".

WHI Warehouse Instruction 

DLMS Note:

1. Use to identify Instructions to Depot remarks. May be used by the materiel owner to 

provide instructions or additional information to the distribution depot.

2. This is a separate additional remarks block reserved for use in association with SDR 

reports forwarded transactionally by the primary action activity to a distribution depot for 

research using Beginning Segment Code 47.

NTE02 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: 1. Use multiple repetitions of 

NTE, with up to 80 positions for each line. 

WebSDR maximum field for note = 500.

2. Special characters are not allowed except 

as identified. Valid characters are: @ # $ ( ) 

- = + , / \ [ ] : . and ?

M AN 1/80 Must use 1
Enclosure 1, ASC 1377A

Page 42

DTM Date/Time Reference Pos: 2500 Max: >1

Detail - Optional

Loop: NCD Elements: 6

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. C0403 - If DTM04 is present, then DTM03 is required.

2. P0506 - If either DTM05 or DTM06 is present, then the other is required.

3. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

DLMS Note:

For SDR and SQCR use in IUID loop to associate a date with a specific batch/lot or item as identified by UII or serial number.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

 

Description: Code specifying type of date 

or time, or both date and time

M ID 3/3 Used 1

Code Name

512 Warranty Expiration 

DLMS Note:

Reserved for future use. Not available at this time.

DTM02 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year

X DT 8/8 Used 1

DTM03 337 Time

 

Description: Time expressed in 24-hour 

clock time as follows: HHMM, or HHMMSS, 

or HHMMSSD, or HHMMSSDD, where H = 

hours (00-23), M = minutes (00-59), S = 

integer seconds (00-59) and DD = decimal 

seconds; decimal seconds are expressed as 

follows: D = tenths (0-9) and DD = 

hundredths (00-99)

X TM 4/8 Used 1

DTM04 623 Time Code

 

Description: Code identifying the time. In 

accordance with International Standards 

Organization standard 8601, time can be 

specified by a + or - and an indication in 

hours in relation to Universal Time 

Coordinate (UTC) time; since + is a 

restricted character, + and - are substituted 

by P and M in the codes that follow

All valid standard codes are used.

O ID 2/2 Used 1

DTM05 1250 Date Time Period Format Qualifier 

Description: Code indicating the date 

format, time format, or date and time format

All valid standard codes are used.

X ID 2/3 Used 1

DTM06 1251 Date Time Period

 

Description: Expression of a date, a time, 

or range of dates, times or dates and times

X AN 1/35 Used 1
Enclosure 1, ASC 1377A

Page 43

REF Reference Identification Pos: 2600 Max: >1

Detail - Optional

Loop: NCD Elements: 4

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

1. Use in 2/HL/0100 IUID loop to provide IUID information. Repeat the REF segment within each IUID loop to identify relevant IUID 

information.

2. In support of Financial Improvement and Audit Readiness (FIAR) compliance, capital equipment candidates require serialization data 

visibility. Submitters must prepare SDRs citing the applicable serial number(s) as mandatory, and when available, include UIIs, when IUID is 

appropriate for the type of discrepancy (e.g., wrong item, shortage/overage, receipt in a condition other than expected, or a serial number/UII 

mismatch between the item and documentation). Refer to ADC 1198.

3. Under DOD IUID policy, UIT programs require serialization data visibility. Submitters must prepare SDRs citing the applicable serial 

number(s) as mandatory, and when available, include UIIs, when appropriate for the type of discrepancy (e.g., wrong item, shortage/overage, 

receipt in a condition other than expected, or a serial number/UII mismatch between the item and documentation). Refer to ADC 1244.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

DLMS Note: 1. For DLMS use, the following 

codes are authorized.

2. Use codes separately or in combination, 

to identify appropriate information for DoD 

IUID Supply Policy, including, but not limited 

to unique item tracking (UIT) programs. 

Authorized DLMS Enhancement. See ADC 

1030.

3. For SQCR use Code: BT, SE, U3

M ID 2/3 Must use 1

Code Name

BT Batch Number 

DLMS Note:

1. Use in IUID loop to identify the batch, lot, or production run related to the discrepant 

materiel.

2. The batch/lot number may not exceed 20 characters in accordance with IUID policy.

M1 Material Storage Location 

DLMS Note:

Use on SA SDR to identify the storage location where the discrepant materiel is being held. 

This information is needed to calculate a transportation reimbursement to the customer, if 

applicable and provide adequate disposition instructions for the return of materiel. Material 

Storage Location is not applicable for non-receipts. Cite one of the listed codes in the REF02. 

Refer to ADC 1203.

USG for U.S. Government Facility

ICD for In-Country Depot

FFD for Freight Forwarder

CON for Contractor Facility
Enclosure 1, ASC 1377A

Page 44

NS National Stock Number 

DLMS Note:

1. Use to identify the missing component by NSN.

2. For NS: WebSDR field length = 13 

PM Part Number 

DLMS Note:

Use to identify the missing component by part number or description.

SE Serial Number 

DLMS Note:

1. Use in IUID loop to identify the serial number.

2. The serial number may not exceed 30 characters and may only include alpha numeric 

characters, dashes and forward slashes. Spaces are not allowed.

U3 Unique Supplier Identification Number (USIN) 

DLMS Note:

1. Use in IUID loop to identify the UII value. Cite the UII in REF03.

A data maintenance action was approved in version 5020. The approved code/name is "UII -

Department of Defense Unique Item Identifier.

2. The UII may not exceed 50 characters in accordance with IUID Policy.

XA Substitute National Stock Number 

DLMS Note:

1. Use to identify the incorrect (wrong) item received by NSN. 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

REF02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

DLMS Note: Use to indicate serial number 

when REF01=SE.

X AN 1/50 Used 1

REF03 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: Use to indicate UII value when 

REF01 = U3.

X AN 1/80 Used 1

REF04 C040 Reference Identifier

 

Description: To identify one or more 

reference numbers or identification numbers 

as specified by the Reference Qualifier

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

M ID 2/3 Must use 1

REF04-02 127 Reference Identification

 

M AN 1/50 Must use 1
Enclosure 1, ASC 1377A

Page 45

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

REF04-03 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

All valid standard codes are used.

X ID 2/3 Used 1

REF04-04 127 Reference Identification 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

X AN 1/50 Used 1
Enclosure 1, ASC 1377A

Page 46

QTY Quantity Pos: 2700 Max: >1

Detail - Optional

Loop: NCD Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

1. E0204 - Only one of QTY02 or QTY04 may be present.

2. R0204 - At least one of QTY02 or QTY04 is required.

Semantics: 

1. QTY04 is used when the quantity is non-numeric.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

 

Description: Code specifying the type of 

quantity

DLMS Note: The following codes are 

authorized. 

M ID 2/2 Must use 1

Code Name

17 Quantity on Hand 

DLMS Note:

1. Use to identify the quantity in stock when reporting product quality deficient materiel. 

2. For 17: WebSDR field length = 7

39 Shipped Quantity

75 Receipts 

DLMS Note:

1. Use to indicate the number of incorrect (wrong) items received. 

2. For 75: WebSDR field length = 7

86 Nonconformance Quantity 

DLMS Note:

1. Must be used to indicate the discrepant/deficient quantity for SDRs/SQCRs.

2. By exception, may be blank for CCP originated SDRs (Document Type= W). Refer to ADC 

282.

3. For 86: WebSDR field length = 7

87 Quantity Received 

DLMS Note:

For 87: WebSDR field length = 7

9A Time Expended 

DLMS Note:

1 Use to indicate the time expended to conduct the inspection expressed as labor hours and 

minutes. Field length is five positions formatted as HHHMM, and must include leading and 

training zeros as necessary to fill the length requirement. Allowable minutes (MM) are 00-59. No 

decimal point is allowed. Provide the expended time value in QTY02, and use with QTY03=LH 

to indicate the unit of measure is Labor Hours. 

2 This qualifier is not currently being used. It is being retained pending a possible SDR/SQCR 

requirement from DLA Distribution.

D1 Billed 

DLMS Note:

For D1: WebSDR field length = 7
Enclosure 1, ASC 1377A

Page 47

FL Units 

DLMS Note:

1. Use to identify the number of discrepant pieces as specified by the type of pack, e.g., the 

number of discrepant boxes, skids, etc when reporting a packaging discrepancy. May be 

provided when reporting packaging discrepancies. Required for CCP-originated 

discrepancies. 

2. When used the value for type pack is identified from the DoD code list (2/LQ01/1050). Unit 

of issue is not used.

3. For FL: WebSDR field Length = 3

OT Number of Operating Periods at Failure 

DLMS Note:

1. Use to indicate the operating time at the time of failure of the discrepant item. Expressed 

as 4 numeric hours and 2 position minutes.

2. For OT: WebSDR field length = 50

SW Sample Amount 

DLMS Note:

Use to indicate the Number of Samples Examined.

VR Variance 

DLMS Note:

Use to indicate the number of missing component parts.

QTY02 380 Quantity

 

Description: Numeric value of quantity

X R 1/15 Must use 1

QTY03 C001 Composite Unit of Measure

 

Description: To identify a composite unit of 

measure(See Figures Appendix for 

examples of use)

DLMS Note: 1. Use to identify the 

discrepant/deficient quantity. Use multiple 

repetitions as needed to identify additional 

quantities associated with the complaint. 

2. DLMS users see the Unit of Issue and 

Purchase Unit Conversion Table for 

available codes.

O Comp Used 1

QTY03-01 355 Unit or Basis for Measurement Code

 

Description: Code specifying the units in 

which a value is being expressed, or manner 

in which a measurement has been taken

DLMS Note: Use to identify the unit of issue.

M ID 2/2 Must use 1
Enclosure 1, ASC 1377A

Page 48

AMT Monetary Amount Pos: 2730 Max: >1

Detail - Optional

Loop: NCD Elements: 3

User Option (Usage): Used

Purpose: To indicate the total monetary amount

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

AMT01 522 Amount Qualifier Code

 

Description: Code to qualify amount

DLMS Note: The following codes are 

authorized. 

M ID 1/3 Must use 1

Code Name

10 Shipment Value in U.S. Dollars 

DLMS Note:

1. Use to indicate the total dollar value of the discrepant materiel.

2. For 10: WebSDR field length = 13

Z1 Repackaging Labor Cost 

DLMS Note:

1. Use to indicate repackaging labor costs. Cost may be estimated. Refer to ADC 1310. 

2. For Z1: WebSDR field length = 12

Z2 Repackaging Material Cost 

DLMS Note:

1. Use to indicate repackaging materiel costs. Cost may be estimated. Refer to ADC 1310.

2. For Z2: WebSDR field length = 12

Z3 Unit Cost of Discrepant Material 

DLMS Note:

1. Use to identify the unit value (price) of the discrepant materiel.

2. For Z3: WebSDR field length = 11

RPC Repackaging Cost 

DLMS Note:

1. Use to include the dollar value for corrective action. Include materiel and labor needed to 

complete a packing, packaging, preservation, palletization and/or marking project. Cost may 

be estimated when submitting the SDR for disposition instructions. Cost must be actual when 

submitting the SDR for reimbursement of corrective action already taken. Refer to ADC 1310.

2. Use with Estimated/Actual Cost Flag (AMT03) and specify in SDR remarks if repackaging 

cost is estimated or actual pending DoD-wide implementation of ADC 1203. Refer to ADC 

1310.

3. For RPC: WebSDR field length = 12

AMT02 782 Monetary Amount

 

Description: Monetary amount

DLMS Note: Dollar values may be 

expressed in whole dollars (with no decimal) 

or in dollar and cents (with a decimal 

included).

M R 1/18 Must use 1

AMT03 478 Credit/Debit Flag Code

 

Description: Code indicating whether 

amount is a credit or debit

DLMS Note: Use to identify the 

Estimated/Actual Cost Flag when requesting 

credit for repackaging cost. Must use only 

with Code RPC (Repackaging Cost). Refer 

to ADC 1203.

O ID 1/1 Used 1
Enclosure 1, ASC 1377A

Page 49

Code Name

A Actual 

DLMS Note:

1. Use to indicate that the dollar amount provided represents the actual cost. 

2. Local code A is established for use in 842A/W Version 4030. A data maintenance action 

will be submitted to establish this code in a future version of the X12 standard.

E Estimated 

DLMS Note:

1. Use to indicate that the dollar amount provided represents an estimated cost.

2. Local code E is established for use in 842A/W Version 4030. A data maintenance action 

will be submitted to establish this code in a future version of the X12 standard.
Enclosure 1, ASC 1377A

Page 50

N1 Name Pos: 2800 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. P0304 - If either N103 or N104 is present, then the other is required.

2. R0203 - At least one of N102 or N103 is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

DLMS Note: The following codes are 

authorized. 

M ID 2/3 Must use 1

Code Name

42 Component Manufacturer 

DLMS Note:

Use with REF01 PM to identify the CAGE code of the manufacturer of the missing component.

BT Bill-to-Party 

DLMS Note:

1. Use for SFIS compliant systems to identify the BPN of the party to receive the bill. BPN 

may only be used when the corresponding DoDAAC is also provided. This will require a 

second iteration of the N1 loop with the same qualifier.

2. Authorized DLMS enhancement; see introductory note 6.

C4 Contract Administration Office 

DLMS Note:

1. Use to identify the DoDAAC of Contract Administration Office (CAO) for the identified 

contract number.

2. Populated via EDA interface with WebSDR when available for contract-related discrepant 

shipments.

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) and SQCR (Type 5)

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.
Enclosure 1, ASC 1377A

Page 51

LW Customer 

DLMS Note:

Use to identify the SDR report initiator by DoDAAC (if not identified by 1/N101/1200/41).

MF Manufacturer of Goods 

DLMS Note:

1. Use to identify the manufacturer by name and/or CAGE Code. Applicable to expired shelflife or product quality discrepancies.

2. For MF: WebSDR field length = 20 if clear text is used

SH Shipper 

DLMS Note:

1. Use to identify the shipping activity by Routing Identifier Code, DoDAAC, or 

vendor/contractor CAGE code.

2. This will be the returning activity DoDAAC for SDRs associated with storage activity 

receipts of returns/retrograde shipments.

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.

Z6 Transferring Party 

DLMS Note:

Use on forwarded SDRs to identify the Routing Identifier of the previous action party. This is 

the party forwarding the SDR.

ZB Party to Receive Credit 

DLMS Note:

1. Use for SFIS compliant systems to identify the BPN of the party to receive credit. BPN may 

only be used when the corresponding DoDAAC is also provided. This will require a second 

iteration of the N1 loop with the same qualifier.

2. Authorized DLMS enhancement; see introductory note 6.

DIR Distribution Recipient 

DLMS Note:

1. Use to identify the recipient of the distribution copy forwarded by email or other nontransaction method.

2. For DIR: WebSDR field length = 50

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.

N102 93 Name

 

Description: Free-form name

DLMS Note: Use to identify the name of the 

manufacturer.

X AN 1/60 Used 1

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

Identification Code (67)

X ID 1/2 Used 1

Code Name

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)
Enclosure 1, ASC 1377A

Page 52

50 Business License Number 

DLMS Note:

1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the 

buyer’s BPN in N104.

2. Authorized DLMS enhancement; see introductory note 6.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

 

Description: Code identifying a party or 

other code

X AN 2/80 Used 1
Enclosure 1, ASC 1377A

Page 53

LM Code Source Information Pos: 3330 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use to identify agency unique coded data related to the characteristics and coding requirements for the nonconformance condition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code 

Description: Code identifying the agency 

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
Enclosure 1, ASC 1377A

Page 62

LQ Industry Code Pos: 3340 Max: >1

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Used

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

 

Description: Code identifying a specific 

industry code list

DLMS Note: The following codes are 

authorized. 

O ID 1/3 Must use 1

Code Name

BG Condition 

DLMS Note:

Use to identify the Supply Condition Code of the incorrect (wrong) item received.

EQ Controlled Inventory Item Code 

DLMS Note:

Use to identify the CIIC associated with the wrong item received.

FD Demilitarization Code 

DLMS Note:

Use to identify Demilitarization Code associated with the wrong item received.

GY Cause of Loss Code 

DLMS Note:

1. Use to identify the Cause Code. This is a DLA unique data element and is not applicable to 

other Components.

2. A data maintenance action was approved in version 5030. The approved code/name is 

"DCC - Cause Code". 

HA Discrepancy Code 

DLMS Note:

1. Use up to three repetitions to identify the discrepancy. (Note: Distribution Depot-originated

SDRs/SQCRs and their equivalents prepared via WebSDR use up to three discrepancy 

codes.)

2. Four-character packaging discrepancy codes are required on new submissions applicable 

to packaging discrepancies. (Refer to ADC 1059)

LQ02 1271 Industry Code

 

Description: Code indicating a code from a 

specific industry code list

X AN 1/30 Must use 1
Enclosure 1, ASC 1377A

Page 63

User Option (Usage): Used

Purpose: To specify the action that is to be taken in response to a nonconformance condition

Syntax Rules: 

1. P0405 - If either NCA04 or NCA05 is present, then the other is required.

2. R0203 - At least one of NCA02 or NCA03 is required.

Semantics: 

1. NCA03 describes the action that is to be undertaken.

Comments: 

1. NCA04 is used to specify the quantity that is associated with NCA02 or NCA03.

DLMS Note:

1.This segment is only used in SQCR.

2.Use this loop to identify Reclassification of Supplies Inspected. Repeat the NCA up to 20 times as needed for each combination of 

quantity/location. This loop may be used in two ways:

a. Use this loop inside the IUID NCD loop to provide reclassification information for the specified uniquely identified item/batch/lot.

b. If items are not uniquely identified, use this loop inside the Report NCD loop for each set of quantity/location.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

NCA02 887 Nonconformance Resultant Response Code

 

Description: Code identifying a response that is the 

result of a nonconformance situation

X ID 1/2 Used

Code Name

UC Other Action 

DLMS Note:

Use code UC to satisfy ANSI syntax.

NCA04 380 Quantity

 

Description: Numeric value of quantity

DLMS Note: Use to indicate Reclassification of 

Supplies Inspected Quantity. If used in the IUID loop, 

quantity will always be "1" to satisfy syntax.

X R 1/15 Used

NCA05 C001 Composite Unit of Measure

 

Description: To identify a composite unit of 

measure(See Figures Appendix for examples of use)

X Comp Used

NCA05-01 355 Unit or Basis for Measurement Code 

Description: Code specifying the units in which a 

value is being expressed, or manner in which a 

measurement has been taken

DLMS Note: 1. Use to identify the unit of issue. 

2. DLMS users see the DLMS Unit of Issue and 

Purchase Unit Conversion Table for available codes. 

M ID 2/2 Must use

NCA Nonconformance Action Pos: 3400 Max: 1

Detail - Optional

Loop: NCA Elements: 3
Enclosure 1, ASC 1377A

Page 64

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. P0304 - If either N103 or N104 is present, then the other is required.

2. R0203 - At least one of N102 or N103 is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

 

Description: Code identifying an organizational 

entity, a physical location, property or an individual

DLMS Note: For DLMS use, the following codes are 

authorized.

M ID 2/3 Must use

Code Name

L1 Inspection Location 

DLMS Note:

For SQCR use only. Use to identify the actual bin/shelf storage location for the inspected 

materiel. Maximum length is 16.

N102 93 Name

 

Description: Free-form name

X AN 1/60 Used

N1 Name Pos: 4100 Max: 1

Detail - Optional

Loop: N1 Elements: 2
Enclosure 1, ASC 1377A

Page 65

SE Transaction Set Trailer Pos: 4700 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Used

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending 

(SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SE01 96 Number of Included Segments

 

Description: Total number of segments 

included in a transaction set including ST 

and SE segments

M N0 1/10 Must use 1

SE02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set

DLMS Note: Cite the same number as the 

one cited in ST02.

M AN 4/9 Must use 1
 Enclosure 2, ASC 1377A

 Page 1 

Enclosure 2

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

Additions are identified by yellow highlight and deletions by single strike-through text.

842 Nonconformance Report

Functional Group=NC

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Nonconformance Report Transaction 

Set (842) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report products and 

processes that do not fulfill specifications or requirements. The Nonconformance Report Transaction Set provides the ability for the sender to 

report the nonconformance at the level of detail that is required. It also provides the ability to report the specific nonconformances of a 

component/part while identifying the assembly as the product that is in nonconformance. The Nonconformance Report Transaction Set may be 

used to report, initiate, or request actions related to the nonconformance being reported. Financial and accounting information is provided for 

reporting purposes only. The Nonconformance Report Transaction Set has the capability to report the cause of the nonconformance and to state 

the proposed action to be followed to prevent a repetition of the problem.

DLMS Note:

1. This DLMS Implementation Convention (IC) provides the DOD standard format for SDR reply. In addition, it is specifically designed to 

transmit action activity SDR response transactions to the DoD WebSDR program. Use a single occurrence of this transaction set to transmit 

single complaint response transaction to a single or multiple organizations.

2. The SDR report submission will be carried in the DS 842A/W

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit 

Conversion Table which can be found on the Enterprise Business Standards Office (EBSO) Web site at www.dla.mil/does/DLMS.

4. This DLMS IC incorporates the Proposed DLMS Change and Approved DLMS Change (ADC) listed. PDC/ADCs are available from the 

EBSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 114, DLMS Supplement (DS) 842A/R DOD Standard SDR Reply and Additional Data Content for the SDR Report

- ADC 128, Revision for SDR Transaction Exchange (Formats, Codes, and UID)

- ADC 137, Revisions for SDR Transaction Exchange Supporting SA and Miscellaneous Administrative Changes

- ADC 144, SDR Transaction Exchange Business Rules

- ADC 184, Redistribution Order (RDO)-based Supply Discrepancy Reports (SDRs)

- ADC 187, Revise Supply Discrepancy Report (SDR) Reply Procedures for Forwarding SDRs to New Action Activity, Email Addresses, and 

Source of Supply (SoS)

- ADC 210, Defense Reutilization and Marketing Service (DRMS) and National Inventory Management Strategy (NIMS) Shipment Types 

Identified for SDR Processing under DLMS

- ADC 210B, Identification of SDR Document Type (includes NIMS and Non-DSS Receipts) Field lengths for non-standard data elements or 

where needed for clarification have been identified in the DLMS notes.

- Administrative change to increase the flexibility in sequencing of codes in the PER, making the SDR reply consistent with the SDR report.

- ADC 268, Inclusion of PQDR RCN on SA Quality-Related SDR Reply (DS 842A/R)

- ADC 293, Revised Time Standards, Codes, and Procedures for Reporting and Processing of Supply Discrepancies

- ADC 311, SDR Attachment Interface

- ADC 317, Revised Business Rules for Transshipper-Prepared Supply Discrepancy Reports (SDRs) (Supply/SDR)

- ADC 322, Addition of Local Catalog ID qualifier to Support Requirements for Theater Enterprise-Wide Logistics System (TEWLS) 

Requisitions (Supply)

- ADC 334, Supply Discrepancy Report Process for AF Retail Storage Activity Denials (Supply/SDR)

- ADC 353, Procedures for Pre-positioned Materiel Receipt (PMR) and Shipment Status for Retrograde and Directed Discrepant/Deficient 

Materiel Returns

- ADC 357, Revisions to DSs for SDRs to Add BDN

- ADC 358, SDR Transaction Content/Business Rule Revisions/Clarification

- ADC 371, Marine Corps SDR Distribution Rules and Navy and Marine Corps SDR and Storage Quality Control Report (SQCR) Procedures 

and Data Content under BRAC

- ADC 381, Procedures and Additional Data Content supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy 

BRAC SS&D/IMSP

- Approved Addendum ADC 381A, Procedures and Additional Data Content supporting Unit of Use Requirements under Marine Corps BRAC 

Storage and Distribution
Enclosure 2, ASC 1377A

Page 2

- ADC 435, DLMS Revisions for SFIS Compliance

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their 

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries 

and their Subdivisions

- 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)

- ADC 1043, DLMS Revisions for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification

- ADC 1044, Enhanced Interim SDR Reply Capability, Status Update, and Completion Notification

- ADC 1052, DOD WebSDR Processes Enhancement and Interface with Electronic Document Access (EDA) System

- ADC 1059, Mandatory Use of Four-Character Packaging Discrepancy Codes on SDRs and Storage Quality Control Reports (SQCRs)

- ADC 1066, SDR Process Enhancements: Follow-up Time Standards, SDR Forwarding, Missing Quality Assurance Representative (QAR) 

Signature, use of Unique Item Tracking (UIT) Designator Code for Management Report Selection Criteria, and Administrative Updates

- ADC 1068, Enhanced Procedures for Requisitioning via DOD EMALL and GSA Internet Ordering: Component Verification of Funds 

Availability and Materiel Identification using the Supplier-Assigned Part Number and/or Supplier Commercial and Government Entity (CAGE) 

Code

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on March 12, 2014.

- ADC 1102, Enhanced SDR Guidance including SDR Routing for Army-Directed DLA Distribution Center Shipments, Procedures for 

Discrepant or Unauthorized Returns to the Distribution Centers, and Administrative Updates

- ADC 1126, Revised 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

- ADC 1127, Enhanced SDR Guidance for Foreign Military Sales (FMS), SDR Time Standards for Controlled Inventory Items, SDR 

Forwarding after Logistics Reassignment (LR), Packaging SDRs, and Administrative Updates

- ADC 1153, SDR Enhancements for Visibility of Discrepancies in Hazardous Materiel Shipments

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions 

and DLMS Manuals (Supply/Contract Administration)

- ADC 1174, WebSDR Process Enhancements and Administrative Updates including SDR Reply Screen and Management Report 

Functionality, New/Revised Reply Codes, and Standardized Identification of the Submitting Customer

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 19, 2016

- ADC 1181A, Implementing the Cause Code for SDRs and Developing a Data Exchange Between WebSDR and Past Performance 

Information Retrieval System-Statistical Reporting Next Generation (PPIRS-SR NG) for Contractor Noncompliance SDRs

- ADC 1203, SDR Procedures for Packaging Discrepancies at FMS Freight Forwarder or Component Retail/Tactical Level Activities including 

Estimated/Actual Repackaging Cost

- ADC 1217, WebSDR Process Enhancement for Source of Supply Disposition Response to Storage Activity on Customer-Initiated SDRs

- ADC 1249, Revised Procedures for Directed Return of Discrepant/ Deficient Materiel including New Document Number Assignment for 

Return Shipment

- ADC 1268, SDR Enhancements for Procurement Instrument Identifier (PIID)-Related Functionality Including Base Contract Number for 

WebSDR and Contract Number and Secondary Document Number in Prepositioned Materiel Receipt (PMR)/Receipt/SDR for Commercial 

Returns

- ADC 1310, Consolidation Containerization Points (CCP)-Originated Supply Discrepancy Reports (SDRs) including Noncompliant Wood 

Packaging Materiel (WPM) with Cost Breakdown and New Procedures for Closing WPM and Passive RFID

- Withdrawal of ADC 1092, DLMS Supply Discrepancy Report (SDR) Interface with the Security Cooperation Enterprise Solution (SCES) 

(Supply/SDR)

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on 

February 27, 2019

- ADC 1331A, Addendum to ADC 1331 Documenting and Expanding DAAS Rejection Criteria for Supply Discrepancy Reports

- ADC 1347, SDR Mandatory Closure Notices for Supply Discrepancy Reports (SDR)

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Used

0200 BNR Beginning Segment For 

Nonconformance Report

M 1 Used

* 0300 REF Reference Identification O >1 Not Used

* 0400 DTM Date/Time Reference O >1 Not Used

* 0500 PID Product/Item Description O >1 Not Used

* LOOP ID - MEA >1

* 0600 MEA Measurements O 1 Not Used

* 0700 DTM Date/Time Reference O >1 Not Used

* 0800 REF Reference Identification O >1 Not Used

* LOOP ID - PWK >1

* 0900 PWK Paperwork O 1 Not Used
Enclosure 2, ASC 1377A

Page 3

* 1000 REF Reference Identification O >1 Not Used

* 1100 DTM Date/Time Reference O >1 Not Used

LOOP ID - N1 >1

1200 N1 Name O 1 Used

* 1300 N2 Additional Name Information O 2 Not Used

* 1400 N3 Address Information O 2 Not Used

* 1500 N4 Geographic Location O 1 Not Used

* 1600 REF Reference Identification O >1 Not Used

1700 PER Administrative Communications 

Contact

O >1 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL >1 N2/0100L

0100 HL Hierarchical Level M 1 N2/0100 Used

0200 LIN Item Identification O 1 Used

* 0300 PID Product/Item Description O >1 Not Used

* 0400 PRS Part Release Status O >1 Not Used

* 0500 CID Characteristic/Class ID O >1 Not Used

0600 DTM Date/Time Reference O >1 Used

0700 REF Reference Identification O >1 Used

0750 CS Contract Summary O 1 Used

* 0800 QTY Quantity O >1 Not Used

* 0900 TMD Test Method O 1 Not Used

* 1000 PSD Physical Sample Description O 1 Not Used

1020 PWK Paperwork O >1 Used

LOOP ID - LM >1

1040 LM Code Source Information O 1 Used

1050 LQ Industry Code M >1 Used

* LOOP ID - MEA >1

* 1100 MEA Measurements O 1 Not Used

* 1200 DTM Date/Time Reference O >1 Not Used

* 1300 REF Reference Identification O >1 Not Used

* LOOP ID - FA1 >1

* 1350 FA1 Type of Financial Accounting Data O 1 Not Used

* 1360 FA2 Accounting Data M >1 Not Used

* LOOP ID - SPS >1

* 1400 SPS Sampling Parameters for 

Summary Statistics

O 1 Not Used

* 1500 REF Reference Identification O >1 Not Used

* 1600 PSD Physical Sample Description O 1 Not Used

* LOOP ID - MEA >1

* 1700 MEA Measurements O 1 Not Used

* 1800 DTM Date/Time Reference O >1 Not Used

* 1900 REF Reference Identification O >1 Not Used

* LOOP ID - STA >1

* 2000 STA Statistics O 1 Not Used

* 2100 DTM Date/Time Reference O >1 Not Used

* 2200 REF Reference Identification O >1 Not Used

LOOP ID - NCD >1

2300 NCD Nonconformance Description O 1 Used

* 2400 NTE Note/Special Instruction O >1 Not Used

* 2500 DTM Date/Time Reference O >1 Not Used

2600 REF Reference Identification O >1 Used
Enclosure 2, ASC 1377A

Page 4

2700 QTY Quantity O >1 Used

2730 AMT Monetary Amount O >1 Used

* 2740 MEA Measurements O >1 Not Used

* 2750 RC Root Cause O >1 Not Used

* LOOP ID - EFI >1

* 2760 EFI Electronic Format Identification O 1 Not Used

* 2770 BIN Binary Data M 1 Not Used

LOOP ID - N1 >1

2800 N1 Name O 1 Used

* 2900 N2 Additional Name Information O 2 Not Used

* 3000 N3 Address Information O 2 Not Used

* 3100 N4 Geographic Location O 1 Not Used

* 3200 REF Reference Identification O >1 Not Used

* 3300 PER Administrative Communications 

Contact

O >1 Not Used

LOOP ID - LM >1

3330 LM Code Source Information O 1 Used

3340 LQ Industry Code M >1 Must use

LOOP ID - NCA >1

3400 NCA Nonconformance Action O 1 Used

3500 NTE Note/Special Instruction O >1 Used

3600 DTM Date/Time Reference O >1 Used

3700 REF Reference Identification O >1 Used

* LOOP ID - PWK >1

* 3800 PWK Paperwork O 1 Not Used

* 3900 REF Reference Identification O >1 Not Used

* 4000 DTM Date/Time Reference O >1 Not Used

LOOP ID - N1 >1

4100 N1 Name O 1 Used

* 4200 N2 Additional Name Information O 2 Not Used

* 4300 N3 Address Information O 2 Not Used

* 4400 N4 Geographic Location O 1 Not Used

* 4500 REF Reference Identification O >1 Not Used

* 4600 PER Administrative Communications 

Contact

O >1 Not Used

LOOP ID - LM >1

4640 LM Code Source Information O 1 Used

4650 LQ Industry Code M >1 Used

LOOP ID - FA1 >1

4660 FA1 Type of Financial Accounting Data O 1 Used

4670 FA2 Accounting Data M >1 Used

4700 SE Transaction Set Trailer M 1 Used

Notes: 

2/0100L The HL levels are item, component, product characteristic, report, and serial number. Valid HL Parent-Child relationships are 1) item 

- component, 2) item - product characteristic, 3) component - product characteristic, 4) report - item, 5) item - serial number, and 6) 

component - serial number.

2/0100 The HL levels are item, component, product characteristic, report, and serial number. Valid HL Parent-Child relationships are 1) item 

- component, 2) item - product characteristic, 3) component - product characteristic, 4) report - item, 5) item - serial number, and 6) 

component - serial number.
Enclosure 2, ASC 1377A

Page 5

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Used

Purpose: To indicate the start of a transaction set and to assign a control number

Semantics: 

1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction 

set definition (e.g., 810 selects the Invoice Transaction Set).

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate 

implementation convention to match the transaction set definition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

 

Description: Code uniquely identifying a 

Transaction Set

M ID 3/3 Must use 1

Code Name

842 Nonconformance Report

ST02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set

DLMS Note: A unique number assigned by 

the originator of the transaction set, or the 

originator's application program.

M AN 4/9 Must use 1

ST03 1705 Implementation Convention Reference

 

Description: Reference assigned to identify 

Implementation Convention

DLMS Note: Use to indicate this 

transmission uses the 842A/R 

Implementation Convention (IC). Enter the 

DLMS IC: 004030F842A0RA00

O AN 1/35 Used 1
Enclosure 2, ASC 1377A

Page 6

BNR Beginning Segment For 

Nonconformance Report

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 5

User Option (Usage): Used

Purpose: To indicate the beginning of a Nonconformance Report Transaction Set

Semantics: 

1. BNR02 is the nonconformance report identifier number.

2. BNR03 is the date that the nonconformance report was created.

3. BNR04 is the time that the nonconformance report was created.

Comments: 

1. BNR05 indicates the status or intention of the nonconformance report.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BNR01 353 Transaction Set Purpose Code

 

Description: Code identifying purpose of 

transaction set

M ID 2/2 Must use 1

Code Name

11 Response 

DLMS Note:

1. Use to identify an SDR/SQCR reply. For Security Assistance SDRs, may be used by action 

office to forward reply to the International Logistics Control Office (ILCO) or by the ILCO to 

record a reply to the customer.

44 Rejection 

DLMS Note:

Use to identify an International Logistics Control Office rejection or request for additional 

information (Action office is intended recipient).

49 Original - No Response Necessary 

DLMS Note:

1. Not authorized for use.

CN Completion Notification 

DLMS Note:

1. Use to indicate the submitter of the SDR has taken all associated disposition actions and 

has closed the SDR in the submitting system.

2. Only the submitting system of the SDR is authorized to send the CN transaction to close 

the SDR. Refer to ADC 1347.

3. Use to indicate the storage activity providing this transaction has closed the SQCR record 

internally. 

SU Status Update 

DLMS Note:

1. Use to provide additional information or status in response to an interim reply from the 

action activity.

2. Use to report recommendations or findings to the materiel owner in response to an SDR 

investigation.

BNR02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

DLMS Note: 1. Enter "U" to identify the Unit 

M AN 1/50 Must use 1
Enclosure 2, ASC 1377A

Page 7

of Use Indicator. When included, the 

quantity and unit of measure values 

associated with this transaction are 

applicable to the unit of use. This applies 

when the materiel identification is by Local 

Stock Number assigned for unit of use. This 

is an Authorized DLMS enhancement under 

DLA industrial activity support agreement. 

Refer to ADC 371. 

2. When not used for Unit of Use Indicator, 

must enter Z to satisfy ANSI syntax. 

BNR03 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year

DLMS Note: This date corresponds to the 

Universal Time Coordinate (UTC).

M DT 8/8 Must use 1

BNR04 337 Time

 

Description: Time expressed in 24-hour 

clock time as follows: HHMM, or HHMMSS, 

or HHMMSSD, or HHMMSSDD, where H = 

hours (00-23), M = minutes (00-59), S = 

integer seconds (00-59) and DD = decimal 

seconds; decimal seconds are expressed as 

follows: D = tenths (0-9) and DD = 

hundredths (00-99)

DLMS Note: 1. Express the originating 

activity's time in Universal Time Coordinate 

(UTC).

2. Express time in a four-position (HHMM) 

format.

O TM 4/8 Must use 1

BNR06 640 Transaction Type Code

 

Description: Code specifying the type of 

transaction

O ID 2/2 Used 1

Code Name

SR Supply Process Deficiency Response 

DLMS Note:

Use to indicate a transaction that reflects a DOD standard SDR/SQCR Reply transaction. 
Enclosure 2, ASC 1377A

Page 8

N1 Name Pos: 1200 Max: 1

Heading - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. P0304 - If either N103 or N104 is present, then the other is required.

2. R0203 - At least one of N102 or N103 is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1.Must use to identify the organizations sending and receiving the transaction set.

2.For SQCR use Code: 91, ZD, 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

DLMS Note: The following codes are 

authorized. 

M ID 2/3 Must use 1

Code Name

91 Action Party 

DLMS Note:

1. Use to identify the Routing Identifier of the organization providing the SDR response.

2. For Type 5 SQCRs this signifies the material owner. 

GP Gateway Provider 

DLMS Note:

Use to identify the Routing Identifier of the DAASC as the intended recipient for distribution or 

posting to the historical record under DOD WebSDR business rules. 

PK Party to Receive Copy 

DLMS Note:

1. Use to identify the organization(s) to receive a distribution copy of the SDR reply.

2. Not authorized for SQCRs (Type 5).

ZD Party to Receive Reports 

DLMS Note:

1. Use to identify the organization(s) to receive the SDR response.

2. For Type 5 SQCRs this is the storage activity.

ZS Monitoring Party 

DLMS Note:

Use to identify the International Logistics Control Office (ILCO).

N102 93 Name

 

Description: Free-form name

X AN 1/60 Used 1

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

Identification Code (67)

X ID 1/2 Used 1
Enclosure 2, ASC 1377A

Page 9

Code Name

10 Department of Defense Activity Address Code (DODAAC) 

DLMS Note:

May be used for the customer DODAAC to receive a copy of the reply using qualifier ZD 

above.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

 

Description: Code identifying a party or 

other code

X AN 2/80 Used 1

N106 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

O ID 2/3 Used 1

Code Name

FR Message From 

DLMS Note:

Use to indicate the organization cited above is originating the transaction set.

TO Message To 

DLMS Note:

Use to indicate the organization cited above is receiving the transaction set.
Enclosure 2, ASC 1377A

Page 10

PER Administrative Communications 

Contact

Pos: 1700 Max: >1

Heading - Optional

Loop: N1 Elements: 9

User Option (Usage): Used

Purpose: To identify a person or office to whom administrative communications should be directed

Syntax Rules: 

1. P0304 - If either PER03 or PER04 is present, then the other is required.

2. P0506 - If either PER05 or PER06 is present, then the other is required.

3. P0708 - If either PER07 or PER08 is present, then the other is required.

DLMS Note:

1.Use a second repetition if needed to identify additional communication numbers.

2. For SQCR, use Code:, IC.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PER01 366 Contact Function Code

 

Description: Code identifying the major 

duty or responsibility of the person or group 

named

M ID 2/2 Must use 1

Code Name

CT

Claimant 

DLMS Note:

Use to identify the contact information of the customer. Include an email address for 

distribution of the SDR reply via email by DoD WebSDR. Use when the original report was 

not entered in WebSDR and, therefore, a customer email address is not otherwise available. 

If an email address is associated with the customer, WebSDR will make email distribution of 

the reply to the address provided. (Use with 1/N101/4100/ZD).

CZ Claim Recipient 

DLMS Note:

Use to identify the recipient of the SDR reply transmitted by email. DoD 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.)

ES Electronic Submission Recipient 

DLMS Note:

Use to identify the recipient of the SDR reply transmitted by email. DoD WebSDR will make 

email distribution of the SDR transaction to any party identified as an electronic (email) 

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.)

IC Information Contact

DLMS Note:

Use on the storage activity status update or completion notice (with N101=41)

RZ Respondant 

DLMS Note:

Use to identify the action activity point of contact associated with this SDR Reply.

A data maintenance action was approved in version 5030. The approved code/name is "DR -

Discrepancy Report Reply Contact".

SE Service Organization 

DLMS Note:

Use to identify the ILCO POC.

A data maintenance action was approved in version 5030. The approved code/name is "IL -

International Logistics Control Office Point of Contact".
Enclosure 2, ASC 1377A

Page 11

PER02 93 Name

 

Description: Free-form name

DLMS Note: WebSDR field length = 25

O AN 1/60 Used 1

PER03 365 Communication Number Qualifier

 

Description: Code identifying the type of 

communication number

X ID 2/2 Used 1

Code Name

AU Defense Switched Network 

DLMS Note:

For AU: WebSDR field length = 8

EM Electronic Mail 

DLMS Note:

For EM: WebSDR field length = 50

FX Facsimile 

DLMS Note:

1. Use to identify the commercial FAX number.

2. For FX: WebSDR field length = 16

TE Telephone 

DLMS Note:

1. Use to identify the commercial number.

2. For TE: WebSDR field length = 16

WF Work Facsimile Number 

DLMS Note:

1. Use to identify the DSN FAX number.

2. For WF: WebSDR field length = 8

PER04 364 Communication Number

 

Description: Complete communications 

number including country or area code when 

applicable

X AN 1/256 Used 1

PER05 365 Communication Number Qualifier

 

Description: Code identifying the type of 

communication number

DLMS Note: Use to identify an alternate 

communications number which can be used 

to contact the specified point of contact.

X ID 2/2 Used 1

Code Name

AU Defense Switched Network 

DLMS Note:

For AU: WebSDR field length = 8

EM Electronic Mail 

DLMS Note:

For EM: WebSDR field length = 50

FX Facsimile 

DLMS Note:

1. Use to identify the commercial FAX number.

2. For FX: WebSDR field length = 16

TE Telephone 

DLMS Note:

1. Use to identify the commercial number.

2. For TE: WebSDR field length = 16
Enclosure 2, ASC 1377A

Page 12

WF Work Facsimile Number 

DLMS Note:

1. Use to identify the DSN FAX number.

2. For WF: WebSDR field length = 8

PER06 364 Communication Number

 

Description: Complete communications 

number including country or area code when 

applicable

X AN 1/256 Used 1

PER07 365 Communication Number Qualifier

 

Description: Code identifying the type of 

communication number

X ID 2/2 Used 1

Code Name

AU Defense Switched Network 

DLMS Note:

For AU: WebSDR field length = 8

EM Electronic Mail 

DLMS Note:

For EM: WebSDR field length = 50

FX Facsimile 

DLMS Note:

1. Use to identify the commercial FAX number.

2. For FX: WebSDR field length = 16

TE Telephone 

DLMS Note:

1. Use to identify the commercial number.

2. For TE: WebSDR field length = 16

WF Work Facsimile Number 

DLMS Note:

1. Use to identify the DSN FAX number.

2. For WF: WebSDR field length = 8

PER08 364 Communication Number

 

Description: Complete communications 

number including country or area code when 

applicable

X AN 1/256 Used 1

PER09 443 Contact Inquiry Reference

 

Description: Additional reference number or 

description to clarify a contact number

DLMS Note: 1. Use as needed to identify 

the office symbol or activity code for the 

party identified.

2. Also may reflect position title of the point 

of contact.

O AN 1/20 Used 1
Enclosure 2, ASC 1377A

Page 13

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment 

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL 

segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the 

transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to 

shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

HL01 628 Hierarchical ID Number

 

Description: A unique number assigned by 

the sender to identify a particular data 

segment in a hierarchical structure

DLMS Note: Cite numeric 1 to satisfy ANSI 

syntax requirement.

M AN 1/12 Must use 1

HL03 735 Hierarchical Level Code

 

Description: Code defining the 

characteristic of a level in a hierarchical 

structure

M ID 1/2 Must use 1

Code Name

RB

I 

Response 

DLMS Note:

Use in all transactions to satisfy ANSI syntax requirement.

Item

DLMS Note:

Use to identify IUID data consistent with IUID data requirements. The IUID data is carried in 

the REF and N1 segments contained within the NCD loop. No other segments are used in the 

IUID loop. Use a separate IUID loop for each item. Skip this level when not applicable. This 

is future enhancement provided to address IUID requirements.
Enclosure 2, ASC 1377A

Page 14

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 8

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., 

U.P.C. No., ISBN No., Model No., or SKU.

DLMS Note:

1. Use this segment to site the National Stock Number.

2. Use remaining LIN segment to further identify an item

3. For SQCR, use Code: MN.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LIN02 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: Use for materiel identification. 

Use multiple Product/Service ID pairs as 

needed.

M ID 2/2 Must use 1

Code Name

A3 Locally Assigned Control Number 

DLMS Note:

1. Defense Medical Logistics Standard Support (DMLSS)/Theater Enterprise-Wide Logistics 

System (TEWLS) use to cite the Local Catalog Identification.

2. DLMS enhancement; see introductory DLMS Note 3a. Refer to ADC 322.

3. Under DLMS, field length is restricted to a maximum of 30 positions.

FS National Stock Number 

DLMS Note:

1. Use to identify the NSN for the materiel.

2. For FS: WebSDR field length = 13
Enclosure 2, ASC 1377A

Page 15

MG Manufacturer's Part Number 

DLMS Note:

1. Use to identify the part number for the item.

2. May be used to identify the supplier-assigned part number when applicable to a DoD 

EMALL or GSA Advantage/Global internet order from a vendor catalog. When used for 

supplier part number, identify the associated CAGE at 2/LIN04. Refer to ADC 1068.

3. For MG: WebSDR field length = 32

SW Stock Number 

DLMS Note:

1. Use to identify the local stock number (LSN).

2. When used for a unit of use LSN applicable to NSN materiel, the applicable NSN will be 

included for cross-reference.

3. When used for a unit of use LSN applicable to part numbered items, the original partnumbered item LSN will also be included for cross-reference.

4. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to 

ADC 381/ Approved Addendum 381A.

ZZ Mutually Defined 

DLMS Note:

1. Use to identify materiel by other than NSN or part number.

2. Field length restricted to 15

LIN03 234 Product/Service ID

 

Description: Identifying number for a 

product or service

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: Use to further identify an item. 

Use multiple Product/Service ID pairs as 

needed. The sequence of data content for 

secondary materiel identification is 

dependent upon the applicable primary 

materiel identification. The preferred 

sequence of secondary information is: 

manufacturer's (or supplier’s) part number; 

manufacturer’s (or supplier’s) CAGE code;

nomenclature. However, part number, 

manufacturer’s CAGE code, and 

nomenclature may be cited in any order 

without causing transaction failure.

X ID 2/2 Used 1

Code Name

CN Commodity Name 

DLMS Note:

1. Use to identify the nomenclature associated with the item identified.

2. For CN: WebSDR field length = 25.

FS National Stock Number 

DLMS Note:

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator is included and the 

Local Stock Number (LSN) is identified as the primary materiel identification. Authorized 

DLMS enhancement under DLA industrial activity support agreement.
Enclosure 2, ASC 1377A

Page 16

MG

MN

Manufacturer's Part Number 

DLMS Note:

1. Use to identify the part number when primary materiel identification is previously identified.

2. For MG: WebSDR field length = 32.

Model Number

SW Stock Number 

DLMS Note:

1. Use to identify the local stock number (LSN). 

2. The LSN is provided as a cross-reference when unit of use indicator is included and the unit 

of use LSN is identified as the primary materiel identification. Authorized DLMS enhancement 

under DLA industrial activity support agreement.

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

1. Use to identify manufacturer (or supplier) associated with a previously identified part 

number.

2. May be used to identify the supplier CAGE when applicable to a DoD EMALL or GSA 

Advantage/Global internet order from a vendor catalog. 

LIN05 234 Product/Service ID

 

Description: Identifying number for a 

product or service

X AN 1/48 Used 1

LIN06 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: Use to further identify an item. 

Use multiple Product/Service ID pairs as 

needed.

X ID 2/2 Used 1

Code Name

CN Commodity Name 

DLMS Note:

1. Use to identify the nomenclature associated with the item identified.

2. For CN: WebSDR field length = 25.

MG Manufacturer's Part Number 

DLMS Note:

1. Use to identify the part number when primary materiel identification is previously identified.

provided by NSN and LSN.

2. For MG: WebSDR field length = 32.

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

Use to identify manufacturer associated with a previously identified part number.

LIN07 234 Product/Service ID

 

Description: Identifying number for a 

product or service

X AN 1/48 Used 1

LIN08 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234)

DLMS Note: Use to further identify an item. 

Use multiple Product/Service ID pairs as 

needed.

O ID 2/2 Used 1

Code Name

CN Commodity Name 

DLMS Note:
Enclosure 2, ASC 1377A

Page 17

1. Use to identify the nomenclature associated with the item identified.

2. For CN: WebSDR field length = 25.

MG Manufacturer's Part Number 

DLMS Note:

1. Use to identify the part number when primary materiel identification is previously identified.

2. For MG: WebSDR field length = 32.

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

Use to identify manufacturer associated with a previously identified part number.

LIN09

LIN10 

LIN11 

234

235

234

Product/Service ID

 

Description: Identifying number for a 

product or service

Product/Service ID Qualifier

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234). All valid 

standard codes are used.

Product/Service ID

Description: Identifying number for a 

product or service 

O

X

X

AN

ID

AN

1/48

2/2

1/48

Used

Used

Used

1
Enclosure 2, ASC 1377A

Page 18

DTM Date/Time Reference Pos: 0600 Max: >1

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. C0403 - If DTM04 is present, then DTM03 is required.

2. P0506 - If either DTM05 or DTM06 is present, then the other is required.

3. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

DLMS Note:

Use multiple repetitions as needed to identify dates associated with the complaint.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

 

Description: Code specifying type of date 

or time, or both date and time

DLMS Note: The following codes are 

authorized. 

M ID 3/3 Must use 1

Code Name

975

Notice 

DLMS Note:

1. Use to identify the SDR reply date.

2. This is the date when the Completion Notice (CN) is generated by the submitter.

DTM02 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year

X DT 8/8 Must use 1
Enclosure 2, ASC 1377A

Page 19

REF Reference Identification Pos: 0700 Max: >1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

Must use to identify the requisition document number. Use multiple repetitions as needed to identify additional reference numbers associated 

with a complaint.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

DLMS Note: 1.The following codes are 

authorized.

2.For SQCR use Codes: 86,9R, IL, NN, TN 

and PWC

M ID 2/3 Must use 1

Code Name

86 Operation Number 

DLMS Note:

1. Use to identify the Key Operation (KO) Number associated with the JO. 

2. Authorized DLMS enhancement for industrial activity support. Refer to ADC 371.

9R Job Order Number 

DLMS Note:

1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement for industrial activity support. Refer to ADC 371.

BY Repair Category Number 

DLMS Note:

1. Use to identify SA product quality deficient item as new or repaired/overhauled (N=New, 

R=Repaired/Overhauled).

2. Use for SDRs for discrepant shipments from commercial activity reported on Document 

Type 9/P to distinguish from new procurement. Enter Code R for commercial returns from 

repair, non-destructive test/evaluation, assembly, disassembly, reclamation, and 

conversion/modification. Refer to ADC 1268.

F8 Original Reference Number 

DLMS Note:

1. Use to identify the SDR Customer Reference Number when provided separately. 

Component SDR applications maintain this number and perpetuate to outgoing transactions. 

Must use alphanumeric characters only with no special characters or DAAS will reject as 

DAAS Reject upon submission. Refer to ADC 1331A.

2. May be used when a manually assigned reference number is to be retained as a crossreference to a system assigned number.

3. Used for FMS SDRs to ensure visibility of the ILCO assigned control number within 

Component SDR applications.
Enclosure 2, ASC 1377A

Page 20

4. Use to identify the Air Force maintenance document number/suffix associated with an SDR 

resulting from depot denial under DLA/AF industrial activity support agreement. The number is 

constructed with the M-series maintenance site identifier in the first six positions of the 

document number. Refer to ADC 334.

5. Use to identify the Navy maintenance document number/suffix associated with an SDR 

resulting from DLA stock positioning/procurement action/requisitioning from another 

Component source of supply. The Navy document number/suffix (normally applicable to the 

requisition alert) will be perpetuated from the Prepositioned Materiel Receipt Document 

(PMRD) provided by DLA under DLA/Navy industrial activity support agreement. Refer to ADC 

371.

6. For F8: WebSDR maximum field length = 18.

HN Hazardous Certification Number 

DLMS Note:

Use to provide or perpetuate the yes/no Hazardous Materiel Indicator in the REF02 specifying 

if the shipment contains hazardous materiels (including explosives/ammunition).

NN Nonconformance Report Number 

DLMS Note:

1. Use to identify the submitting system’s SDR report control number. This will be the 

originator's system assigned number. Identify the originating system in REF03 (see REF03 for 

values).

2. Must use a second REF segment to identify the applicable DoD WebSDR control number 

when one was provided on the SDR report.

3. A WebSDR control number will be assigned to transactions during processing if not 

previously assigned. WebSDR transaction processing will repeat the REF segment if to 

include each previously identified SDR report control number on the outgoing transaction; 

Component applications need not repeat all applicable values.

4. Must use alphanumeric characters only with no special characters or DAAS will reject as 

DAAS Reject upon submission. Refer to ADC 1331A.

5. For NN: WebSDR maximum field length = 20 (actual length for originating applications will 

differ)

6. Use multiple occurrences of the REF segment as needed to identify applicable report 

control numbers.

.

8. Use to indicate the originator’s SQCR report control number.

9. Identify the number in REF02 and the originating system (e.g., EBS for DLA) for the reply 

transaction in REF03.

10. The SQCR report control number is defined as 9 position alphanumeric.

PWC 

QR

DLMS Note:

1. Use to identify a Requisition Alert Document Number.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer 

to ADC 381..

Quality Report Number 

DLMS Note:

1. Use to identify the PQDR report control number (RCN) for cross reference to the 

associated PQDR.

2. Applicable SDR replies resulting from Security Assistance quality-related deficiencies 

reported via an SDR transaction exchange. 

3. Applicable to SDR replies resulting from Distribution Depot PQDR exhibit receipt notices 

reported via SDR transaction exchange.

4. Refer to ADC 268.

5. For QR: WebSDR field length =15
Enclosure 2, ASC 1377A

Page 21

SI Shipper's Identifying Number for Shipment (SID) 

DLMS Note:

1. This is the contractor-assigned shipment number, e.g. vendor shipments invoiced via the 

Mechanization of Contract Administration Services (MOCAS) system are identified by a 

shipment number formatted as three alpha and four numeric characters (may include 1 

position shipment number suffix). 

2. DoD action activities responsible for contracted vendor shipments are required to populate 

the contractor-assigned Shipment Number when applicable and not provided by the submitter.

For SI: WebSDR maximum field length = 22

TN Transaction Reference Number 

DLMS Note:

1. Use to indicate the requisition document number.

2. For TN: WebSDR field length = 14

3. Use to enter the applicable document from the original SQCR. (The SQCR document 

number may be system-generated/assigned by the storage activity when a document number 

is no longer associated with materiel in storage; field length = 14). 

WO Work Order Number 

DLMS Note:

1. Use to identify the Build Directive Number (BDN) for medical/surgical or other component 

assembly/kit. 

2. For future consideration, a data maintenance action was approved in X12 version 5010. 

The approved code/name is “BDN – Build Directive Number.”

REF02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

X AN 1/50 Must use 1

REF03 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: 1.Use to identify the 

generating-system associated with the SDR 

report control number identified in the

REF01:

• WEBSDR - The DoD WebSDR control 

number must be perpetuated to all 

transactions once assigned

• ISDR - Distribution Standard System (DSS) 

Incoming SDR 

• ADRS - DSS Automated Discrepancy 

Reporting System

• BSM - DLA Enterprise Business System 

(EBS) (formerly Business System 

Modernization (BSM))

• LMP - Army Logistics Modernization 

Program)

• NAVSEA-PDREP - Product Data Reporting 

and Evaluation Program Automated 

Information System (Navy-sponsored multiService use)

• D035K - Air Force Stock Control System

• ESS - Air Force Enterprise Solution-Supply 

• ILCO - Air Force Security Assistance and 

Cooperation Directorate SDR-Automation 

(SDR-A) 

• GSA - GSA Vision system

• WMS - Warehouse Management 

X AN 1/80 Used 1
Enclosure 2, ASC 1377A

Page 22

System

REF04 C040 Reference Identifier

 

Description: To identify one or more 

reference numbers or identification numbers 

as specified by the Reference Qualifier

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

M ID 2/3 Must use 1

Code Name

W8 Suffix 

DLMS Note:

1. When citing the requisition number (using Transaction Reference Number, Code TN), use 

to identify the document number suffix if one is provided.

2. When used in association with the Requisition Alert Document Number (Qualifier PWC, 

above), this will be the requisition alert document suffix. The Requisition Alert Document 

Number Suffix, is an Authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381.

3. When providing the original billed document number (using Code 8V), use to identify the 

original billed document number suffix if applicable. Refer to ADC 1084.

REF04-02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

M AN 1/50 Must use 1
Enclosure 2, ASC 1377A

Page 23

CS Contract Summary Pos: 0750 Max: 1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To provide information about a contract

Syntax Rules: 

1. P0405 - If either CS04 or CS05 is present, then the other is required.

Semantics: 

1. CS09 is the permissible overage as a percentage of the total contract line item number (CLIN) quantity.

2. CS10 is the permissible shortage as a percentage of the total contract line item number (CLIN) quantity.

3. CS11 is the permissible overage dollar value specified by the contract above which discrepancy action is taken.

4. CS14 is the Unit of Measure stipulated in the contract.

5. CS15 is the contract line item number (CLIN) unit price specified in the contract.

6. CS17 conveys the Critical Application Indicator. A "Y" indicates that a Critical Application Indicator is specified in the contract; an "N" 

indicates that no Critical Application Indicator is specified in the contract.

7. CS18 conveys the Special Requirements Indicator. A "Y" indicates that a Special Requirements Indicator (requiring special testing and or 

evaluation) is specified in the contract; an "N" indicates that no Special Requirements Indicator is specified in the contract.

Comments: 

1. CS04 may be used to identify the Contract Line Item Number (CLIN) or Extended (or Exhibit) Line Item Number (ELIN).

2. CS07 and CS13 can be used to indicate two different types of special services required.

DLMS Note:

Action activities are required to populate the contractor shipment information when applicable. This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CS01 367 Contract Number

 

Description: Contract number

DLMS Note: 1. Use to identify the 

procurement instrument identifier (PIID). 

Use the legacy procurement instrument 

identification number (PIIN) pending 

transition to the PIID. When procurement is 

authorized under a PIID call/order number (F 

or M in 9th position), provide the value in the 

PIID field.

2. WebSDR field length = 17

O AN 1/30 Used 1

CS03 328 Release Number

 

Description: Number identifying a release 

against a Purchase Order previously placed 

by the parties involved in the transaction

DLMS Note: 1. Use to identify the legacy 

four-position call/order number associated 

with the PIIN.

2. Do not use for the PIID call/order number. 

The PIID call/order number is mapped to 

CS01. Refer to ADC 1161.

O AN 1/30 Used 1

CS04 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

X ID 2/3 Used 1
Enclosure 2, ASC 1377A

Page 24

Code Name

C7 Contract Line Item Number 

DLMS Note:

Use as needed to identify the CLIN or the CLIN including the SUBCLIN, as appropriate.

CS05 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

X AN 1/50 Used 1
Enclosure 2, ASC 1377A

Page 25

PWK Paperwork Pos: 1020 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To identify the type or transmission or both of paperwork or supporting information

Syntax Rules: 

1. P0506 - If either PWK05 or PWK06 is present, then the other is required.

Comments: 

1. PWK05 and PWK06 may be used to identify the addressee by a code number.

2. PWK07 may be used to indicate special information to be shown on the specified report.

3. PWK08 may be used to indicate action pertaining to a report.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PWK01 755 Report Type Code

 

Description: Code indicating the title or 

contents of a document, report or supporting 

item

DLMS Note: The following codes are 

authorized.

M ID 2/2 Used 1

Code Name

AE Attachment 

DLMS Note:

1. Use to indicate that supporting documentation has been provided electronically in the form 

of images or files and is available for download from the DoD WebSDR.

2. Use with Code FT (PWK02) when file is transmitted electronically between the DoD 

WebSDR and the interfacing application. 

R6 Miscellaneous Information 

DLMS Note:

Use to indicate that additional information is being submitted to the action activity off-line.

PWK02 756 Report Transmission Code

 

Description: Code defining timing, 

transmission method or format by which 

reports are to be sent

O ID 1/2 Used 1

Code Name

FT File Transfer 

DLMS Note:

1. Use to indicate attachment is being sent electronically in a separate transmission.

2. Up to five attachments may be provided with the reply transaction.

PWK07 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: 1. Use to indicate the SDR 

Attachment File Name being sent 

electronically in a separate transmission. 

Refer to ADC 311.

2. WebSDR field length = 50.

O AN 1/80 Used 1
Enclosure 2, ASC 1377A

Page 26

LM Code Source Information Pos: 1040 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use to identify coded information maintained in department or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
Enclosure 2, ASC 1377A

Page 27

LQ Industry Code Pos: 1050 Max: >1

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Used

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

 

Description: Code identifying a specific 

industry code list

DLMS Note: 1.The following codes are 

authorized. 

2. For SQCR, use Code:, BG, HA, HD and 

83. Add Type 5

O ID 1/3 Must use 1

Code Name

BG

D

Condition

DLMS Note:

Use for reclassification of condition code (Supply Condition Code-To

Court Document Type Code 

DLMS Note:

1. Must use to identify the Discrepancy Report Document Type Code 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:

• 5- Storage Quality Control Report.

• 6 - Customer originated, direct vendor/contractor delivery. This type is used primarily for 

shipment of requisitioned materiel sourced by the item manager by contracted vendor 

shipment rather than from stock.

• 7 - Customer originated, depot/lateral shipment/other. 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 procurement source receipt

• 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 procurement source receipt (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 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 differ 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".

EQ Controlled Inventory Item Code
Enclosure 2, ASC 1377A

Page 28

FD Demilitarization Code

ST Special Marketing Type Code 

DLMS Note:

1. Use to identify the DLA Disposition Services SDR Type Code 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

 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.

COG

83 

Cognizance Symbol 

DLMS Note:

Use to identify the material cognizance symbol (COG) of the end item. Applicable to US Navy 

only.

Supply Condition Code

LQ02 1271 Industry Code

 

Description: Code indicating a code from a 

specific industry code list

X AN 1/30 Must use 1
Enclosure 2, ASC 1377A

Page 29

NCD Nonconformance Description Pos: 2300 Max: 1

Detail - Optional

Loop: NCD Elements: 2

User Option (Usage): Used

Purpose: To describe the nonconformance condition

Syntax Rules: 

1. R0102 - At least one of NCD01 or NCD02 is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

NCD02 888 Nonconformance Determination Code

 

Description: Code indicating whether a 

nonconforming condition was the reason for 

submitting or the basis upon which a 

nonconformance report is initiated

X ID 1/1 Must use 1

Code Name

5 Discrepant 

DLMS Note:

For all transactions, use to satisfy ANSI requirement.

NCD03 350 Assigned Identification

 

Description: Alphanumeric characters 

assigned for differentiation within a 

transaction set

DLMS Note: 1. Use as a counter to satisfy 

ANSI syntax. Cite numeric 1.

2. Use of the NCD segment looping 

structure to describe multiple wrong items 

received in association with Discrepancy 

Code W5, Mixed Stock, is reserved for 

future implementation.

O AN 1/20 Must use 1
Enclosure 2, ASC 1377A

Page 30

REF Reference Identification Pos: 2600 Max: >1

Detail - Optional

Loop: NCD Elements: 4

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

M ID 2/3 Used 1

Code Name

XA Substitute National Stock Number 

DLMS Note:

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

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). If description is provided, include in REF03.

2. For XB: WebSDR field length = 32

REF02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

O AN 1/50 Used 1

REF03 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

O AN 1/80 Used 1

REF04 C040 Reference Identifier

 

Description: To identify one or more 

reference numbers or identification numbers 

as specified by the Reference Qualifier

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

All valid standard codes are used.

M ID 2/3 Used 1
Enclosure 2, ASC 1377A

Page 31

REF04-02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

M AN 1/50 Used 1

REF04-03 128 Reference Identification Qualifier 

Description: Code qualifying the Reference 

Identification

All valid standard codes are used.

O ID 2/3 Used 1

REF04-04 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

O AN 1/50 Used 1
Enclosure 2, ASC 1377A

Page 32

QTY Quantity Pos: 2700 Max: >1

Detail - Optional

Loop: NCD Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

1. E0204 - Only one of QTY02 or QTY04 may be present.

2. R0204 - At least one of QTY02 or QTY04 is required.

Semantics: 

1. QTY04 is used when the quantity is non-numeric.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

 

Description: Code specifying the type of 

quantity

DLMS Note: The following codes are 

authorized. 

M ID 2/2 Must use 1

Code Name

75 Receipts 

DLMS Note:

1. Use to indicate the number of incorrect (wrong) items received.

2. Wrong item quantity is applicable when multiple discrepancies are reported on an SDR and 

only a portion of the total discrepant quantity is associated with the wrong item(s) received. If 

not populated on the SDR reply, the total discrepant quantity is recognized as the wrong item 

quantity.

3. For 75: WebSDR field length for incorrect item quantity = 7

86 Nonconformance Quantity 

DLMS Note:

1. Use to indicate the discrepant/deficient quantity.

2. For 86: WebSDR field length = 7

QTY02 380 Quantity

 

Description: Numeric value of quantity

X R 1/15 Must use 1

QTY03 C001 Composite Unit of Measure

 

Description: To identify a composite unit of 

measure(See Figures Appendix for 

examples of use)

DLMS Note: DLMS users see the Unit of 

Issue and Purchase Unit Conversion Table 

for available codes.

O Comp Used 1

QTY03-01 355 Unit or Basis for Measurement Code

 

Description: Code specifying the units in 

which a value is being expressed, or manner 

in which a measurement has been taken

DLMS Note: Use to identify the unit of issue.

M ID 2/2 Must use 1
Enclosure 2, ASC 1377A

Page 33

AMT Monetary Amount Pos: 2730 Max: >1

Detail - Optional

Loop: NCD Elements: 3

User Option (Usage): Used

Purpose: To indicate the total monetary amount

DLMS Note:

This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

AMT01 522 Amount Qualifier Code

 

Description: Code to qualify amount

DLMS Note: The following codes are 

authorized. 

M ID 1/3 Must use 1

Code Name

10 Shipment Value in U.S. Dollars 

DLMS Note:

1. Use to indicate the total dollar value of the discrepant materiel.

2. For 10: WebSDR field length = 13

2P Total Recommended Repairs 

DLMS Note:

1. Use for estimated repair costs associated with damaged item (SA only).

2. For 2P: WebSDR field length = 15

RP Repair 

DLMS Note:

1. Use for actual repair costs associated with damaged item (SA only).

2. For RP: WebSDR field length = 15

Z3 Unit Cost of Discrepant Material 

DLMS Note:

1. Use to identify the unit value (price) of the discrepant materiel.

2. For Z3: WebSDR field length = 11

ADM Expected Reimbursement Amount 

DLMS Note:

1. Use for carcass value reimbursement (e.g. for lost reparable). (SA only.)

2. For ADM: WebSDR field length = 15

RPC Repackaging Cost 

DLMS Note:

1. Use to indicate the dollar value for corrective action. Include materiel and labor needed to 

complete a packing, packaging, preservation, palletization and/or marking project.

2. Use with Estimated/Actual Cost Flag (AMT03). Refer to ADC 1203.

3. For RPC: WebSDR field length = 12. Refer to ADC 1310.

AMT02 782 Monetary Amount

 

Description: Monetary amount

DLMS Note: Value may be expressed in 

whole dollars (with no decimal) or in dollar 

and cents (with a decimal included).

M R 1/18 Must use 1
Enclosure 2, ASC 1377A

Page 34

AMT03 478 Credit/Debit Flag Code

 

Description: Code indicating whether 

amount is a credit or debit

DLMS Note: 1. Use to identify the 

Estimated/Actual Cost Flag indicating the 

submitter’s request for credit was based 

upon estimated or actual repackaging cost. 

Use only with Code RPC (Repackaging 

Cost).

2. May be used in interim and final SDR 

reply (e.g., interim reply may be based upon 

an estimate, while the final reply may be 

based upon actual cost). Refer to ADC 

1203.

O ID 1/1 Used 1

Code Name

A Actual 

DLMS Note:

1. Use to indicate that the dollar amount provided represents the actual cost. 

2. Local code A is established for use in 842A/W Version 4030. A data maintenance action 

will be submitted for establishment of this code in a future version of the X12 standard.

E Estimated 

DLMS Note:

1. Use to indicate that the dollar amount provided represents an estimated cost.

2. Local code E is established for use in 842A/W Version 4030. A data maintenance action 

will be submitted to establish this code in a future version of the X12 standard.
Enclosure 2, ASC 1377A

Page 35

N1 Name Pos: 2800 Max: 1

Detail - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. P0304 - If either N103 or N104 is present, then the other is required.

2. R0203 - At least one of N102 or N103 is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

DLMS Note:

This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

M ID 2/3 Used 1

Code Name

C4 Contract Administration Office 

DLMS Note:

1. Use to identify the DoDAAC of Contract Administration Office (CAO) for the identified 

contract number.

2. Populated via EDA interface with WebSDR when available for contract-related discrepant 

shipments.

3. This data element is required on the action activity reply for contract-related shipments 

when unavailable via EDA interface.

SH Shipper 

DLMS Note:

1. Use to identify the shipping activity by Routing Identifier Code, DoDAAC, or 

vendor/contractor CAGE code.

2. Vendor CAGE code populated via EDA interface with WebSDR when available for contractrelated discrepant shipments.

3. This data element is required on the action activity reply for contract-related shipments 

when unavailable via EDA interface.

SU Supplier/Manufacturer 

DLMS Note:

Use with REF01 XB to identify the CAGE code of the manufacturer of the incorrect (wrong) 

item received.

N102 93 Name

 

Description: Free-form name

O AN 1/60 Used 1

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

O ID 1/2 Used 1
Enclosure 2, ASC 1377A

Page 36

Identification Code (67)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

 

Description: Code identifying a party or 

other code

O AN 2/80 Used 1
Enclosure 2, ASC 1377A

Page 37

LM Code Source Information Pos: 3330 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values

M ID 2/2 Used 1

Code Name

DF Department of Defense (DoD)
Enclosure 2, ASC 1377A

Page 38

LQ Industry Code Pos: 3340 Max: >1

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

 

Description: Code identifying a specific 

industry code list

O ID 1/3 Used 1

Code Name

EQ Controlled Inventory Item Code 

DLMS Note:

Use to identify the CIIC associated with the wrong item received.

FD Demilitarization Code 

DLMS Note:

Use to identify Demilitarization Code associated with the wrong item received. 

LQ02 1271 Industry Code

 

Description: Code indicating a code from a 

specific industry code list

O AN 1/30 Used 1
Enclosure 2, ASC 1377A

Page 39

NCA Nonconformance Action Pos: 3400 Max: 1

Detail - Optional

Loop: NCA Elements: 2

User Option (Usage): Used

Purpose: To specify the action that is to be taken in response to a nonconformance condition

Syntax Rules: 

1. P0405 - If either NCA04 or NCA05 is present, then the other is required.

2. R0203 - At least one of NCA02 or NCA03 is required.

Semantics: 

1. NCA03 describes the action that is to be undertaken.

Comments: 

1. NCA04 is used to specify the quantity that is associated with NCA02 or NCA03.

DLMS Note:

This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

NCA01 350 Assigned Identification

 

Description: Alphanumeric characters 

assigned for differentiation within a 

transaction set

DLMS Note: For all transactions, cite 

numeric 1 to satisfy ANSI requirement.

O AN 1/20 Used 1

NCA02 887 Nonconformance Resultant Response 

Code

 

Description: Code identifying a response 

that is the result of a nonconformance 

situation

X ID 1/2 Used 1

Code Name

RS Response Requirements Follow 

DLMS Note:

Use to satisfy ANSI syntax requirements.
Enclosure 2, ASC 1377A

Page 40

NTE Note/Special Instruction Pos: 3500 Max: >1

Detail - Optional

Loop: NCA Elements: 2

User Option (Usage): Used

Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction

Comments: 

1. The NTE segment permits free-form information/data which, under ANSI X12 standard implementations, is not machine processible. The 

use of the NTE segment should therefore be avoided, if at all possible, in an automated environment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

NTE01 363 Note Reference Code

 

Description: Code identifying the functional 

area or purpose for which the note applies

DLMS Note: The following codes are 

authorized.

O ID 3/3 Used 1

Code Name

AES Actual Evaluation Summary 

DLMS Note:

Use to provide general narrative remarks associated with SDR/SQCR reply.

TPO Third Party Organization Notes 

DLMS Note:

Use to identify remarks provided by the ILCO.

A data maintenance action was approved in version 5020. The approved code/name is “ILC 

International Logistics Control Office”.

NTE02 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: 1. Use multiple repetitions of 

NTE, with up to 80 positions for each line.

For AES, WebSDR field length = 750;

For TPO, WebSDR field length = 500.

2. Special characters are not allowed except 

as identified. Valid characters are: @ # $ ( ) 

- = + , / \ [ ] : . and ?

M AN 1/80 Must use 1
Enclosure 2, ASC 1377A

Page 41

DTM Date/Time Reference Pos: 3600 Max: >1

Detail - Optional

Loop: NCA Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. C0403 - If DTM04 is present, then DTM03 is required.

2. P0506 - If either DTM05 or DTM06 is present, then the other is required.

3. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

 

Description: Code specifying type of date 

or time, or both date and time

M ID 3/3 Must use 1

Code Name

198 Completion 

DLMS Note:

Use for SDR/SQCR Completion Date. Use only on completion notice (BNR01=CN).

311 Latest Receiving Date/Cutoff Date 

DLMS Note:

1. This is the suspense date by which requested materiel or documentation must be received.

2. Must use with SDR Reply Code 105, 106, 107, 108, 114, 115, and 117.

3. Use with ship-to location identified at 2/N101/4100. 

4. Pending full implementation of this data field under DLMS, the suspense date must also be 

identified in the SDR Reply remarks field to ensure that the receiving application has visibility 

of this information. Refer to ADC 1249.

446 Replacement 

DLMS Note:

Use to identify the estimated date of reshipment of replacement materiel.

 

DTM02 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year

X DT 8/8 Used 1
Enclosure 2, ASC 1377A

Page 42

REF Reference Identification Pos: 3700 Max: >1

Detail - Optional

Loop: NCA Elements: 4

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

This segment is not used in SQCR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

DLMS Note: The following codes are 

authorized.

M ID 2/3 Must use 1

Code Name

08 Carrier Assigned Package Identification Number 

DLMS Note:

1. Use to identify the commercial carrier-assigned tracking number for materiel return.

2. For 08: WebSDR field length = 17.

16 Military Interdepartmental Purchase Request (MIPR) Number 

DLMS Note:

1. Use to identify the MIPR for disposal of hazardous materiel.

2. For 16: WebSDR field length = 15

GD Return Goods Bill of Lading Number

QE Replacement Customer Reference Number 

DLMS Note:

Use to identify the document number for reshipment of replacement materiel when different 

from the original document number.

QJ Return Material Authorization Number 

DLMS Note:

1. Used to identify the document number applicable to materiel return. Must use return 

document number when SDR Reply Code 105 or 107 applies.

2. Return on original shipment document number preferred, but may not be possible due to 

system constraints. Must use alternate document number for materiel already in a DLA 

Distribution Center necessitating ship-in-place processing for return.

3. For QJ: WebSDR field length = 14.

TH Transportation Account Code (TAC) 

DLMS Note:

Use to identify the TAC for materiel return when applicable.

REF02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

X AN 1/50 Must use 1
Enclosure 2, ASC 1377A

Page 43

REF03 352 Description

 

Description: A free-form description to 

clarify the related data elements and their 

content

DLMS Note: WebSDR field length = 50

X AN 1/80 Used 1

REF04 C040 Reference Identifier

 

Description: To identify one or more 

reference numbers or identification numbers 

as specified by the Reference Qualifier

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

M ID 2/3 Must use 1

Code Name

W8 Suffix 

DLMS Note:

When citing a return document number (Code QJ) or a replacement shipment document 

number (Code QE), use to identify the document number suffix when applicable.

REF04-02 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

M AN 1/50 Must use 1
Enclosure 2, ASC 1377A

Page 44

N1 Name Pos: 4100 Max: 1

Detail - Optional

Loop: N1 Elements: 3

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. P0304 - If either N103 or N104 is present, then the other is required.

2. R0203 - At least one of N102 or N103 is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

DLMS Note: The following codes are 

authorized.

M ID 2/3 Must use 1

Code Name

BT Bill-to-Party 

DLMS Note:

Use to identify the billing DoDAAC for disposal of hazardous materiel.

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) and SQCRs (Type 5). .

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.

LW Customer 

DLMS Note:

1. Use to identify the SDR report initiator by DODAAC (if not identified by 1/N101/1200/ZD).

2. For LW: WebSDR field length =13

ST Ship To 

DLMS Note:
Enclosure 2, ASC 1377A

Page 45

1. Use to identify the location to which materiel must be shipped/returned. Location must be 

identified by DoDAAC or CAGE (for contractors with no assigned DoDAAC). Text address 

may be included in SDR Reply remarks text for DoD activities and must be included for 

contractors identified by CAGE. Must include location when SDR Reply Code 105, 106, 107, 

or 108 applies.

2. Pending full implementation of discrete data elements for the ship-to, the DoDAAC or 

CAGE, must be repeated in the SDR Reply remarks block to ensure that all users will receive 

the specified location. 

TT Transfer To 

DLMS Note:

1. The responding activity uses to designate 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 ADC 1217.

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

identify 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.

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.

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

Identification Code (67)

X ID 1/2 Used 1

Code Name

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

 

Description: Code identifying a party or other code

 

 

X AN 2/80 Used
Enclosure 2, ASC 1377A

Page 46

LM Code Source Information Pos: 4640 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use to identify agency unique coded data related to the characteristics and coding requirements for the disposition and actions resulting from 

the nonconformance condition. This segment is not used for SQCRs

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
Enclosure 2, ASC 1377A

Page 47

LQ Industry Code Pos: 4650 Max: >1

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Used

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

 

Description: Code identifying a specific 

industry code list

DLMS Note: The following codes are 

authorized. 

O ID 1/3 Must use 1

Code Name

GY Cause of Loss Code 

DLMS Note:

1. Use to identify the cause code when providing owner/manager final disposition.

2. Use is optional except when applicable to SDR Document Type 6, 9, P, or W (for vendor 

shipment) and the validated discrepancy is attributed to the fault of the contractor. When this 

is determined, the owner/manager must cite the applicable Cause Code:

CN - Contractor Noncompliance 

CP - Contractor Packaging Noncompliance 

CS - Contractor Noncompliance (Subcontractor) 

3. Also, use to identify the Cause Code when providing DCMA interim reply to the 

owner/manager for contractor noncompliance.

4. A data maintenance action was approved in version 5030. The approved code/name is 

"DCC - Cause Code".

HA Discrepancy Code 

DLMS Note:

1. Use up to three repetitions to identify the discrepancy. (Note: Distribution Depot-originated 

SDRs and their equivalents prepared via WebSDR use up to two discrepancy codes.) 

2. Action activities are required to update inappropriate use of discrepancy codes to support 

use of the SDR record for program metrics.

HD Discrepancy Status or Disposition Code 

DLMS Note:

Use up to three repetitions to identify disposition/status for type 6 (customer originated, vendor 

shipment) and 7 (customer originated, depot shipment) SDRs. Use only one repetition on 

type 8 (depot originated, customer return) and 9 (depot originated, vendor shipment) SDRs. 

(Refer to 2/LQ01/1050, Qualifier D for type document code.). Also referred to as Reply Code.

LQ02 1271 Industry Code

 

Description: Code indicating a code from a 

specific industry code list

X AN 1/30 Must use 1
Enclosure 2, ASC 1377A

Page 48

FA1 Type of Financial Accounting Data Pos: 4660 Max: 1

Detail - Optional

Loop: FA1 Elements: 2

User Option (Usage): Used

Purpose: To specify the organization controlling the content of the accounting citation, and the purpose associated with the accounting citation 

Semantics: 

1. FA101 Identifies the organization controlling the assignment of financial accounting information.

2. FA102 Identifies the purpose of the accounting allowance or charge information.

DLMS Note:

Use to identify credit/debit appropriation/fund code. Also use to identify separate funding information associated with specific actions directed 

by the action point. Use multiple iterations of this loop as needed.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA101 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values

DLMS Note: This data element is required 

for X12 syntax. Select the code that 

corresponds to the organization that is 

responsible for the assignment of the 

DoDAAC used to construct the controlling 

document number for the transaction.

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD) 

DLMS Note:

Use to indicate that the Component is a Department of Defense agency, including Defense 

Logistics Agency. Refer to ADC 1043.

DN Department of the Navy 

DLMS Note:

Includes the United States Marine Corps.

DY Department of Air Force

DZ Department of Army

FG Federal Government

FA102 1300 Service, Promotion, Allowance, or 

Charge Code

 

Description: Code identifying the service, 

promotion, allowance, or charge

O ID 4/4 Used 1

Code Name

A170 Adjustments 

DLMS Note:

Use only for adjustments not specified by any other code.

A520 Base Charge 

DLMS Note:

Use only for materiel charges only.

C930 Export Shipping Charge

D340 Goods and Services Charge 

DLMS Note:

Use for both materiel and related services.

F060 Other Accessorial Service Charge

F560 Premium Transportation

I260 Transportation Direct Billing 

DLMS Note:

Use for non-premium transportation.

R060 Packing, Crating, and Handling Charge
Enclosure 2, ASC 1377A

Page 49

FA2 Accounting Data Pos: 4670 Max: >1

Detail - Mandatory

Loop: FA1 Elements: 2

User Option (Usage): Used

Purpose: To specify the detailed accounting data

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA201 1196 Breakdown Structure Detail Code

 

Description: Codes identifying details 

relating to a reporting breakdown structure 

tree

M ID 2/2 Must use 1

Code Name

B5 Fund Code

I1 Abbreviated Department of Defense (DoD) Budget and Accounting Classification Code (BACC)

L1 Accounting Installation Number 

DLMS Note:

Use to indicate the Authorization Accounting Authority (AAA)/Accounting and Disbursing 

Station Number (ADSN)/Fiscal Station Number (FSN).

FA202 1195 Financial Information Code

 

Description: Code representing financial 

accounting information

M AN 1/80 Must use 1
Enclosure 2, ASC 1377A

Page 59

SE Transaction Set Trailer Pos: 4700 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Used

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending 

(SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SE01 96 Number of Included Segments

 

Description: Total number of segments 

included in a transaction set including ST 

and SE segments

M N0 1/10 Must use 1

SE02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set

DLMS Note: Cite the same number as the 

one cited in ST02.

M AN 4/9 Must use 1
Enclosure 3, ASC 1377A

Page 1

Enclosure 3

Defense Logistics Manual (DLM) 4000.25, Volume 2, Supply Standards and Procedures

Make the following changes to Volume 2. Additions are shown in red bold italics.

Appendix 7.28 SDR Data Elements and Codes

AP7.28.2. SHIPPING AND PACKAGING DISCREPANCY CODES

AP7.28.2.1. The following codes are used to provide a description of the 

discrepant condition. Multiple codes may be used on a single report. Customerprepared SDRs may use up to three discrepancy codes per SDR. SDRs associated 

with Distribution Center receipts may identify up to two discrepancy codes per SDR. 

Preprinted codes on the face of the SF 364 may be supplemented from this list of 

codes. Use of the expanded list of codes is encouraged to clearly identify the 

discrepant situation, reduce the reliance on narrative descriptions, and facilitate capture 

of SDR metrics.

DISCREPANCY CODES

Condition of Materiel

A1 Condition of stored materiel changed because of damage

A2 Condition of stored materiel changed because of deterioration

A3 Stored materiel is misidentified

A5 Stored materiel requires repair

C1 In a condition other than shown on supply document or on the supporting 

inspection/test certificate (if hazardous materiel use code H1)

C2 Expired shelf life item (if hazardous materiel use code H5)

C3 Damaged U.S. Postal Service shipment (Security Assistance customers 

are authorized to use this code for all types of damaged shipments)

C4 Materiel received stripped of parts or components (cannibalized) 

(applicable to materiel returns or repairs only)

C5 Incomplete item received. Do not use for incomplete sets/kits/outfits 

(See discrepancy S9)
Enclosure 3, ASC 1377A

Page 2

DISCREPANCY CODES

Packaging Discrepancy Codes 

P2 Improper packing1

P201 Container inadequate, incorrect, or oversized

P202 Intermediate container inadequate, incorrect, oversized, or omitted

P203 Exterior container inadequate, incorrect, oversized, or omitted

P204 Blocking and bracing inadequate, incorrect, or omitted

P205 Cushioning inadequate, incorrect, or omitted

P206 Level of protection excessive or inadequate

P207 Container deteriorated

P208 Skids incorrect or omitted

P209 Improper packing of hazardous materiels (includes 

ammunitions/explosives)

P210 Non-conformance to specified requirements for packing (explanation 

required)

P211 Improper foam-in-place

P212 Reusable container not used or improperly prepared

P213 Closure incorrect or inadequate

P214 Concealed packing defect found in storage (retail only)

P215 Non-conformance to specified requirements for wood packaging materiel 

(WPM)

P216 Packaging inadequate or incorrect resulting in item corrosion

P299 Improper packing (not identified by other code). See remarks.

Intervening text not shown

AP7.28.5 DISCREPANCY REPORT DOCUMENT TYPE CODES 

Intervening text not shown

AP7.28.5.3. The DLA Disposition Services SDR Type Code (DLMS Qualifier ST) is 

used as a sub-type code in conjunction with the SDR Document Type to further clarify 

the shipment scenario. This data element may be referred to as an SDR Sub-Type 

Code. This data element is conditional; it is used when applicable.

1 Ibid.
Enclosure 3, ASC 1377A

Page 3

SDR DOCUMENT TYPE CODES

Available for DoD WebSDR and Component-Sponsored SDR applications:

5 Storage Quality Control Reports

6 Customer originated, direct vendor/contractor delivery

7 Customer originated, depot/lateral shipment/other