DEFENSE LOGISTICS AGENCY HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

December 16, 2020

MEMORANDUM FOR SUPPLY AND SUPPLY DISCREPANCY REPORT (SDR) PROCESS 

REVIEW COMMITTEE (PRC)

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

1007D, PQDR Establishment, Product Quality Deficiency Report (PQDR) System 

Structure Change and Code Updates to the DLMS 842P PQDR Data

The attached change to Defense Logistics Enterprise Standards as outlined in the attachment 

is approved for implementation.

Addressees may direct questions to the EBSO SDR Administrator, Mr. Ben Breen, e-mail: 

EBSO.SDR@dla.mil. Others must contact their designated PRC representative available at: 

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

THOMAS A. DELANEY 

Director, Enterprise Business Standards Office

Attachment

As stated

cc:

ODASD(Logistics)
Attachment, ADC 1007D

Page 1

ADC 1007D

PQDR Establishment, PQDR System Structure Change, and Code 

Updates to the DLMS 842P PQDR Data

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POCs:

(1) DLA Enterprise Business System (EBS): Defense Logistics Agency, 

Logistics Operations, Makeya Porter, e-mail: Makeya.Porter@dla.mil, 571-767-4504

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

NAVAIR Code 6.8.4, Steven Hauck, e-mail: Steven.Hauck@navy.mil, 732-323-1549 

(3) Product Data Reporting and Evaluation Program – Automated Information 

System (PDREP-AIS): Naval Sea Logistics Center, NSLC Code 6541, Christopher Parker; email: Christopher.J.Parke1@navy.mil, 207-438-6410

b. Functional POCs:

(1) DLA: J344, Steven Nace, e-mail: Steven.Nace@dla.mil, 571-767-6582

(2) Navy: NAVSUP HQ Code N421, Simon Hernandez, e-mail: 

Simon.Hernandez3@navy.mil, 717-605-1425

(3) Army: HQ AMC AMCOL-MC, Eric Woodfin, e-mail: 

Eric.G.Woodfin.civ@mail.mil, 256-450-7139

(4) Air Force: HQ AFMC/A4-EN, Adrian Brown, e-mail: 

Adrian.Brown@us.af.mil, 937-257-2258

(5) Defense Contract Management Agency: DCMA HQ, Michael Garroutte, 

e- mail: Michael.A.Garroutte.civ@mail.mil, 804-734-1510

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: 

a. Primary/Secondary Functional Area: Supply 

b. Primary/Secondary Functional Process: Product Quality Deficiency Reporting

3. 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
Attachment, ADC 1007D

Page 2

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. DLM 4000.25, Volume 2, Chapter 24, PQDR Program, October 9, 2018

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: 

(1) Significant changes subsequent to staffing are eliminating the term 

WebPQDR and replacing it with Product Data Reporting and Evaluation Program – Automated 

Information System (PDREP-AIS). PDREP will be the DoD PQDR repository and the Navy and 

PDREP office have agreed to host this application. 

(2) This change documents system and business rules for inter-Service/Agency 

information system data exchange, when PQDR transaction updates are required and/or 

permitted at any point during the lifecycle of a PQDR (References 3.a. through 3.g.). It also 

defines which activity (Originator, Screening Point, Action Point and Support Point) during the 

PQDR lifecycle may update a given data element for inter-Service processing of a PQDR. A 

diagram is provided in Enclosure 4, which illustrates when data exchanges between disparate 

information systems is permitted, expected, and/or required.

(3) All transactions between those systems will flow through the Defense 

Automated Addressing System (DAAS) and PDREP-AIS. In addition, PQDRs associated with 

the Department of the Navy will go to PDREP-AIS in accordance with SECNAVINST 4855.3 

(Reference 3.h.). 

b. Background: 

(1) The PQDR Program is an inter-Service program established to determine the root 

cause of product failures due to quality deficiencies. To process PQDRs, the Services must 

exchange information among Joint Deficiency Reporting System (JDRS), PDREP-AIS and 

Defense Logistics Agency (DLA) Enterprise Business Systems (EBS). The DLMS 842P 

Implementation Convention (IC) documents the format by which the systems will transfer data.

(2) Data inconsistencies exist among the various information technology (IT) 

systems. Implementation of the 842P DLMS IC and DLMS procedures, as defined in this 

change, will help prevent data inconsistencies and promote interoperability.

c. Requested Change in Detail: The DLMS 842P PQDR Data Exchange IC and 

associated processing is revised and/or clarified as follows:

(1) Adds a new qualifier code, the Final Deficiency Description (FDD)

(2/NTE01/2400). Use of this code will allow the PQDR screening point to provide final 
Attachment, ADC 1007D

Page 3

comments to the report without making changes to the action point’s closing letter and prevent 

screening points from making untracked changes to the PQDR Closing Letter (Enclosure 1).

(2) Increases the element length for the data elements Action and Additional 

Information, (2/NTE01/2400, Qualifiers ACT and ADD) so that more information can be 

provided (Enclosure 1).

(3) Deletes the data elements: Account Closed (Tiring Date) (2/DTM01/0600,

Qualifier 630), Bill of Lading Number (2/REF02/0700 Qualifier BM) and Release Number

(2/CS03/0750) as they are no longer needed. 

(4) Updates the 842P IC to include DLMS Notes specifying which role(s) has 

(have) the necessary permissions to add/update data content.

(5) Documents that DAAS processes transactions to/from component PQDR 

systems, performs file format validations, and routes PQDR’s to/from PDREP-AIS.

(6) Establishes a DoD PQDR central repository, hereafter referred to as, PDREPAIS to meet the requirements of DoDI 5000.79 (Reference 3.j.). PDREP-AIS will perform 

PQDR business process validation such as who can change what data, and when, and act as a 

central repository for all DoD PQDRs. PDREP-AIS will also contain composite PQDRs, 

provide a searchable database of PQDRs, provide transaction repository and transaction 

transparency, and allow users to pull metrics/reports. The Navy and PDREP Program office 

have agreed to implement and host the DoD central repository for PQDRs (PDREP-AIS). 

(7) Specifies that the originating system must send all attachments needed for 

PQDR investigation through the PDREP-AIS interface. This change addresses file size 

limitations for sending information to EBS; specifies what file types are allowed to be 

transmitted, and requires all attachments to be accompanied by a DLMS 842P transaction. The 

attachment name must be specified in the 2/PWK/1020 segment of the DLMS 842P; details are 

shown in Enclosure 1 and filename requirements are specified in Enclosure 3.

d. Revisions to DLM: Revise DLMS IC 842P as shown at Enclosure 1.

e. Approved Transaction Timeline Flow: The PQDR Transaction Timeline specifies 

when a transaction is active within the PQDR life cycle (Enclosure 2).

f. Alternatives: None identified.
Attachment, ADC 1007D

Page 4

5. REASON FOR CHANGE:

a. Currently, there are unacceptable data differences between information systems that are 

mutually processing the same PQDR. Some of these differences affect audit readiness. For 

example, one IT system may close a PQDR before the other IT system’s action point transmits the 

closing request. This premature closure causes rejections and inconsistencies between the IT 

systems, which leads to additional, manual work, and the closing request transaction would need 

to be resent. 

b. Establishing the DoD central repository PDREP-AIS will provide a tool for other 

organizations such as ODASD (Logistics), Navy Criminal Investigative Service (NCIS) and 

Defense Criminal Investigative Service (DCIS), Supplier Performance Risk System (SPRS), and 

the Government Accountability Office (GAO) to obtain metrics and perform research/trend 

analysis on PQDRs. 

c. Establishing PDREP-AIS will facilitate implementing the exhibit transactions outlined 

in this approved change and the following approved changes: ADC 1007, ADC 1007A, ADC 

1007B, and ADC 1007C.

d. Implementing this change will provide a faster and more efficient exchange of 

transactions among IT systems, and enhance communication among the services/agencies.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Provides PQDR business process validation, acts as a central repository 

for PQDRs, contains composite PQDRs, provides searchable database of PQDRs, provides 

transaction repository and transaction transparency, and allows users to pull metrics/reports. The 

primary goal of a PQDR is to prevent recurrence of the issue that led to the PQDR. While 

difficult to quantify, it has the potential to result in significant savings, both in materiel costs and 

personnel hours.

b. Disadvantages: None identified.

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

DEVELOPMENT: ADCs 1007 through 1007C are implemented for routing transactions 

among PQDR processing systems.

8. ADDITIONAL COMMENTS TO CONSIDER: None identified. 

9. ADDITIONAL FUNCTIONAL REQUIREMENTS: None identified. 

10. ESTIMATED TIMELINE/IMPLEMENTATION TARGET: Initial joint 

implementation targeted for 91 weeks after approval of this document. Implementation of the 

new and revised data elements identified in this change is not intended to impact the initial 

implementation. The notional schedule for implementation of the 842P, ADC 1007A, ADC

1007B, ADC 1007C, and ADC 1007Dis listed below. Implementation of business rules and data 

management, where practical, is permitted within each information technology system to support 
Attachment, ADC 1007D

Page 5

transition to implementation of these processes. Legacy system interfaces will be maintained 

until all affected systems are ready for coordinated implementation.

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

Product Delivery

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: The primary goal of a PQDR is to prevent 

recurrence of the issue that led to the PQDR. While difficult to quantify, it has the potential to 

result in significant savings, both in materiel costs and personnel hours.

12. IMPACT: 

a. New/Change DLMS Data Elements: See Enclosure 5.

b. Automated Information Systems (AIS): Impacted systems include the PDREP-AIS,

JDRS and the DLA EBS. 

c. DAAS: 842P transactions will require DAAS ASC X12 validations and mapping as 

applicable. 

d. Non-DLM 4000.25 Series Publications: Requires update to DLAR 4155.24

(Reference 3.g.). Additionally, DoD Components’ internal guidance may require updates to align 

with revised DoD requirements as shown below. There may be other DoD publications that 

require similar updates.

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

305 Product Data Reporting and Evaluation Program, April 10, 2018

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

AND EVALUATION PROGRAM, December 21, 2018

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

Performance Information (PI), October 15, 2019
Attachment, ADC 1007D

Page 6

13. PROPOSED DLMS CHANGE (PDC) 1007D RESPONSE/COMMENT 

RESOLUTION:

Component Response/Comment Disposition

1. DLA Concur with comment.

1. Change the first part of this PDC title from “WebPQDR 

Implementation” to ”WebPQDR Establishment” or 

“Establishment of WebPQDR”. – This PDC does not 

implement the WebPQDR system; it only establishes that 

there will be a WebPQDR system.

2. Remove the words “U.S. Air Force” from paragraph 

4.b.(1).

3. Remove the inclusion of WebSDR from Enclosure 4.

Additional initial DAAS non-concurrence comments:

1. I want to inform you all that DAAS has changed their 

position on PDC 1007D to a non-concur. The reason for 

the non-concurrence is directly related to the language 

regarding WebPQDR. The vague language regarding 

“WebPQDR” opens up interpretations about who will 

develop, host and maintain the proposed system.

Working with my leadership here at DLA, we are 

proposing that the WebPQDR language in PDC 1007D be 

change to PDREP-AIS. This will resolve the concerns 

posed by DAAS and it will keep PDC 1007D and future 

PDC 1007E aligned with DoDI 5000.79, which already 

identifies PDREP as the quality system of record for DoD.

In order for me to formally bring this to EBSO, I need 

each of the Steering Committee leads to provide their 

concurrence/non-concurrence to DLA’s proposed 

adjudication of DAAS’s non-concurrence. EBSO will 

need to inform us if a full re-staffing needs to take place or 

not.

1. Update made to title.

2. Update made.

3. WebSDR remains 

included in the 

Enclosure 4 

flowchart. PQDR 

Exhibit Shipment 

Discrepancies flow 

through WebSDR 

used with 

Discrepancy Code 

Q 11.

_______________

_

4. ADC will now state 

PDREP-AIS 

instead of 

WebPQDR. 

5. Navy/PDREP Concur without comment. As noted. 

ADC will now state 

PDREP-AIS instead of 

WebPQDR.

PDREP Team: Ken Carr:

PDREP has no issue with 

the change in language. 

(email 10/27/2020) 

6. Air Force Concur as written. As noted.

7. US Army Concur with Comment.

Comments:

As noted.
Attachment, ADC 1007D

Page 7

Army may need Screening Point access added for the 

following elements related to credit as the Screening Point 

provides credit in the Army PQDR process:

188 Credit Advice

C9 Previous Credit/Debit Adjustment Number

b. Recommend the Army research these elements further 

and submit any required changes for adjudication in PDC 

1007E.

8. USMC Concur without comment. As noted.

9. DAAS Concur with comment.

Comments:

1 “Establishes a DoD PQDR central repository, hereafter 

referred to as WebPQDR, to meet the requirements of 

DoDI 5000.79 (Reference 3.j.). WebPQDR will perform 

PQDR business process validation such as who can 

change what data, and when, and act as a central

repository for all DoD PQDRs. WebPQDR will also 

contain composite PQDRs, provide a searchable database 

of PQDRs, provide transaction repository and transaction 

transparency, and allow users to pull metrics/reports.”

Comment: Who will implement WebPQDR? Is DAAS 

expected to implement it? If yes, it is subject to PEOs 

approval and is also subject to cost, schedule and priority 

constraints.

New comment: I am assuming that the PDC will now state 

PDREP-AIS instead of WebPQDR. My question still 

remains the same. Who will implement PDREP-AIS? 

Steve Nace’s email indicates that it will be PDREP as the 

system of record. Recommend revising the PDC to state 

that to avoid confusion or at least state that the 

implementing entity is TBD at this time.

2. Establishing the DoD central repository 

(WebPQDR/DAAS) will provide a tool for other 

organizations such as ODASD(Logistics), Navy Criminal 

Investigative Service and Defense Criminal Investigative 

Service (NCIS/DCIS), Supplier Performance Risk System 

(SPRS), and the Government Accountability Office 

(GAO) to obtain metrics and perform research/trend 

analysis on PQDRs.

Comment: Same comment as above. DAAS cannot agree 

to this requirement unless the requirement is vetted and 

approved by the PEO and is subject to cost, schedule and 

priority constraints which may not align with PDC 

timelines.

New comment: Same comment as above. Will you make 

changes to the PDC to remove DAAS reference in the 

statement above and replace it with PDREP? 

As noted.

1. ADC will now state 

PDREP-AIS instead of 

WebPQDR. Revised PQDR 

flow chart inserted 

removing WebPQDR 

swimlane.

2.Same as above.
Attachment, ADC 1007D

Page 8

10. USTRANSCOM N/A N/A

11. GSA N/A N/A

12. ODASD Concurrence as written. Noted.
Enclosure 1, ADC 1007D

Page 1

Enclosure 1

842P Implementation Convention (IC) Change Table

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

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1007D to DLMS Introductory Notes:

- ADC 1007D, Code Updates to the DLMS 842P Product 

Quality Deficiency Report (PQDR) Data

Identifies DLMS 

Changes included in

the

DLMS Supplement.

2. 1/BNR01/0200 Add new or revise DLMS note(s) for the following existing codes

and remove 06 and GO: 

00 Original 

DLMS Note: 

Use when the Originator Originating Point Forwards to Screening 

Point. in another system or when Originator and Screening Point 

don not exist within the same system.

01 Cancellation

DLMS Note: 

Used when PQDR is Cancelled. in one system and cancelation 

needs to be propagated to other systems. Only sScreening pPoints 

may cancel a PQDR. A cancelled PQDR cannot be reopened.

03 Delete 

DLMS Note: 

Retraction used to change ownership a PQDR back to the previous 

processing point or location.

Used by Screening, Action Points and Support Points to return 

ownership of a PQDR action back to the previous processing 

point or location.

06 Confirmation

DLMS Note: 1. Used by an automated IT system to indicate 

Confirmation of Transaction Receipt from another system. 

08 Status 

DLMS Note: 

Used for to acknowledge/Status indicating that a PQDR was 

received and to provide current point of contact to the previous 

point.

10 Not Found 

DLMS Note: 

Use to send an Exhibit Tracer request. Used by exhibit requestor to 

request status or follow up on an exhibit request.

Clarify intended use of 

the qualifiers
Enclosure 1, ADC 1007D

Page 2

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

11 Response 

DLMS Note: 

Used to provide Final Reply from Support Point To Action Point 

when the support point is sending their investigation results to the 

action point.

Used when the Support Point completes their investigation and 

returns the PQDR to an Action Point.

12 Not Processed

DLMS Note: 

Use to indicate Not Processed (Misdirected) for a PQDR that was 

received by the incorrect screening, action, or support point and 

could not be processed. Return misdirected PQDR to the previous 

processing point.

Use to indicate that a PQDR was received by an incorrect 

Screening Point, Action Point, or Support Point and could not be 

processed. The transaction returns the misdirected PQDR to the 

previous processing point.

13 Request

DLMS Note: 

Use to identify an Exhibit Request. Used to request the exhibit and 

provide shipping information. 

14 Advance Notification 

DLMS Note: 

Use by the sending organization to report that an Exhibit Shipped.

Used to provide exhibit shipment information to the requestor.

22 Information Copy

DLMS Note: 

Used by WebPQDR to send Information Copy of PQDR to another 

system. Used for dissemination to non-action activities outside of 

the PQDR process in another system. Use to provide PQDR to 

other agencies with a need to know. All data fields should be sent 

to present the entire PQDR to the receiver.

25 Incremental 

DLMS Note: 

Use to identify an Interim Reply. This type transaction provides a 

formal status of the PQDR by the sender. Used by Support or 

Action Point to provide investigation status of the PQDR to the 

previous owner.

44 Rejection

DLMS Note: 

Used when PQDRII WebPQDR determines that 842P transaction is 

non-compliant with this standard or when a recipient system of an 
Enclosure 1, ADC 1007D

Page 3

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

842P is unable to process a transaction due to its unique data 

requirements (i.e., duplicate Report Control Number). This 

transaction is system generated. End users transaction should use 

Transaction Set Purpose Code 12-Return Misdirect code to return 

record with comment.

45 Follow-up 

DLMS Note: 

Use to send a Follow-up for Status only when a processing point 

has not received current status in a timely manner via SU-Interim 

Replies or the like from the current processing point, level, or 

location. Otherwise, Use CO-General Correspondence in lieu of 

this transaction. Used to request a status when a processing point 

has not provided investigation status via interim reply.

47 Transfer 

DLMS Note: 

Used to Redirect/Transfer a PQDR to another Screening Point, 

Action Point, or Support Point. 

53 Completion

DLMS Note: 

Use to Forward from Screening to Originator for Closure. Used by 

Screening Point to close out and notify other PQDR processing 

points of PQDR process completion for a given PQDR. Only the 

Screening Point may perform this transaction.

CN Completion Notification 

DLMS Note: 

Use to send a Final Reply from Action Point to Screening Point. 

Used when the Action Point completes its investigation and 

returns the PQDR to a Screening Point.

CO Corrected 

DLMS Note: 

Use to transmit a General Correspondence, information concerning 

the PQDR status from the sender to the receiver, and or to send 

corrections with an explanation of changes. Used by originators, 

screening, action, or support point.

DA Delegate to Alternate 

DLMS Note: 

Use to Delegate to Alternate Support Point by the responsible 

Support Point.

1. Used by the responsible 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.
Enclosure 1, ADC 1007D

Page 4

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

ED Exhibit Disposition 

DLMS Note: 

1.Use for Exhibit Disposition Confirmation to indicate compliance 

with instructions. Used by the current exhibit holder to confirm 

compliance with materiel disposition instructions.

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

ER Exhibit Receipt

DLMS Note: 

1. Use to indicate document an Exhibit Receipt.

2. If sent as a late exhibit receipt, PQDR is reassigned to the 

sender’s level. 

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

FA Forward to Action Point 

DLMS Note: 

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

Point. Use to Forward from Screening Point to Action Point. 

Assigns a PQDR to an action point by a screening point.

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

FC Forward to Contractor 

DLMS Note: 

1. Used when the Action Point or Support Point sends PQDR 

investigation request to a contractor. Use when PQDR is 

Forwarded to Contractor.

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

FS Forward to Support Point 

DLMS Note: 

1. Use to Forward from Action Point to Support Point. Assigns a 

PQDR to a support point by an action point. Used when the Action 

Point forwards a PQDR to a Support Point.

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

MD Materiel Disposition

DLMS Note: 

1. Use to provide Materiel Disposition. Used by the Support or 

Action Point after the investigation is complete. Used by the 

Support Point or Action Point after the investigation is complete 

to provide final materiel disposition instructions. 

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

RO Reopen

DLMS Note: 

1. PQDR Reopened by system sending the transaction and needs to 

be reopened in receiving system.

Typically used when PQDR is reopened by a screening point in one 

system and needs to be reopened in other system. Also, treated as a 
Enclosure 1, ADC 1007D

Page 5

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

request to re-open a PQDR when sent by originator, action, or 

support points to a screening point. Used to notify other systems 

that a PQDR has been reopened by the Screening Point, or that 

the other PQDR processing points (Originating, Action, or 

Support Point) have requested that the PQDR be reopened.

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

RR Reply Rebuttal

DLMS Note:

1. Use to provide a Reply Rebuttal to a previously received Final 

Reply Used to rebut an investigation response. PQDR placed at 

the prior ownership level. 

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

SU Status Update

DLMS Note:

Use to send an Update to correct or append specific data fields in 

another IT information system. Used to disseminate information 

to other process points. 

3. 2/LIN02/0200 Add new DLMS Note to the following existing codes:

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.

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.

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

Page 6

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

version 5020.

SW Stock Number

DLMS Note: 

1. Use to identify a local stock number (LSN). The LSN is 

applicable when an NSN has not been assigned and the deficient 

item has been receipted under an LSN.

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

and CAGE code.

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

may be populated or updated by the Screening Point.

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

Point or Screening Point.

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

W2 Work Unit Number

DLMS Note: 

1. Use to identify the Work Unit Code (WUC) or Equipment Item 

Code (EIC) of the nonconforming item.

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

field. 

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

Point or the Screening Point.

5. 2/LIN12/0200 Add new DLMS Note 3 to existing code OT:

OT Internal Number

DLMS Note: 

1. Use to identify the Air Force Reference Designator.

2. This is the Reference Designator (C017)/LCN (F022) of the item 

for which the report is being submitted. For the C017 Reference 

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

to the Integrated Management Information System (IMIS).

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

Originating Point, Screening Point, or Action Point.

6. 2/LIN14/0200 Add new 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.
Enclosure 1, ADC 1007D

Page 7

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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.

7. 2/LIN16/0200 Add new 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.

8. 2/LIN18/0200 Add new 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

9. 2/LIN20/0200 Add new 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.

10. 2/LIN22/0200 Add new 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.
Enclosure 1, ADC 1007D

Page 8

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

11. 2/LIN24/0200 Add new 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.

12. 2/LIN26/0200 Add new 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.

13. 2/LIN28/0200 Add new 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

14. 2/DTM01/0600 Add new DLMS note for the following existing codes: 

002 Delivery Request

DLMS Note: 

1. Use to identify the Exhibit Requested Date. This is the date the 

exhibit was requested by the aAction or sSupport pPoint.

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

Point, Action Point, or Support Point.

009 Process

DLMS Note: 

1. Use to identify the Screening to Action Date (also known as 

Screening Point Release Date). This is the date the Screening Point 

released the deficiency report to the Action Point.

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

Point.
Enclosure 1, ADC 1007D

Page 9

011 Shipped

DLMS Note: 

1. Use to identify the Exhibit Shipped Date.

2. This element may be populated/updated by any role.

050 Received

DLMS Note: 

1. Use to identify the Exhibit Received Date. This is the date 

exhibit was received by the Action or Support Point activity.

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

or Action Point.

094 Manufacture

DLMS Note: 

1. Use to identify the Date of Manufacture.

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

points.

145 Opening Date

DLMS Note:

1. Use to identify PQDR the Re-Open Request Date. Used to 

identify the date the PQDR was reopened. May only be used 

when BNR02 conveys qualifier code RO.

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

Point.

146 Closing Date

DLMS Note: 

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

the PQDR is closed by the Screening Point.

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

Point.

177 Cancellation

DLMS Note: 

1. Use to identify the date of the customer's request to cCancel a 

previously submitted PQDR.

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

Point.

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

188 Credit Advice

DLMS Note: 

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

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

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

date applicable to the document number included in the Report 

Loop (HL01=RP) and use a separate Document Number Loop

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

combination.
Enclosure 1, ADC 1007D

Page 10

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

4. When providing a credit date, also provide the credit value 

(AMT01=PD) (and the DLA Credit Memo Number, when 

applicable) in the same loop.

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

Point.

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.

368 Submittal

DLMS Note: 

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

Action Point released PQDR to the Support Point.

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

Point.

370 Actual Departure Date

DLMS Note: 1. Not used, reserved for future use. Use to identify 

the Exhibit Shipped by Exhibit Warehouse Date.

440 Release of Information

DLMS Note: 

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

Action Point released the PQDR to the Screening Point.

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

Point.

508 Extended

DLMS Note: 

1. Use to identify the Exhibit Extended Hold Date. This is the date 

the exhibit is to be kept in holding status if beyond 90 days.

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

the Screening Point.

512 Warranty Expiration

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

514 Transferred 
Enclosure 1, ADC 1007D

Page 11

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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 only be populated/updated by the Support 

Point.

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.

649 Document Due

DLMS Note: 

1. Use to identify the Support Point Due Date.

2. Only sSupport pPoint may assign the date update information is 

due back to the Action Point and be populated/updated by the 

Support Point.

909 Contestability

DLMS Note: 

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

is the date the Action Point rebutted the final reply from Support 

Point.

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

Point.

922 Original Receipt

DLMS Note: 

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

the Originator.

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

Point or the Screening Point.

947 Preparation

DLMS Note:

1. Use to identify the date the PQDR was completed by the 

originator and submitted to the sScreening pPoint (also known as 

Submitted Date, Preparation Date, Originator Release Date, 

Screening Point receipt date). This is the date the SF368 was filled 

out (completed). Equates to former Block 1c, Date Submitted, on 

the old version of the SF368.

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

Point.
Enclosure 1, ADC 1007D

Page 12

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

AAG Due Date

DLMS Note:

1. Use to identify the Action Point Due Date.

2. Only aAction pPoint may assign this date based on category that 

a response is due back to sScreening pPoint.

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

Screening Point.

ABY Product Held Until

DLMS Note:

1. Use to identify the Exhibit Hold Date. This is the date an item 

will be held until before disposition.

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

Point.

ACK Acknowledgement

DLMS Note: 

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

2. This element may be used and/or updated by the Screening 

Point, Action Point, and/or the Support Point.

ACZ Controvert Date

DLMS Note: 

1. Use to identify the Screening Point Rebuttal/Controvert Date. 

This is the date the Screening Point rebutted the final reply from 

Action Point.

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

Point.

DIS Disposition

DLMS Note: 

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

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

Screening Point.

15. 2/DTM01/0600 Delete code 630 and DLMS Note:

630 Account Closed

DLMS Note: Use to identify PQDR Transaction Item Reporting 

(TIR) Date (Tiring Date). This is the date carcass tracking was 

completed/closed.

16. 2/REF01/0700 Modify DLMS note for the following existing codes: 

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

Page 13

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

Point, the Screening Point, or Action Point.

2E Foreign Military Sales Case Number

DLMS Note:

Reserved for future use to identify FMS Case Numbers for FMS 

SDRs.

3H Case Number

DLMS Note: 

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

the sending system assigned number. i.e. DLA Case Control 

Number, Action Point Control Number, etc. Submitting activity's 

control number, if different than RCN. Identify the system that 

created the control number in REF03.

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

Point.

44 End Use Number

DLMS Note: 

1. Use to identify the End Item Type/Model/Series. This is the 

major weapons system with which the end item is associated. 

Equates to SF 368, Block 18c.

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

Point, the Screening Point, or Action Point.

86 Operation Number

DLMS Note: 

1. Reserved for future use to identify the Navy Key Operation with 

an associated Job Order Number.

87 Functional Category

DLMS Note: 1. Reserved for future use to identify the special 

types of PQDRs, such as aircraft deficiency reports (ADR), 

Equipment Improvement Reports (EIR), etc.

9R Job Order Number

DLMS Note: 

Reserved for future use to identify the Navy Job Order Number.

BY Repair Category Number

DLMS Note: 

1. Use to identify the nonconforming materiel as Item New or 

Repaired/Overhauled Code.

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

Unknown.

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

Point, Screening Point, and Action Point.
Enclosure 1, ADC 1007D

Page 14

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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.

C9 Previous Credit/Debit Adjustment Number

DLMS Note: 

1. Use to identify the DLA Credit Memo Number. This is reference 

number provided to track credit.

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

memo number applicable to the document number included in the 

Report Loop (HL01=RP) and use a separate Document Number 

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

memo number combination.

3. When providing a credit memo number, also provide the credit 

date (DTM01=188) and credit value (AMT01=PD) in the same 

loop.

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

Point.

F8 Original Reference Number

DLMS Note: 

1. Use to identify Screening Point Control Number in REF02 . 

Identify the system that created the control number in REF03.

2. Field size = 14.

3. Definition: Control number assigned by the sScreening pPoint if 

different from the RCN.

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

Point.

GO Exhibit Identifier 

DLMS Note: 

Reserved for future use to identify AF Accession Number.

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

Point, Screening Point, and Action Point.
Enclosure 1, ADC 1007D

Page 15

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

Point, Screening Point, and Action Point.

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 or not the item is used in a critical 

application (end use).

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

Point, Screening Point, and Action Point.

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.

KK Delivery Reference 

DLMS Note: 

1. Cite the applicable PQDR Exhibit Delivery Requirement Code to 

identify the status of exhibit materiel

from the aAction or sSupport pPoint of view. Cite the applicable 

code in REF02. 2. Refer to ADC 1007C.

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

Point or Support Point.

KU Office Symbol

DLMS Note:

1. Use to identify the DLA Action Office code.

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

Point.

NN Nonconformance Report Number

DLMS Note: 

1. Use to identify Parent Master/Previous Record Control Number 

(RCN). This is a previously reported PQDR RCN for same type 

deficiency. Identify the system that created the control number in 

REF03.
Enclosure 1, ADC 1007D

Page 16

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

2. PQDRII fField size = 12.

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

Point or the Screening Point.

PM Part Number

DLMS Note: 

1. Use to identify the End Item Part Number.

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

Point, Screening Point, or the Action Point.

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 only be populated/updated by all processing 

points.

QE Replacement Customer Reference Number

DLMS Note: 

1. Use in responses, as needed to identify the document number 

under which replacement materiel will be

provided to the organization reporting the deficiency, or the 

document number provided from an ICP that authorizes the return 

of deficient materiel or exhibit.

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

Point.

QR Quality Report Number

DLMS Note: 

1. Must use to identify the PQDR Report Control Number (RCN). 

It is comprised of the six-position originating activity DoDAAC, a 

two-digit calendar year, and a unique four-position serial number. 

Field length is 12, alpha numeric only.

2. This element may only be entered by the Originating Point, and 

updated by the Screening Point.

TG Transportation Control Number

DLMS Note: 

1. Use to indicate the Transportation Control number.

2. Field size = 17.

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

Point, Screening Point or Action Point.

TN Transaction Reference Number 

DLMS Note: 

1. Use to indicate the original document numbers under which the 

defective materiel was purchased, requisitioned, shipped, or 
Enclosure 1, ADC 1007D

Page 17

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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, Screening Point.

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.

VW Standard

DLMS Note: 

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

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

of the deficient materiel.

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

Point, Screening Point or Action Point.

X3 Defect Code Number

DLMS Note: 

Use to identify the PQDR Summary Code structured as follows:

Deficiency Responsibility Code (1st position)

AKA Defect Responsibility Code

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

 

Severity of Defect Code (2nd position)

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

Regulation for appropriate codes.

This field may be populated/updated by the Support Point or the 

Action Point. The Screening Point may use the code if it is not 
Enclosure 1, ADC 1007D

Page 18

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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.

Broad Cause of Defect Code (3rd position)

AKA Broad Cause Code.

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. 

Detailed Cause Code (4-6th position)

Definition: Refer to DLAR 4155.24 or Refer to Reference (g

PQDR Joint Regulation detailed cause of deficiency. See PQDR 

Joint Regulation for appropriate codes.

Preventive Action Taken Code (7th position)

Definition: Code used to indicate the preventive action taken to 

prevent recurrence. See PQDR Joint Regulation 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.

Corrective Action Taken Code (8th position)

AKA Action Taken Code, Corrective Action Code

Definition: Corrective action code taken as a result of the 

investigation. See PQDR Joint Regulation 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.
Enclosure 1, ADC 1007D

Page 19

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

Final Exhibit Disposition Code (9th position)

AKA Action Disposition

Definition: Code representing the current disposition of the exhibit. 

See PQDR Joint Regulation 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. 

Credit Code (10th position)

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, SSource of Supply Replacement, T-Source of Supply Repair, WCredit Authorized, X-No Credit Authorized.

This field may be populated/updated by the Screening Point, 

Action Point, or the Support Point.

Defect Verified Code (11th position)

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.

Cost Code (12th position)

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)

This field may only be populated/updated by the Screening Point 

or Action Point.

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.

Action Requested (14th position)

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

or O-Other
Enclosure 1, ADC 1007D

Page 20

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

Originating Point.

AAN Associated Case Control Number

DLMS Note: 1. Use to identify the Support Points Investigators 

Control Number. This is the DCMA/Support Point Control 

Number. Identify the system that created the control number in 

REF03.

2. Field size = 25.

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

Point.

PSM Credit Card

DLMS Note: 1. Use to indicate payment by either Government 

purchase card or commercial credit card. Cite Y in REF02 when 

applicable.

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

Point or Screening Point.

17. 2/REF01/0700 Delete code BM with DLMS Note:

BM Bill of Lading Number

DLMS Note: 

Use to identify Government Bill of Lading/Commercial Bill of 

Lading (GBL/CBL) Number.

18. 2/REF03/0700 Add new Data Element level DLMS Note 2 and update existing 

Note 1:

Description

DLMS Note: 

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

systems such as i.e. Army-LMP, AWIS, DLA- EBS, JDRS, NavyERP, PDREP, or USMC-GCCS).

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

points.

3. Field size = 14.

19. 2/REF04-

01/0700

Add new 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 field may only be used by the Originating Point, 

Screening Point, or Action Point.
Enclosure 1, ADC 1007D

Page 21

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

20. 2/CS03/0750 Mark Data Element 328 “Release Number” Not Used:

DLMS Note:

1. Use to identify the legacy four-position call/order Number 

associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Update to reflect the 

new PIID construct and 

business rules

21. 2/PWK/1020 Segment level DLMS Note:

DLMS Note:

Use a separate PWK segment for each attachment identified by 

filename. Repeat as needed to identify each attachment. 

Included for context.

22. 2/PWK01/1020 Revise DLMS note for existing Code AE and remove Code R6: 

AE Attachment

DLMS Note:

1. Use to indicate that supporting documentation is provided may 

be obtained electronically in the form of images or files. with the 

842P transaction. Must provide the file name, including file type, 

in the description at PWK07.

2. Use with Code FT (PWK02) when a file is transmitted 

electronically between the systems. 

3. When AE is not indicated, files were not sent with the 

transaction. 

R6 Miscellaneous Information

DLMS Note: 

Use to indicate that additional information is being submitted to the 

action activity off-line.

23. 2/PWK02/1020 FT File Transfer

DLMS Note: 

Use to indicate attachments are available. 

Included for context.

24. 2/PWK05-

06/1020

Open PWK05 and PWK06 and add new Code UR in PWK05:

UR Uniform Resource Locator (URL)

DLMS Note: 

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

service.

Web service URL 

maximum length 

(PWK06) is 80 

positions due to X12 

min/max attribute . 

25. 2/PWK07/1020 Update existing Data Element level DLMS Note:

Description

DLMS Note: 

Use to indicate the PQDR Attachment

File Name, including file type. being sent electronically in a 

separate transmission.
Enclosure 1, ADC 1007D

Page 22

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

26. 2/LQ01/1050 Add new DLMS note for the following existing codes: 

CW Controvert Code

DLMS Note: 

1. Use to identify the PQDR Rebuttal/Controvert Code. Must use in 

a reply rebuttal transaction (BNR01Code=RR).

2. Use only valid codes as prescribed under the DLMS; see 

introductory DLMS Notes 3 and 4.

3. This element may be populated and or updated by the 

Screening Point, the Action Point, and/or the Support Point.

DE Signal Code

DLMS Note: 

1. Use to identify the Signal Code.

2. This element may only be populated or updated by the 

Originating Point, Screening Point, or Action Point.

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 noninterfund). 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 or updated by the 

Originating Point, Screening Point, or Action Point.

EQ Controlled Inventory Item Code

DLMS Note: 

1. Use to identify the Controlled Inventory Item Code.

2. This element may only be populated or updated by the 

Originating Point or Screening Point.

FD Demilitarization Code

DLMS Note: 

1. Use to identify the Demilitarization Code.

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

Point, Screening Point, or Action Point.

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

Screening Point, Support Point or Action Point.
Enclosure 1, ADC 1007D

Page 23

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

JN Mission Impact Statement Code

DLMS Note: 

1. Use to specify impact on current operations. Cite the applicable 

code in LQ02:

1 = Inability to perform assigned mission for a classified project

2 = Inability to perform assigned mission.

3 = Performance of assigned mission anticipated to be curtailed or 

stopped if materiel is not received

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

Outside Continental United States

(OCONUS)

4 = Mission performance below prescribed level of effectiveness 

and efficiency

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

assets

2. This element may only be populated or updated by the 

Originating Point or the Screening Point.

27. 2/NTE/2400 Add Segment Note: 

For each qualifier in NTE01, repeat the NTE segment as needed, 

with up to 80 characters in each iteration, until the maximum 

length specified for each data element (e.g., PQDR element 

length for Quality information (qualifier TRS) = 2000 characters 

in the NTE02) is conveyed.

Clarify the repetition of 

the NTE segment for 

large notes.

28. 2/NTE01/2400 Add new Code FDD with the following DLMS Note:

FDD Final Deficiency Description

DLMS Note: 

1. This will be the final closing comments from the Screening 

Point that includes their summary of the investigation. This is a 

narrative field of no more than 2000 characters and provides the 

Screening Point an opportunity to provide comments without 

changing the Action Point closing letter. 

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

Point

29. 2/NTE01/2400 Add new 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 oOriginator or sScreening pPoint.

2. PQDRII fField size = 20 1000.

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

Originating Point or Screening Point.
Enclosure 1, ADC 1007D

Page 24

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

ADD Additional Information

DLMS Note: 

1. Use to identify Additional Information narrative for PQDR. 

Also, used when a PQDR Final reply is rebutted.

2. PQDRII Field Size = 60 4000.

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

Originating Point, Screening Point, or Action Point.

EBK Other Reason for Withdrawal

DLMS Note:1. Reserved for future use to provide comments as to 

why a PQDR was cancelled..

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. PQDRII fField size = 4000.

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

Originating Point or the Screening Point.

POL Property Owner Location Information

DLMS Note: 

1. Use to identify the originators Location of Exhibit narrative. This 

is detailed information about where materiel is currently located.

2. PQDRII fField size = 100.

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

Originating Point or the Screening Point.

Local code SPS is established for use in the DLMS IC 842P 

version 4030. A data maintenance action will be submitted to 

X12 to establish ‘SPS- Screening Point Summary' in a future 

version. Add DLMS Note as shown below. 

SPS Screening Point Summary

DLMS Note: 

This element may only be populated/updated by the Screening 

Point.

30. 2/QTY01/2700 Add new DLMS note for the following existing codes: 

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

Originating Point or the Screening Point.
Enclosure 1, ADC 1007D

Page 25

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

02 Cumulative Quantity

DLMS Note: 

1. Use to identify the quantity of Time Since New/Overhaul. This 

is the time elapsed since the last repair, or initial use for new items, 

and materiel failure.

2. Field size = 7.

3. This field may only be populated or updated by all processing 

points.

38 Original Quantity 

DLMS Note: 

1. Use in to indicate the Quantity of Prior Deficiencies. This is the 

quantity of similar failures reported on previous PQDRs.

2. Field size = 5.

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

Point, Screening Point or Action Point.

39 Shipped Quantity

DLMS Note: 

1. Use to identify the Quantity of Exhibits Shipped.

2. PQDRII fField size = 7.

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

Originating Point, Screening Point or Action Point.

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

Originating Point or Screening Point.

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

Originating Point, Screening Point, or Action Point.

AO Verified Receipts

DLMS Note: 

1. Use to identify the quantity of Exhibits Received by the aAction 

or sSupport pPoint.

2. Field size = 7.

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

Point or the Support Point.
Enclosure 1, ADC 1007D

Page 26

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

Originating Point, Screening Point or Support Point.

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

Originating Point or Screening Point.

V3 Transfer Quantity

DLMS Note: 

1. Use to identify the quantity of Exhibits Requested by aAction or 

sSupport pPoint.

2. Field size = 7.

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

the Support Point.

31. 2/QTY03/2700 Add new 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 only be populated or updated by all 

processing points.

32. 2/AMT01/2730 Add new DLMS note for the following existing codes: 

10 Shipment Value in U.S. Dollars

DLMS Note: 
Enclosure 1, ADC 1007D

Page 27

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

1. Use to indicate “total” value of defectives 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 or updated by all processing 

points.

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 or updated by all processing 

points.

PD Credit

DLMS Note:

1. Use to indicate the amount of credit/debit being authorized or 

recommended (also known as DLA Credit Value).

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

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

amount applicable to the document number included in the Report 

Loop (HL01=RP) and use a separate Document Number Loop 

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

amount combination.

4. When providing a credit amount, also provide the credit date 

(DTM01=188) (and the DLA Credit Memo Number, when 

applicable) in the same loop.

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

Point or Action Point.

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

Originating Point, or the Screening Point.

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

Page 28

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

33. 2/N101/2800 Add new 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 or updated by the 

Originating Point.

91 Action Party

DLMS Note: 

1. Use to identify the Action Point DoDAAC when different than 

the address identified with the DoDAAC-From in 1/N101/1200.

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

Point or the Action Point.

92 Support Party

DLMS Note: 

1. Use to identify the Support Point DoDAAC when different than 

the address identified with the DoDAAC-From in 1/N101/1200.

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

Point, and the Support Point.

C4 Contract Administration Office

DLMS Note: 

1. Use to identify DLA Form 1227, DCMA Review Release 

Authority or Preparer by DoDAAC.

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

Point.

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

Originating Point or the Screening Point.

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

Originating Point or the Screening Point.
Enclosure 1, ADC 1007D

Page 29

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

34. 2/N102/2800 Add new 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 or updated by the 

Originating Point or the Screening Point.

35. 2/N201/2900 Add new Data Element level DLMS Note 3:

Name

DLMS Note: 

1. This equates to address line.

2. Used when customer input for the reporting activity information 

is not available or differs from data extracted from the DoDAAC.

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

Originating Point or the Screening Point.

36. 2/N202/2900 Add new 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 or updated by the 

Originating Point or the Screening Point.

37. 2/PER01/3200 Add new DLMS Note 2 for the following existing codes: 

AU Report Authorizer

DLMS Note:

1. Use to identify the review official's information associated with 

DLA Form 1227 (also known as Review Release Authority). This 

is the official that reviewed the 1227 previous to release.

2. This element may only be populated or updated by the Support 

Point or Action Point (if no Support Point).

PU Report Preparer

DLMS Note: 

1. Use to identify the preparing official's information associated 

with the DLA Form 1227. AKA Prepared By.

2. This element may only be populated or updated by the Support 

Point or Action Point (if no Support Point).
Enclosure 1, ADC 1007D

Page 30

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

Screening Point, Action Point, or Support Point.

38. 2/PER03/3200 Add new 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 or updated by all processing 

points.

EM Electronic Email

DLMS Note: 

1. Use to identify the E-mail address.

2. This element may be populated or updated by all processing 

points.

TE Telephone

DLMS Note: 

1. Use to identify the Commercial Phone Number.

2. This element may be populated or updated by all processing 

points.

39. 2/PER05/3200 Add new 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 or updated by all processing 

points.

EM Electronic Email

DLMS Note: 

1. Use to identify the E-mail address.

2. This element may be populated or updated by all processing 

points.

TE Telephone

DLMS Note: 

1. Use to identify the Commercial Phone Number.

2. This element may be populated or updated by all processing 

points.
Enclosure 1, ADC 1007D

Page 31

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

40. 2/PER07/3200 Add new 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 or updated by all processing 

points.

EM Electronic Email

DLMS Note: 

1. Use to identify the E-mail address.

2. This element may be populated or updated by all processing 

points.

TE Telephone

DLMS Note: 

1. Use to identify the Commercial Phone Number.

2. This element may be populated or updated by all processing 

points.

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

42. 2/NTE/3500 Add Segment Note: 

For each qualifier in NTE01, repeat the NTE segment as needed, 

with up to 80 characters in each iteration, until the maximum 

length specified for each data element (e.g., PQDR element 

length for Quality information (qualifier TRS) = 2000 characters 

in the NTE02) is conveyed.

Clarify the repetition of 

the NTE segment for 

large notes.

43. 2/NTE01/3500 Add new DLMS note for the following existing codes: 

ACI Additional Claim Information

DLMS Note:

1. Used to identify Supplemental Data to provide additional 

information pertinent to the PQDR investigation.

2. Field size = 4000.

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

the Support Point.

ACN Action Taken

DLMS Note: 
Enclosure 1, ADC 1007D

Page 32

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

1. Use to Identify the Final Reply Results narrative describing the 

final results of the investigation.

2. Field size = 2000.

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

the Support Point.

AES Actual Evaluation Summary

DLMS Note: 

1. Use to identify Evaluation of Current Production. This is the 

DCMA representative’s assessment of the effect on current 

production. Equates to DLA Form 1227, Block 15.

2. Field size = 2000.

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

Point.

CAR Other Related Information

DLMS Note: 

1. Use to identify the Corrective Action by Contractor describing 

the actions the contractor took to fix problem. Equates to DLA 

Form 1227, Block 13.

2. Field size = 2000.

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

Point.

CBB Consideration to be Received

DLMS Note: 

1. Use to identify the Contractors Position on repair or replacement 

of materiel. Equates to DLA Form 1227 Bblock 16.

2. Field size = 2000.

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

Point.

CER Certification Narrative

DLMS Note: 

1. Use to identify Final Reply for Alerts narrative. This is the 

PQDR Joint Regulation narrative requesting screening of materiel. 

Optional for USAF.

2. Field size = 2000.

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

Point.

EAT Asset Disposition

DLMS Note:

1. Use to identify the Materiel Disposition instructions.

2. Field size = 2000.

3. Definition: Use to identify the Materiel Disposition instructions 

to the Support Points Materiel Disposition instructions for the 

defective item narrative.
Enclosure 1, ADC 1007D

Page 33

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

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

Point.

IID Inventory (Stock) Description

DLMS Note:

1. Use to document the Results of Depot Surveillance. This is the 

depot stock screening information including any findings as a result 

of screening depot stocks for similar problems.

2. Field size = 2000.

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

Point or the Support Point.

ORI Order Instructions

DLMS Note: 

1. Use to provide, explain, or otherwise describe unique Shipping 

Instructions.

2. Field size = 2000.

3. This element may be used by the Action Point and updated by 

the Screening Point and/or the Support Point.

OTH Other Instructions

DLMS Note: 

1. Use to identify the Exhibit Final Disposition Instruction 

containing the aAction pPoint instruction to sScreening or sSupport 

pPoint for final handling of the exhibit. This is the Action Point’s 

instruction to Screening or Support point for final handling of the 

exhibit.

2. Field size = 2000.

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

Screening Point, Action Point, or Support Point.

REC Recommendation

DLMS Note: 

1. Use to identify the Findings and recommendations of 

Investigation. This is a narrative describing the results of the 

investigation, action taken to correct the deficiency, and the 

corrective action to prevent recurrence.

2. Field size = 4000.

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

Point.

REP Report

DLMS Note: 

1. Use to identify the Preventive Action Taken (Answer) narrative. 

Derived from the DLA Form 1227.

2. Field size = 2000.

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

Point.
Enclosure 1, ADC 1007D

Page 34

# Location DLMS 842P 

Product Quality Deficiency Report (PQDR) 

Data Exchange Revision

Reason

RPT Report Remarks

DLMS Note: 

1. Use to identify Remarks and Recommendations providing any 

government or contractor comments related to the investigation. 

Equates to DLA Form 1227, Block 17.

2. Field size = 2000.

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

Point.

SSC Status Comment

DLMS Note: 

1. Use to identify the Enclosures Distribution. This identifies 

attachments and mailing codes associated with the 1227. Equates to 

DLA Form 1227, Block 18.

2. Field size = 2000.

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

Point.

TRS Quality Information

DLMS Note: 

1. Use to identify the Cause of Deficiency narrative describing the 

Root cause of deficiency found during the investigation. Equates to 

DLA Form 1227, Block 12.

2. Field size = 2000.

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

Point.

WHI Warehouse Instruction

DLMS Note: 

1. Use to identify Corrective Actions by Government narrative. 

This provides DCMA's verification corrective actions. Equates to 

DLA Form 1227, Block 14.

2. Field size = 2000.

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

Point.
Enclosure 2, ADC 1007D

Page 1

Enclosure 2

PQDR Life Cycle Flowchart and Transaction Timeline 
Enclosure 2, ADC 1007D

Page 2
Enclosure 3, ADC 1007D

Page 1

Enclosure 3

Attachment File Name Requirements

1) Originating system must send all attachments submitted for PQDR investigation. 

2) The maximum size that can be sent to DLA-EBS is 15 Megabytes. Larger files will 

be available by accessing a partner system's attachment service (i.e. logging into 

PDREP-AIS or JDRS).

3) Attachment File Rules:

1. No larger than 15 megabytes (MBs)

2. Filename maximum length of 50 characters (excluding the file extension).

3. Spaces/blank characters are not permitted in filenames, hyphen “-” characters 

must be used instead.

4. Lowercase letters are not permitted in filenames, uppercase letters must be used.

5. Underscores separate individual portions of the filename to support processing 

rules.

6. The user-entered file name portion must not contain underscore characters.

7. Filenames must be constructed as follows. The T, R, X and B requirements are 

separated by an underscore. The following construct defines an acceptable 

structure. 

TTTTTTTTTT_RRRRRRRRRRRR_XXXXXX_BB_YYYYJJJHHMMII.EXTN

a. T = Original user-provided file name (up to 10 characters, excluding 

extension), e.g. “testresult” or “WRONG_ITEM”. This portion of the file 

name is derived from the user’s original saved file. If the user-provided 

filename exceeds 10 characters, use the first 10 characters.

b. R = Report Control Number (12 position alphanumeric characters)

c. X = Sender’s System DoDAAC (6 position alphanumeric character)

d. BB = Set Code (2 position alphanumeric characters) value copied from the 

set code of the accompanying 842P transaction.

e. YYYY = Year (4 position numeric characters)

f. JJJ = Julian Day (3 position numeric characters)

g. HH = Hours (2 digit numeric characters)

h. MM = Minutes (2 digit numeric characters)

i. II = Serial Number (2 digit numeric character). Start with “01.” Assigned 

sequentially; used to indicate the order attachments are sent. 

j. EXTN = Original file extension (3 or 4 position alpha characters, see 

allowed file formats below)
Enclosure 3, ADC 1007D

Page 2

4) Only the file types below are allowed:

- AVI (Video) 

- BMP (Bitmap Image)

- CSV (Comma Separated Values)

- DOC (Microsoft Office Document)

- DOCX (Microsoft Office Document)

- GIF (Graphical Format) 

- JPG (Photo) 

- JPEG (Photo) 

- MDB (Database)

- MKV (Video)

- MOV (Video) 

- MP4 (Video) 

- MSG (Microsoft Outlook Message) 

- PDF (Adobe Acrobat Document) 

- PPT (PowerPoint Document)

- PPTX (PowerPoint Document)

- RTF (Text Document) 

- TIFF (Image) 

- TXT (Raw Text file) 

- WAV (Audio) 

- WMV (Video) 

- XLS (Microsoft Office Spreadsheet) 

- XLSX (Microsoft Office Spreadsheet)

5) All attachment file names must be listed in the PWK Segment of the 842P 

transaction. 
Enclosure 4, ADC 1007D

Page 1

Enclosure 4

PQDR Data Flow Methodology

PQDR Data Flow (Component Systems sends X12/XML File to DAAS via Web Service, DAAS forwards to PQDR Repository)

D

A

AS P

D

REP-AIS C

o

m

p

o

n

e

nt

Syste

ms

JDRS DLA-EBS WebSDR

DAAS Interface

- Route transactions to /from component systems and the DOD PQDR Repository (PDREP-AIS)

- File Format checks (ensures transactions are formatted in the appropriate X 12/XML format)

- Central POC for Component System in the event of transaction failures

PQDR 

Data

PQDR 

Data

PQDR

Attachments

PQDR

Attachments

SDR 

Data

SDR

Attachments

PDREP-AIS Application Interface

- PQDR Repository

- Composite PQDR

- Searchable database by RCN

- Ability to run metrics on PQDR data

PDREP-AIS Transaction Interface

- 842P Transaction Validations

- Central POC for Component System in 

the event of transaction failures

PDREP Web 

Services: SDR 

IN & OUTBOX

PDREP Web 

Services: SDR 

Attachments

PDREP Web 

Services: PQDR 

IN & OUTBOX

PDREP Web 

Services: PQDR 

Attachments

PQDR

Attachments

PQDR 

Data

SDR 

Data

SDR

Attachments

Exhibit Tracking

856R
Enclosure 5, ADC 1007D

Page 1

Enclosure 5

LOGISTICS DATA RESOURCES MANAGEMENT SYSTEM (LOGDRMS)

Add the following new Data Element to LOGDRMS

NAME: Final Deficiency Description

DEFINITION: This will be the final closing comments from 

the Screening Point that includes their 

summary of the investigation.

DATA CODE CHARACTERISTICS: TYPE: A/N MIN: 1 MAX: 2000 

SOURCE: DLM 4000.25, Vol 2, Chapter 24

REMARKS: The Deficiency Description will allow the 

PQDR Screening Point to provide final 

comments to the report without making 

changes to the Action Points closing letter 

and prevent Screening Points from making 

untracked changes to the PQDR Closing 

Letter.