DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 1 January 23, 2024

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 transaction may be used to report Product Quality Deficiency Reports (SF 368), Product Quality Deficiency Investigation Report

(DLA 1227) and related to PQDR Exhibit processing. PQDR originators, screening points, action points, support points, and other interested

parties use this transaction set to exchange product quality deficiency information. DoD logistics users should refer to the Defense Logistics

Management Standards (DLMS) Implementation Convention (IC) available at URL: www.dla.mil/does/DLMS. The DLMS IC provides specific

business rules, conditions, and authorized codes necessary for appropriate use of this IC within the DLMS.

2. Organizations use a single occurrence of this transaction set to transmit a Product Quality Deficiency Report (PQDR) and all associated

actions including results of investigation and exhibit tracking. Use a single occurrence (transaction set) of this transaction set to transmit

single reports or responses to single or multiple organizations.

3. Users operating under the DLMS must reference the Defense Logistics Manual (DLM) 4000.25, Volume 2, Chapter 24, and Appendix

7.27 for supplemental guidance supporting information exchange under the Product Quality Deficiency Report (PQDR) Program (DLAR

4155.24/AR 702-7/SECNAVINST 4855.5B/AFR 74-61) at: www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp.

4. Refer to the DLMS Dictionary (Logistics Data Resources Management System (LOGDRMS)) for selected data element definitions and

code values, or cross-reference to the authoritative code source: www.dla.mil/j-6/dlmso/eApplications/LogDataAdmin/dlmsdicdir.asp. 

5. 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 Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS

6. Components must coordinate their unique system requirements and business rules prior to use. This DLMS IC may contain:

 a. Data associated with this transaction set that may or not be accepted or understood by the recipient's automated processing system.

 b. Data associated with an approved change to this transaction set that may not have an established implementation date in the

receiving system. This data may not be received or understood by the recipient's automated processing system.

 c. Data elements which have expanded field sizes above existing capability may not be supported by the recipient's automated

processing system.

 d. Data elements which have an expanded field size above existing PQDRII capability may not be supported by the recipient's automated

processing system.

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

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

from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/ .

- ADC 1007, New DLMS 842P, PQDR Data Exchange and Enhanced Exhibit Tracking via Standard Logistics Transactions

- ADC 1007B, Administrative Update to the DLMS 842P Product Quality Deficiency Report (PQDR) Data Exchange

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on April 24, 2014

- ADC 1007C, Code Updates to the DLMS 842P Product Quality Deficiency Report (PQDR) Data Exchange (Supply/Deficiency Reporting)

- ADC 1007D, PQDR Establishment, Product Quality Deficiency Report (PQDR) System Structure Change and Code Updates to the DLMS

842P PQDR Data

- ADC 1007E, DLMS 842P Systemic Processing, Transaction Business Rules and Coding Updates

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

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

- ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation

Conventions and DLMS Manuals

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 03, 2017

- 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

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

1. This transaction may be used to report Product Quality Deficiency Reports (SF 368), Product Quality Deficiency Investigation Report

(DLA 1227) and related to PQDR Exhibit processing. PQDR originators, screening points, action points, support points, and other interested

parties use this transaction set to exchange product quality deficiency information. DoD logistics users should refer to the Defense Logistics

Management Standards (DLMS) Implementation Convention (IC) available at URL: www.dla.mil/does/DLMS. The DLMS IC provides specific

business rules, conditions, and authorized codes necessary for appropriate use of this IC within the DLMS.

2. Organizations use a single occurrence of this transaction set to transmit a Product Quality Deficiency Report (PQDR) and all associated

actions including results of investigation and exhibit tracking. Use a single occurrence (transaction set) of this transaction set to transmit

single reports or responses to single or multiple organizations.

3. Users operating under the DLMS must reference the Defense Logistics Manual (DLM) 4000.25, Volume 2, Chapter 24, and Appendix

7.27 for supplemental guidance supporting information exchange under the Product Quality Deficiency Report (PQDR) Program (DLAR

4155.24/AR 702-7/SECNAVINST 4855.5B/AFR 74-61) at: www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp.

4. Refer to the DLMS Dictionary (Logistics Data Resources Management System (LOGDRMS)) for selected data element definitions and

code values, or cross-reference to the authoritative code source: www.dla.mil/j-6/dlmso/eApplications/LogDataAdmin/dlmsdicdir.asp. 

5. 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 Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS

6. Components must coordinate their unique system requirements and business rules prior to use. This DLMS IC may contain:

 a. Data associated with this transaction set that may or not be accepted or understood by the recipient's automated processing system.

 b. Data associated with an approved change to this transaction set that may not have an established implementation date in the

receiving system. This data may not be received or understood by the recipient's automated processing system.

 c. Data elements which have expanded field sizes above existing capability may not be supported by the recipient's automated

processing system.

 d. Data elements which have an expanded field size above existing PQDRII capability may not be supported by the recipient's automated

processing system.

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

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

from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/ .

- ADC 1007, New DLMS 842P, PQDR Data Exchange and Enhanced Exhibit Tracking via Standard Logistics Transactions

- ADC 1007B, Administrative Update to the DLMS 842P Product Quality Deficiency Report (PQDR) Data Exchange

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on April 24, 2014

- ADC 1007C, Code Updates to the DLMS 842P Product Quality Deficiency Report (PQDR) Data Exchange (Supply/Deficiency Reporting)

- ADC 1007D, PQDR Establishment, Product Quality Deficiency Report (PQDR) System Structure Change and Code Updates to the DLMS

842P PQDR Data

- ADC 1007E, DLMS 842P Systemic Processing, Transaction Business Rules and Coding Updates

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

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

- ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation

Conventions and DLMS Manuals

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 03, 2017

- 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

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on 
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 2 January 23, 2024

August 09, 2018

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

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on March 1, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

August 09, 2018

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

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on March 1, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

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

LOOP ID - N1 LOOP ID - N1 >1

1200 N1 Name O 1 Used

1700 PER Administrative Communications

Contact

O >1 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL >1 N2/0100L N2/0100L

0100 HL Hierarchical Level M 1 N2/0100 Must use

0200 LIN Item Identification O 1 Used

0600 DTM Date/Time Reference O >1 Used

0700 REF Reference Identification O >1 Used

0750 CS Contract Summary O 1 Used

1020 PWK Paperwork O >1 Used

LOOP ID - LM LOOP ID - LM >1

1040 LM Code Source Information O 1 Used

1050 LQ Industry Code M >1 Must use

LOOP ID - NCD LOOP ID - NCD >1

2300 NCD Nonconformance Description O 1 Used

2400 NTE Note/Special Instruction O >1 Used

2600 REF Reference Identification O >1 Used

2700 QTY Quantity O >1 Used

2730 AMT Monetary Amount O >1 Used

LOOP ID - N1 LOOP ID - N1 >1

2800 N1 Name O 1 Used

2900 N2 Additional Name Information O 2 Used

3000 N3 Address Information O 2 Used

3100 N4 Geographic Location O 1 Used

3300 PER Administrative Communications

Contact

O >1 Used

LOOP ID - NCA LOOP ID - NCA >1

3400 NCA Nonconformance Action O 1 Used

3500 NTE Note/Special Instruction O >1 Used

4700 SE Transaction Set Trailer M 1 Must use

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.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 3 January 23, 2024

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

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

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 transaction number assigned

by the originating system of the transaction set, or

the originator's application program, i.e., 200900001.

M AN 4/9 Must use

ST03 1705 Implementation Convention Reference

Description: Reference assigned to identify

Implementation Convention

DLMS Note: Use to indicate this transmission uses

the 842P DLMS Implementation Convention (IC).

Enter the DLMS IC 004030F842P0PA00.

O AN 1/35 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 4 January 23, 2024

BNR Beginning Segment For

Nonconformance Report

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

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

BNR01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

DLMS Note: The following Transaction Codes are

authorized to describe the PQDR Transaction Code.

M ID 2/2 Must use

Code Name

00 Original

DLMS Note:

Used when the Originator forwards to the Screening Point. Originators are required to execute this

transaction set within 24 hours of discovery for Category I and three calendar days of discovery for

Category II PQDRs.

01 Cancellation

DLMS Note:

Used when PQDR is Cancelled. Only Screening Points may cancel a PQDR. A cancelled PQDR cannot

be reopened.

03 Delete

DLMS Note:

Used by Screening Points and Action Points to request ownership of a PQDR to be transferred back to

them.

06 Confirmation

DLMS Note:

Used by an automated IT system to confirm transaction receipt from another system.

08 Status

DLMS Note:

Used to acknowledge that a PQDR was received and provide current status to the previous point. 

10 Not Found

DLMS Note:

Used by Screening Point, Action Point or Support Point to request status or follow up on a missing

exhibit request, exhibit shipment or exhibit receipt.

11 Response

DLMS Note:

Used when the Support Point completes their investigation and returns the PQDR to an Action Point

and the Action Point does not exist within the same system.

12 Not Processed

DLMS Note:

Use to indicate that a PQDR was received by an incorrect Screening Point, Action Point, or Support 
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 5 January 23, 2024

Point and could not be processed. The transaction returns the misdirected PQDR to the previous

processing point.

13 Request

DLMS Note:

Used to request the exhibit and provide shipping information.

14 Advance Notification

DLMS Note:

Used to provide exhibit shipment information to the requestor.

22 Information Copy

DLMS Note:

Used to send information copy of PQDR to another system. Used for dissemination to non-action

activities outside of the PQDR process in another system. Used to provide PQDR to other agencies

with a need to know. All data fields should be sent to present the entire PQDR to the receiver. 

25 Incremental

DLMS Note:

Used by Support or Action Point to provide investigation status of the PQDR to the previous owner.

44 Rejection

DLMS Note:

Used when WebPQDR determines that 842P transaction is non-compliant with this standard or when a

recipient system of an 842P is unable to process a transaction due to its unique data requirements (i.e.,

duplicate Report Control Number). 

45 Follow-up

DLMS Note:

A systemically generated transaction used to request a status when a processing point has not

provided investigation status via interim reply or the like.

47 Transfer

DLMS Note:

Used to redirect a PQDR to another Screening Point, Action Point, or Support Point within the

component due to major data element changes when the Screening Point determines that a

cancellation is not a preferred resolution.

53 Completion

DLMS Note:

Used by Screening Point to close out and notify other PQDR processing points of PQDR process

completion for a given PQDR. Only the Screening Point may perform this transaction.

CN Completion Notification

DLMS Note:

Used when the Action Point completes their investigation and returns the PQDR to a Screening Point

and the Screening Point does not exist within the same system.

CO Corrected

DLMS Note:

Use to transmit a General Correspondence, information concerning the PQDR status from the sender to

the receiver, or to send corrections with an explanation of changes. For inter-service PQDRs, the

Originating Point may only submit this transaction to the Screening Point.

DA Delegate to Alternate

DLMS Note:

1. Used by the responsible Action Point or Support Point to delegate to another Support Point without

changing the responsible Support Point.

2. ASC X12 added this migration code in version/release 7010.

ED Exhibit Disposition

DLMS Note:

1. Used by the current exhibit holder to confirm compliance with materiel disposition instructions.

2. ASC X12 added this migration code in version/release 7010.

ER Exhibit Receipt
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 6 January 23, 2024

DLMS Note:

1. Used to document exhibit receipt. When the PQDR is located at the Action Point after

acknowledgement level, only the Screening Point and Action Point may have use of this Transaction.

After this point, either the Screening Point, Action Point or Support Point may transmit an exhibit receipt

transaction.

2. If sent as a late exhibit receipt, PQDR is reassigned to the sender’s level. 

3. ASC X12 added this migration code in version/release 7010.

1. Used to document exhibit receipt. When the PQDR is located at the Action Point after

acknowledgement level, only the Screening Point and Action Point may have use of this Transaction.

After this point, either the Screening Point, Action Point or Support Point may transmit an exhibit receipt

transaction.

2. If sent as a late exhibit receipt, PQDR is reassigned to the sender’s level. 

3. ASC X12 added this migration code in version/release 7010.

FA Forward to Action Point

DLMS Note:

1. Used when the Screening Point forwards a PQDR to an Action Point and the Action Point does not

exist within the same AIS.

2. ASC X12 added this migration code in version/release 7010. 

FC Forward to Contractor

DLMS Note:

1. Used when the Action Point or Support Point sends PQDR investigation request to a contractor..

2. ASC X12 added this migration code in version/release 7010. 

FS Forward to Support Point

DLMS Note:

1. Used when the Action Point forwards a PQDR to a Support Point and the Support Point does not

exist within the same system.

2. ASC X12 added this migration code in version/release 7010. 

MD Materiel Disposition

DLMS Note:

1. Used by the Support Point or Action Point after the investigation is complete to provide final materiel

disposition instructions. 

2. ASC X12 added this migration code in version/release 7010. 

RO Reopen

DLMS Note:

1. Used when a PQDR is reopened by the system sending the transaction and a PQDR needs to be

reopened in the receiving system. This transaction notifies other systems that a PQDR has been

reopened by the Screening Point, or that the other PQDR processing points (Originator, Action, or

Support Point) have requested that the PQDR to be reopened.

2. ASC X12 added this migration code in version/release 7010. 

RR Reply Rebuttal

DLMS Note:

1. Used to rebut an investigation response. PQDR placed at the prior ownership level. 

2 ASC X12 added this migration code in version/release 7010. 

SU Status Update

DLMS Note:

1. Use to send an Update to correct or append specific data fields in another information system. Used

to disseminate information to other process points. 

2. This element may be populated/updated by the Screening Point, Action Point or Support Point. 

BNR02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

DLMS Note: Enter "Z" to satisfy ANSI

M AN 1/50 Must use

BNR03 373 Date M DT 8/8 Must use
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Ref Id Element Name Req Type Min/Max Usage

004030F842P0PA10 7 January 23, 2024

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). i.e. 20091231 for April 02,

2012

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. 

i.e. 0859 for 08:59 AM.

O TM 4/8 Must use

BNR05 886 Nonconformance Report Status Code

Description: Code identifying the status of the

nonconformance report

O ID 2/2 Used

Code Name

CL Closed

DLMS Note:

Use to indicate that the PQDR is in a closed status. Where applicable, provide detailed status using the

PQDR Investigation Status Code (2/LQ01/1050 Code GK).

FI Final

DLMS Note:

Use to indicate that the PQDR investigation is completed. Where applicable, provide detailed status

using the PQDR Investigation Status Code (2/LQ01/1050 Code GK).

OI Open, Waiting for Cause and Corrective Action Implementation

DLMS Note:

Use to indicate that the PQDR investigation is not complete. Where applicable, provide detailed status

using the PQDR Investigation Status Code (2/LQ01/1050 Code GK).

RE Reopened

DLMS Note:

Use to indicate that the PQDR status has changed from closed to open in the sending system. Where

applicable, provide detailed status using the PQDR Investigation Status Code (2/LQ01/1050 Code GK).

BNR06 640 Transaction Type Code

Description: Code specifying the type of

transaction

O ID 2/2 Used

Code Name

QD Product Quality Deficiency

DLMS Note:

Use to indicate that the transaction set contains a PQDR.

QR Product Quality Deficiency Response

DLMS Note:

Use to indicate the transaction set contains a PQDR Response.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 8 January 23, 2024

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. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other 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 separate iterations of this 1/N1/1200 loop to identify the organizations sending and receiving the transaction set and to identify

other parties involved with the processing of the PQDR.

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: The following codes are authorized. 

Sender and receiver must be identified in N106 by

using the TO and FR.

M ID 2/3 Must use

Code Name

41 Submitter

DLMS Note:

Use to identify the DoDAAC of the current Originator DoDAAC.

91 Action Party

DLMS Note:

Use to identify the DoDAAC of the current Action Point DoDAAC. This is the activity responsible for the

investigation and resolution of the deficiency.

92 Support Party

DLMS Note:

Use to identify the DoDAAC of the current Support Point DoDAAC. This is the activity handling the

investigation.

RN Repair or Refurbish Location

DLMS Note:

Use to identify the CAGE or DoDAAC Last Repair Facility, aka Last Rework Facility.

ZD Party to Receive Reports

DLMS Note:

Use to identify additional party(ies) to receive a copy of the PQDR via electronic retransmission of the

842P.

ZQ Screening Point

DLMS Note:

Use to identify the DoDAAC of the current Screening Point activity.

N102 93 Name

Description: Free-form name

X AN 1/60 Used

N103 66 Identification Code Qualifier X ID 1/2 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Ref Id Element Name Req Type Min/Max Usage

004030F842P0PA10 9 January 23, 2024

Description: Code designating the system/method

of code structure used for Identification Code (67)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

N104 67 Identification Code

Description: Code identifying a party or other code

DLMS Note: Default for PQDR is to use the

DoDAAC i.e. N00104.

X AN 2/80 Used

N106 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

O ID 2/3 Used

Code Name

FR Message From

DLMS Note:

Use with the appropriate 1/N101/1200 code to indicate that the organization cited in N104 is originating

the transaction set.

TO Message To

DLMS Note:

Use with the appropriate 1/N101/1200 code to indicate that the organization cited in N104 is receiver of

the transaction set.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 10 January 23, 2024

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 multiple repetitions as needed to identify applicable points of contact and communication numbers. Must provide email address and at

least one phone number.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

Code Name

ES Electronic Submission Recipient

DLMS Note:

Use to identify the Screening Point contact information, if not identified as sender (FR) or receiver (TO). 

Use with a "ZQ" identified in line N101.

FC Forwarder Contact

DLMS Note:

Use to identify the Action Point contact information, if not identified as sender (FR) or receiver (TO). 

Use with a "91" identified in line N101.

PI Preparer

DLMS Note:

Use to identify the Originator contact information, if not identified as sender (FR) or receiver (TO). Use

with a "41" identified in line N101.

QA Quality Assurance Contact

DLMS Note:

Use to identify the Support Point contact information, if not identified as sender (FR) or receiver (TO). 

Use with a "92" identified in line N101.

RQ Requestor

DLMS Note:

Use to identify the point of contact to receive information Copy of PQDR. Use when a "ZD" is identified

in line N101.

PER02 93 Name

Description: Free-form name

DLMS Note: Provide the last name, first name,

middle initial, and rank, as required, of the individual

named as point of contact. Include blank spaces

between name components and periods after

initials.

DLMS Note: Provide the last name, first name,

middle initial, and rank, as required, of the individual

named as point of contact. Include blank spaces

between name components and periods after

initials.

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 11 January 23, 2024

Code Name

EM Electronic Mail

DLMS Note:

Use to identify the E-mail address.

PER04 364 Communication Number

Description: Complete communications number

including country or area code when applicable

X AN 1/256 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used

Code Name

TE Telephone

DLMS Note:

Use to identify the commercial phone number, i.e. 1-234-456-7899.

PER06 364 Communication Number

Description: Complete communications number

including country or area code when applicable

X AN 1/256 Used

PER07 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the DSN Phone number, i.e. 456-7890.

PER08 364 Communication Number

Description: Complete communications number

including country or area code when applicable

X AN 1/256 Used

PER09 443 Contact Inquiry Reference

Description: Additional reference number or

description to clarify a contact number

DLMS Note: Use as needed to identify the office

symbol/activity code for the party identified or the

position title or the point of contact, i.e., Quality

Assurance Specialist.

O AN 1/20 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 12 January 23, 2024

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

User Option (Usage): Must use

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

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

HL03 735 Hierarchical Level Code

Description: Code defining the characteristic of a

level in a hierarchical structure

M ID 1/2 Must use

Code Name

I Item

DLMS Note:

Optional use to identify IUID data consistent with IUID data requirements. The IUID data is carried in the

REF and N1 segments; the NCD segment is required by ANSI syntax; and no other segments are used

in the IUID loop. Use a separate IUID loop for each item. Skip this level when not applicable. The UII

value and some of the associated data elements are DLMS enhancements. These elements may not

be received or understood by the recipient’s automated processing system.

W Transaction Reference Number

DLMS Note:

Optional use when multiple requisition or shipment document numbers are applicable. Use this

document loop to report the second and any additional document numbers. Use a separate document

number loop for each applicable document number. Up to 9 document number loops may be used per

transaction (for a total of 10 document numbers per PQDR, since the Report Loop also contains one of

the applicable document numbers). The document number loop may include the document number as

well as associated credit information data carried in the REF, DTM, AMT, NI segments; no other

segments are used in the document number loop.

Optional use when multiple requisition or shipment document numbers are applicable. Use this

document loop to report the second and any additional document numbers. Use a separate document

number loop for each applicable document number. Up to 9 document number loops may be used per

transaction (for a total of 10 document numbers per PQDR, since the Report Loop also contains one of

the applicable document numbers). The document number loop may include the document number as

well as associated credit information data carried in the REF, DTM, AMT, NI segments; no other

segments are used in the document number loop.

RP Report

DLMS Note:

Mandatory use in all transactions to provide detail information associated with the transaction.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 13 January 23, 2024

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 30

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:

Use LIN Segment Product/Service ID pairs as needed to fully identify/describe the nonconforming materiel and associated information such

as the next higher assembly and engine. Skip over any values that are not applicable.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: Must use one of FS, FT, or NN for

materiel identification.

M ID 2/2 Must use

Code Name

FS National Stock Number

DLMS Note:

1. Use to identify the deficient Item NSN (or temporary Navy Item Control Number (NICN) of the

nonconforming materiel. Equates to SF368, Block 5.

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

FT Federal Supply Classification

DLMS Note:

1. Use to identify the 4 character FSC portion of the NSN for the nonconforming materiel. FSC or

National Item Identification Number (NIIN) is required when entire NSN is unavailable. If FSC is

provided, the manufacturer’s part number and CAGE code must also be provided.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 14 January 23, 2024

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

NN National Item Identification Number

DLMS Note:

1. Use to identify the 9 character NIIN portion of the NSN for the nonconforming materiel. FSC (in

association with the manufacturer’s part number and CAGE code) or NIIN is required when entire NSN

is unavailable.

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

3. Qualifier NN is a migration code approved for use in X12 version 5020.

1. Use to identify the 9 character NIIN portion of the NSN for the nonconforming materiel. FSC (in

association with the manufacturer’s part number and CAGE code) or NIIN is required when entire NSN

is unavailable.

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

3. Qualifier NN is a migration code approved for use in X12 version 5020.

SW Stock Number

DLMS Note:

1. Use to identify a local stock number (LSN). The LSN is applicable when an NSN has not been

assigned and the deficient item has been receipted under an LSN.

2. When an LSN is used, also provide manufacturer’s part number and CAGE code.

3. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

ZZ Mutually Defined

DLMS Note:

1. Use to identify materiel when no other authorized codes apply (includes Management Control

Numbers) (MCNs) and Navy Item Control Numbers (NICNs).

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

LIN03 234 Product/Service ID

Description: Identifying number for a product or

service

M AN 1/48 Must use

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.

X ID 2/2 Used

Code Name

MG Manufacturer's Part Number

DLMS Note:

1. Use to identify the Deficient Item Part Number (also known as Supplier/Manufacturers Part Number

of the deficient materiel). Equates to SF368, Block 8. Use in conjunction with the manufacturer’s CAGE

code at LIN06 and/or supplier CAGE code at LIN14.

2. Part number must be provided when identifying an item by FSC or LSN.

3. When available, inclusion of the part number is recommended when identifying an item by NSN.

LIN05 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN06 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

MF Manufacturer

DLMS Note:
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 15 January 23, 2024

Use to identify Manufacturer CAGE Code of the nonconforming materiel. Equates to SF368, Block 9a.

LIN07 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN08 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

CN Commodity Name

DLMS Note:

Use to identify the Deficient Item Nomenclature of the nonconforming materiel. Equates to SF368,

Block 6.

LIN09 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN10 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

W2 Work Unit Number

DLMS Note:

1. Use to identify the Work Unit Code (WUC) or Equipment Item Code (EIC) of the nonconforming item.

USMC stores the Table of Authorized Materiel (TAM) code in this field. 

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

LIN11 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN12 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

OT Internal Number

DLMS Note:

1. Use to identify the Air Force Reference Designator.

2. This is the Reference Designator (C017)/LCN (F022) of the item for which the report is being

submitted. For the C017 Reference Designator refer to the applicable -06 TO. For the F022 LCN refer

to the Integrated Management Information System (IMIS).

3. This element may only be populated/updated by the Air Force Originating Point, Screening Point, or

Action Point.

1. Use to identify the Air Force Reference Designator.

2. This is the Reference Designator (C017)/LCN (F022) of the item for which the report is being

submitted. For the C017 Reference Designator refer to the applicable -06 TO. For the F022 LCN refer

to the Integrated Management Information System (IMIS).

3. This element may only be populated/updated by the Air Force Originating Point, Screening Point, or

Action Point.

LIN13 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN14 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Ref Id Element Name Req Type Min/Max Usage

004030F842P0PA10 16 January 23, 2024

Code Name

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

1. Use to identify the Prime Contractors Code (CAGE) for the supplier of the nonconforming materiel.

2. Use the Qualifier ZB in the LIN segment as the primary means to identify the supplier of the

nonconforming materiel. Use the Qualifier PG in the N1 segment to provide an address that is different

than the address officially listed with the CAGE in Central Contractor Registry (CCR)/Business

Identification Number Cross-Reference System (BINCS).

3. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

1. Use to identify the Prime Contractors Code (CAGE) for the supplier of the nonconforming materiel.

2. Use the Qualifier ZB in the LIN segment as the primary means to identify the supplier of the

nonconforming materiel. Use the Qualifier PG in the N1 segment to provide an address that is different

than the address officially listed with the CAGE in Central Contractor Registry (CCR)/Business

Identification Number Cross-Reference System (BINCS).

3. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN15 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN16 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: Use the next five qualifiers when

applicable to identify the Next Higher Assembly.

X ID 2/2 Used

Code Name

F8 Next Higher Used Assembly

DLMS Note:

1. Use to identify the Next Higher Assembly NSN. Equates to SF368, Block 17a.

2. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN17 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN18 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

GE Generic Name Description

DLMS Note:

1. Use to identify the Next Higher Assembly Nomenclature. Equates to SF368, Block 17b.

2. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN19 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN20 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

EM Equipment Identification Number

DLMS Note:

1. Use to identify Next Higher Assembly Serial Number. Equates to SF368, Block 17d.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 17 January 23, 2024

2. For the Deficient Item Serial Number (SF368, Block 11) refer to 2/LIN20/0200 Code SE in the IUID

loop. For Engine Serial Number, refer to 2/LIN26/0200 Code SN in the report loop. For serial number of

the End Item (SF 368, Block 18d), refer to 2/REF01/0700 Code SE in the report loop.

3. The serial number may not exceed 30 characters in accordance with IUID policy.

4. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

2. For the Deficient Item Serial Number (SF368, Block 11) refer to 2/LIN20/0200 Code SE in the IUID

loop. For Engine Serial Number, refer to 2/LIN26/0200 Code SN in the report loop. For serial number of

the End Item (SF 368, Block 18d), refer to 2/REF01/0700 Code SE in the report loop.

3. The serial number may not exceed 30 characters in accordance with IUID policy.

4. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN21 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN22 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

PU Part Reference Number

DLMS Note:

1. Use to identify Next Higher Assembly Part Number. Equates to SF368, Block 17c.

2. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN23 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN24 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

XZ Contractor Establishment Code

DLMS Note:

1. Use to identify the Next Higher Assembly’s CAGE associated with the next higher assembly’s part

number.

2. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN25 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN26 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: Use the next two qualifiers when

applicable to identify the engine.

X ID 2/2 Used

Code Name

SN Serial Number

DLMS Note:

1. Use to identify the Engine Serial Number. This is a DLMS enhancement not specifically identified to

an SF364 block number.

2. For the Deficient Item Serial Number (SF368, Block 11) refer to 2/LIN20/0200 Code SE in the IUID

loop. For Next Higher Assembly Serial Number (SF368, Block 17d) refer to 2/LIN20/0200 Code EM in

the report loop. For serial number of the End Item (SF 368, Block 18d), refer to 2/REF01/0700 Code SE
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 18 January 23, 2024

in the report loop.

3. The serial number may not exceed 30 characters in accordance with IUID policy.

4. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN27 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN28 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

X ID 2/2 Used

Code Name

MN Model Number

DLMS Note:

1. Use to identify the Engine Model Number.

2. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

LIN29 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used

LIN30 235 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.

X ID 2/2 Used

LIN31 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 19 January 23, 2024

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. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

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

3. P0506 - If either DTM05 or DTM06 is present, then the other 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

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

Code Name

002 Delivery Requested

DLMS Note:

1. Use to identify the Exhibit Requested Date. This is the date the exhibit was requested by the Action

or Support Point.

2. This element may be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

009 Process

DLMS Note:

1. Use to identify the Screening to Action Date (also known as Screening Point Release Date). This is

the date the Screening Point released the deficiency report to the Action Point.

2. This element may only be populated/updated by the Screening Point.

011 Shipped

DLMS Note:

1. Use to identify the Exhibit Shipped Date.

2. This element may be populated by any role. For inter-service transactions, only the Screening Point,

Action Point and Support Point can update this element.

050 Received

DLMS Note:

1. Use to identify the Exhibit Received Date. This is the date exhibit was received by the Action or

Support Point activity.

2. This element may be populated/updated by the Support Point or Action Point.

094 Manufacture

DLMS Note:

1. Use to identify the Date of Manufacture.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

145 Opening Date

DLMS Note:

1. Used to identify the date the PQDR was reopened. May only be used when BNR02 conveys qualifier
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 20 January 23, 2024

code RO.

2. This element may only be populated/updated by the Screening Point.

146 Closing Date

DLMS Note:

1. Use to identify the date the PQDR was closed. This is the date the PQDR is closed by the Screening

Point.

2. This element may only be populated/updated by the Screening Point.

177 Cancellation

DLMS Note:

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

2. This element may only be populated/updated by the Screening Point.

3. May only be used when BNR02 conveys qualifier code 01.

188 Credit Advice

DLMS Note:

1. Use to identify the date credit was issued, Credit Date.

2. Use in the Document Number Loop (HL01=W).

3. If multiple document numbers are applicable, identify the credit date applicable to the document

number included in the Report Loop (HL01=RP) and use a separate Document Number Loop

(HL01=W) for each additional document number and credit date combination.

4. When providing a credit date, also provide the credit value (AMT01=PD) (and the DLA Credit Memo

Number, when applicable) in the same loop.

5. This element may only be populated/updated by the Action Point.

1. Use to identify the date credit was issued, Credit Date.

2. Use in the Document Number Loop (HL01=W).

3. If multiple document numbers are applicable, identify the credit date applicable to the document

number included in the Report Loop (HL01=RP) and use a separate Document Number Loop

(HL01=W) for each additional document number and credit date combination.

4. When providing a credit date, also provide the credit value (AMT01=PD) (and the DLA Credit Memo

Number, when applicable) in the same loop.

5. This element may only be populated/updated by the Action Point.

212 Returned to Customer

DLMS Note:

Use to identify the Exhibit Return Date. This is the date the exhibit was returned to the activity as

stipulated in the disposition instructions.

214 Date of Repair/Service

DLMS Note:

1. Use to identify the date the nonconforming item was repaired or overhauled.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

368 Submittal

DLMS Note:

1. Use to identify the Action to Support Date. This is the date the Action Point released PQDR to the

Support Point.

2. This element may only be populated/updated by the Action Point.

440 Release of Information

DLMS Note:

1. Use to identify Action to Screening Date. This is the date the Action Point released the PQDR to the

Screening Point.

2. This element may only be populated/updated by the Action Point.

508 Extended

DLMS Note:

1. Use to identify the Exhibit Extended Hold Date. This is the date the exhibit is to be kept in holding

status if beyond 90 days.

2. This element may be populated/updated by the Action Point or the Screening Point.

512 Warranty Expiration
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 21 January 23, 2024

DLMS Note:

1. Use to identify the Warranty Expiration Date.

2. Use in the Report Loop (HL01=RP) or in the applicable IUID Loop (HL01=I) if providing different

warranty expiration dates for uniquely identified items.

3. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

514 Transferred

DLMS Note:

1. Use to identify the Support to Action Date (also known as the Support Point Release Date). This is

the date the PQDR was returned to the Action Point by the Support Point.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

516 Discovered

DLMS Note:

1. Use to identify the Date Deficiency was Discovered. This is the date when the deficiency occurred or

was discovered by the originator. Equates to SF368, Block4.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point may update this element.

636 Date of Last Update

DLMS Note:

Use to identify Last Update Date. This is the last date the PQDR was updated to PQDRII.

649 Document Due

DLMS Note:

1. Use to identify the Support Point Due Date.

2. Only Support Point may assign the date update information is due back to the Action Point and be

populated/updated by the Support Point.

868 Last Follow-up

DLMS Note:

Use to identify the Exhibit Follow-up Date. This is the date an exhibit follow-up was forwarded to the

exhibit holding activity.

909 Contestability

DLMS Note:

1. Use to identify the Action Point Rebuttal/Controvert Date. This is the date the Action Point rebutted

the final reply from Support Point.

2. This element may only be populated/updated by the Action Point.

922 Original Receipt

DLMS Note:

1. Use to identify the date the nonconforming item was received by the Originator.

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point may update this element.

947 Preparation

DLMS Note:

1. Use to identify the date the PQDR was completed by the originator and submitted to the Screening

Point (also known as Submitted Date, Preparation Date, Originator Release Date, Screening Point

receipt date). This is the date the SF368 was filled out (completed). Equates to former Block 1c, Date

Submitted, on the old version of the SF368.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point may update this element.

1. Use to identify the date the PQDR was completed by the originator and submitted to the Screening

Point (also known as Submitted Date, Preparation Date, Originator Release Date, Screening Point

receipt date). This is the date the SF368 was filled out (completed). Equates to former Block 1c, Date

Submitted, on the old version of the SF368.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point may update this element.

AAG Due Date

DLMS Note:
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 22 January 23, 2024

1. Use to identify the Action Point Due Date.

2. Only Action Point may assign this date based on category that a response is due back to Screening

Point.

3. This element may be populated/updated by the Action Point or Screening Point

ABY Product Held Until

DLMS Note:

1. Use to identify the Exhibit Hold Date. This is the date an item will be held until before disposition.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point may update this element.

ACK Acknowledgment

DLMS Note:

1. Use to identify the Acknowledged Date by the sender.

2. This element may be used and/or updated by the Screening Point, Action Point, and/or the Support

Point.

ACZ Controvert Date

DLMS Note:

1. Use to identify the Screening Point Rebuttal Date. This is the date the Screening Point rebutted the

final reply from Action Point.

2. This element may only be populated/updated by the Screening Point.

DIS Disposition

DLMS Note:

1. Use to identify the Exhibit Final Disposition Instruction Date.

2. This element may be populated/updated by the Action Point or Screening Point.

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
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 23 January 23, 2024

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 PQDR Report Control Number (RCN). Use multiple repetitions as needed to identify additional reference numbers

associated with a PQDR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

Code Name

0D Subject Property Verification Source

DLMS Note:

Must use to identify the Property Type Code to distinguish Government-furnished property (GFP) from

non-GFP. Cite the applicable code in REF02: 

Y – GFP 

R – GFP returned by the contractor to DoD inventory. 

N – Not GFP 

U – Unknown

Must use to identify the Property Type Code to distinguish Government-furnished property (GFP) from

non-GFP. Cite the applicable code in REF02: 

Y – GFP 

R – GFP returned by the contractor to DoD inventory. 

N – Not GFP 

U – Unknown

17 Client Reporting Category

DLMS Note:

1. Use to identify deficiencies as either Category I or II IAW the PQDR Joint Regulation.

2. DLA Audits are identified as CAT III (DLA only).

3. Enter value as I, II, or III as applicable.

4. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

2E Foreign Military Sales Case Number

DLMS Note:

1. Reserved for future use to identify FMS Case Numbers for FMS PQDRs.

2. This element may only be populated or updated by the ILCO serving as both the Originating Point

and the Screening Point.

3. This qualifier must be used with the Military service FMS indicators as the first position of the

RCN/Originating DoDAAC. 

B – Army FMS customer 

D – Air Force FMS Customer 

P – Navy FMS Customer 

K – Marine Corps FMS Customer

1. Reserved for future use to identify FMS Case Numbers for FMS PQDRs.

2. This element may only be populated or updated by the ILCO serving as both the Originating Point

and the Screening Point.

3. This qualifier must be used with the Military service FMS indicators as the first position of the

RCN/Originating DoDAAC. 

B – Army FMS customer 

D – Air Force FMS Customer 

P – Navy FMS Customer 

K – Marine Corps FMS Customer

2I Tracking Number

DLMS Note:

Use to identify the Exhibit Tracking Number. This is the commercial carrier’s number provided to the 
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 24 January 23, 2024

shipping activity to track the exhibit.

3H Case Number

DLMS Note:

1. Use to identify the Action Points control number. This will be the sending system assigned number.

i.e. DLA Case Control Number, Action Point Control Number, etc. Submitting activity's control number,

if different than RCN. Identify the system that created the control number in REF03.

2. This element may only be populated/updated by the Action Point.

44 End Use Number

DLMS Note:

1. Use to identify the End Item Type/Model/Series. This is the major weapons system with which the

end item is associated. Equates to SF 368, Block 18c.

2. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

86 Operation Number

DLMS Note:

Reserved for future use to identify the Navy Key Operation with an associated Job Order Number.

BY Repair Category Number

DLMS Note:

1. Use to identify the nonconforming materiel as Item New or Repaired/Overhauled Code.

2. Enter 'N' for new, 'R' for Repaired, 'O' for Overhauled, or ‘U’ = Unknown.

3. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

BZ Complaint Code

DLMS Note:

1. Use to identify the PQDR originators Defect Code (also known as the Defect Attribute Code or

Malfunction Code). This is the three-character code describing the defect reported by the originator.

2. This element may be populated by the Originating Point or the Screening Point. For inter-service

transactions, only the Screening Point can update this element.

C9 Previous Credit/Debit Adjustment Number

DLMS Note:

1. Use to identify the DLA Credit Memo Number. This is reference number provided to track credit.

2. If multiple document numbers are applicable, identify the credit memo number applicable to the

document number included in the Report Loop (HL01=RP) and use a separate Document Number Loop

(HL01=W) for each additional document number and credit memo number combination

3. When providing a credit memo number, also provide the credit date (DTM01=188) and credit value

(AMT01=PD) in the same loop.

4. This element may only be populated/updated by the Action Point.

1. Use to identify the DLA Credit Memo Number. This is reference number provided to track credit.

2. If multiple document numbers are applicable, identify the credit memo number applicable to the

document number included in the Report Loop (HL01=RP) and use a separate Document Number Loop

(HL01=W) for each additional document number and credit memo number combination

3. When providing a credit memo number, also provide the credit date (DTM01=188) and credit value

(AMT01=PD) in the same loop.

4. This element may only be populated/updated by the Action Point.

F8 Original Reference Number

DLMS Note:

1. Use to identify Screening Point Control Number in REF02 . Identify the system that created the

control number in REF03.

2. Field size = 14.

3. Definition: Control number assigned by the Screening Point if different from the RCN.

4. This element may only be populated/updated by the Screening Point.

H6 Quality Clause

DLMS Note:

1. Use to identify the Government Source Inspection Code. Y = Yes, N = No

2. Definition: Code used to indicate whether GSI is required.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 25 January 23, 2024

3. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

IQ End Item

DLMS Note:

1. Use to identify the End Item NSN in RE02. Equates to SF 368, Block 18a.

2. Use to identify the End Item Nomenclature in REF03.

3. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

K4 Criticality Designator

DLMS Note:

1. Used to identify the item as a Critical Safety Item (CSI) or Critical Application Item (CAI). Use

Cataloging Data and Transaction Standards, Volume 10, Multiple Applications References / Instructions

/ Tables and Grids, Table 181 to determine if the materiel is CSI/CAI. 

2. Definition: Indicates whether the item is used in a critical application (end use).

3. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

1. Used to identify the item as a Critical Safety Item (CSI) or Critical Application Item (CAI). Use

Cataloging Data and Transaction Standards, Volume 10, Multiple Applications References / Instructions

/ Tables and Grids, Table 181 to determine if the materiel is CSI/CAI. 

2. Definition: Indicates whether the item is used in a critical application (end use).

3. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

K6 Purchase Description

DLMS Note:

1. Use to identify whether the Item Under Warranty is still in effect, Warranty indicator may be Y = Yes,

N = No, and U = Unknown.

2. Definition: Indicates whether the item is or is not under warranty, if known.

3. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

KC Exhibit Distribution List

DLMS Note:

1. Cite the applicable PQDR Exhibit Distribution Status Code. This code indicates status/control of

exhibit during the transportation process. Use only codes: 

1-In transit (user still owner, but not in control) 

2-In staging, awaiting onward transportation 

3-Received by consignee

2. Refer to ADC 1007C.

1. Cite the applicable PQDR Exhibit Distribution Status Code. This code indicates status/control of

exhibit during the transportation process. Use only codes: 

1-In transit (user still owner, but not in control) 

2-In staging, awaiting onward transportation 

3-Received by consignee

2. Refer to ADC 1007C.

KK Delivery Reference

DLMS Note:

1. Cite the applicable PQDR Exhibit Delivery Requirement Code to identify the status of exhibit materiel

from the Action or Support Point of view. Cite the applicable code in REF02. 

2. Refer to ADC 1007C.

3. This element may only be populated/updated by the Action Point or Support Point.

KU Office Symbol

DLMS Note:

1. Use to identify the Action Office code.

2. This element may only be populated/updated by the Action Point

NN Nonconformance Report Number

DLMS Note:

1. Use to identify Parent/Previous Record Control Number (RCN). This is a previously reported PQDR

RCN for same type deficiency. Identify the system that created the control number in REF03.

2. Field size = 12.

3. This element may only be populated/updated by the Action Point or the Screening Point.

PM Part Number
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 26 January 23, 2024

DLMS Note:

1. Use to identify the End Item Part Number.

2. This element may be populated by the Originating Point, the Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

PO Purchase Order Number

DLMS Note:

1. Use to indicate the Purchase Order Number associated with deficient materiel.

2. Field size = 20. 

3. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

QE Replacement Customer Reference Number

DLMS Note:

1. Use in responses, as needed to identify the document number under which replacement materiel will

be

provided to the organization reporting the deficiency, or the document number provided from an ICP

that authorizes the return of deficient materiel or exhibit.

2. This element may only be populated/updated by the Action Point.

QR Quality Report Number

DLMS Note:

1. Must use to identify the PQDR Report Control Number (RCN). It is comprised of the six-position

originating activity DoDAAC, a two-digit calendar year, and a unique four-position serial number. Field

length is 12, alpha numeric only.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

SE Serial Number

DLMS Note:

1. Use to identify End Item Serial Number. Equates to SF 368, Block 18d.

2. For the serial number(s) applicable to the nonconforming materiel (SF 368 Block 11 Deficient Item

Serial Number), refer to 2/LIN20/0200 Code SE in the IUID Loop (HL01=I). For Next Higher Assembly

Serial Number (SF368, Block 17d) refer to 2/LIN20/0200 Code EM in the report loop. For Engine Serial

Number, refer to 2/LIN26/0200 Code SN in the report loop.

 3. The serial number may not exceed 30 characters in accordance with IUID policy.

1. Use to identify End Item Serial Number. Equates to SF 368, Block 18d.

2. For the serial number(s) applicable to the nonconforming materiel (SF 368 Block 11 Deficient Item

Serial Number), refer to 2/LIN20/0200 Code SE in the IUID Loop (HL01=I). For Next Higher Assembly

Serial Number (SF368, Block 17d) refer to 2/LIN20/0200 Code EM in the report loop. For Engine Serial

Number, refer to 2/LIN26/0200 Code SN in the report loop.

 3. The serial number may not exceed 30 characters in accordance with IUID policy.

TG Transportation Control Number (TCN)

DLMS Note:

1. Use to indicate the Transportation Control number.

2. Field size = 17.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point and Action Point can update this element.

TN Transaction Reference Number

DLMS Note:

1. Use to indicate the original document numbers under which the defective materiel was purchased,

requisitioned, shipped, or reworked. When the original document numbers are unavailable, a

reconstructed document number may be used.

2. If multiple document numbers are applicable, identify the first in the Report Loop (HL01=RP) and use

a separate Document Number Loop (HL01=W) for each additional document number.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

1. Use to indicate the original document numbers under which the defective materiel was purchased,

requisitioned, shipped, or reworked. When the original document numbers are unavailable, a

reconstructed document number may be used.

2. If multiple document numbers are applicable, identify the first in the Report Loop (HL01=RP) and use

a separate Document Number Loop (HL01=W) for each additional document number.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

U3 Unique Supplier Identification Number (USIN)

DLMS Note:
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 27 January 23, 2024

1. Use to identify the End Item Unique Item Identifier (UII). For the UII(s) applicable to the

nonconforming materiel uses the IUID Loop (HL01=I).

2. The approved code/name is "UII - Department of Defense Unique Item Identifier.

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

4. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

1. Use to identify the End Item Unique Item Identifier (UII). For the UII(s) applicable to the

nonconforming materiel uses the IUID Loop (HL01=I).

2. The approved code/name is "UII - Department of Defense Unique Item Identifier.

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

4. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

VW Standard

DLMS Note:

1. Use to identify the Standard Reporting Designator (SRD) Code.

2. Definition: Air Force three-character code related to the end item of the deficient materiel.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

AAN Associated Case Control Number

DLMS Note:

1. Use to identify the Support Points Investigators Control Number. This is the DCMA/Support Point

Control Number. Identify the system that created the control number in REF03.

2. Field size = 25.

3. This field may only be populated and/or updated by the Support Point.

PSM Credit Card

DLMS Note:

1. Use to indicate payment by either Government purchase card or commercial credit card. Cite Y in

REF02 when applicable.

2. This field may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

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

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 report number from systems

such as DLA- EBS, JDRS, or PDREP.

2. This element may be populated by all processing

points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can

update this element.

3. Field size = 14.

X AN 1/80 Used

REF04 C040 Reference Identifier

Description: To identify one or more reference

numbers or identification numbers as specified by

the Reference Qualifier

O Comp Used

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

M ID 2/3 Must use

Code Name

W7 Commercial and Government Entity (CAGE) Code
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 28 January 23, 2024

DLMS Note:

1. Use to identify the End Item CAGE Code associated with the End Item Part Number (REF01 Code

PM).

2. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

W8 Suffix

DLMS Note:

When citing the document number (using Code TN), or replacement shipment document number (using

Code QE) use to identify the suffix if one is provided.

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
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 29 January 23, 2024

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

CS01 367 Contract Number

Description: Contract number

DLMS Note: Used to identify the procurement

instrument identifier (PIID under which the

nonconforming materiel was. Use the legacy

procurement instrument identification number (PIIN)

pending transition to the PIID. When procurement is

authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. For

Other Transaction (OT) agreements, the type of

instrument (9th position of PIID) will be a 3 for

Research OTs or 9 for Prototype and Production

OTs. Refer to ADC 1161A or ADC 1420.

DLMS Note: Used to identify the procurement

instrument identifier (PIID under which the

nonconforming materiel was. Use the legacy

procurement instrument identification number (PIIN)

pending transition to the PIID. When procurement is

authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. For

Other Transaction (OT) agreements, the type of

instrument (9th position of PIID) will be a 3 for

Research OTs or 9 for Prototype and Production

OTs. Refer to ADC 1161A or ADC 1420.

O AN 1/30 Used

CS03 328 Release Number

Description: Number identifying a release against a

Purchase Order previously placed by the parties

involved in the transaction

O AN 1/30 Not used

CS04 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

X ID 2/3 Used

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

X AN 1/50 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Ref Id Element Name Req Type Min/Max Usage

004030F842P0PA10 30 January 23, 2024

Reference Identification Qualifier
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 31 January 23, 2024

PWK Paperwork Pos: 1020 Max: >1

Detail - Optional

Loop: HL Elements: 5

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 as needed to identify each attachment. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

Code Name

AE Attachment

DLMS Note:

Use to indicate that supporting documentation may be obtained electronically in the form of images or

files. Must provide the file name, including file type, in the description at PWK07.

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

Code Name

FT File Transfer

DLMS Note:

Use to indicate attachments are available.

PWK05 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Used

Code Name

UR Uniform Resource Locator (URL)

DLMS Note:

Use to indicate the URL for retrieval of attachment files via Web service.

PWK06 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Used

PWK07 352 Description

Description: A free-form description to clarify the

related data elements and their content

DLMS Note: Use to indicate the PQDR Attachment

File Name, including file type. 

O AN 1/80 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Ref Id Element Name Req Type Min/Max Usage

004030F842P0PA10 32 January 23, 2024
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 33 January 23, 2024

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

LM01 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

M ID 2/2 Must use

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 34 January 23, 2024

LQ Industry Code Pos: 1050 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.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

Code Name

83 Supply Condition Code

DLMS Note:

Use to identify the Supply Condition Code of the deficient materiel.

CR Federal Item Identification Guide Criticality (FIIG) Code

DLMS Note:

1. Use to identify the Federal Item Identification Guide – Criticality Code.

2. Qualifier CR is a migration code approved for use in X12 version 4050.

CW Controvert Code

DLMS Note:

1. Use to identify the PQDR Rebuttal Code. Must use in a reply rebuttal transaction (BNR01Code=RR).

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. This element may be populated and or updated by the Screening Point, the Action Point, and/or the

Support Point.

DE Signal Code

DLMS Note:

1. Use to identify the Signal Code.

2. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

DG Fund Code

DLMS Note:

1. Use to identify the Fund Code. This is the two position alpha/numeric code used to designate the

billing method (interfund or non-interfund). When interfund billing is indicated, the fund code also

indicates the fund account to be charged (disbursed) or credited (refunded).

2. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

EQ Controlled Inventory Item Code

DLMS Note:

1. Use to identify the Controlled Inventory Item Code.

2. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

FD Demilitarization Code

DLMS Note:

1. Use to identify the Demilitarization Code.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 35 January 23, 2024

2. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

GK Investigation Status Code

DLMS Note:

1. Use to identify the PQDR Investigation Status Code to indicate the current status of the PQDR.

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

JN Mission Impact Statement Code

DLMS Note:

1. Use to specify impact on current operations. Cite the applicable code in LQ02:

 1 = Inability to perform assigned mission for a classified project

 2 = Inability to perform assigned mission.

 3 = Performance of assigned mission anticipated to be curtailed or stopped if materiel is not

received within 15 days Continental United States (CONUS) or 20 days Outside Continental United

States (OCONUS)

 4 = Mission performance below prescribed level of effectiveness and efficiency

 5 = A classified NMCS condition exists due to lack of required assets

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

1. Use to specify impact on current operations. Cite the applicable code in LQ02:

 1 = Inability to perform assigned mission for a classified project

 2 = Inability to perform assigned mission.

 3 = Performance of assigned mission anticipated to be curtailed or stopped if materiel is not

received within 15 days Continental United States (CONUS) or 20 days Outside Continental United

States (OCONUS)

 4 = Mission performance below prescribed level of effectiveness and efficiency

 5 = A classified NMCS condition exists due to lack of required assets

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

ARC Action Requested Code 

DLMS Note:

SF368 Block 21: Use codes C-Credit, R-Repair, E- Replacement, or O-Other This field may only be

populated and/or updated by the Originating Point.

A data maintenance action will be submitted to X12 to establish ‘ARC – Action Requested Code' in a

future version.

BCD Broad Cause of Defect Code

DLMS Note:

Third position of the PQDR Summary Code. AKA Broad Cause Code.

1. Definition: PQDR Joint Regulation code describing the cause of deficiency. See PQDR Joint

Regulation for appropriate codes. This field may be populated/updated by the Support Point or the

Action Point. The Screening Point may use the code if it is not their intention to forward the PQDR to an

Action Point. Once the PQDR is forwarded to the Action Point, the Screening Point will not be able to

populate/update Summary Code fields and will communicate with the Action Point through the rebuttal

process for any updates/changes.

2. A data maintenance action will be submitted to X12 to establish ‘BCD – Broad Cause of Defect

Code' in a future version.

Third position of the PQDR Summary Code. AKA Broad Cause Code.

1. Definition: PQDR Joint Regulation code describing the cause of deficiency. See PQDR Joint

Regulation for appropriate codes. This field may be populated/updated by the Support Point or the

Action Point. The Screening Point may use the code if it is not their intention to forward the PQDR to an

Action Point. Once the PQDR is forwarded to the Action Point, the Screening Point will not be able to

populate/update Summary Code fields and will communicate with the Action Point through the rebuttal

process for any updates/changes.

2. A data maintenance action will be submitted to X12 to establish ‘BCD – Broad Cause of Defect

Code' in a future version.

CAT Corrective Action Taken Code

DLMS Note:

Eighth Positions of the PQDR Summary Code. AKA Corrective Action Taken Code.

1. Definition: Corrective action code taken as a result of the investigation. DLAR 4155.24 or Reference

(g)for appropriate codes.

2. This field may be populated/updated by the Support Point or the Action Point. The Screening Point

may use the code if it is not their intention to forward the PQDR to an Action Point. Once the PQDR is

forwarded to the Action Point, the Screening Point will not be able to populate/update Summary Code

fields and will communicate with the Action Point through the rebuttal process for any updates/changes.

3. A data maintenance action will be submitted to X12 to establish ‘CAT – Corrective Action Taken

Code' in a future version.

Eighth Positions of the PQDR Summary Code. AKA Corrective Action Taken Code.

1. Definition: Corrective action code taken as a result of the investigation. DLAR 4155.24 or Reference

(g)for appropriate codes.

2. This field may be populated/updated by the Support Point or the Action Point. The Screening Point

may use the code if it is not their intention to forward the PQDR to an Action Point. Once the PQDR is

forwarded to the Action Point, the Screening Point will not be able to populate/update Summary Code

fields and will communicate with the Action Point through the rebuttal process for any updates/changes.

3. A data maintenance action will be submitted to X12 to establish ‘CAT – Corrective Action Taken

Code' in a future version.

CDC Current Disposition Code

DLMS Note:

1. SF368 Block 19: Use codes H-Holding Exhibit, D-Disposed of/Destroyed, R-Repaired, or O-Other.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 36 January 23, 2024

2. This field may only be populated and/or updated by the Originating Point.

3. A data maintenance action will be submitted to X12 to establish ‘CDC – Current Disposition Code' in

a future version.

COG Cognizance Symbol

DLMS Note:

Use to identify the materiel cognizance symbol (COG). Indicate NSL for non-stock numbered listed

items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to

perpetuate without action.

DRC Deficiency Responsibility Code 

DLMS Note:

First Position of PQDR Summary Code. AKA Defect Responsibility Code. Indicates the

responsible/liable party for the deficiency. See PQDR Joint Regulation for appropriate codes. This field

may be populated/updated by the Support Point or the Action Point. The Screening Point may use the

code if it is not their intention to forward the PQDR to an Action Point. Once the PQDR is forwarded to

the Action Point, the Screening Point will not be able to populate/update Summary Code fields and will

communicate with the Action Point through the rebuttal process for any updates/changes.

A data maintenance action will be submitted to X12 to establish ‘DRC – Deficiency Responsibility Code'

in a future version.

First Position of PQDR Summary Code. AKA Defect Responsibility Code. Indicates the

responsible/liable party for the deficiency. See PQDR Joint Regulation for appropriate codes. This field

may be populated/updated by the Support Point or the Action Point. The Screening Point may use the

code if it is not their intention to forward the PQDR to an Action Point. Once the PQDR is forwarded to

the Action Point, the Screening Point will not be able to populate/update Summary Code fields and will

communicate with the Action Point through the rebuttal process for any updates/changes.

A data maintenance action will be submitted to X12 to establish ‘DRC – Deficiency Responsibility Code'

in a future version.

DVC Defect Verified Code 

DLMS Note:

1. Definition: Code used to indicate whether the defect actually existed as described. Use codes

N-Defect not verified, O-Other Than reported, U-Unable to Test, Y-Defect Verified. This field may be

populated/updated by the Screening Point, Action Point, or the Support Point.

2. A data maintenance action will be submitted to X12 to establish ‘DVC – Defect Verified Code' in a

future version

FEC Final Exhibit Disposition Code 

DLMS Note:

Ninth Positions of the PQDR Summary Code. AKA Final Exhibit Disposition Code.

1. Definition: Code representing the current disposition of the exhibit. See DLAR 4155.24 or Reference

(g)for appropriate codes.

2. This field may be populated/updated by the Support Point or the Action Point. The Screening Point

may use the code if it is not their intention to forward the PQDR to an Action Point. Once the PQDR is

forwarded to the Action Point, the Screening Point will not be able to populate/update Summary Code

fields and will communicate with the Action Point through the rebuttal process for any updates/changes.

3. A data maintenance action will be submitted to X12 to establish ‘FEC – Final Exhibit Disposition

Code' in a future version.

Ninth Positions of the PQDR Summary Code. AKA Final Exhibit Disposition Code.

1. Definition: Code representing the current disposition of the exhibit. See DLAR 4155.24 or Reference

(g)for appropriate codes.

2. This field may be populated/updated by the Support Point or the Action Point. The Screening Point

may use the code if it is not their intention to forward the PQDR to an Action Point. Once the PQDR is

forwarded to the Action Point, the Screening Point will not be able to populate/update Summary Code

fields and will communicate with the Action Point through the rebuttal process for any updates/changes.

3. A data maintenance action will be submitted to X12 to establish ‘FEC – Final Exhibit Disposition

Code' in a future version.

GCP Product QualityDeficiency Report General Correspondence Purpose Code

DLMS Note:

1. Use to identify the Product Quality Deficiency Report General Correspondence Purpose Code

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘GCP – Product Quality Deficiency

Report General Correspondence Purpose Code' in a future version.

IRC Product Quality Deficiency Report Interim Reply Codes

DLMS Note:

1. Use to identify the Product Quality Deficiency Report Interim Reply Code

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘IRC – Product Quality Deficiency

Report Interim Reply Codes' in a future version.

MAC Material Management Aggregation Code

DLMS Note:

1. Use to identify the Material Management Aggregation Code (MMAC) for NSNs managed by a specific
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 37 January 23, 2024

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.

2. Qualifier MAC is a migration code approved for use in X12 version 5010.

P1C PQDR Cost Code 

DLMS Note:

1. Definition AKA DLA Cost Code. Use Codes C-Cost to Gov’t (Commercial Supplier), G-Cost to

Navy(Government Manufacturer/Supplier), N-No Cost to Gov’t (Commercial Supplier), U-undetermined,

Z-No Cost to Navy (Government Manufacturer /Supplier)

2. This field may only be populated by the Screening Point or Action Point.

3. A data maintenance action will be submitted to X12 to establish ‘P1C – PQDR Cost Code' in a future

version.

1. Definition AKA DLA Cost Code. Use Codes C-Cost to Gov’t (Commercial Supplier), G-Cost to

Navy(Government Manufacturer/Supplier), N-No Cost to Gov’t (Commercial Supplier), U-undetermined,

Z-No Cost to Navy (Government Manufacturer /Supplier)

2. This field may only be populated by the Screening Point or Action Point.

3. A data maintenance action will be submitted to X12 to establish ‘P1C – PQDR Cost Code' in a future

version.

P2C PQDR Credit Code

DLMS Note:

1. Definition: A single character alpha code used to describe whether credit or other form of resolution

is authorized. Use only codes: F-Repaired by user, P-Vendor Replacement, R-Vendor Repair, S-Source

of Supply Replacement, T-Source of Supply Repair, W-Credit Authorized, X-No Credit Authorized. This

field may be populated/updated by the Screening Point, Action Point, or the Support Point.

2. A data maintenance action will be submitted to X12 to establish ‘P2C – PQDR Credit Code' in a

future version.

1. Definition: A single character alpha code used to describe whether credit or other form of resolution

is authorized. Use only codes: F-Repaired by user, P-Vendor Replacement, R-Vendor Repair, S-Source

of Supply Replacement, T-Source of Supply Repair, W-Credit Authorized, X-No Credit Authorized. This

field may be populated/updated by the Screening Point, Action Point, or the Support Point.

2. A data maintenance action will be submitted to X12 to establish ‘P2C – PQDR Credit Code' in a

future version.

PAT Preventative Action Taken Code 

DLMS Note:

1. Seventh Positions of the PQDR Summary Code. AKA Preventative Action Taken Code.

2. Definition: Code used to indicate the preventive action taken to prevent recurrence. DLAR 4155.24 or

Reference (g) for appropriate codes. This field may be populated/updated by the Support Point or the

Action Point. The Screening Point may use the code if it is not their intention to forward the PQDR to an

Action Point. Once the PQDR is forwarded to the Action Point, the Screening Point will not be able to

populate/update Summary Code fields and will communicate with the Action Point through the rebuttal

process for any updates/changes

3. A data maintenance action will be submitted to X12 to establish ‘PAT – Preventative Action Taken

Code' in a future version.

1. Seventh Positions of the PQDR Summary Code. AKA Preventative Action Taken Code.

2. Definition: Code used to indicate the preventive action taken to prevent recurrence. DLAR 4155.24 or

Reference (g) for appropriate codes. This field may be populated/updated by the Support Point or the

Action Point. The Screening Point may use the code if it is not their intention to forward the PQDR to an

Action Point. Once the PQDR is forwarded to the Action Point, the Screening Point will not be able to

populate/update Summary Code fields and will communicate with the Action Point through the rebuttal

process for any updates/changes

3. A data maintenance action will be submitted to X12 to establish ‘PAT – Preventative Action Taken

Code' in a future version.

PCC Product Quality Deficiency Report Cancellation Code

DLMS Note:

1. Use to identify the Product Quality Deficiency Report Cancellation Code.

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘PCC - Product Quality Deficiency

Report Cancellation Code” in a future version.

PCD Detailed Cause Code

DLMS Note:

1. Fourth- Sixth Positions of the PQDR Summary Code. AKA Detailed Cause Code.

2. Definition: Refer to DLAR 4155.24 or Refer to Reference (g) detailed cause of deficiency.

3. A data maintenance action will be submitted to X12 to establish ‘PCD – Detailed Cause Code' in a

future version.

PDD Product Quality Deficiency Report Discovery Code

DLMS Note:

1. Use to identify the Product Quality Deficiency Report Discovery Code.

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘PDD - Product Quality Deficiency

Report Discovery Code’ in a future version.

PQC Product Quality Deficiency Report Retract Reason Code
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 38 January 23, 2024

DLMS Note:

1. Use to identify the Product Quality Deficiency Report Retract Reason Code.

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘PQC – Product Quality Deficiency

Report Retract Reason Code' in a future version.

PQR Product Quality Deficiency Exhibit Delivery Requirement Code

DLMS Note:

1. Use to identify the Product Quality Deficiency Exhibit Delivery Requirement Code to indicate the

current status of the PQDR.

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘PQR – Product Quality Deficiency

Exhibit Delivery Requirement Code' in a future version.

PQS Product Quality Deficiency Report Status Code

DLMS Note:

1. Use to identify the PQDR Deficiency Status Code to indicate the current status of the PQDR.

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘PQS – Product Quality Deficiency

Report Status Code' in a future version.

RAC Reject Advice Code

DLMS Note:

1. Use to identify the PQDR Reject Advice Code.

2. Use only valid codes as prescribed under the DLMS; see introductory DLMS Notes 3 and 4.

3. A data maintenance action will be submitted to X12 to establish ‘RAC – PQDR Reject Advice Code'

in a future version.

SDC Severity of Defect Code

DLMS Note:

1. Second position of PQDR Summary Code. Definition: Level of Severity of the defect. See PQDR

Joint Regulation for appropriate codes. This field may be populated/updated by the Support Point or the

Action Point. The Screening Point may use the code if it is not their intention to forward the PQDR to an

Action Point. Once the PQDR is forwarded to the Action Point, the Screening Point will not be able to

populate/update Summary Code fields and will communicate with the Action Point through the rebuttal

process for any updates/changes..

2. A data maintenance action will be submitted to X12 to establish ‘SDC – Severity of Defect Code' in a

future version.

1. Second position of PQDR Summary Code. Definition: Level of Severity of the defect. See PQDR

Joint Regulation for appropriate codes. This field may be populated/updated by the Support Point or the

Action Point. The Screening Point may use the code if it is not their intention to forward the PQDR to an

Action Point. Once the PQDR is forwarded to the Action Point, the Screening Point will not be able to

populate/update Summary Code fields and will communicate with the Action Point through the rebuttal

process for any updates/changes..

2. A data maintenance action will be submitted to X12 to establish ‘SDC – Severity of Defect Code' in a

future version.

SMI Special Material Identification Code

DLMS Note:

Use to identify the Special Material Identification Code (SMIC) for an end item. This is a Navy-unique

data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

LQ02 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Must use
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 39 January 23, 2024

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. Begin a new NCD loop for each IUID loop. The UII value and some of the associated data elements are future DLMS enhancements and

require coordination prior to use.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

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: Use as a counter to satisfy ANSI

syntax. Cite numeric '1' EXCEPT where additional

NCD loops when providing unique identification of

discrepant items. In these instances, Increase

incrementally by 1 for each uniquely identified item.

DLMS Note: Use as a counter to satisfy ANSI

syntax. Cite numeric '1' EXCEPT where additional

NCD loops when providing unique identification of

discrepant items. In these instances, Increase

incrementally by 1 for each uniquely identified item.

O AN 1/20 Must use
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 40 January 23, 2024

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:

For each qualifier in NTE01, repeat the NTE segment as needed, with up to 80 characters in each iteration, until the maximum length

specified for each data element (e.g., PQDR element length for Quality information (qualifier TRS) = 2000 characters in the NTE02) is

conveyed.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

Code Name

ACT Action

DLMS Note:

1. Use to identify Action Requested narrative (also known as Originator Recommendation). This is the

recommended action requested by the Originator or Screening Point.

2. Field size = 1000.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

ADD Additional Information

DLMS Note:

1. Use to identify Additional Information narrative for PQDR. Also, used when a PQDR Final reply is

rebutted.

2. Field Size = 4000.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

COD Corrected Data

DLMS Note:

Use to identify the narrative comments associated with a PQDR follow-up. Status comment used to

pass General Correspondence between system users. When data is corrected comments should

explain what fields are affected.

DEL Delivery

DLMS Note:

1. Use to identify the Exhibit Required/Requested/Hold status from the Originator. This provides

verification that the exhibit is required and should be sent or held by originator.

2. PQDRII field size = 10.

FDD Final Deficiency Description

DLMS Note:

1. This will be the final closing comments from the Screening Point that includes their summary of the

investigation. This is a narrative field of no more than 2000 characters and provides the Screening

Point an opportunity to provide comments without changing the Action Point closing letter. 
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 41 January 23, 2024

2. This field may only be populated or updated by the Screening Point.

ODD Originator Deficiency Description

DLMS Note:

1. Use to identify the originator’s Description of Deficiency (also known as Narrative Details). This is the

originator’s description of the deficiency and any requested actions. Equates to SF368, Block 3.

2. Field size = 4000.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

POL Property Owner Location Information

DLMS Note:

1. Use to identify the originators Location of Exhibit narrative. This is detailed information about where

materiel is currently located.

2. Field size = 100.

3. This element may only be populated or updated by the Originating Point or the Screening Point.

Local code SPS is established for use in the DLMS IC 842P version 4030. A data maintenance action

will be submitted to X12 to establish ‘SPS- Screening Point Summary' in a future version. 

1. Use to identify the originators Location of Exhibit narrative. This is detailed information about where

materiel is currently located.

2. Field size = 100.

3. This element may only be populated or updated by the Originating Point or the Screening Point.

Local code SPS is established for use in the DLMS IC 842P version 4030. A data maintenance action

will be submitted to X12 to establish ‘SPS- Screening Point Summary' in a future version. 

SPS Screening Point Summary

DLMS Note:

This element may only be populated/updated by the Screening Point.

Local code SPS is established for use in the DLMS IC 842P version 4030. A data maintenance action

will be submitted to X12 to establish ‘SPS- Screening Point Summary' in a future version. 

NTE02 352 Description

Description: A free-form description to clarify the

related data elements and their content

DLMS Note: 1. Differences in system field sizes

may exist. Coordinate with receiving systems to

ensure they have the capability accept the quantity

of data sent.

2. Use multiple repetitions of NTE, with up to 80

positions for each line, until reaching the maximum

length available.

3. Special characters are not allowed except as

specified. Valid characters are: @ # $ ( ) - = + , / & ;

: and .

M AN 1/80 Must use
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 42 January 23, 2024

REF Reference Identification Pos: 2600 Max: >1

Detail - Optional

Loop: NCD Elements: 2

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 the IUID Loop (HL01=I) to provide IUID information. Repeat the REF segment within each IUID loop to identify relevant IUID

information.

2. This transaction will support item identification based upon the UII and/or the serial number. Data elements associated with the UII may

be identified separately. Use the appropriate data elements to satisfy the desired functionality.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: 1. The following codes are authorized.

2. Use codes separately or in combination, to

identify appropriate information for serialized items. 

3. In support of Financial Improvement and Audit

Readiness (FIAR) compliance, capital equipment

candidates require serialization data visibility. 

Submitters must prepare PQDRs citing the

applicable serial number(s) as mandatory, and when

available, include UIIs.

3. In support of Financial Improvement and Audit

Readiness (FIAR) compliance, capital equipment

candidates require serialization data visibility. 

Submitters must prepare PQDRs citing the

applicable serial number(s) as mandatory, and when

available, include UIIs.

4. Under IUID policy, unique item tracking (UIT)

program items require serialization data visibility. 

Submitters must prepare PQDRs citing the

applicable serial number(s) as mandatory, and when

available, include UIIs.

M ID 2/3 Must use

Code Name

BT Batch Number

DLMS Note:

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

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

SE Serial Number

DLMS Note:

1. Use in IUID loop to identify the serial number. Equates to SF 368 Block 11 Deficient Item Serial

Number.

2. For Next Higher Assembly Serial Number (SF368, Block 17d) refer to 2/LIN20/0200 Code EM in the

report loop. For Engine Serial Number, refer to 2/LIN26/0200 Code SN in the report loop. For serial

number of the End Item (SF 368, Block 18d), refer to 2/REF01/0700 Code SE in the report loop.

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

dashes and forward slashes. Spaces are not allowed.

1. Use in IUID loop to identify the serial number. Equates to SF 368 Block 11 Deficient Item Serial

Number.

2. For Next Higher Assembly Serial Number (SF368, Block 17d) refer to 2/LIN20/0200 Code EM in the

report loop. For Engine Serial Number, refer to 2/LIN26/0200 Code SN in the report loop. For serial

number of the End Item (SF 368, Block 18d), refer to 2/REF01/0700 Code SE in the report loop.

3. 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:
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 43 January 23, 2024

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

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

Department of Defense Unique Item Identifier.

3. The UII may not exceed 50 characters in accordance with IUID policy.

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 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 44 January 23, 2024

QTY Quantity Pos: 2700 Max: >1

Detail - Optional

Loop: NCD Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

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

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

Semantics: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

QTY01 673 Quantity Qualifier

Description: Code specifying the type of quantity

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

Code Name

01 Discrete Quantity

DLMS Note:

1. Use to identify the quantity of Time Since Installation. This is the time elapsed between installation

and materiel failure.

2. Field size = 7.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

02 Cumulative Quantity

DLMS Note:

1. Use to identify the quantity of Time Since New/Overhaul. This is the time elapsed since the last

repair, or initial use for new items, and materiel failure.

2. Field size = 7.

3. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

17 Quantity on Hand

DLMS Note:

1. Use to identify the Quantity in Stock of the Nonconforming Materiel. This is the quantity of items

currently held in stock. Equates to SF368, Block 10d.

2. Field size = 15.

38 Original Quantity

DLMS Note:

1. Use in to indicate the Quantity of Prior Deficiencies. This is the quantity of similar failures reported

on previous PQDRs.

2. Field size = 5.

3. This field may only be populated or updated by the Originating Point, Screening Point or Action Point.

39 Shipped Quantity

DLMS Note:

1. Use to identify the Quantity of Exhibits Shipped.

2. Field size = 7.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 45 January 23, 2024

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

86 Nonconformance Quantity

DLMS Note:

1. Used to identify the Quantity Deficient of the nonconforming materiel received. This is the quantity of

deficient items as reported by the originator. This equates to SF368, Block 10c.

2. Field size = 9.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point can update this element.

87 Quantity Received

DLMS Note:

1. Used to identify the Quantity Received of the nonconforming materiel received. Equates to SF368,

Block 10a.

2. Field size = 9.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

AO Verified Receipts

DLMS Note:

1. Use to identify the quantity of Exhibits Received by the Action or Support Point.

2. Field size = 7.

3. This element may only be populated or updated by the Action Point or the Support Point.

OT Number of Operating Periods at Failure

DLMS Note:

1. Use to identify the Operating Time at Failure (OTAF). This is a measurement of time prior to failure.

It describes how long a part was operated before failure. Equates to SF368, Block 7.

2. Field size = 15.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

T8 Time Since New/Overhaul

DLMS Note:

1. Use to identify the Time Since New/Overhaul.

It describes how long a part has been operating since it was overhauled. Equates to SF368, Block 7.

2. Field size = 15.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

4. A data maintenance action will be submitted to X12 to establish ‘T8 – Time Since New/Overhaul' in a

future version.

1. Use to identify the Time Since New/Overhaul.

It describes how long a part has been operating since it was overhauled. Equates to SF368, Block 7.

2. Field size = 15.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

4. A data maintenance action will be submitted to X12 to establish ‘T8 – Time Since New/Overhaul' in a

future version.

T9 Time Since Installation

DLMS Note:

1. Use to identify the Time Since Installation. It describes how long a part has been operational since

installation. Equates to SF368, Block 7.

2. Field size = 15.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

4. A data maintenance action will be submitted to X12 to establish ‘T9 – Time Since Installation' in a

future version.

1. Use to identify the Time Since Installation. It describes how long a part has been operational since

installation. Equates to SF368, Block 7.

2. Field size = 15.

3. This element may only be populated by the Originating Point, Screening Point or Action Point. For

inter-service transactions, only the Screening Point and Action Point can update this element.

4. A data maintenance action will be submitted to X12 to establish ‘T9 – Time Since Installation' in a

future version.

UA Units Completed
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 46 January 23, 2024

DLMS Note:

1. Use to identify the Quantity Inspected by the originator. Equates to SF368, Block 10b.

2. Field size = 9.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point and can update this element.

V3 Transfer Quantity

DLMS Note:

1. Use to identify the quantity of Exhibits Requested by Action or Support Point.

2. Field size = 7.

3. This element may only be used/updated by the Action Point or the Support Point.

QTY02 380 Quantity

Description: Numeric value of quantity

X R 1/15 Must use

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, except

as listed below for Operating Time at Failure, Time

Since New/Overhaul, and Time Since Installation.

3. Definition: Type of standard unit the materiel was

packaged in. Also used for measure of time or

events as listed below for Operating Time 

at Failure, Time Since New/Overhaul, and Time

Since Installation.

4. This element may be populated by all processing

points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can

update this element.

O Comp Used

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: 1. For QTY01 code 01, 02, or OT use

one of the following Operating Time Codes.

2. Refer to ADC 1007C.

M ID 2/2 Must use

Code Name

03 Seconds

14 Shot

DLMS Note:

Use to indicate number of “Catapult Shots;” this is the number of launches an aircraft has been

launched, i.e. aircraft catapult systems and/or unmanned air vehicles.

1N Count

DLMS Note:

Use to indicate number of “Starts”.

7A Landings

DLMS Note:

1. Used to document the amount of landings an aircraft has completed. 
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 47 January 23, 2024

2. Migration code 7A is established for use in the 842P, version 4030. A data maintenance action was

approved in version 7020. The approved code/name is 7A - Landings.

7C Flight Hours

DLMS Note:

1. Used to document the amount of time in hours that an aircraft/equipment has been flying. 

2. Migration code 7C is established for use in the 842P, version 4030. A data maintenance action was

approved in version 7020. The approved code/name is 7C – Flight Hours.

B7 Cycles

DLMS Note:

Use to indicate cycles of equipment, e.g., engine start-up and stop, or take-off and landings.

DA Days

DH Miles

FT Foot

HR Hours

IS Stops

DLMS Note:

Use to indicate number of “Arrestments;” this is the number of times an aircraft has engaged arresting

gear to stop forward momentum of a routine or emergency landing or an aborted takeoff.

MJ Minutes

MO Months

RH Running or Operating Hours

DLMS Note:

Use to indicate “Under/Steaming Hours”.

RO Round

DLMS Note:

Use to indicate “Rounds Fired”.

UN Unit

DLMS Note:

Use to indicate unit if measure is “Other” (i.e., than those listed here).

YR Years
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 48 January 23, 2024

AMT Monetary Amount Pos: 2730 Max: >1

Detail - Optional

Loop: NCD Elements: 2

User Option (Usage): Used

Purpose: To indicate the total monetary amount

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

AMT01 522 Amount Qualifier Code

Description: Code to qualify amount

DLMS Note: The following codes are authorized.

M ID 1/3 Must use

Code Name

10 Shipment Value in U.S. Dollars

DLMS Note:

1. Use to indicate “total” value of defective items in Defective Unit Cost. This is the cost of the deficient

materiel based on the unit of issue.

2. Field size = 15.

3. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

2H Operating Expenses

DLMS Note:

1. Use to indicate the amount of recovered or reconsideration received by processing the PQDR (also

known as Recovery Value).

2. Field size = 15.

3. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

PD Credit

DLMS Note:

1. Use to indicate the amount of credit/debit being authorized or recommended (also known as DLA

Credit Value).

2. Use in the Document Number Loop (HL01=W).

3. If multiple document numbers are applicable, identify the credit amount applicable to the document

number included in the Report Loop (HL01=RP) and use a separate Document Number Loop

(HL01=W) for each additional document number and credit amount combination.

4. When providing a credit amount, also provide the credit date (DTM01=188) (and the DLA Credit

Memo Number, when applicable) in the same loop.

5. This element may only be populated/updated by the Screening Point or Action Point.

1. Use to indicate the amount of credit/debit being authorized or recommended (also known as DLA

Credit Value).

2. Use in the Document Number Loop (HL01=W).

3. If multiple document numbers are applicable, identify the credit amount applicable to the document

number included in the Report Loop (HL01=RP) and use a separate Document Number Loop

(HL01=W) for each additional document number and credit amount combination.

4. When providing a credit amount, also provide the credit date (DTM01=188) (and the DLA Credit

Memo Number, when applicable) in the same loop.

5. This element may only be populated/updated by the Screening Point or Action Point.

RP Repair

DLMS Note:

1. Use to identify “unit” value of a “single” defective item in Defective Unit Cost. This is the cost of the

deficient materiel based on the unit of issue.

2. Field size = 15.

3. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point and can update this element

Z3 Unit Cost of Discrepant Material

DLMS Note:

1. Use to identify “unit” value of a “single” defective item in Defective Unit Cost. This is the cost of the

deficient materiel based on the unit of issue.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 49 January 23, 2024

2. Field size = 15.

3. This element may only be populated by the Originating Point, Screening Point, or Action Point. For

inter-service transactions, only the Screening Point or Action Point can update this element.

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
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 50 January 23, 2024

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. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other 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:

Use to identify other agencies involved with the processing of the PQDR. Also, use in IUID loop to identify the Enterprise Identifier.

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: The following codes are authorized.

M ID 2/3 Must use

Code Name

41 Submitter

DLMS Note:

1. Use to identify the Originator DoDAAC when different than the address identified with the

DoDAAC-From in 1/N101/1200.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point and can update this element.

91 Action Party

DLMS Note:

1. Use to identify the Action Point DoDAAC when different than the address identified with the

DoDAAC-From in 1/N101/1200.

2. This element may only be populated/updated by the Screening Point or the Action Point.

92 Support Party

DLMS Note:

1. Use to identify the Support Point DoDAAC when different than the address identified with the

DoDAAC-From in 1/N101/1200.

2. This element may only be populated/updated by the Action Point, and the Support Point.

C4 Contract Administration Office

DLMS Note:

1. Use to identify DLA Form 1227, DCMA Review Release Authority or Preparer by DoDAAC.

2. This element may only be populated/updated by the Support Point.

CA Carrier

DLMS Note:

1. Use to identify the PQDR exhibit carrier by Standard Carrier Alpha Code (SCAC). Used by the

shipping activity to identify the carrier transporting the exhibit.

2. If the SCAC is not available, cite “Hand” (Hand Carry) or “DTS” (Defense Transportation Service), as

applicable.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 51 January 23, 2024

 3. Refer to United States Transportation Command (USTRANSCOM) Reference Data Management

(TRDM) for valid codes.

4. Refer to ADC 1007C.

LG Location of Goods

DLMS Note:

Use to identify Exhibit Holding DoDAAC/CAGE of the organization that is holding the exhibit. Aka

Exhibit Location.

MF Manufacturer of Goods

DLMS Note:

1. Use to identify the Supplier/Manufacturer CAGE, DUNS or DUNSS Plus 4.

2. PQDRII Definition: Manufacturers/Suppliers Commercial and Government Entity (CAGE), Dunn and

Bradstreet Number (DUNS) and/or DUNS Plus Four number.

PG Prime Contractor

DLMS Note:

1. Use to identify the Prime Contractors Code (CAGE) for the supplier of the nonconforming materiel.

2. Contractor and Government Entity (CAGE) Code of the Supplier.

RN Repair or Refurbish Location

DLMS Note:

Use to identify the Last Repair Facility, aka Last Rework Facility, when different than the address

identified with the DODAAC-From in 1/N101/1200.

SH Shipper

DLMS Note:

1. Use to identify Shipper of the nonconforming materiel. Shipper Code must be CAGE or DoDAAC.

2. PQDRII Definition: DoDAAC or CAGE of the Shipping activity who delivered the defective materiel.

ST Ship To

DLMS Note:

Use to identify the Exhibit Shipped To Address. This is the address to which the exhibit was shipped.

Z7 Mark-for Party

DLMS Note:

Use to identify the Mark For party to receive an exhibit.

ZB Party to Receive Credit

DLMS Note:

1. Use to identify the DoDAAC for the activity to receive credit if not the PQDR originator’s organization.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point and can update this element.

ZD Party to Receive Reports

DLMS Note:

Use to identify additional party(ies) to receive a copy of the PQDR via electronic retransmission of the

842P.

ZQ Screening Point

DLMS Note:

1. Use to identify the Screening Point DoDAAC when different than the address identified with the

DoDAAC-from N101.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point and can update this element.

DIR Distribution Recipient

DLMS Note:

Use to identify the recipient of the distribution copy forwarded by email or other non-transaction method.

IAT Party Executing and Verifying
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 52 January 23, 2024

DLMS Note:

1. Use to indicate the Enterprise Identifier (EID) responsible for the UII.

2. The value of the IUID Issuing Agency Code (IAC) may be derived from the qualifier used for the

Enterprise Identifier. Use only N103 qualifiers for which a corresponding IAC is noted.

SUS Supply Source

DLMS Note:

Use to identify the Source of Supply by Routing Identifier Code (RIC).

N102 93 Name

Description: Free-form name

DLMS Note: 1. Use to identify the name of the code

listed above (e.g., Portsmouth Naval Shipyard). 

2. This element may only be populated by the

Originating Point or Screening Point. For

inter-service transactions, only the Screening Point

and can update this element.

X AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Used

Code Name

2 Standard Carrier Alpha Code (SCAC)

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

A2 Military Assistance Program Address Code (MAPAC)

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or other code

DLMS Note: Use to identify the name of the code

listed above. i.e. DoDAAC = N39040

X AN 2/80 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 53 January 23, 2024

N2 Additional Name Information Pos: 2900 Max: 2

Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): Used

Purpose: To specify additional names

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N201 93 Name

Description: Free-form name

DLMS Note: 1. This equates to address line.

2. Used when customer input for the reporting

activity information is not available or differs from

data extracted from the DoDAAC.

3. This element may only be populated by the

Originating Point or Screening Point. For

inter-service transactions, only the Screening Point

and can update this element.

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

DLMS Note: 1. This equates to address line two.

2. Used when customer input for the reporting

activity information is not available or differs from

data extracted from the DoDAAC.

3. This element may only be populated by the

Originating Point or Screening Point. For

inter-service transactions, only the Screening Point

and can update this element.

O AN 1/60 Must use
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 54 January 23, 2024

N3 Address Information Pos: 3000 Max: 2

Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): Used

Purpose: To specify the location of the named party

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N301 166 Address Information

Description: Address information

DLMS Note: This equates to street address. Used

when customer input for the reporting activity

information is not available or differs from data

extracted from the DODAAC.

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

DLMS Note: This equates to street address. Used

when customer input for the reporting activity

information is not available or differs from data

extracted from the DODAAC.

O AN 1/55 Must use
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 55 January 23, 2024

N4 Geographic Location Pos: 3100 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

Purpose: To specify the geographic place of the named party

Syntax Rules: 

1. E0207 - Only one of N402 or N407 may be present.

2. C0605 - If N406 is present, then N405 is required.

3. C0704 - If N407 is present, then N404 is required.

Comments: 

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2. N402 is required only if city name (N401) is in the U.S. or Canada.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (Standard State/Province) as

defined by appropriate government agency

X ID 2/2 Used

N403 116 Postal Code

Description: Code defining international postal

zone code excluding punctuation and blanks (zip

code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the country

X ID 2/3 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 56 January 23, 2024

PER Administrative Communications

Contact

Pos: 3300 Max: >1

Detail - 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 to identify the report preparer when the customer DoDAAC is identified in this loop (rather than in the transaction header). Only one

POC may be identified as the report preparer.

2. Use a second repetition if needed to identify additional communication numbers. When used, must provide email address and at least

one phone number.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

Code Name

AU Report Authorizer

DLMS Note:

1. Use to identify the review official's information associated with DLA Form 1227 (also known as

Review Release Authority). This is the official that reviewed the 1227 previous to release.

2. This element may only be populated or updated by the Support Point or Action Point (if no Support

Point).

PU Report Preparer

DLMS Note:

1. Use to identify the preparing official's information associated with the DLA Form 1227. AKA Prepared

By.

2. This element may only be populated or updated by the Support Point or Action Point (if no Support

Point).

RP Responsible Person

DLMS Note:

1. Use to indicate a POC at receiving location. Also, use in PQDR exhibit shipments to indicate the

Government representative at the receiving location.

2. This element may only be populated by the Originating Point or Screening Point. For inter-service

transactions, only the Screening Point and can update this element.

PER02 93 Name

Description: Free-form name

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used

Code Name

AU Defense Switched Network

DLMS Note:
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 57 January 23, 2024

1. Use to identify the DSN Phone Number.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

EM Electronic Mail

DLMS Note:

1. Use to identify the E-mail address.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

TE Telephone

DLMS Note:

1. Use to identify the Commercial Phone Number.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

PER04 364 Communication Number

Description: Complete communications number

including country or area code when applicable

X AN 1/256 Used

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

Code Name

AU Defense Switched Network

DLMS Note:

1. Use to identify the DSN Phone Number.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

EM Electronic Mail

DLMS Note:

1. Use to identify the E-mail address.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

TE Telephone

DLMS Note:

1. Use to identify the Commercial Phone Number.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

PER06 364 Communication Number

Description: Complete communications number

including country or area code when applicable

X AN 1/256 Used

PER07 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used

Code Name

AU Defense Switched Network

DLMS Note:
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 58 January 23, 2024

1. Use to identify the DSN Phone Number.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

EM Electronic Mail

DLMS Note:

1. Use to identify the E-mail address.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

TE Telephone

DLMS Note:

1. Use to identify the Commercial Phone Number.

2. This element may be populated by all processing points. For inter-service transactions, only the

Screening Point, Action Point and Support Point can update this element.

PER08 364 Communication Number

Description: Complete communications number

including country or area code when applicable

X AN 1/256 Used

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. May

also reflect position title of the point of contact.

2. This element may be populated or updated by all

processing points.

O AN 1/20 Used
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 59 January 23, 2024

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. R0203 - At least one of NCA02 or NCA03 is required.

2. P0405 - If either NCA04 or NCA05 is present, then the other 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:

Used to describe actions taken in response to the original PQDR report.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

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

RS Response Requirements Follow

DLMS Note:

Use to satisfy ANSI syntax requirements.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 60 January 23, 2024

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.

DLMS Note:

For each qualifier in NTE01, repeat the NTE segment as needed, with up to 80 characters in each iteration, until the maximum length

specified for each data element (e.g., PQDR element length for Quality information (qualifier TRS) = 2000 characters in the NTE02) is

conveyed.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

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

Code Name

ACI Additional Claim Information

DLMS Note:

1. Used to identify Supplemental Data to provide additional information pertinent to the PQDR

investigation.

2. Field size = 4000.

3. This element may be populated/updated by the Action Point or the Support Point.

ACN Action Taken

DLMS Note:

1. Use to Identify the Final Reply Results narrative describing the final results of the investigation.

2. Field size = 2000.

3. This element may be populated/updated by the Action Point or the Support Point.

AES Actual Evaluation Summary

DLMS Note:

1. Use to identify Evaluation of Current Production. This is the DCMA representative’s assessment of

the effect on current production. Equates to DLA Form 1227, Block 15.

2. Field size = 2000.

3. This element may only be populated or updated by the Support Point.

CAR Other Related Information

DLMS Note:

1. Use to identify the Corrective Action by Contractor describing the actions the contractor took to fix

problem. Equates to DLA Form 1227, Block 13.

2. Field size = 2000.

3. This element may only be populated or updated by the Support Point.

CBB Consideration to be Received

DLMS Note:

1. Use to identify the Contractors Position on repair or replacement of materiel. Equates to DLA Form

1227 Block 16.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 61 January 23, 2024

2. Field size = 2000.

3. This element may only be populated or updated by the Support Point.

CER Certification Narrative

DLMS Note:

1. Use to identify Final Reply for Alerts narrative. This is the PQDR Joint Regulation narrative

requesting screening of materiel. Optional for USAF.

2. Field size = 2000.

3. This element may only be populated or updated by the Action Point.

EAT Asset Disposition

DLMS Note:

1. Use to identify the Materiel Disposition instructions.

2. Field size = 2000.

3. Definition: Use to identify the Materiel Disposition instructions to the Support Point for the defective

item narrative.

4. This element may only be populated or updated by the Action Point.

IID Inventory (Stock) Description

DLMS Note:

1. Use to document the Results of Depot Surveillance. This is the depot stock screening information

including any findings as a result of screening depot stocks for similar problems.

2. Field size = 2000.

3. This element may only be populated or updated by the Action Point or the Support Point.

ORI Order Instructions

DLMS Note:

1. Use to provide, explain, or otherwise describe unique Shipping Instructions.

2. Field size = 2000.

3. This element may be used by the Action Point and updated by the Screening Point and/or the

Support Point.

OTH Other Instructions

DLMS Note:

1. Use to identify the Exhibit Final Disposition Instruction containing the Action Point instruction to

Screening or Support Point for final handling of the exhibit.

2. Field size = 2000.

3. This element may only be populated or updated by the Screening Point, Action Point, or Support

Point.

REC Recommendation

DLMS Note:

1. Use to identify the Findings and recommendations of Investigation. This is a narrative describing the

results of the investigation, action taken to correct the deficiency, and the corrective action to prevent

recurrence.

2. Field size = 4000.

3. This element may only be populated or updated by the Action Point.

REP Report

DLMS Note:

1. Use to identify the Preventive Action Taken (Answer) narrative. Derived from the DLA Form 1227.

2. Field size = 2000.
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

Code Name

004030F842P0PA10 62 January 23, 2024

3. This element may only be populated or updated by the Support Point.

RPT Report Remarks

DLMS Note:

1. Use to identify Remarks and Recommendations providing any government or contractor comments

related to the investigation. Equates to DLA Form 1227, Block 17.

2. Field size = 2000.

3. This element may only be populated or updated by the Support Point.

SSC Status Comment

DLMS Note:

1. Use to identify the Enclosures Distribution. This identifies attachments and mailing codes associated

with the 1227. Equates to DLA Form 1227, Block 18.

2. Field size = 2000.

3. This element may only be populated or updated by the Support Point.

TRS Quality Information

DLMS Note:

1. Use to identify the Cause of Deficiency narrative describing the Root cause of deficiency found

during the investigation. Equates to DLA Form 1227, Block 12.

2. Field size = 2000.

3. This element may only be populated or updated by the Support Point.

WHI Warehouse Instruction

DLMS Note:

1. Use to identify Corrective Actions by Government narrative. This provides DCMA's verification

corrective actions. Equates to DLA Form 1227, Block 14.

2. Field size = 2000.

3. This element may only be populated or updated by the Support Point.

NTE02 352 Description

Description: A free-form description to clarify the

related data elements and their content

DLMS Note: 1. Differences in system field sizes

may exist. Coordinate with receiving systems to

ensure they have the capability accept the quantity

of data sent.

2. Use multiple repetitions of NTE, with up to 80

positions for each line, until reaching the maximum

length specified.

3. Special characters are not allowed except as

specified. Valid characters are: @ # $ ( ) - = + , / & ;

: and .

M AN 1/80 Must use
DLMS Implementation Convention (IC) 842P ADC 1007, 1007B, 1007C, 1007D, 1007E, 1043C, 1136, 1161A, 1244, 1367, 1412 and 1420 DLM 4000.25

Product Quality Deficiency Report (PQDR)

004030F842P0PA10 63 January 23, 2024

SE Transaction Set Trailer Pos: 4700 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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

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

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