OFFICE OF THE ASSISTANT SECRETARY OF DEFENSE

3500 DEFENSE PENTAGON

WASHINGTON, DC 20301-3500

 SUSTAINMENT 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE

SUBJECT: Approved Defense Logistics Management Standards Change 1292, Images of 

Receipt Transaction for Defense Automatic Addressing System and System 

Generated Materiel Receipt Acknowledgements (Supply)

The attached Approved Defense Logistics Management Standards Change (ADC), as 

outlined in the attachment, is approved for implementation.

Addressees may direct questions to Rafael Gonzalez, e-mail: rafael.gonzalez@dla.mil. 

Others must contact their designated Process Review Committee representative available at 

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

 

Leigh E. Method, SES 

Deputy Assistant Secretary of Defense

 for Logistics

Attachment:

As stated

cc: 

OUSD(C)

DLA J6DS
Attachment, ADC 1292

Page 1

ADC 1292

Images ofReceipt Transaction for DAAS and System Generated 

Materiel Receipt Acknowledgements (MRA) (Supply)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

Technical/Functional POC: Mr. Rafael Gonzalez, e-mail: Rafael.Gonzalez@dla.mil

2. REFERENCES:

a. DLM 4000.25, Volume 2, Chapter 13, Materiel Receipt 

b. DoDM 4140.01, Volume 5, Delivery of Materiel, Change 1, September 17, 2018.

c. Approved DLMS Change (ADC) 1343, Missing Materiel Receipt Acknowledgement 

(MRA) Closeout, June 21, 2021.

d. DLM 4000.25, Volume 2, Chapter 10, Materiel Receipt Acknowledgement 

e. DLM 4000.25, Volume 6, Logistics Systems Interoperability Support Services,

Chapter 4, Pipeline Measurement

f. Joint Supply PRC/JPIWG Meeting Minutes 14-1 October 22-23, 2014

3. APPROVED CHANGE(S): Changes from the proposed to approved change are identified 

in green shade text.

a. Brief Overview of Change:

(1) Updates DLM 4000.25 Volume 2, Chapter 13 (Reference 2.a.) procedures in 

accordance with DoDM 4140.01, Volume 5, Delivery of Materiel (Reference 2.b.). The DoDM 

4140.01 requires DoD Components to send an image of the receipt transaction to Defense 

Automatic Addressing System (DAAS) under certain scenarios where the Component does not

need to report the receipt of assets to an external automated information system (AIS) via

DAAS.

(2) Authorizes DAAS to create and transmit Material Receipt

Acknowledgements (MRAs) on behalf of the services when needed. This part of the change 

supports the opt-out options for MRA close-out procedures under Reference 2.c. 

(3) Enables the Logistics Metrics Analysis Reporting System (LMARS) to 

calculate logistic response time (LRT) using images of receipt transactions when the original 

receipt or the MRA is not available.
Attachment, ADC 1292

Page 2

b. Background:

(1) On October 22-23, 2014, the Joint Supply Process Review Committee (PRC) 

14-01 and Joint Physical Inventory Work Group (JPIWG) members met to discuss the 

accountability of materiel while in maintenance (Reference 2.f.). The members reported a large 

volume of receipts recorded directly in the Service systems in which the materiel is received 

without exiting a receipt transaction to the materiel owner and enterprise systems via DAAS. 

Consequently, DoD may not have visibility of all materiel receipts and cannot properly 

calculate LRT. Contributing to this matter is the lack of an MRA that would close out the 

shipment. An outcome of this meeting was, ODASD(Logistics) agreed to change the policy and 

require DoD Components to transmit receipt images to DAAS for the defined scenario. DoDM 

4140.01, Volume 5, Enclosure 3, paragraph 7.a.(3)(c), Receipt Processing, Delivery of Materiel

shows:

“(3) Send an image of the receipt transaction to Defense Automatic Addressing System in 

accordance with the procedures in Volume 6 of Reference (p) for all receipts of materiel 

from the wholesale level, e.g.: 

(a) Lateral redistributions and depot level reparables that have been directed by the 

ICP or integrated materiel manager. 

(b) Organic or commercial items shipped directly from maintenance. 

(c) Receipts for that have been items performed internally by Component personnel 

within a Component AIS without the processing of a receipt transaction to the owner 

through the Defense Automatic Addressing System.”

(2) ADC 1343 (Reference 2.c.), established procedures to administratively close 

outstanding orders when the wholesale ICP (source of supply) receives no MRA. The 

Integrated Project Team requested additional changes to the approved change to include options 

to prevent administrative closure of outstanding orders lacking MRA. One of the options 

provided under ADC 1343 is the use of system generated MRAs as described in this change. A 

system generated MRA is the same as a regular MRA but created and transmitted by DAAS 

based on a receipt transaction. This process is available to all DoD Components and can only 

be used when requested.

c. Approved Change in Detail:

(1) To comply with DoDM 4140.01 Volume 5 Delivery of Materiel, DoD 

Component systems will transmit images of receipts to DAAS for materiel shipped from the 

wholesale level for:

(a) Lateral redistributions and depot level reparables that have been 

directed by the Inventory Control Point (ICP) or integrated materiel manager,

(b) Organic or commercial items shipped directly from maintenance.

(c) Receipts that have been performed internally by Component personnel 

within a Component AIS without processing a receipt transaction to the owner through DAAS. 
Attachment, ADC 1292

Page 3

(2) The DoD requirement to transmit an image receipt transaction will also apply 

to legacy systems using the legacy DIC DZK transaction. However, the system generated MRA 

process is not available for systems under legacy environments.

(3) The Component will send the image of receipt transaction to Routing 

Identifier Code (RIC) SGA.

(4) DoD policy requires Components to implement the MRA process in their 

respective AIS. However, not all Components AISs can transmit MRAs today. This change also 

allows DoD Components to create and transmit a system generated MRA using DAAS services. 

The use of system generated MRAs is an alternative for Components unable to generate MRAs

on their own systemically but still need to comply with MRA policy.

(a) To use this process, Components will transmit the original or image of 

receipt transaction and cite RIC SGA (DAAS) (qualifier ZD in the 2/N101/210 segment) as party 

to receive copy (qualifier PK in the 2/N106/210 segment). The Component will use another loop 

to identify the RIC destination for the MRA as Party to Receive Reports (qualifier ZD in the 

2/N101/210 segment). DAAS will then create and transmit the MRA based on the image of 

receipt transaction.

(b) System generated MRAs comply with the MRA requirements 

documented in the DLM 4000.25, Chapter 10, Materiel Receipt Acknowledgement (Reference 

2.d.) and with the MRA administrative closeout procedures. The expectation is for DoD 

Components using system generated MRAs to transmit the appropriate receipt (original or 

image) transaction to DAAS in real time. This will enable DAAS to transmit the system 

generated MRAs in compliance with the time standards in Chapter 10.

(c) System generated MRAs will not happen unless the DoD Component 

directs DAAS to do so via the receipt transaction. 

(5) This change revises the DLMS 527R Receipt Implementation Convention (IC) to 

add the necessary DLMS notes and authorize transmission of images of receipt to DAAS as required 

in Reference 2.b. See Enclosure 1 for additional details. 

(6) Lastly, this change authorizes DAAS to use an image of a receipt transaction 

required in Reference 2.b. to calculate the LRT when the original receipt or the MRA are not 

available. LMARS captures and reports LRT within the 12 logistics pipeline segments

(Reference 2.e.). Each of the 12 pipeline segments captures unique logistic events, starting at 

Segment 1 Requisition Submission Time. Segment 12 is currently limited to the DLMS 527R 

MRA (legacy DIC DRA/DRB). To improve LMARS capabilities to calculate LRT, this change 

allows DAAS to expand receipt reporting in LMARS and capture additional receipt timestamps 

contained in the receipt image transactions when the original MRA is not available. 

d. Revisions to Defense Logistics Manuals:

(1) Update DLM 4000.25, Volume 2, Chapter 13, as shown in Enclosure 2

(2) Update DLM 4000.25, Volume 2, Chapter 10, as shown in Enclosure 2
Attachment, ADC 1292

Page 4

(3) Update DLM 4000.25, Volume 6, Chapter 4, Pipeline Measurement

e. Approved Transaction Flow: For the system generated MRAs, the following 

transaction flow applies:

(1) The DoD Component (originator) performs the receipt process internally 

within its respective warehousing system. The system will transmit the original or image 

transaction to RIC SGA with the information corresponding to the materiel receipted. The 

transaction must indicate the ICP/storage activity that will receive the MRA. The Component 

may use an original or image of the receipt to request a system generated MRA. 

(a) DAAS will create and route the system generated MRA to the 

applicable ICP only when the originator indicates SGA in the N101 segment and a second loop 

indicating the RIC where the MRA will be directed. This will allow the Components to have full 

control when the system generated MRAs are used or not.

(b) The receipt image transaction will feed several systems to include the 

Integrated Data Environment (IDE)/Global Transportation Network (GTN) Convergence (IGC), 

and LMARS when applicable. 

(2) DAAS will use the information in the image transaction to create a system 

generated MRA and transmit accordingly. 

f. Alternatives: Submit MRA transactions per existing DoD Policy/Procedures

4. REASON FOR CHANGE: Align receipt business rules in DLM 4000.25 with 

DoDM 4140.01, Volume 5.

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Provides greater visibility for receipts performed internally by DoD 

Components in their respective warehousing systems in compliance with DoDM 4140.01 Vol 5. 

b. Disadvantages: None.

6. ESTIMATED TIMELINE/IMPLEMENTATION TARGET: There are several factors in 

this change that allow separate target implementations. 

a. The requirements for DoDM 4140.01 Volume 5 as well as the LMARS changes will 

take effect upon approval. Components must review and plan for implementation at the earliest. 

Components will also coordinate with DAAS to ensure the image transaction can be processed 

accordingly. The target implementation should not exceed 5 years from approval. 

b. With regards to the system generated MRAs, the target implementation correlates 

with ADC 1343. Components that are not able to submit MRAs are highly encouraged to 

implement this part of the change as soon as possible. By doing so, the system generated MRAs 

will significantly reduce outstanding orders awaiting receipt acknowledgements, therefore, 

avoiding the automatic close-out procedures. 
Attachment, ADC 1292

Page 5

c. US Navy Ordnance Information System (OIS) reports implementation of this PDC 

will require significant effort and will be completed no later than 2027, based on changes to 

Naval Operational Supply System (NOSS) or recoding, whichever comes sooner.

7. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: There are no known estimated savings or cost 

avoidance because of this change. However, DoD Components that implement the system 

generated MRAs procedures could potentially see significant savings in MRA implementation 

costs. 

8. IMPACT: 

a. New/Changes Data Elements: No impact to DLMS data elements.

(1) Automated Information Systems (AIS): DoD Component AISs (DLMS 

and Non-DLMS compliant) must transmit images of receipts to DAAS for relevant receipts as 

stated in DoDM 4140.01 Volume 5. Impacted systems include but are not limited to the DLA 

Distribution's Warehouse Management System, Logistic Modernization Program (LMP), Navy 

Enterprise Resource Planning (ERP), and Defense Property Accountability System (DPAS) and 

others. 

(2) Defense Automatic Addressing System (DAAS):

(a) DAAS will route using Communication Routing Identifier

(COMMRI) RUE0ZZH. 

(b) When the original or image of receipt transaction (N101=SGA, and 

N106=PK) is received, DAAS will translate it into the MRA/DRA transaction as applicable and 

transmit to the party to receive report. Under DLMS, the system generated MRA will be routed 

to the ICP cited in the second loop under the 2/N101/210 segment.

(c) For LMARS, DAAS will use image of receipt timestamps when the 

original MRA is not available to calculate LRT segments as necessary. 

9. Non-DLM Publications: 

a. Update reference (p) in the DoDM 4140.01, Volume 5, Delivery of Materiel to the 

DLM 4000.25, Defense Logistics Management Standards (DLMS). 

b. DoD Components may need to update any local procedures as necessary to reflect the 

changes documented in this change.
Attachment, ADC 1292

Page 6

10. PROPOSED DLMS CHANGE (PSC) 1292RESPONSE/COMMENT 

RESOLUTION:

Component Response/Comment Disposition

1. DLA Concur with Comment.

Comments:

1. Does this mean they will now be required to submit the 

image of receipt transaction regardless of where they 

obtained the materiel? And, if they obtained materiel 

outside of DLA, would the MRA still flow to EBS and 

look the same? Recommendation: If materiel was 

obtained outside of DLA's supply chain, it should be noted 

but not submitted as a system generated MRA via the 

image of receipt transaction. (known issue in which the 

Navy submits MRA's systemically when receiving 

materiel laterally.)

2. DLA Distribution DSS and WMS processes a 527R 

MRA for all items received. In addition, for controlled 

items, the DTEB 856A is received and DLA responds to 

this at time of transaction receipt, as well as physical 

receipt to the shipper. I do not know why DLA Warehouse 

systems are listed as impacted within the PDC, nor do I 

understand why DEDSO is adamant that DLA Warehouse 

systems should request DAASC forward all the MRA's.

Resolved as noted.

DEDSO Response.

1. Noted. (c) System 

generated MRAs will not 

happen unless the DoD 

Component directs DAAS 

to do so via the receipt 

transaction.

2. Noted. This change 

documents an alternative for 

DLA to provide MRAs in 

lieu of making systems 

changes to DSS/WMS. 

1. Navy Concur with Comment.

Comments:

Ordnance Information System (OIS) reports 

implementation of this PDC will require significant effort 

and will be completed no later than 2027, based on 

changes to NOSS or recoding, whichever comes sooner.

As noted.

DEDSO response.

Noted in paragraph 6 above,

6. ESTIMATED 

TIMELINE/IMPLEMENT

ATION TARGET.

2. Air Force Concur with comments.

Comment:

1. Recommend changing this sentence from 

"Contributing to this is the lack of an MRA that would 

close out the order" to "Contributing to this is the lack of 

an MRA that would close out the shipment'. 

2. Add this sentence: DoD Components will have the 

option to allow system generated MRAs to be forwarded 

to shipment consignees.

3. Change "DLA Warehousing System" to read "DLA 

Distribution's Warehouse Management System"

4. There should be a mention of Defense Reutilization 

and Marketing Service (DRMS) along with the inventory 

control points (ICP) and storage activities here. (Page 10 

(Enclosure 2))

5. D035 has been designed to automatically send a MRA 

transaction based on processing a receipt transaction for 

20 plus years. It appears ILSS is also doing the exact 

same thing. 

As noted. 

DEDSO response.

1. Revised in ADC 1292. 

2.Revised in ADC 1292.

3.Revised in ADC 1292.

4.Noted. DLA Disposition 

Services use the Turn-in 

Receipt Acknowledge 

(TRA) and not the MRA. 

5. Noted in paragraph 6 of 

ADC 1292.
Attachment, ADC 1292

Page 7

3. US Army Concur without Comment As noted.

USARMY National Level -

HQ AMC G-3 Concurs on 

10/26/21 (unofficial 

response)

4. USMC Concur without comment. As noted.

5. DAAS Concur with comments.

This PDC directs DAAS to route the MRAs to the 

COMMRI RUEOZZH. That COMMRI is specifically set 

up to route transactions to LOTS. Therefore, there are no 

changes required for LOTS. Since LMARS and MRA pick 

up data from LOTS, these MRAs will be in both systems. 

Consequently, if DMARS routes these to RUEOZZH as 

described, the PDC will work correctly.

As noted.

DEDSO Response.

ADC 1292 revised to reflect 

this comment.

6. USTRANSCOM N/A N/A

7. GSA None. None noted.

8. ODASD (LOG) Not applicable. Not applicable.
Enclosure 1, ADC 1292

Page 1

Enclosure 1

Revise DLMS 527R Receipt Implementation Convention as shown. 

Changes are identified by bold italics and deletions by single strikethrough text

DS# Location DLMS 527R Revisions for Materiel Receipt Reason

1. DLMS 

Introductory 

Note

Add PDC 1292 to DLMS Introductory note 7:

- PDC 1292, Images of Receipt Transaction for DAAS and System 

Generated Materiel Receipt Acknowledges (MRA) 

(Supply/MILSTRAP).

To identify DLMS 

change included in 

the DLMS IC.

2. 1/BR06/020 Add new DLMS note 3 for existing qualifier FI

FI File

DLMS Note:

1. Authorized for Air Force and DSS use with PIC Nuclear WeaponsRelated Material (NWRM) unique Item Tracking (UIT). Use with BR02 

Code D4 to identify a receipt image transaction where the original

receipt transaction has bypassed the normal DAAS transaction flow. All 

transaction set recipients must use extreme caution to ensure individual 

transactions with this code do not process as action documents which 

affect accountable records. Must use with 2/N101/210 code ‘KK’ and 

2/N106/210 code ‘PK’. There will be no 2/N106/210 code ‘TO’ for this 

transaction. Refer to ADC 347.

2. Authorized for Air Force contractor inventory control point (CICP) 

use to provide an image of the MRA or TRA to the Air Force 

accountable property system record (APSR) to update the inventory 

intransit balance. Refer to ADC 1238.

3. Must use when transmitting an image of receipt transactions to 

DAAS as required by DoDM 4140.01 Volume 5. Refer to PDC 1292.

To document 

requirement for 

DoDM 4140.01, 

Volume 5, Materiel 

Receipt.

3. 2/N101/210 Add new DLMS Note 7 for existing qualifier ZD:

ZD Party to Receive Reports

DLMS Note:

1. Use in MRA transactions to cite additional organizations requiring 

MRA.

2. Use in Navy Commercial Asset Visibility (CAV) receipts to identify 

the party to receive report. CAV expresses party to receive report as a 

DoDAAC (N903 code 10). CAV use is an authorized DLMS migration 

enhancement. See DLMS introductory note 5g.

3. Used between Navy and DLA for Navy MRAs submitted directly to 

other Component Source of Supply, so DLA will be able to support 

follow-on actions on behalf of the Navy under a DLA industrial activity 

support agreement. Refer to ADC 377.
Enclosure 1, ADC 1292

Page 2

DS# Location DLMS 527R Revisions for Materiel Receipt Reason

4. Use in receipt transactions to identify additional organizations 

requiring notification of receipt when the receipt is related to a PQDR 

exhibit.

5. Disposition Services Field Office uses with disposition services turnin receipt acknowledgement (TRA) transaction to identify the DoDAAC 

of the recipient of TRA transaction. This will be the DoDAAC of the 

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

Refer to ADC 1111.

6. For Air Force GFP accountability, use to identify the Air Force 

program manager in the accountable property system of record (APSR) 

when the contractor inventory control point (CICP) must transmit an 

image of this transaction to a separately maintained property system. 

Must identify the program manager by RIC. If the program manager 

DoDAAC does not have an assigned RIC, use the generic Air Force 

GFP APSR RIC with 2/N106=PK and use a second iteration of the N1 

loop (repeating Code ZD without 2/N106=PK) to provide the program 

manager DoDAAC. Use in conjunction with N106 Code PK to provide 

an image of the MRA or TRA transaction (image is identified by 

1/BR06/020 Action Code FI) to update inventory intransit balance in the 

APSR associated with the CICP (identified in 1/N101/070 Code Z4). 

Refer to ADC 1238.

7. Use to provide the image of receipt transactions to DAAS as 

required by DoDM 4140.01 Volume 5. Authorized DLMS 

enhancement, see introductory DLMS Note 5.g. Refer to PDC 1292.

8. Must use when requesting a system generated MRA. When 

requesting a system generated MRA via the image of receipt 

transaction, the originating system will need a second loop to identify 

the RIC where the MRA should be directed. Refer to PDC 1292.

Supports the DoDM 

4140.01, Volume 5, 

requirement for a 

Materiel Receipt

image transaction.

Allows Components 

to cite the recipient 

of a system 

generated MRA.
Enclosure 1, ADC 1292

Page 3

DS# Location DLMS 527R Revisions for Materiel Receipt Reason

4. 2/N106/210 Add new DLMS Note 5 to existing qualifier PK and renumber existing 

Note 5 as Note 6, and update DLMS Note to existing qualifier TO:

PK Party to Receive Copy

1. Use when appropriate to send an information copy of the transaction 

to a Component UIT registry. For use with N101 Code KK.

2. Authorized DLMS enhancement for Air Force and DSS use with PIC 

NWRM UIT. For PIC UIT, must use in conjunction with 2/N101 Code

KK and 1/BR06/20 Action Code FI and cite the applicable Routing

Identifier in 2/N103.

3. Use to provide a copy of the receipt to Product Data Reporting and 

Evaluation Program-Automated Information System (PDREP-AIS) for 

PQDR exhibit tracking when the PQDR Report Control Number

(RCN) is included. For use with N101 Code ZD and DoDAAC N45112. 

Refer to ADC 1007.

4. For Air Force GFP accountability, use with N101 Code ZD to provide 

an image of an MRA or TRA to the APSR. Do not use N101 Code TO 

with Air Force CICP MRA and TRA image transactions to the APSR.

5. Use to provide an image of receipt transactions to DAAS as required 

by DoDM 4140.01 Volume 5. 

6. Must use when requesting a system generated MRA. Use in 

combination with 1/BR06/020 Action Code FI, N101 Code ZD, and 

N106 Code PK. Refer to PDC 1292. 

57. Except as noted above, Authorized DLMS enhancement as noted 

above for specific implementations; see introductory DLMS note 5g. 

For all other applications, see introductory DLMS note 5a.

TO Message TO

DLMS Note:

Must use with the appropriate 2/N101/210 code to indicate the 

organization cited in N104 is receiving the transaction, except when 

N106 Code PK is authorized for use to provide information copies or 

images of the transaction to the party to receive copy, and TO is not 

required.

Supports the DoDM 

4140.01 Volume 5

requirement for a 

Materiel Receipt

image transaction.

Allows Components 

to cite who will 

receive the system 

generated MRA.
Enclosure 2, ADC 1292

Page 1

Enclosure 2

Defense Logistics Manual (DLM) 4000.25 

A. Volume 2, Supply Standards and Procedures

Make the following changes to Volume 2. Additions are shown by red bold italics

Chapter 13, Materiel Receipt 

C13.1. GENERAL

C13.1.1. Purpose

C13.1.1.1. Wholesale Level Receipt Processing. This chapter prescribes standard 

procedures for processing wholesale materiel receipt information between inventory control 

points (ICP) and storage activities, and between losing inventory managers (LIM) and gaining 

inventory managers (GIM). The procedures require expeditious showing of assets in the 

property accountability records and related financial accounts. Documentation covering 

consignment of materiel to storage activities is prescribed in other DoD and DoD Component 

regulations. These documents are used, together with information developed by inspection and 

classification procedures, as source data for documenting transactions in terms of this manual. 

The distribution of disbursement, procurement, and transportation documentation by storage 

activities is also governed by existing regulations and is, therefore, not a consideration here.

C13.1.1.2. Image of Receipt Transactions for Wholesale Assets. As required by 

DoDM 4140.01, Volume 5, Delivery of Materiel, DoD Component must transmit the image of 

receipt for materiel received from wholesale where the Component does not need to report the 

receipt of assets to an external automated information system (AIS) via DAAS. This 

requirement applies to lateral redistribution and depot level reparable orders directed by the 

ICP or integrated materiel manager as well as organic or commercial items shipped directly 

from maintenance.

Chapter 10, Materiel Receipt Acknowledgement

Preceding text not shown

C10.11. Use of System Generated MRAs. When appropriate, DoD Components may opt to 

use DAAS services to create and transmit a system generated MRA on their behalf. DoD 

policy requires DoD Components to implement the MRA process in their respective AIS. The 

use of system generated MRAs is an alternative for Components unable to generate MRAs on 

their own systemically.

C10.11.1. The use of system generated MRAs allow prompt submission of the 

receipt acknowledgement when a system is otherwise unable to transmit an MRA as required 

by this chapter. The Component must transmit the image of receipt transaction in real time to 

ensure the system generated MRA complies with the MRA time standards. The use of a 
Enclosure 2, ADC 1292

Page 2

system generated MRA follows the current policies and procedures for MRAs and ensures 

prompt submission of a receipt acknowledgement to the appropriate organization.

C10.11.2. DAAS System Generated MRA Procedures

C10.11.2.1. To authorize DAAS to transmit a system generated MRA on 

behalf of a Component, the supply system must transmit the receipt or the receipt image to 

DAAS and identify the RIC ICP where the MRA should be directed.

C10.11.2.2. The transaction must include the DAAS Routing Identifier Code 

(RIC) SGA as party to receive copy and the organization to receive the MRA as party to 

receive report. When using the image of a receipt to request a system generated MRA, the 

originating system must use a second loop to indicate the RIC MRA destination.

C10.11.2.3. The combination of the party to receive copy and party to receive 

report will serve as the authorization for DAAS to create and transmit the MRA to the 

appropriate destination.

C10.11.2.4. DAAS will not transmit a system generated MRA unless 

authorized by the Component. 

B. Volume 6, Logistics Systems Interoperability Support Services

Make the following changes to Volume 6. Additions are shown by red bold italics

Chapter 4, Pipeline Measurement

Preceding text not shown

C4.6.2.12. Logistics Pipeline Segment 12, “Receipt Take-Up Time” is the time 

between consignee receipt or “tailgate” date and the record posting date in the MRA transactions 

527R/DRA/DRB. A receipt or the image of receipt may also be used to calculate this segment 

when the MRA is not available.