DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

MEMORANDUM FOR RECORD

SUBJECT: Administrative Approved Defense Logistics Management Standards Change 1463A, 

Update Retail Transportation and Supply Receipt and Acknowledgement Process 

(Transshipment) in the DLMS Environment (Supply) 

The attached approved administrative change is effective immediately. This 

administrative change does not change or eliminate any existing procedures or add any new 

procedures. This administrative update corrects a reference identified in paragraph 2a of ADC 

1463. Administrative ADC 1463A replaces ADC 1463 in its entirety. 

Addressees may direct questions to Dr. Gail Fuller, e-mail: DEDSO.Supply@dla.mil. 

Others must contact their designated PRC representative available at https://www.dla.mil/

Defense-Data-Standards/Committees/Contacts/. 

 

 

Sarah Winegardner

Director, Defense Enterprise Data 

Standards Office

Attachment:

As stated

cc:

OUSD(C)

DLA J6DS
Attachment 1, MFR Admin ADC 1463A 

Page 1 

Memorandum For Record

Administrative Approved Defense Logistics Management Standards Change 1463A, 

Update Retail Transportation and Supply Receipt and Acknowledgement Process 

(Transshipment) in the DLMS Environment (Supply) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: Defense Logistics Agency (DLA) J345, Transportation Policy, 

Wayne Howard, email: wayne.howard@dla.mil. 

b. Functional POC: DLA J345, Asset Management (In-transit Visibility and 

Accountability), David Stieger, email: david.stieger@dla.mil. 

2. REASON FOR CHANGE: 

a. Bottom Line Up-Front: 

(1) This change incorporates several qualifiers required to identify Defense 

Logistics Management Standards (DLMS) 940R Materiel Release transactions for the sole 

purpose of requesting transportation only services (better known as transshipment) from DLA. 

In addition, this change will discontinue the use of Distribution Code 111 for transshipments. 

Today, DoD Components use materiel release transactions with distribution code 111 to 

transship materiel. However, Distribution Code 111 doesn’t distinguish a transshipment action 

from a standard Materiel Release Order (MRO). Improper identification causes unnecessary 

denials directly affecting the warehouse performance metrics. This change is co-dependent with 

references 10.b. (ADC 1460) and 10.c. (ADC 316). 

(2) This change replaces Approved DLMS Changes (ADC) 316 and 316B in 

their entirety (reference 10.d. and 10.f.).

(3) This corrective ADC replaces ADC 1463 in its entirety. It updates the 

references in section 2.

b. Background: 

(1) ADC 316 and 316B were established to enable the movement of cargo from 

retail activities using wholesale transportation. However, the lack of distinct qualifiers in the 

transaction made this process inefficient and is causing unnecessary inventory record 

adjustments. In addition, these changes will not be implemented by DLA Warehousing 

Management System (WMS). To continue using wholesale transportation from DLA, impacted 

retail systems must implement this change.

(a) ADC 316A - USAF Requirements for Item Record Data and Unique 

Item Tracking (UIT) using the Materiel Release (DLMS Implementation Convention 940R) under 

Transportation and Supply Receipt and Acknowledgement Interchange provides the capability to 

transfer shipment data to the Integrated Logistics Support System (ILSS) - Cargo Movement 

Operations System (CMOS) interface. It is important that this process continues as programmed. 
Attachment, MFR Admin ADC 1463A 

Page 2 

References pertaining the use of the distribution code 111 should be replaced with the 

appropriate X12 references. 

(b) ADC 316C - Revise DLMS Implementation Convention 940R 

Material Release and DLMS Implementation Convention 945A Material Release Advice, to 

Support Unique Item Tracking for Air Force Positive Inventory Control (PIC) under the Retail 

Transportation and Supply Receipt and Acknowledgement Interchange authorizes the generation 

of an information copy of the 940R and 945A transactions (Distribution Code “111”) for a 

specific Air Force PIC Nuclear Weapons-Related Materiel (NWRM) need. This change utilizes 

the established standardized interchange between retail transportation and supply using EDI 

transactions, specifically the Material Release, 940R, and Material Release Advice 945A. As 

stated in the change, DAAS will send image transactions of the DLMS 940R and/or DLMS 

945A as applicable to other parties when indicated in the N1 segment. 

(c) h. ADC 316D - Air Force-Unique Document Identifier Code 

Mappings to 940R under the Retail Transportation and Supply Receipt and Acknowledgement 

Transactions incorporates several DLMS notes to further explain that cancellation request for 

assemblages will be done at the lead document number. Notes will be updated as necessary to 

align with the current process. 

(2) ADC 316B - New Distribution Code (111) for the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange for the 940R and 945A established 

Distribution Code 111 to pre-position actual arrival of cargo from a co-located service owned 

storage activity into DLA. The code was necessary to support MILS customers. However, the 

code itself is not sufficient to prevent from transshipments being denied as they appear to be the 

same as a standard MRO. Currently this is an issue affecting US Marines whenever they inquiry 

about an outstanding pre-positioned actual arrival of cargo and the shipment is still pending 

check-in. In response, DLA and US Marines submitted this change to standardize 

transshipments using elements only available in a variable length environment and ensure the 

inquiry process for transshipment does not result in denials. Upon approval of this change, 

distribution code 111 will no longer be authorized for use. Defense Enterprise Data Standards 

Office (DEDSO) will be adding/updating the appropriate implementation conventions to ensure 

transshipments are properly identified and prevent any further denials. 

(3) This change, ADC 1460 - Pre-position Release Orders, incorporates 

qualifiers RA - Release Against Assortment and CR - Change to Release to enable materiel 

owners to pre-position release orders ahead of upcoming inbound shipments. This process will 

help expedite the issue of materiel from receipt. Once approved this change enables materiel 

owners to leverage these qualifiers in combination with a new transaction type code when 

requesting the movement of cargo from retail using wholesale transportation services. The 

combination of the new transaction type code and the qualifiers updates in ADC 1460 will help 

prevent further confusion with standard MROs and prevent the request from being rejected prior 

to the cargo check-in. 

3. CHANGE IN DETAIL: 

a. Technical Details: 
Attachment, MFR Admin ADC 1463A 

Page 3 

(1) Under DLMS 940R Materiel Release (W0506/0200): 

(a) Add a new transaction type code CU - Cargo Release Order. This 

new qualifier will identify the transaction as a transportation of cargo only release order and will 

avoid further confusion with standard MROs. This new type of release order is not a balance 

affecting action therefore, there will be no changes to inventory records. For serially managed 

items, the retail site must provide all serial numbers and/or UII associated with the cargo. 

(b) Add a new transaction type code CC - Cargo Release Cancellation. 

This new qualifier will allow retail sites to submit a request for cancellation of a previously 

submitted cargo release order. This new type of release order is not a balance affecting action 

therefore, there will be no changes to inventory records. For serially managed items, the retail 

site must provide all serial numbers and/ or UII associated with the cargo.

(2) Under DLMS 945A Materiel Release (W0611/0200): 

(a) Add a new transaction type code CJ - Cargo Release Confirmation. 

The new qualifier will enable a transportation/warehousing system of record to send 

confirmation of shipment in response to a cargo release order. This new type of confirmation is 

not a balance affecting action therefore, there will be no changes to inventory records. 

(b) Add a new transaction type code 56 - Cargo Release Denial. The new 

qualifier will help distinguish a denial to a cargo release order vs standard denial. This new type 

of denial is not a balance affecting action therefore, there will be no changes to inventory 

records. The new qualifier will allow a transportation/warehousing system of record to deny a 

cargo release order when any of the following conditions apply: 

1. The originator of the cargo release order submitted a request for 

cancellation via the DLMS 940R Materiel Release transaction. 

2. After 45 days, cargo was not checked-in by the transportation 

or warehouse system of record. 

3. The transportation/warehousing system of record cannot move 

forward with the request. The appropriate management code is required to convey the reason for 

denial. 

(3) The new transaction type codes CU and CC will be used in combination with 

qualifiers RA - Release Against Assortment or CR - Change to Release as necessary to ensure 

the transaction is not processed until the transportation/warehousing system of record process a 

cargo check-in. See reference 10.c. for details. 

(4) Discontinue the use of Distribution Code 111 Inter-Component use for Retail 

Transportation and Supply Receipt and Acknowledgement Interchange. This code was 

originally established to support the transportation of cargo from retail as stated under reference 

10.e. When DoD Components transport cargo via this process, the materiel is not at a wholesale 

storage activity and no accountable record exist. The retail storage activity initiating the request 

retains custodial responsibility until the cargo is surrender to transportation. The code itself 
Attachment, MFR Admin ADC 1463A 

Page 4 

doesn’t differentiate a standard MRO from a transportation of cargo request leading to potential 

denials and inaccurate inventory adjustments.

(5) Update status code BQ definition under Appendix 7.16. Status code BQ will 

help transportation/warehousing system of records respond to unsuccessful cancellation request 

from the retail site. See section 6.a. for the new definition. 

b. Revised Transaction Flow: 

(1) DoD Component transmit a DLMS 940R MRO, W0506/RC/0200, 

W0508/RA/0200 to indicate the need for transportation of cargo. The transaction will remain on 

hold in the transportation/warehousing system of record awaiting check-in. 

(2) The transportation/warehousing system of record will hold inbound cargo 

release orders waiting for cargo until one of the reasons below applies: 

(a) The originator of the cargo release order submitted a request for 

cancellation via the DLMS 940R Materiel Release transaction. 

(b) After 45 days, cargo was not checked-in by the 

transportation/warehouse system of record. 

(c) The transportation/warehousing system of record cannot move 

forward with the request. The appropriate management code is required to convey the reason for 

denial. 

(3) Upon check-in, Wholesale will transmit a DLMS 945A Materiel Release 

Confirmation (MRC), W0611/NO/0200, W1201/UR/0200, and the appropriate status code (BA) 

to retail as confirmation. 

(4) For inquiries, the DoD Component will transmit a DLMS 940R MRO, 

W0506/NB/0200, W0507/82/0200 to wholesale. In response, wholesale will transmit either an 

image copy of the most recent action (checked-in, on-hold, confirmation, denial) or a DLMS 

945A with the appropriate status code back to retail. Inquiries will be done at the lead document 

number for assemblages. 

(5) Retail may submit a request for cancellation of a previously submitted cargo 

release order via the DLMS 940R Cargo Release Cancellation transaction. In response, the 

transportation/warehousing system of record will transmit a DLMS 945A Cargo Release Denial 

transaction to confirm the cancellation was successful. Cargo release orders may only be 

cancelled before checked in. When the cancellation is not successful, the transportation and/or 

warehousing system of record will reply via the DLMS 945A Cargo Release Denial, status code 

BQ. 

(6) Once the transportation has been arranged for the cargo, wholesale will 

transmit a DLMS 945A as confirmation. The cargo will then be released to transportation.
Attachment, MFR Admin ADC 1463A 

Page 5 

4. IMPLEMENTATION TARGET: The new DLA Warehousing Management System 

(WMS) will not support the Distribution Code 111. DoD Components who need these services 

from wholesale must coordinate with DLA and implement as soon as possible. The 

transportation of cargo only will not be available under legacy environments. DAAS will plan 

for implementation within 180 days from approval of this change.

5. TECHNICAL IMPACT: 

a. Additions or Changes to Data Elements: 

(1) Incorporate qualifier CU and CC in the DLMS 940R Materiel Release 

transaction mapping as stated in enclose 2. 

(2) Incorporate qualifiers CJ and 56 in the DLMS 945A materiel release advice 

transaction mapping as stated in enclosure 2. 

b. Automated Information Systems (AIS): 

(1) Retail sites and transportation systems currently using distribution code 111 

will be impacted. 

(2) United States Transportation Command (USTRANSCOM) will be impacted 

with the cancellation of ADC 316B. 

(3) USTRANSCOM systems Integrated Development Environment/Global 

Transportation Network (IGC) and Global Air Transportation Execution System (GATES) will 

be impacted and will plan for implementation. All other USTRANSCOM systems are 

unaffected by this change.

(4) Defense Property Accountability System (DPAS) and WMS will be 

impacted. 

(5) Retail sites using DLA WMS wholesale transportation must coordinate with 

DLA and schedule to implement as soon as possible but prior to WMS go live. DLA WMS will 

not be implementing Distribution Code 111. 

c. Defense Automatic Addressing System (DAAS): 

(1) Incorporate the new data elements and qualifiers as stated in enclosure 2 in 

the appropriate transaction mapping. 

(2) DAAS will need to perform an impact assessment on routing rules and 

identify any necessary cleanup because of this change. 

(3) ADC 316A - USAF Requirements for Item Record Data and Unique Item 

Tracking (UIT) using the Materiel Release (DLMS Implementation Convention 940R) under 

Transportation and Supply Receipt and Acknowledgement Interchange provides the capability to 

transfer shipment data to the ILSS – CMOS interface. It is important this process continues as 
Attachment, MFR Admin ADC 1463A 

Page 6 

documented. Any references to distribution code 111 should be replaced with the appropriate 

X12 reference. 

(4) ADC 316C - Revise DLMS Implementation Convention 940R Material 

Release and DLMS Implementation Convention 945A Material Release Advice, to Support 

Unique Item Tracking for Air Force Positive Inventory Control (PIC) under the Retail 

Transportation and Supply Receipt and Acknowledgement Interchange authorizes the generation 

of an information copy of the 940R and 945A transactions (Distribution Code “111”) for a 

specific Air Force PIC NWRM need. This change utilizes the established standardized 

interchange between retail transportation and supply using EDI transactions, specifically the 

Material Release, 940R, and Material Release Advice 945A. As stated in the change, DAAS 

will send image transactions of the DLMS 940R and/or DLMS 945A as applicable to other 

parties when indicated in the N1 segment. 

6. PUBLICATION/POLICY IMPACT: 

a. Defense Logistics Manual (DLM) 4000.25: 

(1) Update Volume 3, Transportation, Chapter 2, Retail Supply and 

Transportation - Stock Shipments as shown in enclosure 1. 

(2) Update Volume 2, Appendix 7.16, Status Codes as shown in enclosure 1. 

b. Non-DLM 4000.25 Publications: none. 

7. ASSUMPTIONS: DLMS compliant systems will no longer use Distribution Code 111 upon 

approval of ADC 1463.

8. FINANCIAL IMPROVEMENT AND AUDIT REMEDIATION (FIAR), MATERIAL 

WEAKNESS, AND AUDIT-RELATED INFORMATION: 

a. Notices of Findings and Recommendations (NFR): None. 

b. Corrective Action Plan (CAP) References: None.

c. Other FIAR, Material Weakness, and Audit-Related Information: None.

9. END-TO-END TESTING REQUIREMENTS: None. 

10. REFERENCES: 

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

Volume 3.

b. ADC 1460 - Pre-positioned Release Orders, pending final approval. 

c. ADC 316 - Retail Transportation and Supply Receipt and Acknowledgement 

Transactions, signed 02/19/2009. 
Attachment, MFR Admin ADC 1463A 

Page 7 

d. ADC 316A - USAF Requirements for Item Record Data and Unique Item Tracking 

(UIT) using the Materiel Release (DLMS Implementation Convention 940R) under 

Transportation and Supply Receipt and Acknowledgement Interchange, signed 06/26/2009. 

e. ADC 316B - New Distribution Code (111) for the Retail Transportation and Supply 

Receipt and Acknowledgement Interchange for the 940R and 945A, signed 06/26/2009. 

f. ADC 316C - Revise DLMS Implementation Convention 940R Material Release and 

DLMS Implementation Convention 945A Material Release Advice, to Support Unique Item 

Tracking for Air Force Positive Inventory Control (PIC) under the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange (Supply/Transportation), signed 01/15/2010. 

g. ADC 316D - Air Force-Unique Document Identifier Code Mappings to 940R under 

the Retail Transportation and Supply Receipt and Acknowledgement Transactions 

(Transportation/Supply), signed 08/03/2010.

11. PROPOSED DLMS CHANGE (PDC) 1463 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition 

1. DLA Concur Acknowledged.

2. US Air Force Concur with comments

1. From the ILS-S understanding, the distribution code 

‘111’ was initiated to aid DLA Transaction Services to 

identify those DLMS 940R transactions from ILS-S which 

needed to be routed to CMOS via UDF. CMOS returns 

the distribution code ‘111’ in a UDF, which is converted 

by DLA Transaction Services to the DLMS 945A and then 

sent to ILS-S. ILS-S now assumes with the deletion of the 

distribution code ‘111’, that CMOS will either 

receive/send the DLMS 940R/945A transactions or DLA 

Transaction Services has a different rule in place to ensure 

these DLMS transactions are routed to/from CMOS 

UDFs. 

DEDSO Response:

1. Correct. Distribution code 

111 will no longer be 

available for use. DEDSO 

reached out to 

USTRANCOM and CMOS 

doesn’t use the distribution 

code 111.

CMOS does still utilize the 

DAAS translation/conversion 

services between X12 and 

UDF for the 940R/945A 

exchange with Supply. That 

DAAS translation capability 

will need to remain in place 

for the 940R/945A exchange 

to work successfully.

CMOS does not do anything 

with the Distribution Code 

that Supply sends in the 940R 

other than store it in the 

database, display it to the user 

and send it back in the 945A 

response. There is no 

business logic built in CMOS 

to take the distribution codes 

into consideration when 

processing the cargo for 

transportation purposes. That 

is why we have indicated 
Attachment, MFR Admin ADC 1463A 

Page 8 

Component Response/Comment Disposition 

there is no impact to CMOS if 

Distribution Code 111 is 

removed. If Supply does not 

send the 111 code, CMOS 

will not store it and send it 

back in the 945A. If Supply 

sends the 111 code, CMOS 

will return it back in the 

945A.

3. US Army No response DEDSO Response:

No response represents 

concurrence per PDC 1463

change memo.

4. USMC Concur as written Acknowledged

5. US Navy Concur with comments: 

This one has no impact to current Navy ERP business. 

If/when Transportation is implemented in ERP+, this 

should be reviewed for implementation.

Acknowledged comments of 

Navy ERP implementation 

will be reviewed. 

6. DAAS Concur Acknowledged.

7. USTRANSCOM Concur without Impact Acknowledged.
Enclosure 1, Admin ADC 1463

Page 1 

Enclosure 1 

A. Revised DLM 4000.25, Volume 3, Chapter 2, Retail Supply And Transportation Interchange 

– Stock Shipments 

Additions are shown in red bold italics. Deletions are shown by double strikethrough text. 

C2. CHAPTER 2 

RETAIL SUPPLY AND TRANSPORTATION 

INTERCHANGE – STOCK SHIPMENTS

C2.1. GENERAL. This chapter provides procedures for use in retail transportation and 

supply processes related to the transportation in-check of cargo from a supply 

warehouse and subsequent outbound shipment by the servicing transportation activity. 

These procedures create a virtual warehouse between supply and transportation by 

standardizing a supply-transportation interchange and provide in-transit visibility and 

accountability of government assets shipped in the Defense Transportation System 

(DTS). The transactions provide users with an electronic method of obtaining shipment 

data and status on specific line items upon inquiry.

C2.2. BACKGROUND. This section documents a standardized interchange of 

information between retail transportation and supply through the use of Electronic Data 

Interchange (EDI) transactions. For materiel requirements processed using Military 

Standard Requisitioning and Issue Procedures (MILSTRIP) legacy 80 record position 

transactions and Defense Logistics Management Standards (DLMS) procedures, the 

standardized interchange employs DLMS 940R, Materiel Release and DLMS 945A, 

Materiel Release Advice. This standard provides retail supply systems the ability to preposition release order data in transportation, to submit follow-up status messages to 

transportation requesting updated shipment status, and to submit cancellation requests 

to transportation for release orders already turned over to transportation for shipment 

planning and execution. The standard also provides retail transportation systems the 

capability to provide supply status messages to supply, to provide cancellation response 

messages to supply, and to submit materiel release confirmation messages to supply 

when the materiel has shipped.

C2.3. STOCK SHIPMENT PROCEDURES

C2.3.1. Supply and Transportation Systems. There are six Automated Information 

Systems (AISs) that use this standardized interchange between retail transportation and 

supply activities. They are the Defense Medical Logistics Standard Support (DMLSS), 

Global Combat Support System – Marine Corps (GCSS-MC), USAF Expeditionary 

Combat Support System (ECSS), and the Integrated Logistics Solution—Supply (ILS—

S; formerly Standard Base Supply System (SBSS)), which represent the supply 
Enclosure 1, MFR Admin ADC 1463A 

Page 2 

systems for their respective business areas, and the Cargo Movement Operations 

System (CMOS), as well as the DLA Warehouse Management System 

(WMS)Distribution Standard System (DSS), which represents the transportation system. 

Systems other than the six systems above, planning to use these standardized 

interchange transactions to implement a similar capability must coordinate with the

Defense Enterprise Data Standards Office (DEDSO) prior to attempting to implement 

the interchange.

C2.3.2. Retail Supply Activity. This paragraph provides general procedures for 

retail supply activities related to the delivery of items to the servicing transportation 

activity for further shipment.

 C2.3.2.1. Pre-Positioned Release Order. For designated sSupply trading 

partners, must transmit a DLMS 940R Cargo Release Order (W0506/CU) in advance 

to the delivery of cargo. the Defense Automatic Addressing System (DAAS) will route

transmit copies of the DLMS 940R, Cargo Release Order Materiel Release 

Order/Disposal Release Order/Redistribution Order (Document Identifier Codes (DIC) 

A2_/A5_/A4_) transactions to the designated transportation system to be pre-positioned 

awaiting actual arrival of cargo from the supply warehouse.

 C2.3.2.1.1. For designated supply trading partners (currently limited to 

the SBSS—CMOS interface) the DLMS 940R, Materiel Release will be used to pass 

Federal Logistics Information System (FLIS) National Stock Number (NSN) item data 

(as identified in the 940R) that is not otherwise available to CMOS. This is an interim 

measure pending establishment of a FLIS interface.

 C2.3.2.1.2. For designated supply trading partners (currently limited to 

the SBSS—CMOS interface), the DLMS 940R, Materiel Release will be used to support 

the unique item tracking (UIT) program for Positive Inventory Control (PIC) nuclear 

weapon Related Materiel (NWRM). A unique item identifier (UII) and the associated 

serial number will be passed in the DLMS 940R for each item meeting the PIC NWRM 

program criteria. For legacy items where the UII has not been marked in accordance 

with Item Unique Identification (IUID) policy, the serial number alone will be passed. 

This is an interim measure pending transition to tracking by UII and associated IUID 

business rules/transactions. DLMS Volume 2, Chapter 3019, Procedures For Serially 

Managed Materiel Requiring Owner Visibility UIT Procedures applies (with 

exceptions as noted). Future CMOS releases will include the serial number/UII in the 

DLMS 945A, Materiel Release Advice transaction.

 C.2.3.2.1.3. For designated supply trading partners (currently limited to 

the SBSS—CMOS interface), an information copy (image) of the Materiel Release 940R 

will be used in support of Air Force PIC Fusion program data requirements. The routing 

of an additional information-only copy of the DLMS standard transactions (940R) is 

authorized for forwarding PIC Fusion data needed for the Air Force UIT registry. This is 
Enclosure 1, MFR Admin ADC 1463A 

Page 3 

a specific authorized use with unique identifiers to flag the transaction as information 

only.1

 C2.3.2.1.4. Item Unique Identification. For designated trading partners, 

when NSNs containing an IUID indicator Yes (Y), indicating that DoD IUID Supply 

Policy is required, the DLMS 940R Materiel Release must contain the UII and/or serial 

number for each item when available.2

 C2.3.2.1.5. Updated Pre-Positioned Release Order. In the event 

required UII and/or serial number information is not transmitted in the initial DLMS 940R 

to transportation, an updated DLMS 940R citing the value R at 1/W0502/0200 must be 

sent prior to sending the materiel to transportation. The lack of serialization data in 

the transaction may result in a denial. 

 C2.3.2.1.6. When authorized by the trading partners, the materiel 

release may include identification of a pre-designated carrier and the carrier account 

number for the applicable shipment. When provided, this information will be 

perpetuated to the materiel release confirmation.3

 C2.3.2.2. Delivery and In-Check. The supply activity will make local 

deliveries of the items to be shipped to the servicing transportation activity. The line 

items will be in-checked by the transportation activity based on the cargo and the 

documentation received from the supply activity.

 C2.3.2.3. Shipment Documentation. The materiel for shipment will be 

delivered to the servicing transportation activity by the retail supply activity accompanied 

by a DD Form 1348-1A, Issue Release/Receipt Document, (IRRD). DLM 4000.25, 

Volume 2, Chapter 29 documents procedures for the use and generation of the IRRD.

 C2.3.2.4. Follow-up Requests. The supply system will initiate DLMS 940R, 

Cargo Release Inquiry (DIC AF6/AFJ) message transaction for follow-up requests. 

Based upon elapsed time from either the initial release of the Materiel Release 

Order/Disposal Release Order/Redistribution Order or the estimated shipping date from 

the Materiel Release Advice/Disposal Shipment Advice, The supply system will initiate 

the inquiry using standard materiel release/confirmation normal follow-up procedures 

as documented in DLM 4000.25, Volume 2, Chapter 4. The only exceptions relate to 

multi-packs (see paragraph C2.3.6. below) and assemblages (e.g., medical (see 

paragraph C2.3.7. below)).

 C2.3.2.5. Cancellation Requests. The supply system will initiate DLMS 

940R, Materiel Release Cancellation/Disposal Release Cargo Release Cancellation 

(DIC AC6/ACJ) message for cancellation requests. DLM 4000.25, Volume 2, Chapter 4 

1 Refer to ADC 316C.

2 Refer to DLM 4000.25 Volume 2, Chapter 5, Status Reporting, and ADC 1030

3 Refer to ADC 1164
Enclosure 1, MFR Admin ADC 1463A 

Page 4 

prevails; the only exceptions relate to multi-packs (see paragraph C2.3.6. below) and 

assemblages (e.g., medical (see paragraph C2.3.7. below)).

 C2.3.2.6. Shipment Status Messages 

 C2.3.2.6.1. Initial Shipment Status Message. When the retail supply 

activity receives the CargoMateriel Release Confirmation for a multi-pack, the activity 

must associate it with all the document numbers that were contained in the initial 

CargoMateriel Release Order, generate the required DLMS 856S, Shipment Advice 

(DIC AS_) shipment status transactions for the multipack, and transmit to DAAS for 

distribution per existing procedures and trading partner profiles. When the retail supply 

activity receives the CargoMateriel Release Confirmation for an assemblage (e.g., 

medical), the activity will generate the required DLMS 856S Shipment Status 

transaction at the Assemblage Identification Number (AIN) level. For all Materiel 

Release Confirmations, the retail supply activity will insert the original distribution code 

assigned to the Materiel Release Order/Disposal Release Order/Redistribution Order in 

lieu of the special distribution code used to denote the retail transportation and supply 

interchange when generating the shipment status transactions.

 C2.3.2.6.2. Shipment Status Message Updates. In the event a 

shipment does not get lifted as originally intended (e.g., shipment is left off the truck) 

and the retail supply activity receives an updated DLMS 945A, CargoMateriel Release 

Confirmation message from the retail transportation activity, then the retail supply 

activity will generate an updated DLMS 856S, Shipment Status transaction to convey 

the changed transportation information. See DLM 4000.25, Volume 2, Chapter 5 for 

detailed procedures. Examples of changed transportation information would include 

transportation method code, standard carrier alpha code (SCAC), ship date, bill of 

lading information, and tracking information.

 C2.3.2.6.3. Unique Item Identification.4 Shipment Status for NSNs 

containing an IUID indicator Yes (Y), indicating that DoD IUID Supply Policy is required, 

must contain the UII and/or serial number for each item when available. Refer to DLM 

4000.25 Volume 2, Chapter 5, Status Reporting; paragraph C5.1.3.5. contains specific 

shipment status requirements for IUID. 

C2.3.3. Servicing Transportation Activity. This paragraph provides general 

procedures for servicing transportation activities following receipt of the CargoMateriel

release order (MRO) from the retail supply systems and subsequent local delivery of 

items for shipment (received from retail supply).

 C2.3.3.1. Initial Transportation Account Code Validation.

5 Following receipt 

of the Cargo Release Order (MRO) from the retail supply system, transportation will 

validate the transmitted transportation account code (TAC). In case of an invalid or 

missing TAC, the transportation system will generate a DLMS 945A (AE6), 

CargoMateriel Release Advice transaction with Shipment Hold Code S, Invalid or

4 Refer to DLM 4000.25 Volume 2, Chapter 5, Status Reporting, and ADC 1030

5 Refer to ADC 1206 for detailed procedures.
Enclosure 1, MFR Admin ADC 1463A 

Page 5 

Missing Transportation Account Code (TAC), and send it back to the retail supply 

system. This provides visibility for possible delays in processing a shipment due to an 

invalid or missing TAC and gives the supply activity the option to resend the DLMS 

940R with the correct TAC. If the supply activity sends an updated MRO, the 

transportation activity will validate the TAC and append the Cargo Release OrderMRO. 

Figure C2.F1 depicts the transaction account code validation process.

 C2.3.3.2. In-Check. Upon local delivery of the item (from retail supply) to the 

transportation activity customer service area, transportation personnel will in-check the 

items as follows:

 C2.3.3.2.1. Either scan the DD Form 1348-1A, IRRD using a handheld 

scanner or manually in-check the document numbers into the transportation system. 

 C2.3.3.2.2. Generate DLMS 945A, Notice Materiel Release 

Advice/Disposal Shipment Advice (DIC AE6/AEJ) in-check status message and send it 

to the supply activity electronically.

 C2.3.3.2.3. When CMOS is the servicing transportation activity, the incheck status message will include the transportation in-checker identification code 

(three position numeric value) and the associated in-checker full name in the format of 

First Name Middle Initial Last Name, with no special characters (e.g., periods, commas) 

to separate the components of the full name. If there is no middle initial, then insert 

NMN (no middle name) in place of the middle initial. Optional contact information may 

include phone numbers (e.g., commercial, DSN, international, and fax) and electronic 

mail. If more than three types of contact information are required, repeat the X12 PER 

segment, not to exceed two repetitions. 

 C2.3.3.3. Transportation Account Code Validation on Shipping Documents. 

Verify that the TAC on the DD Form 1348-1A matches the TAC on the Cargo Release 

OrderMRO. If the TAC on the DD Form 1348-1A is either missing or there is a 

mismatch, then coordinate with the supply activity. Upon receipt of a valid TAC from the 

supply activity, update historical records and shipping documentation to reflect the 

correct TAC citation. Figure C2.F1 depicts the transaction account code validation 

process.

 C2.3.3.4. Hold Status. Subsequent to in-check and prior to cargo materiel

release confirmation, if the cargo is placed in transportation hold status, additional 

DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (DIC AE6/AEJ) status 

messages will be sent by transportation to supply.

 C2.3.3.5. Status/Follow-up Response. The transportation system will 

respond to a follow-up request using DLMS 945A Materiel Release Advice 

(W0610/NO). When the cargo was checked-in and/or shipped, the transportation 

system will transmit an image copy of the transaction as applicable. , Materiel 

Release Advice/Disposal Shipment Advice (DIC AE6/AEJ) supply status message. 
Enclosure 1, MFR Admin ADC 1463A 

Page 6 

 C2.3.3.6. Cancellation Response. The transportation system will generate a 

DLMS 945A, Cargo Release DenialMateriel Release Advice (W0506/56)/Disposal 

Shipment Advice (DIC AE6/AEJ) status message with applicable status code indicating 

acknowledgement of the cancellation requirements.

 C2.3.3.7. CargoMateriel Release Confirmation

 C2.3.3.7.1. Initial CargoMateriel Release Confirmation. After the 

shipment is processed and shipped, the transportation activity generates a DLMS 945A, 

CargoMateriel Release Confirmation/Disposal Release Confirmation, and sends it to 

the supply activity, where the shipment status message will be generated and 

transmitted.

 C2.3.3.7.2. CargoMateriel Release Confirmation 

Changes/Corrections/Updates. In the event a shipment does not get lifted as originally 

intended (e.g., shipment is left off the truck), the transportation activities will send an 

updated that originate the DLMS 945A CargoMateriel Release Confirmation

(W0611/CJ and W0612/A6) will send an updated MRC transaction with all of the 

changeds made to the transportation information. The updated information will to 

the supply activity to enable the supply activity to prepare an updated DLMS 856A 

Shipping Status message. See DLM 4000.25 Volume 2, Chapter 4 for detailed 

procedures for preparation of the MRC change/update message. Examples of changed 

transportation information would include transportation method code, SCAC, ship date, 

bill of lading information, and tracking information. 

 C2.3.3.7.3. Item Unique Identification. When the DLMS 940R contains 

IUID data content (e.g., UII and/or serial number), perpetuate the IUID content in the 

DLMS 945A CargoMateriel Release Confirmation to clearly delineate which UIIs/serial 

numbers were shipped under a particular TCN. When a shipment contains IUID content 

and is shipped in multiple freight pieces, shippers are NOT authorized to execute the 

movement of the shipment using multiple freight piece procedures (e.g., citing the same 

TCN for all boxes). Those shipments must be “partialled” by using the 16th position of 

the TCN to uniquely identify each freight piece. A separate DLMS 945A Cargo

Release Confirmation MRC will be transmitted for each document number – partial 

TCN pair, identifying the contents of each freight piece, to include pRFID tag(s) and 

UII(s) and/or serial numbers.

 C2.3.3.8. Transaction Information Copy. For designated supply trading 

partners (currently limited to the SBSS–CMOS interface), an information copy (image) 

of the DLMS 945A, CargoMateriel Release Advice will be used in support of Air Force 

PIC Fusion program data requirements. The routing of an additional information-only 

copy of the DLMS 945A, CargoMateriel Release Advice transaction is authorized for 

forwarding PIC Fusion data needed for the Air Force UIT Registry. This is a specific 

authorized use with unique identifiers to flag the transaction as information only.

 C2.3.3.9. Transportation Account Code Validation Process Flow. Figure 

C2.F1 depicts the transaction account code validation process.
Enclosure 1, MFR Admin ADC 1463A 

Page 7 

Figure C2.F1 – Transportation Account Code (TAC) Validation Process Flow

940R comes into 

retail transportation 

AIS from retail 

supply AIS

TAC validation

TAC validation 

passed?

Physical item arrives 

at transportation 

activity w/ 

DD 1348-1A

Transportation AIS 

sends 945A (AE6) w/ 

Shipment Hold Code 

S to supply AIS

Yes

No

Physical item arrives 

at transportation 

activity w/ 

DD 1348-1A

Is TAC on DD 

1348-1A?

Can TAC be 

validated?

TAC validation 

complete

Manual 

research 

resulting in 

correct & valid 

TAC

Yes

Yes

No

No

Is TAC on DD 

1348-1A the same 

as in 940R?

YES

Manual 

research 

resulting in 

correct & valid 

TAC

No

Is the correct 

TAC in 940R? Yes

Internal 

procedure to 

correct the 

TAC in historic 

data.

No

Internal 

procedure to 

insert the TAC 

in historic 

data.

*

*The supply activity has the option to resend the 940R with the correct TAC to prevent delays.

C2.3.4. DAAS Processing. DAAS will route transactions between designated 

supply and transportation systems based on mutual agreements between the trading 

partners. This includes both DLMS compliant and MILSTRIP legacy transaction 

compliant systems.

 C2.3.4.1. Transportation Systems. The Cargo Movement Operations System 

(CMOS) and Distribution Standard System (DSS) are capable of receiving DLMS 
Enclosure 1, MFR Admin ADC 1463A 

Page 8 

compliant DLMS 940R, Materiel Release and transmitting DLMS 945A, Materiel 

Release Advice messages.

 C2.3.4.2. Supply Systems. Depending on whether the supply system is 

DLMS compliant, DAAS will process the transactions as follows:

 C2.3.4.2.1. DLMS Compliant Systems. If the supply system is DLMS 

compliant, DAAS will not transform the transactions to/from MILSTRIP legacy 

transactions, based on established trading partner profiles held by DAAS. If the supply 

system is DLMS compliant and is exchanging information about multi-packs, the W0507 

data element in the DLMS 940R, Materiel Release and W0612 data element in the 

DLMS 945A, Materiel Release Advice will carry Action Code CN. For assemblages 

(e.g., medical), the W0507 data element in the DLMS 940R, Materiel Release and 

W0612 data element in the DLMS 945A, Materiel Release Advice will carry Action Code 

ME. For interchanges other than multi-packs and assemblages, the W0507 data 

element in the DLMS 940R, Materiel Release and the W06112 data element in the 

DLMS 945A, Materiel Release Advice will carry Action Code A6. Additionally, DLMS 

940R and DLMS 945A will have qualifier under W0506. Distribution Code 111. These 

action codes and Distribution Code 111 will denote the applicability of special 

procedures authorized under this Chapter and authorize the use of selected EDI 

segments and loops to denote contents of multi-packs and assemblages.

 C2.3.4.2.2. MILSTRIP Legacy Transaction Compliant Systems. If the 

supply system is MILSTRIP legacy transaction compliant, Distribution Code 111 will be 

identified to denote the applicability of special procedures authorized under this 

Chapter. Normally DAAS will transform the transactions to/from MILSTRIP legacy 

formats based on existing maps, except when there is a Distribution Code 111 in DLMS 

945A, Materiel Release Advice/Disposal Shipment Advice messages from the 

transportation system. Distribution Code 111 authorizes the following actions: use of 

DIC AE6/AEJ for unsolicited supply status responses by the transportation system; use 

of transportation hold and delay codes in DIC AE6/AEJ (rp51) by the transportation 

system in addition to its normal usage in the Materiel Release Confirmation; and use of 

DIC AE6/AEJ in lieu of DIC AG6/AGJ as a cancellation response by transportation 

system to facilitate usage of the supply status and transportation hold and delay codes.

C2.3.5. Retail Transportation and Supply Interchange. Figure C2.F1 shows the 

standard transactions that will occur between retail supply and the transportation activity 

for the business processes covered in this chapter.
Enclosure 1, MFR Admin ADC 1463A 

Page 9 

Figure C2.F2 – Retail Transportation and Supply Data Interchange

 C2.3.5.1. DLMS and MILSTRIP Legacy Transaction Designations. To 

denote a transaction is in support of the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange, it will contain the designated action code and/or 

distribution code as delineated below:

 C2.3.5.1.1. Action Code (Other than Multi-packs and Assemblages 

(e.g., Medical))

 C2.3.5.1.1.1. DLMS 940R (W0507) = A6

 C2.3.5.1.1.2. DLMS 945A (W0612) = A6 

 C2.3.5.1.2. Action Code (Multi-Packs and Assemblages (e.g., Medical))

 C2.3.5.1.2.1. Multi-Packs. DLMS 940R (W0507) = CN and DLMS 

945A (W0612) = CN

 C2.3.5.1.2.2. Assemblages. DLMS 940R (W0507) = ME and 

DLMS 945A (W0612) = ME
Enclosure 1, MFR Admin ADC 1463A 

Page 10

 C2.3.5.1.3. Distribution Code

 C2.3.5.1.3.1. DLMS 940R and DLMS 945A LQ01 = AK and LQ02 = 

111

 C2.3.5.1.3.2. MILSTRIP legacy transaction distribution code = 111.

 C2.3.5.2. Pre-Positioned transactions from Supply. For designated supply 

trading partners, the DLMS 940R Cargo Release Order (W0506=CU) DAAS will transmit 

copies of DLMS 940R, Materiel Release Order/Disposal Release Order/Redistribution 

Order (DICs A2_/A5_/A5J/A4_) transactions can be used to the designated 

transportation system to be pre-position a cargo-only release order ed awaiting actual 

arrival of cargo from the supply warehouse. Once the cargo arrives and checked-in, 

the storage activity (wholesale) will transmit a DLMS 945A Materiel Release Advice 

(W0611=NO) transaction to notify the supply activity (retail) that the property has 

been received. The applicable transactions can be readily identified by use of 

Distribution Code = 111. Additionally, the action code in DLMS 940R (W0507) and DLMS 

945A (W0612) will be either A6, CN, or ME.

 C2.3.5.3. Transportation Account Code Validation.

6 Following receipt of the 

DLMS 940R Cargo Release Order MRO transaction from the supply system, 

transportation will perform a validation of the transmitted TAC. If the provided TAC 

proves to be invalid or is missing, the transportation system generates a DLMS 945A

(W0611/NOAE6), Materiel Release status Advice transaction with Shipment Hold Code S, 

Invalid or Missing TAC, and sends it back to the supply system. The supply activity then 

has the option to resend the DLMS 940R Cargo Release Order MRO with the correct 

TAC to prevent delays in processing the shipment for release. 

 C2.3.5.3.1. If the supply activity sends an updated Cargo Release Order

MRO, the transportation activity will validate the TAC and append accordingly the MRO.

 C2.3.5.3.2. If the supply activity does not send an updated Cargo 

Release Order MRO, the transportation activity will validate the TAC following in-check of 

the materiel by comparing the DD 1348-1A to the Cargo Release Order MRO. If there is 

a mismatch, the transportation activity will coordinate with the supply activity to identify a 

valid TAC, at which time the transportation activity will update its records and process the 

shipment for release.

 C2.3.5.4. Receipt/In-Check of Cargo by Transportation. Upon physical 

receipt/in-check of cargo by transportation, the transportation system will self-initiate a 

DLMS 945A (W0611/NO), Materiel Release Advice/Disposal Shipment Advice (DIC 

AE6/AEJ) supply status response message to notify the supply activity via DAAS that the 

property has been received. Since there was no initial DLMS 940R, Materiel Release 

Inquiry/Disposal Release Inquiry (DIC AF6/AFJ) follow-up request prompting the status 

message, the American National Standards Institute, Accredited Standards Committee 

X12 (X12) Code NO will be inserted in the W0611 data element to denote that this is 

6 Refer to ADC 1206 for detailed procedures.
Enclosure 1, MFR Admin ADC 1463A 

Page 11

being used by transportation to report cargo processing status prior to materiel release 

confirmation, and X12 code A6 will be inserted in the W0612 data element to denote that 

the supply status response is part of the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange. To facilitate mapping of the DLMS 945A, Materiel 

Release Inquiry/Disposal Release Inquiry to a MILSTRIP legacy DIC AE6/AEJ 

transaction, the Distribution Code will carry a value of 111 to inform DAAS of the special 

routing and generation of an unsolicited supply status message and to authorize the use 

of the transportation hold and delay code in lieu of a signal code for a supply status 

response, in addition to the Materiel Release Confirmation where it normally is reported. 

If the materiel is later placed into a transportation hold status, such as awaiting air 

clearance, a self-initiated DLMS 945A (W0611/NO), Materiel Release Advice/Disposal 

Shipment Advice supply status message will be generated for every reportable status 

change prior to shipment. The W06, LQ, and G62 segment values in the DLMS 945A, 

Materiel Release Advice/Disposal Shipment Advice for this step are as follows:

 C2.3.5.4.1. In-Check Reporting. To report in-check of cargo, W0611 = 

NO and W0612 = A6; LQ01 = AK and LQ02 = 111; LQ01 = 81 and LQ02 = BA; G6201 = 

17 and G6202 = estimated shipping date in CCYYMMDD format.

 C2.3.5.4.2. Transportation Hold and Delay Reporting. To report a 

transportation hold and delay status, W0611 = NO and W0612 = A6; LQ01 = AK and 

LQ02 = 111; LQ01 = BC and LQ02 = authorized code values from DLM 4000.25, Volume 

2, Appendix 7.17, Shipment Hold Codes; G6201 = 17 and G6202 = estimated shipping 

date in CCYYMMDD format.

 C2.3.5.5. Status Inquiry and Response. The supply system will initiate a 

DLMS 940R, Cargo Release Order Follow-up (W0506/CU and W0507/82) Materiel 

Release Inquiry/Disposal Release Inquiry (DIC AF6/AFJ) message for follow-up requests 

to inquire on the status of a release order turned over to transportation for shipping.; the 

W0507 data element will carry an A6 to denote that the follow-up request is part of the 

Retail Transportation and Supply Receipt and Acknowledgement Interchange. Based 

upon elapsed time from either the initial release of the Materiel Release Order/Disposal 

Release Order/Redistribution Order or the estimated shipping date from the Materiel 

Release Advice/Disposal Shipment Advice, the supply system will initiate the inquiry 

using standard normal follow-up procedures for MRO/DRO., with communications via 

DAAS. The transportation system will respond to a follow-up request with a DLMS 945A, 

NO Notice (W0610 Materiel Release Advice/Disposal Shipment Advice supply status 

response message with an A6 in the W0612 data element and Distribution Code 111 to 

denote that the supply status response is part of the Retail Transportation and Supply 

Receipt and Acknowledgement Interchange. Distribution Code 111 also authorizes the 

use of the transportation hold and delay code in lieu of the signal code, as applicable for a 

supply status response, in addition to the Materiel Release Confirmation where it normally 

is reported. The W06, LQ, and G62 segment values in the cargo release DLMS 945A, 

Materiel Release Advice/Disposal Shipment Advice for this step are as follows:

 C2.3.5.5.1. Materiel Release Order
Enclosure 1, MFR Admin ADC 1463A 

Page 12

 C2.3.5.5.1.1. W0611 = NL

 C2.3.5.5.1.2. W0612 = A6

 C2.3.5.5.1.3. LQ01 = AK and LQ02 = 111

 C2.3.5.5.2. Disposal Release Order

 C2.3.5.5.2.1. W0611 = NQ

 C2.3.5.5.2.2. W0612 = A6

 C2.3.5.5.2.3. LQ01 = AK and LQ02 = 111.

 C2.3.5.5.3. To report the applicable supply status code, LQ01 = 81 and 

LQ02 = authorized code values from DLM 4000.25-1, Appendix 27.16. Typical status 

codes that may be reported by transportation are BA to denote the item is being 

processed for release and shipment (in-checked) or BF to denote that transportation has 

no record of the document for the follow-up request, or BX to indicate that pre-positioned 

data on the item from shipment was received from supply but the item has not yet arrived 

at the transportation activity for in-check. When providing a BA status, G6201 = 17 and 

G6202 = estimated shipping date in CCYYMMDD format.

 C2.3.5.5.4. To report a transportation hold and delay status, LQ01 = AK 

and LQ02 = 111; LQ01 = BC and LQ02 = authorized code values from DLM 4000.25, 

Volume 2, Appendix 7.17, Shipment Hold Codes; G6201 = 17 and G6202 = estimated 

shipping date in CCYYMMDD format.

 C2.3.5.6. Cancellation Requests and Responses. The supply system will 

transmit initiate a DLMS 940R, Cargo Release Cancellation Materiel Release 

Cancellation/Disposal Release Cancellation (DIC AC6/ACJ) transaction message to 

when it wants to issue a cancellation request to the transportation system and request 

the cancellation of a previously submitted cargo release order. The transportation 

system will attempt to process the request unless the cargo was already released 

to and shipped. For a cancellation prior to release and shipment, the 

transportation system will transmit a DLMS 945A Cargo Release Denial with the 

appropriate status code to indicate the cancellation was successful. See DLM 

4000.25, Volume 2, Appendix 7.16. for available status codes. Once the cargo has 

been released for transportation, the release order cannot be cancelled. for release 

orders that have already been turned over to transportation for shipping; the W0507 data 

element will carry an A6 to denote that the cancellation request is part of the Retail 

Transportation and Supply Receipt and Acknowledgement Interchange. Standard

Normal cancellation request procedures will apply. The transportation system will 

respond to the cancellation request with a DLMS 945A, Materiel Release Advice/Disposal 

Shipment Advice message, with an A6 in the W0612 data element. The distribution code 

will carry a value of 111 to inform DAAS of the use of the supply status response 

(MILSTRIP legacy DIC AE6/AEJ format) as part of the Retail Transportation and Supply 

Interchange. In addition to Distribution Code 111 identifying the retail interface, it also 
Enclosure 1, MFR Admin ADC 1463A 

Page 13

authorizes the use of supply status codes, as a response to the cancellation request. 

DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (W0611), (W0612), and 

LQ01/02 data element values for this step are as follows:

 C2.3.5.6.1. Materiel Release Order

 C2.3.5.6.1.1. W0611 = NL

 C2.3.5.6.1.2. W0612 = A6

 C2.3.5.6.1.3. LQ01 = AK and LQ02 = 111

 C2.3.5.6.2. Disposal Release Order

 C2.3.5.6.2.1. W0611 = NQ

 C2.3.5.6.2.2. W0612 = A6

 C2.3.5.6.2.3. LQ01 = AK and LQ02 = 111.

 C2.3.5.6.3. To report the applicable supply status code associated with 

the cancellation response, LQ01 = 81 and LQ02 = authorized code values from DLM 

4000.25, Volume 2, Appendix 7.16. Typical status codes that may be reported by 

transportation are BF to denote that transportation has no record of the document for the 

cancellation request, BQ to denote that the cancellation request is confirmed and the 

release order is no longer being processed for shipment, and B8 to denote that the 

quantity requested for cancellation cannot be processed because the item has already 

been shipped.

 C2.3.5.7. Shipment Notification (Materiel Release Confirmation). Once the 

materiel is shipped, the transportation system will initiate a DLMS 945A, Cargo Release 

Confirmation transaction Materiel Release Confirmation/Disposal Release Confirmation 

(DIC AR_) message to notify the supply system via DAAS that the materiel has been 

shipped. The W0612 data element will contain an A6 and Distribution Code 111. Upon 

receipt of a DLMS 945A, Cargo Release Confirmation transaction Materiel Release 

Confirmation/Disposal Release Confirmation (DIC AR_), the supply system will transmit, 

via DAAS, the required DLMS 856S, Shipment Advice (DIC AS_) messages to the 

designated recipients following standard normal supply business rules. Note: the retail 

supply system will apply the original distribution code in lieu of the specially assigned 

code value of 111 in the shipment status messages. The W06, LQ, and G62 segment 

values in the DLMS 945A, Materiel Release Confirmation/Disposal Release Confirmation 

for this step are as follows:

 C2.3.5.7.1. Materiel Release Order

 C2.3.5.7.1.1. W0611 = NJ

 C2.3.5.7.1.2. W0612 = A6
Enclosure 1, MFR Admin ADC 1463A 

Page 14

 C2.3.5.7.1.3. LQ01 = AK and LQ02 = 111

 C2.3.5.7.2. Disposal Release Order

 C2.3.5.7.2.1. W0611 = NM

 C2.3.5.7.2.2. W0612 = A6

 C2.3.5.7.2.3. LQ01 = AK and LQ02 = 111.

 C2.3.5.7.3. Partial Transportation Control Numbers. If the shipment is 

partialed into multiple TCNs (e.g., alpha character other than X in record position 16), the 

W12 sub-loop will be repeated for each related partial TCN (e.g., record positions 1-15 

are identical) with the TCN and the document number for the shipment identified in the 

N9/0040 segment.

C2.3.6. Multi-Pack Processing Procedures. This paragraph provides procedures for 

use when processing multi-packs. 

 C2.3.6.1. DLMS Compliant Supply Systems

 C2.3.6.1.1. DLMS 940R, Materiel Release. DLMS 940R will be used as a 

multi-line document transaction to identify the lead document number for a multi-pack and 

the document numbers contained within the multi-pack. The authorization to do this will 

be carried in the W0507/0200 data element with a value CN. For Cargo Release Orders

materiel and disposal release orders and redistribution orders, the N9/0900 segment will 

contain the lead document number assigned to the multi-pack, from which the 

transportation control number will be derived/assigned. The W01 Loop (Loop ID 0310) 

will be repeated for each document number associated with the multi-pack including the 

lead document number identified in N9/0900. Follow-up requests will only be at the lead 

document number level, with it identified in the N9/0400 segment in the W01 loop; no 

looping of the W01 is required; however, the following values will be used to satisfy X12 

syntax compliance: W0101 = 1, W0102 = MX, W0104 = ZZ, and W0105 = MIXED. 

Cancellation requests will contain the single line Cargo Release Orders Materiel Release 

Order document number, and the transportation system will recognize that the document 

number being used may not be the lead document number but may still be part of a multipack. Cancellation will be attempted for all items/quantities for which a DD Form 1348-1A 

has been released and there is no record of transportation release, unless the dollar 

value of a single line packed in a consolidated shipment unit is less than $200, per DLM 

4000.25, Volume 2, Chapter 4.

 C2.3.6.1.2. DLMS 945A, Cargo Release Confirmation Materiel Release 

Advice. DLMS 945A will be used as a multi-line document transaction to identify the 

transportation control number (and partial TCNs) and lead document number associated 

to it. The authorization to do this will be carried in the W0507/0200 data element with a 

value CN. Status responses will only be at the lead document number level, with it 

identified in the W12 loop in the N9/0040 segment and the W1207 data element will carry 

a ZZ with the word “MIXED” in the W1208 data element to denote a multi-pack with mixed 
Enclosure 1, MFR Admin ADC 1463A 

Page 15

commodities. For cancellation responses, the response will be at the single line 

document number level. For materiel release confirmation Wwhen the multi-pack is not 

partialed into multiple TCNs, the transaction will be processed as a single line transaction 

with the TCN and the lead document number identified in the W12 sub-loop, and the 

W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element. If 

the multi-pack is partialed into multiple TCNs (e.g., alpha character other than X in record 

position 16), the W12 sub-loop will be repeated for each related partial TCN (e.g. record 

positions 1-15 are identical) with the TCN and the lead document number for the multipack identified in the N9/0040 segment and the W1207 data element will carry a ZZ with 

the word “MIXED” in the W1208 data element. When the retail supply activity receives 

the Cargo Release Confirmation Materiel Release Confirmation, the activity will 

associate it with all the document numbers that were contained in the initial Cargo 

Release Order Materiel Release Order, generate the required DLMS 856S, Shipment 

Advice shipment status transactions for the multi-pack, and transmit to DAAS for 

distribution per existing procedures and trading partner profiles. 

 C2.3.6.2. MILSTRIP Legacy Compliant Supply Systems

 C2.3.6.2.1. DLMS 940R, Materiel Release. DLMS 940R will be 

transformed by DAAS from the MILSTRIP legacy transaction release order into a single 

line item order, as it is normally done today. The transportation system will in-check the 

multi-pack by either scanning or manually loading the lead document number; the 

transportation operator will then have to read the individual DD Form 1348-1A contained 

within the pack list to in-check the items individually and associate them to the lead 

document number. The TCN will be derived from the lead document number. Follow-up 

and cancellation requests will contain the single line Materiel Release Order document 

number. For cancellations, the transportation system will recognize that the document 

number used may not be the lead document number, but may still be part of a multi-pack. 

Cancellation will be attempted for all items/quantities for which a DD Form 1348-1A has 

been released and there is no record of transportation release, unless the dollar value of 

a single line packed in a consolidated shipment unit is less than $200, per DLM 4000.25, 

Volume 2, Chapter 4.

 C2.3.6.2.2. DLMS 945A, Materiel Release Advice. For status and 

cancellation responses, the message will be originated by the transportation system at 

the single line item transaction, comparable to the single line item DLMS 940R, Materiel 

Release received from the supply system; it will be transformed by DAAS into a single 

line MILSTRIP legacy DIC AE6/AEJ transaction at the Materiel Release Order document 

number level. For materiel release confirmations, the transportation system will originate 

the transaction at the single line item level, comparable to the single line item DLMS 

940R, Materiel Release received from the retail supply system; DAAS will transform the 

message into individual MILSTRIP legacy DIC AR_ transactions with the appropriate TCN 

(or partial TCN) mapped to the document numbers cited in the N9/0040 segment within 

the W12 sub-loop.

C2.3.7. Assemblage (e.g., Medical) Processing Procedures. This paragraph 

provides procedures for assemblage processing and the associated transactions between 
Enclosure 1, MFR Admin ADC 1463A 

Page 16

supply and transportation for shipment requirements. Refer to Volume 2, Chapter 20, 

Medical Unit Assembly Program, for related procedures used by the medical supply 

system to construct assemblages.

 C2.3.7.1. DLMS Compliant Supply Systems

 C2.3.7.1.1. DLMS 940R, Materiel Release. The DLMS 940R will be used 

as a multi-line document transaction to identify the Assemblage Identification Number 

(AIN) for an assemblage and the internal document numbers contained within the 

assemblage. The authorization to do this will be carried in the W0507/0200 data element 

with a value ME. The N9/0900 segment will contain the AIN assigned to the assemblage, 

from which the transportation control number will be derived/assigned. The W01 (Loop ID 

0310) loop will be repeated for each internal document number associated with the 

assemblage, with the information associated with the AIN being the first loop. Follow-up 

and cancellation requests will be only at the AIN level (no looping of the W01 is required); 

however, the following values will be used to satisfy X12 syntax compliance: W0101 = 1, 

W0102 = MX, W0104 = ZZ, and W0105 = “MIXED”. The lead document number will be in 

the W01 loop in the N9/0400 segment.

 C2.3.7.1.2. DLMS 945A, Materiel Release Advice. The DLMS 945A will 

be used as a multi-line document transaction to identify the transportation control number 

(and partial TCNs) and AIN associated to it. The authorization to do this will be carried in 

the W0612/0200 data element with a value ME. Status and cancellation responses will 

only be at the lead AIN level, with it identified in the W12 loop in the N9/0040 segment, 

and the W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data 

element to denote an assemblage with mixed commodities; no looping of the W12 is 

required. For materiel release confirmation wWhen the assemblage is not partialed into 

multiple TCNs, the transaction will be processed as a single line transaction with the TCN 

and the AIN identified in the W12 sub-loop, and the W1207 data element will carry a ZZ 

with the word “MIXED” in the W1208 data element. If the assemblage is partialed into 

multiple TCNs (e.g., alpha character other than X in record position 16), the W12 sub-loop 

will be repeated for each related partial TCN (e.g. record positions 1-15 are identical) with 

the TCN and the AIN for the assemblage identified in the N9/0040 segment, and the 

W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element. 

When the retail supply activity receives the Cargo Release Confirmation Materiel 

Release Confirmation, the supply activity will generate the required DLMS 856S, 

Shipment Advice shipment status transaction at the AIN level for the assemblage.

 C2.3.7.2. MILSTRIP Legacy Compliant Supply Systems

 C2.3.7.2.1. DLMS 940R, Materiel Release. DLMS 940R will be 

transformed by DAAS from the MILSTRIP legacy release order into a single line item for 

the entire assemblage as a single unit. The transportation system will in-check the 

assemblage by scanning or manually loading the AIN and process the assemblage as a 

single shipment unit. The TCN will be derived from the AIN. Follow-up and cancellation 

requests must only be at AIN level; no looping of the W01 is authorized.
Enclosure 1, MFR Admin ADC 1463A 

Page 17

 C2.3.7.2.2. DLMS 945A, Materiel Release Advice. For status and 

cancellation responses, the message will be originated by the transportation system at 

the single line item transaction, comparable to the single line item DLMS 940R Materiel 

Release received from the supply system; it will be transformed by DAAS into a single 

line MILSTRIP legacy DIC AE6/AEJ transaction at the AIN level. For materiel release 

confirmations, the transportation system will originate the transaction at the single line 

item level, comparable to the single line item DLMS 940R received from the retail supply 

system; DAAS will transform the message into individual MILSTRIP legacy equivalent 

DIC AR_ transactions with the appropriate TCN (or partial TCN) mapped to the AIN cited 

in the N9/0040 segment within the W12 sub-loop.

B. Update DLM 4000.25 Volume 2 Supply Standards and Procedures, Appendix 7.16 Status 

Codes as follows:

BQ Canceled. 

1. Results from receipt of cancellation request from requisitioner, consignee, 

manager, or other authorized activity. Also applies to cancellations resulting 

from deletion of a DoDAAC identified as requisitioner, ship-to, bill-to activity 

from the DoDAAD. De-obligate funds, if applicable.

2. For status messages under the Retail Transportation and Supply 

Receipt and Acknowledgement Interchange process, denotes 

cancellation request is confirmed and the release order is no longer being 

processed for shipment. See DLM 4000.25, Volume 3, Chapter 2.
Enclosure 2, MFR Admin ADC 1463A 

Page 1 

Enclosure 2

Revise the following DLMS Implementation Conventions (IC) as shown.

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

# Location DLMS 940R Materiel Release Reason

1. DLMS

Introductory Note

Update DLMS Introductory Note 5 as follows:

5. This transaction may be used to provide item unique identification 

(IUID) information in accordance with DLMS procedures and OSD 

Supply Policy. Implementation is limited to the Positive Inventory 

Control (PIC) nuclear weapon Related Materiel (NWRM) Unique 

Item Tracking (UIT) program and the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange (Distribution 

Code 111) under OSD Supply Policy for item unique identification 

(IUID). For all other procedures, the UII information is a placeholder 

for DLMS enhancement spending development of DLMS procedures 

and overarching OSD Supply Policy. Refer to the IUID web at URL: 

http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

Removes reference for 

distribution code 111.

2. DLMS

Introductory Note

Update DLMS Introductory Note 7 as follows:

- ADC 316, Transportation Supply Receipt and Acknowledgement

- Approved Addendum to ADC 316A, USAF Requirements for Item 

Record Data and Unique Item Tracking (UIT)

using the Materiel Release (DS 940R) under Transportation and 

Supply Receipt and Acknowledgement

Interchange

- Approved Addendum to ADC 316B, New Distribution Code (111) 

for Retail Transportation and Supply Receipt

and Acknowledgement Interchange Transactions (940R and 945A)

- ADC 1463, Discontinue of Distribution Code 111 under Move of 

Cargo Only (Transshipment) Process

Identifies the IC as 

modified by this 

change.

It also removes from 

the note all changes 

replaced by ADC 1463

3. 1/W0502/0200 Close W0502 and delete DLMS notes as follow:

DLMS Note: 

1. When this transaction supports the Retail Transportation and 

Supply Receipt and Acknowledgement

Interchange (See DLM 4000.25, Volume 3, Chapter 2) and is 

passing corrected IUID data content (e.g., UII, serial number,

batch/lot number), use Code R to indicate that this is an updated 

transaction to a previously submitted 940R. Used in conjunction 

with a distribution code = 111. DLMS enhancement; see 

introductory DLMS note 4f. Refer to ADC 1073.

2. For all other uses of this transaction, use Code Z for this data 

element to meet mandatory X12 syntax requirements.

Closes elements no 

longer needed.
Enclosure 2, MFR Admin ADC 1463A 

Page 2 

# Location DLMS 940R Materiel Release Reason

4. 1/W0506/0200 Add qualifiers CU and CC with corresponding DLMS notes as 

follow:

CU Cargo Outturn Report

DLMS Note: Use this code to indicate Cargo Release Order to 

identify the movement of cargo from retail using wholesale 

transportation. This is a borrowed code. Must use in combination 

with W0508 qualifier RA or CR. This is not a balance affecting 

transaction type. There is no legacy MILS equivalent.

CC Credit Commission Invoice

DLMS Note: Use this code to indicate Cargo Release Cancellation 

to submit a request for cancellation of a previously submitted cargo 

release order. This is a borrowed code. This is not a balance 

affecting transaction type. There is no legacy MILS equivalent.

NB Material Release Inquiry 

DLMS Note: 1. Use to inquire (follow-up) about the status of an 

open materiel release action. (Equates to MILSTRIP DIC AF6) 

2. For inquiry on a materiel release order by a retail supply system to 

a transportation system regarding multi-packs or assemblages (e.g., 

medical), inquiry will be done at the lead document number (for 

multi-packs) and Assemblage Identification Number, AIN, (for 

assemblies). For single line materiel release orders, the inquiry will 

be at the document number level. DLMS enhancement; see 

introductory DLMS note 4f.

ND Material Release Cancellation 

DLMS Note: 

1. Use to request cancellation (or diversion) of either an open 

materiel release order or redistribution order. Also used to follow up 

on a cancellation request. (Equates to MILSTRIP DIC AC6 or AK6). 

2. Use to follow up on a mass or universal cancellation request. Cite 

action code82 in the W0507. Authorized DLMS enhancement; see 

introductory DLMS note 4f. Refer to ADC 1132. 

3. For cancellation of a materiel release order by a retail supply 

system to a transportation system regarding multi-packs or 

assemblages (e.g., medical), cancellations will be done either at the 

lead document number (for multi-packs) or Assemblage 

Identification Number (AIN) (for assemblies). Use the AIN for 

assemblies to provide one reference for multiple document numbers. 

For single line materiel release orders, the cancellation will be at the 

document number level. DLMS enhancement; see introductory 

DLMS note 4f.

Adds two new 

transaction types only 

for cargo movements. 

W0508 was open 

under PDC 1460

Removes notes from 

MRO inquiry

5. 1/W0507/0200 Remove qualifier A6 and DLMS note as follows:

A6 Modified 

DLMS Note: 

1. Only use when this message supports the Retail Transportation and 

Removes qualifier A6 

to ensure customers 

can properly send 

follow-ups or 

corrections to all 
Enclosure 2, MFR Admin ADC 1463A 

Page 3 

# Location DLMS 940R Materiel Release Reason

Supply Receipt and Acknowledgement Interchange (See DoD 

4000.25-M, Volume 3, Chapter 2). 

2. Applies to materiel release order (A2_/A5_)/disposal release order 

(A5J)/redistribution orders (A4_), materiel release inquiries 

(AF6)/disposal release inquiries (AFJ) and materiel release 

cancellation (AC6)/disposal release cancellation (ACJ) transactions, 

except for multi-pack and assemblage processing as defined for 

W0507=“CN” or “ME”. 3. Used in conjunction with a distribution 

code = “111”. 4. DLMS enhancement; see introductory DLMS note 

4f. 

CN Consolidated 

DLMS Note: 

1. Only use when this message supports the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange (See DoD 

4000.25-M, Volume 3, Chapter 2). 

2. Use to advise that this message supports multi-line release 

order/supply documentation in support of multi-pack processing. The 

N9/0900 is authorized for use to identify the lead document number 

for the multi-pack. The W01 subloop(Loop ID - 0310) is authorized 

to be repeated to provide the supply information lead document 

number and each of the document numbers contained within the 

multi-pack. 

3. Use to advise that this follow-up request is in support of multipack processing. The N9/0400 will carry the lead document number 

for the status inquiry. No looping of the W01 subloop (Loop ID – 

0310) is required for multi-pack contents. 4. Used in conjunction 

with a distribution code = “111”. 5. Cancellation requests for 

multipacks shall be at the single line level. 6. DLMS enhancement; 

see introductory DLMS note 4f

ME Merge 

DLMS Note: 

1. Only use when this message supports the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange (See DoD 

4000.25-M, Volume 3, Chapter 2). 

2. Use to advise that this message supports multi-line release 

order/supply documentation in support of assemblage (e.g., medical) 

processing. The N9/0900is authorized for use to identify the 

Assemblage Identification Number for the assemblage. The W01 

subloop (Loop ID - 0310) is authorized to be repeated to provide the 

supply information associated with each of the internal document 

numbers contained within the assemblage. 

3. Use to advise that this follow-up request is in support of 

assemblage processing. The N9/0400 will carry the Assemblage 

Identification Number for the status inquiry. No looping of the W01 

subloop (Loop ID – 0310) is required for assemblage contents. 

4. Used in conjunction with a distribution code = “111”. 5. 

Cancellation requests for assemblages (e.g., medical) shall be at the 

release orders.
Enclosure 2, MFR Admin ADC 1463A 

Page 4 

# Location DLMS 940R Materiel Release Reason

AIN level.6. DLMS enhancement; see introductory DLMS note 4f.
Enclosure 2, MFR Admin ADC 1463A 

Page 5 

# Location DLMS 945A (4030) Materiel Release Advice Reason

1. DLMS

Introductory Note

Update DLMS Introductory Note 5 as follows:

5. This transaction may be used to provide item unique 

identification (IUID) information in accordance with DLMS 

procedures and OSD Supply Policy. Implementation is limited to 

the Positive Inventory Control (PIC) nuclear weapon Related 

Materiel (NWRM) Unique Item Tracking (UIT) program and the 

Retail Transportation and Supply Receipt and Acknowledgement 

Interchange (Distribution Code 111) under OSD Supply Policy for 

item unique identification (IUID). For all other procedures, the UII 

information is a placeholder for DLMS enhancement spending 

development of DLMS procedures and overarching OSD Supply 

Policy. Refer to the IUID web at URL: 

http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

Removes reference for 

distribution code 111.

2. DLMS

Introductory Note

Update DLMS Introductory Note 7 as follows:

- ADC 316, Transportation Supply Receipt and Acknowledgement

- Approved Addendum to ADC 316A, USAF Requirements for Item 

Record Data and Unique Item Tracking (UIT)

using the Materiel Release (DS 940R) under Transportation and 

Supply Receipt and Acknowledgement

Interchange

- Approved Addendum to ADC 316B, New Distribution Code (111) 

for Retail Transportation and Supply Receipt

and Acknowledgement Interchange Transactions (940R and 945A)

- ADC 1463, Discontinue of Distribution Code 111 under Move 

of Cargo Only (Transshipment) Process

Identifies the IC as 

modified by this 

change.

It also removes from 

the note all changes 

replaced by ADC 1463

3. 1/W0611/0200 Add qualifiers CJ and 56 with corresponding DLMS notes as follow:

CJ Confirmation 

DLMS Note: Use this code to indicate Cargo Release 

Confirmation. This is a borrowed code. Used in combination with 

W1201/UR. This is not a balance affecting transaction type. There 

is no legacy MILS equivalent.

56 Denied Request 

DLMS Note: Use this code to indicate denial on a cargo release 

order. This is a borrowed code. Used in combination with 

W1201/UR. This is not a balance affecting transaction type. There 

is no legacy MILS equivalent

Enables DoD 

Components to confirm 

or deny a cargo release 

order without causing 

balance affecting 

actions.

4. 1/W0611/0200 Update DLMS note as follows:

NO Notice 

DLMS Note: Use to identify a self-initiated supply status message 

provided by transportation to report cargo processing status (reply,

in-check, or hold) prior to materiel release confirmation. This is not 

to be used for standard normal supply status messages in response to 

Cargo Release follow-up requests. 

Updates NO DLMS 

Notes to clarify it can 

be used for replies. 
Enclosure 2, MFR Admin ADC 1463A 

Page 6 

# Location DLMS 945A (4030) Materiel Release Advice Reason

5. 1/W0612/0200 Update qualifier A6 DLMS notes, removes CN, and ME as well as 

corresponding DLMS Notes as follows: 

A6 Modified 

DLMS Note: 

Use to identify a correction or update to the original Cargo Release 

Order.

1. Only use when this message supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange (See DLM 

4000.25, Volume 3, Chapter 2). 

2. Applies to solicited and unsolicited materiel release inquiry 

(AE6)/disposal shipment inquiry (AEJ) in support of supply status 

and cancellation responses, materiel release and disposal release 

confirmations, except for multi-pack and assemblage processing as 

defined for W0507=CN or ME. 

3. Used in conjunction with a distribution code = 111. 

4. DLMS enhancement; see introductory DLMS note 4f.

CN Consolidated 

DLMS Note: 

1. Only use when this message supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange (See DLM 

4000.25, Volume 3, Chapter 2). 

2. Use to advise that this message is a status response in support of 

multi-pack processing. The N9/0040 is authorized for use to identify 

the lead document number for the multi-pack. No looping of the 

W12 subloop (Loop ID – 0310) is required for multi-pack contents; 

if the shipment is partialled, then the W12 loop shall be repeated to 

document each partial TCN. 

3. Used in conjunction with a distribution code = 111. 

4. Cancellation responses for multipacks shall be at the single line 

level. 

5. DLMS enhancement; see introductory DLMS note 4f. 

FI File 

DLMS Note: 

1. Use to identify an image transaction provided for information. 

2. Authorized for Air Force and DSS use with PIC NWRM UIT, 

except when the distribution code = 111. 

ME Merge 

DLMS Note: 

1. Only use when this message supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange (See DLM 

4000.25, Volume 3, Chapter 2). 

2. Use to advise that this message is a status response in support of 

assemblage (e.g., medical) processing. The N9/0040 is authorized 

for use to identify the Assemblage Identification Number for the 

Repurposes qualifier 

A6 as the action code to 

identify corrections and 

updates to the original 

cargo release order. 

Removes unnecessary 

qualifiers in the 

segment. This change 

mimics the changes in 

the DLMS 940R. 
Enclosure 2, MFR Admin ADC 1463A 

Page 7 

# Location DLMS 945A (4030) Materiel Release Advice Reason

assemblage. No looping of the W12 subloop (Loop ID – 0310) is 

required for assemblage contents; if the shipment is partialled, then 

the W12 loop shall be repeated to document each partial TCN. 

3. Used in conjunction with a distribution code = 111. 

4. Cancellation responses for assemblages (e.g., medical) shall be at 

the AIN level. 

5. DLMS enhancement; see introductory DLMS note 4f. 

6. 1/PER01/0800 Update Segment DLMS Notes as follows: 

DLMS Note: 

1. Only use when this transaction supports the Retail Supply and 

Transportation Receipt and Acknowledgement Interchange (See 

DLM 4000.25, Volume 3, Chapter 2). 

2. Used in conjunction with a distribution code = 111. Use in 

combination with Cargo Release Orders, Notice, Confirmations, or 

Denials. 

3. May use up to two repetitions of the PER Segment to provide all 

applicable contact information. Repeat the PER01-PER02 in the 

second repetition to satisfy syntax requirements. 

4. DLMS enhancement; see introductory DLMS note 4e. 

5. See ADC 1055. 

Updating DLMS Note 

to reference cargo 

release transactions.

7. 2/N101/0800 Update DLMS Notes as follows: 

KK Registering Party 

DLMS Note: 

1. Use to identify the Component UIT registry. May be used by a 

Component when their UIT process requires that a copy of the 

transaction should also be sent to a UIT registry for information 

purposes. Must be used with 2/N106/0800 code PK-Party to Receive 

Copy’ to identify that this is only an information copy of the 

transaction, for use with the Component UIT registry. Cite the 

applicable Routing Identifier in 2/N104. 

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

PIC NWRM UIT program. For PIC UIT, must use in conjunction 

with 2/N106 code PK and 1/W0612/0200 Action Code FI and cite 

the applicable Routing Identifier in 2/N104. 

3. Authorized DLMS enhancement for Air Force use under the 

Retail Transportation and Supply Receipt and Acknowledgement 

Interchange (Distribution Code of 111). For PIC UIT, must use in 

conjunction with 2/N106 code PK and cite the applicable Routing 

Identifier in 2/N104. 

Removes Distribution 

code 111 reference. 
Enclosure 2, MFR Admin ADC 1463A 

Page 8 

# Location DLMS 945A (4030) Materiel Release Advice Reason

4. Except as noted above, DLMS enhancement; see introductory 

DLMS note 4a. 

8. 2/N106/0800 Updates DLMS Notes as follows: 

PK Party to Receive Copy 

DLMS Note: 

1. Use when appropriate to send an information copy 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 program. For PIC UIT, must use in conjunction 

with 2/N101 code KK and 1/W0612/0200 Action Code FI and cite 

the applicable RIC in 2/N104. 

3. Authorized DLMS enhancement for Air Force use under the 

Retail Transportation and Supply Receipt and Acknowledgement 

Interchange (Distribution Code of 111). For PIC UIT, must use in 

conjunction with 2/N101 code KK and cite the applicable RIC in 

2/N104. 

4. Except as noted above, DLMS enhancement; see introductory 

DLMS note 4a. 

Removing Distribution 

code 111 reference.