1. Materiel Receipt Acknowledgement (MRA) Issues
Supply Process Review Committee Meeting 17-1
May 17, 2017
Mary Jane Johnson
Paul Jensen
Enterprise Business Standards Office

2. Materiel Receipt Acknowledgment
Transaction Definitions
Discrepancy Indicator Codes (partial list)
MRA Issue–MRA for requisitions recorded before physical distribution / receipt occurred
Processing Details–Discrepancy Indicator Codes

3. Materiel Receipt Acknowledgment - Definitions
DRA Materiel Receipt Acknowledgement (MRA) Transaction is DLMS 527R, identified by the ASC X12 beginning segment (1BR02/020) Transaction Type Code TH – Receipt Acknowledgement Advice. Provides MILSTRAP legacy DIC DRA functionality
DRF MRA Inquiry Transaction is DLMS 527R, identified by Transaction Type Code TG – Receipt Acknowledgement Inquiry. Provides MILSTRAP legacy DIC DRF functionality.
DRB MRA Response to Inquiry Transaction is DLMS 527R, identified by Transaction Type Code TH–Receipt Acknowledgement Advice, used with 1/BR06/20 Action Code V–Respond. Provides MILSTRAP legacy DIC DRB functionality.

4. Discrepancy Indicator Codes (partial list)
Used in the MRA transaction to indicate when a supply or transportation discrepancy or product quality deficiency affects the receipt posting and/or MRA process. (DLMS 527R LQ01 Segment/Legacy DRA/DRB record position 63)
B – No record of requisition. Used in the MRA Response to Inquiry if there is no record of the requisition and the materiel has not been received.
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 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. Navy use in MRA Response to Inquiry (DRB) 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. The reporting activity may send up to six MRA Response to Inquiry transactions with Discrepancy Indicator Code G. (ADC 474). Navy Units with DoDAACs starting with V or R will use Discrepancy Indicator Code H for materiel in transit.
ADC 474 (April 2012) was initiated by DLA

5. Discrepancy Indicator Codes (partial list) (Continued)
H – Materiel still in transit. Components will use in the MRA Response to Inquiry when responding to an MRA Inquiry and the Component research identified that the materiel is still in transit. The reporting activity may send up to six MRA Response to Inquiry transactions with Discrepancy Indicator Code H. This is similar to Discrepancy Code G – Nonreceipt Due to Extended Transit Time, added in ADC 474 for Navy use
ADC (April 2016) was initiated by DLA

6. Issue: MRA for requisitions recorded before physical distribution / receipt occurred
Comment from U.S. TRANSCOM about logistics response time (LRT) performance where an issue was identified with some requisitions they report each month that are closed out by a MRA Response to Inquiry (DRB) with Discrepancy Indicator Code F transaction.
The U.S. TRANSCOM team felt the Services should be aware that using Discrepancy Indicator Code F (Shortage or partial or total nonreceipt) when materiel is still in transit caused inaccurate date reporting in Logistics Metrics Analysis Reporting System (LMARS).

7. Question: Is there logic in LMARS and the MRA process to indicate if the MRA Response to Inquiry (DRB) has Discrepancy Indicator Code F that the receipt will indicate the item has not been received?
Answer:
There is no logic to “not accept” the DRA/DRB with Discrepancy Indicator Code B or F
When MRA procedures were initially developed, the inventory control point (ICP) representatives noted they close out their records with the DRA/DRB regardless of the discrepancy indicator code
Problem Description: MRA is recorded by LMARS when the first DRA or DRB transaction is received. Sometimes, the DRB that is processed as the acknowledgement, is sent with a discrepancy code to inform of non-receipt, not acknowledgement of receipt.
Discrepancy Indicator Codes G and H were added to allow for longer time before reporting an MRA. DAAS implemented G, and H is pending implementation.
Services have not reported implementation of G (Navy), or H (All)

8. MRA Processing Details
MRA processing has a time limit based on expected delivery time for the requisition. If the requisition exceeds the expected delivery time then an MRA Inquiry (DRF) transaction is sent to the consignee.
The reply is sent to LMARS as an MRA Response to Inquiry (DRB) transaction with a discrepancy Indicator code is necessary.
B (No record of requisition)
or F (Not received, or partial/shortage shipment received)
LMARS does not process these codes differently than a DRB without a discrepancy code. ADCs 474 and 1114 added codes G and H.
LMARS was updated to process these new codes (H is pending), however the Service supply systems need to implement ADCs 474 (Navy) and 1114 (All) to use the new codes
If Discrepancy Indicator Code H is received by LMARS, the expected delivery time will be extended by a set number of days. This extension of delivery timeframe can only happen for six time periods before MRA Reports indicate not MRA was received. LMARS has been updated to process G and H codes but Services do not seem to be sending / using these codes yet.

9. Way Ahead
Discontinue use of Discrepancy Indicator Code F when status indicates the materiel is still in transit.
Use Discrepancy Indicator Code G for Nonreceipt due to extended transit time
Use Discrepancy Indicator Code H for shipments in transit.
Services will tack and report implementation of ADCs 474/1114 and use of Discrepancy Indicator Code H and G (Navy) under an ongoing OUSD(SCI) coordinated effort to track DLMS implementation status

10. Potential Issues with Discrepancy Codes G and H
1. If the 527R (MRA) comes in with multiple TCNs and each one has a different discrepancy code, MRA and LMARS can only put 1 in the data download since everything is by document number / suffix. WEBVLIPS can show the latest discrepancy code for each TCN Status: EBSO and DAAS working on the issue 2. DAAS history files for MRA indicate some transactions appear to have a G or H in record position 63 – Analysis shows this is incorrect data replicated from earlier transactions, for example a portion of a project code used in the initial requisition is still showing in an MRA. Status: Use correct transaction format (legacy), and in DLMS this should not be an issue if the transaction correctly mapped