DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

July 12, 2018

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

1281, Align Materiel Receipt Acknowledgement (MRA) Procedures in DLM 

4000.25, Volume 2 with DLM 4000.25-2 (Supply/MILSTRAP)

The attached administrative change to Defense Logistics Manual (DLM) 4000.25, Defense 

Logistics Management System and DLM 4000.25, Military Standard Transaction Reporting and 

Accountability Procedures (MILSTRAP) is approved for publication. This change 

administratively aligns the MRA procedures in DLM 4000.25 (DLMS) and DLM 4000.25-2

(MILSTRAP). This change will be published in the next Formal Change.

Addressees may direct questions to, Mr. Rafael Gonzalez, DOD MILSTRAP Administrator, 

and Mr. Paul Jensen, EBSO contractor support, e-mail: DLMSSupply@dla.mil. All others must 

contact their Component designated Supply PRC representative available at: 

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

HEIDI M. DAVEREDE

Director

Enterprise Business Standards Office

Attachment

As stated

cc: 

ODASD (SCI)
Attachment, ADC 1281

Page 1

ATTACHMENT TO ADC 1281

Align Materiel Receipt Acknowledgement (MRA) Procedures in DLM 

4000.25, Volume 2 with DLM 4000.25-2 (Supply)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Mr. Rafael

Gonzalez, Enterprise Business Standards Office (EBSO), and Mr. Paul Jensen, EBSO contractor

support, e-mail: DLMSSupply@dla.mil

2. FUNCTIONAL AREA: Supply

3. REFERENCES:

a. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2 Supply

Standards and Procedures, Chapter 10

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

Procedures (MILSTRAP), Chapter 6 

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: This change administratively aligns DLM 4000.25,

Volume 2, Chapter 10, Materiel Receipt Acknowledgement (Reference 3.a.) with its companion 

chapter in DLM 4000.25-2, MILSTRAP, Chapter 6, Materiel Receipt Acknowledgement

(Reference 3.b.). This change will mark MILSTRAP MRA Chapter 6 and mark the associated 

appendices as “Reserved” with pointers to DLM 4000.25, DLMS Manual. There are no 

changes to the MRA procedures. 

b. Background:

(1) This change is one in series of DLMS changes to DLMS Volume 2 and

MILSTRAP. This change will update DLM 4000.25, DLMS, Volume 2, Chapter 10, MRA 

procedures to align with the companion procedures in DLM 4000.25-2, MILSTRAP, Chapter 6, 

MRA procedures. The MILSTRAP Chapter will be marked as “Reserved”. When all 

MILSTRAP Chapters are marked as “Reserved” the MILSTRAP Manual will be cancelled and 

the DLM 4000.25, DLMS Manual (primarily Volume 2) will serve as the single guidance for the 

Military Standard Transaction Reporting and Accountability Procedures, business rules, data 

standards, and transaction formats. 

(2) DLM 4000.25-2, Chapter 6 defines procedures associated with MRA using

legacy MILSTRAP 80 record position formats. DLM 4000.25, Volume 2, Chapter 10 defines 

DLMS enhanced procedures for MRA using DLMS formats (X12 Electronic Data Interchange 

(EDI) and eXtensible Markup Language (XML)).

c. Approved Change in Detail: Update DLM 4000.25, Volume 2, Chapter 10, to align

MRA procedures between the two manuals. There are no changes to the overall MRA 

procedures. There are several areas where the DLMS chapter did not contain relevant 

information contained in the MILSTRAP chapter and several areas where the text was clarified
Attachment, ADC 1281

Page 2

to remove a disconnect between legacy procedures and DLMS procedures. These updates are 

done solely in the DLMS, Volume 2, Chapter 10. Two specific areas are: 

(1) Clarify the terminology used in shipment status in legacy and DLMS 

procedures for ‘date shipped’ and ‘release date’ (there is an existing disconnect in the shipment 

status between the legacy transaction AS_, and the DLMS 856S transaction). The term "release 

date" is used specifically on the materiel release confirmation. DLMS Chapter 10 is being 

updated to reflect “date shipped (date released to carrier)" when it is related to the Shipment 

Status Transaction (legacy AS_ or DLMS 856S.

(2) MILSTRAP Chapter 6 contained a section on MRA syntax errors in a mixed 

DLMS/legacy transaction environment. This section is added to the DLMS chapter to retain the 

procedures in a mixed environment when some Component systems are not yet DLMS 

compliant.

d. Revisions to DLM 4000.25 Manuals:

(1) Update Chapter 10 to DLM 4000.25, Volume 2 to align with DLM 4000.25-

2, Chapter 6. See Enclosure 1. 

(2) Update the Table of Contents for DLM 4000.25, to reflect renumbered 

content. See Enclosure 2.

(3) Update the Table of Contents for of DLM 4000.25-2, MILSTRAP to mark 

the following chapters and appendices as “Reserved”. See Enclosure 3 

(a) Chapter 6, Material Receipt Acknowledgement

(b) Appendix 4, Time Limits – Index

(c) Appendix 4.1 – Materiel Receipt Acknowledgement Time Limits

(d) Appendix 5 – Business Rules 

(e) Appendix 5.1 Materiel Receipt Acknowledgement Business Rules

(f) Figure AP5.1F1 – MRA Report Business Rules

(4) Administrative update to DLMS 527R MRA Implementation Convention 

(IC) to update terminology from “inquiry” to follow-up”, associated with Follow-up for 

Delinquent MRA transaction. See Enclosure 3.

e. Proposed Transaction Flow: This DLMS change does not affect existing MRA 

transaction flows.

f. Alternatives: None.

5. REASON FOR CHANGE: Align the DLMS and MILSTRAP Manuals content so that 

DLM 4000.25-2, MILSTRAP Manual can be cancelled. The DLM 4000.25, DLMS, volume 2 

will serve as the single source for MRA procedures.
Attachment, ADC 1281

Page 3

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Furthers goal of providing a single source for documenting MRA 

procedures. This change removes the requirement to update the DLM 4000.25-2, MILSTRAP, 

MRA Chapter, and eliminates the need to maintain two separate manuals with redundant 

information.

b. Disadvantages: None

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: This change does not 

require additional system changes, beyond those already documented in previously published 

Approved DLMS Changes.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: There is no cost/impact to systems that have 

implemented the required MRA procedures.

9. IMPACT:

a. New DLMS Data Elements: There are no new DLMS data elements required by this 

alignment.

b. Changes to DLMS Data Elements: There are no changes to DLMS data elements 

required by this alignment.

c. Automated Information Systems (AIS): No impact beyond those already 

documented in published Approved DLMS Changes

d. Defense Automatic Addressing System (DAAS): No impact beyond those already 

documented in published Approved DLMS Changes.

e. Non-DLM 4000.25 Series Publications: Components should update their local 

procedures to ensure consistency with MRA procedures documented in DLM 4000.25.

Enclosures
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 1

ENCLOSURE 1 TO ADC 1281

A. Update Chapter 10 to DLM 4000.25, DLMS Manual, Volume 2. Moved and removed text 

is identified by double strikethroughs. Updated and relocated text is annotated with red, 

bold, italics. 

C10. CHAPTER 10

MATERIEL RECEIPT ACKNOWLEDGEMENT

C10.1. GENERALPURPOSE

C10.1.1. Purpose. This chapter provides the processprocedures for a DoD automated, 

closed-loop system to provide accountability and monitor receipt of shipments of DoD and 

General Services Administration (GSA) wholesale stocks and DLA Disposition Services stocks 

issued from on-hand assets or procured for direct vendor delivery (DVD). These procedures 

interface with logistics response time (LRT) for measuring receipt take-up time by 

requisitioners and with Chapter 5, for providing 100 percent shipment status on stock issues, 

including DVDs.

C10.1.2. These procedures provide for the control of due-in records below the wholesale 

level and the interface among the transportation, quality, supply, and financial 

operations/systems below the wholesale level and between the supply and purchasing 

operations/systems at the wholesale level to provide proper control over in transit assets and 

document receipt in the payment files.

C10.1.13.1. MRA Business Rules. Appendix 12 identifies the detailed business rules for 

generating the MRA Report. Appendix 12 also includes an MRA Decision Tree diagram to 

provide graphic representation of the MRA business rules to capture shipments out of 

wholesale assets that qualify for MRA Reporting.

C10.1.1.2. MRA Decision Tree. Appendix 12 also includes an MRA Decision Tree

diagram to provide graphic representation of the MRA business rules to capture shipments out of 

wholesale assets that qualify for MRA Reporting.

C10.1.24 Transactions. This chapter addresses the procedures applicable to the following 

Accredited Standards Committee (ASC) X12 transactions with their functions identified by their 

beginning segment (1/BR02/020) transaction type code. Other DLMS formats, such as XML, 

are available from the DLA Logistics Management Standards WebsiteThe DLMS 

implementation conventions (IC) are available on the Electronic Business Standards Office 

Website

www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997. The 

corresponding MILSTRAP legacy 80 record position transaction functionality is identified for 

information purposes in a mixed DLSS/DLMS environment.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 2

C10.1.24.1. Materiel Receipt Acknowledgement (MRA) Transaction is DLMS 527R, 

identified by the ASC X12 with beginning segment (1BR02/020) Transaction Type Code TH –

Receipt Acknowledgement Advice. This transaction provides MILSTRAP legacy DIC DRA 

functionality.

C10.1.24.2. MRA Response to Inquiry Follow-up Transaction is DLMS 527R, 

identified by with Transaction Type Code TH–Receipt Acknowledgement Advice, used in 

conjunction with 1/BR06/20 Action Code V–Respond. This transaction provides MILSTRAP 

legacy DIC DRB functionality.

C10.1.24.3. Follow-up for Delinquent MRA Inquiry Transaction is DLMS 527R, 

identified by with Transaction Type Code TG – Receipt Acknowledgement Inquiry. This 

transaction provides MILSTRAP legacy DIC DRF functionality.

C10.21.3. APPLICABILITY.

C10.21.3.1. These procedures apply to shipments of DoD wholesale stocks and DLA 

Disposition Services stocks and, in part, to shipments of GSA wholesale stocks--whether pushed 

or pulled, delivered or picked up, issued from on hand assets or procured for DVD from 

commercial sources. 

C10.2.2. These procedures therefore, apply to:

C10.2.2.1.3.1.1. All DoD integrated materiel managers (IMM) wholesale 

inventory control points (ICP) and the DLA Disposition Services (for the purposes of MRA, 

DLA Disposition Services is the DoD managerICP for shipments from reutilization and 

marketing Disposition Services).

C10.2.21.3.1.2. Recipients of DoD and GSA wholesale stocks and DLA 

Disposition Services stocks–including DoD intermediate/retail level and end-use activities; 

contractors thatwhich receive Government furnished material GFM, as and defined under 

DoDM 4140.01, “DoD Supply Chain Materiel Management Procedures,” February 10, 2014; 

DoD ICPs thatwhich requisition materiel from GSA, DLA Disposition Services, or other DoD 

inventory control points (ICPs); and DoD maintenance facilities that which receive items for 

maintenance when the maintenance activity accountable officer assumes property accountability 

for the inducted items--hereafter called reporting activities.

C10.2.2.3. Implementation of the materiel receipt acknowledgment concept is 

optional for intra-Component shipments of retail stock. However, DoD Components which 

choose to implement the concept for such shipments will prescribe use of these procedures.

C10.1.3.2. GSA will not use the MRA to monitor materiel receipt but will use the 

data to interface with the discrepancy reporting process. Therefore, GSA will not follow-up to 

reporting activities to request an MRA.

Staffing Note: Moved to C10.5.6.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 3

C10.1.3.3. The DoD Components may prescribe additional internal follow-up 

requirements to those identified in this chapter.

Staffing Note: Moved to C10.5.7.

C10.31.4. Exclusions.EXCLUSIONS.

1

 The following are excluded from MRA procedures: 

These procedures are not applicable to the following:

C10.31.4.1. Commodities excluded from requisitioning, except that receipt of 

requisitioned forms and publications will be acknowledged.

C10.31.4.2. Shipments to foreign military sales and grant aid customers except when 

the shipment concerns an unconfirmed materiel release order (MRO) as described in Chapter 4 

(Processing Follow-Ups). FMS documents beginning with B, D, I, P, K and T .

C10.31.4.3. Inter-Component lateral redistributions of retail stock not directed by the 

wholesale ICPIMM.

2

C10.31.4.4. Shipments to state, civil, or federal agency activities. Special Program 

DoDAACs are identified by numeric character in the first position followed by an alpha 

character in the second position. These identify entities that are neither DoD or other Federal 

entities and that are associated with a special program. Among other purposes, special programs 

include programs authorized by Congress for state and local entities to purchase materiel from 

Federal sources. The existing DLA Transaction ServicesDefense Automatic Addressing System 

(DAAS) logic for extracting the LMARS database includes the exclusion orof Special Program 

DoDAACs (ADC 1088).

C10.31.4.5. Receipts into DoD wholesale stock controlled under Chapter 13, 

including relocations/shipments to contractors, commercial or industrial activities which are 

receipt reported to the owning ICPowner, when the owing ICP also issued the materiel. 

 1 Known MRA gaps include shipments associated with DLA Industrial Prime Vendor (IPV), and DLA Tailored 

Vendor Relationships (TVR) such as Medical Prime Vendor; Subsistence Prime Vendor; Maintenance Repair 

and Operations program; and Kentucky Logistics Operation Center (KyLOC). The MRA process requires a 

MILSTRIP Shipment Status transaction; there is no shipment status in these processes. These processes are not 

excluded from MRA (except Fresh fruits and vegetables (FF&V)), and are identified as known process gaps that 

DLA is working to close. Another possible MRA gap exists for immediate issue scenarios (e.g., bearer walkthrough or “over the counter” issues) where shipment status/materiel release confirmation is provided and an 

MRA would typically be expected. DLA will submit a proposed DLMS change to document this as a valid 

MRA exclusion. (ADC 1088) 2 This is not a true “exclusion” from MRA because the MRA is only required for release of wholesale assets. When 

DAAS gets the passing order that has a RIC-TO of a non-wholesale ICP, they will flag the document number as 

not eligible for LMARS/MRA, but still be available for WEBVLIPS as history. Any subsequent transactions 

that come in under that document number (regardless of data content and indication of a wholesale ICP) 

automatically gets that flag. This is similar to what DAAS does for the requisition alert process. The one 

underlying assumption to this solution is that the passing order (DIC A3_) will be present so that the flag can be 

set at the document number level. This is a safe assumption, since ADC 1062 states that GCSS-A will not 

release the requisition image until they receive the passing order routed by DAAS. Note the DAAS check on the 

shipment status is just the presence of a shipment status for the document number that clears the first part of the 

MRA decision Tree. DLA Transaction ServicesDAAS feels this will eliminate a concern with LMARS picking 

up the transaction as a byproduct when the bill comes out of the wholesale ICP system (LMP) after the post-post 

issue is passed to that system (For Army GCSS-A to LMP). (ADC 1088)
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 4

However, when ICPsIMMs requisition materiel from another ICPIMM or the DLA Disposition 

Services, and the receipt is reported under Chapter 13, the requisitioning ICPIMM will 

acknowledge the receipt (ADC 1087).

C10.31.4.6. Shipment status (DLMS 870S/Legacy AS3) with Distribution Code 9 

(DLA Distribution Services). Shipments to dDisposition sServices that are covered under the 

procedures for in-transit control of shipments to DLA Disposition Services Field Offices.

C10.31.4.7. Shipments of fresh fruit and vegetables (FF&V). FF&V transactions are 

received by DLA Transaction ServicesDAAS in a monthly data feed from DLA Troop Support 

and do not have shipment data.

C10.31.4.8. Shipments to Army/Air Force Exchange Service (DoD activity address 

codes (DoDAAC) HX1_, HX2_, HX3_ , and HX4 _).

C10.31.4.9. DoDAAC indicating activity is GSA or FEDSTRIP.

C10.31.4.10. Exclude intra-Component shipments when the issuing wholesale ICP 

does not generate a Follow-up for Delinquent MRA transaction within the required delinquent 

MRA Follow-up time limit. The rationale is that if the issuing wholesale ICP business process 

requires that the intra-Component reporting activity provide a Receipt transaction back to the 

issuing wholesale ICP, then it falls under the MRA exclusions and the issuing ICP would not 

generate a Follow-up for Delinquent MRA transaction. For the purpose of this exclusion logic, 

DLA Transaction ServicesDAAS will use the MRA Follow-up timeframe plus one day. Under 

existing MRA Report logic, lookup will be done at the end of the month.” (ADC 1087).

C10.4 COMMUNICATIONS

C10.4.1.2.5.5. DAAS MRA Processing. Reporting activities will direct MRAs to the 

managing ICP using guidance in C10.4.2. If operating under MILSTRAP legacy 

transactions, refer to the instructions in DLMS Volume 2, Appendix 10 for the legacy 

DRA/DRB transactions. DAAS will pass the MRA to the designated ICPIMM the reporting 

activity indicates in the transaction, and provide images to other designated activities based 

upon DoD Component rules. 

C10.4.2 Reporting activities will direct the MRA to the managing ICP using one of the 

following (listed in order of preference):

C10.4.2.5.5.1. The organization that directed the materiel shipment as shown 

on DLMS 856S, Shipment Status.

C10.4.2.5.5.2. The last known source of supply that authorized follow-up 

action as shown on DLMS 870S, Supply Status. 

C10.4.2.5.5.3. The source of supply to which the DLMS 511R, Requisition, 

was submitted.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 5

C10.4.3. ICPs will send all MRA follow-ups to the DAAS for transmission. 

The DAAS will route MRA follow-ups for U.S. forces to the “ship-to” activity identified in the 

856S Shipment Status. The DAAS will route MRA follow-ups for security assistance 

requisitions to the applicable Service International Logistics Control Office (ILCO) based 

upon the Service Code in the Document Number and distribution code 

C10.52. RESPONSIBILITIES

C10.5.1. Reporting activities and ICPs will meet the time limits stated throughout this 

chapter and summarized in Table C10.T1, MRA Submission Timeframe, and Table C10.T2, 

MRA Follow-up Timeframe for ICPs and Disposition Services. 

C10.5.2.1. Reporting Activity. Reporting activities excluding International Logistics 

Control Offices (ILCOs) will:

C10.5.2.1.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.

C10.5.2.1.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 MRA prescribed 

timeframes in Table C10.T1. 

C10.5.2.1.3. Post receipts from wholesale stock to a stock record/property, or 

equivalent, account and acknowledge materiel receipt under these procedures.

C10.5.2.1.4. Post receipts to the appropriate account. Whenever materiel is taken 

into U.S. Government custody at final destination, whether it has been accepted or not, ensure 

the receipt is posted to the stock record/property, or equivalent, account. Establish any needed 

interface among the transportation, quality, and supply operations/processes to meet this 

requirement.

C10.5.2.1.5. Monitor due-in records and report nonreceipt under these procedures 

when materiel is not received within the prescribed timeframes in Table C10.T1. DLMS 

requires that 100 percent shipment status be sent to all reporting activities so they can meet this 

requirement.

C10.5.2.1.6. Coordinate with the financial operation/function before clearing a duein record by any action other than materiel receipt. Maintain an auditable record of all due-in 

records so cleared.

C10.5.2.1.7. Establish an interface with financial accounting operations/processes to 

maintain proper financial accounting control for in-transit assets, as prescribed by DoD 7000.14-

R, “DoD Financial Management Regulations”.

C10.5.32.2. ILCO History Screening. ILCOs reporting activities will screen history 

records for valid shipment status or coordinate with freight forwarders/customers to determine 
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 6

shipment status/receipt data, for unconfirmed MROs and send an MRA Advice Transaction 

within the prescribed timeframes in Table C10.T1.

C10.5.42.3. Integrated Materiel Manager. IMMs ICPs will:

C10.5.42.3.1. Have a closed-loop system to monitor materiel receipt on all shipments 

of wholesale stock to DoD activities.

C10.5.42.3.2. Control MRA data based on quantity within document number. When 

the MRA does not match a shipped record, use the data only for quality control/management 

evaluation purposes. Do not reject MRAs to the submitter.

C10.5.42.3.3. Keep an accessible record of requisitions, by document number and 

suffix code shipped, until materiel receipt is confirmed, nonreceipt is reported for the quantity 

shipped, or failure to acknowledge is included in management evaluation reports.

C10.5.42.3.4. Establish an interface between the supply and disbursing 

functions/operations to provide receipt acknowledgment data for all DVDs for documentation of 

payment files.

C10.5.42.3.5. Consider MRA data in the supply discrepancy report (SDR) validation 

process.

C10.5.5.2.4. DoD Components. The DoD Components:

C10.5.5.2.4.1. Will establish the internal interface among the logistics, financial, and 

contracting operations/systems necessary to accomplish the MRA requirements of this chapter. 

When operations are geographically removed from each other, DoD Components may 

prescribe use of intra-DoD Component transactions to accomplish the required interface.

C10.5.5.2.4.2. May, for intra-DoD Component shipments, elect to have their 

shipping activity or container consolidation and containerization point create an MRA and send 

it with the shipment for completion and submission by the reporting activity.

C10.5.5.2.4.3. May prescribe, where appropriate, that intermediate levels of supply 

(i.e., organizations that are not the ultimate materiel recipient but maintain due-in records for 

referred user requisitions) post receipts to their due-in records and acknowledge materiel receipt 

for the user.

C10.5.5.2.4.4. May record MRA data in requisition history and use to close 

unconfirmed MROs.

C10.5.61.3.2. GSA will not use the MRA to monitor materiel receipt but will use 

the data to interface with the discrepancy reporting process. Therefore, GSA will not followup to reporting activities to request an MRA.

C10.5.71.3.3. The DoD Components may prescribe additional internal follow-up 

requirements to those identified in this chapter. 
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 7

C10.62.5. MRA Submission PREPARING AND SENDING MATERIAL RECEIPT 

ACKNOWLEDGEMENT 

C10.6.2.5.1. Reporting Time Limits. Reporting activities will meet the time limits 

identified in this chapter. These requirements and timeframes are independent from prescribed 

shipment tracing and discrepancy reporting requirements and timeframes to which the receiving 

facility must also adhere. MRA reporting timeframes are summarized below:

Table C10.T1. Materiel Receipt Acknowledgement Submission Time Limits for Reporting 

Activities

ACTION TIME LIMIT3

U.S. Forces send MRA * 5 Business days from date materiel received and: 

 12 calendar days from the DLMS 856S date shipped (date 

released to carrier) field entry (CONUS destination) for 

nonreceipt;

 29 calendar days from the DLMS 856S date shipped (date 

released to carrier) field entry (OCONUS destination) for 

nonreceipt for Transportation Category 1 and 2;

or

 76 calendar days from the DLMS 856S date shipped (date 

released to carrier) field filed entry (OCONUS 

destination) for nonreceipt for Transportation Category 3.

ILCOs Send MRA *120 calendar days from the DS 856S (Pseudo Shipment Status 

for Unconfirmed Materiel Release Orders) date shipped (date 

released to carrier) field entry for security assistance shipments.

Send MRA in Reply to 

Follow-up

*10 calendar days from transaction preparation date in 

the MRA Follow-up Inquiry.

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

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

C10.6.2.5.2. Submission of MRA Advice Transaction. 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:

C10.2.5.3. U.S. Forces Reporting. U.S. Forces reporting activities will send an 

MRA:4

C10.6.2.5.3.1. Within 5 business days from date of materiel receipt is received.

 3 Refer to ADC 1114.

4 Ibid.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 8

C10.6.2.5.3.2. For nonreceipt of materiel with a CONUS destination, within 12 

calendar days from date shipped (date released to carrier) cited in DLMS 856S, Shipment 

Status.

C10.6.2.5.3.3. 29 calendar days from the date shipped (date released to 

carrier)date when a Transportation Category 1 or 2 shipment to an OCONUS activity has not 

been received.

C10.6.2.5.3.4. For nonreceipt of materiel (Transportation Category 3) with an 

OCONUS destination, within 76 calendar days from the date shipped (date released to carrier) 

cited in DLMS 856S.

C10.6.32.5.4. SA Shipments. ILCOs in receipt of DLMS 856S pseudo shipment status 

will screen history records for valid shipment status. If valid shipment status is not available, 

ILCOs may coordinate with freight forwarders/customers to determine shipment status/receipt 

data. Submit an MRA to reflect the show shipment status, or receipt data, or nonreceipt within 

120 calendar days from the pseudo shipment status release date.

C10.2.5.5. DAAS MRA Processing. DAAS will pass the MRA to the designated 

IMM the reporting activity indicates in the transaction, and provide images to other designated 

activities based upon the DoD Component rules. Reporting activities will direct the MRA to one 

of the following (listed in order of preference):

C10.2.5.5.1. The organization that directed the materiel shipment as shown on 

DLMS 856S.

C10.2.5.5.2. The last known source of supply to that authorized follow-up 

action will be directed as shown on DLMS 870S, Supply Status. 

C10.2.5.5.3. The source of supply to which the DLMS 511R, Requisition, was 

submitted.

Staffing Note: Moved to C10.4 Communications.

C10.6.4.5.6. MRA For Materiel Provided to Contractors as Government Furnished 

Materiel and for MRA Associated with Contractor Furnished Materiel Obtained from 

Government Supply Sources. This business process is applicable when contractors are 

authorized to receive specific items and quantities of government furnished materiel (GFM) or 

contractor furnished materiel (CFM) (also known as contractor acquired property (CAP)) from 

Government sources of supply. Materiel may be issued to the contractor based upon a contract 

schedule/Bill of Material (BOM) or issued in response to a requisition made by the contractor or 

a responsible Government representative. Under DLMS, MRA of GFM/CFM requires 

identification of the DoD contract number and call/order number, when applicable, which 

authorized the provision of GFM/CFM to establish accountability to the authorizing DoD 

contract. This contract number is required in addition to the controlling document number for 

the MRA transaction.

C10.6.5.5.7. MRA for Tailored Vendor Relationship. DLA, in conjunction with the DoD 

Components and vendors, has implemented tailored vendor relationship (TVR). TVR is a 
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 9

business process where there is a direct relationship between the customer and the vendor. 

Under TVR, customers place orders directly with the Prime Vendor, outside the routine supply 

requisitioning process/systems, using various communication channels such as EDI, phone, fax, 

email, or via the prime vendor's ordering system. DLA EBS receives copies of transactions in 

order to maintain line item accountability. MRA of TVR shipments require use of the contract 

number, call, and line item numbers to uniquely identify lines. This data is necessary because 

TVR orders can have multiple lines for the same document number and suffix code. DLA 

receives MRAs for TVR from, Defense Medical Logistics Standard Support (DMLSS), Theater 

Enterprise-Wide Logistics System (TEWLS), EMALL, or customer systems.

C10.6.6.6. Acknowledgement of Split or Partial Shipments. When a shipped line item 

(requisition document number and suffix code) is consigned as a split or partial shipment, 

sendsubmit an MRA, for the shipment segments as they are received. The split or partial 

shipment codes are part of the transportation control number (TCN) structure in accordance with 

DTR 4500.9-R, DoD Transportation Regulation”. Accordingly, reporting activities will include 

the TCN in the MRA transaction when it is available. If the total quantity for the shipped line 

item is not received by the due-in date, report the missing quantity, citing Discrepancy Indicator 

Code F, in accordance with the guidance in the MRA transaction.

C10.6.7.7. Acknowledgement of a Discrepant/Deficient Shipment. To acknowledge 

receipt of a discrepant/deficient shipment, submit an MRA, except as noted below, with the 

appropriate discrepancy indicator code. With the exception of the receipt of multiple stock 

numbers, use a single MRA transaction to acknowledge the receipt showing both non-discrepant 

and discrepant quantities.5 Note that MRA requirements and timeframes are independent from 

prescribed shipment tracing and discrepancy/deficiency reporting requirements and timeframes 

to which the receiving facility must also adhere.

C10.6.7.2.7.1. If the document number of a receipt cannot be identified, post the 

receipt using a local document number. Do not submit an MRA.

C10.6.7.7.2. If stock number/part number cannot be identified, do not include the 

stock/part number in the MRA and enter Discrepancy Indicator Code A.

C10.6.72.7.3. For total or partial nonreceipt, (Discrepancy Indicator Code F)

C10.6.7.3.1. Enter the quantity not received and Discrepancy Indicator Code F. 

C10.6.7.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 C10.6.8.2.7.1.6

 C10.6.7.7.4. Except for shortage and partial or total nonreceipt, covered in 

addressed aboveC10.6.7.3, enter Discrepancy Indicator Code X in the MRA if the discrepancy 

does not meet discrepancy reporting criteria.

 5 This this is an enhancement that the Components never implemented as part of the looping structure capability. 6 Refer to ADC 1114.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 10

C10.6.7.2.7.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.When posting a receipt using more than one transaction because the 

discrepancy results from the receipt of multiple stock numbers, send an MRA for each 

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

C10.6.7.2.7.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 C10.6.12.7.16.1.

C10.6.7.2.7.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.7

C10.73. INQUIRY FOLLOW-UPS FOR DELINQUENT MATERIEL RECEIPT 

ACKNOWLEDGEMENT

C10.73.1. Timeframe for MRA Inquiry. When materiel shipment is confirmed or when 

the requisition involves an unconfirmed MRO as described in Chapter 4, the ICP IMM will 

monitor for receipt of MRA(s). For U.S. Forces’ shipments to CONUS activities, ICP IMMs

must receive MRA for the total quantity shipped within 12 calendar days from the date 

released to carrier shipped cited in the DLMS 945A, Materiel Release Advice, or DLMS 

856S. For U.S. Forces shipments to OCONUS activities, ICP IMMs must receive MRA within 

29 calendar days from the date released to carrier for Transportation Category 1 and 2, 76 

calendar days from the date released to carrier for Transportation Category 3, or within 135 

calendar days from the DLMS 856S shipment status release date for security assistance 

requisitions. Otherwise, the ICP IMM will send an MRA InquiryFollow-up Transaction for 

the delinquent MRA to (See Table C10.T2):

C10.73.1.1. The organization that the materiel was shipped to, for U.S. Forces.

C10.73.1.2. The applicable ILCO, for SA requisitions.

C10.73.1.3. 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. 

C10.73.1.4. The follow-up time limits for a delinquent MRA are 17 calendar days 

from the date shipped (date released to carrier) field entry in the MRC or DLMS 856S Pseudo 

Shipment Status for CONUS, 34 calendar days for OCONUS destinations with Transportation 

 7 Ibid.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 11

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

Category 3. (See Table C10.T2).

C10.73.1.53. Summary of MRA Inquiry Follow-Up Time Limits. Reporting 

activities will meet the time limits identified in this chapter. These requirements and 

timeframes are independent from prescribed shipment tracing and discrepancy reporting 

requirements and timeframes to which the receiving facility must also adhere. MRA inquiry

follow-up time limits are summarized in Table C10.T2.

Table C10.T2. Materiel Receipt Acknowledgement InquiryFollow-Up Time Limits for ICPs and 

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 LIMIT8

Follow-Up for Delinquent 

MRA

 17 calendar days from the date shipped (date released to 

carrier) field entry in the Materiel Release Confirmation 

(MRC) or Pseudo Shipment Status (DLMS 856S/MILSTRIP 

legacy DIC ASH) for U.S. Forces shipments (CONUS 

destination).

 34 calendar days from the date shipped (date released to 

carrier) field entry in the MRC or DLMS 856S Pseudo 

Shipment Status for U.S. Forces shipments (OCONUS 

destination) for Transportation Category 1 and 2.

 81 calendar days from the date shipped (date released to 

carrier)field entry in the MRC or Pseudo Shipment Status 

(for U.S. Forces shipments (OCONUS destination) for 

Transportation Category 3.

 135 calendar days from the date shipped (date released to 

carrier) field entry in the Pseudo Shipment Status for 

security assistance shipments.

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

C10.3.2. Delinquent MRA Inquiry Response 

C10.7.23.2.1. To answer the follow-up respond to an inquiry on a delinquent MRA, the 

reporting activity will prepare a MRA following paragraph C10.62.5., above. Send the MRA 

to the ICP originator of the inquiry within 10 calendar days from the transaction preparation 

date cited in the inquiryfollow-up.

C10.7.3.2.2. 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 MRA Follow-up Transaction containing Discrepancy Indicator Code G. 

 8 Refer to ADC 1114.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 12

This will signal the ICP to keep the record open and continue to monitor for receipt of 

MRA(s), and send another MRA Inquiry Transaction after another 45 calendar days have 

elapsed (which may be responded to with an additional MRA Response to Inquiry Transaction

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 MRA 

Response to Inquiry Transaction with Discrepancy Indicator Code G. The Navy ship 

reporting activity will send an MRA, using DLMS 527R MRA Response to Inquiry 

Transaction, 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 MRA Response to Inquiry Transaction with Discrepancy Indicator Code G, the ICP will 

include the delinquency information in the management evaluation report (C10.2.10). Also, if 

the requisition involves an unconfirmed MRO (see Chapter 4, (Processing Follow-Ups)), then 

the ICP will resolve the record as described in Chapter 4 for Force Closed Materiel Release 

Confirmation).

C10.7.43.2.3. When Component research into a Follow-up For Delinquent MRA 

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

Response to Inquiry transaction 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 Follow-up For Delinquent MRA transaction after another 45 

calendar days have elapsed.9

 If a reply is not received within 45 calendar days from the sixth 

MRA Response to Inquiry transaction 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.10

C10.7.53.2.4. Except as noted in C10.7.3.2.2., if a reply is not received within 30 

calendar days from the MRA inquiry preparation date, the ICP IMM will include the 

delinquency information in the MRA Management Information Report. Also, if the 

requisition involves an unconfirmed MRO, then the ICP IMM will resolve the record as 

described in the procedures in Chapter 4 for (Force-Closed Materiel Release Confirmations).

C10.2.8. Correcting or Canceling a MRACORRECTING OR CANCELING MATERIAL 

RECEIPT ACKNOWLEDGEMENT

C10.8.1 MRA Errors

C10.2.8.1. Identification of Erroneous Information. Activities that which 

acknowledge a materiel receipt in error will 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, “Report of Discrepancy”) or in the ASC X12 

note/special instruction segment (2/NTE/2400) of the DLMS 842A/W, SDR Follow-up, 

 9 Refer to ADC 1114.

10 Ibid.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 13

Correction, Cancellation, & Reconsideration Request note/special instruction segment. MRAs 

with an invalid quantity field or blank unit of issue will be processed and corrected as 

addressed in C10.8.1.2.

C10.8.1.2. Syntax Errors in Mixed DLMS/DLSS Environment. MRAs submitted 

in legacy DIC DRA/DRB format, with an invalid quantity or blank unit of issue, cannot be 

processed by DLMS trading partners due to syntax errors. Accordingly, when DAAS must 

convert DIC DRA/DRB to a DLMS 527R MRA transaction for a DLMS trading partner, and 

the DRA/DRB contained an invalid quantity or blank unit of issue, DAAS will reject the 

transaction using narrative message rejects as follows:

C10.8.1.2.1. Invalid Quantity Syntax Error. (Quantity field is blank or 

contains alphas or special characters):

C10.8.1.2.1.1 DAAS will reject MRA transactions (DICs DRA/DRB) 

received with an invalid quantity field (record position 25-29) to the reporting activity with a 

narrative message reject stating: Correct and resubmit. The quantity in record position 25-29 

is invalid.

C10.8.1.2.1.2. Reporting activities which acknowledged receipt using an 

invalid quantity are to correct and resubmit the MRA upon receipt of the narrative message 

reject.

C10.8.1.2.2. Blank Unit of Issue Syntax Error

C10.8.1.2.2.1. DAAS will reject legacy MRA transactions (DICs 

DRA/DRB) received with a blank unit of issue (record position 23-24) to the reporting activity 

with a narrative message reject stating: Unit of Issue contains blanks or special characters.

C10.8.1.2.2.2. Reporting activities which acknowledged receipt using a 

blank unit of issue are to correct and resubmit the MRA upon receipt of the narrative 

message reject.

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

does not match a shipment record, or contains errors, the ICP IMM will document the error in 

the management evaluation report or quality control data, as applicable.

C10.2.9. Quality Controls QUALITY CONTROL

C10.2.9.1. Evaluation of Internal MRA Processing. To comply with the requirements of 

Chapter 6, ICPs IMMs and reporting activities will include the evaluation of internal MRA 

processing in their quality control programs. The following work processes will be included: 

accuracy of MRA initiation or inquiryof follow-up, submission timeliness, and investigative 

research to determine and correct processing errors.

C10.2.9.2. Designation of Responsible Organization. Command managers IMMs will

assign to specific organizations the responsibility for directing and monitoring corrective action. 

The purpose of the program is to assist management in identifying those human, procedural, or 
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 14

system errors adversely affecting the MRA process or indicating potential deficiencies in the 

control over in-transit assets.

C10.2.9.3. Organizational Interface. Command managers IMMs must ensure effective 

organizational interrelationships among the functional operations/processes concerned with 

MRA, such as: supply, procurement, financial, inventory management, transportation, quality 

assurance, and storage.

C10.2.10. Management Evaluation MANAGEMENT EVALUATION

C10.2.10.1. The DoD Components will: C10.2.10.1.1. establish a management evaluation 

program which monitors and evaluates MRA submission to ensure compliance with MRA 

requirements. C10.2.10.1.2. Execute timely processing and perform response rate analyses to 

identify non-responsive activities and initiate corrective actions. 

C10.2.10.2. The evaluation program will provide for:

C10.2.10.2.1. Review of the MRA Management Information report (Report Control 

Symbol DD-AT&L(AR)1419 applies). DLA Transaction ServicesDAAS will prepare the report 

and provide access by electronic means. The report content is determined by the Supply Process 

Review Committee. Each Supply Process Review Committee representative is responsible for 

analysis of the report to identify potential deficiencies in their Service or Agency MRA 

operations or procedures contributing to breakdowns in internal controls for intransit wholesale 

stock. Supply Process Review Committee representatives are responsible for initiating 

corrective action with delinquent and non-reporting activities.

C10.2.10.2.2. The MRA Management information report will include as a minimum:

C10.2.10.2.2.1. General MRA Management Report Criteria. 

Documentation of nonresponses for a reporting period to include: the number of qualifying 

shipments made to an activity (by “ship to” DoDAAC); the number of MRA responses received 

from that activity; the number of nonresponses. The following sections identify a common report 

description, how to do additional analysis of the data, and the types of breakdown to be available 

for MRA responses/non-responses for several different categories and whether detail by 

individual DoDAAC is available.

C10.2.10.2.2.2. Capability for Additional MRA Report Analysis.

C10.2.10.2.2.2.1. Most of the MRA reports contain a “Save” link 

above the report title. Clicking the “Save” link launches the applicable MRA report content in a 

spreadsheet format for additional analysis 

C10.2.10.2.2.2.2. The MRA reports contain an option from the 

MRA Report Detail page (after selecting a DoDAAC) to download the entire list of document 
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 15

numbers with associated requisition/initial supply transaction data to an Excel file for additional 

research.11 The following data elements are included in the downloadable file:

• Header with Date Run and Source of Supply RIC

• Shipment Date

• Document Number

• Suffix

• Supplementary Address12

• Ship-To DoDAAC

• Signal Code13

• Bill-To DoDAAC

• Priority

• NSN

• Shipped Quantity

• Unit of Issue

• Unit Price (U/P)

• Total Cost

• Initial Transaction DLMS/MILS, (e.g., requisition or initial supply transaction if no 

requisition is available per MRA Business Rules/Decision Tree)14

• Communication Routing Identifier (COMMRI) of the system from which the requisition or 

initial supply transaction originated

• COMMRI associated with the Document Number DoDAAC, (e.g., could be a 

requisitioner/requiring/other activity)

• COMMRI where the Follow-up for Delinquent MRA transaction was transmitted

C10.2.10.2.2.3. Common Text for Report Descriptions. In general, for 

each report category, the count of qualified shipments requiring an MRA is matched against 

MRAs received/not received within the allotted timeframe and a percentage is computed. The 

reports shows results for Shipments Requiring MRA and MRA Not Received. Some of the 

reports include a column for MRA Received. Where the report is broken out by Service, click on 

the Service line hyper link to show the specific report category MRA Service/Agency Detail 

Report showing all DoDAACs making up the totals within each Service. The detail report shows 

results for shipments requiring an MRA and MRA received. Some of the detail reports include a 

column for MRA received. Selecting a DoDAAC from the detail report will show all document 

numbers associated with that DoDAAC total. Clicking on an individual document number will 

 11 ADC 1086. 12 This enhancement perpetuates legacy “MILS” data requirements due to the DLA Transaction ServicesDAAS

Micro Automated Routing System (DMARS) which performs transaction level services, such as, validation, 

editing, routing, imaging, and exception processing, using the 80 record position legacy format. 13 Ibid. 14 This is the transaction that results in the inclusion in the MRA Report per the MRA Business Rules/Decision Tree 

(ADC 1088 , Reference 3.d.).
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 16

launch WEBVLIPS for further analysis of the selected document number. Differences from this 

standard report description are noted in the following descriptions of each specific MRA report 

type:

C10.2.10.2.2.3.1. MRA Service/Agency Summary. This summary shows 

shipments for DoD Components/Participating Agencies and all categories by area of the ship-toDoDAAC and customer. Detail report is available. Summary and Detail Reports include an extra 

column for MRA received.

C10.2.10.2.2.3.2. Direct Vendor Delivery (DVD) (Non Stock) MRA 

Summary. shows DVD (Non Stock) shipments for DoD Components/Participating Agencies and 

all categories by Area and Customer. Detail report is available.

C10.2.10.2.2.3.3. Stock Shipment Summary, MRA Not Received. shows 

Stock Shipments by area of the ship-to-DoDAAC and DoD Components/ Participating Agencies. 

Detail report is available.

C10.2.10.2.2.3.4. Direct Vendor Delivery (DVD) and Stock Shipment 

Summary, MRA Not Received. This Summary shows DVD and Stock Shipments for all DoD 

Components/Participating Agencies and all categories by Ship-to DoDAAC. Detail report is 

available. 

C10.2.10.2.2.3.5. MRA Report by Source of Supply (Wholesale ICP). 

This report shows MRAs from the perspective of the wholesale ICP to review how well the 

Services acknowledge receipt of the materiel the ICP shipped out of wholesale assets for a given 

Service/Agency. Detail report is available.

C10.2.10.2.2.4. Specific Category Reports. The MRA Management Information 

report provides the capability to access information by specific categories for ammunition, contractor, 

and Army Total Package Fielding. For these specific category reports, the detail report reflects the 

same layout as the summary report:

C10.2.10.2.2.4.1. Ammunition Percent of Delinquents Summary. This 

summary shows shipments for ammunition by area of the ship-to-DoDAAC and DoD 

Component/Agency. The report shows results for Shipments Requiring an MRA, where an MRA was 

received within the allotted timeframe and where an MRA was not received within the allotted 

timeframe. Only the percentage of qualified shipments that received an MRA is shown.

C10.2.10.2.2.4.2. Contractor Percent of Delinquents Summary. This 

summary shows contractor shipments by area of the ship-to-DoDAAC and DoD 

Component/Agency. Detail report is available. The report shows results for Shipments 

Requiring an MRA, where an MRA was received within the allotted timeframe and where an 

MRA was not received within the allotted timeframe. Only the percentage of qualified 

shipments that received an MRA is shown. 

C10.2.10.2.2.4.3. Army Total Package Fielding (TPF), Percent of 

Delinquents Summary. This summary shows Army TPF shipments by area of the ship-to-
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 17

DoDAAC. The report shows results for Shipments Requiring an MRA, where an MRA was 

received within the allotted timeframe and where an MRA was not received within the 

allotted timeframe. Only the percentage of qualified shipments that received an MRA is 

shown.

C10.2.10.2.2.4.4. Percent of Delinquents General Summary. This 

summary shows general shipments by area of the ship-to-DoDAAC and DoD Component. 

The report shows results for Shipments Requiring an MRA, where an MRA was received 

within the allotted timeframe and where an MRA was not received within the allotted 

timeframe. Only the percentage of qualified shipments that received an MRA is shown. The 

report excludes the categories for Ammunition, Contractor, and Army Total Package Fielding. 

C10.2.10.3. ICPs IMMs will keep accessible records of shipments and MRA 

transactions to support the reporting requirements.

C10.3. INQUIRY FOR DELINQUENT MATERIEL RECEIPT ACKNOWLEDGEMENT

C10.3.1. Timeframe for MRA Inquiry. When materiel shipment is confirmed or when the 

requisition involves an unconfirmed MRO, the IMM will monitor for receipt of MRA(s). For 

U.S. Forces’ shipments to CONUS activities, IMMs must receive MRA for the total quantity 

shipped within 12 calendar days from the date shipped cited in the DLMS 945A, Materiel 

Release Advice, or DLMS 856S. For U.S. Forces shipments to OCONUS activities, IMMs must 

receive MRA within 29 calendar days from the date released to carrier for Transportation 

Category 1 and 2, 76 calendar days from the date released to carrier for Transportation Category 

3, or within 135 calendar days from the DS 856S shipment status release date for security 

assistance requisitions. Otherwise, the IMM will send an MRA Inquiry Transaction for the 

delinquent MRA to (See Table C10.T1):

C10.3.1.1. The organization that the materiel was shipped to, for U.S. Forces.

C10.3.1.2. The applicable ILCO, for SA requisitions.

C10.3.1.3. 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. 

C10.3.1.4. The follow-up time limits for a delinquent MRA are 17 calendar days 

from the date shipped field entry in the MRC or DLMS 856S Pseudo 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 Table 

C10.T2).

C10.3.1.3. Summary of MRA Inquiry Time Limits. Reporting activities will meet 

the time limits identified in this chapter. These requirements and timeframes are independent 

from prescribed shipment tracing and discrepancy reporting requirements and timeframes to 

which the receiving facility must also adhere. MRA inquiry time limits are summarized below:
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 18

Table C10.T2. Materiel Receipt Acknowledgement Inquiry 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 LIMIT15

Follow-Up for Delinquent 

MRA

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

Materiel Release Confirmation (MRC) or Pseudo 

Shipment Status (DLMS 856S/MILSTRIP legacy DIC 

ASH) for U.S. Forces shipments (CONUS destination).

 34 calendar days from the date shipped field entry in the 

MRC or DLMS 856S Pseudo Shipment Status for U.S. 

Forces shipments (OCONUS destination) for 

Transportation Category 1 and 2.

 81 calendar days from the date shipped field entry in the 

MRC or Pseudo Shipment Status (for U.S. Forces 

shipments (OCONUS destination) for Transportation 

Category 3.

 135 calendar days from the date shipped field entry in 

the Pseudo Shipment Status for security assistance 

shipments.

 Take the action when the time limit is reached.

C10.3.2. Delinquent MRA Inquiry Response 

C10.3.2.1. To respond to an inquiry on a delinquent MRA, the reporting activity will 

prepare a MRA following paragraph C10.2.5., above. Send the MRA to the originator of the 

inquiry within 10 calendar days from the transaction preparation date cited in the inquiry.

C10.3.2.2. 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 MRA Inquiry Transaction containing Discrepancy Indicator Code G. This 

will signal the ICP to keep the record open and continue to monitor for receipt of MRA(s), and 

send another MRA Inquiry Transaction after another 45 calendar days have elapsed (which may 

be responded to with an additional MRA Response to Inquiry Transaction 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 MRA Response to Inquiry 

Transaction with Discrepancy Indicator Code G. The Navy ship reporting activity will send an 

MRA, using DLMS 527R MRA Response to Inquiry Transaction, without the Discrepancy 

Indicator Code G, once the materiel is received (e.g., picked-up or otherwise delivered directly to 

 15 Refer to ADC 1114.
DLM 4000.25, Volume 2, Month XX, 2018

Change 11

Enclosure 1, ADC 1281

Page 19

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 MRA Response to Inquiry Transaction with 

Discrepancy Indicator Code G, the ICP will include the delinquency information in the 

management evaluation report (C10.2.10). Also, if the requisition involves an unconfirmed 

MRO (see Chapter 4, (Processing Follow-Ups)), then the ICP will resolve the record as 

described in Chapter 4 for force closed materiel release confirmation).

C10.3.2.3. When Component research into a Follow-Up For Delinquent MRA 

identifies that materiel is still in transit, the reporting activity will respond with a MRA Response 

to Inquiry transaction 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 Follow-Up For Delinquent MRA transaction after another 45 calendar days have 

elapsed.16 If a reply is not received within 45 calendar days from the sixth MRA Response to 

Inquiry transaction 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.17

C10.3.2.4. Except as noted in C10.3.2.2., if a reply is not received within 30 calendar 

days from the MRA inquiry preparation date, the IMM will include the delinquency information 

in the MRA Management Information Report. Also, if the requisition involves an unconfirmed 

MRO, then the IMM will resolve the record as described in the procedures in Chapter 4 for 

force-closed materiel release confirmations. 

Staffing Note: Moved to C10.7 Follow-ups for delinquent material receipt acknowledgement.

 16 Refer to ADC 1114. 17 Ibid.
DLM 4000.25-1, Month XX, 2018

Change 11

Enclosure 2, ADC 1281

Page 1

ENCLOSURE 2 TO ADC 1281

A. Update the DLM 4000.25, DLMS, Volume 2 Table of Contents. Removed text is identified 

by double strikethroughs. Updated and relocated text is annotated with red, bold, italics. 

CHAPTER 10 MATERIEL RECEIPT ACKNOWLEDGMENT

C10.1 GENERALPURPOSE..................................................................... C10-1

C10.2 RESPONSIBILITIESAPPLICABILITY....................................... C10-TBD

C10.3 INQUIRY FOR DELINQUENT MATERIEL RECEIPT 

ACKNOWLEDGMENTEXCLUSIONS.................................. C10-TBD

C10.4 COMMUNICATIONS ................................................................. C10-TBD

C10.5 RESPONSIBILITIES.................................................................. C10-TBD

C10.6 PREPARING AND SENDING MATERIAL RECEIPT 

ACKNOWLEDGEMENT ...................................................... C10-TBD

C10.7 FOLLOWUP FOR DELINQUENT MATERIEL RECEIPT 

ACKNOWLEDGMENT......................................................... C10-TBD

C10.8 CORRECTING OR CANCELING MATERIAL RECEIPT 

ACKNOWLEDGEMENT ...................................................... C10-TBD

C10.9 QUALITY CONTROL................................................................. C10-TBD

C10.10 MANAGEMENT EVALUATION................................................ C10-TBD

(Intervening text not shown)

TABLES

(Intervening Text Not Shown)

C10.T1 MATERIEL RECEIPT ACKNOWLEDGMENT SUBMISSION

TIME LIMITS FOR REPORTING ACTIVITIES ........................ ..C10-TBD

C10.T2 MATERIEL RECEIPT ACKNOWLEDGE INQUIRY FOLLOW-UP

TIME LIMITS FOR ICPS/DLA DISPOSITION SERVICES ........ C10-TBD
DLM 4000.25-1, Month XX, 2018

Change 11

Enclosure 3, ADC 1281

Page 1

ENCLOSURE 3 TO ADC 1281

Update the DLM 4000.25-2, MILSTRAP Table of Contents. Removed text is identified by 

double strikethroughs. Updated and relocated text is annotated with red, bold, italics. 

TABLE OF CONTENTS

(Intervening Text Not shown)

C6 CHAPTER 6 – MATERIEL RECEIPT ACKNOWLEDGMENT Reserved

– See 4000.25, DLMS, Volume 2, Chapter 10

(Intervening Text Not shown)

APPENDIX 4 – TIME LIMITS Reserved – See 4000.25, DLMS, Volume 2, 

Appendix 12

AP4 TIME LIMITS 

INDEX..................................................................AP4-i

AP4.1 MATERIEL RECEIPT ACKNOWLEDGMENT TIME 

LIMITS............AP4.1-1

APPENDIX 5 – BUSINESS RULES – Reserved – See 4000.25, DLMS, 

Volume 2, Chapter 10

AP4 BUSINESS 

RULES.....................................................................AP5-i

AP4.1 MATERIEL RECEIPT ACKNOWLEDGMENT REPORT

BUSINESS RULES 

AP5.1-1

(Intervening Text Not shown)

FIGURES

AP5.1.F1 MRA REPORT BUSINESS RULES....................................... AP5.1-9
Enclosure 4, ADC 1281

Page 1

ENCLOSURE 4 TO ADC 1281

Administrative update to DLMS 527R MRA Implementation Convention (IC) to update 

terminology from “inquiry” to follow-up”, associated with Follow-up for Delinquent MRA 

transaction.

# Location Revisions to DLMS 527R MRA Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add ADC 1281 to DLMS Introductory Notes: 

- ADC 1281, Align Materiel Receipt Acknowledgement 

(MRA) Procedures in DLM 4000.25, Volume 2 with

DLM 4000.25-2 (Supply)

Identifies DLMS 

Changes included in 

the IC

2. IC cover page 

DLMS 

Introductory 

Notes

Revise existing DLMS Note 1:

DLMS Note:

1. Receiving activities use this transaction set to report both 

receipts and historical receipt information to owners and 

other management control activities. Owners use this

transaction set to inquire to storage activities about the 

status of overdue receipts. For Materiel Receipt 

Acknowledgment (MRA), reporting activities use this 

transaction set to acknowledge, to the Inventory Control 

Point (ICP), the receipt or nonreceipt of materiel; and ICPs 

use this transaction set to inquirefollow-up to the reporting 

activity when MRA is delinquent. DLA Disposition 

Service Field Offices use to provide Disposition Services 

Turn-in Receipt Acknowledgement (TRA) back to the 

activity identified in the disposal turn-in document (DTID) 

number. For Army Total Package Fielding (TPF), Unit 

Materiel Fielding Points and staging sites use this 

transaction set to acknowledge, to the Fielding Command, 

the receipt of materiel. This transaction encompasses the 

functionality of MILSTRAP Document Identifier Codes 

(DIC) D4_, D6_, DRA, DRF, DXA, DXB, DXC, and 

DXD. This transaction also accommodates the 

functionality of non-DLSS DIC as follows: DIC C2J, C2K, 

and C3D in support of Medical requirements; DIC BAY in 

support of Army Total Package Fielding; Distribution 

Standard System DIC Z4S, Z6S, and Z6T supplemental 

receipt data; and NAVSUP P-724 BG1/BG2 serial/lot 

number reporting transactions.

Update terminology

3. 1/BR02/0-90 Revise existing code TG DLMS Note:

TG Receipt Acknowledgement Inquiry

DLMS Note: Use when initiating an inquiry for a Followup for Delinquent MRA. (MILSTRAP legacy DIC DRF 

functionality)

Update terminology
Enclosure 4, ADC 1281

Page 2

# Location Revisions to DLMS 527R MRA Reason

4. 1/BR02/020BR Revise existing code TH DLMS Note:

TH Receipt Acknowledgement Advice

DLMS Note: MRA Transaction. Use for MRA to 

acknowledge the receipt or nonreceipt of materiel 

(MILSTRAP legacy DIC DRA functionality). Use in 

conjunction with BR06 Action Code V-Respond when 

sending MRA in response to an Inquiry a Follow-up for 

Delinquent MRA (MILSTRAP legacy DIC DRB 

functionality.)

Update terminology

5. 1/BR06/020 Revise existing code V DLMS Note:

V Respond

DLMS Note: MRA Response to Inquiry follow-up 

Transaction. Use in conjunction with BR02 Transaction 

Type Code TH when sending an MRA in response to an 

Inquiry a Follow-up for Delinquent MRA. (MILSTRAP 

legacy DIC DRB functionality.) Refer to ADC 313.

Update terminology

6. 2/N901/030 Revise existing N9 Segment DLMS Note:

DLMS Note: Must use for all nonprocurement source 

transactions (which includes all MRA, inquiry follow-up

on delinquent MRA, and disposition services turn-in 

receipt acknowledgement (TRA) transactions) to identify 

the document number.

Update terminology