DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

June 12, 2014 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

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

Revise Materiel Receipt Acknowledgement (MRA) Report Selection Criteria 

to Reflect the MRA Process Exclusion for Receipt Transaction Reporting 

(Supply/MILSTRAP) 

The attached change to DLM 4000.25, Defense Logistics Management System, 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. DLA Transaction Services projected initial implementation date is July 15, 2015 

for Air Force, Marine Corps, and DLA. Army and Navy implementation at a later date is 

dependent upon their implementation of the Delinquent MRA Follow-up process. 

Addressees may direct questions to Mary Jane Johnson, (703) 767-0677; DSN 427-0677 

or email: Mary.Jane.Johnson@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. 

Attachment 

As stated 

cc: ODASD (SCI) 

c-:i ~~ 

DONALD C. PIPP 

Director 

Defense Logistics Management 

Standards Office 
ATTACHMENT TO ADC 1087

Revise Materiel Receipt Acknowledgement (MRA) Report Selection Criteria

to Reflect the MRA Process Exclusion for Receipt Transaction Reporting

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

b. Functional POC: Mary Jane Johnson, DLMSO, DOD MILSTRAP Administrator, 

(703) 767-0677; DSN 427-0677; email: mary.jane.johnson@dla.mil

2. FUNCTIONAL AREA: Supply/Materiel Receipt Acknowledgment (MRA) Report (DLA 

Transaction Services Logistics Report-MRA Report); DLMS/MILSTRAP/DAAS

3. REFERENCES (available at www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp):

a. Defense Logistics Manual (DLM) 4000.25-2, Military Standard Transaction Reporting and 

Accountability Procedures (MILSTRAP), Chapter 6, MRA

b. DLM 4000.25, Defense Logistics Management System, Volume 2, Chapter 10, MRA

c. DLM 4000.25-4, Defense Automatic Addressing System (DAAS), Appendix 5, 

Logistics Information Data Services (LIDS)

4. APPROVED CHANGE(S):

a. Brief Overview of Change:

(1) Revise the MRA Report selection criteria to exclude intra-Component shipments of 

wholesale assets when those assets are reported by a Materiel Receipt (aka Receipt) transaction to the 

issuing wholesale Inventory Control Point (ICP), rather than by an MRA transaction.

(a) This change uses the absence of a Follow-Up for Delinquent MRA

transaction from the issuing wholesale ICP, for an intra-Component shipment out of wholesale 

assets, as criteria for excluding that shipment from the MRA Report. Rationale is that if the 

issuing ICP is expecting a Receipt transaction (rather than an MRA transaction) on an intraComponent basis, based on the Component’s business process, then they would not follow up for a 

delinquent MRA transaction. 

(b) The ICP uses a separate process, unrelated to the MRA process, to follow 

up for a Receipt transaction. MILSTRAP, Chapter 4, paragraph C4.10., addresses the Materiel 

Receipt Follow-up transactions and process:

“C4.10. FOLLOW-UP ON INTRANSIT DUE-INS

C4.10.1. When a maximum of 45 calendar days have elapsed since the shipping date 

indicated in shipment notification and receipt of the total quantity has not been reported, the 

owner will follow up, for the intransit quantity(s) to the storage activity(s) designated to receive 

the materiel. (Extension of the 45 day calendar timeframe is authorized when long intransit times 

are involved.)

Attachment, ADC 1087

Page 1 of 7
C4.10.2. Prepare follow-ups on receipts due from procurement sources using Document 

Identifier Code (DIC) DXA. Prepare follow-ups on receipts due from nonprocurement sources using 

DIC DXB.

 C4.10.3. When the storage activity reply indicates that the materiel has not been received 

(DIC DXC or DXD), any required shipment tracer and/or discrepancy reports are to be initiated 

under the procedures cited in C4.8. Coordinate with the CAO/PO for intransit contract receipts.”

(2) The specific transactions involved in this discussion are:

• MRA, identified by DLMS 527R with beginning segment (1/BR02/020)

Transaction Type Code TH (MILSTRAP legacy DIC DRA).

• Follow-Up for Delinquent MRA, identified by DLMS 527R with Transaction 

Type Code TG (MILSTRAP legacy DIC DRF).

• Materiel Receipt, identified by DLMS 527R with Transaction Type Code D4 

(MILSTRAP legacy DIC D6_).

• Materiel Receipt Follow-up, identified by DLMS 527R with 1/BR02/020

Transaction Type Code IN (MILSTRAP legacy DIC DXA/DXB)

b. Background:

(1) At past Supply Process Review Committee (PRC) meetings, Army and Navy 

identified a disconnect with the MRA Report selection criteria for identifying “No MRA” when 

the issuing ICP expects and receives a Receipt transaction on an intra-Component basis, rather 

than an MRA transaction, as a result of the ICP’s shipment of wholesale assets, whether pushed 

or pulled, delivered or picked up, issued from onhand assets, or procured for direct vendor 

delivery (DVD) from commercial sources. Army and Navy provided the following examples:

(a) Army has had Single Stock Fund for years under which the Army 

wholesale ICPs own much of Army 'retail' assets. Under Single Stock Fund, the Army noted 

that there are circumstances where Army retail activities provide Materiel Receipt transactions, 

rather than MRA transactions, to the owning/issuing Army wholesale ICP.

1 Materiel Receipt 

transactions are sent in lieu of MRAs when the routing identifier code (RIC) of the 

corresponding (document number and suffix code match) Materiel Release Order (MRO) 

(DLMS 940R; legacy DIC A5_, record position (rp) 67-69, RIC of the activity originating the 

MRO) or Direct Delivery Notice (DLMS 870S; legacy DIC AB_, rp 4-6, RIC of the source of 

supply furnishing the status) equals “A12, AJ22, AKZ, B14, B16, B64, or B17,” the signal code 

equals “M,” and the fund code equals “GK.” 

1 The Army does have instances under Single Stock Fund when a Materiel Receipt is provided by the Army retail 

activity and then an MRA is provided by the owning Army wholesale ICP to the issuing ICP. These Materiel 

Receipt and MRA instances apply mostly to Army Working Capital Fund funded requisitions sent to DLA, GSA, or 

the PICA/SICA or referred back to the Army under DOD Lateral Redistribution. The signal and fund codes are 

different though, so they should never be confused with instances where only a Materiel Receipt is provided by the 

retail activities.

2 RIC “AJ2” is not applicable to the Direct Delivery Notice.

Attachment, ADC 1087

Page 2 of 7

 
(b) Navy ERP expects Receipt transactions when materiel is sent to sites 

where Navy is accountable for maintaining inventory balances in Navy ERP (wholesale ICP). 

One example cited at a prior Supply PRC meeting was that Navy Commercial Asset Visibility 

(CAV) contractors, and Navy CAV Organic Repair Module (CAV-ORM) activities, provide a 

Receipt transaction (rather than an MRA transaction) back to Navy ERP, which issued the 

materiel out of Navy wholesale assets.

(2) In accordance with MRA procedures in DOD MILSTRAP and DLMS (references 3.a. 

and 3.b. respectively), the scenarios noted above are excluded from the MRA process because the 

Receipt transaction, rather than an MRA, is provided to the issuing wholesale ICP. There is no 

expectation that the issuing wholesale ICP would receive both an MRA transaction and a Receipt 

transaction from the intra-Component reporting activity. Below is an excerpt from MILSTRAP 

Chapter 6 documenting the MRA exclusion when a Receipt transaction is reported to the

issuing/owning ICP:

“C6.3. EXCLUSIONS. These [MRA] procedures are not applicable to the 

following:”

[Intervening text not shown.]

“C6.3.5. Receipts into DoD wholesale stock which are controlled under 

Chapter 4, including relocations/shipments to contractors, commercial, or industrial activities 

which are receipt reported to the owning ICP. However, when ICPs requisition materiel 

from another ICP or the DLA Disposition Services and the receipt is reported under Chapter 4, 

the requisitioning ICP shall acknowledge the receipt.”

c. Describe Approved Change in Detail:

(1) Revise the MRA exclusion for Receipt transactions, as currently documented in 

MILSTRAP/DLMS to stipulate the Receipt transaction exclusion for relocations/shipments to 

contractors, commercial, or industrial activities that are receipt reported to the owning ICP only 

applies when the ICP is both the issuing and owning ICP for the materiel. Currently this 

exclusion only stipulates that the receipt is reported to the owning ICP. 

(2) Add the following exclusion criteria to the MRA Report Selection Criteria: 

Exclude intra-Component shipments when the issuing/owning ICP does not generate a FollowUp for Delinquent MRA transaction (DLMS 527R with BR02 Transaction Type Code TG or 

MILSTRAP legacy DIC DRF) within the required follow-up time limit. DLA Transaction 

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

Time Limits to follow up for Delinquent MRA:

• Follow up at 45 calendar days from the date shipped field entry in the Materiel 

Release Confirmation (MRC) or the Pseudo Shipment Status for Unconfirmed

Materiel Release Orders (DLMS 856S/MILSTRIP legacy DIC ASH) for U.S. 

Forces shipments (CONUS destination).

Attachment, ADC 1087

Page 3 of 7
• Follow up at 105 calendar days from the date shipped field entry in the MRC or 

the Pseudo Shipment Status for Unconfirmed Materiel Release Orders for U.S. 

Forces shipments (Overseas destination).

d. Revisions to DLM 4000.25 series Manuals (changes are shown by bold, red, italics): 

(1) DLM 4000.25-2, MILSTRAP, Chapter 6 (corresponding changes will be 

made to DLMS, Volume 2, Chapter 10):

“C6.3. EXCLUSIONS. These procedures are not applicable to the following:”

[Intervening text not shown.]

“C6.3.5. Receipts into DoD wholesale stock which are controlled under Chapter 

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

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

when ICPs requisition materiel from another ICP or the DLA Disposition Services and the receipt 

is reported under Chapter 4, the requisitioning ICP shall acknowledge the receipt.”

(2) DLM 4000.25-4, DAAS (reference 3.c.). Revise Appendix 5, Logistics 

Information Data Services (LIDS), paragraph AP5.2.12.3. MRA Report Exclusions, to add a 

new subparagraph: 

“AP5.2.12.3.xx. 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 Services 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.3” 

3 Under ADC 1087, DLA Transaction Services implementation for Air Force, Marine Corps, and DLA is 

projected for July 1, 2015; delayed implementation authorized for Army and Navy ICPs.

5. REASON FOR CHANGE: Improves MRA Report by closing a known gap in report 

selection criteria. If a Receipt transaction, rather than an MRA transaction, is expected by the 

wholesale ICP that issued the item, then the issuing ICP should not generate the Follow-up for 

Delinquent MRA transaction. There is a separate process to follow for a Receipt transaction 

that is unrelated to the MRA process as noted in paragraph 4.a.(1)(b).

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Improves the accuracy of the MRA Report by correcting the MRA Report 

selection criteria to eliminate capture of intra-Component shipments out of wholesale assets when

the issuing Component’s business process requires the assets to be reported as a Receipt 

transaction back to the issuing ICP rather than an MRA transaction. 

b. Disadvantages: None.

Attachment, ADC 1087

Page 4 of 7
7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT: This standard generic logic is expected to work for all Components, 

rather than attempting to discover, document, and program for specific rules applicable to 

each scenario/trading partner arrangement.

8. ADDITIONAL COMMENTS TO CONSIDER: DOD Components must ensure their 

automated information systems (AIS) correctly generate the Follow up for Delinquent MRA 

for intra-Component shipments out of wholesale assets when their business process does not 

require that a Receipt transaction, rather than an MRA transaction, be provided back to the 

issuing ICP. 

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET:

a. The new rule approved by this change is dependent upon proper implementation of 

the MILSTRAP/DLMS process to follow up for delinquent MRA. Accordingly, staggered

implementation at a later date will be required for those DOD Components that have not 

implemented the Delinquent MRA Follow-up process by the time DLA Transaction Services 

implements this change.

b. DLA Transaction Services reported that they cannot implement this ADC until 

approximately July 15, 2015 (thirteen months after ADC date). DLA Transaction Services will 

implement with the DOD Components on a staggered basis, based on whether the Component has 

implemented the Delinquent MRA Follow-up process as noted above.

(1) DLA Transaction Services will accomplish the initial July 15, 2015 

implementation with those DOD Components that have advised that the follow-up for delinquent 

MRA process is currently implemented in their systems. At time of publication of this 

approved change, DLA, Air Force, and Marine Corps have advised that they have 

implemented the Delinquent MRA Follow-up process; accordingly, they are subject to the 

July 15, 2015 implementation for this ADC. 

(2) DLA Transaction Services will delay implementation of ADC 1087 for 

Army and Navy, until such time as Army and Navy have implemented the Delinquent MRA 

Follow-up process. Army and Navy must notify DLMSO when Army LMP, and Navy ERP

respectively, have implemented the Delinquent MRA Follow-up process. At that time 

DLMSO can coordinate the Army and/or Navy ADC 1087 implementation date with DLA 

Transaction Services. DLA Transaction Services generates the MRA Reports from the set of data 

that is pulled for the Logistics Metrics Analysis Reporting System (LMARS). Accordingly, DLA 

Transaction Services will use the current list of wholesale Army and Navy ICP RICs identified for 

LMARS, to exclude Army and Navy from initial implementation. Refer to LMARS Table D, 

Wholesale ICP RICs, available at: 

www.dla.mil/j-6/dlmso/eLibrary/Documents/PMPRC/KeyLMARSTables.docx. At time of 

publication of this ADC those wholesale ICP RICs are:

(a) Army: A12, A35, AKZ, AP5, B14, B16, B17, B64, B69, BAM, BR4

(b) Navy: N52, NFZ, NRP

Attachment, ADC 1087

Page 5 of 7
10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

11. IMPACT:

a. New DLMS Data Elements: None.

b. Changes to DLMS Data Elements: None.

c. Automated Information Systems (AIS): Army and Navy are not compliant with 

the Follow up for Delinquent MRA process, and must implement this DOD requirement

before this ADC can be implemented for their Service. DLA, Air Force and Marine Corps 

have implemented the process to follow up for delinquent MRA.

(1) Navy advised that the MRA follow-up process was not implemented in 

Navy ERP. Navy is investigating and will provide additional information when known. 

DLA Transaction Services implementation of this change for Navy will be held in abeyance 

until Navy implements the DOD requirement for the Follow up for Delinquent MRA process.

ACTION FOR NAVY: Provide DLMSO with Navy ERP implementation information 

for the Follow up for Delinquent MRA process. 

(2) Army advised that Army LMP implementation of outbound Follow-up for 

Delinquent MRA transaction is pending action to correct some logic. DLA Transaction 

Services implementation of this change for Army will be held in abeyance until Army 

implements the DOD requirement for the Follow up for Delinquent MRA process. 

ACTION FOR ARMY: Provide DLMSO with Army LMP implementation information 

for the Follow up for Delinquent MRA process.

d. DLA Transaction Services: Requires modification of MRA Report selection 

criteria and the associated program logic and Logistics On-line Tracking System (LOTS) 

database. Once the ADC is released, DLA Transaction Services estimates that they will 

require 12 months to modify coding for the MRA Report selection criteria and LOTS changes,

and an additional 1 month to test MRA changes.

• DLA Transaction Services implementation target is 13 months after release of 

the approved DLMS change for those Components that have implemented the 

MILSTRAP/DLMS ICP Follow-up for Delinquent MRA process. At time of ADC 

publication, it is known that initial implementation will be with Air Force, Marine Corps, and 

DLA.

• DLA Transaction Services will provide staggered implementation at a later 

date, for Army and Navy, once Army and Navy have not implemented the Delinquent MRA 

Follow-up process.

Attachment, ADC 1087

Page 6 of 7
12. PROPOSED DLMS CHANGE (PDC) 1087 RESPONSE TABLE:

Component Response to PDC 1087 Disposition

DLA 

Transaction 

Services

For implementation, after the ADC is approved, 

estimate 12 months for the LOTS changes and an 

additional 1 month to test MRA changes. MRA 

coding can be done while LOTS is being worked 

on so just some final testing would be needed. 

Noted.

Initial implementation with Components that have 

implemented the Follow-up for Delinquent MRA 

process, estimated for 13 months after date of 

ADC. Those Components are: Air Force, Marine 

Corps, and DLA.

DLA Concur without comment. We do not foresee any 

system changes needed to comply.

DLA email advised that DLA is compliant with the 

DLMS Follow up for Delinquent MRA process.

Noted. 

DLA implementation will coincide with DLA 

Transaction Services implementation.

Air Force Concurs as written.

The AF implemented the follow up on open 

shipments years ago.

[AF clarified that ‘follow up on open

Shipments’ refers to the process to follow up for 

delinquent MRA (MILSTRAP legacy DIC DRF).] 

Noted.

Air Force implementation will coincide with DLA 

Transaction Services implementation.

Army Concurs.

Army LMP implementation of outbound Follow-up 

for Delinquent MRA transactions is pending action 

to correct some logic.

ADC 1087 implementation delayed for Army 

until such time as outbound Follow up for 

Delinquent MRA (527R with 1/BR02/020 

Transaction Type Code TG/legacy DIC DRF) 

process is implemented. 

Outbound follow-up not implemented at time of 

ADC. Army must advise DLMSO when 

implemented, to establish an ADC 1087 

implementation date for Army.

Marine Corps Concur without comment. 

Marine Corps uses the Air Force’s Stock Control 

System for our inventory control point activities. 

That system is compliant in generating follow-ups 

for delinquent MRA transactions under DOD 

MILSTRAP/DLMS rules. We use this function 

regularly.

Noted. 

Marine Corps implementation will coincide with 

DLA Transaction Services implementation.

Navy Concurs as written. ADC 1087 implementation delayed for Navy 

until such time as outbound Follow up for 

Delinquent MRA (527R with 1/BR02/020 

Transaction Type Code TG/legacy DIC DRF) 

process is implemented.

Navy previously advised that the MRA follow-up 

process was not implemented in Navy ERP. Navy 

is investigating. Navy must advise DLMSO 

when implemented, to establish an ADC 1087 

implementation date for Navy.

USTRANSCOM Abstain. There is no impact to USTRANSCOM 

systems.

Noted.

Attachment, ADC 1087

Page 7 of 7