17 Minutes Services review procedures to ensure that the All 30 Jan 2014 Open 6/16/15 When Navy ERP – generates an outgoing requisition proper suffixes are identified in the MRA 19 Sep 2014 § n (A0_) to DLA, and DLA splits the transactions to align with the suffixes identified 10 Dec 2014 Page 9 order, Navy ERP should send in the corresponding shipment status. corresponding suffix-coded MRA transactions. Navy will submit a trouble ticket/Change Request to require these transactions in Navy ERP. 6/23/15 AF Retail (ILS-S) reply: – ILS-S MRA programs generate accurate DLMS 527Rs with the correct suffix code contingent upon base user entering correct value on REC input. 18 Minutes Marine Corps to research why MRA USMC 30 Jan 2014 Open No updates received transactions are being sent to the RIC LA9 19 Sep 2014 § n – (Advanced Military Packaging MILSTRIP 10 Dec 2014 Page 9 – Orders, Oshkosh, WI. LA9 is not a valid wholesale ICP RIC per LMARS business rules and confirmed during the staffing of ADC 1025. If LA9 is in fact a wholesale ICP RIC, then Marine Corps needs to submit PDC to update LMARS business rules to reflect that change. 19 Minutes Navy submit a PDC to define and document Navy 30 Jan 2014 Open 6/16/15 PDC should not be required. – The two examples provided identify that their Service unique data requirement for RP 19 Sep 2014 § n the site/user basically copied the last 77-80 (Service-use field) in the MRA legacy 10 Dec 2014 Page 9 transaction they received (AE1 status) and transaction (DRA) and clarify the procedures changed the DIC to DRA. In doing this, the being used. structure/card columns (ccs) did not match the DRA layout.
17 Minutes § n Page 9 Services review procedures to ensure that the proper suffixes are identified in the MRA transactions to align with the suffixes identified in the corresponding shipment status. All 30 Jan 2014 19 Sep 2014 10 Dec 2014 Open 6/16/15 – When Navy ERP generates an outgoing requisition (A0_) to DLA, and DLA splits the order, Navy ERP should send corresponding suffix-coded MRA transactions. Navy will submit a trouble ticket/Change Request to require these transactions in Navy ERP. 6/23/15 – AF Retail (ILS-S) reply: ILS-S MRA programs generate accurate DLMS 527Rs with the correct suffix code contingent upon base user entering correct value on REC input. 18 Minutes § n Page 9 Marine Corps to research why MRA transactions are being sent to the RIC – LA9 (Advanced Military Packaging – MILSTRIP Orders, Oshkosh, WI. LA9 is not a valid wholesale ICP RIC per LMARS business rules and confirmed during the staffing of ADC 1025. If LA9 is in fact a wholesale ICP RIC, then Marine Corps needs to submit PDC to update LMARS business rules to reflect that change. USMC 30 Jan 2014 19 Sep 2014 10 Dec 2014 Open No updates received 19 Minutes § n Page 9 Navy submit a PDC to define and document their Service unique data requirement for RP 77-80 (Service-use field) in the MRA legacy transaction (DRA) and clarify the procedures being used. Navy 30 Jan 2014 19 Sep 2014 10 Dec 2014 Open 6/16/15 – PDC should not be required. The two examples provided identify that the site/user basically copied the last transaction they received (AE1 status) and changed the DIC to DRA. In doing this, the structure/card columns (ccs) did not match the DRA layout.
SPRC-(MRA)-13-3-AI-Tracking.docx