DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

April 28, 2016

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

Change in Timing to Follow-up for Delinquent Materiel Receipt Acknowledgement

(MRA), and for MRA Submission, Based on Time Definite Delivery (TDD) 

Standards (Supply/MILSTRAP/DAAS)

The attached change to DLM 4000.25, Defense Logistics Management Standards, 

DLM 4000.25-2, Military Standard Transaction Reporting and Accountability Procedures 

(MILSTRAP), and DLM 4000.25-4, Defense Automatic Addressing System (DAAS) is 

approved for staggered implementation. 

Transaction Services requires 3-4 months after release of this ADC to implement MRA 

Report changes based on the revised timeframes documented by this change. Transaction 

Services requires 15 to 18 months after release of this ADC to implement the new discrepancy 

indicator code. The DOD Components did not provide implementation dates. Accordingly,

the Supply PRC representatives must actively monitor for implementation of this ADC in 

their automated information systems and provide DLMSO with their Component 

implementation date when known.

Addressees may direct questions to Ms. Mary Jane Johnson, email: 

Mary.Jane.Johnson@dla.mil, or Ms. Heidi Daverede, email: Heidi.Daverede@dla.mil. Others 

must contact their Service or Agency designated Supply PRC representative available at

https://www2.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp.

DONALD C. PIPP

Director

Defense Logistics Management 

Standards Office

Attachment

As stated 

cc: 

ODASD(SCI)

Pipeline Management PRC
Attachment, ADC 1114 

Page 1

ATTACHMENT TO ADC 1114

Change in Timing to Follow-up for Delinquent Materiel Receipt 

Acknowledgement (MRA), and for MRA Submission, Based on Time Definite 

Delivery (TDD) Standards 

1. ORIGINATOR: Defense Logistics Agency, DLA J341, 703-767-1565 (DSN 427)

2. FUNCTIONAL AREA: Primary: Supply/Logistics

3. REFERENCES: 

a. DOD Manual (DODM) 4140.01, DOD Supply Chain Materiel Management Procedures, 

February 10, 2014

b. DOD Instruction (DODI) 4140.61, Customer Wait Time and Time Definite Delivery, 

December 14. 2000.

c. “DOD Time Standards for Order Process and Delivery” document available at

http://www.acq.osd.mil/log/sci/policy_vault.html

d. Defense Logistics Manual (DLM) 4000.25, Defense Logistics Management 

Standards, Volume 2, Supply Standards and Procedures

e. DLM 4000.25-2, Military Standard Transaction Reporting and Accountability 

Procedures (MILSTRAP)

f. DLM 4000.25-4, Defense Automatic Addressing System (DAAS)

g. ADC 474, New Materiel Receipt Acknowledgment (MRA) Discrepancy Indicator 

Code (Supply/MILSTRAP)

4. APPROVED CHANGE: Substantive updates subsequent to staffing are identified in green 

highlighting.

a. Brief Overview of Change: Allow an automated follow-up for delinquent materiel 

receipt acknowledgment (MRA) transactions at a number of days beyond shipment more aligned 

with the Time Definite Delivery (TDD) standards set forth in the DODM 4140.01, Volume 8,

DODI 4160.61, and the DOD Time Standards for Order Process and Delivery (References 3.a., 

3.b., and 3.c. respectively). Provide for MRA submission timeframes associated to TDD. 

Modify the timeframe to send an MRA Reply to Follow-Up transaction. Modify the timeframe 

for submission of MRA after receipt of materiel, to align with DODM 4140.01 timeframe for 

receiving activities to process receipts after materiel delivery.

b. Background and Current Process: 

(1) The MRA transaction provides evidential matter supporting Audit 

Readiness. DLA identified MRAs as key transactions for proving to auditors that the DLA

inventory control point (ICP) appropriately paid vendors and billed customers for Direct Vendor 
Attachment, ADC 1114 

Page 2

Delivery (DVD) contract shipments. The significance of MRAs is further emphasized by

DODM 4140.01, Volume 5, Delivery of Materiel, in the section for Item Accountability and 

Control policy for materiel in-transit, which states that “The owning DoD Component directing 

materiel into an in-transit status will retain accountability within their logistics records for that 

materiel (to include resolution of shipping and other discrepancies) until the consignee or 

receiving activity formally acknowledges receipt.”

(2) DLM 4000.25, DLMS, Volume 2, Chapter 10 (Reference 3.d.) and DLM 

4000.25-2, MILSTRAP, Chapter 6 (Reference 3.e.) require that MRA reporting activities 

provide an MRA to the ICP within 5 calendar days of receipt of materiel. If the ICP does not 

receive an MRA after 45 days from the date of shipment (for CONUS), the ICP sends a Followup for Delinquent MRA transaction (DLMS 527R with 1/BR02/020 Transaction Type Code 

TG/legacy Document Identifier Code (DIC) DRF). DLA typically accrues interest penalties for 

nonpayment from vendors after 30 days of the vendor shipping materiel directly to a customer. 

However, DLA advises that they are receiving fewer than 70 percent of MRAs for DVD materiel 

within 30 days and fewer than 70 percent of Class II, IV, & IX MRAs up to 5 months after 

shipment.

(3) Transportation Categories: The established transportation categories 

(TC) are identified to assist in understanding the ensuing discussion of the proposed changes to 

the MRA follow-up timeframes. 

(a) TC 1 – Priority Designator (PD) 01 through PD 03 regardless of RDD

(b) TC 2 – PD 04 through 15 in conjunction with DLMS Special 

Requirements Codes (mapped to the legacy MILSTRIP Required Delivery Date (RDD) field) 

444, 555, 777, 999, N__, E__, or RDD 8 days or less (CONUS), or RDD 21 days or less 

(OCONUS)

(c) TC 3 – PD 04 through 15 with Special Requirements Codes (legacy 

RDDs) that are blank or the RDD is a date greater than 8 days (CONUS), or a date greater than 

21 days (OCONUS). In general practice, other transactions not meeting the TC1 or TC2 

criteria will go under TC3 (e.g., when the first position of the DLMS Special Requirements 

Code (legacy RDD) is S or X). MILSTRIP transaction edits blank out the Special 

Requirements Code/RDD field when the specific RDD conditions identified in Table C4.T4 of 

Reference 3.d. are not met. 

(4) TDD standards are based on the ship-to location. Each major location 

(CONUS, AFRICOM, CENTCOM, NORTHCOM, EUCOM, PACOM, and SOUTHCOM) may 

be further divided into different regional standards. Table 1 shows a sub-section of the TDD 

Standard for each Combatant Command (COCOM)/Region based on the DOD Time Standards 

for Order Process and Delivery for the Transportation and Theatre Segments (Reference 3.c.). 

For CONUS (NORTHCOM) the intransit segment and the DODM 4140.01 default of 5 days for 

receipt take-up is shown in the bottom rows of Table 1. For the OCONUS COCOMs, the last two

segments for each COCOM and region were used and the average, high, and low were calculated 

for each TC identified in Reference 3.c. 
Attachment, ADC 1114 

Page 3

Table 1. Time Definite Delivery Standards Calculation

Transportation Segment (D) Time and Theatre Segment (E) Time

With the exception of CONUS, the last two segments for each COCOM and region were 

used for the timeframes for the non-Receipt MRA and for the Follow-up for Delinquent 

MRA. The averages, highs and lows were calculated for each transportation category 

(TC) identified in Reference 3.c.

(5) For Navy ships, MRA Discrepancy Indicator Code G – Nonreceipt Due to 

Extended Transit Time was authorized by ADC 474 (Reference 3.g.) This is used in the MRA 

Reply to Follow-up (527R MRA/legacy DIC DRB), if more time is needed to pick up the materiel

being held at a Navy Local Logistics Support Center or Materiel Processing Center. This added an 

additional 45 days to the MRA follow-up timeframes in MILSTRAP/DLMS for Navy ships 

(identified by DoDAACs that start with ‘R’ or ‘V’), and provides limited additional time for 

deployed ships to receive materiel. This adjustment is reflected in Table 1 for the Navy columns 

associated with TC1, TC2, and TC3.

c. Approved Change in Detail: The revised MRA follow-up timeframes align with 

TDD standards for delivery of materiel. The timeframe for submitting MRA after materiel is 

received, from within 5 calendar days to within 5 business days, to align with DOD policy

(Reference 3.a.).

(1) Revise MILSTRAP, Chapter 6, and corresponding DLMS, Volume 2, 

Chapter 10, to allow for MRA follow-ups based upon the TDD Standard according to the 

schedule identified in Table 2. The revised MRA Follow-Up timeframes identified in Table 2 

are derived from the TDD Standards identified in Table 1 by using the highest number within the 
Attachment, ADC 1114 

Page 4

COCOM Region for each transportation category to determine an MRA Follow-up timeframe for 

each transportation category.

(a) CONUS (NORTHCOM). For a more consistent and reasonable MRA

approach based on the narrow time difference for the three transportation categories in CONUS 

(NORTHCOM), the MRA timeframe for reporting non-receipt was revised to 12 days for all 

three transportation categories, rather than have MRA reporting required at 7, 9, or 12 days 

dependent on the TC. For the MRA follow-up, 5 days were added to arrive at the CONUS 

Follow-up for Delinquent MRA timeframe of 17 days. The extra 5 days were added to allow

time for processing a non-receipt MRA. 

(b) OCONUS. In Table 2, the highlighted days in the “Others Segment” 

reflect the highest number of days by COCOM/Region shown in Table 1 for each TC. To 

simplify the approach, based on the close time difference between the highest figures for TC 1 

and 2, the MRA timeframe for reporting non-receipt was revised to 29 days for both TC 1 and 

TC2, rather than have MRA reporting required at 15 days for TC 1 and 29 days for TC 2. TC 3

was revised to 76 days. For the MRA follow-up, 5 days were added to arrive at the Follow-up 

for Delinquent MRA timeframe of 34 days for TC 1 and 2, and 81 days for TC3. The extra 5

days were added to allow time for processing a non-receipt MRA.

Table 2. MRA Follow-Up Timeframe Based on TDD

COCOM Others Segment D+E Navy Afloat Segment D+E

TC1 TC2 TC3 TC1 TC2 TC3

AFRICOM 15 17 50 64 66 99

CENTCOM 11 29 76 27 45 92

NORTHCOM 8 13 22 8 13 22

EUCOM 12 22 47 31 41 66

PACOM 13 23 44 44 54 75

SOUTHCOM 11 17 29 11 17 29

NORTHCOM (CONUS) 7 9 12 12 12 12

Transportation Categories

TC 1 OCONUS Issue Priority Group (IPG) 1 (World Wide Express (WWX) or local truck).

TC 2 OCONUS IPG 2 and 3 (Military Air) with required delivery date (RDD) requesting fast delivery 

TC 3 OCONUS IPG 2 and 3 (Surface) with and RDD not requesting fast delivery

*Navy TC1 and TC2 were combined and this segment breakout applies to Navy operational DoDAACs 

beginning with V and R and does not apply to those beginning with N (See ADC 474)

(2) Revise MILSTRAP Chapter 6, MRA and Appendix 4 MRA Time Limits 

for Reporting Activities, to (refer to Enclosures 1through 4 for the specific changes to the 

manual):

(a) modify timeframe to submit MRA reflecting non-receipt taking TDD 

standards into consideration,
Attachment, ADC 1114 

Page 5

(b) modify the timeframe to send an MRA Reply to Follow-Up in

response to an MRA Follow-Up. The MRA Reply to Follow-Up is decreased from 15 to 10 

calendar days from the transaction day in the MRA Follow-Up,

(c) modify the timeframe for U.S. Forces to send an MRA after materiel is 

received, to within 5 business days from date materiel received, rather than within 5 calendar

days. This is consistent with DODM 4140.01, Volume 5 receipt processing timeframe

(Enclosure 3, AP4.1.1).

(d) modify the MRA Time limits for ICPs and Disposition Services, to 

reflect modified timeframes to generate an MRA Follow-up reflecting the TDD timeframes,

which include the transaction processing time, and also to allow time for processing a NonReceipt MRA (DRA with Discrepancy Indictor Code F) (Enclosure 3, AP4.1.2).

(3) Add new Discrepancy Indicator Code H (materiel is still in transit) to 

MILSTRAP, Appendix 2.17, Discrepancy Indicator Codes. Components will use it in the MRA 

Reply to Follow-Up when responding to an MRA Follow-Up and the Component research 

identified that the materiel is still in transit. The reporting activity may send up to six MRA 

transactions in response to follow-up, using MRA Follow-up transactions with Discrepancy 

Indicator Code H (Enclosure 3).

Staffing Note 1: This is similar to Discrepancy Code G – Nonreceipt Due to Extended Transit 

Time, added in ADC 474 for Navy use when additional time is needed to pick up the materiel 

being held at a Navy Local Logistics Support Center or Materiel Processing Center. Navy Units 

with DoDAACs starting with V or R would use Discrepancy Code H for materiel in transit and 

use G for the stated purpose. 

(4) Document a new requirement in the MRA chapters to submit an MRA 

when materiel is received after an MRA is submitted for the two scenarios noted below: 

(a) The submitted MRA conveys Discrepancy Indicator Code F Shortage, 

partial or total nonreceipt (MRA Discrepancy Indicator Code F), (reference MILSTRAP 

C6.6.6.3), (Enclosure 1).

(b) The submitted MRA conveys Discrepancy Indicator Code B – No 

Record of Requisition. An MRA is required when materiel is subsequently received after an 

MRA Reply with Discrepancy Indicator Code B – No Record of Requisition was the original 

response (reference MILSTRAP C6.6.6.6), (Enclosure 1).

(5) Business Rules for MRA Reports 

(a) MRA Reports. Updates the MRA Report business rules to reflect the 

revised MRA follow-up and reply to follow-up timeframes. Enclosure 3 reflects the revisions 

needed to identify the qualifying shipments to include in the MRA Reports. The MRA Report 

business rules revisions identified in Enclosure 4 reflect the revised timeframes identified in 

Enclosures 1 and 2 for CONUS and OCONUS shipments. The MRA Reports will continue to be 

broken out into CONUS and OCONUS sections but the OCONUS section will not be broken out 

further to show Transportation Category 1 and 2 and Transportation Category 3. 
Attachment, ADC 1114 

Page 6

(b) Document a new MRA report business rule: An MRA Reply to Followup transaction with MRA Discrepancy Indicator Code B or F is not reported as “No MRA” in the 

MRA reports prepared by Transaction Services, it is reported as receiving an MRA. The MRA 

report is created at the end of each month to reflect the MRA transactions as received/not received 

in the preceding month. Receipt of an MRA citing Discrepancy Code B or F will update the

Logistics Metrics Analysis Reporting System (LMARS) reports to reflect the current status of MRA 

transactions received. However, because of how MRA reports are created, they will not be 

adjusted retroactively when an MRA is submitted following receipt of materiel after an MRA 

citing Discrepancy Indicator Code B or F is received.

Staffing Note 2: Summary of Transaction Services comments: An MRA is counted the first 

time it is received. Transaction Services recommends that if a Discrepancy Code B or F is 

received in response to an MRA Follow-up, and then in the next few months, Transaction 

Services receives a new MRA with a different discrepancy code, that the document number is 

NOT opened for MRA re-reporting. The document number was originally reported as receiving 

an MRA in both LMARS and MRA reporting, so it was not a negative for anyone. Depending 

on the timeframe that the new MRA is received, the original requisition and its data might 

already be purged off the files. Once an MRA is received and reported, the LMARS master 

record stays on the LMARS file and the Logistics On-line Tracking System (LOTS) files for 

only 90 days.

Transaction Services recommended that since the MRA is reported on the first time it is received 

(MRA and LMARS Reports), that no further reporting be done except for the exclusion of 

Discrepancy Coded G and H records.

d. Revision to DLM 4000.25 Manuals:

(1) Revise DLM 4000.25-2, MILSTRAP, Chapter 6, MRA, as shown in 

Enclosure 1 (DLMSO will make corresponding changes to DLM 4000.25, Volume 2, Chapter 10).

(2) Revise DLM 4000.25-2, MILSTRAP, Appendix 4.1, paragraph 4.1.1. Time 

Limits for Reporting Activities, and paragraph 4.1.2. MRA Time Limits (Follow-Up for 

Delinquent MRA), as shown in Enclosure 2.

(3) Revise DLM 4000.25-2, MILSTRAP, Appendix 5.1 Materiel Receipt 

Acknowledgement Report Business Rules as shown in Enclosure 4 (DLMSO will make 

corresponding changes to DLM 4000.25, DLMS, Volume 2. Appendix 12 and DLM 4000.25-4, 

DAAS Appendix 7). In Appendix 5.1, several occurrences of the word “overseas” were changed 

to “OCONUS” to reflect that not all OCONUS locations are overseas.

(4) Revise the Logistics Data Resources Management System (LOGDRMS)

Data Element 1270 Code EI – Discrepancy Indicator Code; and DLM 4000.25-2, MILSTRAP, 

Appendix 2.17, Discrepancy Indicator Codes (MRA), as shown in Enclosure 3.

e. Alternatives: None identified.
Attachment, ADC 1114 

Page 7

5. REASON FOR CHANGE:

a. More closely aligning MRA submission for nonreceipt, as well as Follow-up for 

Delinquent MRA, with TDD standards will result in more timely MRAs and increase the odds of 

avoiding or reducing penalties set forth in most contracts requiring payment of vendors in a 

timely fashion.

b. A more timely reply to an MRA Follow-Up will help to minimize interest accrual. 

This is because purchase orders for which the contractor has shipped the materiel, start 

accumulating interest when the contract invoice is over 30 days old. 

c. Revising the timeframe for U.S. Forces to send an MRA after materiel is received, to 

within 5 business days from date materiel received, rather than within 5 calendar days, aligns the 

MRA timeframe with the DODM 4140.01 receipt timeframe. DODM 4140.01, Volume 5, 

Enclosure 3, paragraph 8.b. requires that receiving activities will record receipts no later than 5

business days from date materiel received. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

(1) The intent of this approved change is for the customers and ICPs to execute 

the MRA process in a more timely, realistic manner, by factoring in the various time definite 

delivery standards established by the United States Transportation Command in coordination with 

the Combatant Commanders that are used to optimize the overall supply chain. Aligning the 

follow-up timeframe with TDD timeframes will provide a more realistic MRA submission and 

follow-up timeframe based on negotiated TDD standards for when materiel should be received

within a specific theatre.

(2) Based on the new follow-up timeframes, associated to TDD, ICPs should 

receive MRAs in a timelier manner in both CONUS and OCONUS, thus assisting DOD in avoiding 

additional costs (interest penalties). This also provides for more timely closure of intransit records.

b. Disadvantages: None identified.

7. ADDITIONAL FUNCTIONAL REQUIREMENT FOR FUTURE CONSIDERATION: 

Combatant Command (COCOM) Area Requirement. At Supply PRC Meeting 13-3, the committee

discussed a change to the MRA Report AREA headings from CONUS and/or OCONUS, to SAME 

AREA and DIFFERENT AREA to more accurately reflect COCOM designation and provide a 

more realistic representation of MRA Timeframes. This requirement will be considered for a future 

change.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: 

a. DOD Components. DOD Components are authorized staggered implementation for 

this change to the MRA timeframes and for use of new Discrepancy Indicator Code H. All Supply 

PRC representatives must actively monitor for implementation of this ADC in their 

automated information systems and provide DLMSO with their Component implementation 

date(s) when known.
Attachment, ADC 1114 

Page 8

Staffing Note 3: DLA and Services comment on their time frame to implement this change.

Component Responses:

DLA: DLA will provide timeline for implementation after DLA sends requirements to DLA J6, 

after release of ADC.

Navy: This change will impact Navy ERP in the future; the plan is to include it as part of the 

series of changes required to implement the MRA follow-up program in Navy ERP. DLMSrelated changes to Navy ERP are currently under review and have not yet been prioritized. The 

program is aware of the mandate to be DLMS compliant by 2019 and plans to complete required 

DLMS changes by the end of CY 2019.

b. Transaction Services:

(1) Transaction Services time line to implement the MRA Report changes 

based on the revised timeframes is 3–4 months after the ADC is released.

(2) Transaction Services timeline to implement Discrepancy Indicator Code H 

is 15 to 18 months after the ADC is released. The changes required to implement Discrepancy 

Indicator Code H (materiel still in transit) will require modification to the Logistics On-line 

Tracking System (LOTS), Logistics Metrics Analysis Reporting System (LMARS) and MRA 

Reports. 

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not identified.

10. IMPACT:

a. New DLMS Data Elements: No new DLMS data element is proposed by this change.

b. Changes to DLMS Data Elements: Discrepancy Indicator Code. Add new code 

value H to the existing Logistics Data Resource Management System (LOGDRMS) Data 

Element ID 1270 Qualifier EI - Discrepancy Indicator Code. Also refer to DLM 4000.25-2, 

MILSTRAP Appendix 2.17, Discrepancy Indicator Code. New Discrepancy Indicator Code H = 

Materiel still in transit.

c. Automated Information Systems (AIS):

(1) DOD Component ICP systems must change the timeframe to send DLMS 

Follow-up for Delinquent MRA transactions to customers, based on customer location and 

transportation mode, and recognize/process the new Discrepancy Indicator Code H.

(2) DOD Component MRA reporting activity systems must implement the 

change(s) required to:

(a) revise timeframes to submit an MRA,

(b) process multiple follow-ups sent at revised timeframes identified in this 

change, and 

(c) use new Discrepancy Indicator Code H.
Attachment, ADC 1114 

Page 9

d. Transaction Services: Transaction Services will have specific programming 

changes to address the revised MRA Follow-Up and submission timeframes, and to address new 

Discrepancy Indicator Code H. 

e. Non-DLM 4000.25 series Publications: Components should consider changes to 

internal guidance, as needed.

11. PDC 1114 Response Table:

Component Component Response DLMSO Response

DLA Concur with comment:

In paragraph 4.c.(1)(a) and (b), DLA adjusted the 

number of days added to derive MRA follow-up 

from three/four to five in CONUS and OCONUS 

for consistency. This adjusted the Follow-up for 

Delinquent MRA timeframes to 17 days for 

CONUS and OCONUS TC1 and 2 at 34 days and 

TC 3 at 81 days. Change was made through out 

the ADC. 

Estimated Timeline/Implementation Target: DLA 

will provide timeline for implementation after 

requirements are sent to J6 after release of ADC.

DLMSO Concurs

Noted. The DLA Supply PRC 

representative must actively monitor 

for implementation of this ADC and 

provide DLMSO with the DLA 

implementation date when known.

Transaction 

Services

Staffing Note 4: Transaction Services 

comment/address impacts of this change on 

existing reports being generated.

Response: 3-4 months for all MRA report 

changes. 15-18 for the LOTS changes for the 

discrepancy code changes in LOTS.

For the Transportation Categories, what date 

should be used to compare the 8 or 21 days to 

determine if it is TP3, Serial date, Birthdate (First 

time we see a requisition. If no requisition, the 

date we receive the first transaction).

Noted.

Per discussion, use the date transaction 

services receives the initial requisition 

or supply transaction . Additionally if 

the transaction is not TC 1 or 2, then it 

is TC3.

Air Force Concurs without comment. Noted. 

The Air Force Supply PRC 

representative must actively monitor 

for implementation of this ADC and 

provide DLMSO with the Air Force 

implementation date when known.
Attachment, ADC 1114 

Page 10

Component Component Response DLMSO Response

Army The Army concurs with comment.

Comment: A change would be required for LMP 

to be able to respond to an MRA follow-up with 

a discrepancy indicator code of 'H' if material is 

still showing as in-transit.

Noted.

12/17/15 DLMSO email [Johnson] 

noted that the larger magnitude of the 

changes were to the MRA follow-up 

and response timeframes. Accordingly 

Army will also have systems changes 

such as LMP sending follow-ups based 

on the revised timeframes; Army 

MRA reporting activities need to 

respond to follow-ups that are sent 

based on revised timeframes; Army 

MRA reporting activities have revised 

timeframes in which they must submit 

MRAs for nonreceipt, etc. 

The Army Supply PRC representative 

must actively monitor for 

implementation of this ADC and 

provide DLMSO with the Army 

implementation date when known.

Marine Corps Concur with PDC as written Noted. 

The Marine Corps Supply PRC 

representative must actively monitor 

for implementation of this ADC and 

provide DLMSO with the Marine 

Corps implementation date when 

known.

Navy Concur with PDC.

This change will impact Navy ERP in the future; 

the plan is to include it as part of the series of 

changes required to implement the MRA followup program in Navy ERP. DLMS-related 

changes to Navy ERP are currently under review 

and have not yet been prioritized. The program 

is aware of the mandate to be DLMS compliant 

by 2019 and plans to complete required DLMS 

changes by the end of CY 2019.

Noted. 

The Navy Supply PRC representative 

must actively monitor for 

implementation of this ADC and 

provide DLMSO with the Navy

implementation date when known.

USTRANSCOM Abstains. There is no impact to USTRANSCOM 

systems based on this change

Noted.

Enclosures
Enclosure 1, ADC 1114

Page 1

ENCLOSURE 1 TO ADC 1114

Revise DLM 4000.25-2, Chapter 6, MRA, as follows (changes identified by bold, red, italics

and double strikethrough). Comparable changes will be made to the DLMS Manual, Volume 2, 

Chapter 10:

Preceding text not shown

C6.5. POLICY

C6.5.1. Reporting Activities and ICPs will meet the time limits stated throughout this chapter 

and summarized in Appendix AP4.1.

C6.5.2. Reporting Activities, excluding ILCOs, will:

C6.5.2.1. Establish supply due-in records for all requisitions (pulled or pushed) being 

supplied from wholesale stock. It is not required to establish a due-in record when shipment status 

is received after the materiel has been received.

C6.5.2.2. Update (or establish, when no previous record of the due-in/materiel receipt 

exists) due-in records and estimated delivery dates, based on supply and shipment status 

received. Establish due-in record estimated delivery dates which equal the Appendix AP4.1 

timeframes. (i.e., the shipment status release day (document identifier code (DIC) AS_/AU_ record 

positions 57-59) plus 30 or 90 calendar days for shipments to continental United States (CONUS) 

or overseas activities, respectively)

Intervening text not shown

C6.6. PREPARING AND SENDING MATERIEL RECEIPT ACKNOWLEDGMENT

C6.6.1. Reporting activities will submit an MRA when a materiel receipt is posted to the retail 

stock record, stock record account, property account, or equivalent record. Also, submit an MRA 

when due-in dates are reached and materiel has not been received. Send an MRA to the ICP:

C6.6.1.1. Within five calendar 5 business days of materiel receipt.

C6.6.1.2. 3012 calendar days from the release date when a shipment to a CONUS 

activity has not been received.

C6.6.1.3. 29 calendar days from the release date when a Transportation Category 

1 or 2 shipment to an OCONUS activity has not been received.

C6.6.1.4. 9076 calendar days from the release date when a Transportation Category 

3 shipment to an OCONUS activity has not been received.

Intervening text not shown

C6.6.6. To acknowledge receipt of a discrepant/deficient shipment, submit an MRA, except 

as noted below, with the appropriate discrepancy indicator code (Appendix AP2.17) in record 

position 63. Note that these requirements and timeframes are independent from prescribed 
Enclosure 1, ADC 1114 

Page 2

shipment tracing and discrepancy/deficiency reporting requirements and timeframes to which the 

receiving facility must also adhere.

C6.6.6.1. If the document number cannot be identified, post the receipt using a local 

document number. Do not submit an MRA.

C6.6.6.2. If the stock number/part number of the item received cannot be fully entered 

in record positions 8-22, leave blank. If stock number/part number cannot be fully entered in 

record positions 8-22 and is a wrong item or cannot be identified, leave record positions 8-22 blank 

and enter Discrepancy Indicator Code A in record position 63.

C6.6.6.3. For total or partial nonreceipt (Discrepancy Indicator Code F)

C6.6.6.3.1. Enter the quantity not received in record positions 25-29, Discrepancy 

Indicator Code F in record position 63, and the transaction preparation day in record positions 60-62.

C6.6.6.3.2. If materiel is received subsequent to submitting an MRA Reply 

with Discrepancy Indicator Code F, submit a new MRA reflecting the new/additional 

quantity received following the MRA procedures in C6.6.1

C6.6.6.4. Except for shortage and partial or total nonreceipt, covered in C6.6.6.3., enter 

a code X in record position 63 of the MRA if the discrepancy does not meet discrepancy reporting 

criteria.

C6.6.6.5. When the discrepancy causes the receipt to be posted using more than one 

transaction (e.g., multiple supply condition codes or multiple stock numbers are received), send an 

MRA for each transaction posted. If needed, also send an MRA for any quantity not received.

C6.6.6.6. If materiel is received after submitting an MRA Reply with Discrepancy 

Indicator Code B (No Record of Requisition), submit an MRA following the MRA procedures 

in C6.6.1. 

C6.6.6.7. The MRA report is created at the end of each month to reflect the MRA 

transactions as received/not received in the preceding month. Receipt of an MRA citing 

Discrepancy Code B or F updates the Logistics Metrics Analysis Reporting System 

(LMARS) reports to reflect the current status of MRA transactions received. The MRA 

Reports are created monthly and reflect the MRA data at the end of each month and will not 

be adjusted retroactively when an MRA is submitted following receipt of materiel after an 

MRA citing Discrepancy Indicator Code B or F is received.

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 will monitor for receipt of 

MRA(s). MRA must be received for the total quantity shipped within 45 12 calendar days from 

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

the date released to carrier for shipments to OCONUS activities for Transportation Category 1 

and 2, 76 calendar days from the date released to carrier for shipments to OCONUS 

activities for Transportation Category 3, or within 135 days from the DIC ASH pseudo 

shipment status release date for security assistance requisitions. Otherwise, the ICP will send a 

DIC DRF follow-up, prepared in the Appendix AP3.30 format. See Appendix 4, AP4.1.1.
Enclosure 1, ADC 1114 

Page 3

C6.7.1.1. The MRA Follow-up timeframes are based upon the existing Time Definite 

Delivery (TDD) Standards and take into account the wide variation in TDD timeframes based 

on the Combatant Commands/Regions and the allowed receipt take-up timeframe. 

C6.7.1.2. The follow-up time limits for a delinquent MRA are 17 calendar days from 

the date shipped field entry in the MRC or DIC ASH Shipment Status for Conus, 34 calendar 

days for OCONUS destinations with Transportation Category 1 and 2, and 81 calendar days for

OCONUS destinations with Transportation Category 3. See Appendix 4. AP4.1.2. 

C6.7.2. To answer the follow-up, the reporting activity will shallwill out an MRA following 

the procedures in C6.6, but entering DIC DRB in record positions 1-3. Send the MRA to the ICP 

within 1510 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 will respond with a DIC 

DRB containing Discrepancy Indicator Code G in record position 63. This will signal the ICP to 

keep the 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 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 shallwill send an MRA, using DIC 

DRB, without the Discrepancy Indicator Code G, 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 shallwill include the delinquency information in the 

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

(see MILSTRIP, Chapter 3, (Processing Follow-ups)), then the ICP shallwill resolve the record as 

described in MILSTRIP, Chapter 3, (Force Closed Materiel Release Confirmation).

C6.7.4. When Component research into a DIC DRF (Follow-Up For Delinquent MRA) 

identifies that materiel is still in transit, the reporting activity will respond with a DIC DRB 

containing Discrepancy Indicator Code H in record position 63. This will signal the ICP 

to keep the record open and continue to monitor for receipt of MRA(s), and send another 

DIC DRF after another 45 calendar days have elapsed.1

 If a reply is not received within 45 

calendar days from the sixth DRB with Discrepancy Indicator Code G, the ICP will include 

the delinquency information in the management evaluation report (C6.10). Navy afloat 

units should use Discrepancy Indicator Code H if they determine the materiel is still 

intransit and not at an MPC. 

C6.7.5. 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 will include the delinquency information in the 

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

(see MILSTRIP, Chapter 3, (Processing Follow-ups)), then the ICP will resolve the record as 

described in MILSTRIP, Chapter 3, (Force Closed Materiel Release Confirmation).

 1 Refer to ADC 1114.
Enclosure 2, ADC 1114 

Page 1

ENCLOSURE 2 TO ADC 1114

Revise DLM 4000.25-2.Appendix 4.1, MRA Time Limits, as follows (changes identified by 

double strikethrough and bold, red, italics). Comparable changes will be made to the relevant 

tables in DLMS Manual, Volume 2, Chapter 10:

DLM 4000.25-2, Month xx, year

Change x

AP4.1. APPENDIX 4.1

MATERIEL RECEIPT ACKNOWLEDGMENT TIME 

LIMITS1

AP4.1.1. Time Limits for Reporting Activities:2

ACTION TIME LIMIT

U.S. Forces Send 

MRA

* 5 calendar5 business days from date materiel received, and:

 3012 calendar days from the DIC AS_ date shipped field entry 

(CONUS destination) for nonreceipt;

or

 9029calendar days from the DIC AS_ date shipped field entry 

(OverseasOCONUS destination) for nonreceipt for 

Transportation Category 1 and 2

 76 calendar days from the DIC AS_ date shipped filed entry 

(OCONUS destination) for nonreceipt for Transportation 

Category 3

ILCOs Send 

MRA

* 120 calendar days from the DIC ASH (Pseudo Shipment Status for 

Unconfirmed Materiel Release Orders) date shipped field entry for 

security assistance shipments.

Send MRA in 

Reply to FollowUp

* 1510 calendar days from transaction day in DIC DRF follow-up.

* Means take the action before the time limit is reached.

 Means take the action when the time limit is reached.

 1 Refer to ADC 1114. 2 These requirements and timeframes are independent from prescribed shipment tracing and discrepancy/deficiency 

reporting requirements and timeframes to which the receiving facility must also adhere.
Enclosure 3, ADC 1114 

Page 2

AP4.1.2. Time Limits for ICPs/DLA Disposition Services:

The Time Limits below for an MRA Follow-up reflect the TDD timeframes, which include

the transaction processing time, and also allow time for processing a Non-Receipt Materiel 

Receipt Acknowledgement.

ACTION TIME LIMIT3

Follow-Up for 

Delinquent MRA

 45 17 calendar days from the date shipped field entry in 

the MRC or DIC ASH Shipment Status for U.S. Forces 

shipments (CONUS destination).

 34 calendar days from the date shipped field entry in 

the MRC or DIC ASH Shipment Status for U.S. Forces 

shipments (OCONUS destination) for Transportation 

Category 1 and 2. 

 10581 calendar days from the date shipped field entry in 

the MRC or DIC ASH Shipment Status for U.S. Forces 

shipments (OverseasOCONUS destination) for 

Transportation Category 3.

135 calendar days from the date shipped field entry in the 

DIC ASH Shipment Status for security assistance 

shipments.

 Means take the action when the time limit is reached.

 3 Refer to ADC 1114
Enclosure 3, ADC 1114

Page 1

ENCLOSURE 3 TO ADC 1114

Revise DLM 4000.25-2, Appendix 2.17.1, Discrepancy Indicator Codes, as follows (changes 

identified by bold, red, italics):

DLM 4000.25-2, Month xx, year

Change xx

AP2.17. APPENDIX 2.17

DISCREPANCY INDICATOR CODES

NUMBER OF CHARACTERS: One

TYPE OF CODE: Alphabetic

EXPLANATION: A one-digit code.

Used in the Material Receipt Acknowledgement (MRA) 

transaction to indicate when a supply or transportation 

discrepancy or product quality deficiency affects the receipt 

posting and/or MRA process. MRA is DLMS 527R with 

Transaction Type Code TH or legacy DIC DRA/DRB.

Discrepancy Indicator Codes A, D, E, and F may also be 

used with DLMS 527R Disposition Services Turn-In Receipt 

Acknowledgement (TRA) transaction when acknowledging 

receipt of a discrepant/deficient shipment. TRA is DLMS 

527R with Transaction Type Code CJ. TRA is a DLMS 

enhancement with no legacy DIC. Refer to ADC 1111.

Select codes may be used with intra-Army Receipt (Other 

than Procurement Instrument Source) transactions (legacy 

DIC D6_/DLMS 527R with Transaction Type Code D4) 

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

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

Instrument Source Receipts 

(DIC D6_).

DLMS 527R 

SEGMENT/QUALIFIER

LQ Segment, LQ01 Data Element ID 1270 Qualifier

“EI – Discrepancy Indicator Code”

CODES USED WITH MRA and select codes (A, D, E, and F) used with TRA:

CODE DEFINITION

A SDR being submitted. (Excludes shortage and partial or total nonreceipt.)
Enclosure 3, ADC 1114 

Page 2

CODES USED WITH MRA and select codes (A, D, E, and F) used with TRA:

CODE DEFINITION

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. 

When used with MRA transaction, the quantity not received is entered in legacy 

DIC DRA/DRB record positions 25-29 or in DLMS 527R MRA 2/RCD02/040. 

When used with TRA transaction, the quantity received is entered in DLMS 527R 

2/RCD02/040. 

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 Materiel still in transit.

HI-L Reserved for future DoD assignment.

M-T See below

U Reserved for future DoD assignment.

V MRA is based on a systemic virtual receipt. MRA is generated from virtual receipt 

transaction which the Navy industrial site (Navy Shipyard/Fleet Readiness Center) 

created from a Supply Status transaction (DLMS 870S) with Status Code ‘PD’. 

Authorized for Navy and DLA use in DLMS 527R MRA under Supply, Storage 

and Distribution/Inventory Management and Stock Positioning (SS&D/IMSP). 

Refer to ADC 372.

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.

 1 Refer to ADC 474. As required by DODM 4140.01, 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.
Enclosure 3, ADC 1114 

Page 3

CODES USED WITH MRA and select codes (A, D, E, and F) used with TRA:

CODE DEFINITION

Y-Z Reserved for future DoD assignment.

CODES USED WITH INTRA-ARMY RECEIPT (OTHER THAN PROCUREMENT 

INSTRUMENT SOURCE) TRANSACTIONS (DLMS 527R Receipt/legacy 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)
Enclosure 4, ADC 1114

Page 1

ENCLOSURE 4 TO ADC 1114

Revise DLM 4000.25-2, Appendix 5.1, Materiel Receipt Acknowledgement Report Business 

Rules, as follows (changes identified by bold, red, italics). Comparable changes will be made 

to DLM 4000.25, DLMS Manual, Volume 2. Appendix 12 and DLM 4000.25-4, DAAS Manual 

Appendix 7:

AP5.1. APPENDIX 5.1

MATERIEL RECEIPT ACKNOWLEDGMENT REPORT 

BUSINESS RULES

AP5.1.1. Materiel Receipt Acknowledgement Report – Business Rules

AP5.1.2. Background 

AP5.1.2.1. MRA reports show shipments and the percentage of 

shipments for which the DAAS receives and does not receive the associated MRA 

transactions. Qualifying Shipments included in the report are determined by the 

date released to carrier (recorded at Transaction Services) plus 6025 calendar days 

to accommodate the 4517calendar days MRA reporting period and the 1510

calendar days MRA follow-up response timeframes (if CONUS); or plus 43

calendar days to accommodate the 34 calendar days MRA reporting period 

and the 10 calendar days MRA follow-up response timeframe (if OCONUS –

Transportation Category 1 or 2); or plus 12090 calendar days to accommodate the 

10581 calendar days MRA reporting period and the 1510 calendar days MRA followup response timeframe (if OCONUS – Transportation Category 3).1

 Security 

assistance program requisitions are not captured for inclusion in LMARS or MRA 

Reports based on the Security Cooperation Implementing Agency code in the first 

position of the document number.

AP5.1.2.2. The MRA report is created at the end of each month to 

reflect the MRA transactions as received/not received in the preceding month. 

Receipt of an MRA citing Discrepancy Code B or F updates the Logistics 

Metrics Analysis Reporting System (LMARS) reports to reflect the current 

status of MRA transactions received. The MRA Reports are created monthly 

and reflect the MRA data at the end of the month and will not be adjusted 

retroactively when an MRA is submitted following receipt of materiel after an 

MRA citing Discrepancy Indicator Code B or F is received.

 1 Per DLM 4000.25-2, Chapter 6, the reporting period is defined as 4517 calendar days for Conus; and 34

calendar days for OCONUS Transportation Category 1 and 2 shipments; and10581 calendar days 

for OCONUS Transportation Category 3 shipments. The follow-up response timeframe for both is 1510

days.