OFFICE OF THE ASSISTANT SECRETARY OF DEFENSE 3500 DEFENSE PENTAGON

WASHINGTON, DC 20301-3500

SUSTAINMENT 

MEMORANDUM FOR PRODUCT QUALITY DEFICIENCY REPORT PROCESS

REVIEW COMMITTEE 

SUBJECT: Approved Defense Logistics Management Standards Change 1007E, Defense 

Logistics Management Standards 842P Procedures, Business Rules, Data Elements 

and Coding Updates 

The Defense Logistics Management Standards change, as outlined in the attachment, is 

approved for implementation. 

Addressees may direct questions to Mark Rockwell, e-mail: DEDSO.PQDR@dla.mil. 

Others must contact their designated PRC representative available at https://www.dla.mil/

Defense-Data-Standards/Committees/Contacts/. 

Leigh E. Method, SES 

Deputy Assistant Secretary of Defense 

for Logistics 

Attachment

As stated

cc:

OUSD(C)

DLA J6DS 
Attachment, ADC 1007E

Page 1

Approved Defense Logistics Management Standards Change 1007E

Defense Logistics Management Standards 842P Procedures, 

Business Rules, Data Elements, and Coding Updates 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: 

(1) Defense Logistics Agency, Logistics Operations, Makeya Porter, 703-223-

3446, makeya.porter@dla.mil. 

(2) Product Data Reporting and Evaluation Program - Automated Information 

System (PDREP-AIS): Naval Sea Logistics Center, Elizabeth Woodbury, 207-438-6527, 

elizabeth.a.woodbury3.civ@us.navy.mil. 

(3) Joint Deficiency Reporting System (JDRS): Naval Air Systems Command, 

Brian McCabe, 732-323-1683, brian.d.mccabe4.civ@us.navy.mil. 

b. Functional POC: 

(1) Defense Logistics Agency, Logistics Operations, Steven Nace, 571-477-4194, 

steven.nace@dla.mil.

(2) Headquarters, Army Materiel Command, Marc Saperstein, 973-769-6410, 

marc.d.saperstein.civ@army.mil.

(3) Headquarters, United States Marine Corps, Chief Warrant Officer (CWO5)

Jason Pierce, 571-256-7127, jason.m.pierce@usmc.mil. 

(4) Naval Supply Systems Command, Jared Trinkaus, 484-515-2504, 

jared.s.trinkaus.civ@us.navy.mil.

(5) Headquarters, United States Air Force, John Wright, 703-697-5238, 

john.wright.45@us.af.mil. 

(6) Defense Contract Management Agency, Phil Wedgie, 804-536-6638, 

Philip.wedgie.civ@mail.mil. 

2. REASON FOR CHANGE: Significant changes after staffing the proposed change are in 

green shade. To establish the business rules, data elements, and codes required to fully program 

the Department of Defense (DoD) automated information systems (AISs) listed in Paragraph 5.b. 

to fully implement the Defense Logistics Management Standards (DLMS) 842P transaction set 

and increase use of Product Quality Deficiency Reports (PQDR) data analytic capabilities.

a. Bottom Line Up-Front: This change updates, clarifies, and expands upon the DLMS 

842P PQDR Data Exchange Implementation Convention (IC), associated business rules, data 

elements, codes, and procedures for the systemic processing of PQDRs. 
Attachment, ADC 1007E

Page 2 

b. Background: The Approved DLMS Changes (ADCs) referenced in Paragraph 10

have incrementally provided improvements to the DLMS 842P PQDR Data Exchange IC. 

However, these changes have not provided the full scale of business rules necessary to fully 

program applicable AISs for DoD PQDR processing. 

3. CHANGE IN DETAIL: 

a. Technical Details: This change includes the following with more specific details 

provided in Enclosures 1, 3 and 4: 

(1) Transaction Set Purpose Code citations have been moved from Reference 

10.f. to a newly created section within Reference 10.g. This move reorganizes the structure of 

information in both references to allow Reference 10.f. to be more procedural for end users while 

Reference 10.g. provides more AIS specific information and business rules. 

(2) Transaction Set Purpose Codes have been reviewed in their entirety and 

revised, where needed, to inform which PQDR processing point may populate and update a 

specific transaction. The Transaction Set Purpose Code uses, and definitions have been updated 

while also establishing newly created business rules needed to support AIS programing. 

(3) This change establishes new 842P specific data elements and associated 

codes, further described in Section 12.a. of this change and Enclosure 4. These new codes will 

allow for increased data analytic capabilities and provides recipients of specific Transaction Set 

Purpose Codes with a high-level purpose or reason for the communication. 

(4) Incorporates the description of the PQDR investigative closing data elements 

and Summary Code into Reference 10.f. Additionally, these data elements and their 

corresponding codes been added to Reference 10.g., where they will replace Reference 10.i. as 

the authoritative document for these codes. The investigative closing codes provide specific 

details about the findings of the investigation. Together these codes make up seven segments of 

investigation related data forming a nine-character code referred to as the Summary Code. These 

closing data elements were already incorporated into Reference 10.h. as part of Reference 10.a.

(5) The procedures located in Reference f. have been significantly updated to 

provide end users with more detailed guidance on the transactional processing and information 

control requirements for PQDRs. It also expands upon both the purpose and functional 

requirements of PDREP-AIS as the being the DoD quality system of records as established in 

Reference 10.e. More specific changes to Reference 10.f. can be found in Enclosure 3. 

b. Revised Transaction Flow: See Enclosure 2.

4. IMPLEMENTATION TARGET: The initial implementation target prescribed in 

Reference 10.f. could not be executed by PQDR processing systems due to missing business 

rules. This change implements the business rules required for system programming and restarts 

the phased implementation as follows:
Attachment, ADC 1007E

Page 3 

TASK ESTIMATED 

DURATION

ESTIMATED 

COMPLETION

Develop Detailed Requirements (DR) 12 weeks 12 weeks

Design 2 weeks 14 weeks

Development 44 weeks 58 weeks

Internal System Test 16 weeks 74 weeks

Integrated System Test 12 weeks 86 weeks

Product Delivery 4 weeks 90 weeks

Release to Production - 2 days (Saturday/Sunday 

weekend maintenance window)

2 days 90 weeks, 2 days 

5. TECHNICAL IMPACT: 

a. Additions or Changes to Data Elements: See Enclosure 1.

b. Automated Information Systems (AIS): 

(1) Product Data Reporting and Evaluation Program (PDREP). 

(2) Joint Deficiency Reporting System (JDRS). 

(3) Enterprise Business System (EBS). 

c. Defense Automatic Addressing System (DAAS): DAAS will route transactions to 

the appropriate activity identified to receive the transactions. 

6. PUBLICATION/POLICY IMPACT:

 a. Defense Logistics Manual (DLM) 4000.25: Update DLM Volume 2, Chapter 24, 

Product Quality Deficiency Reporting and Appendix 7.27 Product Quality Deficiency Report 

Relevant Data Elements as shown in Enclosures 3 and 4. 

 b. Non-DLM 4000.25 Publications: Updates to the following publications may be 

required, in addition to local military service and defense agency guidance:

(1) DLAR 4155.24/AR 702- 7/SECNAVINST 4855.21/AFI 21-115/DCMA 

INST 1102, PRODUCT QUALITY DEFICIENCY REPORT PROGRAM, August 1, 2022 

(2) SECNAVINST 4855.3, (ASN (RD&A)) PRODUCT DATA REPORTING 

AND EVALUATION PROGRAM, December 21, 2018
Attachment, ADC 1007E

Page 4 

(3) DoDI 5000.79, Defense-Wide Sharing and Use of Supplier and Product 

Performance Information (PI), October 15, 2019

7. ASSUMPTIONS: System-to-system testing will be necessary for DAAS and all applicable 

systems programing to this change prior to being released to end users for use. 

8. FINANCIAL IMPROVEMENT AND AUDIT REMEDIATION (FIAR), MATERIAL 

WEAKNESS, AND AUDIT-RELATED INFORMATION: 

a. Notices of Findings and Recommendations (NFR): None identified. 

b. Corrective Action Plan (CAP) References: None identified.

c. Other FIAR, Material Weakness, and Audit-Related Information: None 

identified.

9. END-TO-END TESTING REQUIREMENTS: 

 a. JDRS, PDREP and EBS will develop a test plan to ensure all functional and systemic 

requirements documented in this change will be tested as set forth in the above timeframe for 

implementation.

 b. DAAS will also route and transmit transactions to the activities identified to receive 

the transactions. 

10. REFERENCES:

a. Approved DLMS Change (ADC) 1007, New DLMS 842P, PQDR Data Exchange and 

Enhanced Exhibit Tracking via Standard Logistics Transactions, October 1, 2012 

b. ADC 1007A, Enhanced Pre-positioned Materiel Receipt (PMR) Data for PQDR 

Exhibit Tracking, February 27, 2013

c. ADC 1007B, Administrative Update to the DLMS 842P Product PQDR Data 

Exchange (Supply/Deficiency Reporting), July 18, 2013

d. ADC 1007C, Code Updates to the DLMS 842P PQDR Data Exchange 

(Supply/Deficiency Reporting) July 31, 2014

e. ADC 1007D, PQDR Establishment, PQDR System Structure Change, and Code 

Updates to the DLMS 842P PQDR Data, December 16, 2020

f. DLM 4000.25, Volume 2, Chapter 24, Product Quality Deficiency Report, current 

version

g. DLM 4000.25, Volume 2, Appendix 7.27 Product Quality Deficiency Report (PQDR) 

Relevant Data Elements, current version 

h. DLMS Implementation Convention 842P, February 12, 2021
Attachment, ADC 1007E

Page 5 

i. DLAR 4155.24 DLAR 4155.24/AR 702- 7/SECNAVINST 4855.21/AFI 21-

115/DCMA INST 305, PRODUCT QUALITY DEFICIENCY REPORT PROGRAM, October 

19, 2018 (CAC Required)

11. PDC 1007E RESPONSE/COMMENT RESOLUTION: 

Component Response/Comment Disposition

1. ODASD 

(Logistics)

Concurrence by signing PDC. As noted. 

2. USASAC Concur As noted. 

3. US Navy Concur with comments:

1. AP7.27.4 (AP7.27.4.1-.3) is unnecessary as no systems 

use these codes. Concur to delete as requested. 

2. AP7.27.1.3.6: The committee has not defined what an 

Alternate Support Point is and the business processes related 

to this role. Unless the business process is further defined, 

Alternate Support Point cannot be added to the process. 

3. AP7.27.1.3.6/ AP7.27.1.3.7: The Transaction Set Purpose 

Code DA code needs to remain, but it should not be used to 

create multiple support points (see comment 2 above), at least 

not as the business process currently exists. Another 

transaction type would be required if the intention is to 

document the involvement of another activity providing 

information back to the Support or Action Point. 

DEDSO Response:

1.Updates complete.

2. AP7.27.1.3.6. states: 

Delegate to Alternate 

(Delegate to Alternate 

Support Point) 

(Transaction Set 

Purpose Code DA). 

Used to document 

Action Point or 

responsible Support 

Point delegation to an 

entity that does not 

support PQDR 

investigations through a 

PQDR IS, such as 

Engineering Support 

Activities (ESA). 

3. The use of this code 

to add another Support 

Point without changing 

the existing Support 

Point was not part of 

this change. This was 

existing language that 

already existed in the 

DLMS 842P IC. 

AP7.27.1.3.6. was 

updated to reflect what 

was in the existing 

DLMS note.
Attachment, ADC 1007E

Page 6

4. Clarification required: 1/BNR01/0200, 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.

a. PDREP question - For 'Transfer within Action Point' - is 

this within PDREP only or is this a status change that will be 

a received as an update from EBS or JDRS?

5. Clarification required: 1/BNR01/0200, 08 Status; DLMS 

Note: Used to acknowledge that a PQDR was received and 

provide the status to the previous point. Originators are 

required to execute this transaction set within 24 hours of 

discovery from Category I and three calendar days of 

discovery from Category II PQDRs. 

a. PDREP Question: Originators do not acknowledge receipt. 

This requires further clarification. 

6. Navy is formally recommending in their reply that no 

codes specific to PQDR be removed that are not noted by 

Navy above. Other system components can choose not to use 

codes, but unless agreed by all system components, a code 

should not be removed without further discussion and 

concurrence. 

7. PDC 1007E states “inter-service transactions” several 

times throughout, however, it is not clearly defined. Please 

provide a clear definition of inter-service transactions. A 

clear definition is required since there are several 

transactional restrictions required for inter-service 

transactions. Without the full scope of this term, accurate 

programming and implementation cannot occur.

4.No change. None of 

the definitions of the set 

codes or how they are 

to be used were part of 

the change. All that was 

updated regarding set 

codes was who could 

use/update certain 

codes. All comments 

outside of the changes 

to who can use the set 

code is outside of the 

scope for this review.

a. No change. Out of 

scope for this change.

5. Concur. Originator 

wording and 

requirement removed 

from the DLMS note.

6. Navy concurred to 

removing set code 06, 

as discussed in a 

meeting held on April 

10, 2023. If Navy has 

changed, then the 

removal of set code 06 

will need to be added to 

a future PDC. 

7. During ADC 

development, the Army 

wanted the flexibility to 

change portions of the 

PQDR process for 

PQDRs that existed 

100% within the Army. 

Example: The set code 

CO states: For interservice PQDRs, the 

Originating Point may 

only submit this 

transaction to the 

Screening Point. This 

verbiage was added so 
Attachment, ADC 1007E

Page 7

that PQDRs within the 

Army “intra-service” 

could allow Originators 

to communicate outside 

of the swim lane 

business rules agreed 

upon for “inter-service” 

PQDRs.

4. US Air Force Concur. As noted.

5. US Army Concur with comments:

1. Proposed revisions for the 842P Implementation 

Convention can be found in Enclosure 1, Attachment 1. (See 

attached) 

2. Proposed revisions Revised DLM 4000.25, Volume 2, 

Chapter 24 and Appendix 7.27, Product Quality Deficiency 

Report Relevant Data Elements can be found on Enclosure 1, 

Attachment 2. (See attached)

3. See ADC 1007E Enclosure 6 for Army Updates to the 

Change Table.

DEDSO Response:

1. See enclosure 6. 

Updates completed.

2. See enclosure 6. 

Updates completed.

3.Updates completed. 

See enclosure 6.

Note: TACOM 

comments deemed 

pertinent for 

implementation 

meetings. 

6. USMC Concur with comments: 

1. Would like to see an overall time limit table for PQDRs. 

It is in the different segments but would serve the user better 

if there was a table with all time limits.

2. It is important the time limit be I the DLMS or we will 

have no accountability on the Action or Support point.

DEDSO Response:

1. DEDSO agrees but 

this would need to be in 

new PDC. 

2. DEDSO agrees but 

this would need to be in 

new PDC. 

7. DLA Concur with comments:

1. Proposed revisions for the 842P Implementation 

Convention can be found in Attachment 3. 

2. Proposed revisions for Revised DLM 4000.25, Volume 2, 

Appendix 7.27 can be found at Attachment 4.

3. See ADC 1007E Enclosure 5 for DLA Updates to the 

Change Table.

DEDSO Response:

1. See enclosure 5. 

Updates completed.

2.See enclosure 5. 

Updates completed.

3.Updates completed. 

See enclosure 5.
Attachment, ADC 1007E

Page 8 

8. DCMA Concur with comments:

1. b (6) change From: Defense Contract Management 

Agency, Nathan Rentfrow, 804-638-4696, 

nathan.l.rentfrow.civ@mail.mil. 

To: Defense Contract Management Agency, Phil Wedgie, 

804-536-6638, Philip.wedgie.civ@mail.mil 

2. Throughout the document it appears that Automated 

Information System (AIS) and the word system are used 

interchangeably other places it appears they are used for 

specific purpose 

o Suggest when adjudicating comments verify the 

usage of terms and change to a consistent 

lexicon. 

3. 6.b. Non-DLM publications: 

o Change or remove: (1) DLAR 4155.24/AR 702- 

7/SECNAVINST 4855.21/AFI 21- 115/DCMA INST 

305, PRODUCT QUALITY DEFICIENCY 

REPORT PROGRAM,

December 19, 2018

o To: (1) DLAR 4155.24/AR 702- 7/SECNAVINST 

4855.21/AFI 21-115/DCMA INST 1102, PRODUCT 

QUALITY DEFICIENCY REPORT PROGRAM, 

August 1, 2022 

4. There are two different C24.1.2. paragraphs. Recommend 

renumbering. 

5. C24.1.5. The term PDREP-AIS refers to both the overall 

business process and supporting automation, including both 

direct web input and transaction exchange.

 o Verify with PDREP, that PDREP-AIS refers to the 

overall business process. 

6. C24.1.5.2 

o From: PDREP will provide an automated process for

tracking PQDR response information Data collected

will enable the DOD to identify trends, establish

volume and dollar values of PQDRs, bring 

management attention to problems with materiel

quality and supplier performance information as

necessary, and improve the requisitioning and 

distribution process within logistics operations. This

provides an effective means to report, resolve, and 

measure deficiencies related to supply chain

performance. One of the goals is to incorporate

DEDSO Response:

1. Update completed. 

2. Para 5.b. defines the 

AIS systems PDREP, 

JDRS, and EBS. These 

acronyms and the word 

“system” are used 

frequently and 

appropriately. 

3. Change made to 

reflect DCMA INST 

1102, August 1, 2022. 

Note: Yellow 

highlights are imbedded 

with the DLA 

comments and cannot 

be removed. 

4. Change completed to 

reflect C24.1.2.1. 

5. DEDSO agrees and 

para C24.1.5 has been 

re-written for clarity. 

PDREP is the overall 

program and PDREPAIS is the automated 

information system. 

6. ADC updated. 
Attachment, ADC 1007E

Page 9 

PQDR metrics to improve overall supply chain

performance.

To: PDREP provides an automated process for tracking

PQDR response information. Data collected will enable the 

DOD to identify trends, establish discrepancy volume, and

dollar values of PQDRs. This allows users to bring 

management attention to problems with materiel quality and 

supplier performance information as necessary, improving

the requisitioning and distribution process within logistics

operations. This process provides an effective means to

report, resolve, and measure deficiencies related to supply 

chain performance. One of the goals is to incorporate PQDR 

metrics to improve overall supply chain performance. [Either 

define all goals or remove the sentence]

7. C24.1.5.2.1. Access to PDREP PQDR management 

reports requires submission of a User Access Request (UAR) 

to the PDREP System home page. 

o Suggest moving up earlier in chapter right after PDREP 

introduction 

8. C24.1.5.3. 

o From: The DOD requirement is that paper 

submission of PQDRs and non-DLMS compliant

PQDR applications will be fully phased out with

migration to DLMS. By exception, until

electronic reporting under DLMS is universally 

available, PQDRs and associated responses may 

be reported via hard-copy SF 368, email, through 

customer service help lines or any other manner 

acceptable to the submitter and recipient. All

manner of inter-service transactional reporting 

must meet the criteria described in this chapter.

o To: The DOD requirement is that paper submission of 

PQDRs and non-DLMS compliant PQDR

applications will be fully phased out with migration to

DLMS. However, until electronic reporting under 

DLMS is universally available, PQDRs and

associated responses may be reported via hard-copy 

SF 368, email, through customer service help lines or

any other manner acceptable to the submitter and

recipient. 

o [incorporate into Applicability” paragraph] All 

manner of inter-service transactional reporting 

must meet the criteria described in this chapter.

 Suggest moving up earlier in chapter right after C24.1.1 

9. C24.2.1. 

7. DEDSO agrees, and 

the sentence has been 

merged into C.24.1.5.1. 

8. DEDSO does not 

agree with this 

comment since use of 

the word, “However” 

instead of “By 

Exception,” has a 

material change in the 

meaning and intent of 

this paragraph. No 

change has been made 

to C24.1.5.3. 
Attachment, ADC 1007E

Page 10

o From: ~ The Action Point will either investigate the report 

or assign the report to a Support Point for investigation. 

o To: ~The Action Point will either investigate the report or 

assign the report to a Support Point to assist with the

investigation. 

10. C24.2.2. 

o From: Detailed Requirement. When data is 

required to be exchanged across Component lines 

or between various AISs, there will be a data 

exchange process. ...

o To: Detailed Requirement. The process for interservice data exchange or between various AIS is as 

follows; ... or remove the sentence. 

11. C24.2.3.1 

o From: Which PQDR processing points may update any 

data element and at what point in the PQDR process is also

defined in the DLMS 842P IC. For inter-Service PQDRs,

communication both to and from Originators must only be 

sent to the Screening Point for evaluation regardless of 

transaction code. PQDR processing points can only directly

communicate with the processing point directly preceding or 

following them. Additional

business rules can be found in Appendix 7.27 of this volume. 

o To: The DLMS 842P IC defines the PQDR 

processing points. Appendix 7.27 of this volume 

contains the PQDR processing business rules. 

9. ADC updated.

10. ADC updated. 

11. DEDSO partially 

agrees with this 

comment and rewrote a 

portion of para 

C24.2.3.1 for added 

clarity, but most of the 

verbiage has remained 

intact. 
Enclosure 1, ADC 1007E

Page 1

Enclosure 1

Revised 842P Implementation Convention (IC) Change Table

Additions are identified by bold italics and deletions by single strikethrough text. 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1007E to DLMS Introductory Note 8:

- ADC 1007E, DLMS 842P Systemic Processing, Transaction 

Business Rules and Coding Updates

Identifies DLMS Changes

included in the

DLMS Supplement. 

2. 1/BNR01/0200 Update DLMS note(s) for existing codes 00, 03, 06, 08, 10, 11, 22, 45, 

47, CN, CO, DA, ER, FA, FS, RO and SU: 

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. 

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.

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. 

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

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 2 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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.

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. 

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.

DA Delegate to Alternate

DLMS Note: 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.

ER Exhibit Receipt

DLMS Note: 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. 

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. 

FS Forward to Support

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.

RO Reopen

DLMS Note: 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.

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.
Enclosure 1, ADC 1007E

Page 3 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

3. 2/LIN02/0200 Update DLMS Note to the following existing codes FS, FT, NN, SW 

and ZZ: 

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

2. This element may be populated/updated 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/updated 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/updated 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/updated by the Originating Point or 

the Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

Clarify intended use of the 

qualifiers

4. 2/LIN10/0200 Update DLMS Note 2 to existing code W2:

W2 Work Unit Number

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 4 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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/updated by the Originating Point or 

the Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

5. 2/LIN14/0200 Update DLMS note 3 to existing code ZB:

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 CrossReference System (BINCS).

3. This element may be populated/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers

6. 2/LIN16/0200 Update DLMS Note 2 to existing code F8:

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/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers

7. 2/LIN18/0200 Update DLMS Note 2 to existing code GE:

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/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers

8. 2/LIN20/0200 Update DLMS Note 4 to existing code EM:

EM Equipment Identification Number

DLMS Note: 1. Use to identify Next Higher Assembly Serial Number. 

Equates to SF368, Block 17d.

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/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 5 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

9. 2/LIN22/0200 Update DLMS Note 2 to existing code PU:

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/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers

10. 2/LIN24/0200 Update DLMS note 2 to existing code GE:

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/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers

11. 2/LIN26/0200 Update DLMS note 4 to existing code SE:

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 in the report loop.

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

IUID policy.

4. This element may be populated/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers

12. 2/LIN28/0200 Update DLMS note 2 to existing code MN:

MN Model Number

DLMS Note: 1. Use to identify the Engine Model Number.

2. This element may be populated/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers

13. 2/DTM01/0600 Update DLMS note for the following existing codes 002, 011, 094, 

214, 512, 514, 516, 922, 947, and ABY: 

002 Delivery Request

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/updated by the Originating Point, 

Screening Point, or Action Point. For inter-service transactions, only 

the Screening Point or Action Point can update this element.

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 6 

011 Shipped

DLMS Note: 1. Use to identify the Exhibit Shipped Date.

2. This element may be populated/updated by any role. For interservice transactions, only the Screening Point, Action Point and 

Support Point can update this element.

094 Manufacture

DLMS Note: 1. Use to identify the Date of Manufacture.

2. This element may be populated/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

512 Warranty Expiration

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/updated 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/updated 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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point may update this element.

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/updated 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 
Enclosure 1, ADC 1007E

Page 7 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point may update this element.

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point may update this element.

14. 2/REF01/0700 Modify DLMS note for the following existing codes, remove code X3

and add code 2E: 

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/updated 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

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

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.

Clarify intended use of the 

qualifiers, remove code and add 

new code.
Enclosure 1, ADC 1007E

Page 8 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

3. This element may be populated/updated 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/updated by the Originating Point or 

the Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

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.

3. This element may be populated/updated 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/updated 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'Y' 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/updated 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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

PM Part Number

DLMS Note: 1. Use to identify the End Item Part Number.
Enclosure 1, ADC 1007E

Page 9 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

2. This element may be populated/updated 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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

TG Transportation Control Number

DLMS Note: 1. Use to indicate the Transportation Control number.

2. Field size = 17.

3. This element may only be populated/updated 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/updated 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: 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/updated 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 
Enclosure 1, ADC 1007E

Page 10

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

(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/updated by the Originating 

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

X3 Defect Code Number

DLMS Note:

Use to identify the PQDR Summary Code structured as follows: 

{Intervening Note text not shown} 

Current Disposition (13th position)

SF368 Block 19: Use codes H-Holding Exhibit, D-Disposed 

of/Destroyed, R-Repaired, or O-Other.

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

Point or Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

Action Requested (14th position)

SF368 Block 21: Use codes C-Credit, R-Repair, E- Replacement, or OOther

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

Point or Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

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 and/or updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

15. 2/REF03/0700 Update DLMS Note 2 

DLMS Note: 

1. Use to identify the generating-system report number from systems 

such as DLA- EBS, JDRS, or PDREP.

1. This element may be populated/updated 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.

Clarify intended use of the 

qualifiers

16. 2/REF04-

01/0700

Update DLMS Note 2 to existing code W7:

W7 Commercial and Government Entity (CAGE) Code

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/updated by the Originating 

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 11

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

17. 2/LQ01/1050 Update DLMS note for the following existing codes and add new 

codes ARC, BCD, CAT, CDC, DRC, DVC, FEC, GCP, IRC, PAT, 

P1C, P2C, PCC, PCD, PDD, PQC, PQR, PQS, RAC, and SDC: 

ARC Action Requested Code 

DLMS Note: SF368 Block 21: Use codes C-Credit, R-Repair, EReplacement, or O-Other This field may only be populated and/or 

updated by the Originating Point.

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

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.

CDC Current Disposition Code 

DLMS Note:

1. SF368 Block 19: Use codes H-Holding Exhibit, D-Disposed 

of/Destroyed, R-Repaired, or O-Other.

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.

DE Signal Code

DLMS Note: 1. Use to identify the Signal Code.

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

Point, Screening Point or Action Point. For inter-service 

Clarify intended use of the 

qualifiers and add new codes.
Enclosure 1, ADC 1007E

Page 12

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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/updated by the Originating 

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

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.

1. 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, OOther 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

EQ Controlled Inventory Item Code

DLMS Note: 1. Use to identify the Controlled Inventory Item Code.

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

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

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 
Enclosure 1, ADC 1007E

Page 13

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

FD Demilitarization Code

DLMS Note: 1. Use to identify the Demilitarization Code.

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

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

GCP Product Quality Deficiency 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.

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/updated by the Originating 

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

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.

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
Enclosure 1, ADC 1007E

Page 14

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

Point or Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

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.

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/updated 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

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.
Enclosure 1, ADC 1007E

Page 15

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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 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 PQRD Summary Code. 

Definition: Level of Severity of the defect. See PQDR Joint 

Regulation for appropriate codes This field may be 
Enclosure 1, ADC 1007E

Page 16

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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.

18. 2/NTE01/2400 Update DLMS note for the following existing codes, add Code SPS 

and remove Code EBK: 

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/updated 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/updated by the Originating 

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point can update this element.

Clarify intended use of the 

qualifiers

19. 2/QTY01/2700 Update DLMS note for the following existing codes and add new 

codes T8 and T9: 

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/updated 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 

Clarify intended use of the 

qualifiers and add new 

qualifiers.
Enclosure 1, ADC 1007E

Page 17

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

materiel failure.

2. Field size = 7.

3. This element may be populated/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

39 Shipped Quantity

DLMS Note: 1. Use to identify the Quantity of Exhibits Shipped.

2. Field size = 7.

3. This element may only be populated/updated 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/updated 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/updated by the Originating 

Point, Screening Point or Action Point. For inter-service 

transactions, only the Screening Point and Action Point can update 

this element.

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/updated 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.
Enclosure 1, ADC 1007E

Page 18

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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.

UA Units Completed

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

20. 2/QTY03/2700 Update Data Element level DLMS Note 4:

Composite Unit of Measure

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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

Clarify intended use of the 

qualifiers

21. 2/AMT01/2730 Update DLMS note for the following existing codes: 

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/updated 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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 19

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

RP Repair

DLMS Note: 1. Use to identify the Estimated Repair Cost to repair the 

deficient materiel.

2. Field size = 15.

3. This element may only be populated/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

Z3 Unit of 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.

2. Field size = 15.

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

Point, Screening Point, or Action Point. For inter-service 

transactions, only the Screening Point or Action Point can update 

this element.

22. 2/N101/2800 Update DLMS note for the following existing codes: 

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

Clarify intended use of the 

qualifiers

23. 2/N102/2800 Update Data Element level DLMS Note 2:

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

24. 2/N201/2900 Update Data Element level DLMS Note 3:

Name

DLMS Note: 1. This equates to address line.

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 20

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

25. 2/N202/2900 Update Data Element level DLMS Note 3:

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

Clarify intended use of the 

qualifiers

26. 2/PER01/3200 Update DLMS Note 2 for the following existing codes: 

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/updated by the Originating 

Point or Screening Point. For inter-service transactions, only the 

Screening Point and can update this element.

Clarify intended use of the 

qualifiers

27. 2/PER03/3200 Update DLMS Note 2 for the following existing codes: 

AU Defense Switched Network

DLMS Note: 1. Use to identify the DSN Phone Number.

2. This element may be populated/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

EM Electronic Email

DLMS Note: 1. Use to identify the E-mail address.

2. This element may be populated/updated 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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

Clarify intended use of the 

qualifiers
Enclosure 1, ADC 1007E

Page 21

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

28. 2/PER05/3200 Update DLMS note 2 for the following existing codes: 

AU Defense Switched Network

DLMS Note: 1. Use to identify the DSN Phone Number.

2. This element may be populated/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

EM Electronic Email

DLMS Note: 1. Use to identify the E-mail address.

2. This element may be populated/updated 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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

29. 2/PER07/3200 Update DLMS Note 2 for the following existing codes: 

AU Defense Switched Network

DLMS Note: 1. Use to identify the DSN Phone Number.

2. This element may be populated/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

EM Electronic Email

DLMS Note: 1. Use to identify the E-mail address.

2. This element may be populated/updated 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/updated by all processing points. 

For inter-service transactions, only the Screening Point, Action Point 

and Support Point can update this element.

Clarify intended use of the 

qualifiers

30. 2/PER09/3200 Add new Data Element level DLMS Note 2:

Contact Inquiry Reference

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.

Clarify intended use of the 

qualifiers
Enclosure 2, ADC 1007E

Page 1

Enclosure 2 

PQDR Life Cycle Flowchart and Transaction Timeline

Legend

Transaction moves the PQDR to the next location

Transaction moves the PQDR back to the previous location

Interim Transaction (Interim reply, Follow-up, Correspondence, etc.)

Transfers ownership of the PQDR to a different activity/person

Exhibit Transactions
Enclosure 2, ADC 1007E

Page 2 

Legend

Transaction moves the PQDR to the next location

Transaction moves the PQDR back to the previous location

Interim Transaction (Interim reply, Follow-up, Correspondence, etc.)

Transfers ownership of the PQDR to a different activity/person

Exhibit Transactions
Enclosure 3, ADC 1007E

Page 1

Enclosure 3

Revised DLM 4000.25, Volume 2, Chapter 24

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

C24. CHAPTER 24

PRODUCT QUALITY DEFICIENCY REPORTING

C24.1 GENERAL 

C24.1.1. Processing Requirements. This chapter provides general information 

supporting the DOD Product Quality Deficiency Report (PQDR) Program Process. and

SECNAVINST 4855.3, Product Data Reporting and Evaluation Program. The DOD 

PQDR program process requires DOD Components to capture and exchange product 

quality deficiency information to facilitate root cause determinations, corrective actions, 

reliability analysis, and recoupment actions (contractor caused deficiencies). This 

chapter provides an overview of the Defense Logistics Management Standard (DLMS) 

transaction exchange supporting the PQDR program process. Initial implementation 

will include the DLA Enterprise Business Systems (EBS), SECNAV Product Data 

Reporting and Evaluation Program (PDREP), and NAVAIRSYSCOM Joint Deficiency 

Reporting System (JDRS). Initially, all transactions will pass through the PQDR Interservice Interface (PQDR II). Components developing PQDR processing systems will 

comply with this DLMS to exchange data with other DOD PQDR. 

C24.1.2. PQDR Processing Information Systems. It is DOD policy that DOD 

Components maintain a reliable and standard system for investigation of Product 

Quality Deficiency Reports. Systems must provide feedback of product quality 

deficiency data across DOD AISs. Components developing or maintaining PQDR 

processing AISs comply with this DLMS to exchange data with other DOD PQDR 

AISs.

C24.1.2.1 Operations Security (OPSEC) Applicability. Due to an identified 

OPSEC requirement, PQDRs have been designated as controlled unclassified 

information (CUI) and must be identified as CUI. Physical handling and electronic 

transmission of PQDRs must comply with DoD rules for this level of sensitive 

unclassified information, to include proper labeling, protection, and encryption of 

communication. 

C24.1.3. Standard PQDR Transactions. Under DLMS, the PQDR will be 

considered a common logistics information exchange to be integrated with 

transaction processing through DAAS. The DOD approved standard for 

electronic transmission of PQDR transactions is prescribed by the DLMS 842P

Implementation Convention (IC) using a Web Service XML transaction format. 

The DLMS 842P, Standard PQDR, will be employed for transactional exchange 
Enclosure 3, ADC 1007E

Page 2 

and is available via the Implementation Convention/DLMS IC page of the Defense 

Enterprise Data Standards Office (DEDSO) website.

C24.1.4. PQDR Transaction Sets. The PQDR transaction set is used to move 

the all PQDR (SF-368) data as listed in DLMS 842P between the various PQDR 

processing points (oOriginator/oOriginating pPoint, sScreening pPoint, aAction pPoint, 

and sSupport pPoint). It is also used to facilitate PQDR exhibit movement,and 

exchange general information pertinent correspondence and/or data regarding a 

PQDRs status (i.e., interim responses, general correspondence, etc.). For each 

transmission, the receiving system will provide a transaction to the submitting system 

acknowledging data receipt. The DLMS 842P IC, PQDR Data Exchange, replaces 

system unique transactions currently used to exchange PQDR date data This DLMS 

enhancement provides by providing the DOD Components with a standard electronic 

transmission method for reporting PQDR data exchange across between AIS's.

C24.1.5. Product Data Reporting and Evaluation Program (PDREP). The term 

PDREP refers to both the overall business process and supporting automation, 

including both direct web input and transaction exchange. PDREP promotes 

continuous process improvement of supply chain processes within the DoD for 

increased material readiness by providing a means to hold external DoD 

suppliers and internal supply chain stakeholders accountable. PDREP-AIS 

formerly known as the Product Quality Deficiency Report Inter-service Interface 

(PQDRII), is the DoD's PQDR system of record. PDREP-AIS supports DLMS 

implementation that enables PQDR transaction exchange; provides a web-based 

entry method to assist users who are not supported by another DLMS-compliant 

PQDR application; and provides visibility of PQDRs for research and trend 

analysis via management report/query capability. PDREP-AIS will allow users to 

query the transaction history by Report Control Number (RCN), view a composite 

of the PQDR, and provide central points of contact in the event of a transaction 

failure.

 C24.1.5.1. The PDREP-AIS PQDR application automates the Standard 

Form (SF) 368 paper form, facilitating the DoD standard transactional exchange 

described above. It brings the PQDR into an integrated transactional 

environment, supporting both direct input (under Component business rules) and 

transaction exchange originating within Component applications. PDREP-AIS 

facilitates communication and interoperability between U.S. Military, Federal 

Agencies, Contractors, and the International Logistics Control Office (ILCO) on 

behalf of the Security Assistance customer. It controls routing of web 

submissions and logistics transactions according to established business rules. 

It supports information exchange between the customer, the Inventory Control 

Point (ICP)/Integrated Material Manager (IMM), the Originating Point, Screening 

Point, Action Point, Support Point, Contractor, and other Stakeholders. It 

encompasses many transaction types between multiple parties to include, but not 

limited to, new report submission, correction/modification, cancellation, followup, requests for reconsideration (rebuttals), and PQDR investigation results 

(including interim responses, additional information requests, and resolution 

responses), in addition to the capture of report and response management 
Enclosure 3, ADC 1007E

Page 3 

statistics. Access to PDREP PQDR management reports requires submission of a 

User Access Request (UAR) to the PDREP System home page.

 C24.1.5.2. PDREP provides an automated process for tracking PQDR 

response information. Data collected will enable the DOD to identify trends, 

establish discrepancy volume and dollar values of PQDRs. This allows users to

bring management attention to problems with materiel quality and supplier 

performance information as necessary; improving the requisitioning and 

distribution process within logistics operations. This process provides an 

effective means to report, resolve, and measure deficiencies related to supply 

chain performance. 

 C24.1.5.3. The DOD requirement is that paper submission of PQDRs 

and non-DLMS compliant PQDR applications will be fully phased out with 

migration to DLMS. By exception, until electronic reporting under DLMS is 

universally available, PQDRs and associated responses may be reported via 

hard-copy SF 368, email, through customer service help lines or any other 

manner acceptable to the submitter and recipient. All manner of inter-service 

transactional reporting must meet the criteria described in this chapter. 

 C24.1.5.4. DoD Components with an established interface with PDREP, 

through DAAS for PQDR processing, will designate primary and alternate 

representatives for the Component PQDR AIS to the PDREP System 

Administrator. These representatives will be notified via email when catastrophic

transactional failures occur during PDREP business rule validation protocols. 

Catastrophic transactional failures are those that are so severe that PDREP will 

not generate a Transaction Set Purpose Code (T-44) and corresponding Reject 

Advice Code. Components will provide name, telephone, and email address to 

the PDREP System Administrator, and to the DAAS.

C24.1.5. DLMS Process Review Committee (PRC). The DoD Component 

members of the PQDR PRC will be identified on the PQDR PRC page of the 

Defense Enterprise Data Standards Office (DEDSO) website. The PQDR PRC is 

responsible for the development, expansion, improvement, maintenance, and 

administration of the systemic processing under the DLMS.

C24.1.6. Applicability. This guidance is applicable to all DOD Components 

responsible for reporting and processing PQDRs information. and requiring 

assistance from another DOD Component or AIS to process a PQDR.information.

When more than one DOD Component or AIS is involved in processing a PQDR, it 

is referred to as an inter-Service PQDR and must comply with inter-Service 

processing instructions contained in this document. It applies to all supply classes 

not specifically excluded from PQDR reporting under DLAR 4155.24/AR 702-

7/SECNAVINST 4855.21/AFI 21-115/DCMA INST 305. 

C24.2. PROCEDURES
Enclosure 3, ADC 1007E

Page 4 

C24.2.1. PQDR Overview. The oOriginator/oOriginating pPoint discovers a 

deficiency and submits the PQDR to the appropriate sScreening pPoint. The 

sScreening pPoint reviews the initial submission and determines the appropriate 

DoD Action Point (normally the item manager) to forward the report for investigation. 

The Action Point will either investigate the report or assign the report to a Support Point 

to assist with the investigation. (normally the Defense Contract Management Agency 

(DCMA)) for investigation. When required, the PQDR exhibits are moved between the 

exhibit holder and the investigating point. Throughout the investigation process, each 

point sends interim responses and other routine correspondence transactions to keep 

each interested activity and AIS updated with the current investigation status. Under 

DLMS, PQDR data is exchanged between information technology (IT) systems using 

the 842P PQDR Data Exchange transaction. Once data is shared between systems, all 

subsequent transactions must be sent to each shared system. 

C24.2.2. Detailed Requirement. When data is required to be exchanged 

across Component lines or between EBS, PDREP and JDRS, the PQDR data 

exchanged will pass through the PDREP business rule validation protocol

WebPQDR, DAAS, and be compliant with the DLMS 842P IC. The sending system is 

responsible for complying with the DLMS 842P IC format and including the applicable 

data elements. The report control number (RCN) is the key identifier for each unique 

PQDR and will be perpetuated with each transaction. PDREP The WebPQDR will 

validate each transaction for required data elements and reject incomplete or noncompliant transactions to the sending system. In addition, the WebPQDR PDREP will 

maintain a transaction history and a composite record of the ITS having received a 

prior transaction for each RCN. PDREP history tracking will be by Transaction Set 

Purpose Code data exchanges. History tracking will display both the Transaction 

Set Purpose Code as well as the description of the transaction. Additionally, 

transactions that require a specified data element accompany that transmission, 

as described in Appendix 7.27 of this DLMS Volume, will also display the data 

element name, code and code description. PDREP WebPQDR will route a copy of 

all subsequent transactions to the ITS.

C24.2.3.. PQDR Movement Transactions. The DLMS 842P moves the PQDR 

between the different investigating points. PQDR Inter-Service data exchange is 

required IAW DLMS 842P. Data required in each transaction is defined in the 

DLMS 842P IC. All transactions will have the ability to provide attachments as 

needed. 

 C24.5.1.1. Originator Forwards to Screening Point (Transaction Set Purpose 

Code 00). Used when the originator forwards to screening point in another system or 

when originator and screening point do not exist within the same system. Note: EBS is 

not permitted to originate PQDRs.

 C24.5.1.2. Forward from Screening Point to Action Point (Transaction Set 

Purpose Code FA). Used when the screening point forwards a PQDR to an action point 

and the action point does not exist within the same system. 
Enclosure 3, ADC 1007E

Page 5 

 C24.5.1.3. Forward from Action Point to Support Point (Transaction Set 

Purpose Code 4S). Used when the action point forwards a PQDR to a support point 

and the support point does not exist within the same system. 

 C24.5.1.4. Final Reply from Support Point To Action Point (Transaction Set 

Purpose Code 11). 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. 

 C24.5.1.5. Final Reply (Completion Notice) from Action Point to Screening 

Point (Transaction Set Purpose Code CN). 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. 

 C24.5.1.6. Not Processed (Misdirected) (Transaction Set Purpose Code 12)

Use to indicate that a PQDR was received by the incorrect screening, action, or support 

point and could not be processed. Return misdirected PQDRs to the previous 

processing point.

 C24.5.1.7. Retraction (Transaction Set Purpose Code 03). Used by 

screening and action points to change ownership of a PQDR action back to the previous 

processing point or location.

 C24.5.1.8. Reply Rebuttal (Transaction Set Purpose Code RR). Used to 

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

C24.5.2. Exhibit Movement Transactions. PQDR exhibit movement transactions 

provide status and control over exhibit movements. All PQDR processing points can 

use exhibit movement transactions. Use of this DLMS 842P for exhibit movement 

supplements the use of standard logistics transactions for receipt and shipment status. 

When information copies of the receipt and shipment status are provided to the PDREPAIS, they will be used to update the exhibit movement and disseminated as appropriate.

 C24.5.2.1. Exhibit Request (Transaction Set Purpose Code 13). Used to 

request the exhibit and provide shipping information. Refer to paragraph C11.20 for 

specific guidance for directed deficient materiel returns including document number 

assignment and associated transactions for prepositioned materiel receipt and materiel 

returns shipment status.

 C24.5.2.2. Exhibit Shipped Notification (Transaction Set Purpose Code 14). 

Used to provide exhibit shipment information to the requestor.

 C24.5.2.3. Exhibit Receipt (Transaction Set Purpose Code ER). Used to 

document exhibit receipt. Note: If sent as a late exhibit receipt, PQDR is reassigned to 

the sender’s level. 

 C24.5.2.4. Exhibit Tracer (Not Found) (Transaction Set Purpose Code 10). 

Used by exhibit requestor to request status or follow up on an exhibit request. 
Enclosure 3, ADC 1007E

Page 6 

 C24.5.2.5. Materiel Disposition (Transaction Set Purpose Code MD). Used 

to provide final materiel disposition instructions. Used by the support or action point 

after the investigation is complete. 

 C24.5.2.6. Exhibit Disposition Confirmation (Transaction Set Purpose Code 

ED) Used by the current exhibit holder to confirm compliance with materiel disposition 

instructions. 

C24.5.3. General Information Transactions. The PQDR general information 

transactions provide information or status regarding the PQDR without changing 

ownership.

 C24.5.3.1. Acknowledge/Status (Transaction Set Purpose Code 08). Used 

to acknowledge that a PQDR was received and provide current status to the sender.

 C24.5.3.2. Interim Reply (Transaction Set Purpose Code 25). Used by 

support or action point to provide investigation status of the PQDR to the previous 

owner.

 C24.5.3.3. General Correspondence (Transaction Set Purpose Code CO). 

Used to transmit general correspondence information concerning the PQDR status from 

the sender to the receiver, or to send corrections with an explanation of changes.

 C24.5.3.4. Follow-up for Status (Transaction Set Purpose Code 45). Used to 

request status when a processing point has not provided investigation status via interim 

reply or the like. 

 C24.5.3.5. Cancellation (Transaction Set Purpose Code 01). Use when 

PQDR is cancelled in one system and cancelation needs to be propagated to other 

systems. Note: Only screening points may cancel a PQDR.

 C24.5.3.6. Delegate to Alternate Support Point (Transaction Set Purpose 

Code DA). Used to delegate to another support point by the responsible support point 

without changing the responsible support point.

 C24.5.3.7. Redirect/Transfer (Transaction Set Purpose Code 47). Used to 

redirect a PQDR to another screening point, action point, or support point within the 

component.

 C24.5.3.8. Reopen (Transaction Set Purpose Code RO). Used when a 

PQDR is reopened by the system sending the transaction and needs to be reopened in 

receiving system. The screening point will send to notify other systems that a PQDR 

has been reopened. The other touch points (originator, action, or support point) will 

send when requesting the PQDR to be reopened.

 C24.5.3.9. Update (Transaction Set Purpose Code SU). Used to send an 

update to correct or append specific data fields in another IT system.
Enclosure 3, ADC 1007E

Page 7 

 C24.5.3.10. Forward to Contractor (Transaction Set Purpose Code FC). 

Used when support point sends PQDR investigation request to a contractor.

 C24.5.3.11. Information Copy (Transaction Set Purpose Code 22). Used to 

send information copy of PQDR to another system. Used for dissemination to nonaction 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.

C24.5.4. System Transactions. System transactions are used to confirm data 

receipt and communicate transaction failures to the sending system. 

 C24.5.4.1. Transaction Rejection (Transaction Set Purpose Code 44). Used 

when the PQDR II 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 data 

requirements (i.e. duplicate RCN). This transaction is system generated. End users 

should use Transaction Set Purpose Code 12, Not Processed (Misdirected), to return 

with comment.

 C24.5.4.2. Confirmation of Transaction Receipt (Transaction Set Purpose 

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

system. 

 C24.2.3.1. The procedure by which PQDR processing points may 

update any data element and at what point in the PQDR process is also defined in 

the DLMS 842P IC. For inter-Service PQDRs, communication both to and from 

Originators must only be sent to the Screening Point for evaluation regardless of 

transaction code. PQDR processing points can only directly communicate with 

the processing point immediately preceding or following them. Additional 

business rules can be found in Appendix 7.27 of this volume. 

C24.3.5. Exhibit Tracking. Systemic update of the PDREP-AIS for exhibit tracking 

is provided as a by-product of standard logistics transactions. When received at a 

distribution center, the receipt transaction will identify the PQDR RCN and an 

information copy of the receipt will be provided. Similarly, when a DLMS shipment 

status transaction is prepared for the shipment of an exhibit, the shipment status will 

perpetuate the PQDR RCN from the release order.

C24.3.5.1 When the Support Point returns the PQDR back to 

the Action Point because the exhibit(s) was not received, control of the PQDR 

transfers back to the Action Point. If the exhibit(s) arrives at the contractors 

facility after the PQDR was returned by Support Point to the Action Point, and the 

PQDR is currently located at the Action Point, the Action Point should rebut (TRR) the PQDR back to the Support Point for processing; if the PQDR is located at 

the Screening Point or was closed, the Screening Point reopens (T-RO), if 

necessary, and rebuts (T-RR) the PQDR to the Action Point level. 

C24.4. PQDR Transaction Timeline. The PQDR transactional timeline, or the 
Enclosure 3, ADC 1007E

Page 8 

systemic method of moving a PQDR between process points, will be conducted 

in accordance with Enclosure 2 of ADC 1007E. Information systems will only 

allow transactions within the information system when the PQDR has reached 

that point in the PQDR Timeline. Only the transactions at the point in the timeline 

will be permitted. All others will be systemically rejected by PDREP-AIS. 

 C24.4.1. Services/Agency information systems may perform additional 

tasks within their information systems as long as they do not interfere with the 

DoD processing of inter-Service PQDRs. Data elements may only be updated by 

personnel processing PQDRs at the point in the PQDR Timeline process flow IAW 

DLMS 842P IC. 

 C24.4.2. DLA will not reopen a PQDR investigation after 180 days of 

sending a Completion Notification (T- CN) Final Reply with no response (action) 

by the Screening Point. On day 181 or later, a new PQDR (RCN) would need to be 

issued referencing the old RCN, if further action by the Action Point or Support 

Point is required. 

 C24.4.3. When it is determined that credit should be issued after the 

PQDR has been closed by all parties, the Originator or Screening Point must 

submit a new PQDR and reference the original PQDR RCN.

C24.5. Product Quality Deficiency Investigative Closing Requirements. 

C24.5.1. Input by either the PQDR Action Point or Support Point, the 

information to be entered in each data element is dependent upon the type and 

cause of the deficiency, and the information requested may not be appropriate in 

all cases. The information requested is typical when the cause of the deficiency is 

due to non-conformance with contract requirements. The investigative closing 

codes provide specific details about the findings of the investigation. Together 

these codes make up seven segments of investigation related data forming a 

nine-character code referred to as the Summary Code. All segments of the 

investigative closing codes must be completed prior to the Action Point 

submitting a Final Reply. Failure to complete each of these data elements by the 

Action Point will result in the transaction being rejected. 

C24.5.1.1. The seven segments of closing data include (1) defect 

responsibility, (2) severity of the defect, (3) broad classification of the cause, (4) 

detailed cause of the defect, (5) preventative action taken because of the defect, 

(6) corrective action taken for the defective materiel, and (7) disposition of the 

deficient materiel. A complete list of investigative closing codes can be found in 

Appendix 7.27 of this this Volume. 
Enclosure 4, ADC 1007E

Page 1

Enclosure 4

Revised DLM 4000.25, Volume 2, Appendix 7.27, Product Quality Deficiency Report 

Relevant Data Elements

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

AP7.27 APPENDIX 7.27

PRODUCT QUALITY DEFICIENCY REPORT (PQDR) 

RELEVANT DATA ELEMENTS

AP7.27. GENERAL. This appendix provides a consolidated reference resource for 

transaction sets, data elements and their associated code sets applicable to Product 

Quality Deficiency Report (PQDR) submissions, subsequent communication between 

trading partners, and responses. These transaction sets and data elements are 

applicable in all DoD PQDR applications under the DLMS. The data elements listed 

below are included in this appendix. Within the context of PQDR procedures, these

transaction sets and data elements may be recognized by abbreviated names as 

indicated. Refer to Product Quality Deficiency Report (PQDR) Program (DLAR 

4155.24/AR 702-7/SECNAVINST 4855.5B/AFR 74-61) the DLMS Dictionary (Logistics 

Data Resources Management System (LOGDRMS) for additional PQDR data 

definitions and codes

• Product Quality Deficiency Report (PQDR) Status Code. 

Also referred to as Status Code.

• Product Quality Deficiency Report (PQDR) Rebuttal/Controvert Code. 

Also referred to as Rebuttal Code.

• Product Quality Deficiency Report (PQDR) Credit Code. 

Also referred to as Credit Code.

• Product Quality Deficiency Report (PQDR) Exhibit Distribution Status Code.

Also referred to as Exhibit Accounted For/Received Code.

• Operating Time at Failure.

• Time Since Installation.

• Time Since New/Overhaul.

AP7.27.1. PQDR Transaction Set Purpose Codes. 

 AP7.27.1.1. General Opening, Closing and Related Codes. These codes 

process transactions that include but are not limited to; open, close, transfer, and 

return PQDRs to other PQDR processing points.

 AP7.27.1.1.1. Original (Originator Forwards to Screening Point)

(Transaction Set Purpose Code 00). Used when the Originator forwards to the 

Screening Point. Originators are required to execute this transaction set within 
Enclosure 4, ADC 1007E

Page 2 

24 hours of discovery for Category I and three calendar days of discovery for 

Category II PQDRs. 

 AP7.27.1.1.2. Forward to Action (Forward from Screening Point to 

Action Point) (Transaction Set Purpose Code FA). Used when the Screening Point 

forwards a PQDR to an Action Point and the Action Point does not exist within 

the same AIS. 

 AP7.27.1.1.3. Forward to Support (Forward from Action Point to 

Support Point) (Transaction Set Purpose Code FS). Used when the Action Point 

forwards a PQDR to a Support Point and the Support Point does not exist within 

the same system. 

 AP7.27.1.1.4. Response (Final Reply from Support Point to Action 

Point) (Transaction Set Purpose Code 11). 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. 

 AP7.27.1.1.5. Completion Notification (Final Reply) from Action 

Point to Screening Point (Transaction Set Purpose Code CN). 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. 

 AP7.27.1.1.6. Not Processed (Misdirected) (Transaction Set 

Purpose Code 12). Use to indicate that a PQDR was received by an incorrect 

Screening, Action, or Support Point and could not be processed. The transaction 

returns the misdirected PQDR to the previous processing point.

 AP7.27.1.1.7. Delete (Retraction) (Transaction Set Purpose Code 

03). Used by Screening Points and Action Points to request ownership of a 

PQDR be transferred back to them. 

 AP7.27.1.1.7.1. Where system capabilities exist within a 

single PQDR processing AIS, the AIS may be programmed to systemically move 

the PQDR back to the Screening Point or Action Point. Use of (T-03) will not be 

programmed to systemically transfer a PQDR back to the Screening Point or 

Action Point from different AIS's.

 AP7.27.1.1.8. Rebuttal (Transaction Set Purpose Code RR). Used 

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

 AP7.27.1.1.9. Completion (Closure)(Transaction Set Purpose Code 

53). Used by Screening Point to close out and notify other PQDR processing 

points of PQDR process completion for a given PQDR. Note: Only the Screening 

Point may perform this transaction.

 AP7.27.1.2. Exhibit Movement Transactions. PQDR exhibit movement 

transactions provide status and control over exhibit movements. All PQDR 
Enclosure 4, ADC 1007E

Page 3 

processing points can use exhibit movement transactions. Use of exhibit related 

transactions may not be used prior to Action Point acknowledgement of the 

PQDR. Additionally, exhibit related transaction workflows must start with either 

an Action Point exhibit request or exhibit disposition. The only exception to this 

rule will be when the PQDR is at the Support Point level after acknowledgment, 

where either the Action Point or Support Point may open the exhibit related 

workflows by sending an exhibit request transaction set. Use of this DLMS 842P 

for exhibit movement supplements the use of standard logistics transactions for 

receipt and shipment status. When information copies of the receipt and 

shipment status are provided to the PDREP-AIS, they will be used to update the 

exhibit movement and disseminated as appropriate.

 AP7.27.1.2.1. Exhibit Request (Transaction Set Purpose Code 13) 

Used to request the exhibit and provide shipping information.

 AP7.27.1.2.1.1. When an exhibit is required to complete a 

PQD investigation, this transaction will open the ability to send exhibit shipped 

(T-14) and exhibit status update request (T-10) transactions. If the T-14 or T-10 

are provided prior to T-13, it will result in a transaction rejection. 

 AP7.27.1.2.1.2. With exception to when the PQDR is at the 

Support Point level after acknowledgement, where either the Action Point or 

Support Point may transmit the request, initial use of this transaction at any other 

level will be restricted to the Action Point. Action point use of this code will open 

the ability for the Screening Point to send the exhibit request transaction to 

Originator. 

 AP7.27.1.2.2. Advance Notification (Exhibit Shipped Notification) 

(Transaction Set Purpose Code 14). Used to provide exhibit shipment 

information to the requestor.

 AP7.27.1.2.2.1. When an exhibit is requested, the exhibit 

shipped transaction will open the ability to transmit the exhibit receipt (ER) 

transaction.

 AP7.27.1.2.2.2. When the PQDR is at the Action Point level 

after acknowledgement, use of this transaction will be limited to the Originator 

and Screening Point.

 AP7.27.1.2.2.3. If the PQDR has been assigned to a Support 

Point, and is at the Support Point after acknowledgement level, the Originator, 

Screening Point and Action Point may transmit the exhibit shipped transaction 

set.

 AP7.27.1.2.2.4. If the PQDR has been assigned to a Support 

Point, and the PQDR has been moved to the Action Point from Support Point 

level, all PQDR processing points may transmit this transaction. 
Enclosure 4, ADC 1007E

Page 4 

 AP7.27.1.2.3. Exhibit Receipt (Transaction Set Purpose Code ER). 

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

acknowledgment 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. Note: If sent as a late 

exhibit receipt, PQDR is reassigned to the sender’s level. 

 AP7.27.1.2.4. Not Found Exhibit Tracer (Transaction Set Purpose 

Code 10). Used by exhibit requestor to request status or follow up on an exhibit 

request. 

 AP7.27.1.2.5. Material Disposition (Final Materiel Disposition) 

(Transaction Set Purpose Code MD). Material Disposition must be provided prior 

to PQDR closure. 

 AP7.27.1.2.5.1. Used by the Screening Point, Action Point and 

Support Point after the investigation is complete to provide final materiel 

disposition instructions. If a Support Point has been assigned and the PQDR is 

at the Support Point after acknowledgment level, only the Support Point may use 

this transaction at this level.

 AP7.27.1.2.6. Exhibit Disposition Confirmation) (Transaction Set 

Purpose Code ED). Used by the current exhibit holder to confirm compliance 

with materiel disposition instructions. 

 AP7.27.1.2.6.1. Use of this transaction may be used any time 

after Material Disposition (T-MD) has been provided and may continue to be used 

after the Screening Point closes the report (T-53). This allows for reports to 

continue to be updated in situations such as long-term overhaul corrective 

actions by vendors that will take place over months or years, while not 

unnecessarily keeping the report open.

 AP7.27.1.3. General Information Transactions. The PQDR general 

information transactions provide information or status regarding the PQDR 

without changing ownership.

 AP7.27.1.3.1. Status (Acknowledge)Transaction Set Purpose Code 

08). Used to acknowledge that a PQDR was received and provide current status to 

the previous point. Screening Points, Action Points and Support Points are all 

required to provide this transaction set within 24 hours for Category I and three 

business days for Category II PQDRs.

 AP7.27.1.3.2. Incremental (Interim Reply) (Transaction Set Purpose 

Code 25). Used by Support or Action Point to provide investigation status of the 

PQDR to the previous owner.

 AP7.27.1.3.3. Corrected (General Correspondence) (Transaction 

Set Purpose Code CO). Used to transmit a general correspondence information 
Enclosure 4, ADC 1007E

Page 5 

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

transaction will also be used to inform other PQDR processing points when Major 

Data Element changes are required after they have acknowledged receipt of the

PQDR.

 AP7.27.1.3.4. Follow-up (Follow-up for Status) (Transaction Set 

Purpose Code 45). A systemically generated transaction used to request a status 

when a processing point has not provided investigation status via interim reply or 

the like. 

 AP7.27.1.3.5. Cancellation (Transaction Set Purpose Code 01). 

Used when a PQDR is cancelled. 

 AP7.27.1.3.5.1. Cancellations may take place at the request of 

the Screening Point when major data element changes are required to a PQDR. 

Major data element changes include the RCN, NIIN/NSN, contract number and 

CAGE. These data elements have the ability to change the scope and responsible 

parties associated with the investigation. Note: Only Screening Points may 

cancel a PQDR. and cancelled PQDRs cannot be reopened.

 AP7.27.1.3.6. Delegate to Alternate (Delegate to Alternate Support 

Point) (Transaction Set Purpose Code DA). Used to document Action Point or 

responsible Support Point delegation to an entity that does not support PQDR 

investigations through a PQDR AIS, such as Engineering Support Activities 

(ESA). 

 AP7.27.1.3.7. Transaction Set Purpose Code DA. may be used by 

either the Action Point or responsible Support Point without systemically 

changing the initial responsible Support Point. Use of this transaction set in 

conjunction with the systemic assignment of a traditional Support Point, such as 

DCMA, will require PDREP-AIS to provide an information copy(T-22) to the 

Support Point assigned at the Support Point level for the PQDR.

 AP7.27.1.3.8. Transfer (Redirect/Transfer) (Transaction Set 

Purpose Code 47). 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.

 AP7.27.1.3.9. Reopen (Transaction Set Purpose Code RO). 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.
Enclosure 4, ADC 1007E

Page 6 

 AP7.27.1.3.10. Status Update (Transaction Set Purpose Code SU). 

Used to send an update to correct or append specific data fields in another AIS. 

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

Support Point for minor changes. Only the Screening Point may use the SU 

transaction or make major data element changes (RCN, NIIN/NSN, Contract

Number or CAGE Code). In order for the Screening Point to make a major data 

element change using the SU transaction, the PQDR must be at the Screening 

Point level. The use of the SU transaction other than specified will result in a (T44).

 AP7.27.1.3.11. Notice of Defect (Transaction Set Purpose Code 

FC). Used when Support Point sends PQDR investigation request to a contractor.

 AP7.27.1.3.12. Information Copy (Transaction Set Purpose Code 

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

 AP7.27.1.4. System Transactions. System transactions are used to 

confirm data receipt and communicate transaction failures to the sending system. 

 AP7.27.1.4.1. Rejection (Transaction Rejection) (Transaction Set 

Purpose Code 44). Used when the 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 data requirements (i.e., duplicate RCN). This transaction is 

both system generated, and user defined. 

 AP7.27.1.4.2. Confirmation (Confirmation of Transaction Receipt) 

(Transaction Set Purpose Code 06). Used by an automated IT system to confirm 

transaction receipt from another system.

AP7.27.2. PRODUCT QUALITY DEFICIENCY REPORT SPECIFIC DATA

ELEMENTS. 

AP7.27.2.1. Product Quality Deficiency Report (PQDR) Status Code. 

 AP7.27.1.1. Definition. A two-character alpha-numeric compound code 

consisting of the PQDR STATE (active or closed) in the first position, and either the 

active PQDR's LAST KEY EVENT CODE or the closed PQDR's CLOSURE REMARK 

CODE in the second position. 

 AP7.27.1.1.1. PQDR STATE: A single character alphabetic code 

indicating whether the status of a PQDR is "Active" (permitted value = A) or "Closed" 

(permitted value = C) 
Enclosure 4, ADC 1007E

Page 7 

 AP7.27.1.1.2. LAST KEY EVENT CODE: A single character alphanumeric code used to indicate the last key event accomplished in processing an active 

PQDR. Used with PQDR STATE = A.

 AP7.27.1.1.3. CLOSURE REMARK CODE = A code used with (T-53) 

to indicate the circumstances under which a PQDR was closed. Used with PQDR 

STATE = C. 

 AP7.27.1.2. Usage. Facilitates workflow efficiencies for functional users, and 

program management metrics for oversight and analyses of process performance and 

production issues.

 AP7.27.1.3. DLMS 842P Reference: 2/LQ01/1050 Code PQS Product 

Quality Deficiency Reporting Status Code. 

 AP7.27.1.4. PQDR Status Codes are listed in Table AP7.27.T1: 

Table AP7.27.T1. PQDR Status Codes

Code Literal

<Blank> Draft Record

A1 Child PQDR

A2 Screening Pt Request For Information

A3 Action Point Request For Information

A4 Support Point Request For Information Request for Support Point 

Investigation

A8 Awaiting Verification Of Corrective Action

A9 Stock Screened PQDR

AA Request for Additional Information

AB Under Engineering Review

AC Investigation Requested Of Action Pt

AD Action Point Accepted PQDR for Investigation

AE Exhibit Requested

AF Exhibit Shipped

AG Case/PQDR Reopened

AH PQDR Rebutted Back To Support Pt

AI Information Only/Trending Purposes

AJ Awaiting Credit Recommendation Or Credit Reversal
Enclosure 4, ADC 1007E

Page 8 

Table AP7.27.T1. PQDR Status Codes

Code Literal

AK Awaiting Other Closing Delay

AM Awaiting Final Materiel Disposition Instructions

AN Awaiting Funds

AO Record Returned To Originator

AP Action Pt Inv Report Submitted

AQ Investigation Requested Of Support Pt

AR Awaiting Reqs Approval/ECP Request for Additional Information

AU Other

CA Invalid PQDR

CC Nonresponsive Investigation

CD Defect Previously Investigated

CE Enhancement

CF Exhibit Unavailable

CG Investigation Completed Without Exhibit (Not Requested)

CH No Investigation - Exhibit Damaged

CI Information Only/Reliability Data

CJ Investigation With Damaged Exhibit

CK Contractor Unwilling To Investigate

CN Manufacturing Sources Or Technical Data No Longer Available

CO Child PQDR

CP Investigation Completed With Exhibit

CR Stock Screened PQDR

CS No Closing Data Received From External System

CT Missing Necessary Information

CU Investigation Could Not Validate Defect

CV Corrected And Verified

CW Isolated Incident/Acceptable Risk

CX Cancelled Record

CY Closed Under Warranty Provisions
Enclosure 4, ADC 1007E

Page 9 

Table AP7.27.T1. PQDR Status Codes

Code Literal

CZ Administrative Closing

AP7.27.2. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) REBUTTAL/ 

CONTROVERT CODE

 AP7.27.2.1. Definition. A 2-character alpha compound code, consisting of 

the rebuttal “Point Of Origin” (Screening Point, or Action Point) in the first position, and 

the rebuttal “Reason” in the second position.

 AP7.27.2.1.1. Point Of Origin: A single character alphabetic code 

indicating who generated the rebuttal: Action Point (permitted value = A) or Screening 

Point (permitted value = S). Originator’s rebuttal generates an official correspondence 

to the screening point for review, but it does not open a closed record. Screening point 

may accept request to reopen for originator and reopen PQDR for further investigation.

 AP7.27.2.1.2. Reason: A single character alphabetic code indicating the 

reason for the rebuttal being generated. 

 AP7.27.2.2. Usage. Provides mechanism to facilitate program oversight.

 AP7.27.2.3. DLMS 842P Reference: 2/LQ01/1050 Code CW.

 AP7.27.2.4. PQDR Rebuttal/Controvert Reason Codes are listed in 

Table AP7.27.T2:

Table AP7.27.T2. PQDR Rebuttal/Controvert Reason Codes

Code Literal

C Root Cause Not Addressed

D Responsible Party Not Addressed

E Corrective Action Not Addressed

E Corrective Action Not Addressed

F Disposition Not Addressed

G Credit Not Addressed

H Preventive Action Not Addressed

I Incomplete Or Incorrect PQDR Information On Closing Letter

M Multiple Reasons For Rebuttal
Enclosure 4, ADC 1007E

Page 10

Table AP7.27.T2. PQDR Rebuttal/Controvert Reason Codes

Code Literal

N Disagree With Closing Response/Findings

O Other - Not Covered By A Defined Code

R Repeat Rebuttal

S Response Truncated Or Not Submitted In Proper Format

T Case Reopened Due To Delayed Receipt Of Exhibit Or Data

U Update Or Change Requested

V Response Needs Clarification

W Response Is For Wrong PQDR

AP7.27.3. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) CREDIT CODE

 AP7.27.3.1. Definition. A single character alpha code used to describe 

whether credit or other form of resolution is authorized. 

 AP7.27.3.2. Usage. Used by Screening/Action point to provide the originator 

with current status of financial liability on reported materiel. Secondary usage is to 

support management metrics. This code appears in the 10th position of the PQDR 

Summary Code.

 AP7.27.3.3. DLMS 842P Reference: 10th position of PQDR Summary Code 

atDLMS 842P Reference: 2/LQ01/1050/P2C – PQDR Credit Code (new data 

element). 

 AP7.27.3.4. PQDR Credit Codes are listed in Table AP7.27.T3

Table AP7.27.T3. PQDR Credit Codes

Code Literal

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
Enclosure 4, ADC 1007E

Page 11

AP7.27.4. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT 

DISTRIBUTION STATUS CODE1 

AP7.27.4.1. Definition. Code indicates status/control of exhibit during the 

transportation process. Transportation process starts when the originator passes 

materiel to shipper and ends when consignee takes control of the materiel.

 AP7.27.4.2. Usage. To ensure proper and effective processing in order to 

maintain valid PQDR resolution time frames

 AP7.27.4.3. DLMS 842P Reference: 2/REF01/0700 Code KC.

AP7.27.4.4. PQDR Exhibit Distribution Status Codes are listed in Table AP7.27.T4

Table AP7.27.T4. PQDR Exhibit Distribution Status Codes

Code Literal

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

2 In staging, awaiting onward transportation

3 Received by Consignee 

AP7.27.5. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT 

CURRENT DISPOSITION CODE

 AP7.27.5.1. Definition. A single character alpha code, used to identify the 

status of exhibit materiel from originator point of view on initial PQDR Submission.

 AP7.27.5.2. Usage. Provide mechanism to identify exhibit initial locations. 

This code appears in the 13th position of the PQDR Summary Code.

 AP7.27.5.3. DLMS 842P Reference: 13th position of PQDR Summary Code 

at 842P Reference: 2/LQ01/1050/CDC – Current Disposition Code (new data 

element). 

1

 Refer to ADC 1007C. 
Enclosure 4, ADC 1007E

Page 12

 AP7.27.5.4. PQDR Exhibit Current Disposition Codes are listed in Table 

AP7.27.T5:

Table AP7.27.T5. PQDR Exhibit Current Disposition Codes

Code Literal

H Holding Exhibit

D Disposed or Destroyed

R Repaired

O Other 

AP7.27.6. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT

CURRENT DISPOSITION DELIVERY REQUIREMENT CODE

 AP7.27.6.1. Definition. A single character alpha code, used to identify the 

status of exhibit materiel from the action or support point of view. 

 AP7.27.6.2. Usage. Use to identify the Exhibit Delivery Requirement Code 

from the Action or Support Point. This provides verification that the exhibit is required 

and should be sent or held by originator. 

 AP7.27.6.3. DLMS 842P Reference: 2/LQ01/1050 Code PQR Product

Quality Exhibit Delivery Requirement Code.

 AP7.27.6.4. PQDR Exhibit Delivery Requirement Codes are listed in Table 

AP7.27.T6:

Table AP7.27.T6. PQDR Exhibit Delivery Requirement Code

Code Literal

H Hold Exhibit

N Exhibit Not Required

Q Exhibit Required (but not Requested)

R Exhibit Requested

AP7.27.7. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT

CURRENT DISPOSITION OPERATING TIME AT FAILURE CODE AP
Enclosure 4, ADC 1007E

Page 13

 AP7.27.7.1. Definition. A two character alphanumeric code, used for 

measure of time or events as listed in Table AP7.27.T7 for data elements: Operating 

Time at Failure, Time Since New/Overhaul, and Time Since Installation. 

 AP7.27.7.2. Usage. Use to identify the quantity of time a unit entered 

operational service as a new or overhauled item to time the deficiency was discovered. 

Operating Time Codes are mapped as Unit of Measure Codes associated with the 

applicable quantified value for Operating Time at Failure, Time Since New/Overhaul, or 

Time Since Installation.

 AP7.27.7.3. DLMS 842P Reference: 2/QTY03-01/2700. 

 AP7.27.7.4. Operating Time Codes are listed in Table AP7.27.T7:

Table AP7.27.T7. Operating Time Codes2

Code Literal Notes

03 Seconds

14 Catapult Shots Used to document the number of launches an 

aircraft has been launched, i.e. aircraft catapult 

systems and/or unmanned air vehicles.

7A Landings Used to document the number of landings an 

aircraft has completed.

7C Flight Hours Used to document the amount of time in hours 

that an aircraft/equipment has been flying.

1N Starts

B7 Cycles 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 Arrestments Used to document the number of times an aircraft 

has engaged arresting gear to stop forward 

momentum of a routine or emergency landing or 

an aborted takeoff.

2 Codes 7A and 7C are established Local Codes. A data maintenance action has been submitted for 

establishment of “7A – Landings” and “7C – Flight Hours” in a future X12 Version. Refer to ADC 

1007C. 
Enclosure 4, ADC 1007E

Page 14

Table AP7.27.T7. Operating Time Codes2

Code Literal Notes

MJ Minutes

MO Months

RH Running or Operating 

Hours

RO Rounds Fired

T8 Time Since 

New/Overhaul

New X12 data element

T9 Time Since 

Installation

New X12 data element

YR Year

UN Unit, other than listed 

above

AP7.27.8. Product Quality Deficiency Report (PQDR) Reject Advice Code.

 AP7.27.8.1. Definition. A two-position alpha code used with transaction 

set purpose code 44, identifying the reason a transaction was rejected. 

 AP7.27.8.2. Usage. Informs the originator of a transaction, the reason 

for rejection, and indicates return of the transaction for correction and 

resubmission.

 AP7.27.8.3. DLMS 842P Reference: 2/LQ01/1050/RAC PQRD Reject 

Advice Code. (new data element)

 AP7.27.8.4. PQDR Reject Advice Codes are listed in Table AP7.27.T8:

Table AP7.27.T8. Reject Advice Code.

Non-Security Assistance User Defined Reject Advice Codes

Code Literal

701 PQDR rejected. Incorrect Screening Point assigned

702 PQDR rejected. Incorrect Action Point assigned – different IMM 

exists 
Enclosure 4, ADC 1007E

Page 15

703 PQDR Rejected. Report does not meet the requirements of a 

PQDR – invalid report.

704 PQDR Rejected. Acceptable substitute issued for materiel

requisitioned.

705 PQDR rejected. Material shipped prior to cancellation request.

706 PQDR rejected. Report identifies a supply discrepancy. Resubmit 

as a SDR.

707 PQDR rejected. Requisition document is not from Action Point 

Source of Supply.

Security Assistance User Defined Reject Advice Codes

Code Literal

80_ (Reserved for Future Use)

Systemic Reject Advice Codes

Code Literal

901 Transaction rejected. Discrepancy report canceled.

902 Transaction rejected. Record is currently open and cannot be 

reopened until closed.

903 Transaction rejected. Missing or invalid requisition document 

number (or document number/suffix).

904 Transaction rejected. Missing or invalid report control number.

905 Transaction rejected. Duplicate report control number.

906 Transaction rejected. Missing or invalid discrepant quantity.

907 Transaction rejected. Missing or invalid point of contact name.

908 Transaction rejected. Missing or invalid point of contact phone 

number/email.

909 Transaction rejected. Missing or invalid transaction date.
Enclosure 4, ADC 1007E

Page 16

910 Transaction rejected. Missing or invalid deficiency discovery 

date.

911 Transaction rejected. Narrative missing.

912 Transaction rejected. No record found.

913 Transaction rejected. Missing or invalid materiel identification.

914 Transaction rejected. Missing materiel nomenclature.

915 Transaction rejected. Missing PQDR category.

916 Transaction rejected. Missing, invalid, or unauthorized use of 

DoDAAC or MAPAC

917 Transaction rejected. Missing or invalid transaction set purpose 

code. 

918 Transaction rejected. Missing action requested.

920 Transaction rejected. Exhibit shipment information provided prior 

to exhibit request.

921 Transaction rejected. Exhibit status information provided prior to 

exhibit request.

922 Transaction rejected. Exhibit receipt information provided prior to 

exhibit request.

923 Transaction rejected. Exhibit receipt information received prior to 

exhibit shipped transaction.

924 Transaction rejected. Exhibit shipping information missing 

exhibit shipped date.

925 Transaction rejected. Exhibit shipping information missing 

exhibit shipped quantity.

926 Transaction rejected. Exhibit shipping information missing 

exhibit shipped to address.

927 Transaction rejected. Exhibit shipping information missing 

exhibit shipped tracking number.

928 Transaction rejected. Exhibit receipt information missing exhibit 

receipt date.
Enclosure 4, ADC 1007E

Page 17

929 Transaction rejected. Exhibit receipt information missing exhibit 

receipt quantity.

930 Transaction rejected. Exhibit Disposition (ED) transaction 

provided prior to Material Disposition (MD) transaction.

931 Transaction rejected. Invalid special character used.

932 Transaction rejected. Time to failure missing measurement code.

933 Transaction rejected. Final reply missing defect responsibility.

934 Transaction rejected. Final reply missing severity of the defect.

935 Transaction rejected. Final reply missing broad cause.

936 Transaction rejected. Final reply missing detailed cause.

937 Transaction rejected. Final reply missing preventative action.

938 Transaction rejected. Final reply missing corrective action.

939 Transaction rejected. Final reply missing final exhibit disposition.

940 Transaction rejected. Transaction 03 RR missing Retraction 

Reason Code.

941 Transaction rejected. Transaction CO missing General 

Correspondence Purpose Code.

942 Transaction rejected. Transaction 25 missing Interim Reply Code.

943 Transaction rejected. Transaction 01 missing Cancellation Code.

944 Transaction rejected. Transaction 00 missing Discovery Defect 

Codes.

945 Transaction rejected. Transaction 00 missing FMS case number.

946 Transaction rejected. Transaction 03 submitting after PQDR 

acknowledgement.

947 Transaction Rejected. T-SU submitted for major data element 

change when not at Screening Point.
Enclosure 4, ADC 1007E

Page 18

AP7.27.9. Product Quality Deficiency Report (PQDR) Retract Reason Code.

 AP7.27.9.1. Definition. A two-position alpha numeric code used with 

transaction set purpose code 03 to describe the reason for requesting the PQDR 

be returned to the previous level. 

 AP7.27.9.2. Usage. Request a PQDR be returned back to the previous 

level due to incorrect routing or to make major data element changes to the 

PQDR that could result in changes to the Screening Point, Action Point or 

Support Point. . 

 AP7.27.9.3. DLMS 842P Reference: 2/LQ01/1050/PQC PQDR Retract 

Reason Code (new data element)

Table AP7.27.T9. PQDR Retraction Reason Code

Code Literal

A1 Incorrect Screening Point Assigned

A2 Incorrect Action Point Assigned

A3 Incorrect Support Point Assigned

B1 Major Data Element Correction Required

AP7.27.10. Product Quality Deficiency Report (PQDR) General 

Correspondence Purpose Code.

 AP7.27.10.1. Definition. A two-position alpha code used with 

transaction set purpose code CO, informing the purpose for the general 

correspondence. 

 AP7.27.10.2. Usage. Informs the recipient of the main purpose of the 

communication, i.e., gain in discrepant quantity, decrease in discrepant quantity, 

point of contact change, etc.

 AP7.27.10.4. DLMS 842P Reference: 2/LQ01/1050/GCP PQDR General 

Correspondence Purpose Code (new data element)

Table AP7.27.T10. PQDR General Correspondence Purpose Code

Code Literal

GN Gain or increase in quantity reported

LS Loss or decrease in quantity reported

CC Change in point of contact information
Enclosure 4, ADC 1007E

Page 19

Table AP7.27.T10. PQDR General Correspondence Purpose Code

Code Literal

IP Requested information provided

MI Minor Data Element Change Required

MJ Major Data Element Change Required

MR Follow Up Requested Due to Late/Missed Interim Reply

OT Other

 

AP7.27.11. Product Quality Deficiency Report (PQDR) Interim Reply Codes.

 AP7.27.11.1. Definition. A two- position alpha code describing the 

current interim status causing delay the delay in the PQDR investigation. 

 AP7.27.11.2. Usage. Informs the recipient of the status and reason that 

the investigation is pending final completion.

 AP7.27.11.3. DLMS 842P Reference: 2/LQ01/1050/IRC PQDR Interim 

Reply Code (new data element). 

Table AP7.27.T11. PQDR Interim Reply Codes

Code Literal

AE Pending for Engineering Response

AR Pending Approving Official Review Prior to Completion 

Notification

CR Pending Credit/Replacement Determination

ED Pending Exhibit Disposition Confirmation

ER Exhibit Requested, Awaiting Exhibit

IR Awaiting IM Response

MD Pending Material Disposition

OR Awaiting Originator Response

PA Pending Post Award Review

PM Awaiting PM Review

PR Pending Pre-positioned Materiel Request

RR Pending Requisition Number request
Enclosure 4, ADC 1007E

Page 20

Table AP7.27.T11. PQDR Interim Reply Codes

Code Literal

SC Awaiting Screening Pt Response

SP Awaiting Support Pt Response

SR Pending Shipment Received (Exhibit)

SS Pending Stock Screening Results

TD Awaiting Design Information

TR Awaiting Test Results

VL Pending Vendor Litigation

VR Awaiting Vendor Response

VR Pending Vendor Receipt of Exhibits

AP7.27.12. Product Quality Deficiency Report (PQDR) Cancellation Codes.

 AP7.27.12.1. Definition. A two-position numeric code used with 

transaction set purpose code 01, describing the reason for PQDR cancellation. 

 AP7.27.12.2. Usage. Informs the recipient why the PQDR was 

cancelled.

 AP7.27.12.3. DLMS 842P Reference: 2/LQ01/1050/PCC PQDR 

Cancellation Code (new data element). 

AP7.27.T12 PQDR Cancellation Codes

Code Description

19 Exhibit Compromised

22 Exhibit Not Received by Customer Service

17 Exhibit Not Received by Supply

26 Exhibit Unavailable - Not Marked as a PQDR

27 Exhibit Unavailable - Released by Supply (BCM'd)

24 Exhibit not Received by DCMA
Enclosure 4, ADC 1007E

Page 21

25 Exhibit not Received by Inter-Service Agency (Air 

Force, Army, etc...)

23 Request Cancellation by Submitting Unit

21 Wrong Exhibit Shipped

20 Cancelled due to non-responsiveness of Originator

18 Deficiency reported is an SDR

 AP7.27.13. Defect Code. Originators are required to provide a Defect 

Code as part of the Transaction Set Purpose Code 00 data transmission, detailing 

what the Originator believes the cause of deficiency is.

 AP7.27.13.1. Definition. A three-position alpha numeric code 

detailing what the Originator of the PQDR believes is the detailed cause of the 

defect. These codes are identical to the Detailed Cause codes required to be 

used by Action Point or Support Points at the conclusion of the PQDR 

investigation. 

 AP7.27.12.2. Usage. Informs the recipient what the Originator 

believes is the detailed cause of the quality deficiency.

 AP7.27.12.3. DLMS 842P Reference: 2/LQ01/1050/PDD PQDR 

Discovery Code (new data element). 

Table AP7. 27.T13. Discovery Defect Codes

Code Literal

1AA Material, Incorrect

1AB Blank Intentionally

1AC Welding

1AD Coating, Protective

1AE Marking Improper

1AF Installation Improper

1AG Blank Intentionally

1AH Manufacturing /Fabrication

1AI Soldering Inadequate

1AJ Lubrication Improper

1AK Documentation Missing

1AL Blank Intentionally

1AM Damaged (Visual)

1AN Component Failure

1AO Blank Intentionally

1AP Brazing
Enclosure 4, ADC 1007E

Page 22

1AQ Bonding

1AR Potting

1AS Heat Treat

1AT Plating

1AU Chemical Film

1AV Impregnation

1AW Kitting

1AX Machining (Cutting, Grinding, Etc.)

1AY Cleaning

1AZ Clean Room

2AA Technical Data Package, Incorrect/Incomplete

2AB Blank Intentionally

2AC Blank Intentionally

2AD Test Procedures, Inadequate

2AE Blank Intentionally

2AF Blank Intentionally

2AG Configuration Control, Inadequate

2AH Instructions, Work

2AI Design, Inadequate

2AJ Operational Malfunction, Electrical

2AK Material Defective, Electrical

2AL Operational Malfunction, Electronic

2AM Material Defective, Electronic

2AN Operational, Malfunction, Mechanical

2AP Blank Intentionally

2AR Preservation/Packaging

3AA QA Requirements, Inadequate

3AB Blank Intentionally

3AC Drawing, Procured

3AD Maintenance Procedure, Improper

3AE Overhaul, Incomplete

3AF Torque, Improper

3AG Blank Intentionally

3AH Computer (Software) Quality Assurance / Software, Incomplete

3AI Test Equipment, Automatic

3AJ Calibration

3AK Testing, Electronic

3AL Testing, Mechanical

3AM Testing, Nondestructive

3AN Inspection, Final

3AO Blank Intentionally

3AP Chemical Analysis

4AA Shelf-Life Expired

4AB Shelf-Life Inappropriate

4AC Blank Intentionally
Enclosure 4, ADC 1007E

Page 23

4AD Technical Manual Error

4AE Field Fix, Improper

4AF Electrostatic Sensitive Device Controls

4AG Lead Free Solder

5AA Purchasing Error

5AB Certification, Vendor

5AC Inspection, Receiving

5AD Blank Intentionally

5AE Material, Segregation of Nonconforming

5AF Blank Intentionally

5AG Blank Intentionally

5AH Blank Intentionally

5AI Test, Pressure

5AJ Verification, Mechanical Properties

5AK Material Defective, Mechanical

5AL Material, Unauthorized Substitution

5AM Specification Error

5AN Material Identification/Mic

5AO Mercury Free Requirement, Noncompliance

5AP Contamination

5AQ Finish

5AR Assembly, Improper

5AS Counterfeit Parts, Suspect

9XA Undetermined – Isolated Case

9XB Undetermined – Info Only

9XC Undetermined – Exhibit Unavailable

9XD Undetermined – Defect Not Duplicated

9XE Undetermined – Item Warranty Procedures

9XX Undetermined - Other: The root cause of the defect could not 

be determined for reason other than listed. use of this code 

requires the reason(s) for inability to identify the root cause to 

be stated as part of the investigation report. (For Example: 

budgetary constraints, equipment or test procedures are no 

longer practical for investigation, etc.)

9XY Other Than Listed: Use of this code requires the detailed cause 

be identified as part of the investigation report.

9XZ Invalid Report: The PQDR did not meet the requirements of 

DLAR 4155.24 and is considered invalid.

AP7. 27.3. Product Quality Deficiency Investigative Closing Codes.

AP7. 27. 13.1. The information to be entered in each data element is

dependent upon the type and cause of the deficiency and the information 

requested may not be appropriate in all cases. The information requested is 

typical when the cause of the deficiency is due to non-conformance with contract 
Enclosure 4, ADC 1007E

Page 24

requirements. The investigative closing codes provide specific details about the 

findings of the investigation. Together these codes make up seven segments of 

investigation related data forming a nine-position code referred to as the 

Summary Code. 

AP7.27.13.2. The seven segments of closing data include (1) defect 

responsibility, (2) severity of the defect, (3) broad classification of the cause, (4) 

detailed cause of the defect, (5) preventative action taken because of the defect, 

(6) corrective action taken for the defective materiel, and (7) disposition of the 

deficient materiel. Each segment and their corresponding codes can be found in 

27.T14 through 27.T20. 

AP7.27.T14. SEGMENT 1 – Deficiency Responsibility - 1st Position

842P Reference: 2/LQ01/1050/DRC – Deficiency Responsibility Code (new data 

element). 

Code Literal Notes

1 Private Contractor The cause of the defect occurred at a 

contractor-operated facility and was 

determined to be a contractor's error.

2 Procurement Agency The defect was the result of a faulty 

procurement package and the 

responsibility of the buying command 

activity for contracting and procurement 

of the materiel.

3 Government Manufacturer 

(Organic Facility)

The defect was caused by a contractor 

manufacturing error at a governmentoperated manufacturing facility.

4 Design Agency The cause of the defect was due to a 

faulty Technical Data Package (TDP) or 

performance and technical 

requirements and the responsibility of 

the design activity.

5 Government Overhaul 

Facility

The cause of the defect occurred at a 

government operated overhaul facility 

not including field maintenance.

6 Using Activity The defect occurred as a result of user 

error and is the responsibility of the 

user activity.

7 Government Supply Activity The defect occurred at a government

supply facility for storing and 

requisitioning the materiel.

8 Unknown Responsible party for the cause of the 

defect could not be determined. Use of 

this code requires the reason(s) for 

inability to identify responsibility to be 
Enclosure 4, ADC 1007E

Page 25

stated as part of the investigation 

report. (For example: budgetary 

constraints, equipment or test 

procedures are no longer practical for 

the investigation, Exhibit Not Available, 

etc.).

9 Invalid Report The PQDR did not meet the 

requirements of DLAR 4155.24 and is 

considered invalid.

10 Blank (Intentionally) 

11 Field Maintenance The cause of the defect occurred during 

field maintenance, evaluation or 

operation and is the responsibility of the 

field activity.

Table AP7.27.T15. SEGMENT 2 - Severity of Defect - 2nd Position

842P Reference: 2/LQ01/1050/SDC – Severity of Defect Code (new data element). 

Code Literal Description

1 Critical A nonconformance that judgment and 

experience indicate is likely to result in 

hazardous or unsafe conditions for individuals 

using, maintaining, or depending upon the 

supplies or services or is likely to prevent 

performance of a vital agency mission.

2 Major A nonconformance, other than critical, that is 

likely to result in failure, or to materielly reduce 

the usability of the unit of supplies or services 

for their intended purpose.

3 Minor A nonconformance that is not likely to materielly 

reduce the usability of the supplies or services 

for their intended purpose or is a departure from 

established standards having little bearing on 

the effective use or operation of the supplies or 

services.

4 Unknown

5 No Defect Found

Table AP7.27.T16. SEGMENT 3 - Broad Cause - 3rd Position
Enclosure 4, ADC 1007E

Page 26

842P Reference: 2/LQ01/1050/BCD – Broad Cause of Defect Code (new data 

element). 

Code Literal Notes

A Normal Wear and Tear 

& Component (Worn 

Out)

Indicates that the reported deficiency is 

attributed to normal wear and tear of the 

item, within expected or designed 

performance levels. The PQDR is 

considered invalid.

C Contract Error The actual contract was in error, e.g., wrong 

part number called out, wrong specification 

cited, etc.

D Technical Data 

Package (TDP)/Design 

Error

Contractor met requirements but the TDP or 

specified design requirements were 

inadequate and resulted in defective 

materiel.

M Maintenance Error Defect occurred during the repair, rework, 

modification, or overhaul of the item.

N Contractor 

Noncompliance

Contractor (Government or private) failed to 

meet one or more contractual 

manufacturing requirements, resulting in 

defective materiel.

P Part Application Part Complies but is not usable in the 

application.

S Shelf-Life Problem The item's shelf-life was expired or 

inappropriate.

U Misuse Of Item The originator caused the defect through 

misuse.

V Operated Beyond Life 

Limits

Component operated past life limits set by 

design or engineering

X Undetermined The cause of the defect could not be 

determined. Use of this code requires the 

reason(s) for inability to identify the broad 

cause to be stated as part of the 

investigation report. (For example: 

budgetary constraints, equipment or test 

procedures are no longer practical for 

investigation, Exhibit Not Available, etc.).

Z Invalid Report The PQDR did not meet the requirements of 

DLAR 4155.24 and is considered invalid. 

Invalid Report will not be used to closed 

Child PQDRs. Child PQDRs are VALID.

Table AP7.27.T17. SEGMENT 4 - Detailed Cause - 4th, 5th, and 6th Position
Enclosure 4, ADC 1007E

Page 27

842P Reference: 2/LQ01/1050/PDC – PDQR Detailed Cause Code (new data 

element). 

Code Literal

1AA Material, Incorrect

1AB Blank Intentionally

1AC Welding

1AD Coating, Protective

1AE Marking Improper

1AF Installation Improper

1AG Blank Intentionally

1AH Manufacturing /Fabrication

1AI Soldering Inadequate

1AJ Lubrication Improper

1AK Documentation Missing

1AL Blank Intentionally

1AM Damaged (Visual)

1AN Component Failure

1AO Blank Intentionally

1AP Brazing

1AQ Bonding

1AR Potting

1AS Heat Treat

1AT Plating

1AU Chemical Film

1AV Impregnation

1AW Kitting

1AX Machining (Cutting, Grinding, Etc.)

1AY Cleaning

1AZ Clean Room

2AA Technical Data Package, Incorrect/Incomplete

2AB Blank Intentionally

2AC Blank Intentionally

2AD Test Procedures, Inadequate

2AE Blank Intentionally

2AF Blank Intentionally

2AG Configuration Control, Inadequate

2AH Instructions, Work

2AI Design, Inadequate

2AJ Operational Malfunction, Electrical

2AK Material Defective, Electrical

2AL Operational Malfunction, Electronic

2AM Material Defective, Electronic

2AN Operational, Malfunction, Mechanical

2AP Blank Intentionally

2AR Preservation/Packaging
Enclosure 4, ADC 1007E

Page 28

3AA QA Requirements, Inadequate

3AB Blank Intentionally

3AC Drawing, Procured

3AD Maintenance Procedure, Improper

3AE Overhaul, Incomplete

3AF Torque, Improper

3AG Blank Intentionally

3AH Computer (Software) Quality Assurance / Software, Incomplete

3AI Test Equipment, Automatic

3AJ Calibration

3AK Testing, Electronic

3AL Testing, Mechanical

3AM Testing, Nondestructive

3AN Inspection, Final

3AO Blank Intentionally

3AP Chemical Analysis

4AA Shelf-Life Expired

4AB Shelf-Life Inappropriate

4AC Blank Intentionally

4AD Technical Manual Error

4AE Field Fix, Improper

4AF Electrostatic Sensitive Device Controls

4AG Lead Free Solder

5AA Purchasing Error

5AB Certification, Vendor

5AC Inspection, Receiving

5AD Blank Intentionally

5AE Material, Segregation of Nonconforming

5AF Blank Intentionally

5AG Blank Intentionally

5AH Blank Intentionally

5AI Test, Pressure

5AJ Verification, Mechanical Properties

5AK Material Defective, Mechanical

5AL Material, Unauthorized Substitution

5AM Specification Error

5AN Material Identification/Mic

5AO Mercury Free Requirement, Noncompliance

5AP Contamination

5AQ Finish

5AR Assembly, Improper

5AS Counterfeit Parts, Suspect

9XA Undetermined – Isolated Case

9XB Undetermined – Info Only

9XC Undetermined – Exhibit Unavailable
Enclosure 4, ADC 1007E

Page 29

9XD Undetermined – Defect Not Duplicated

9XE Undetermined – Item Warranty Procedures

9XX Undetermined - Other: The root cause of the defect could not 

be determined for reason other than listed. use of this code 

requires the reason(s) for inability to identify the root cause to 

be stated as part of the investigation report. (For Example: 

budgetary constraints, equipment or test procedures are no 

longer practical for investigation, etc.)

9XY Other Than Listed: Use of this code requires the detailed cause 

be identified as part of the investigation report.

9XZ Invalid Report: The PQDR did not meet the requirements of 

DLAR 4155.24 and is considered invalid.

Table AP7.27.T18. SEGMENT 5 - Preventative Action 7th Position

842P Reference: 2/LQ01/1050/PAT – Preventative Action Taken Code (new data 

element). 

Code Literal

A Process Changed (Includes Changes to Process Instructions)

B Initiated Engineering Change Proposal

C Revised Test Procedures

D Revise/Reviewed Specification/Drawing/Technical Order, 

Publication/Manual

E Blank Intentionally

F Issued Technical/Safety Bulletins

G Improved Packaging

H Change Contractual Requirements for Future Buys

I Policy Changed

J Quality Assurance Requirements Changed

K Training Provided/Modified

L Blank Intentionally

M Further Investigation to Determine Root Cause And Corrective Action

N Corrective Action Request Submitted

O Contract Terminated

P Source Qualification Revoked / Removed as Approved Source From 

Total Item Record.

Q Blank Intentionally

R No Preventative Action - Operational Risk Accepted – Use Of This Code 

Is Restricted To The PQDR Owner Or Service Only.

X No Preventative Action - Use of This Code Requires The Reason(S) For 

No Preventative Actions To Be Stated As Part Of The Investigation

Report

Z Invalid Report
Enclosure 4, ADC 1007E

Page 30

Table AP7.27.T19. SEGMENT 6 - Corrective Action 8th Position

842P Reference: 2/LQ01/1050/CAT – Corrective Action Taken Code (new data 

element). 

Code Literal

A To Be Repaired/Replaced by Contractor At No Cost To Government

B Repaired By Using Activity - Not Contractor Representative

C To Be Repaired/Replaced by Govt - Depot/Overhaul Facility

D Exhibit(S) Scrapped Without Replacement

E Use-As-Is

F To Be Repaired/Replaced by Contractor At Government Expense

G Exhibit Not Required, Turn in Through Normal Supply

H Consideration Requested

I No Corrective Action – Acceptable Risk – Use of this code is restricted to 

the PQDR owner or Service only.

X No Corrective Action - Use of This Code Requires The Reason(S) For No 

Corrective Action To Be Stated As Part Of The Investigation Report. (For 

example: budgetary constraints, equipment or test procedures are no 

longer practical for investigation, Exhibit Not Available, etc.)

Z Invalid Report - The PQDR did not meet the requirements of DLAR 4155.24 

and was considered invalid.

Table AP7.27.T20. SEGMENT 7 - Final Exhibit Disposition - 9th Position

DLMS 842P Reference: 2/LQ01/1050/FEC – Final Exhibit Disposition Code (new 

data element). 

Code Literal Notes

A Retained As Is by User Indicates the user activity 

retained the exhibit for use as is.

B Repaired by User for Use Indicates the user activity 

maintained or repaired the 

exhibit for use by the user 

activity.

C Return To Supply/User in SCC “A” Indicates the exhibit was or will 

be returned to RFI Supply under 

RFI condition.

D Return To Supply in SCC “F” Indicates the exhibit was or will 

be returned to NRFI Supply 

under normal repair cycle.

E Return To Supply in As 

Suspended/Controlled Assets In SCC

“J”, “L”, Or “Q”

Indicates that exhibit was or is 

planned to be returned to NRFI 

Supply under a suspended 

condition.
Enclosure 4, ADC 1007E

Page 31

F Return To Supply in SCC “H/S” 

Condemn/Scrap

Indicates that the exhibit was or 

is planned to be returned to NRFI 

Supply to be scraped/destroyed.

G Return To Vendor Without Re-Supply Indicates that the exhibit was 

returned to and retained by the 

contractor, vendor, or SOS.

H Holding Activity Authorized to

Dispose/Scrap 

Indicates the user or holding

activity of the exhibit has or has 

been instructed to scrap or 

destroy the exhibit.

I Disposition Not Necessary- No 

Exhibit Available

Indicates that final disposition of 

exhibit is not necessary for 

reasons such as invalid report, 

info only report, materiel not 

received, etc.

J Removed For Conditioned Based 

Maintenance (CBM) Analysis

Indicates the exhibit was 

transferred to the CBM program 

and final Disposition will be 

executed by CBM.

K Undetermined Indicates that final disposition of 

exhibit is not known or identified 

as part of the PQDR report
Enclosure 5, PDC 1007E

Page 1

Enclosure 5

DLA Staffing Comments have been addressed in this ADC. 

Attachment 1

Revised 842P Implementation Convention (IC) Change Table 

Recommended revisions to PDC 1007E have been highlighted. 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

1. 1/BNR01/0200 Update DLMS note(s) for existing codes 00, 03, 06, 08, 10, 11, 22, 45, 

47, CN, CO, DA, ER, FA, FS, RO and SU: 

10 Not Found

DLMS Note: Used by Screening Point, Action Point or Support Point 

exhibit requestor to request status or follow up on an exhibit request, 

exhibit shipment or exhibit receipt.

Clarify intended use of the 

qualifiers

2. 2/LQ01/1050 Update DLMS note for the following existing codes and add new codes 

ARC, BCD, CAT, CDC, DRC, DVC, FEC, GCP, IRC, PAT, P1C, P2C, 

PCC, PCD, PDD, PQC, PQR, PQS, RAC, and SDC: 

ARC Action Requested Code 

DLMS Note: Fourteenth Position of the PQDR Summary Code.

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

3. A data maintenance action will be submitted to X12 to establish 

‘ARC – Action Requested Code' in a future version

CDC Current Disposition Code 

DLMS Note:Thirteenth Position of the PQDR Summary Code. 

4. SF368 Block 19: Use codes H-Holding Exhibit, D-Disposed 

of/Destroyed, R-Repaired, or O-Other.

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

Point.

6. A data maintenance action will be submitted to X12 to establish 

‘CDC – Current Disposition Code' in a future version.

DVC Defect Verified Code 

DLMS Note:Eleventh Position of the PQDR Summary Code. 

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

P1C PQDR Cost Code 

DLMS Note: Twelfth Position of the PQDR Summary Code.Definition

AKA DLA Cost Code. Use Codes C-Cost to Gov’t (Commercial 

Supplier), G-Cost to Navy(Government Manufacturer/Supplier), N-No 

Clarify intended use of the 

qualifiers and add new codes.
Enclosure 5, ADC 1007E

Page 2 

# Location DLMS 842P (4030)

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

Cost to Gov’t (Commercial Supplier), U-undetermined, Z-NoCost to 

Navy (Government Manufacturer /Supplier)

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

Action Point.

2. 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:Tenth Position of the PQDR Summary Code. AKA 

Credit Code. 

3. Definition: A single character alpha code used to describe whether 

credit or other form of resolution is authorized. Use only codes: FRepaired 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.

4. A data maintenance action will be submitted to X12 to establish 

‘P2C – PQDR Credit Code' in a future version
Enclosure 5, PDC 1007E

Page 3

Attachment 2

Revised DLM 4000.25, Volume 2, Appendix 7.27, Product Quality Deficiency Report 

Relevant Data Elements

Recommended revisions (additions/deletions/formatting) to PDC 1007E have been highlighted. 

AP7.27 APPENDIX 7.27

PRODUCT QUALITY DEFICIENCY REPORT (PQDR) 

RELEVANT DATA ELEMENTS

 AP7.27.1.3.3. Corrected (General Correspondence) (Transaction 

Set Purpose Code CO). Used 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. This 

transaction will also be used to inform other PQDR processing points when Major 

Data Element changes are required after they have acknowledged receipt of the 

PQDR.

 AP7.27.1.3.10. Status Update (Transaction Set Purpose Code SU). 

Used to send an update to correct or append specific data fields in another IS.

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

Support Point for minor changes. Only the Screening Point may use the SU 

transaction or make major data element changes (RCN, NIIN/NSN, Contract 

Number or CAGE Code). In order for the Screening Point to make a major data 

element change using the SU transaction, the PQDR must be at the Screening 

Point level. The use of the SU transaction other than specified will result in a (T44).

 AP7.27.1.3.12. Information Copy (Transaction Set Purpose Code 

22). 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. See citation 

C24.3.3.6. for mandatory uses of this transaction set.

AP7.27.2. PRODUCT QUALITY DEFICIENCY REPORT SPECIFIC DATA 

ELEMENTS. 

AP7.27.2.1. Product Quality Deficiency Report (PQDR) Status Code. 

 
Enclosure 5, ADC 1007E

Page 4 

Table AP7.27.T1. PQDR Status Codes

Code Literal

<Blank> Draft Record

A1 Child PQDR

A2 Screening Pt Request For Information

A3 Action Point Request For Information

A4 Support Point Request For Information Request for Support Point 

Investigation

A8 Awaiting Verification Of Corrective Action

A9 Stock Screened PQDR

AA Request for Additional Information

AB Under Engineering Review

AC Investigation Requested Of Action Pt

AD Action Point Accepted PQDR for Investigation

AE Exhibit Requested

AF Exhibit Shipped

AG Case/PQDR Reopened

AH PQDR Rebutted Back To Support Pt

AI Information Only/Trending Purposes

AJ Awaiting Credit Recommendation Or Credit Reversal

AK Awaiting Other Closing Delay

AM Awaiting Final Materiel Disposition Instructions

AN Awaiting Funds

AO Record Returned To Originator

AP Action Pt Inv Report Submitted

AQ Investigation Requested Of Support Pt

AR Awaiting Reqs Approval/ECP Request for Additional Information

AU Other

CA Invalid PQDR

CC Nonresponsive Investigation

CD Defect Previously Investigated
Enclosure 5, ADC 1007E

Page 5 

Table AP7.27.T1. PQDR Status Codes

Code Literal

CE Enhancement

CF Exhibit Unavailable

AP7.27.3. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) CREDIT CODE 

 AP7.27.3.2. Usage. Used by Screening/Action point to provide the originator 

with current status of financial liability on reported materiel. Secondary usage is to 

support management metrics. This code appears in the 10th position of the PQDR 

Summary Code.

 AP7.27.3.3. DLMS 842P Reference: 10th position of PQDR Summary Code 

at 842P Reference: 2/LQ01/1050/P2C – PQDR Credit Code (new data element).

 

AP7.27.4. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT 

DISTRIBUTION STATUS CODE3 

AP7.27.4.1. Definition. Code indicates status/control of exhibit during the 

transportation process. Transportation process starts when the originator passes 

materiel to shipper and ends when consignee takes control of the materiel.

 AP7.27.4.2. Usage. To ensure proper and effective processing in order to 

maintain valid PQDR resolution time frames

 AP7.27.4.3. DLMS 842P Reference: 2/REF01/0700 Code KC.

AP7.27.4.4. PQDR Exhibit Distribution Status Codes are listed in Table AP7.27.T4

Table AP7.27.T4. PQDR Exhibit Distribution Status Codes

Code Literal

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

2 In staging, awaiting onward transportation

3 Received by Consignee 

3

 Refer to ADC 1007C. 
Enclosure 5, ADC 1007E

Page 6 

AP7.27.5. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT 

CURRENT DISPOSITION CODE

 AP7.27.5.2. Usage. Provide mechanism to identify exhibit initial locations. 

This code appears in the 13th position of the PQDR Summary Code. 

 AP7.27.5.3. DLMS 842P Reference: 13th position of PQDR Summary Code 

at 842P Reference: 2/LQ01/1050/CDC – Current Disposition Code Code (new data 

element). 

AP7.27.6. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT 

CURRENT DISPOSITION DELIVERY REQUIREMENT CODE

 

AP7.27.7. PRODUCT QUALITY DEFICIENCY REPORT (PQDR) EXHIBIT

CURRENT DISPOSITION OPERATING TIME AT FAILURE CODEAP

 AP7.27.7.1. Definition. A two character alphanumeric code, used for 

measure of time or events as listed in Table AP7.27.T7 for data elements: Operating 

Time at Failure, Time Since New/Overhaul, and Time Since Installation. 

 

Table AP7.27.T7:

Table AP7.27.T7. Operating Time Codes4

Code Literal Notes

03 Seconds

4 Codes 7A and 7C are established Local Codes. A data maintenance action has been submitted for 

establishment of “7A – Landings” and “7C – Flight Hours” in a future X12 Version. Refer to ADC 

1007C. 

QTY 01 Code Literal Notes

OT Operating Time at Failure

T8 Time Since 

New/Overhaul

New X12 data element

T9 Time Since Installation New X12 data element
Enclosure 5, ADC 1007E

Page 7 

Table AP7.27.T7. Operating Time Codes4

Code Literal Notes

14 Catapult Shots Used to document the number of launches an 

aircraft has been launched, i.e. aircraft catapult 

systems and/or unmanned air vehicles.

7A Landings Used to document the number of landings an 

aircraft has completed.

7C Flight Hours Used to document the amount of time in hours 

that an aircraft/equipment has been flying.

1N Starts

B7 Cycles 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 Arrestments Used to document 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

RO Rounds Fired

T8 Time Since 

New/Overhaul

New X12 data element

T9 Time Since 

Installation

New X12 data element

UN Unit, other than listed 

above
Enclosure 5, ADC 1007E

Page 8 

AP7.27.8. Product Quality Deficiency Report (PQDR) Reject Advice Code.

Table AP7.27.T8. Reject Advice Code.

Non-Security Assistance User Defined Reject Advice Codes

Code Literal

701 PQDR rejected. Incorrect Screening Point assigned

702 PQDR rejected. Incorrect Action Point assigned – different IMM 

exists 

703 PQDR Rejected. Report does not meet the requirements of a 

PQDR – invalid report.

704 PQDR Rejected. Acceptable substitute issued for material 

requisitioned.

705 PQDR rejected. Material shipped prior to cancellation request.

706 PQDR rejected. Report identifies a supply discrepancy. Resubmit 

as a SDR.

707 PQDR rejected. Requisition document is not from Action Point 

Source of Supply.

Security Assistance User Defined Reject Advice Codes

Code Literal

80_ (Reserved for Future Use)

Systemic Reject Advice Codes

Code Literal

901 Transaction rejected. Discrepancy report canceled.
Enclosure 5, ADC 1007E

Page 9

902 Transaction rejected. Record is currently open and cannot be 

reopened until closed.

903 Transaction rejected. Missing or invalid requisition document 

number (or document number/suffix).

904 Transaction rejected. Missing or invalid report control number.

905 Transaction rejected. Duplicate report control number.

906 Transaction rejected. Missing or invalid discrepant quantity.

907 Transaction rejected. Missing or invalid point of contact name.

908 Transaction rejected. Missing or invalid point of contact phone 

number/email.

909 Transaction rejected. Missing or invalid transaction date.

910 Transaction rejected. Missing or invalid deficiency discovery 

date.

911 Transaction rejected. Narrative missing.

912 Transaction rejected. No record found.

913 Transaction rejected. Missing or invalid materiel identification.

914 Transaction rejected. Missing materiel nomenclature.

915 Transaction rejected. Missing PQDR category.

916 Transaction rejected. Missing, invalid, or unauthorized use of 

DoDAAC or MAPAC

917 Transaction rejected. Missing or invalid transaction set purpose 

code. 

918 Transaction rejected. Missing action requested.

920 Transaction rejected. Exhibit shipment information provided prior 

to exhibit request.

921 Transaction rejected. Exhibit status information provided prior to 

exhibit request.

922 Transaction rejected. Exhibit receipt information provided prior to 

exhibit request.
Enclosure 5, ADC 1007E

Page 10

923 Transaction rejected. Exhibit receipt information received prior to 

exhibit shipped transaction.

924 Transaction rejected. Exhibit shipping information missing 

exhibit shipped date.

925 Transaction rejected. Exhibit shipping information missing 

exhibit shipped quantity.

926 Transaction rejected. Exhibit shipping information missing 

exhibit shipped to address.

927 Transaction rejected. Exhibit shipping information missing 

exhibit shipped tracking number.

928 Transaction rejected. Exhibit receipt information missing exhibit 

receipt date.

929 Transaction rejected. Exhibit receipt information missing exhibit 

receipt quantity.

930 Transaction rejected. Exhibit Disposition (ED) transaction 

provided prior to Material Disposition (MD) transaction.

931 Transaction rejected. Invalid special character used.

932 Transaction rejected. Time to failure missing measurement code.

933 Transaction rejected. Final reply missing defect responsibility.

934 Transaction rejected. Final reply missing severity of the defect.

935 Transaction rejected. Final reply missing broad cause.

936 Transaction rejected. Final reply missing detailed cause.

937 Transaction rejected. Final reply missing preventative action.

938 Transaction rejected. Final reply missing corrective action.

939 Transaction rejected. Final reply missing final exhibit disposition.

940 Transaction rejected. Transaction 03 RR missing Retraction 

Reason Code.

941 Transaction rejected. Transaction CO missing General 

Correspondence Purpose Code.
Enclosure 5, ADC 1007E

Page 11

942 Transaction rejected. Transaction 25 missing Interim Reply Code.

943 Transaction rejected. Transaction 01 missing Cancellation Code.

944 Transaction rejected. Transaction 00 missing Discovery Defect 

Codes.

945 Transaction rejected. Transaction 00 missing FMS case number.

946 Transaction rejected. Transaction 03 submitting after PQDR 

acknowledgement.

947 Transaction Rejected. T-SU submitted for major data element 

change when not at Screening Point.

AP7.27.9. Product Quality Deficiency Report (PQDR) Retract Reason Code.

 AP7.27.9.1. Definition. A two-position alpha numeric code used with 

transaction set purpose code 03 RR to describe the reason for requesting the 

PQDR be returned to the previous level. 
Enclosure 6, PDC 1007E

Page 1
Enclosure 6, PDC 1007E

Page 2
Enclosure 6, PDC 1007E

Page 3
Enclosure 6, PDC 1007E

Page 4