1 of 6 

Attachment, ADC 474 

ATTACHMENT TO ADC 474 

New MRA Discrepancy Indicator Code (STAFFED AS PDC 464) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATON: Defense Logistics Agency, 

Supply Process Review Committee representative, DLA J33, 703-767-7297 (DSN 427)

2. FUNCTIONAL AREA: Supply, MRA Reports, Logistics Metrics Analysis Reporting 

System (LMARS)

 

3. REFERENCES: 

a. DOD 4140.1-R, DOD Supply Chain Materiel Management Regulation, available at: 

www.dtic.mil/whs/directives/corres/pdf/414001r.pdf

b. DLMSO memorandum, November 17, 2000, subject: ADC 42, Removal of the MRA 

Exclusion for Navy Manual Ships, available at www.dla.mil/j-6/dlmso/elibrary/changes/approved2.asp 

 c. DOD 4000.25-M, Defense Logistics Management System (DLMS), Volume 2, Chapter 10, 

available at www.dla.mil/j-6/dlmso/elibrary/manuals/dlms/v2.asp 

d. DOD 4000.25-2-M, Military Standard Transaction Reporting and Accounting Procedures 

(MILSTRAP), Chapter 6, available at www.dla.mil/j-6/dlmso/elibrary/Manuals/MILSTRAP/default.asp 

e. March 24, 2011, Navy-DLA Partnership Council (PAC) Meeting 

4. APPROVED CHANGE: 

NOTE: Changes from the PDC are highlighted in yellow throughout this ADC 

 a. Description of Change: Create a new MRA discrepancy code for use with Navy ships to 

indicate that an MRA is being submitted in response to a follow-up request, but that there has not yet 

been an opportunity to pick-up/stow the order due to deployment or extended transit times. 

b. Implementation Date: DOD Component implementation dates were not established at 

time of release of this ADC. Components must monitor for implementation of ADC 474 and 

advise DLA Logistics Management Standards office of projected implementation dates when 

known. DOD 4140.1-R (reference 3.a.), Appendix 13, requires that DOD Components provide the 

DLA Logistics Management Standards office with status on implementation of approved DLMS 

changes. 

 c. Background: 

	 	 1) The MILSTRAP administrator notes that at one time Navy manual ships were 

excluded from the MRA process. The Navy manual ship exclusion was removed at Navy’s 
2 of 6 

Att, ADC 474 

request by ADC 42 (reference 3.b.), as all Navy afloat units were by that time operating under 

automated systems with MRA capability.

2) DLA has noticed a high volume of MRA responses from Navy ships that contain 

Discrepancy Indicator Code F (Shortage or partial or total nonreceipt), after sending an MRA followup for delinquency. NAVSUP indicated that this code gets used when the ship has not yet had the 

opportunity to return to port and pick up its order. It is possible that the materiel has been received at 

a Navy Local Logistics Support Center (LSC) or Materiel Processing Center (MPC) and is being 

held for the ship. The MPCs do not receipt for the materiel since they only are holding it and do not 

have an accountable record. MPCs do provide supply status to the ship to notify the ship that the 

shipment has arrived. The MRA transactions with Discrepancy Indicator Code F lead DLA to believe 

that the order is missing, and also skew metrics such as Logistics Response Time (LRT) and Perfect 

Order Fulfillment (POF) by erroneously closing out the order too soon with that MRA. 

d. Detailed Procedures: 

 1) Revise DOD 4000.25-2-M, MILSTRAP, AP 2.17, Discrepancy Indicator Code, as shown 

in Enclosure 1 to add a new Discrepancy Indicator Code G for use with MRA transactions. 

Corresponding change will be made to the DLMS Data Dictionary. 

 2) When an MRA contains the Discrepancy Indicator Code G, the Inventory Control Point 

(ICP) will not close out the order and will send another follow-up for MRA after another 45 days have 

passed (if an MRA without code G is not submitted beforehand). Revise MILSTRAP Chapter 6 as 

shown in Enclosure 2. Corresponding changes would be made to DLMS, Volume 2, Chapter 10. 

 3) PDC STAFFING NOTE TO NAVY: How many Discrepancy Indicator G codes should 

be accepted for a given MRA? ADC NOTE: Navy was asked to provide, in their response to PDC 

464, guidance to help set a limit for the maximum number of G codes that should be allowed/accepted. 

The MILSTRAP Administrator addressed this requirement with the Navy and DLA Supply PRC 

representatives, and agreement was reached that a maximum number of six submissions of 

Discrepancy Indicator Code G would be allowed for MRA for a given shipment. If a reply is not 

received within 45 calendar days from the sixth DRB with Discrepancy Indicator Code G, the ICP 

shall include the delinquency information in the management evaluation report. The 

MILSTRAP/DLMS procedures at Enclosure 2 reflect this. 

e. Alternative: Add an additional 45 days to the MRA follow-up timeframes presented in 

MILSTRAP/DLMS for Navy ships (identified by DoDAACs that start with ‘R’ or ‘V’), which will 

provide limited additional time for deployed ships to receive their orders. 

5. REASON FOR CHANGE: To reduce the number of MRAs from Navy ships that contain 

Discrepancy Indicator Code F when the reason is the ship’s deployment schedule interfering with 

pick-up. This is a documented problem for Navy ships discussed at the March 24, 2011, Navy-DLA 

Partnership Council (PAC) call (reference 3.e.). At the referenced PAC meeting, Navy and DLA 

agreed that something should be put into place to prevent the large volume of MRA transactions with 

Discrepancy Indicator Code F, when the reason is the ship’s deployment schedule interfering with 

pick-up. This ADC addresses this problem. 

6. ADVANTAGES AND DISADVANTAGES: 
3 of 6 

Att, ADC 474 

 a. Advantages: Reduces investigation of Discrepancy Indicator Code F in MRA transactions 

from Navy ships, where nothing can be done due to deployment schedules. Also corrects metrics that 

key off of MRA submission. 

 b. Disadvantages: Requires system changes at DOD Component ICPs and at Navy ship MRA 

reporting activities. 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: DOD Components must 

identify to the DLA Logistics Management Standards office when this change can be 

implemented. DLA identified their earliest possible implementation as the latter half of Fiscal Year 

2013. The Services did not identify an implementation timeframe at the time this ADC was 

published.

8. IMPACT:

 a. Changes to DLMS Data Elements: No new DLMS data element. Revises an existing 

DLMS data element to add a new code value. 

 b. DLA Transaction Services: Edit Logistics Reports-MRA Summary Reports and 

LMARS business rules to accommodate this functional change as noted below: 

1) This use of the new Discrepancy Indicator Code G shall only apply to requisitions from 

DoDAACs beginning with letters V and R. The Defense Automatic Addressing System (DAAS) 

Receipt date of the MRA will be recorded for every MRA of this type received in Logistics On-Line 

Tracking System (LOTS). This is a change to the way all DAAS receipt dates are stored now. 

Presently, the DAAS receipt date is frozen after the first transaction of a given type. In order to 

identify multiple Discrepancy Indicator Code G transactions received one after another, the MRA 

DAAS receipt date of a transaction with a Discrepancy Indicator Code G will be updated with each 

new transaction. An MRA, with other than a Discrepancy Indicator Code of G received from a V or 

R DoDAAC, after an initial G coded MRA, will also update the DAAS receipt date. This ensures 

that the final MRA has the actual customer receipt date in LMARS and in MRA, and is reported in 

the actual month it was received. An MRA with Discrepancy Indicator Code G, from DoDAACs 

beginning with letters V and R, received after an initial MRA with other than a Discrepancy 

Indicator Code G, will not be recorded in LOTS. Current LOTS MRA processing rules will still 

apply to all non V or R transactions as well as V or R transactions where a Discrepancy Indicator 

Code G was never received. 

 2) The MRA Reports will not count an MRA containing a Discrepancy Indicator Code G as 

an MRA “received.” This code will add 45 days to the time limit (CONUS and OCONUS) used to 

determine when an MRA is successfully received. Up to 6 MRAs with code Discrepancy Indicator 

Code G may be submitted. 

 3) LMARS will not use an MRA containing a Discrepancy Indicator Code G to populate the 

CUST-RECEIPT-DATE, TPT-NODE, or RTT-NODE fields with an MRA/customer receipt date. 

 4) Multiple MRAs (up to a maximum of 6) with Discrepancy Indicator Code G will be 

accepted from V or R DoDAACs, limited to one per LMARS monthly cycle. Since LMARS and 

MRA are a "snapshot in time", MRAs with Discrepancy Indicator Code G might be received 

after the monthly LMARS cycle has started. These MRAs will not be considered in either 
4 of 6 

Att, ADC 474 

LMARS or MRA if an earlier MRA has been received. In LMARS, once a segment is reported 

on, it is never reported on again. 

 5) If an MRA with Discrepancy Indicator Code G is received after the original 60 or 

120 day time limit for MRA receipt, the order will be considered in non-receipt. 

6) This will not affect Supply Discrepancy Report (SDR) use of LOTS data. 

7) MRA Discrepancy Indicator Code G is only authorized for use by Navy ships. If 

Discrepancy Indicator Code G is used by other than a Navy ship, the reporting activity and ICP 

must follow existing MILSTRAP/DLMS procedure for activities that acknowledge receipt with 

erroneous information, as shown in this excerpt from current DLMS, Vol 2, Chapter 10: 

"C10.2.8. Correcting or Canceling an MRA 

 C10.2.8.1. Identification of Erroneous Information. Activities that acknowledge a 

materiel receipt in error shall not correct the MRA. However, to ensure validation of any SDR for 

the shipment, the reporting activity must identify the erroneous MRA information in the SDR 

remarks (SF364) or in the NTE segment of DS to Federal IC 842A/W, SDR Follow-up, Correction, 

Cancellation, & Reconsideration Request. 

 C10.2.8.2. Error Documentation. When the ICP receives an MRA that does not 

match a shipment record, or contains errors, the ICP shall document the error in the management 

evaluation report or quality control data, as applicable.” 

c. Automated Information Systems (AIS): 

 1) Service and DLA ICPs: Change MRA follow-up logic in supply systems to recognize 

the new code and process per this requirement. 

 2) DOD Component MRA Reporting activities: Navy ship MRA reporting activity 

systems require update to use this code when applicable. Discrepancy Indicator Code G is only 

authorized for use by Navy ships (identified by DoDAACs that start with R or V). Navy ships 

using Discrepancy Indicator G must be in receipt of Supply Status NL indicating that materiel 

has been received by the LSC or MPC. 

d. Publications: 

 1) Requires revision to MILSTRAP Chapter 6 (MRA) and Appendix 2.17, Discrepancy 

Indicator Codes. 

 2) Requires revision to DLMS, Volume 2 Chapter 10 (MRA) and DLMS Data Dictionary 

Discrepancy Indicator Codes. 

 3) May require revision of DOD Component publications. 

e. New or revised DLMS Data: 

 1) No new DLMS data elements. 

 2) Revises existing DLMS data element to add a new code value. 
5 of 6 

Att, ADC 474 

9. PDC 464 RESPONSE TABLE: 

Organization Comment to PDC 464 Disposition 

DLA Logistics 

Management 

Standards 

office 

1. All DOD Component Supply PRC 

representatives must monitor for implementation of 

this this ADC and provide this office with their 

Component projected implementation date when 

available. 

 

2. The procedures will allow for up to six (6) DIC 

DRB (or DLMS 527R equivalent) transactions with 

code G for a given record. Allowing up to 6 DIC DRB 

MRA transactions with code G, to be submitted would 

provide up to 315 days to receive the materiel. The 

limitation was reached after MILSTRAP 

Administrator discussion with the Navy and DLA 

Supply PRC representatives. 

MRA procedures updated accordingly at 

Enclosure 2.

DLA Concurs without comment. There will be a system 

change. Earliest possible implementation would be the 

latter half of FY13. 

The DLA Supply PRC representatives 

must monitor for DLA implementation 

of ADC 474 and provide projected 

implementation date when known. 

ARMY CONCUR w/comments - LMP doesn't use the 

DRA/DRB to 'close out' a requisition. LMP just writes 

the delivery PGI information to a table and generates 

DRFs based on PGI date and non-receipt of DRA. 

Note that under ADC 474, the Army, and 

all DOD Components would need system 

logic to recognize and respond to new 

Discrepancy Indicator Code G when 

provided on MRAs from Navy ships, as 

described in this change. The Army 

Supply PRC representative must monitor 

for Army implementation of ADC 474 

and provide projected implementation 

date when known. 

AIR FORCE Concurs without comments. The Air Force Supply PRC 

representative must monitor for Air 

Force implementation of ADC 474 and 

provide projected implementation date 

when known. 

NAVY Concurs as written and submits no additional changes 

or amendments. 

The Navy Supply PRC representatives 

must monitor for Navy implementation 

of ADC 474 and provide projected 

implementation date when known. 
6 of 6 

Att, ADC 474 

Organization Comment to PDC 464 Disposition 

MARINE 

CORPS 

Concur with comments: 

1. SASSY will accept the D6* transaction, with the 

Discrepancy Code, and convert the transactions the 

appropriate DRA. Note: The D6* receipt transactions 

screens has capability of entering a Discrepancy Code, 

is only available in ATLASS. Data entry does not 

provide that capability of entering a Discrepancy 

Code. 

2. After reviewing the GCSS-MC receipting process, it 

does not appear that GCSS-MC has incorporated the 

Discrepancy Code into the systems platform. 

3. MOWASP not the Stock Control System (SCS) 

have the capability of inserting a Discrepancy Code 

into either system. 

4. The Marine Corps should adopt the codes currently 

restricted to the intra-ARMY use. The codes listed as 

intra- ARMY use are directly in line with the SDR 

reporting and should be utilized in conjunction with 

the SDR. 

The Marine Corps Supply PRC 

representative must monitor for 

implementation of ADC 474 and provide 

projected implementation date when 

known. 

 

For comment #4, Marine Corps would 

need to submit a separate PDC to 

propose Marine Corps use of the codes 

currently identified as intra-Army. 

Please note that as defined, Army uses 

the codes with the D6_ receipt 

transaction only, and not with MRAs. 

USTRANSCOM Abstains 

Enclosures
AP2.17-1 

APPENDIX 2.17 

Enclosure 1, ADC 474 

ENCLOSURE 1 TO ADC 474 

AP2.17. APPENDIX 2.17 

DISCREPANCY INDICATOR CODES 

ADC 474 revisions identified by red bold italics. Also contains administrative updates in black bold 

italics. 

NUMBER OF CHARACTERS: One 

TYPE OF CODE: Alphabetic 

EXPLANATION: A one-digit code used in the MRA to indicate when a supply or 

transportation discrepancy or product quality deficiency affects 

the receipt posting and/or MRA process. 

Intra-Army Codes M through T are used with intra-army receipt 

(other than procurement instrument source) (DIC D6_) 

RECORD POSITIONS: 63 of MRA (DIC DRA/DRB) 

80 (intra-Army use only) of Other Than Procurement 

Instrument Source Receipts (DIC D6_). 

CODES USE WITH MRA: 

CODE DEFINITION 

A SDR being submitted. (Excludes shortage and partial or total nonreceipt.) 

B No record of requisition. (Use in DIC DRB reply to DIC DRF follow-up if there is no 

record of the requisition and the materiel has not been received.) In DLMS use with 

527R MRA in response to a follow-up (identified by beginning segment BR02 code 

TH with BR06 Action Code V). 

C Reserved for future DoD assignment. 

D Transportation discrepancy report being submitted. (Excludes shortage and partial or 

total nonreceipt.) 

E Product quality deficiency report being submitted. 

F Shortage or partial or total nonreceipt. Quantity not received entered in record 

positions 25-29 of MRA. 
AP2.17-2 

APPENDIX 2.17 

Encl 1, ADC 474 

CODE DEFINITION

G Nonreceipt due to extended transit time. (Use in DIC DRB reply to DIC DRF 

follow-up, if more time is needed to pick up the materiel.) Only for use by Navy 

ships and only when materiel is being held at a Navy Local Logistics Support Center 

or Materiel Processing Center. In DLMS use with 527R MRA in response to a 

follow-up (identified by beginning segment BR02 code TH with BR06 Action Code 

V). 1

H-L Reserved for future DoD assignment. 

M-T Assigned for intra-army use as indicated below. 

U-W Reserved for future DoD assignment. 

X Discrepant receipt, other than shortage and partial or total nonreceipt, which does not 

meet qualifying criteria for discrepancy report submission. 

Y-Z Reserved for future DoD assignment. 

THE FOLLOWING CODES ARE USED WITH INTRA-ARMY RECEIPT (OTHER THAN 

PROCUREMENT INSTRUMENT SOURCE) TRANSACTIONS (DIC D6_): 

CODE DEFINITION 

M Damaged Receipt (for intra-Army use) 

N Receipt Storage (for intra-Army use) 

O Reserved for future DoD assignment 

P Receipt Overage (for intra-Army use) 

Q Wrong Material (for intra-Army use) 

R Duplicate Receipt (for intra-Army use) 

S Receipt previously processed as a Materiel Receipt Discrepancy (for intra-Army use) 

T Condemned Upon Receipt or Shelf-Life Expired (for intra-Army use) 

 

1

 Refer to ADC 474. As required by DOD 4140.1-R, the DoD Components must provide 

implementation status for this approved change. DLA has identified their earliest possible 

implementation as the latter half of Fiscal Year 2013. 
1 of 2 

MILSTRAP Chapter 6 

Enclosure 2, ADC 474 

ENCLOSURE 2 TO ADC 474 

Revise DOD 4000.25-2-M, MILSTRAP Chapter 6, paragraph C6.7, as shown in 

this enclosure. Revision identified by red bold italic text. Corresponding changes will 

be made to DLMS, Volume 2, Chapter 10.

C6. CHAPTER 6. 

MATERIEL RECEIPT ACKNOWLEDGMENT 

C6.7. FOLLOW-UPS FOR DELINQUENT MATERIEL RECEIPT ACKNOWLEDGMENT 

 C6.7.1. When materiel shipment is confirmed or when the requisition involves an 

unconfirmed MRO as described in MILSTRIP chapter 3, the ICP shall will monitor for 

receipt of MRA(s). MRA must be received for the total quantity shipped within 45 

calendar days from the date released to carrier for shipments to CONUS activities, 

within 105 calendar days from the date released to carrier for shipments to overseas 

activities, or within 135 days from the DIC ASH pseudo shipment status release date for 

security assistance requisitions. Otherwise, the ICP shall send a DIC DRF follow-up, 

prepared in the appendix AP3.30 format. 

 C6.7.2. To answer the follow-up, the reporting activity shall fill out an MRA 

following the C6.6. procedures but entering DIC DRB in record positions 1-3. Send the 

MRA to the ICP within 15 calendar days from the transaction day in the follow-up. 

C6.7.3. In the event that materiel has not been received because a Navy ship 

has not yet had the opportunity to physically pick it up (it is awaiting pick up at a 

Navy Local Logistics Support Center or the Material Processing Center), the Navy 

ship reporting activity shall respond with a DIC DRB containing Discrepancy 

Indicator Code G in rp 63. This will signal the ICP to keep the requisition record 

open and continue to monitor for receipt of MRA(s), and send another DIC DRF 

after another 45 calendar days have elapsed (which may be responded to with 

another an additional DIC DRB with Discrepancy Indicator Code G if the ship is 

unable to pick up their materiel from the Navy Local Logistics Support Center or 

the Material Processing Center). The Navy ship reporting activity may send up to 

six MRA transactions in response to follow-up, using DIC DRB with Discrepancy 

Indicator Code G. The Navy ship reporting activity shall send an MRA, using DIC 

DRB, without the Discrepancy Indicator Code G in rp 63, once the materiel is 

received (e.g., picked-up or otherwise delivered directly to the ship), which may 

include the use of other discrepancy codes as appropriate. If a reply is not 

received within 45 calendar days from the sixth DRB with Discrepancy Indicator 

Code G, the ICP shall include the delinquency information in the management 

evaluation report (C6.10). Also, if the requisition involves an unconfirmed MRO 

(see MILSTRIP, chapter 3, C3.21 (Processing Follow-Ups)), then the ICP shall 

resolve the record as described in MILSTRIP, Chapter 3, C3.22 (Force Closed 

Materiel Release Confirmation). 
2 of 2 

MILSTRAP Chapter 6 

Encl 2, ADC 474 

 C6.7.34. Except as noted in C6.7.3., if a reply is not received within 30 calendar 

days from the follow-up transaction date, the ICP shall include the delinquency 

information in the management evaluation report (C6.10). Also, if the requisition 

involves an unconfirmed MRO (see MILSTRIP, Chapter 3, C3.21 (Processing FollowUps)), then the ICP shall resolve the record as described in MILSTRIP, Chapter 3, 

C3.22 (Force Closed Materiel Release Confirmation).