Attachment, ADC 1007 

Page 2

ADC 1007 

New DLMS 842P, PQDR Data Exchange and Enhanced Exhibit 

Tracking via Standard Logistics Transactions 

 

 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION

 a. Technical POC: 

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

and Maritime-BATA, DSN 850-1692 

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

NAVAIR code 6.8.4, 304-466-3021 

 (3) Product Data Reporting and Evaluation Program (PDREP): Naval Sea Logistics 

Center, NSLC Code 6231, DSN 684-6432 

 b. Functional POC: 

 (1) DLA: DLA Land and Maritime-BATA, DSN 850-1692

 (2) Navy: NAVSUP HQ Code N311, 717-605-8343 

 (3) Army: AMCLG-PC, 256-450-8272 

 (4) Air Force: AFMC HQ AFMC/A4UE, 937-257-4296 

 (5) DCMA: DCMA-QAB, 602-594-7869 

2. FUNCTIONAL AREA:

 a. Primary/Secondary Functional Area: Quality Assurance/Receipt and Shipment 

 b. Primary/Secondary Functional Process: PQDR Preparation and Processing/Receipt 

and Shipment of PQDR Exhibits 

3. REFERENCES: 

 a. AR 702–7/AFR 74–6/SECNAVINST 4855.5A/DLAR 4155.24, Product Quality 

Deficiency Report Program, available from the DLA PQDR Home Page. 

b. Approved DLMS Supplement 842P, PQDR Data Exchange, published on the DLMS 

Web at www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp . 

c. Approved DLMS Change 245C, Approved Addendum to ADC 245C, Notification for 

Distribution Depot Product Quality Deficiency Report (PQDR) Exhibit Receipt - Product Data 
Attachment, ADC 1007 

Page 3

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

(Supply/SDR), dated July 21, 2011. 

d. Approved DLMS Change 353A, Revised Procedures for Pre-Positioned Materiel 

Receipt (PMR) and Shipment Status for Retrograde and Directed Discrepant/Deficient Materiel 

Returns Including Corrected Time Standard for Security Assistance/Foreign Military Sales 

(SA/FMS) (Supply/SDR/PQDR/TDR/Retrograde), dated August 25, 2010. 

4. REQUESTED CHANGE:

 a. Brief Overview: This change establishes a new standard transaction format for 

exchanging PQDR data between systems. This change also establishes enhanced exhibit 

tracking procedures using standard logistics transactions. This is accomplished by including the 

PQDR Report Control Number (RCN) in applicable DLMS transactions and providing 

information copies to the PDREP-AIS. 

 b. Scenario for Which the Transaction is Used: DLAR 4155.24 requires PQDR 

submissions for deficiencies detected on new or newly reworked Government owned products 

that do not fulfill their expected purpose, operation, or service due to deficiencies in design, 

specification, materiel, software, manufacturing process, and/or workmanship, items suspected 

or found to be counterfeit or an unauthorized/unapproved product substitution. Currently PQDR 

investigation is conducted using the Product Data Reporting Evaluation Program (PDREP), the 

Joint Deficiency Reporting System (JDRS), and DLA’s Enterprise Business System (EBS). 

When the PQDR process involves multiple systems, each system will use the DLMS transaction 

to exchange PQDR data. 

 c. Procedures, Transactions, Data Elements, Processing Details in Use Today: 

 (1) PQDR: Currently, each system uses a custom data set to exchange PQDR data. 

Each interface uses limited data sets, and utilizes different rules for exchanging data. 

 (2) Exhibit Tracking: As a work around, at this time the DLMS 842A/W with 

Discrepancy Code Q11 identifies distribution depot receipt of a PQDR exhibit. ADC 245 and 

associated addendums (Reference 3.c.) updated this transaction to include the PQDR Report 

Control Number (RCN) for distribution to PDREP; the system change request for the 

Distribution Standard System has been approved and implementation is pending. The DLMS 

856R Shipment Status Materiel Returns includes the PQDR RCN although this change has not 

been implemented (Reference 3.d.). 

 d. Approved Change in Detail: Significant revisions subsequent to staffing are identified 

by green highlighting. 

 (1) PQDR. Adopt the DLMS 842P PQDR Data Exchange to establish a standard data 

transaction for exchanging PQDR data. Communication exchange will be supported by the 

PQDR Intra-Service Interface (PQDRII). Implementation of a standard DLMS format will 

facilitate transition to DLA Transaction Services subsequent to further coordination and 

evaluation as a separate action. 
Attachment, ADC 1007 

Page 4

 (a) Revisions to DLM 4000.25: General guidance and procedures applicable to 

the PQDR transaction exchange are documented in the DLMS manual chapter provided at 

Enclosure 1. For detailed procedures refer to Reference 3.a. 

 (b) Revisions to DLMS Supplements: The new DLMS 842P PQDR is 

provided as Enclosure 2. The enclosed version includes supplemental information to facilitate 

understanding. The actual DLMS Supplement is available at Reference 3.b. 

 (2) Exhibit Tracking: During staffing of PDC 1007, the DLA Logistics Management 

Standards Office proposed alternative functionality to support automated for exhibit tracking. 

Component response to this proposal was positive and the recommended changed are 

incorporated in this approved change. The additional requirement will leverage core logistics 

transactions for the desired exhibit tracking to minimize the manual effort needed to 

independently update PQDR applications with exhibit status. This functionality will be 

accomplished by including the PQDR Report Control Number (RCN) in the applicable DLMS 

transaction and by providing a copy of the transaction to Product Data Reporting and Evaluation 

Program-Automated Information System (PDREP-AIS). Upon receipt of the transaction, 

PDREP would notify any other applicable interfacing system via the PQDRII. The identification 

of PDREP will be accomplished by inclusion of the PDREP DoDAAC as a “Party to Receive 

Copy” in the transaction for dissemination to PDREP by DLA Transaction Services. 

 (a) Revisions to DLM 4000.25: Updates are identified in red bold italics. 

 Receipt: Revise Volume 2, Chapter 13 as follows: 

“C13.2.8.2.10.1. Condition of Materiel 

 (Intervening text not shown.) 

 C13.2.8.2.10.9. Product Quality Deficiency. An SCC Q entered in an ARI file shows 

that the receipt is related to a reported product quality deficiency. Report receipt of this 

materiel in SCC Q and do not cite a management code. Based on the results of the inspection 

or technical/engineering analysis, owners will direct the appropriate materiel disposition. 

 C13.2.8.2.10.9.1 Additionally, when the receipt is applicable to a Product 

Quality Deficiency Report (PQDR) exhibit, include the PQDR Report Control Number 

(RCN) and designate a copy of the receipt transaction for distribution to the Product Data 

Reporting and Evaluation Program-Automated Information System (PDREP-AIS). SCC 

Q is applicable to exhibits returned for evaluation and returned subsequent to testing. 

 C13.2.8.2.10.9.2 DAAS will recognize the inclusion of the PDREP-AIS 

DoDAAC in the receipt transaction and forward a copy of the transaction for use in 

exhibit tracking.” 

 Materiel Release Order: Revise Volume 2, Chapter 4 as follows: 

 “C4.7.14. Preparing MROs 
Attachment, ADC 1007 

Page 5

 (Intervening text not shown.) 

 C4.7.14.3. Product Quality Deficiency Report (PQDR) Exhibit Tracking. 

When directing release of a PQDR exhibit, the owner must include the PQDR Report 

Control Number (RCN) to facilitate exhibit tracking. When the shipment is processed 

for issue, the shipping activity will perpetuate the PQDR RCN from the MRO to the 

shipment status.” 

 Shipment Status: Revise Volume 2, Chapter 5 as follows:

 “C5.1.3.1. Preparation of Shipment Status 

 (Intervening text not shown.)

 C5.1.3.1.10. Product Quality Deficiency Report (PQDR) Exhibit Tracking 

 C5.1.3.1.10.1. When shipment status is prepared for shipment of a PQDR 

exhibit, the shipping activity will perpetuate the PQDR Report Control Number (RCN) 

from the MRO to the shipment status and designate a copy of the receipt transaction for 

distribution to the Product Data Reporting and Evaluation Program-Automated 

Information System (PDREP-AIS). 

 C5.1.3.1.10.2. DAAS will recognize the inclusion of the PDREP-AIS DoDAAC 

in the shipment status and forward a copy of the shipment status for use in exhibit 

tracking.” 

 (b) Revisions to DLMS Supplements. The following changes are approved for 

the DLMS 527R Receipt, DLMS 940R Materiel Release Order, and DLMS 856S Shipment 

Status. 

# Location 527R Revision Explanation 

1. DLMS 

Introductory 

Note: 

Add ADC 1007 to DLMS Introductory notes. 

- ADC 1007, New DLMS 842P, PQDR Data Exchange and 

Enhanced Exhibit Tracking via Standard Logistics Transactions 

To identify 

DLMS changes 

included in the 

DLMS 

Supplement. 

2. 1/N101/210 Insert new DLMS note 4. 

ZD Party to Receive Reports 

DLMS Note: 

1. Use in MRA transactions to cite additional organizations requiring 

MRA. 

2. Use in Navy Commercial Asset Visibility (CAV) receipts to 

identify the party to receive report. CAV expresses party to receive 

report as a DoDAAC (N903 code 10). CAV use is an authorized 

DLMS migration enhancement. See DLMS introductory note 5g. 

3. Used between Navy and DLA for Navy MRAs submitted directly 

Expands usage 

to provide a 

copy of the 

receipt 

transaction to 

PDREP-AIS. 
Attachment, ADC 1007 

Page 6

# Location 527R Revision Explanation 

to other Component SoS, so that DLA will be able to support followon actions on behalf of the Navy under a DLA industrial activity 

support agreement. Refer to ADC 377. 

4. Use in receipt transactions to identify additional organizations 

requiring notification of receipt when the receipt is related to a 

PQDR exhibit. 

3. 1/N106/210 Insert new DLMS note 3. 

PK Party to Receive Copy 

DLMS Note: 

1. Use when appropriate to send an information copy of the 

transaction to a Component UIT registry. 

For use with N101 code KK. 

2. Authorized DLMS enhancement for Air Force and DSS use with 

PIC NWRM UIT. For PIC UIT, must 

use in conjunction with 2/N101 code KK and 1/BR06/20 Action 

Code FI and cite the applicable Routing 

Identifier in 2/N103. 

3. Use to provide a copy of the receipt to Product Data Reporting 

and Evaluation Program-Automated Information System (PDREPAIS) for PQDR exhibit tracking when the PQDR Report Control 

Number (RCN) is included. For use with N101 code ZD and 

DoDAAC N45112. Refer to ADC 1007. 

4. Except as noted above, DLMS enhancement; see introductory 

DLMS note 5a. 

Same as above. 

4. 2/N901/90 Add Qualifier “QR” and DLMS Note: 

QR Quality Report Number

DLMS Note: 

1. When applicable, use to cite the associated PQDR report control 

number (RCN) for exhibit tracking. 

2. Authorized DLMS enhancement. Refer to ADC 1007. 

Links the 

receipt to a 

specific PQDR. 

# Location 940R Revision Explanation 

1. DLMS 

Introductory 

Note: 

Add ADC 1007 to DLMS Introductory notes. 

- ADC 1007, New DLMS 842P, PQDR Data Exchange and 

Enhanced Exhibit Tracking via Standard Logistics Transactions 

To identify 

DLMS changes 

included in the 

DLMS 

Supplement. 

2. 2/N901/0400 Add Qualifier “QR” and DLMS Note: 

QR Quality Report Number

DLMS Note: 

1. When applicable, use to cite the associated PQDR report control 

number (RCN) for exhibit tracking. 

Links the 

release order to 

a specific 

PQDR so that 

the PQDR can 

be perpetuated 
Attachment, ADC 1007 

Page 7

# Location 940R Revision Explanation 

2. Authorized DLMS enhancement. Refer to ADC 1007. to the shipment 

status. 

# Location 856S Revision Explanation 

1. DLMS 

Introductory 

Note: 

Add ADC 1007 to DLMS Introductory notes. 

- ADC 1007, New DLMS 842P, PQDR Data Exchange and 

Enhanced Exhibit Tracking via Standard Logistics Transactions 

To identify 

DLMS changes 

included in the 

DLMS 

Supplement. 

2. 2/REF01/1500 Add Qualifier “QR” and DLMS Note: 

QR Quality Report Number

DLMS Note: 

1. When applicable, use to cite the associated PQDR report control 

number (RCN) for exhibit tracking. 

2. Authorized DLMS enhancement. Refer to ADC 1007. 

Links the 

shipment status 

to a specific 

PQDR. 

3. 2/N101/2200 Insert new DLMS note 4. 

Z1 Party to Receive Status 

DLMS Note: 

1. Use to indicate the organization to receive shipment status. 

2. For shipment status forwarded for DAAS distribution to status 

recipients under MILSTRIP/DLMS distribution rules (AS8), the 

recipients will be identified on the DAAS-generated transactions and 

will not appear on the original transaction. 

3. As a DLMS enhancement, may be used to identify recipients other 

than the prescribed status recipients under DLMS/MILSTRIP 

distribution rules. Use multiple iterations of the 2/N1/2200 loop to 

identify shipment recipients, as needed. Use with N106=TO to 

indicate that the value in N104 is receiving the transaction. See 

introductory DLMS note 2a. 

4. Use to provide shipment status to Product Data Reporting and 

Evaluation Program-Automated Information System (PDREP-AIS) 

for PQDR exhibit tracking when the PQDR RCN is included. For 

use with DoDAAC N45112. Refer to ADC 1007. 

Expands usage 

to provide a 

copy of the 

shipment status 

transaction to 

PDREP-AIS. 

Administrative 

update to 

further clarify 

use of the 

Qualifier Z1. 

 c. PQDR Transaction Flow: Each system will route all transactions to the PQDR IntraService Interface. The Intra-service interface will validate the sender and recipient information 

and forward the transaction to the appropriate systems. Data transmission format may be X12 

EDI or XML with direct secure connection to between the source system (i.e. EBS, JDRS, 

PDREP) and PQDRII (pending future agreement for transition to the DLA Transaction Services 

processing hub).
Attachment, ADC 1007 

Page 8

 d. Alternatives: Continue current procedures with limited deficiency data exchanged 

between systems. 

 e. Comment Resolution: Refer to Enclosure 4 for concurrence and comments received 

during staffing.

5. REASON FOR CHANGE: Establishment of a standard electronic transaction for PQDR 

data will enhance the PQDR investigation process and enhance data communication between 

Component systems. This change will facilitate transition to the DAAS processing hub as 

envisioned for future enhancement by separate DLMS change. 

6. ADVANTAGES AND DISADVANTAGES:

 a. Advantages: 

 (1) Standardized data transactions will improve the current PQDR process through 

improved communication between systems. In addition, a standard transaction set will reduce 

timeframes and development costs as Components develop new automated information systems 

for processing PQDR data. 

 (2) The use of standard logistics transactions for PQDR exhibit tracking will eliminate 

a great deal of manual effort to update PQDR applications manually for each shipment and 

receipt of an exhibit and will ensure a more consistent outcome. 

 b. Disadvantages: No known disadvantage. 

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

DEVELOPMENT: 

a. Funding and resources: Adequate funding and resources are available to complete 

implementation in 2013. 

b. Business Rules: Components will complete business rule development in 2012. 

c. DLMS Requirement. The adoption of a DLMS-compliant PQDR information 

exchange does not supersede or take precedence over the PQDR program guidance under 

Reference 3.a. Upon successful implementation of the DLMS 842P within the PQDRII and 

associated Service/Agency applications, additional evaluation and coordination via a DLMS 

Change proposal will be needed to transition processing by DLA Transaction Services. 

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: Upon successful implementation 

of revised exhibit tracking procedures, the use of the DLMS 842A/W with Discrepancy Code 

Q11 for PQDR exhibit receipt notification will be terminated. Follow-on DLMS Changes may 

be needed to further refine the exhibit tracking procedures and update procedures associated with 

the PQDR information exchange. 
Attachment, ADC 1007 

Page 9

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The following timeline is 

provided for PQDR transaction implementation. These dates are subject to change due to 

resource constraints:

 ADC publication – September-October, 2012 

 Code values set – October-November, 2012 

 Business rule completion – November 31, 2012 

 Programming completion – March, 31, 2013 

 Developmental testing – Feb 1, 2013 

 System testing – March 31, 2013 

 Go-live – June 8, 2013 

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available.

11. IMPACT: 

 a. New DLMS Data Elements: Refer to Enclosure 3. 

 b. Changes to DLMS Data Elements: Refer to Enclosure 3. 

c. Component Automated Information Systems (AIS): 

 (1) PQDR: Initial implementation will include the DLA EBS, SECNAV PDREP, and 

NAVAIRSYSCOM JDRS. Initially, all transactions will pass through the PQDR Inter-service 

Interface (PQDR II). After the transaction data set, business rules, and PQDR II functionality are 

stabilized, the DOD PQDR committee will review and determine whether DLA Transaction 

Services will assume responsibility for the PQDR II functionality and transaction processing. 

Components developing new PQDR processing systems will comply with this DLMS standard to 

exchange data with other DOD PQDR systems. 

 (2) Enhanced Exhibit Tracking: 

 (a) Implementation requires the DLMS-compliant receiving activities, including 

the Distribution Standard System (DSS), to record the PQDR RCN in the receipt. When the 

PQDR RCN is populated, the application must systemically identify PDREP by DoDAAC to 

receive an information copy of the receipt (DLMS 527R). 

 (b) DLMS-compliant Inventory Control Point (ICP) applications must include the 

PQDR RCN in the MRO (DLMS 940R) used to direct shipment of exhibits from the storage 

activity, e.g., to a commercial lab for testing. 

 (c) DLMS-compliant storage activity applications, including DSS, must be 

updated to perpetuate the PQDR RCN from the MRO to the shipment status transaction (DLMS 

856S). When the PQDR RCN is populated, the application must systemically identify PDREP 

by DoDAAC to receive an information copy of the shipment status 

 
Attachment, ADC 1007 

Page 10

d. DLA Transaction Services: 

 (1) PQDR: No initial impact for PQDR processing. A separate DLMS Change will 

be submitted to adopt DAAS as the processing hub and address any additional process 

enhancements. 

 (2) Exhibit Tracking: Functionality to provide additional information copies is 

required for the DLMS 527R and 856S.
Enclosure 1, PDC 1007 

Page 1

Enclosure 1, DLMS Manual Chapter 

The following chapter will be added to the DLM 4000.25, Volume 2. The chapter number is 

notional and may be revised for formal publication. 

C25. CHAPTER 25 

PRODUCT QUALITY DEFICIENCY REPORT PROGRAM 

C25.1. GENERAL. This chapter provides general information supporting the DoD Product 

Quality Deficiency Report (PQDR) Program. The authoritative source for detail procedures 

pertaining to this program is DLAR 4155.24/AR 702-7/SECNAVINST 4855.5 series/AFI 21-

115, Product Quality Deficiency Report Program (refer to the DLA PQDR Home Page). The 

DoD PQDR program requires DoD Component 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 

DLMS transaction exchange supporting the PQDR program. 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 Inter-service Interface (PQDR II). 

Components developing new PQDR processing systems will comply with this DLMS standard to 

exchange data with other DoD PQDR systems. 

 

C25.2. PQDR Transaction Set. The PQDR transaction set is used to move the PQDR (SF-368) 

data between points (originator/originating point, screening point, action point, and support 

point), facilitate PQDR exhibit movements, and exchange general information (interim 

responses, general correspondence, etc.). For each transmission, the receiving system will 

provide a transaction to the submitting system acknowledging data receipt. DLMS Supplement 

842P, PQDR Data Exchange, replaces the system unique transactions currently used to exchange 

date. This DLMS enhancement provides the DoD Components with a standard electronic 

transmission method for reporting PQDRs across systems. 

C25.3. APPLICABILITY AND SCOPE. This guidance is applicable to all DoD Components 

responsible for reporting and processing PQDR information. It applies to all supply classes not 

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

4855.5 series/AFI 21-115. 

C25.4. PQDR OVERVIEW. The originator/originating point discovers a deficiency and 

submits the PQDR to the appropriate screening point. The screening point determines the 

appropriate action point (normally the item manager) and forwards the report for investigation. 

The action point will either investigate the report or assign the report to a support point (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 updated with the current investigation status. Under 
Enclosure 1, PDC 1007 

Page 2

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. 

C25.5. DETAILED REQUIREMENT. PQDR data exchanged electronically between EBS, 

PDREP, and JDRS will pass through the PQDR II. The sending system is responsible for 

complying with the 842P 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. The PQDR II will validate each transaction for required data elements and reject 

incomplete transactions to the sending system. In addition, the PQDR II will maintain a record 

of the IT systems having received a prior transaction for each RCN and route a copy of all 

subsequent transactions to the IT system. 

C25.5.1. PQDR Movement Transactions. The DLMS 842P moves the PQDR between the 

different investigating points. 

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

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

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

 

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

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

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

C25.4.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. 
Enclosure 1, PDC 1007 

Page 3

C25.5.1.8. Reply Rebuttal (Transaction Set Purpose Code RR). Used to rebut an 

investigation response. PQDR placed at the prior ownership level. 

C25.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 PDREP-AIS, they will be used to update the 

exhibit movement and disseminated as appropriate. 

C25.5.2.1. Exhibit Request (Transaction Set Purpose Code 13). Used to request the 

exhibit and provide shipping information. 

C25.5.2.2. Exhibit Shipped Notification (Transaction Set Purpose Code 14). Used to 

provide exhibit shipment information to the requestor. 

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

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

C25.5.2.5. Materiel Disposition (Transaction Set Purpose Code MD). Used to provide 

final material disposition instructions. Used by the support or action point after the investigation 

is complete. 

C25.5.2.6. Exhibit Disposition Confirmation (Transaction Set Purpose Code ED) Used 

by the current exhibit holder to confirm compliance with material disposition instructions. 

C25.5.3. General Information Transactions. The PQDR general information transactions 

provide information or status regarding the PQDR without changing ownership. 

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

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

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

C25.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. 
Enclosure 1, PDC 1007 

Page 4

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

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

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

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

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

C25.5.3.10. Forward to Contractor (Transaction Set Purpose Code FC). Used when 

support point sends PQDR investigation request to a contractor. 

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

C25.5.4. System Transactions. System transactions are used to confirm data receipt and 

communicate transaction failures to the sending system. 

 

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

 C25.5.4.1. Confirmation of Transaction Receipt (Transaction Set Purpose Code 06). Used 

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

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

depot, 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. 
Enclosure 1, PDC 1007 

Page 5

C21.25.7. PQDR Inter-Service Interface Query Capability. The PQDR II will allow users to 

query the transaction history by RCN, the system inbox to view pending incoming transactions, 

and the system outbox to view pending outgoing transaction. 
DLMS Supplement 842P, PQDR Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 1 

Enclosure 2. DLMS Supplement 842P, PQDR Data Exchange 

842 Nonconformance Report

Functional Group=NC

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Nonconformance Report Transaction Set (842) for use 

within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report products and processes that do not fulfill 

specifications or requirements. The Nonconformance Report Transaction Set provides the ability for the sender to report the nonconformance at the level of 

detail that is required. It also provides the ability to report the specific nonconformances of a component/part while identifying the assembly as the product that 

is in nonconformance. The Nonconformance Report Transaction Set may be used to report, initiate, or request actions related to the nonconformance being 

reported. Financial and accounting information is provided for reporting purposes only.The Nonconformance Report Transaction Set has the capability to 

report the cause of the nonconformance and to state the proposed action to be followed to prevent a repetition of the problem.

Federal Note:

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

including results of investigation and exhibit tracking. 

2. Use a single occurrence (transaction set) of this transaction set to transmit single reports or responses to single or multiple organizations. 

3. DoD logistics users should refer to the Defense Logistics Management System (DLMS) Supplement to the Federal Implementation Convention (FIC) 

available at http://www.dla.mil/j-6/dlmso/eApplications/LOG.NET/UIL/Default.aspx. The DLMS Supplement provides specific business rules, conditions, 

and authorized codes necessary for appropriate use of this FIC within the DLMS.

DLMS Note:

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

related to PQDR Exhibit processing. PQDR originators, screening points, action points, support points, and other interested parties use this transaction set 

to exchange product quality deficiency information. 

2. Users operating under the DLMS must reference the Unit of Issue and Purchase Unit Conversion Table, Transportation Mode of Shipment Conversion 

Table, and Accounting Classification Appendix which can be found on the DLMS web site at http://www.dla.mil/j6/dlmso/eLibrary/TransFormats/140_997.asp. 

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

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

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

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

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

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

system. 

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

the DLMSO website: http://www.dla.mil/j-6/dlmso/eLibrary/changes/processchanges.asp. 

 - PDC 1007, New Transaction 4030 842P, Product Quality Deficiency Report (PQDR) Data Exchange 

 
DLMS Supplement 842P, PQDR Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 2 

EDI Control Segment Notes 

Staffing Note: This following guidance is provided for information, but will not be included in the actual DLMS Supplement.

The 842P transaction set must be preceded with Electronic Data Interchange (EDI) ISA and GS segments and then followed by GE and IEA 

segments. These segments are not included in the842P transaction set. These EDI segments define which PQDR system the 842P transaction 

is destined for and how many lines are contained within the transaction. Below is a brief explanation of the ISA/IEA and GS/GE control 

segments used in an ANSI X12 EDI interchange. . 

The ISA segment is used to envelope and identifies data to be sent to one trading partner. It is the only segment in the envelope that is a 

fixed-length (specifically, 104 characters/bytes). The length of the segment is determined by summing all data element fields and adding the 

number of element delimiters used to separate those data elements. The ISA segment begins the envelope and the IEA segment closes the 

envelope. 

Data Element Size Name & Notes 

ISA-01 2 Authorization Information Qualifier. 00- means no info present in ISA-02 

ISA-02 10 Authorization Information spaces mean no information 

ISA-03 2 Security Information Qualifier 00- means no security info present in ISA-04 

ISA-04 10 Security Information spaces mean no security information 

ISA-05 2 Interchange ID Qualifier. This is a code used to identify the type of information used in ISA-06 

 ZZ- means mutually-defined. 

ISA-06 15 Interchange Sender's ID. ID used to identify the sending trading partner 

ISA-07 2 Interchange ID Qualifier. This is a code used to identify the type of information used in ISA-08 

 ZZ- means mutually-defined 

ISA-08 15 Interchange Receiver's ID. ID used to identify the receiving trading partner 

ISA-09 6 Interchange Date. Envelope creation date (YYMMDD) 

ISA-10 4 Interchange Time. Envelope creation time (HHMM) 

ISA-11 1 Interchange Control Standards ID. Identifies the agency responsible for the control standard used to 

 create this ISA segment OR 

ISA-11 1 Repetition (X12 Version 4030 only). The character used to separate repeating elements within the envelope. 

ISA-12 5 Interchange Control Version Number. Version number of the standard used to create this ISA segment 

ISA-13 9 Interchange Control Number. The control number assigned to this envelope by the sender 

ISA-14 1 Acknowledgement Requested. Code sent by sender to request an envelope acknowledgment (TA1) 

 0- means no acknowledgment requested 

ISA-15 1 Usage Indicator. Code used to indicate if this envelope is for Transaction Set Purpose Code T-test, P-production, 

 I-information 

ISA-16 1 Component Element Separator. This is character used to separate data elements in a "composite data element" 

IEA-01 1/5 Number of Included Function Groups. Number of groups enclosed in this envelope 

IEA-02 9 Interchange Control Number. The control number assigned to this envelope by the sender (same as ISA-13) 

Description: The GS segment is used to group and identify data of one transaction type (I.e. Invoices, PQDR and SDR Report's, etc.) The 

GS segment begins the group and the GE segment closes the group. 

Data Element Size Name & Notes 

GS-01 2 Functional ID Code identifying what application-related group the enclosed transactions belong to 

(example is Function Group "NC" of which transaction-set 842 is a member) 

GS-02 2/15 Application Sender's Code. String identifying the sender of this group of transactions 

GS-03 2/15 Application Receiver's Code. String identifying the receiver of this group of transaction 

GS-04 8 Date Group creation date (CCYYMMDD) 

GS-05 8 Time Group creation time (HHMMSSDD) 

GS-06 1/9 Group Control Number the control number assigned to this group by the sender 

GS-07 1/2 Responsible Agency Code. Code used to identify the issuer of the standard used to create 
DLMS Supplement 842P, PQDR Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 3 

 the enclosed group of transactions 

GS-08 1/12 Version/Release/Industry ID Code. Code indicating the version of the standard used to create the 

 enclosed group of transactions 

GE-01 1/6 Number of Transaction Sets Included. Number of transactions enclosed in this group 

GE-02 1/9 Group Control Number. The control number assigned to this group by the sender (same as GS-06). 

842P Heading:

 

Pos Id Segment Name Req Max 

Use

Repeat Notes Usage

 0100 ST Transaction Set 

Header 

M 1 Indicates the start of a transaction set and to assign a transaction 

control number. 

Must use 

 0200 BNR Beginning Segment 

For 

Nonconformance 

Report 

M 1 Indicates the beginning of the Nonconformance Report. Must use 

* 0300 REF Reference 

Identification 

O >1 Not Used 

* 0400 DTM Date/Time 

Reference 

O >1 Not Used 

* 0500 PID Product/Item 

Description 

O >1 Not Used 

* LOOP ID - MEA >1

* 0600 MEA Measurements O 1 Not Used 

* 0700 DTM Date/Time 

Reference 

O >1 Not Used 

* 0800 REF Reference 

Identification 

O >1 Not Used 

 

* LOOP ID - PWK >1

* 0900 PWK Paperwork O 1 Not Used 

* 1000 REF Reference 

Identification 

O >1 Not Used 

* 1100 DTM Date/Time 

Reference 

O >1 Not Used 

 

LOOP ID - N1 >1

 1200 N1 Name O 1 Identifies organization sending and receiving the transaction set. 

Identifies the primary actors of the PQDR: originator, screening point, 

action point, support points, and info copy recipients to receive a copy 

of the report. 

Used 

* 1300 N2 Additional Name 

Information 

O 2 Not Used 

* 1400 N3 Address 

Information 

O 2 Not Used 

* 1500 N4 Geographic 

Location 

O 1 Not Used 

* 1600 REF Reference 

Identification 

O >1 Not Used 

 1700 PER Administrative 

Communications 

Contact 

O >1 Identifies a person or office that the administrative communications 

should be directed. 

Used 

 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 4 

842P Detail:

Pos Id Segment Name Req Max 

Use

Repeat Notes Usage

LOOP ID - HL >1 N2/0100L

 0100 HL Hierarchical Level M 1 Identifies dependencies among and the content of hierarchically related 

groups of data segments. 

Used 

 0200 LIN Item Identification O 1 Specifies nonconforming item identification data and some additional 

related information such as next higher assembly. 

Used 

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

* 0400 PRS Part Release Status O >1 Not Used 

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

 0600 DTM Date/Time Reference O >1 Identifies dates associated with the complaint. Used 

 0700 REF Reference Identification O >1 Identifies additional reference numbers and codes associated with a 

complaint. Includes document number and end item. 

Used 

 0750 CS Contract Summary O 1 Provides information about a contract. Used 

* 0800 QTY Quantity O >1 Not Used 

* 0900 TMD Test Method O 1 Not Used 

* 1000 PSD Physical Sample Description O 1 Not Used 

 1020 PWK Paperwork O >1 Identifies associated attachments or paperwork sent separately or by 

another method. 

Used 

LOOP ID - LM >1

 1040 LM Code Source Information O 1 Syntax requirement to use DoD code sets. Used 

 1050 LQ Industry Code M >1 Identifies standard DoD codes related to the nonconforming item. Used 

* LOOP ID - MEA >1

* 1100 MEA Measurements O 1 Not Used 

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

* 1300 REF Reference Identification O >1 Not Used 

 

* LOOP ID - FA1 >1

* 1350 FA1 Type of Financial Accounting 

Data 

O 1 Not Used 

* 1360 FA2 Accounting Data M >1 Not Used 

 

* LOOP ID - SPS >1

* 1400 SPS Sampling Parameters for 

Summary Statistics 

O 1 Not Used 

* 1500 REF Reference Identification O >1 Not Used 

* 1600 PSD Physical Sample Description O 1 Not Used 

* LOOP ID - MEA >1

* 1700 MEA Measurements O 1 Not Used 

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

* 1900 REF Reference Identification O >1 Not Used 

 

LOOP ID - STA >1

* 2000 STA Statistics O 1 Not Used 

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

* 2200 REF Reference Identification O >1 Not Used 

 

LOOP ID - NCD >1

 2300 NCD Nonconformance Description O 1 Describes the nonconformance condition. Used 

 2400 NTE Note/Special Instruction O >1 Transmits information in a free-form format for comment, narrative, or 

special instruction concerning the original nonconformance. 

Used 

 2500 DTM Date/Time Reference O >1 Not Used 

 2600 REF Reference Identification O >1 Use in IUID loop to associate a reference numbers with a specific 

batch/lot or item as identified by UII or serial number. 

Used 

 2700 QTY Quantity O >1 Specifies quantity information. Used 

 2730 AMT Monetary Amount O >1 Indicates the monetary amounts. Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 5 

* 2740 MEA Measurements O >1 Not Used 

* 2750 RC Root Cause O >1 Not Used 

* LOOP ID - EFI >1

* 2760 EFI Electronic Format Identification O 1 Not Used 

* 2770 BIN Binary Data M 1 Not Used 

 

LOOP ID - N1 >1

 2800 N1 Name O 1 Use to identify parties other than the originator, screening point, action 

point and support point. Use in IUID loop to identify the enterprise 

identifier. 

Used 

 2900 N2 Additional Name Information O 2 Use to identify address line 1. Used 

 3000 N3 Address Information O 2 Use to identify address line 2. Used 

 3100 N4 Geographic Location O 1 Use to identify city, state, zip, and country. Used 

* 3200 REF Reference Identification O >1 Not Used 

 3300 PER Administrative Communications 

Contact 

O >1 Identifies a person or office that the administrative communications 

should be directed. 

Used 

 

LOOP ID - LM >1

 3330 LM Code Source Information O 1 Not Used 

 3340 LQ Industry Code M >1 Not Used 

* LOOP ID - NCA >1

 3400 NCA Nonconformance Action O 1 Describes the action that is to be undertaken. Used 

 3500 NTE Note/Special Instruction O >1 Responses to the original complaint. Used 

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

* 3700 REF Reference Identification O >1 Not Used 

* LOOP ID - PWK >1

* 3800 PWK Paperwork O 1 Not Used 

* 3900 REF Reference Identification O >1 Not Used 

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

 

* LOOP ID - N1 >1

* 4100 N1 Name O 1 Not Used 

* 4200 N2 Additional Name Information O 2 Not Used 

* 4300 N3 Address Information O 2 Not Used 

* 4400 N4 Geographic Location O 1 Not Used 

* 4500 REF Reference Identification O >1 Not Used 

* 4600 PER Administrative Communications 

Contact 

O >1 Not Used 

 

LOOP ID - LM >1

* 4640 LM Code Source Information O 1 Not Used 

* 4650 LQ Industry Code M >1 Not Used 

 

* LOOP ID - FA1 >1

* 4660 FA1 Type of Financial Accounting 

Data 

O 1 Not Used 

* 4670 FA2 Accounting Data M >1 Not Used 

 4700 SE Transaction Set Trailer M 1 Indicates the last segment of a transaction set Used 

Notes: 

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

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

serial number. 

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

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

serial number. 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 6 

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

 

User Option (Usage): Must use

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

 

Semantics: 

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

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

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

convention to match the transaction set definition. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 ST01 143 Transaction Set Identifier Code 

Description: Code uniquely identifying a Transaction Set 

 

M ID 3/3 Must use 

 CodeList Summary (Total Codes: 314, Included: 1) 

Code Name

 842 Nonconformance Report 

 

 ST02 329 Transaction Set Control Number 

Description: Identifying control number that must be 

unique within the transaction set functional group assigned 

by the originator for a transaction set 

Federal Note: A unique transaction number assigned by 

the originating system of the transaction set, or the 

originator's application program, 

i.e., 200900001. 

 

M AN 4/9 Must use 

 ST03 1705 Implementation Convention Reference 

Description: Reference assigned to identify 

Implementation Convention 

Federal Note: Use to indicate which version of the 842P 

DLMS Supplement is used to create the transaction, i.e., 

004030F842P0. 

 

O AN 1/35 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 7 

BNR Beginning Segment For Nonconformance Report Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

 

User Option (Usage): Must use

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

 

Semantics: 

1. BNR02 is the nonconformance report identifier number. 

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

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

Comments: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 BNR01 353 Transaction Set Purpose Code 

Description: Code identifying purpose of transaction set 

Federal Note: Use any code. 

DLMS Note: For DLMS use, the following Transaction 

Codes are authorized to describe the PQDR Transaction 

Code. 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 74, Included: 28) 

Code Name

 00 Original 

DLMS Note:

Use when the Originator Forwards to Screening Point in another system or when Originator and 

Screening Point do not exist within the same system.

 01 Cancellation 

DLMS Note:

Use when PQDR is Cancelled in one system and cancelation needs to be propagated to other systems. 

Only screening points may cancel a PQDR.

 03 Delete 

DLMS Note:

Retraction used to change ownership a PQDR back to the previous processing point or location.

 06 Confirmation 

DLMS Note:

Used by an automated IT system to indicate Confirmation of Transaction Receipt from another system.

 08 Status 

DLMS Note:

Use for Acknowledge/Status indicating that a PQDR was received and to provide current status.

 10 Not Found 

DLMS Note:

Use to send an Exhibit Tracer request.

 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.

 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.

 13 Request 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 8 

DLMS Note:

Use to identify an Exhibit Request.

 14 Advance Notification 

DLMS Note:

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

 22 Information Copy 

DLMS Note:

Use to send an 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.

 44 Rejection 

DLMS Note:

Used for a Rejection when PQDRII determines that 842P transaction is non-compliant with this 

standard or when a recipient system of an 842P is unable to process a transaction due to its unique 

data requirements. This transaction is system generated. End user transaction should use 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.

 47 Transfer 

DLMS Note:

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

 CN Completion Notification 

DLMS Note:

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

 CO Corrected 

DLMS Note:

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

the receiver, and to send corrections with an explanation of changes. Used by originators, screening, 

action, or support point.

 DA Delegate to Alternate 

DLMS Note:

1. Use to Delegate to Alternate Support Point by the responsible Support Point. 

2. At this time a local code DA is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘DA - Delegate to Alternate’ in a future version.

 ED Exhibit Disposition 

DLMS Note:

1. Use for Exhibit Disposition Confirmation to indicate compliance with instructions. 

2. At this time a local code ED is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘ED - Exhibit Disposition’ in a future version.

 ER Exhibit Receipt 

DLMS Note:

1. Use to indicate an Exhibit Receipt. 

2. At this time a local code ER is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘ER - Exhibit Receipt’ in a future version.

 FA Forward to Action Point 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 9 

DLMS Note:

1. Use to Forward from Screening Point to Action Point. Assigns a PQDR to an action point by a 

screening point. 

2. At this time a local code FA is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘FA - Forward to Action Point’ in a future version.

 FC Forward to Contractor 

DLMS Note:

1. Use when PQDR is Forwarded to Contractor. 

2. At this time a local code FC is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘FC - Forward to Contractor’ in a future version.

 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. 

2. At this time a local code FS is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘FS - Forward to Support Point’ in a future version.

 MD Materiel Disposition 

DLMS Note:

1. Use to provide Materiel Disposition. Used by the Support or Action Point after the investigation is 

complete. 

2. At this time a local code ‘MD is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘MD - Materiel Disposition’ in a future version.

 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 request to re-open a PQDR when sent by originator, action, or support 

points to a screening point. 

2. At this time a local code RO is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘RO - Reopen’ in a future version.

 RR Reply Rebuttal 

DLMS Note:

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

2. At this time a local code RR is established for use in the 842P, version 4030. A data maintenance 

action has been submitted for establishment of ‘RR - Reply Rebuttal’ in a future version.

 SU Status Update 

DLMS Note:

Use to send an Update to correct or append specific data fields in another IT system. 

 BNR02 127 Reference Identification 

Description: Reference information as defined for a 

particular Transaction Set or as specified by the Reference 

Identification Qualifier 

DLMS Note: Enter "Z" to satisfy ANSI 

 

M AN 1/50 Must use 

 BNR03 373 Date 

Description: Date expressed as CCYYMMDD where CC 

represents the first two digits of the calendar year 

Federal Note: This date corresponds to the Universal 

Time Coordinate (UTC). i.e. 20091231 for April 02, 2012 

 

M DT 8/8 Must use 

 BNR04 337 Time 

Description: Time expressed in 24-hour clock time as 

follows: HHMM, or HHMMSS, or HHMMSSD, or 

O TM 4/8 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 10 

HHMMSSDD, where H = hours (00-23), M = minutes 

(00-59), S = integer seconds (00-59) and DD = decimal 

seconds; decimal seconds are expressed as follows: D = 

tenths (0-9) and DD = hundredths (00-99) 

Federal Note: 1. Express the originating activity's time in 

Universal Time Coordinate (UTC). 

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

0859 for 08:59 AM. 

 

 BNR05 886 Nonconformance Report Status Code 

Description: Code identifying the status of the 

nonconformance report 

 

O ID 2/2 Used 

 CodeList Summary (Total Codes: 9, Included: 4) 

Code Name

 CL Closed 

DLMS Note:

Use to indicate that the PQDR is in a closed status. More detailed status codes are available in the 

section REF 0700.

 FI Final 

DLMS Note:

Use to indicate that the PQDR investigation is completed. More detailed status codes are available in 

the section REF 0700.

 OI Open, Waiting for Cause and Corrective Action Implementation 

DLMS Note:

Use to indicate that the PQDR investigation is not complete. More detailed status codes are available 

in the section REF 0700.

 RE Reopened 

DLMS Note:

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

detailed status codes are available in the section REF 0700. 

 BNR06 640 Transaction Type Code 

Description: Code specifying the type of transaction 

 

O ID 2/2 Used 

 CodeList Summary (Total Codes: 500, Included: 2) 

Code Name

 QD Product Quality Deficiency 

DLMS Note:

Use to indicate that the transaction set contains a PQDR.

 QR Product Quality Deficiency Response 

DLMS Note:

Use to indicate the transaction set contains a PQDR Response.
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 11 

N1 Name Pos: 1200 Max: 1

Heading - Optional

Loop: N1 Elements: 5

 

User Option (Usage): Used

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

Syntax Rules: 

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

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

 

Comments: 

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

must provide a key to the table maintained by the transaction processing party. 

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

Federal Note:

Must use separate iterations of this 1/N1/1200 loop to identify the organizations sending and receiving the transaction set and to identify other parties 

involved with the processing of the PQDR.

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 N101 98 Entity Identifier Code 

Description: Code identifying an organizational entity, a 

physical location, property or an individual 

DLMS Note: For DLMS use the following codes are 

authorized. Sender and receiver must be identified in 

N106 by using the TO and FR. 

 

M ID 2/3 Must use 

 CodeList Summary (Total Codes: 1446, Included: 6) 

Code Name

 41 Submitter 

DLMS Note:

Use to identify the DoDAAC of the current Originator DoDAAC.

 91 Action Party 

DLMS Note:

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

the investigation and resolution of the deficiency.

 92 Support Party 

DLMS Note:

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

investigation.

 RN Repair or Refurbish Location 

DLMS Note:

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

 ZD Party to Receive Reports 

DLMS Note:

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

842P.

 ZQ Screening Point 

DLMS Note:

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

 N102 93 Name 

Description: Free-form name 

 

X AN 1/60 Used 

 N103 66 Identification Code Qualifier 

X ID 1/2 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 12 

Description: Code designating the system/method of code 

structure used for Identification Code (67) 

 

 CodeList Summary (Total Codes: 223, Included: 2) 

Code Name

 10 Department of Defense Activity Address Code (DODAAC) 

 33 Commercial and Government Entity (CAGE) 

 

 N104 67 Identification Code 

Description: Code identifying a party or other code 

DLMS Note: Default for PQDR is to use the DoDAAC i.e. 

N00104. 

 

X AN 2/80 Used 

 N106 98 Entity Identifier Code 

Description: Code identifying an organizational entity, a 

physical location, property or an individual 

 

O ID 2/3 Used 

 CodeList Summary (Total Codes: 1446, Included: 2) 

Code Name

 FR Message From 

Federal Note:

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

originating the transaction set.

 TO Message To 

Federal Note:

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

of the transaction set.
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 13 

PER Administrative Communications Contact Pos: 1700 Max: >1

Heading - Optional

Loop: N1 Elements: 9

 

User Option (Usage): Used

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

Syntax Rules: 

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

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

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

 

DLMS Note:

Use multiple repetitions as needed to identify applicable points of contact and communication numbers. Must provide email address and at least one phone 

number.

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 PER01 366 Contact Function Code 

Description: Code identifying the major duty or 

responsibility of the person or group named 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 234, Included: 5) 

Code Name

 ES Electronic Submission Recipient 

DLMS Note:

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

(TO). Use with a "ZQ" identified in line N101.

 FC Forwarder Contact 

DLMS Note:

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

Use with a "91" identified in line N101.

 PI Preparer 

DLMS Note:

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

Use with a "41" identified in line N101.

 QA Quality Assurance Contact 

DLMS Note:

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

Use with a "92" identified in line N101.

 RQ Requestor 

DLMS Note:

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

identified in line N101. 

 PER02 93 Name 

Description: Free-form name 

DLMS Note: Provide the last name, first name, middle 

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

point of contact. Include blank spaces between name 

components and periods after initials. 

 

O AN 1/60 Used 

 PER03 365 Communication Number Qualifier 

Description: Code identifying the type of communication 

number 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 40, Included: 1) 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 14 

Code Name

 EM Electronic Mail 

DLMS Note:

Use to identify the E-mail address. 

 PER04 364 Communication Number 

Description: Complete communications number including 

country or area code when applicable 

 

X AN 1/256 Used 

 PER05 365 Communication Number Qualifier 

Description: Code identifying the type of communication 

number 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 40, Included: 1) 

Code Name

 TE Telephone 

DLMS Note:

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

 PER06 364 Communication Number 

Description: Complete communications number including 

country or area code when applicable 

 

X AN 1/256 Used 

 PER07 365 Communication Number Qualifier 

Description: Code identifying the type of communication 

number 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 40, Included: 1) 

Code Name

 AU Defense Switched Network 

DLMS Note:

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

 PER08 364 Communication Number 

Description: Complete communications number including 

country or area code when applicable 

 

X AN 1/256 Used 

 PER09 443 Contact Inquiry Reference 

Description: Additional reference number or description 

to clarify a contact number 

DLMS Note: Use as needed to identify the office 

symbol/activity code for the party identified or the position 

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

Specialist. 

 

O AN 1/20 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 15 

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

 

User Option (Usage): Must use

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

 

Comments: 

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

packaging data to line-item data. 

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

3. HL01 will contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to 

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

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

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

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

For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or itemlevel information. 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 HL01 628 Hierarchical ID Number 

Description: A unique number assigned by the sender to 

identify a particular data segment in a hierarchical 

structure 

DLMS Note: Cite numeric '1' to satisfy ANSI syntax 

requirement. 

 

M AN 1/12 Must use 

 HL03 735 Hierarchical Level Code 

Description: Code defining the characteristic of a level in 

a hierarchical structure 

 

M ID 1/2 Must use 

 CodeList Summary (Total Codes: 218, Included: 3) 

Code Name

 I Item 

DLMS Note:

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

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

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

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

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

 W Transaction Reference Number 

DLMS Note:

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

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

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

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

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

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

segments are used in the document number loop.

 RP Report 

DLMS Note:

Mandatory use in all transactions to provide detail information associated with the transaction.
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 16 

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 30

 

User Option (Usage): Used

Purpose: To specify basic item identification data 

Syntax Rules: 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

 

Semantics: 

1. LIN01 is the line item identification 

Comments: 

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

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

Model No., or SKU. 

DLMS Note:

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

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 LIN02 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

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

identification. 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 506, Included: 3) 

Code Name

 FS National Stock Number 

DLMS Note:

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

nonconforming materiel. Equates to SF368, Block 5.

 FT Federal Supply Classification 

DLMS Note:

Use to identify the 4 character FSC portion of the NSN for the nonconforming materiel. Required when 

entire NSN is unavailable.

 NN National Item Identification Number 

 

DLMS Note:
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 17 

1. Use to identify the 4 character NIIN portion of the NSN for the nonconforming materiel. Required 

when entire NSN is unavailable. 

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

 LIN03 234 Product/Service ID 

Description: Identifying number for a product or service 

M AN 1/48 Must use 

 LIN04 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

DLMS Note: Use to further identify an item. Use multiple 

Product/Service ID pairs as needed. 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 MG Manufacturer's Part Number 

DLMS Note:

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

the deficient materiel). Equates to SF368, Block 8. 

 LIN05 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN06 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 MF Manufacturer 

DLMS Note:

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

 LIN07 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN08 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 CN Commodity Name 

DLMS Note:

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

Block 6. 

 LIN09 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN10 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 W2 Work Unit Number 

DLMS Note:

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. 

 LIN11 234 Product/Service ID X AN 1/48 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 18 

 

Description: Identifying number for a product or service 

 

 LIN12 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 OT Internal Number 

DLMS Note:

1. Use to identify the Air Force Reference Designator. 

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

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

refer to the Integrated Management Information System (IMIS). 

 LIN13 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN14 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

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

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

nonconforming materiel. 

Use the Qualifier PG in the N1 segment to provide an address that is different than the address 

officially listed with the CAGE in Central Contractor Registry (CCR)/Business Identification Number 

Cross- Reference System (BINCS). 

 LIN15 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN16 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

DLMS Note: Use the next five qualifiers when applicable 

to identify the Next Higher Assembly. 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 F8 Next Higher Used Assembly 

DLMS Note:

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

 LIN17 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN18 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 GE Generic Name Description 

DLMS Note:

Use to identify the Next Higher Assembly Nomenclature. Equates to SF368, Block 17b.
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 19 

 

 LIN19 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN20 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 EM Equipment Identification Number 

DLMS Note:

Use to identify Next Higher Assembly Serial Number. Equates to SF368, Block 17d. 

 LIN21 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN22 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 PU Part Reference Number 

DLMS Note:

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

 LIN23 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN24 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 XZ Contractor Establishment Code 

DLMS Note:

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

number. 

 LIN25 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN26 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

DLMS Note: Use the next two qualifiers when applicable 

to identify the engine. 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 SN Serial Number 

DLMS Note:

Use to identify the Engine Serial Number. 

 LIN27 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN28 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

 

X ID 2/2 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 20 

 CodeList Summary (Total Codes: 505, Included: 1) 

Code Name

 MN Model Number 

DLMS Note:

Use to identify the Engine Model Number. 

 LIN29 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 

 LIN30 235 Product/Service ID Qualifier 

Description: Code identifying the type/source of the 

descriptive number used in Product/Service ID (234) 

All valid standard codes are used. (Total Codes: 505) 

X ID 2/2 Used 

 LIN31 234 Product/Service ID 

Description: Identifying number for a product or service 

 

X AN 1/48 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 21 

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

Detail - Optional

Loop: HL Elements: 2

 

User Option (Usage): Used

Purpose: To specify pertinent dates and times 

Syntax Rules: 

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

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

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

 

DLMS Note:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 DTM01 374 Date/Time Qualifier 

Description: Code specifying type of date or time, or both 

date and time 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

M ID 3/3 Must use 

 CodeList Summary (Total Codes: 1226, Included: 30) 

Code Name

 002 Delivery Requested 

DLMS Note:

Use to identify the Exhibit Requested Date. This is the date the exhibit was requested by the action or 

support point.

 009 Process 

DLMS Note:

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.

 011 Shipped 

DLMS Note:

Use to identify the Exhibit Shipped Date.

 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.

 094 Manufacture 

DLMS Note:

Use to identify the Date of Manufacture.

 145 Opening Date 

DLMS Note:

Use to identify PQDR the Re-Open Request Date.

 146 Closing Date 

DLMS Note:

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

Point.

 177 Cancellation 

DLMS Note:

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

 188 Credit Advice 

DLMS Note:

1. Use to identify the date credit was issued, Credit Date. 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 22 

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

 212 Returned to Customer 

DLMS Note:

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

as stipulated in the disposition instructions.

 214 Date of Repair/Service 

DLMS Note:

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

 368 Submittal 

DLMS Note:

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

Support Point.

 370 Actual Departure Date 

DLMS Note:

Use to identify the Exhibit Shipped by Exhibit Warehouse Date.

 440 Release of Information 

DLMS Note:

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

Screening Point.

 508 Extended 

DLMS Note:

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.

 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.

 514 Transferred 

DLMS Note:

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.

 516 Discovered 

DLMS Note:

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.

 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.

 636 Date of Last Update 

DLMS Note:

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

 649 Document Due 

DLMS Note:

1. Use to identify the Support Point Due Date. 

2. Only support point may assign the date update information is due back to the Action Point.

 868 Last Follow-up 

DLMS Note:

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

exhibit holding activity.

 909 Contestability 

DLMS Note:

Use to identify the Action Point Rebuttal/Controvert Date. This is the date the Action Point rebutted 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 23 

the final reply from Support Point.

 922 Original Receipt 

DLMS Note:

Use to identify the date the nonconforming item was received.

 947 Preparation 

DLMS Note:

Use to identify the date the PQDR was completed by the originator and submitted to the screening point 

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

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

Submitted, on the old version of the SF368.

 AAG Due Date 

DLMS Note:

1. Use to identify the Action Point Due Date. 

2. Only action point may assign this date based on category that a response is due back to screening 

point.

 ABY Product Held Until 

DLMS Note:

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

 ACK Acknowledgment 

DLMS Note:

Use to identify the Acknowledged Date by the sender.

 ACZ Controvert Date 

DLMS Note:

Use to identify the Screening Point Rebuttal/Controvert Date. This is the date the Screening Point 

rebutted the final reply from Action Point.

 DIS Disposition 

DLMS Note:

Use to identify the Exhibit Final Disposition Instruction Date. 

 DTM02 373 Date 

Description: Date expressed as CCYYMMDD where CC 

represents the first two digits of the calendar year 

 

X DT 8/8 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 24 

REF Reference Identification Pos: 0700 Max: >1

Detail - Optional

Loop: HL Elements: 4

 

User Option (Usage): Used

Purpose: To specify identifying information 

Syntax Rules: 

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

 

Semantics: 

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

DLMS Note:

Must use to identify the PQDR Report Control Number (RCN). Use multiple repetitions as needed to identify additional reference numbers associated with 

a PQDR.

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 REF01 128 Reference Identification Qualifier 

Description: Code qualifying the Reference Identification 

Federal Note: Use any code. 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

M ID 2/3 Must use 

 CodeList Summary (Total Codes: 1632, Included: 34) 

Code Name

 0D Subject Property Verification Source 

DLMS Note:

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

non-GFP. Cite the applicable code in REF02: 

Y – GFP 

R – GFP returned by the contractor to DoD inventory. 

N – Not GFP 

U – Unknown

 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.

 2E Foreign Military Sales Case Number 

DLMS Note:

Reserved for future use to identify FMS Case Numbers for FMS SDRs.

 2I Tracking Number 

DLMS Note:

Use to identify the Exhibit Tracking Number. This is the commercial carrier’s number provided to the 

shipping activity to track the exhibit.

 3H Case Number 

DLMS Note:

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.

 44 End Use Number 

DLMS Note:

Use to identify the End Item Type/Model/Series This is the major weapons system with which the end 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 25 

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

 86 Operation Number 

DLMS Note:

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

 87 Functional Category 

DLMS Note:

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.

 BM Bill of Lading Number 

DLMS Note:

Use to identify Government Bill of Lading/Commercial Bill of Lading (GBL/CBL) 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.

 BZ Complaint Code 

DLMS Note:

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.

 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.

 F8 Original Reference Number 

DLMS Note:

1. Use to identify Screening Point Control Number. Identify the system that created the control number 

in REF03. 

2. PQDRII field size = 14. 

3. PQDRII Definition: Control number assigned by the screening point if different from the RCN.

 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. PQDRII Definition: Code used to indicate whether GSI is required.

 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.

 K4 Criticality Designator 

DLMS Note:

1. Used to identify the item as a Critical Safety Item (CSI). Use 'Y' if the materiel is CSI. 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 26 

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

 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. PQDRII Definition: Indicates whether the item is or is not under warranty, if known.

 KU Office Symbol 

DLMS Note:

Use to identify the DLA Action Office code.

 NN Nonconformance Report Number 

DLMS Note:

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

2. PQDRII field size = 9.

 PM Part Number 

DLMS Note:

Use to identify the End Item Part Number.

 PO Purchase Order Number 

DLMS Note:

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

 

2. PQDRII field size = 20.

 QE Replacement Customer Reference Number 

DLMS Note:

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.

 QR Quality Report Number 

DLMS Note:

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.

 SE Serial Number 

DLMS Note:

1. Use to identify End Item Serial Number. Equates to SF 368, Block 18d. For the serial number(s) 

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

2. The serial number may not exceed 30 characters in accordance with UID policy.

 SI Shipper's Identifying Number for Shipment (SID) 

DLMS Note:

Use to identify the vendor's shipment number shown on new procurement shipping documentation.

 TG Transportation Control Number (TCN) 

DLMS Note:

1. Use to indicate the Transportation Control number. 

 

2. Field size = 17.

 TN Transaction Reference Number 

DLMS Note:

1. Use to indicate the document number under which the defective materiel was purchased 

requisitioned, shipped, or reworked. 

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.

 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). 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 27 

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.

 VW Standard 

DLMS Note:

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

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

 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 

PQDRII Definition: Indicates the responsible/liable party for the deficiency. See PQDR Joint 

Regulation for appropriate codes. 

Severity of Defect Code (2nd position) 

PQDRII Definition: Level of Severity of the defect. See PQDR Joint Regulation for appropriate codes.

Broad Cause of Defect Code (3rd position) 

Aka Broad Cause Code. 

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

Regulation for appropriate codes. 

Detailed Cause Code(4-6th position) 

PQDRII Definition: PQDR Joint Regulation detailed cause of deficiency. See PQDR Joint Regulation 

for appropriate codes. 

Preventive Action Taken Code (7th position) 

PQDRII Definition: Code used to indicate the preventive action taken to prevent recurrence. See PQDR 

Joint Regulation for appropriate codes. 

Corrective Action Taken Code (8th position) 

Aka Action Taken Code, Corrective Action Code 

PQDRII Definition: Corrective action code taken as a result of the investigation. See PQDR Joint 

Regulation for appropriate codes. 

Final Exhibit Disposition Code (9th position) 

Aka Action Disposition 

PQDRII Definition: Code representing the current disposition of the exhibit. See PQDR Joint 

Regulation for appropriate codes. 

Credit Code (10th position) 

PQDRII Definition: The Credit Code. Use Codes C-No Credit (Commercial Supplier), F-repaired by 

user, G-No Credit (Gov’t Supplier), N-Credit (Commercial Supplier), P-Vendor Replacement, RVendor Repair, S-Source of Supply replacement, U-Unknown, W-Credit Authorized, X-No Credit 

Authorized, Z-Credit (Gov’t Supplier) 

Defect Verified Code(11th position) 

PQDRII 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 

Cost Code (12th position) 

PQDRII 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), Uundetermined, Z-No Cost to Navy (Government Manufacturer/Supplier) 

Current Disposition (13th position) 

SF368 Block 19: Use codes H-Holding Exhibit, D-Disposed of/Destroyed, R-Repaired, or O-Other. 

Action Requested (14th position) 

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

 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. PQDRII field size = 25.

 PSM Credit Card 

DLMS Note:

Use to indicate payment by either Government purchase card or commercial credit card. Cite Y in 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 28 

REF02 when applicable. 

 REF02 127 Reference Identification 

Description: Reference information as defined for a 

particular Transaction Set or as specified by the Reference 

Identification Qualifier 

 

X AN 1/50 Must use 

 REF03 352 Description 

Description: A free-form description to clarify the related 

data elements and their content 

DLMS Note: Use to identify the generating-system report 

number. i.e. Army-LMP, AWIS, DLA- EBS, JDRS, NavyERP, PDREP, or USMC-GCCS 

 

X AN 1/80 Used 

 REF04 C040 Reference Identifier 

Description: To identify one or more reference numbers 

or identification numbers as specified by the Reference 

Qualifier 

O Comp Used 

 REF04-01 128 Reference Identification Qualifier 

Description: Code qualifying the Reference Identification 

 

M ID 2/3 Must use 

 CodeList Summary (Total Codes: 1631, Included: 1) 

Code Name

 W8 Suffix 

DLMS Note:

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

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

 REF04-02 127 Reference Identification 

Description: Reference information as defined for a 

particular Transaction Set or as specified by the Reference 

Identification Qualifier 

 

M AN 1/50 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 29 

CS Contract Summary Pos: 0750 Max: 1

Detail - Optional

Loop: HL Elements: 4

 

User Option (Usage): Used

Purpose: To provide information about a contract 

Syntax Rules: 

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

 

Semantics: 

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

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

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

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

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

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

no Critical Application Indicator is specified in the contract. 

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

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

Comments: 

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

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 CS01 367 Contract Number 

Description: Contract number 

DLMS Note: Used to identify the Contract Number under 

which the nonconforming materiel was procured, i.e., 

N0010492340001. 

 

O AN 1/30 Used 

 CS03 328 Release Number 

Description: Number identifying a release against a 

Purchase Order previously placed by the parties involved 

in the transaction 

DLMS Note: Use to identify the Contract Numbers Call 

or Order Number, i.e., 0012. 

 

O AN 1/30 Used 

 CS04 128 Reference Identification Qualifier 

Description: Code qualifying the Reference Identification 

 

X ID 2/3 Used 

 CodeList Summary (Total Codes: 1631, Included: 1) 

Code Name

 C7 Contract Line Item Number 

DLMS Note:

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

 CS05 127 Reference Identification 

Description: Reference information as defined for a 

particular Transaction Set or as specified by the Reference 

Identification Qualifier 

 

X AN 1/50 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 30 

PWK Paperwork Pos: 1020 Max: >1

Detail - Optional

Loop: HL Elements: 3

 

User Option (Usage): Used

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

Syntax Rules: 

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

 

Comments: 

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

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

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

DLMS Note:

Use a separate PWK segment for each attachment identified by filename. Repeat as needed to identify each attachment. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 PWK01 755 Report Type Code 

Description: Code indicating the title or contents of a 

document, report or supporting item 

Federal Note: Use any code. 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 533, Included: 2) 

Code Name

 AE Attachment 

DLMS Note:

1. Use to indicate that supporting documentation is provided electronically in the form of images or 

files with the 842P transaction. 

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. 

 PWK02 756 Report Transmission Code 

Description: Code defining timing, transmission method 

or format by which reports are to be sent 

 

O ID 1/2 Used 

 CodeList Summary (Total Codes: 55, Included: 1) 

Code Name

 FT File Transfer 

DLMS Note:

Use to indicate attachments are available. 

 PWK07 352 Description 

Description: A free-form description to clarify the related 

data elements and their content 

DLMS Note: Use to indicate the PQDR Attachment File 

Name being sent electronically in a separate transmission. 

 

O AN 1/80 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 31 

LM Code Source Information Pos: 1040 Max: 1

Detail - Optional

Loop: LM Elements: 1

 

User Option (Usage): Used

Purpose: To transmit standard code list identification information 

 

Comments: 

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

DLMS Note:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 LM01 559 Agency Qualifier Code 

Description: Code identifying the agency assigning the 

code values 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 187, Included: 1) 

Code Name

 DF Department of Defense (DoD) 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 32 

LQ Industry Code Pos: 1050 Max: >1

Detail - Mandatory

Loop: LM Elements: 2

 

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes 

Syntax Rules: 

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

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 LQ01 1270 Code List Qualifier Code 

Description: Code identifying a specific industry code list 

Federal Note: Use any code. 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

O ID 1/3 Must use 

 CodeList Summary (Total Codes: 770, Included: 12) 

Code Name

 83 Supply Condition Code 

DLMS Note:

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

 CR Federal Item Identification Guide Criticality (FIIG) Code 

DLMS Note:

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

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

 CW Controvert Code 

DLMS Note:

Use to identify the PQDR Rebuttal/Controvert Code. Must use in a reply rebuttal transaction 

(BNR01Code=RR). 

Staffing Note: Rebuttal Codes will be provided as a part of a DLMS approved data change to this 

standard.

 DE Signal Code 

DLMS Note:

Use to identify the Signal Code.

 DG Fund Code 

DLMS Note:

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

 EQ Controlled Inventory Item Code 

DLMS Note:

Use to identify the Controlled Inventory Item Code.

 FD Demilitarization Code 

DLMS Note:

Use to identify the Demilitarization Code.

 GK Investigation Status Code 

DLMS Note:

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

Staffing Note: PQDR Investigation Status Codes will be provided separately.

 JN Mission Impact Statement Code 

DLMS Note:
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 33 

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 

Staffing Note: These codes are were originally defined for use in Supply Support Requests under 

DLMS. If definitions for use in PQDRS require updates or additional codes are needed, they will be 

coordinated separately. 

 COG Cognizance Symbol 

DLMS Note:

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

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

perpetuate without action.

 MAC Material Management Aggregation Code 

DLMS Note:

1. Use to identify the Material Management Aggregation Code (MMAC) for NSNs managed by a 

specific manager (i.e., System, program, aggregation, selected FSC, technology group). This is an Air 

Force-unique data element meaningful to the Air Force only. Non-Air Force components perpetuate 

without action. 

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

 SMI Special Material Identification Code 

DLMS Note:

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

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

 LQ02 1271 Industry Code 

Description: Code indicating a code from a specific 

industry code list 

 

X AN 1/30 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 34 

NCD Nonconformance Description Pos: 2300 Max: 1

Detail - Optional

Loop: NCD Elements: 2

 

User Option (Usage): Used

Purpose: To describe the nonconformance condition 

Syntax Rules: 

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

 

DLMS Note:

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

2. Begin a new NCD loop for each IUID loop. The UII value and some of the associated data elements are future DLMS enhancements and require 

coordination prior to use.

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 NCD02 888 Nonconformance Determination Code 

Description: Code indicating whether a nonconforming 

condition was the reason for submitting or the basis upon 

which a nonconformance report is initiated 

 

X ID 1/1 Must use 

 CodeList Summary (Total Codes: 7, Included: 1) 

Code Name

 5 Discrepant 

DLMS Note:

For all transactions, use to satisfy ANSI requirement. 

 NCD03 350 Assigned Identification 

Description: Alphanumeric characters assigned for 

differentiation within a transaction set 

DLMS Note: Use as a counter to satisfy ANSI syntax. 

Cite numeric '1' EXCEPT where additional NCD loops 

when providing unique identification of discrepant items. 

In these instances, Increase incrementally by 1 for each 

uniquely identified item. 

 

O AN 1/20 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 35 

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

Detail - Optional

Loop: NCD Elements: 2

 

User Option (Usage): Used

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

 

Comments: 

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

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 NTE01 363 Note Reference Code 

Description: Code identifying the functional area or 

purpose for which the note applies 

Federal Note: Use any code. 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

O ID 3/3 Used 

 CodeList Summary (Total Codes: 342, Included: 7) 

Code Name

 ACT Action 

DLMS Note:

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

recommended action requested by the originator or screening point. 

2. PQDRII field size = 20.

 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.

 COD Corrected Data 

DLMS Note:

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

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

what fields are affected.

 DEL Delivery 

DLMS Note:

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

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

2. PQDRII field size = 10.

 EBK Other Reason for Withdrawal 

DLMS Note:

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

 POL Property Owner Location Information 

DLMS Note:

1. Use to identify the originators Location of Exhibit narrative. This is detailed information about 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 36 

where materiel is currently located. 

2. PQDRII field size = 100. 

 NTE02 352 Description 

Description: A free-form description to clarify the related 

data elements and their content 

DLMS Note: 1. Differences in system field sizes may 

exist. Coordinate with receiving systems to ensure they 

have the capability accept the quantity of data sent. 

 

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

for each line, until reaching the maximum length 

available. 

3. Special characters are not allowed except as specified. 

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

 

M AN 1/80 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 37 

REF Reference Identification Pos: 2600 Max: >1

Detail - Optional

Loop: NCD Elements: 2

 

User Option (Usage): Used

Purpose: To specify identifying information 

Syntax Rules: 

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

 

Semantics: 

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

DLMS Note:

1. Use in the IUID Loop (HL01=I) to provide IUID information. Repeat the REF segment within each IUID loop to identify relevant IUID information. 

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

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 REF01 128 Reference Identification Qualifier 

Description: Code qualifying the Reference Identification 

Federal Note: Use any code. 

DLMS Note: 1. For DLMS use the following codes are 

authorized. 

 

2. Use codes separately or in combination, to identify 

appropriate information for unique item tracking (UIT) or 

reporting under UID policy. 

 

M ID 2/3 Must use 

 CodeList Summary (Total Codes: 1631, Included: 3) 

Code Name

 BT Batch Number 

DLMS Note:

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

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

 SE Serial Number 

DLMS Note:

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

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

 U3 Unique Supplier Identification Number (USIN) 

DLMS Note:

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

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

Department of Defense Unique Item Identifier. 

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

 REF02 127 Reference Identification 

Description: Reference information as defined for a 

particular Transaction Set or as specified by the Reference 

Identification Qualifier 

X AN 1/50 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 38 

QTY Quantity Pos: 2700 Max: >1

Detail - Optional

Loop: NCD Elements: 3

 

User Option (Usage): Used

Purpose: To specify quantity information 

Syntax Rules: 

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

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

 

Semantics: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 QTY01 673 Quantity Qualifier 

Description: Code specifying the type of quantity 

Federal Note: Use any code. 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 976, Included: 11) 

Code Name

 01 Discrete Quantity 

DLMS Note:

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

and materiel failure. 

2. PQDRII field size = 7.

 02 Cumulative Quantity 

DLMS Note:

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

and materiel failure. 

2. PQDRII field size = 7.

 17 Quantity on Hand 

DLMS Note:

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

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

2. PQDRII field size = 15.

 38 Original Quantity 

DLMS Note:

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

on previous PQDRs. 

2. PQDRII field size = 5.

 39 Shipped Quantity 

DLMS Note:

1. Use to identify the quantity of Exhibits Shipped. 

2. PQDRII field size = 7.

 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. 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 39 

2. PQDRII field size = 9.

 87 Quantity Received 

DLMS Note:

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

Block 10a. 

2. PQDRII field size = 9.

 AO Verified Receipts 

DLMS Note:

1. Use to identify the quantity of Exhibits Received by the action or support point. 

2. PQDRII field size = 7. 

 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. PQDRII field size = 15.

 UA Units Completed 

DLMS Note:

1. Use to identify the Quantity Inspected by the originator. Equates to SF368, Block 10b. 

 

2. PQDRII field size = 9. 

 V3 Transfer Quantity 

DLMS Note:

1. Use to identify the quantity of Exhibits Requested by action or support point. 

2. PQDRII field size = 7. 

 QTY02 380 Quantity 

Description: Numeric value of quantity 

 

X R 1/15 Must use 

 QTY03 C001 Composite Unit of Measure 

Description: To identify a composite unit of measure(See 

Figures Appendix for examples of use) 

DLMS Note: 1. Use to identify the discrepant/deficient 

quantity. Use multiple repetitions as needed to identify 

additional quantities associated with the complaint. 

2. DLMS users see the Unit of Issue and Purchase Unit 

Conversion Table for available codes. 

3. PQDRII Definition: Type of standard unit the materiel 

was packaged in 

 

O Comp Used 

 QTY03-01 355 Unit or Basis for Measurement Code 

Description: Code specifying the units in which a value is 

being expressed, or manner in which a measurement has 

been taken 

DLMS Note: 1. PQDRII Definition: Unit of measure not 

related to time prior to failure. Aka Operating Cycles at 

Failure. 

2. For QTY01 code 01,02, or OT use one of the following 

codes: 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 803, Included: 11) 

Code Name

 03 Seconds 

 1N Count 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 40 

Federal Note:

Use to indicate number of starts (time failure code STA).

 B7 Cycles 

DLMS Note:

Use to indicate cycles of equipment, e.g., engine start-up and stop, or take-off and landings.

 DA Days 

 DH Miles 

 FT Foot 

 HR Hours 

 MJ Minutes 

 MO Months 

 RO Round 

DLMS Note:

Use to indicate rounds fired.

 UN Unit 

DLMS Note:

Use to indicate unit if measure is other than those listed here (time failure code OTH).
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 41 

AMT Monetary Amount Pos: 2730 Max: >1

Detail - Optional

Loop: NCD Elements: 2

 

User Option (Usage): Used

Purpose: To indicate the total monetary amount 

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 AMT01 522 Amount Qualifier Code 

Description: Code to qualify amount 

Federal Note: Use any code. 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

M ID 1/3 Must use 

 CodeList Summary (Total Codes: 1696, Included: 5) 

Code Name

 10 Shipment Value in U.S. Dollars 

DLMS Note:

1. Use to indicate “total” value of defects in Defective Unit Cost. This is the cost of the deficient 

materiel based on the unit of issue. 

2. PQDRII field size = 15.

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

 PD Credit 

DLMS Note:

Use to indicate the amount of credit/debit being authorized or recommended (also known as DLA 

Credit Value).

 RP Repair 

DLMS Note:

1. Use to identify the Estimated Repair Cost to repair the deficient materiel. 

2. PQDRII field size = 15.

 Z3 Unit Cost of Discrepant Material 

DLMS Note:

1. Use to identify “unit” value of a “single” defective item in Defective Unit Cost. This is the cost of 

the deficient materiel based on the unit of issue. 

2. PQDRII field size = 15. 

 AMT02 782 Monetary Amount 

Description: Monetary amount 

DLMS Note: Dollar values may be expressed in whole 

dollars (with no decimal) or in dollar and cents (with a 

decimal included). 

 

M R 1/18 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 42 

N1 Name Pos: 2800 Max: 1

Detail - Optional

Loop: N1 Elements: 4

 

User Option (Usage): Used

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

Syntax Rules: 

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

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

 

Comments: 

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

must provide a key to the table maintained by the transaction processing party. 

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

DLMS Note:

Use to identify other agencies involved with the processing of the PQDR. Also, use in IUID loop to identify the Enterprise Identifier. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 N101 98 Entity Identifier Code 

Description: Code identifying an organizational entity, a 

physical location, property or an individual 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

M ID 2/3 Must use 

 CodeList Summary (Total Codes: 1446, Included: 17) 

Code Name

 41 Submitter 

DLMS Note:

Use to identify the Originator DoDAAC when different than the address identified with the DODAACFrom in 1/N101/1200.

 91 Action Party 

DLMS Note:

Use to identify the Action Point DoDAAC when different than the address identified with the DODAACFrom in 1/N101/1200.

 92 Support Party 

DLMS Note:

Use to identify the Support Point DoDAAC when different than the address identified with the 

DODAAC-From in 1/N101/1200.

 C4 Contract Administration Office 

DLMS Note:

Use to identify DLA Form 1227DCMA Review Release Authority or Preparer by DoDAAC.

 LG Location of Goods 

DLMS Note:

Use to identify Exhibit Holding DoDAAC/CAGE of the organization that is holding the exhibit. Aka 

Exhibit Location.

 MF Manufacturer of Goods 

DLMS Note:

1. Use to identify the Supplier/Manufacturer CAGE, DUNS or DUNSS Plus 4. 

2. PQDRII Definition: Manufacturers/Suppliers Commercial and Government Entity (CAGE), Dunn 

and Bradstreet Number (DUNS) and/or DUNS Plus Four number.

 PG Prime Contractor 

DLMS Note:
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 43 

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

2. Contractor and Government Entity (CAGE) Code of the Supplier.

 RN Repair or Refurbish Location 

DLMS Note:

Use to identify the Last Repair Facility, aka Last Rework Facility, when different than the address 

identified with the DODAAC-From in 1/N101/1200.

 SH Shipper 

DLMS Note:

1. Use to identify Shipper of the nonconforming materiel. Shipper Code must be CAGE or DoDAAC. 

2. PQDRII Definition: DoDAAC or CAGE of the Shipping activity who delivered the defective materiel.

 ST Ship To 

DLMS Note:

1. Use to identify the Exhibit Shipped To Address. This is the address to which the exhibit was shipped.

 Z7 Mark-for Party 

DLMS Note:

Use to identify the Mark For party to receive an exhibit.

 ZB Party to Receive Credit 

DLMS Note:

Use to identify the DoDAAC for the activity to receive credit if not the PQDR originator’s organization.

 ZD Party to Receive Reports 

DLMS Note:

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

842P.

 ZQ Screening Point 

DLMS Note:

1. Use to identify the Screening Point DoDAAC when different than the address identified with the 

DODAAC from N101.

 DIR Distribution Recipient 

DLMS Note:

Use to identify the recipient of the distribution copy forwarded by email or other non-transaction 

method.

 IAT Party Executing and Verifying 

DLMS Note:

1. Use to indicate the Enterprise Identifier (EID) responsible for the UII. 

2. The value of the IUID Issuing Agency Code (IAC) may be derived from the qualifier used for the 

Enterprise Identifier. Use only N103 qualifiers for which a corresponding IAC is noted.

 SUS Supply Source 

DLMS Note:

Use to identify the Source of Supply by Routing Identifier Code (RIC). 

 N102 93 Name 

Description: Free-form name 

DLMS Note: Use to identify the name of the code listed 

above i.e. Portsmouth Naval Shipyard. 

 

X AN 1/60 Used 

 N103 66 Identification Code Qualifier 

Description: Code designating the system/method of code 

structure used for Identification Code (67) 

 

X ID 1/2 Used 

 CodeList Summary (Total Codes: 223, Included: 6) 

Code Name

 1 D-U-N-S Number, Dun & Bradstreet 

 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix 

 10 Department of Defense Activity Address Code (DODAAC) 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 44 

 33 Commercial and Government Entity (CAGE) 

 A2 Military Assistance Program Address Code (MAPAC) 

 M4 Department of Defense Routing Identifier Code (RIC) 

 

 N104 67 Identification Code 

Description: Code identifying a party or other code 

DLMS Note: Use to identify the name of the code listed 

above. i.e. DoDAAC = N39040 

 

X AN 2/80 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 45 

N2 Additional Name Information Pos: 2900 Max: 2

Detail - Optional

Loop: N1 Elements: 2

 

User Option (Usage): Used

Purpose: To specify additional names 

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 N201 93 Name 

Description: Free-form name 

DLMS Note: 1. This equates to address line. 

2. Used when customer input for the reporting activity 

information is not available or differs from data extracted 

from the DODAAC. 

 

M AN 1/60 Must use 

 N202 93 Name 

Description: Free-form name 

DLMS Note: 1. This equates to address line two. 

2. Used when customer input for the reporting activity 

information is not available or differs from data extracted 

from the DODAAC. 

 

O AN 1/60 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 46 

N3 Address Information Pos: 3000 Max: 2

Detail - Optional

Loop: N1 Elements: 2

 

User Option (Usage): Used

Purpose: To specify the location of the named party 

 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 N301 166 Address Information 

Description: Address information 

DLMS Note: This equates to street address. Used when 

customer input for the reporting activity information is not 

available or differs from data extracted from the 

DODAAC. 

 

M AN 1/55 Must use 

 N302 166 Address Information 

Description: Address information 

DLMS Note: This equates to street address. Used when 

customer input for the reporting activity information is not 

available or differs from data extracted from the 

DODAAC. 

 

O AN 1/55 Must use 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 47 

N4 Geographic Location Pos: 3100 Max: 1

Detail - Optional

Loop: N1 Elements: 4

 

User Option (Usage): Used

Purpose: To specify the geographic place of the named party 

Syntax Rules: 

1. E0207 - Only one of N402 or N407 may be present. 

2. C0605 - If N406 is present, then N405 is required. 

3. C0704 - If N407 is present, then N404 is required. 

 

Comments: 

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 

2. N402 is required only if city name (N401) is in the U.S. or Canada. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 N401 19 City Name 

Description: Free-form text for city name 

 

O AN 2/30 Used 

 N402 156 State or Province Code 

Description: Code (Standard State/Province) as defined 

by appropriate government agency 

 

X ID 2/2 Used 

 N403 116 Postal Code 

Description: Code defining international postal zone code 

excluding punctuation and blanks (zip code for United 

States) 

 

O ID 3/15 Used 

 N404 26 Country Code 

Description: Code identifying the country 

 

X ID 2/3 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 48 

PER Administrative Communications Contact Pos: 3300 Max: >1

Detail - Optional

Loop: N1 Elements: 9

 

User Option (Usage): Used

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

Syntax Rules: 

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

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

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

 

DLMS Note:

1. Use to identify the report preparer when the customer DoDAAC is identified in this loop (rather than in the transaction header). Only one POC may be 

identified as the report preparer. 

2. Use a second repetition if needed to identify additional communication numbers. When used, must provide email address and at least one phone number. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 PER01 366 Contact Function Code 

Description: Code identifying the major duty or 

responsibility of the person or group named 

 

M ID 2/2 Must use 

 CodeList Summary (Total Codes: 234, Included: 3) 

Code Name

 AU Report Authorizer 

DLMS Note:

1. Use to identify the review official's information associated with DLA Form 1227 (also known as 

Review Release Authority). This is the official that reviewed the 1227 previous to release.

 PU Report Preparer 

DLMS Note:

Use to identify the preparing official's information associated with the DLA Form 1227. Aka Prepared 

By.

 RP Responsible Person 

DLMS Note:

Use to indicate a POC at receiving location. Also, use in PQDR exhibit shipments to indicate the 

Government representative at the receiving location. 

 PER02 93 Name 

Description: Free-form name 

 

O AN 1/60 Used 

 PER03 365 Communication Number Qualifier 

Description: Code identifying the type of communication 

number 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 40, Included: 3) 

Code Name

 AU Defense Switched Network 

DLMS Note:

Use to identify the DSN Phone Number.

 EM Electronic Mail 

DLMS Note:

Use to identify the E-mail address.

 TE Telephone 

DLMS Note:

Use to identify the Commercial Phone Number. 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 49 

 PER04 364 Communication Number 

Description: Complete communications number including 

country or area code when applicable 

 

X AN 1/256 Used 

 PER05 365 Communication Number Qualifier 

Description: Code identifying the type of communication 

number 

DLMS Note: Use to identify an alternate communications 

number which can be used to contact the specified point of 

contact. 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 40, Included: 3) 

Code Name

 AU Defense Switched Network 

DLMS Note:

Use to identify the DSN Phone Number.

 EM Electronic Mail 

DLMS Note:

Use to identify the E-mail address.

 TE Telephone 

DLMS Note:

Use to identify the Commercial Phone Number. 

 PER06 364 Communication Number 

Description: Complete communications number including 

country or area code when applicable 

 

X AN 1/256 Used 

 PER07 365 Communication Number Qualifier 

Description: Code identifying the type of communication 

number 

 

X ID 2/2 Used 

 CodeList Summary (Total Codes: 40, Included: 3) 

Code Name

 AU Defense Switched Network 

DLMS Note:

Use to identify the DSN Phone Number.

 EM Electronic Mail 

DLMS Note:

Use to identify the E-mail address.

 TE Telephone 

DLMS Note:

Use to identify the Commercial Phone Number. 

 PER08 364 Communication Number 

Description: Complete communications number including 

country or area code when applicable 

 

X AN 1/256 Used 

 PER09 443 Contact Inquiry Reference 

Description: Additional reference number or description 

to clarify a contact number 

DLMS Note: Use as needed to identify the office symbol 

or activity code for the party identified. 

May also reflect position title of the point of contact. 

 

O AN 1/20 Used 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 50 

NCA Nonconformance Action Pos: 3400 Max: 1

Detail - Optional

Loop: NCA Elements: 2

 

User Option (Usage): Used

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

Syntax Rules: 

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

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

 

Semantics: 

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

Comments: 

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

DLMS Note:

Used to describe actions taken in response to the original PQDR report. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 NCA01 350 Assigned Identification 

Description: Alphanumeric characters assigned for 

differentiation within a transaction set 

DLMS Note: For all transactions cite numeric 1 to satisfy 

ANSI requirement. 

 

O AN 1/20 Used 

 NCA02 887 Nonconformance Resultant Response Code 

Description: Code identifying a response that is the result 

of a nonconformance situation 

 

X ID 1/2 Used 

 CodeList Summary (Total Codes: 15, Included: 1) 

Code Name

 RS Response Requirements Follow 

DLMS Note:

Use to satisfy ANSI syntax requirements.
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 51 

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

Detail - Optional

Loop: NCA Elements: 2

 

User Option (Usage): Used

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

 

Comments: 

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

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 NTE01 363 Note Reference Code 

Description: Code identifying the functional area or 

purpose for which the note applies 

DLMS Note: For DLMS use the following codes are 

authorized. 

 

O ID 3/3 Used 

 CodeList Summary (Total Codes: 342, Included: 17) 

Code Name

 ACI Additional Claim Information 

DLMS Note:

1. Used to identify Supplemental Data to provide additional information pertinent to the PQDR 

investigation. 

2. PQDRII field size = 4000.

 ACN Action Taken 

DLMS Note:

1. Use to Identify the Final Reply Results narrative describing the final results of the investigation. 

2. PQDRII field size = 2000.

 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. PQDRII field size = 2000.

 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. PQDRII field size = 2000.

 CBB Consideration to be Received 

DLMS Note:

1. Use to identify the Contractors Position on repair or replacement of materiel. Equates to DLA Form 

1227 block 16. 

2. PQDRII field size = 2000.

 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. PQDRII field size = 2000.

 EAT Asset Disposition 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 52 

DLMS Note:

1. Use to identify the Materiel Disposition instructions. 

2. PQDRII field size = 2000. 

3. PQDRII Definition: Use to identify the Support Points Materiel Disposition instructions for the 

defective item narrative.

 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. PQDRII field size = 2000.

 ORI Order Instructions 

DLMS Note:

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

2. PQDRII field size = 2000.

 OTH Other Instructions 

DLMS Note:

1. Use to identify the Exhibit Final Disposition Instruction containing the action point instruction to 

screening or support point for final handling of the exhibit. This is the Action Point’s instruction to 

Screening or Support point for final handling of the exhibit. 

2. PQDRII field size = 2000.

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

 REP Report 

DLMS Note:

1. Use to identify the Preventive Action Taken (Answer) narrative. Derived from the DLA Form 1227.

2. PQDRII field size = 2000.

 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. PQDRII field size = 2000.

 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. PQDRII field size = 2000.

 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. PQDRII field size = 2000.

 VEC Verification Comments 

DLMS Note:

1. Use to identify the Exhibit Accounted For providing verification that the exhibit arrived at the 

correct location. 
DLMS Supplement 842P PDC 1007 DoD 4000.25-M

Product Quality Deficiency Report (PQDR) Data Exchange 

004030D842P0 - DLMS Supplement

 Enclosure 2, ADC 1007 

Page 53 

2. PQDRII field size = 10.

 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. PQDRII field size = 2000. 

 NTE02 352 Description 

Description: A free-form description to clarify the related 

data elements and their content 

DLMS Note: 1. Differences in system field sizes may 

exist. Coordinate with receiving systems to ensure they 

have the capability accept the quantity of data sent. 

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

for each line, until reaching the maximum length specified.

3. Special characters are not allowed except as specified. 

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

 

M AN 1/80 Must use 
DLMS Supplement to Proposed Federal IC 842P for 

Product Quality Deficiency Report (PQDR) 

004030D842P0 - DLMS Supplement

 Enclosure 2, PDC 1007 

Page 54 

SE Transaction Set Trailer Pos: 4700 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

 

User Option (Usage): Must use

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

ending (SE) segments)

 

 

Comments: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

 SE01 96 Number of Included Segments 

Description: Total number of segments included in a 

transaction set including ST and SE segments 

 

M N0 1/10 Must use 

 SE02 329 Transaction Set Control Number 

Description: Identifying control number that must be 

unique within the transaction set functional group assigned 

by the originator for a transaction set 

Federal Note: Cite the same number as the one cited in 

ST02. 

 

M AN 4/9 Must use 
Enclosure 3, PQDR Dictionary 

PQDRII Column name DLMS Data Existing/Add/Revise

(E/A/R) 

PQDRII 

Type/Size 

Definition 

Action Disposition A number(2) Code representing the current disposition of the ex

Regulation for appropriate codes. 

Action Office A varchar2(25) DLA Action Office Code. Action Point Address Line 1 A varchar2(40) 1st line address of the action point based on DAction Point Address Line 2 A varchar2(40) 2nd line address of the action point based on DAction Point City A varchar2(20) City address of the action point based on DoDAction Point DoDAAC A char(6) Use to identify the DoDAAC of the current Action 

DoDAAC of the activity responsible for the investdeficiency (Action Point) 

Action Point Due Date A date Use to identify the Action Point Due Date. Date 

response is due back to screening pt. Only Action 

Action Point E-Mail Address A varchar2(120) Use to identify the E-mail address Action Point Name A varchar2(70) Use to identify the Action Point name and contacAction Point Postal Code A char(10) ZIP Code address of the action point based on Action Point State/Province A char(2) State code address of the action point based on Action Point Phone A varchar2(40) Use to identify the Commercial Phone number Action Point DSN A varchar2(40) Use to identify the DSN Phone Number Action Requested Narrative by Originator or Screening Point 

A varchar2(20) Recommended action requested by the originator o

Action Taken code (corrective action) A char(3) Corrective action code taken as a result of the inve

Regulation for appropriate codes. 

Action to Screening Date A date Date the Action Point released the PQDR to the ScAction to Support Date A date Date the Action Point Released QDR to the SuppoAdditional Information/Narrative A varchar2(60) Additional user notes related to PQDR. Broad Cause of Defect Code A char(3) PQDR Joint Regulation code describing the cause 

Regulation for appropriate codes. 

PQDR Category R number(1) Designates the category IAW PQDR Joint RegulatClosure Date A date Date the PQDR is closed by the Screening Point. 
Cognizance Code (COG) E char(2) Navy identifier of the cognizant item manager. Supply Condition Code E char(1) Supply condition code as described by DLA catalo

(Serviceable/Unserviceable) 

Contract Number E varchar2(21) Used to identify the Contract Number under which 

was procured. 

Contractor Address Line 1 E varchar2(40) Address line 1 for the manufacturer/supplier based Contractor City E varchar2(20) City address of the manufacturer/supplier based on Contractor Postal Code E char(10) ZIP Code address of the manufacturer/supplier basContractor State E char(2) State or province of the manufacturer/supplier baseContractors position Repair/Replace A varchar2(2000) Contractors position as relates to deficiency. DLA Control Number (Action Point) A varchar2(9) Submitting activity's control number, if different th

Action Points control number. This will be the senumber. I.e. DLA Case Control Number, Action PIdentify the system that created the control number 

Corrective Action by Contractor A varchar2(2000) Actions contractor took to fix problem. DLA Form Corrective Action by Government A varchar2(2000) DCMA's verification corrective actions. DLA ForCritical Safety Item E char(1) Indicates whether or not the item is used in a critic

to identify the item as a Critical Safety Item (CSI). 

Deficiency Responsibility Code N char(4) Indicates the responsible/liable party for the deficie

Regulation for appropriate codes. 

Date Deficiency Discovered E date Date deficiency was discovered by the originator. 

Deficiency was Discovered. Date when the deficiediscovered. 

Detailed Cause Code A char(3) PQDR Joint Regulation detailed cause of deficienc

Regulation for appropriate codes. 

DUNS Number E char(9) Manufacturers/Suppliers Dunn and Bradstreet NumDUNS Plus Four E char(13) Manufacturers/Suppliers Dunn and Bradstreet Num

Four number. 

Enclosures Distribution E varchar2(2000) Attachments and mailing codes associated with the 

Block 18. 

End Item Serial Number E varchar2(17) The serial number for the End Item. End Item Type/Model/Series E varchar2(50) The major weapons system with which the end item 

identify the SF368 Block 18c End Item Type/Mod

Estimated Repair Cost E varchar2(15) Estimated cost to repair the deficient material. Evaluation of Current Production A varchar2(2000) DCMA Representatives assessment of the effect on 

Form 1227, Block 15. 

Exhibit Accounted for/Received A char(10) Verification that the exhibit arrived at the correct lDate of Exhibit Final Disposition A date Date of final disposition instructions. 
Instructions Exhibit Final Disposition Instruction A varchar2(2000) The Action Points instruction to Screening or Supp

the exhibit. 

Exhibit Follow-up Date A date Date an exhibit follow-up was forwarded to the exDate Exhibit Received A date Date exhibit was received by the Action or SupporDate Exhibit Requested A date Date the exhibit was requested by the action or supExhibit Required/Requested/Hold A char(10) Verification that the exhibit is required and should Exhibit Return Date A date Date the exhibit was returned to the activity as stip

instructions. 

Exhibit Shipment Number E varchar2(25) Tracking number of the shipper. Exhibit Shipped Date E date The date the exhibit was shipped. Date Exhibit Shipped by Exhibit Warehouse 

A date The date the exhibit was shipped by a warehouse. 

Exhibit shipped to Address E varchar2(500) The address to which the exhibit was shipped. Exhibit Tracking Number E varchar2(16) Shipper’s number provided to the shipping activity Extended Hold Date A date Date the exhibit is to be kept in hold status if beyoFinal Reply for Alerts A char(200) Screening or Action Point information regarding nFinal Reply Results A LONG Final results of the investigation Findings and recommendations A varchar2(4000) Narrative describing the results of the investigation

deficiency and the corrective action to prevent recu

FSC E char(4) Federal Supply Class GBL/CBL Number E varchar2(17) Government or commercial bill of lading. Property Type Code A char(1) Code to distinguish Government-furnished propert

cite the applicable code: Y – GFP R – GFP returned by the contractor to DoD inventoN – Not GFP U – Unknown 

Investigator's Control Number A varchar2(25) Use to identify the Support Points Investigators CItem New/Repaired/Overhauled R char(1) Use to identify the non-conforming materiel as Ite

Repaired/Overhauled Code. Enter N = New, R = = Unknown. Code indicating whether the deficienoverhauled. 

Item under warranty A varchar2(8) Use to identify whether the Item Under Warranty 

Yes, N = No, U = Unknown. Indicates whether thwarranty, if known 

Last Update Date of PQDR A date Use to identify the Last Update Date. Last date th

PQDR II 
Exhibit holding DoDAAC/CAGE A varchar2(100) Use to identify Exhibit Holding DoDAAC/CAG

holding the exhibit. Also known as Exhibit Locatiof the activity that has possession of the deficient m

Location of Exhibit Narrative A varchar2(100) Use to identify the originators Location of Exhib

information about where material is currently locat

Manufacturer Code (CAGE) E char(5) Use to identify SF368 Block 9a Manufacturer CA

material. 

Manufacturer's Address Line 1 E varchar2(40) 1st line address of the manufacturer. Manufacturer's Address Line 2 E varchar2(40) 2nd line address of the manufacturer. Manufacturer City E varchar2(20) City address of the manufacturer. Manufacturer Country E char(2) Country code of the manufacturer. Manufacturer’s Part Number E varchar2(32) Use to identify the SF368 Block 8 Deficient It

known as Supplier/Manufacturers Part Numbematerial. 

Manufacturer Postal Code E char(10) ZIP Code of the manufacturer. Manufacturer State/Province E char(2) State or Province Code address of the manufacMaster/Previous Record Control Number (RCN) 

A char(9) Use to identify Master/Previous Record Contro

the system that created the control number in REF0RCN for same type deficiency. 

MMAC E char(2) Use to identify the Material Management Aggrega

to be managed by a specific manager (i.e., System, selected FSC, technology group). 

Narrative Details E varchar2(4000) Use to identify the originators' SF368 Block 3 DesNext Higher Assembly Nomenclature 

E varchar2(50) Use to identify the SF368 Block 17b Next Higher 

Next Higher Assembly NSN E varchar2(19) Use to identify the SF368 Block 17a Next Higher Next Higher Assembly Part Number E varchar2(32) Use to identify SF368 Block 17c Next Higher Next Higher Assembly Serial No. E varchar2(25) Use to identify the SF368 Block 17d Next Hig

Number. 

Nomenclature E varchar2(100) Use to identify the SF368 Block 6 Deficient Item N

conforming material. 

NIIN/NICN/LSN E varchar2(19) Use to identify the SF368 Block 5 Deficient Item N

or NICN) of the non-conforming material. (FSC + and National Item Identification Number. 

Operating Cycles at Failure E varchar2(15) Unit of measure not related to time prior to fai
Operating Time at Failure E varchar2(15) Use to identify the SF368 Block 7 Operating Tim

Measurement of time prior to failure. Describes hobefore failure. 

Operational Impact Code A char(10) Use to identify the Operational Impact Code. A

on current operations. 

Originator Address Line 1 E varchar2(40) 1st line address of the originator based on DoDOriginator Address Line 2 E varchar2(40) 2nd line address of the originator based on DoOriginator City E varchar2(20) City address of the originator based on DoDAOriginator DODAAC E char(6) Use to identify the DoDAAC of the current Origin

DoDAAC of the Originating Activity 

Originator E-Mail Address E varchar2(120) Use to identify the E-mail address Originator Name E varchar2(70) Use to identify the Originator's name and contOriginator Phone E varchar2(40) Use to identify the Commercial Phone number Originator DSN E varchar2(40) Use to identify the DSN Phone Number Originator Postal Code E char(10) ZIP Code address of the originator based on DOriginator State/Province E char(2) State code address of the originator based on DPrepared By E varchar2(2000) Use to identify the preparing official's information 

Form 1227. Also known as Prepared By

Purchase Order Number E varchar2(20) Use to indicate the Purchase Order Number. Pur

associated with deficient material. 

Quantity Deficient E number(9) Used to identify the SF368 Block 10c Quantity D

conforming material. Quantity deficient items as r

Quantity In Stock E number(15) Use to identify the SF368 Block 10d Quantity In 

material. Quantity of items currently held in stock

Quantity Inspected E number(9) Use to identify the SF368 Block 10b Quantity Ins

inspected by the originator. 

Quantity of Exhibits Received A number(7) Use to identify the quantity of Exhibits Received

received by Action or Support. 

Quantity of Exhibits Requested A number(7) Use to identify the quantity of Exhibits Requeste

requested by Action or Support. 

Quantity of Exhibits Shipped by Originator 

A number(7) Use to identify the quantity of Exhibits Shipped. 

Quantity of Prior Deficiencies A number(5) Use to indicate the Quantity of Prior Deficiencies

reported on previous PQDRs. 

Quantity Received E varchar2(9) Used to identify the SF368 Bock 10a Quantity Re

material received. Quantity deficient items as repo
Date Received/Manufactured/ Repaired/Overhauled 

E date Use to identify the Date of Manufacture. Also k

Rcvd/Mfrd/Rep/Overhauled. Date item was receiv

1227 Review/Release Authority (Name)/info 

A varchar2(2000) Use to identify DLA Form 1227DCMA Review R

by DoDAAC 

Reference Designator A varchar2(10) Use to identify the Reference Designator. Air 

The Ref Des (C017)/LCN (F022) of the item fsubmitted. For the C017 Ref Des refer to the F022 LCN refer to the Integrated Managemen(IMIS). 

Remarks/Recommendations A varchar2(2000) Use to identify Remarks and Recommendations

contractor comments related to the investigation D

Report Control Number E varchar2(25) Use to identify the PQDR Report Control Numb

identifying the PQDR. It is comprised of the six poDODAAC, a two digit calendar year, and a unique 

Requisition Number E varchar2(20) Use to indicate the Requisition Number. Requis

defective material was purchased/reworked. 

Results of Depot Surveillance E varchar2(2000) Use to identify the Depot Surveillance. Use to d

Surveillance. Depot stock screening information. screening depot shocks for similar problems. 

Screening Point Address Line 1 A varchar2(40) 1st line address of the screening point based oScreening Point Address Line 2 A varchar2(40) 2nd line address of the screening point based oScreening Point City A varchar2(20) City address of the screening point based on DScreening Point DoDAAC A char(6) Use to identify the Screening Point DoDAAC. D

Point Activity 

Screening Point E-Mail Address A varchar2(120) Use to identify the E-mail address Screening Point Name A varchar2(70) Use to identify the Screening Point contact inform

information. 

Screening Point Phone A varchar2(40) Use to identify the Commercial Phone number Screening Point DSN A varchar2(40) Use to identify the DSN Phone Number Screening Point Postal Code A char(10) ZIP Code address of the screening point based Screening Point State/Province A char(2) State code address of the screening point baseScreening to Action Date A date Use to identify the Screening to Action Date. A

Release Date - Date the Screening Point released th

Serial Number E varchar2(45) Use to identify the SF368 Block 11 Serial NumbeSeverity of Defect A varchar2(20) Severity of Defect Code. Level of Severity of th
PQDR Joint Regulation for appropriate codes. 

Shipper Address Line 1 E varchar2(140) 1st line address of the screening point based oShipper Address Line 2 E varchar2(40) 2nd line address of the screening point based oShipper City E varchar2(36) City address of the screening point based on DShipper Code E char(6) Use to identify Shipper of the non-conforming mat

CAGE or DoDAAC. The Shipping activity who de

Shipper Country E char(2) Country code of the shipper. Shipper Name E varchar2(70) Use to identify the Shipper's name and contacShipper Postal Code E char(10) ZIP Code address of the shipper. Shipper State/Province E char(2) State code address of the shipper. Special Material Identification Code (SMIC) 

E char(2) Use to identify the 2 digit SMIC of the End Item. 

Source of Supply E char(3) Use to identify the Source of Supply. Routing Id

source of supply. 

Support Point Cause of Deficiency A varchar2(2000) Use to identify the Cause of Deficiency narrative

Root cause of deficiency found during the investig

Standard Reporting Designator A varchar2(3) Use to identify the three-character Standard Repo

Code. Air Force code related to the end item of th

Date Submitted by Originator A date Use to identify the date the PQDR was comple

submitted to the Screening Point. Also known Preparation Date, Originator Release Date, ScThis is the SF368 Date. The date the SF368 wFormerly Block 1c Date Submitted on the old 

PQDR Supplemental Data A varchar2(4000) Used to identify Supplemental Data. Additional 

PQDR investigation. 

Support Point Address Line 1 A varchar2(50) 1st line address of the support point based on DSupport Point Address Line 2 A varchar2(40) 2nd line address of the support point based on Support Point City A varchar2(20) City address of the support point based on DoScreening Point Control Number A varchar2(14) Use to identify Screening Point Control Numbe

created the control number in REF03. Control numPoint if different from the RCN 

Support Point DoDAAC A varchar2(25) Use to identify the DoDAAC of the current Suppo

DoDAAC of the Support Point activity handling th

Support Point Due Date A date Use to identify the Support Point Due Date. Dat

back to the Action Point. Only Support Point may 
Support Point E-Mail Address A varchar2(120) Use to identify the E-mail address Support Point Postal Code A char(10) ZIP Code address of the support point based oSupport Point Name A varchar2(70) Use to identify the Support Point name and coSupport Point State/Province A char(2) State or Province Code address of the support Support Point Phone A varchar2(40) Use to identify the Commercial Phone number Support Point DSN A varchar2(40) Use to identify the DSN Phone Number Support to Action Date A date Use to identify the Support to Action Date. Also 

Release Date. Date PQDR was returned to the Acti

Source Server A varchar2(10) ISA 06, see page 2 of 842P, also must use the Target Server A varchar2(10) ISA 08, see page 2 of 842P, also must use the Time Since New/Overhaul A number(7) Use to identify the quantity of Time Since New

since last repair and material failure. Number(

Time Since Installation A number(7) Use to identify the quantity of Time Since Ins

between installation and material failure. Num

Unit Cost (Total) E varchar2(15) Use to indicate "total" value of defects in Defectiv

deficient material based on the unit of issue 

Unit Cost (Single Item) E number(11,2) Use to identify "unit" value of a "single" defective 

Cost. Cost of the deficient material based on the u

Unit of Issue E char(2) Related to the type of QTY reported. Refer to 

Purchase Unit Conversion Table for available 

Warranty Expiration Date E date Use to identify the Warranty Expiration Date. D

the defective material 

Work Unit Code/EIC A varchar2(50) Use to identify the Work Unit Code (WUC) of th

Work Unit Code or Equipment Item Code of defecthe Table of Authorized Material (TAM) code in th

New Fields for PQDRII End Item NSN E varchar2(19) Use to identify the SF368 Block 18a End Item NSCurrent Disposition A char(1) Current Disposition. SF368 Block 19: Use cod

Disposed of/Destroyed, R-Repaired, or O-Oth368. 

Screening Point Rebuttal/ Controvert Date 

A date Date the Screening Point rebutted the final reply fr

Re-open Request Date A date Use to identify PQDR the Re-open Request Date

to be re-opened 

Transaction Code E char(2) Code used to describe the purpose of the 842 t
Date/Time Stamp A date+timestamp Date stamp used in the 842 ISA and GSA segm

the transaction 

UII E varchar2(50) Use to report only a single occurrence of the IUID

the HL IUID Loop. The approved code/name is "UUnique Item Identifier. The UII may not exceed 5with IUID Policy 

Preventative Action Taken E varchar2(2000) . Use to identify the Preventative Action Taken (A

the DLA Form 1227, Block 13b. 

Materiel Disposition Instructions A varchar2(2000) Use to identify the Materiel Disposition instructi

Support Points Material Disposition instructions fo

Action Requested Code A char(1) Action Requested code as shown on the SF368

Credit, R-Repair, E- Replacement, or O-Other. 

Cost Code A char(1) Cost Code. Also known as DLA Cost Code. Use 

(Commercial Supplier), G-Cost to Navy (Gov’t MfGov’t (Commercial Supplier), U-undetermined, Z-Mfg/Supplier). 

Credit Code A char(1) The Credit Code. Use Codes C-No Credit (Comm

by user, G-No Credit (Gov’t Supplier), N-Credit (CVendor Replacement, R-Vendor Repair, S-Source Unknown, W-Credit Authorized, X-No Credit AutSupplier). 

Defect Verified Code A char(1) Code used to indicate whether the defect actually e

codes N-Defect not verified, O-Other Than reporteVerified. 

Government Source Inspection Code A char(1) Use to identify the Government Source Inspecti

No. Code used to indicate whether GSI is required

Recovery Value A number(11,2) Use to indicate the amount of recovered or reconsi

processing the PQDR. Also known as Recovery Vdollar amount recovered or reconsideration receiveDeficient) 

Signal Code E char(1) Used to identify the Signal Code. (Required wh

number)

Fund Code E char(2) Use to identify the Fund Code. (Required when c

Two position alpha/numeric code used to designate or noninterfund). When interfund billing is indicatindicates the fund account to be charged (disbursed

Supplementary address E char(6) Use to identify the Supplementary Address (D

credit if not the PQDR originators organizatio
is 'B' or 'K'. The DoDAAC to which credit is DoDAAC. (Required when signal code is B o

Credit memo (DLA reference for credit) 

A varcahr2(30) Use to identify the DLA Credit Memo Number. 

to track credit. 

PQDR Status Code A char(2) Use to identify unique PQDR II Status Codes. Co

status of the PQDR. See list of approved Status Co

Last Repair Facility A char(6) Use to identify the CAGE or DoDAAC of Last RePOC to Receive Information Copy E varchar2(30) Use to identify the Point of Contact to receive inEngine Model Number A varchar2(17) Use to identify Engine Model Number.Batch or Lot Number E varchar2(20) Use to identify the SF368 Block 11 Batch, lot or 

the non-conforming material. 

End Item Nomenclature E varchar2(25) Use to identify Use to identify the End Item NomEnd Item CAGE E char(5) Use to identify the End Item CAGE associated wPrime Contractors Code E char(5) Use to identify the Prime Contractors CAGE Co

conforming material. Staffing note: Use the Qualifier ZB in the LIN segidentify the supplier of the non-conforming materiN1 segment to provide an address that is different listed with the CAGE in Central Contractor RegistIdentification Number Cross- Reference System (B

Acknowledge Date A date Use to identify the Acknowledged Date by the seExhibit Hold Date A date Use to identify the Exhibit Hold Date. Date an it

disposition. 

Cancel Date A date Use to identify the date of the customer's request to 

submitted PQDR. 

Defect Code (originator) A char(3) Use to identify the PQDR originators Defect Cod

Attribute Code, Malfunction Code. Three charactereported by the originator. 

Document Number E varchar2(20) Use in responses, as needed to identify the doc

which replacement material will be provided tthe deficiency, or the document number proviauthorizes the return of deficient material or e

Criticality Code - Federal Item Identification Guides 

E char(1) Use to identify the Federal Item Identification G

Controlled Inventory Item Code E char(1) Use to identify the Controlled Inventory Item CDemilitarization Code E char(1) Use to identify the Demilitarization Code
General Correspondence (Narrative) A varchar2(2000) Use to identify the narrative comments associated 

Status comment used to pass General CorrespondWhen data is corrected, comments should explain 

Credit Value E number(11,2) Use to indicate the amount of credit/debit being au

Also known as DLA Credit Value

Distribution Recipient E varchar2(30) Use to identify recipient of the distribution copy 

non-transaction method 

Party Executing and Verifying E Char(6) Use to indicate the Enterprise Identifier (EID) resp

of the IUID Issuing Agency Code (IAC) may be defor the Enterprise Identifier by CAGE or DoDAAC

Party to Receive Credit E char(6) Use to identify the DoDAAC of the activity to rece

validated PQDR. This is applicable only when the receive credit if not the PQDR originator’s organiz

Party to Receive Reports E char(6) Use to identify additional parties to receive a co

electronic retransmission of the 842P by DoDAAC

Mark For E varchar2(30) Use to identify the Mark For party to receive an eCause Code E char(2) Use to identify Cause Code. Use only DLA CausEngine Serial Number A varchar2(45) Use to identify an Engine Serial Number. Next Higher Assembly CAGE A char(5) Use to identify the Next Higher Assembly CA

NHA's part number. 

End Item Part Number A varchar2(32) Use to identify the End Item Part Number. Transaction Item Reporting (TIR) (Tiring) Date 

A date Use to identify the Transaction Item Reporting 

This is the date carcass tracking was complete

Credit Date E date Use to identify the date credit was issued. Transportation Control Number E varchar2(17) Use to indicate the Transportation Control NuShipping Instructions A varchar2(2000) Use to provide, explain, or otherwise describe 

Instructions 

Review Release Authority A varchar2(30) Use to identify the review official's information as

1227. Also known as Review Release Authority1227 previous to release. 

Responsible Person (at receiving location) 

A varchar2(30) Use to indicate a POC at receiving location. Al

shipments to indicate the Government representativ

Preventative Action Taken Code (7th position). 

A char(1) Preventative Action Taken Code used to indica

to prevent recurrence. See PQDR Joint Regulation 

Rebuttal/Controvert Code A char(2) Use to identify the reason for rebuttal using the Re
Enclosure 4, Comment Resolution 

Originator Response/Comment Disposition 

1. DLA Concur. 

Additionally, DLA concurs with enhanced exhibit tracking portion of the PDC. Comments: 1. Where is clear guidance in the PDREP system to notify the customers who use the item that there is an investigation ongoing; or an item has been found to be flawed or suspect counterfeit and I have not found any clear guidance that says we should notify the customers who use the item. I don't see it in the 77 pages (other than note 22 that sends a copy to interested parties not in the system) of this change. Can you tell me if it's in there and I just missed it? 2. DLA Land and Maritime concurs with the PQDC 1007 with one change: The reason for rebuttal code (enclosure 3, page 12) should be identified as a 2 character code in lieu of a single character code. The Rebuttal element is listed on page 36 as: CW Controvert Code DLMS Note: Use to identify the PQDR Rebuttal/Controvert Code. Must use in a reply rebuttal transaction 

1. PDREP Assurance Specialist ResponDoD has a policy document out on repormaterial, see AT&L memorandum, Over

Prevention Guidance, dated March 16, 2implement as they see fit. The team has been discussing and plans proposed DLMS change to supplement tbusiness rule requirements which will coonce each service has agreed, on how to business rule that each IT system must chaving all those rules documented in a P842P is rolled out by IT systems. Navy has already implemented within thInformation System (AIS), the requiremto report on PQDRs using the Detailed C

Counterfeti, Suspect' and building an int

permit action points to send agency actiowith a copy of the suspect counterfeit PQservices/agencies may use this if desiredare marked in PDREP with the 5AS cod

submitters can look on the SF368 of a PQsuspect counterfeit code has been added

action points can add 9or remove) the 5Asubmission by the originator within the P

has opted not to do this at this time.) 
Originator Response/Comment Disposition 

(BNR01Code=RR). Staffing Note: Rebuttal Codes will be provided as a part of a DLMS approved data change to this standard. The PQDR team members discussed and concurred with this change. 

Also, several agencies are already notifiemarked with a 5AS in PDREP-AIS. If a

with a need to know requires notification PDREP Customer Support Desk know. The 5AS code is currently transmitted in existing infrastructure with DLAs EBS a5AS code will be transmitted in the 842P 

2. ADC updated as requested. 

2. Marine Corps Concur Noted. 3. Navy Navy concurs with proposed changes. 

1. Change paragraph 1.b.(2) Navy Functional POC: From: Navy: NAVSUP WSS code 854, 717-605-1746 To: Navy: NAVSUP HQ Code N311, 717-605-8343 2. NAVSUP supports this effort because we currently have a 100% manual effort, which is rarely completed. An automated method to track PQDR exhibits should be supported, as lost exhibits/lost exhibit requests are our biggest 

reason for not completing a PQDR investigation. 

Noted. 1. ADC POC information updated. 2. Standard logistics transactions for recand shipment status have been updated t

4. Army Concur with comment 

COMMENT 1: Page 3; 5, c. - PQDRII is supposed to be a stopgap measure so it shouldn't be referenced in this document as a permanent 

Noted. Responses provided by Navy (PDREP-A1. The current joint regulation for PQDR 
Originator Response/Comment Disposition 

solution. COMMENT 2: Page 6; 7, b. Disadvantages - Potential to gray lines that should remain black and white. Aviation issues cannot be treated the same as those for ground items. There is much more detail required for ANY aviation component than there are for components of ground materiel. COMMENT 3: Page 7; a. Funding was provided to everyone (all 3 databases) through April of 2013.  b. July 2012 has been pushed forward by 6 months. COMMENT 4: Page 7; 9. Estimated Time Line/Implementation Target should be updated. COMMENT 5: Enclosure 1, Page 1, C25.3 - (normally the item manager) should be removed. This is not value added to the document and is not true for all Components. Also (normally the Defense Contract Management Agency (DCMA)) should be removed for the same reason. These comments apply only to DLA and not to the Joint process. 

component system", as of today and for component system has been the PQDR Ia stop gap and no determination has been PQDRII yet. The new draft also refers tsystem as the PQDRII. With looming buevaluation will be coming as we all look processes, including IT overhead. If and into something else, a PDC can and will PQDRII to whatever other software perffunctions of tracking and routing PQDRThe 842P team plans on submitting a PDrules that the 842P team has put together business rules will define the minimum rsystems are expected to handle PQDR dPQDRII (aka cross component system) rpossible we'll include any of the codes frReview Team and have those added in aprovide the same codes wherever possib2. The 842P is written to flow down higdoes not we should fix it) and should be or strengthen those defined processes. Oprocesses that are triggered by the DoD and expected for processing within Servincluding unique aviation processes, uniprocesses, unique tank and armaments pweapons systems with critical design feafor PQDRs does not prevent Services frounique processes; however, when the daService (or IT system) it must conform tthe 842P so the receiving organization (othe data its sent and what they are expec
Originator Response/Comment Disposition 

agreement between Services on a new dacurrently unique process by one service should be imposed on other services, the opportunity to state the case and gain copreviously have. Nothing is written in ssponsor a PDC. For example, we've begtracking and I noticed in another thread fconcerning flow of credit info. 3. Funding should not be addressed in thshould update the schedule for deployme4. PDREP is operating under the DLA twill strive to meet DLAs timeline. 5. C25.3 paragraph is just a PQDR overprocess. It must be universally understoOriginator, Screening Point, Action Poinwhat their actual function is. There are sdescribing these functions in the current draft version. Maybe reference to the joprovide the appropriate clarity. DLA Logistics Management Standards Oparagraph C25.1 does reference the joinNote that if the SOS is never notified of their supplier or their supply chain. Engalone don't get these existing stock screeresolved. Notifying the SOS that there amaterial they are procuring for the field preventing recurrence of material quality responsible for coordinating the investig
Originator Response/Comment Disposition 

info together, from engineers, labs, suppscreened ect ... and ensuring it's all docuinvestigation results. 

5. Air Force Concur Noted. 6. DLA 

Transaction Services 

There were several issues/concerns I had with the 842P proposal. 1. Inclusion of codes in higher ANSI versions is a problem. There are probably workarounds I can do to accommodate this, but I would need a complete list of the inclusions before I could determine any possible resolutions. Another potential issue may be validations of the X12 data at the routing level (i.e. before & after processing the transactions). 2. DLA Trans Svcs does not have a clear idea of what the pass-thru routing rules are expected to 

be. At the very least, what data element within the 842P would be used to route the transaction forward? 3. We need to determine if transactional routing is established for all the potential recipients. 

Also, depending on the recipient list, we would need to know if additional connections might be required to include the 842P transaction in process data flows. 4. Answers to the above questions are needed to determine what is needed (resources, timeframe, etc.) to implement this requirement. 5. The XML statement is confusing because current XML files do not contain the ISA and GS information within them. So, if intent is to use 

Discussion with PDREP Assurance Specclarification to resolve DLA Trans Svcs 1. All local codes (codes proposed for amigration codes (codes approved for use than documented for the 842P) are clearSupplement. DLA Trans Svcs will ensuacceptable for processing. 2. Identification of the receiving activitythe current inter-service interface. The padd in the new routing rules inter-service providing additional info copies. 3. Regarding DLA Trans Svcs pass-thru Services opening transaction (to include required iDOC format for EBS: If requir

enhancement, PDREP team and DLA m

DLA Transaction Services. The envelop

cause issues with routing to multiple Serthis time if the DLMS EDI-based XML format will be preferred. Capability to tconsidered during design; the document the attachment. These decisions are defeenhancements. 4. PDREP will work with DLA Trans S
Originator Response/Comment Disposition 

XML format, routing may be a problem. design plan is supported by the necessar

7. USTRANSCOM Abstain Noted. 8. Supply PRC 

Chair 

I am finalizing the ADC and wanted to confirm 

that your concurrence included the extra additional functionality I was advocating for the three DLMS transactions to carry the PQDR RCN (and the additional “party to receive copy” identifying PDREP). I only received feedback from Ramon Marin on the exhibit tracking (comment resolution in last enclosure) and since there is impact on DLA DSS, I wanted to be sure DLA concurred. I think capturing the PQDR RCN in the receipt is a good process since you could get multiple receipts as the exhibit moves and you would be able to track the movement better. The receipt would be more functionally correct than the current SDR notification. Today when an exhibit shipment is directed (e.g. for testing at lab), I believe the MRO uses exception data to identify the exhibit (would like confirmation on how this works – how the depot records the exhibit so it can be located for shipping when MRO is provided). Is the PQDR RCN unique to the one exhibit? Will using the PQDR RCN work for the MRO....if included on the MRO it could be systemically perpetuated to the outgoing shipment status and trigger the additional party to receive copy so PDREP gets 

Responses provided by Navy (PDREP-APDREP Concurs and will work to integrvarious transaction types into the DoD PThis additional data flow should help exThe 842P team will need to develop subintegration of that data, this is a very big 
Originator Response/Comment Disposition 

the information copy without manual effort to update PDREP for exhibit tracking. 

9. DLMS Data 

Team 

New purpose codes for PQDRs were identified in PDC 1007 (DLMS 842P). 

Nine Code Maintenance Requests (CMRupdate of the X12 standard. The current CMR submission window clthe 21-day member review period will c

Logistics Management Office personnel reply appropriately. Assuming there are adds will be approved at the next TechniSubcommittee (TAS) meeting (Feb/Mar “officially” added to the next X12 versio

January, 2014. Once approved by TAS available, the DLMS supplement will be 

indicating local codes are employed (wo

refer to “migration” codes).