1 

ADC 316 

Retail Transportation and Supply Receipt and Acknowledgement Transactions 

 

1. ORIGINATOR: 

a. Service/Agency: Department of the Air Force 

b. Sponsor: CMOS PMO, 754 ELSG/ILTT, Commercial (334) 416-2501 

2. FUNCTIONAL AREA:

Primary: Transportation 

Secondary: Supply Chain Visibility and Accountability 

3. REFERENCES: 

a. DoD 4000.25-M, Defense Logistics Management System (DLMS), Volume 3, 

Chapters 1 and 2 

b. DoD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Chapters 2, 3, 4, and Appendixes 2.1, 2.12, 2.16, and 3.10 

4. REQUESTED CHANGE: 

a. Description of Changes: 

 

 (1) Implement a standardized interchange between retail transportation and supply 

through the use of EDI transactions, specifically the Warehouse Shipping Order, 940R, and 

Warehouse Shipping Advice, 945A. This standard exchange provides the ability to pre-position 

release order data in transportation, submit follow-up status messages to transportation 

requesting updated shipment status, submit cancellation requests to transportation for release 

orders already turned over to transportation for shipment planning and execution, provide supply 

status messages from transportation to supply, provide cancellation response messages from 

transportation to supply, and submit material release confirmation messages from transportation 

to supply when the material has shipped. 

 (2) At present, there are five systems that are planning to use this standardized 

interchange; the Defense Medical Logistics Standard Support (DMLSS), Global Combat Support 

System - Marine Corps (GCSS-MC), Standard Base Supply System (SBSS), and USAF 

Expeditionary Combat Support System (ECSS) systems represent the supply systems for their 

respective business areas and the Cargo Movement Operations System (CMOS) represents the 

transportation system. Systems other than those mentioned in this document, planning to use 

these standardized interchange transactions to implement a similar capability must coordinate 
2 

with DLMSO and United States Transportation Command (USTRANSCOM) prior to attempting 

to implement the interchange. 

b. Description of Changes in detail: (see Figure 1 on page 4 of this document) 

(1) To denote a transaction is in support of the Retail Transportation and Supply 

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

distribution code as delineated below. 

(a) For DLMS transactions, other than those supporting multi-packs and 

assemblages (e.g., medical), the appropriate action code shall be: 

• EDI 940R W0507 = “A6” 

• EDI 945A W0612 = “A6” 

(b) For DLMS transactions, supporting multi-packs and assemblages (e.g., 

medical), the appropriate action code shall be: 

• For multi-packs, the EDI 940R W0507 = “CN” and the EDI 945A 

W0612 = “CN” 

• For assemblages, the EDI 940R W0507 = “ME” and the EDI 945A 

W0612 = “ME” 

(c) For all MILS and DLMS transactions, the distribution code shall be: 

• EDI 940R and EDI 945A LQ01 = “AK” and LQ02 = “1” 

• MILS distribution code = “1” 

(2) For designated supply trading partners, DAASC shall transmit copies of the 

Material Release Order/Disposal Release Order/Redistribution Order 940R (A2_/A5_/A5J/A4_) 

transactions to the designated transportation system to be pre-positioned awaiting actual arrival 

of cargo from the supply warehouse. The applicable transactions can be readily identified by use 

of the distribution code = “1”. Additionally, the action code in the EDI 940R W0507 and the 

EDI 945A W0612 will be either “A6, “CN”, or “ME”. 

(3) Upon physical receipt/incheck of cargo into transportation, the transportation 

system shall self-initiate a Material Release Advice/Disposal Shipment Advice 945A (AE6/AEJ) 

supply status response message to notify the supply activity via DAASC that the property has 

been received. Since there was no initial Material Release Inquiry/Disposal Release Inquiry 

940R (AF6/AFJ) follow-up request prompting the status message, a new X12 code of “NO” shall 

be inserted in the W0611 segment and a new X12 code of “A6” shall be inserted in the W0612 

segment to denote that this is being used by transportation to report cargo processing status prior 

to material release confirmation. To facilitate mapping of the Material Release Advice/Disposal 

Shipment Advice 945A to a MILS AE6/AEJ transaction, a specially assigned distribution code 

value of “1” shall be used by the transportation system to inform DAASC of the special routing 

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

transportation hold and delay code in a supply status response in addition to the material release 

confirmation where it normally is reported. If the material is subsequently placed by the 

transportation system into a transportation hold status, such as awaiting air clearance, a selfinitiated Material Release Advice/Disposal Shipment Advice 945A supply status message shall 

be generated for every reportable status change, prior to shipment. 

(a) To report physical receipt/incheck of cargo, the Material Release 

Advice/Disposal Shipment Advice 945A W0611 segment shall have an “NO” to denote that this 

supply status response is unsolicited and the W0612 segment shall have an “A6” to denote that 

this response is part of the Retail Transportation and Supply Receipt and Acknowledgement 

Interchange. The LQ segment shall be populated as follows: LQ01 = “AK” and LQ02 = “1”; 

LQ01 = “81” and LQ02 = “BA”. The G62 segment will be populated as follows to provide the 

estimated shipping date: G6201 = “17”; G6202 = estimated shipping date in CCYYMMDD 

format. 

(b) To report a transportation hold and delay status, the Material Release 

Advice/Disposal Shipment Advice 945A W0611 segment shall have an “NO” to denote that this 

supply status response is unsolicited and the W0612 segment shall have an “A6” to denote that 

this response is part of the Retail Transportation and Supply Receipt and Acknowledgement 

Interchange. The LQ segment shall be populated as follows: LQ01 = “AK” and LQ02 = “1”; 

LQ01 = “BC” and LQ02 = authorized code values from the Transportation Hold Code table at 

the following URL https://www-tmds.c2.amc.af.mil/TMDS/dtr_index.xsql. The G62 segment 

will be populated as follows to provide the estimated shipping date: G6201 = “17”; G6202 = 

estimated shipping date in CCYYMMDD format. 

(4) The supply system will initiate a Material Release Inquiry/Disposal Release 

Inquiry 940R (AF6/AFJ) message when it wants to follow-up on the status of a release order 

turned over to transportation for shipping; the W0507 segment shall contain the code “A6” and 

the distribution code shall contain a “1” to denote that this 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 material release order/disposal release 

order/redistribution order or the estimated shipping date from the material release 

advice/disposal shipment advice, the supply system will initiate the inquiry using normal followup procedures, with communications via DAASC. The transportation system shall respond to a 

follow-up request with a Material Release Advice/Disposal Shipment Advice 945A supply status 

response message; the W0612 segment shall contain the code “A6” and the distribution code 

shall contain a “1” to denote that the supply status response is part of the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange. The distribution code of “1” 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 material release confirmation where it 

normally is reported. 

(a) To report supply status on a material release order, the Material Release 

Advice 945A shall clearly identify that this response is part of the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange through use of the following: 
4 

• W0611 = “NL” 

• W0612 = “A6” 

• LQ01 = “AK” and LQ02 = “1” 

(b) To report supply status on a disposal release order, the Disposal Shipment 

Advice 945A shall clearly identify that this response is part of the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange through use of the following: 

• W0611 = “NQ” 

• W0612 = “A6” 

• LQ01 = “AK” and LQ02 = “1” 

(c) To report the applicable supply status code, the Material Release 

Advice/Disposal Shipment Advice 945A LQ segment shall be populated as follows: LQ01 = 

“81”; LQ02 = authorized code values from DOD 4000.25-1-M, Appendix 2.16, Status Codes. 

Typical status codes that may be reported by transportation are “BA” to denote the item is being 

processed for release and shipment (inchecked) or “BF” to denote that you have no record of the 

document for the follow-up request. When providing a “BA” status, the G62 segment shall be 

populated as follows to provide the estimated shipping date: G6201 = “17”; G6202 = estimated 

shipping date in CCYYMMDD format. 

(d) To report a transportation hold and delay status, the Material Release 

Advice/Disposal Shipment Advice 945A LQ segment shall be populated as follows: LQ01 = 

“AK” and LQ02 = “1”; LQ01 = “BC” and LQ02 = authorized code values from the 

Transportation Hold Code table located at the following URL https://wwwtmds.c2.amc.af.mil/TMDS/dtr_index.xsql. The G62 segment shall be populated as follows to 

provide the estimated shipping date: G6201 = “17”; G6202 = estimated shipping date in 

CCYYMMDD format. 

(5) The supply system shall initiate a Material Release Cancellation/Disposal Release 

Cancellation 940R (AC6/ACJ/) message when it wants to issue a cancellation request to the 

transportation system for release orders that have already been turned over to transportation for 

shipping. The W0507 segment shall contain the code “A6” to denote that this cancellation 

request is part of the Retail Transportation and Supply Receipt and Acknowledgement 

Interchange; the distribution code shall contain a “1”. Normal cancellation request procedures 

shall apply. The transportation system shall respond to the cancellation request with a Material 

Release Advice/Disposal Shipment Advice 945A message. A specially assigned distribution 

code value of “1” will be used by the transportation system to inform DAASC of the use of the 

supply status response (MILS AE6/AEJ format) as part of the Retail Transportation and Supply 

Interchange. In addition to the distribution code “1” identifying the retail interface, it also 

authorizes the use of AE6/AEJ and supply status codes as a response to a cancellation request in 

lieu of AG6/AGJ, when applicable. 

(a) To report a cancellation response on a material release order, the Material 

Release Advice 945A shall clearly identify that this response is part of the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange through use of the following: 
5 

• W0611 = “NL” 

• W0612 = “A6” 

• LQ01 = “AK” and LQ02 = “1” 

 

(b) To report a cancellation response on a disposal release order, the Disposal 

Shipment Advice 945A shall clearly identify that this response is part of the Retail 

Transportation and Supply Receipt and Acknowledgement Interchange through use of the 

following: 

• W0611 = “NQ” 

• W0612 = “A6” 

• LQ01 = “AK” and LQ02 = “1” 

(c) To report the applicable supply status code, the Material Release 

Advice/Disposal Shipment Advice 945A LQ segment shall be populated as follows: LQ01 = 

“81” and LQ02 = authorized code values from DOD 4000.25-1-M, Appendix 2.16, Status Codes. 

Typical status codes that may be reported by transportation are “BF” to denote that you have 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. 

(6) Once the material is shipped, the transportation system shall initiate a Material 

Release Confirmation/Disposal Release Confirmation 945A message to notify the supply system 

via DAASC that the material has shipped. Upon receipt of the Material Release 

Confirmation/Disposal Release Confirmation 945A (AR_), the supply system shall transmit via 

DAASC the required Shipment Advice 856S (AS_) messages to designated recipients, following 

normal supply business rules. 

(a) To report a material release confirmation for a material release order, the 

945A shall clearly identify that this response is part of the Retail Transportation and Supply 

Receipt and Acknowledgement Interchange through use of the following: 

• W0611 = “NJ” 

• W0612 = “A6” 

• LQ01 = “AK” and LQ02 = “1” 

(b) To report a disposal release confirmation for a disposal release order, the 

945A shall clearly identify that this response is part of the Retail Transportation and Supply 

Receipt and Acknowledgement Interchange through use of the following: 

• W0611 = “NM” 

• W0612 = “A6” 

• LQ01 = “AK” and LQ02 = “1” 
6 

(c) If the shipment is partialled into multiple TCNs (e.g., alpha character other 

than “X” in record position 16), the W12 subloop 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. 

Note: This process also applies to disposal transactions 

with their applicable DLMS qualifiers and DIC codes

Retail

Source

of Supply

AIS

Retail

TMO

AIS

1.Release Order

940R Material Release/Redistribution Order (W0506=NA/NI)

DIC=A4_/A5_/A2_

2. In-check/Hold Status

945A Material Release Advice (W0611=NO)

DIC=AE6

3a. Status Inquiry 3b. Status Response

940R Material Release Inquiry (W0506=NB)

DIC=AF6

945A Material Release Advice (W0611=NL)

DIC=AE6

4a. Order Cancellation 4b. Order Cancellation Response

940R Material Release Cancellation (W0506=ND)

DIC=AC6

945A Material Release Advice (W0611=NL)

DIC=AE6

5. Shipment Notification

945A Material Release Confirmation (W0611=NJ)

DIC=AR_

b. Procedures: The procedures that are added or changed are as follows. 

(1) Retail transportation and supply interchange. 

(a) The supply activity will make local deliveries to the servicing 

transportation activity (e.g., CMOS), and the line items shall be inchecked based on cargo and 

documentation received from the supply activity using a handheld terminal or manually input to 

the transportation system. 

(b) Material will be delivered to the servicing transportation office and will 

be accompanied by a DD Form 1348-1A (IRRD - Issue Release/Receipt Document). 

Figure 1 – Retail transportation and supply Data Interchange
7 

(c) Upon delivery to the transportation office customer service area, 

transportation personnel shall either scan the IRRD using a handheld or manually incheck the 

document numbers into the transportation system. 

(d) The supply activity leaves the cargo and documentation with the 

transportation activity, and the transportation office begins processing the cargo. The 

transportation system shall search for a matching Material Release Order/Disposal Release 

Order/Redistribution Order 940R pre-positioned by the supply system to identify required supply 

data used in the transportation planning process. When no matching 940R is found, the 

transportation office shall manually enter data from the IRRD into the transportation system. 

Upon completion of the incheck process, the transportation system shall generate a Material 

Release Advice/Disposal Shipment Advice 945A incheck status message and send it to the 

supply activity electronically. 

(e) If cargo is subsequently placed in transportation hold status prior to 

material release confirmation, additional Material Release Advice/Disposal Shipment Advice 

945A status messages shall be sent by transportation to supply. 

(f) After the shipment is processed and shipped, the transportation activity 

shall release the shipment from the system and generate a Material Release 

Confirmation/Disposal Release Confirmation 945A material release confirmation for 

transmission to the supply activity. 

(g) Supply and transportation shall interchange Material Release 

Inquiry/Disposal Release Inquiry 940R (AF6/AFJ), Material Release Cancellation/Disposal 

Release Cancellation 940R (AC6/ACJ) and Material Release Advice/Disposal Shipment Advice 

945A (AE6/AEJ) to execute and acknowledge follow-up and cancellation requirements. 

(2) DAASC Processing for DLMS-compliant and MILS-compliant systems.

(a) CMOS will be capable of receiving DLMS-compliant EDI 940R and 

transmitting EDI 945A messages. DAASC shall route transactions between designated supply 

systems and CMOS based upon mutual agreement between trading partners. 

(b) If the supply system is MILS-compliant, DAASC shall transform the 

transactions to/from MILS based on existing maps, except when there is a distribution code of 

“1” in the EDI 945A messages from the transportation system: 

• Authorize use of AE6 for unsolicited supply status response by 

transportation system. 

• Authorize use of transportation hold and delay code in the AE6, rp51 

by transportation system in addition to normal usage in the material release confirmation. 
8 

• Authorize use of AE6, vice AG6/AGJ, as a cancellation response by 

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

codes. 

(c) If the supply system is DLMS-compliant, DAASC shall not transform the 

transactions to/from MILS, based on established trading partner profiles held by DAASC. 

(d) If the supply system is DLMS-compliant and is exchanging information 

about either multi-packs or assemblages (e.g., medical), the appropriate action code shall be 

identified to authorize the use of selected EDI segments and loops to denote contents of a multipack or assemblage. 

• For multi-packs, the EDI 940R W0507 = “CN” and the EDI 945A 

W0612 = “CN” 

• For assemblages, the EDI 940R W0507 = “ME” and the EDI 945A 

W0612 = “ME” 

(e) For DLMS transactions, other than those supporting multi-packs and 

assemblages (e.g., medical), the appropriate action code shall be identified to denote special 

transaction processing in support of the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange. 

• EDI 940R W0507 = “A6” 

• EDI 945A W0612 = “A6” 

(3) Multi-pack Processing. 

(a) DLMS-Compliant supply systems. 

• The Material Release Order/Disposal Release Order/Redistribution 

Order 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 shall be carried in the W0507/0200 segment with a value “CN”. The 

N9/0900 segment shall contain the lead document number assigned to the multi-pack, from 

which the transportation control number shall be derived/assigned. The W01 (Loop ID 0310) 

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

document number identified in N9/0900. For Material Release Inquiry/Disposal Release Inquiry 

940R, the requests shall only be at the lead document level number, with it identified in the W01 

loop in the N9/0400 segment; no looping of the W01 is required; however, the following values 

shall be used to satisfy X12 syntax compliance: W0101 = “1”, W0102 = “MX”, W0104 = “ZZ”, 

and W0105 = “MIXED”. For Material Release Cancellation/Disposal Release Cancellation 

940R messages, the requests shall contain the single line Material Release Order (MRO) 

document number, and the transportation system shall 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 
9 

no record of transportation release, unless the dollar value of a single line packed in a 

consolidated shipment unit is less than $200, per DoD 4000.25-1-M, C3.34-6. 

• The EDI 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 shall be carried in the W0612/0020 segment with a 

value “CN”. When used as a Material Release Advice/Disposal Shipment Advice 945A 

response, the response shall be at the lead document number level number, with it identified in 

the W012 loop in the N9/0040 segment; the W1207 segment shall carry a “ZZ” with the word 

“MIXED” in the W1208 segment to denote a multi-pack with mixed commodities. For 

cancellation responses, the Material Release Advice/Disposal Shipment Advice 945A shall be at 

the single line document number level. When used to report material release confirmation for a 

multi-pack that is not partialled into multiple TCNs, the Material Release Confirmation/Disposal 

Release Confirmation 945A shall be processed as a single line transaction with the TCN and the 

lead document number identified in the W12 subloop and the W1207 segment shall carry a “ZZ” 

with the word “MIXED”. If the multi-pack is partialled into multiple TCNs (e.g., alpha 

character other than “X” in record position 16), the W12 subloop shall 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 multi-pack identified in the N9/0040 segment and the W1207 segment 

shall carry a “ZZ” with the word “MIXED” in the W1208 segment. When the retail supply 

activity receives the material release confirmation, they shall associate it with all the document 

numbers that were contained in the initial material release order, generate the required Shipment 

Advice 856 transactions for the multi-pack and transmit to DAAS for distribution per existing 

procedures and trading partner profiles.

(b) MILS-Compliant supply systems. 

• The Material Release Order/Disposal Release Order/Redistribution 

Order 940R (A2_/A5_/A5J/A4_) transformed from the MILS release order shall be a single line 

item transaction, as it is normally done today. The transportation system shall incheck the multipack by either scanning or manually loading the lead document number; the transportation 

operator will then have to read the individual DD1348-1A contained within the pack list to 

incheck the items individually and associate them to the lead document number. The 

transportation control number shall be derived from the lead document number. When the 

Material Release Inquiry/Disposal Release Inquiry 940R (AF6/AFJ) and the Material Release 

Cancellation/Disposal Release Cancellation 940R (AC6/ACJ) are used as a follow-up request or 

cancellation request message, respectively, they shall be transacted at the single line document 

number level. For cancellations, the transportation system shall 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 DoD 4000.25-1-M, C3.34-6.

• The Material Release Advice/Disposal Shipment Advice 945A, when 

serving as a status response or cancellation response message, shall be originated by the 

transportation system at the single line item transaction, comparable to the single line item 940R 
10 

received from the supply system; it shall be transformed by DAASC into a single line MILS 

AE6/AEJ transaction at the Material Release Order (MRO) document number level. When the 

Material Release Confirmation/Disposal Release Confirmation 945A is used as a material release 

confirmation message, the transportation system shall originate the transaction at the single line 

item level, comparable to the single line item 940R received from the retail supply system; it 

shall be transformed by DAASC into individual MILS equivalent AR_ transactions with the 

appropriate TCN (or partial TCN) mapped to the document numbers cited in the W12 subloop.

(4) Assemblage (e.g., Medical) Processing. 

(a) DLMS-Compliant supply systems. 

• The Material Release Order/Disposal Release Order/Redistribution 

Order 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 shall be carried in the W0507/0200 segment 

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

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

0310) loop shall be repeated for each internal document number associated with the assemblage, 

with the information associated with the AIN being the first loop. For Material Release 

Inquiry/Disposal Release Inquiry 940R follow-up requests and Material Release 

Cancellation/Disposal Release Cancellation 940R cancellation requests, the requests shall only 

be at the AIN level, no looping of the W01 is required; however, the following values shall 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. 

• The EDI 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 shall be carried in the W0612/0020 segment with a value “ME”. When 

used as a Material Release Advice/Disposal Shipment Advice 945A response for supply status or 

cancellation responses, the response shall be at the AIN level; the W1207 segment shall carry a 

“ZZ” with the word “MIXED” in the W1208 segment to denote an assemblage with mixed 

commodities. When used to report shipment status when the assemblage is not partialled into 

multiple TCNs, the Material Release Confirmation/Disposal Release Confirmation 945A shall be 

processed as a single line transaction with the TCN and AIN identified in the W12 subloop and 

the W1207 segment shall carry a “ZZ” with the word “MIXED” in the W1208 segment. If the 

assemblage is partialled into multiple TCNs (e.g., alpha character other than “X” in record 

position 16), the W12 subloop shall be repeated for each related partial TCN (e.g. record 

positions 1-15 are identical) with the TCN and the AIN identified in the N9/0040 segment and 

the W1207 segment shall carry a “ZZ” with the word “MIXED” in the W1208 segment. When 

the retail supply activity receives the material release confirmation, they shall generate the 

required Shipment Advice 856S transaction at the AIN level for the assemblage. 

(b) MILS-Compliant supply systems. 
11 

• The Material Release Order/Disposal Release Order/Redistribution 

Order 940R (A2_/A5_/A5J/A4_) transformed from the MILS release order will be the single line 

item for the entire assemblage as a single unit. The transportation system shall incheck the 

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

shipment unit. The transportation control number should be derived from the AIN. When the 

Material Release Inquiry/Disposal Release Inquiry 940R (AF6/AFJ) and the Material Release 

Cancellation/Disposal Release Cancellation 940R (AC6/ACJ) are used as a follow-up request or 

cancellation request message, respectively, they shall be transacted at the AIN level.

• The Material Release Advice/Disposal Shipment Advice 945A, when 

serving as a status response or cancellation response message, shall be originated by the 

transportation system at the single line item transaction, comparable to the single line item 940R 

received from the supply system; it shall be transformed by DAASC into a single line MILS AE6 

transaction at the AIN level. When the Material Release Confirmation/Disposal Release 

Confirmation 945A is used as a shipment status message, the transportation system shall 

originate the transaction at the single line item level, comparable to the single line item 940R 

received from the retail supply system; it shall be transformed by DAASC into individual MILS 

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

in the W12 subloop.

(5) Changes to the DLMS Supplement Warehouse Shipping Order, 940R, and 

Warehouse Shipping Advice, 945A are identified in the tables below. 

(6) DAAS map changes will be required based on the contents of this PDC. 

(7) These new processes shall be added to DoD 4000.25-M, Volume 3, 

Transportation, and the DoD 4000.25-M-1, MILSTRIP. See attachments for specific details. 

# Locatio

n 

Revision to 

4030 940R, Material Release 

Reason for Change 

1 DLMS 

Introduct

ory note 

_ 

Add ADC 316 to DLMS introductory note 6:

- ADC 316 Transportation Supply Receipt and Acknowledgement 

To identify changes in 

the DS. 

2 1/W050

6/0200 

Add new DLMS Notes:

NB Material Release Inquiry 

DLMS Note: 

1. Use to inquire (follow-up) about the status of an open 

material release action. 

2. For inquiry on a material 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 material release orders, the inquiry will be at the 

document number level. DLMS enhancement; see 

To identify 

requirements for 

generation of release 

orders, follow-up 

requests, and 

cancellation requests 

for multi-packs and 

assemblages (e.g., 

medical). 
12 

introductory DLMS note 4f. 

NF Disposal Release Inquiry 

DLMS Note: 

1. Use to inquire (follow-up) about the status of open disposal 

release orders, shipment discrepancies at a DRMO, or receipt 

discrepancies at a DRMO. (Equates to MILSTRIP DI AFJ). 

2. For inquiry on a disposal 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 disposal release orders, the inquiry will be at the 

document number level. DLMS enhancement; see 

introductory DLMS note 4f.

2 1/W050

7/0200 

Add new qualifiers and DLMS Notes:

A6 Modified 

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. Applies to material release order (A2_/A5_)/disposal 

release order (A5J)/redistribution orders (A4_), material 

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

and material 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 = “1”. 

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 

To establish a unique 

action code for 

transactions 

supporting the Retail 

Transportation and 

Supply Interchange 

and to advise of 

special procedures 

apply as documented 

in DoD 4000.25-M, 

Vol 3, Chapter 2. 

To authorize the use of 

the N9/0900 segment 

to identify and 

repeated looping of 

the W01/0200 subloop 

to support multi-pack 

and medical 

assemblage 

processing. 

To authorize the use of 
13 

each of the document numbers contained within the multipack. 

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

multi-pack 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 = “1”. 

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/0900 is 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 = “1”. 

5. Cancellation requests for assemblages (e.g., medical) shall 

be at the AIN level. 

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

the N9/0400 segment 

to identify the lead 

document number for 

multi-packs or the 

Assemblage 

Identification Number 

for assemblages (e.g., 

medical) when 

transacting a followup request. 

3 1/N9/09

00 

Add new segment

Reference Identification 

Optional 

DLMS enhancement 

to enable reporting of 

multipack document 

number and its 

contents. 

4 1/N901/

0900 

Add new data element, qualifier and DLMS Note:

Reference Identification Qualifier 

M ID 2/3 Must Use 

Description: Code qualifying the Reference Identification. 

DLMS Note: Use only for multi-pack and assemblage (e.g., 

DLMS enhancement 

to enable reporting of 

multipack and 

assemblage (e.g., 

medical) document 

numbers and their 
14 

medical) release orders to identify the lead document number 

assigned and from which the transportation control number will 

be derived. When conducting an inquiry (follow-up) for multipacks or assemblages, the lead document number or AIN will be 

identified in the N9/0400. 

TN Transaction Reference Number 

DLMS Note: 

1. Must use to identify the transaction number assigned to a 

transaction. This is the document number. 

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

WF Locally Assigned Control Number 

DLMS Note: 

1. Use to identify the Assemblage Identification Number (AIN) 

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

contents. Note: TN 

and WF qualifiers 

carry the same DLMS 

usages as already 

authorized in the 

N901/0400. 

5 1/N902/

0900 

Add new data element

Reference Identification 

X AN 1/50 Must Use 

Description: Reference information as defined for a particular 

transaction set or as specified by the Reference Identification 

Qualifier. 

DLMS enhancement 

to enable reporting of 

multipack and 

assemblage (e.g., 

medical) document 

numbers and their 

contents. 

6 2/W01/0

200 

Add DLMS Note

W01 Line item detail – Warehouse 

DLMS Note: 

1. When the W0507 = “CN”, and the message supports a multiline release order in support of a multi-pack process, the W01 loop 

shall be repeated to provide the individual document numbers 

associated with the lead document number. When the W0507 = 

“ME”, and the message supports a multi-line release order in 

support of an assemblage, the W01 loop shall be repeated to 

provide the internal document numbers for each of the line items 

in an assemblage. 

2. When the W0506 = “NB” or “NF” and the W0507 = “CN”, the 

release inquiry (e.g., follow-up) shall be done at the lead document 

number level. When the W0506 = “NB” or “NF” and the W0507 

= “ME”, the release inquiry (e.g., follow-up) shall be done at the 

AIN level. 
15 

7 2/W010

1/0200 

Add DLMS Note.

Quantity Ordered 

DLMS notes: 

1. A field size exceeding 5 positions may not be received or 

understood by the recipient’s automated processing system. See 

introductory DLMS note 4d. 

2. When the W0506 = “NB” or “NF” and the W0507 = “CN” or 

“ME”, enter a value of “1” since inquiry is being done at the lead 

document number/AIN level. 

8 2/W010

2/0200 

Add DLMS Note.

Unit or Basis for Measurement Code 

DLMS notes: 

1. DLMS users see the Unit of Issue and Purchase Unit Conversion 

Table for available codes. 

2. When the W0506 = “NB” or “NF” and the W0507 = “CN” or 

“ME”, enter a value of “MX” since inquiry is being done at the 

lead document number/AIN level.

9 2/W010

4/0200 

Add DLMS Note.

ZZ Mutually Defined 

DLMS notes: 

1. Use to identify nonstandard material when all other authorized 

codes do not apply (includes management control numbers and 

locally assigned control numbers). May be used for DLSS-toDLMS conversion when the translator cannot determine a more 

appropriate code. 

2. When the W0506 = “NB” or “NF” and the W0507 = “CN” or 

“ME”, this is used to identify that the product inquiry is being 

done at the lead document number/AIN level. 

10 2/W010

5/0200 

Add DLMS Note.

Product/Service ID 

DLMS notes: 

When the W0506 = “NB” or “NF” and the W0507 = “CN” or 

“ME”, enter a value of “MIXED” since inquiry is being done at 

the lead document number/AIN level. 
16 

11 2/N901/

0400 

Add DLMS Notes.

TN Transaction Reference Number 

DLMS notes: 

 1. Must use to identify the transaction number assigned to a 

transaction. This is the document number. 

 2. For follow-up requests on multi-packs and assemblages 

(W0507 = “CN” or “ME”), enter the lead document number or 

Assemblage Identification Number, as applicable. No looping of 

the W01 subloop (Loop ID – 0310) is required. 

12 2/N901/

0400 

Add new qualifier and DLMS Note

 IA Internal Vendor Number 

DLMS Note: 

1. Use to identify the internal document number for the line 

item inside of assemblage (e.g., medical). 

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

DLMS enhancement 

to enable reporting of 

assemblage (e.g., 

medical) internal 

document numbers. 

13 2/FA102

/2900 

Add DLMS Note

A170 Adjustments 

DLMS Note: 

1. Use only for adjustments not specified by any other code. 

2. DLMS enhancement; see introductory DLMS note 4a. 

A520 Base Charge 

DLMS Note: 

1. Use for material charge only. 

2. DLMS enhancement; see introductory DLMS note 4a. 

C930 Export Shipping Charge 

DLMS Note: DLMS enhancement; see introductory DLMS note 

4a. 

D340 Goods and Services Charge 

DLMS Note: 1. Use for both material and related services. 

2. DLMS enhancement; see introductory DLMS note 4a. 

F060 Other Accessorial Service Charge 

DLMS Note: DLMS enhancement; see introductory DLMS note 

4a. 

F560 Premium Transportation 

DLMS Note: DLMS enhancement; see introductory DLMS note 

4a. 

Administrative 

correction. 
17 

I260 Transportation Direct Billing 

DLMS Note: 

1. Use for non-premium transportation 

2. DLMS enhancement; see introductory DLMS note 4a. 

R060 Packing, Crating, and Handling Charge 

DLMS Note: DLMS enhancement; see introductory DLMS note 

4a. 
18 

# Location Revision to 

4010 945A, Material Release Advice 

Reason for Change 

1 DLMS 

Introductor

y note 

Add ADC 316 to DLMS introductory note 5:

- ADC 316, Transportation Supply Receipt and Acknowledgement 

To identify changes in 

the DS. 

2 1/W0611/2

0 

Add new qualifier and DLMS Note:

NL Material Release Advice 

DLMS Note: 

1. Use to provide supply status on a material release order. 

(This corresponds to DLSS Document Identifier AE6). 

2. For supply status on a material release order by a 

transportation system to a retail supply system regarding 

multi-packs or assemblages (e.g., medical), status will be 

done at the lead document number (for multi-packs) and 

Assemblage Identification Number, AIN, (for assemblies). 

For single line material release orders, the status will be at 

the document number level. DLMS enhancement; see 

introductory DLMS note 3e. 

NO Notice 

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

provided by transportation to report cargo processing status 

(incheck or hold) prior to material release confirmation. This is 

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

follow-up requests. 

NQ Disposal Shipment Confirmation 

DLMS Note: 

1. Use to provide supply status to the ICP on a disposal release 

order. (This corresponds to DLSS Document Identifier 

AEJ.) 

2. For supply status on a disposal release order by a 

transportation system to a retail supply system regarding 

multi-packs or assemblages (e.g., medical), status will be 

done at the lead document number (for multi-packs) and 

Assemblage Identification Number (for assemblies). For 

single line disposal release orders, the status will be at the 

document number level. DLMS enhancement; see 

introductory DLMS note 3e.

NR Material Release Cancellation Advice 

DLMS Note: Use to provide status taken on a request to cancel a 

material release order. (This corresponds to DLSS Document 

Identifier AG6). 

Add capability for 

generation of a 945A 

supply status response, 

without prompting by 

a 940R follow-up 

request. 

Administrative 

correction for DLMS 

note associated with 

code “NR”. Change 

“A6_” to read “AG6”.
19 

3 1/W0612/2

0 

Add new qualifier and DLMS Note:

A6 Modified 

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. Applies to solicited and unsolicited material release inquiry 

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

status and cancellation responses, material 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 = “1”. 

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 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 = “1”. 

4. Cancellation responses for multipacks shall be at the single 

line level. 

5. 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 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 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 = “1”. 

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

To establish a unique 

action code for 

transactions 

supporting the Retail 

Transportation and 

Supply Interchange 

and to advise of 

special procedures 

apply as documented 

in DoD 4000.25-M, 

Vol 3, Chapter 2. 

To authorize the use of 

the N9/0900 segment 

to identify and 

repeated looping of 

the W01/0200 subloop 

to support multi-pack 

and assemblage (e.g., 

medical) processing. 
20 

shall be at the AIN level. 

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

4 2/W12/20 Add DLMS Note:

DLMS Note: 

1. If the transportation control number (TCN) is partialled 

(e.g., record position 16 is an alpha character other than 

“X”) by the shipper, then repeat the W12 loop to identify 

each related partial TCN (e.g., record positions 1-15 are 

identical). 

2. DLMS enhancement; see introductory DLMS note 3e. 

Add capability to 

identify related 

partialled TCNs by 

looping the W12 

segment. 

5 2/W1207/2

0 

Modify DLMS Note: 

ZZ Mutually Defined 

DLMS note: 

1. Use to identify nonstandard material when all other 

authorized codes do not apply (includes management control 

numbers and locally assigned control numbers). May be 

used for DLSS-to-DLMS conversion when the translator 

cannot determine a more appropriate code. 

2. Use when the W0612 = “CN” or “ME” and the LQ02 = 

“1” for (LQ01 = “AK”) to denote the consolidation as 

“MIXED” in the W1208.

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

Provide capability to 

define consolidation as 

mixed. 

6 2/G6201/5

0 

Modify DLMS Note: 

17 Estimated Delivery Date 

DLMS note: 

Use in material release advice (DIC AE6), material release 

confirmation, disposal shipment confirmation (DIC AEJ), 

historical material release confirmation, disposal release 

confirmation, and historical disposal release confirmation 

transactions to identify the estimated shipping date or estimated date 

material will be available for shipment when shipment has not 

occurred. 

Administrative 

correction.

7 2/LQ01/10

0 

Revise wording of DLMS Note:

BC Transportation Holding Delay Code 

DLMS Note: 

1. Use for material release confirmation, historical material release 

confirmation, and historical disposal release confirmation 

transactions to identify the reason shipment has been delayed. 

2. Use for supply status response either self-initiated by 

Add capability to use 

the transportation 

holding delay code 

when transportation 

self-initiates a supply 

status message to 

provide cargo status 

details. 
21 

transportation or in response to a follow-up request to identify the 

reason shipment has been delayed. 

5. REASON FOR CHANGE: The changes are proposed to standardize a retail supplytransportation electronic interface in order to provide intransit visibility and accountability of all 

government assets being shipped within the Defense Transportation System (DTS). In addition, 

the transactions will provide end-users an electronic method of obtaining shipment data and 

status codes on specific line items upon inquiry. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: This interface will provide a bi-directional exchange of shipment data 

transactions between retail supply and transportation systems. Adding these capabilities to the 

transaction sets will improve asset visibility throughout the transportation processing and 

movement cycle while decreasing cargo movement processing times. The changes will also 

allow the supply and transportation activities to communicate in the clear status information 

electronically on each line item. The proposed changes to the supplements enable DLMScompliant system to use extended DLMS enhancements that would not otherwise be available in 

a MILS environment; while MILS-based supply systems will be able to interface with 

transportation, through transformation of data by DAASC. 

b. Disadvantages: N/A 

7. Impact:

a. CMOS to implement DLMS-compliant Warehouse Shipping Order, 940R, and 

Warehouse Shipping Advice, 945A. 

b. DMLSS, GCSS-MC, and ECSS to implement DLMS-compliant Warehouse Shipping 

Order, 940R, and Warehouse Shipping Advice, 945A. 

c. SBSS to implement MILS equivalent messages to the Warehouse Shipping Order, 940R, 

and Warehouse Shipping Advice, 945A. 

d. DAASC to update maps and be able to distinguish which EDI to transform to MILS and 

which to route as an EDI transaction code based on the action code in the headers of the 

Warehouse Shipping Order, 940R, and Warehouse Shipping Advice, 945A. 

e. Transportation offices implementing this interchange will need to obtain Routing 

Identification Codes (RIC) from DAASC. If trading partner is a MILS-compliant system, then 

RIC is the only authorized code to be inserted in the transaction. 

f. Retail transportation and supply systems implementing this interchange will need to 

coordinate with DAASC to establish trading partner profiles identifying DLMS or MILS 
22 

capability for each respective system and determine if RIC or DODAAC will be used to identify 

the transportation office either receiving or transmitting the transaction. 

g. DAASC to confirm that use of Distribution code = “1” is unused in last six months. Per 

MILSTRIP AP2.12, it is marked as “Reserved for assignment by the DOD MILSTRIP System 

Administrator”. 
23 

Attachments: 

1. DoD 4000.25-M, Volume 3, Transportation, Chapter 2 

2. DoD 4000.25-1-M, MILSTRIP, Appendix 2.12 

3. DoD 4000.25-1-M, MILSTRIP, Appendix 2.16 

4. DoD 4000.25-1-M, MILSTRIP, Appendix 2.1 

5. DoD 4000.25-1-M, MILSTRIP, Appendix 3.10 

6. DoD 4000.25-1-M, MILSTRIP, Chapter 2 

7. DoD 4000.25-1-M, MILSTRIP, Chapter 3 

8. DoD 4000.25-1-M, MILSTRIP, Chapter 4 
C2-1 CHAPTER 2 

C2. CHAPTER 2

RETAIL TRANSPORTATION AND SUPPLY

INTERCHANGE

(STOCK AND NON-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. 

This interchange creates a virtual warehouse between supply and transportation by 

standardizing a supply-transportation interchange and provides intransit 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. The information described in this section implements a 

standardized interchange between retail transportation and supply through the use of 

EDI transactions. 

 C2.2.1. STOCK SHIPMENTS. For material requirements processed using 

standard MILSTRIP and DLMS procedures, the standardized interchange employs the 

940R (Warehouse Shipping Order) and 945A (Warehouse Shipping Advice). This 

standard provides retail supply systems the ability to pre-position 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 material release confirmation messages to supply when the 

material has shipped. 

 C2.2.2. NON-STOCK SHIPMENTS. Reserved for future use. 

C2.3. STOCK SHIPMENT PROCEDURES. 

 C2.3.1. SUPPLY AND TRANSPORTATION SYSTEMS. Initially there are five 

Automated Information Systems (AIS) that are expected to 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 

Standard Base Supply System (SBSS) which represent the supply systems for their 

respective business areas. The Cargo Movement Operations System (CMOS) 
C2-2 CHAPTER 2 

represents the transportation system. Systems other than those mentioned in this 

document, planning to use these standardized interchange transactions to implement a 

similar capability must coordinate with DLMSO and United States Transportation 

Command (USTRANSCOM) prior to attempting to implement the interchange. 

 C2.3.2. RETAIL SUPPLY ACTIVITY. This section provides general procedures 

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

activity for further shipment. 

 C.2.3.2.1 Pre-positioned Release Order. For designated supply trading 

partners, DAAS shall transmit copies of the Material Release Order/Disposal Release 

Order/Redistribution Order 940R (A2_/A5_/A5J/A4_) transactions to the designated 

transportation system to be pre-positioned awaiting actual arrival of cargo from the 

supply warehouse. 

 C2.3.2.2. Delivery and Incheck. The supply activity will make local deliveries 

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

inchecked by the transportation activity based on the cargo and the documentation 

received from the supply activity. 

 C2.3.2.3. Shipment Documentation. The material 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). DoD 4000.25-1-M, 

Military Standard Requisitioning And Issue Procedures (MILSTRIP) Manual, Chapter 5, 

Release and Receipt of Materiel, documents procedures for the use and generation of 

the IRRD. 

 C2.3.2.4. Follow-up Requests. The supply system will initiate a Material 

Release Inquiry/Disposal Release Inquiry 940R (AF6/AFJ) message for follow-up 

requests. Based upon elapsed time from either the initial release of the material release 

order/disposal release order/redistribution order or the estimated shipping date from the 

material release advice/disposal shipment advice, the supply system will initiate the 

inquiry using normal follow-up procedures as documented in DoD 4000.25-1-M, 

Chapter 2, paragraph C2.13; the only exceptions relate to multi-packs (see DoD 

4000.25-M, Volume 3, Chapter 2, paragraph C2.3.6) and assemblages, e.g., medical 

(see DoD 4000.25-M, Volume 3, Chapter 2, paragraph C2.3.7). 

 C2.3.2.5. Cancellation Requests. The supply system will initiate a Material 

Release Cancellation/Disposal Release Cancellation 940R (AC6/ACJ) message for 

cancellation requests. DoD 4000.25-1-M, Chapter 2, paragraph C2.17 prevails; the only 

exceptions relate to multi-packs (see DoD 4000.25-M, Volume 3, Chapter 2, paragraph 

C2.3.6) and assemblages, e.g., medical (see DoD 4000.25-M, Volume 3, Chapter 2, 

paragraph C2.3.7). 
C2-3 CHAPTER 2 

 C2.3.2.6. Shipment Status Message. When the retail supply activity receives 

the material release confirmation for a multi-pack, they shall associate it with all the 

document numbers that were contained in the initial material release order, generate 

the required Shipment Advice 856S (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 material release confirmation for an 

assemblage (e.g., medical), they shall generate the required Shipment Advice 856S 

shipment status transaction at the Assemblage Identification Number (AIN) level. For 

all material release confirmations, the retail supply activity shall insert the original 

distribution code assigned to the material 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.3. SERVICING TRANSPORTATION ACTIVITY. This section provides 

general procedures for servicing transportation activities, upon local delivery of items for 

shipment (received from retail supply). 

 C2.3.3.1. Incheck. Upon local delivery of the item (from retail supply) to the 

transportation activity customer service area, transportation personnel shall incheck the 

items as follows: 

 C.2.3.3.1.1. Either scan the DD Form 1348-1A IRRD using a handheld 

or manually incheck the document numbers into the transportation system. 

 C2.3.3.1.2. Generate a Material Release Advice/Disposal Shipment 

Advice 945A (AE6/AEJ) incheck status message and send it to the supply activity 

electronically. 

 C2.3.3.2. Hold Status. Subsequent to incheck and prior to material release 

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

Release Advice/Disposal Shipment Advice 945A (AE6/AEJ) status messages shall be 

sent by transportation to supply. 

 C2.3.3.3. Status/Follow-up Response. The transportation system shall 

respond to a follow-up request using the Material Release Advice/Disposal Shipment 

Advice 945A (AE6/AEJ) supply status message. 

 C2.3.3.4. Cancellation Response. The transportation system shall generate 

the Material Release Advice/Disposal Shipment Advice 945A (AE6/AEJ) status 

message with applicable status code indicating acknowledgement of the cancellation 

requirements. 

 C2.3.3.5. Material Release Confirmation. After the shipment is processed 

and shipped, the transportation activity generates a Material Release 
C2-4 CHAPTER 2 

Confirmation/Disposal Release Confirmation 945A material release confirmation and 

sends it to the supply activity, where the shipment status message will be generated 

and transmitted. 

 C2.3.4. DEFENSE AUTOMATIC ADDRESSING SYSTEM CENTER (DAASC) 

PROCESSING. DAASC shall route transactions between designated supply and 

transportation systems based on mutual agreements between the trading partners. 

This includes both DLMS-compliant and MILS-compliant systems. 

 C2.3.4.1. Cargo Movement Operations System (CMOS). CMOS shall be 

capable of receiving DLMS-compliant Warehouse Shipping Order 940R and 

transmitting Warehouse Shipping Advice 945A messages. 

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

DLMS-compliant, DAASC will process the transactions as follows: 

 C2.3.4.2.1. DLMS-Compliant Systems. If the supply system is DLMScompliant, DAASC shall not transform the transactions to/from MILS, based on 

established trading partner profiles held by DAASC. If the supply system is DLMScompliant and is exchanging information about multi-packs, the Warehouse Shipping 

Order 940R W0507 and Warehouse Shipping Advice 945A W0612 segments shall carry 

the action code of “CN”; for assemblages (e.g., medical), the Warehouse Shipping Order 

940R W0507 and Warehouse Shipping Advice 945A W0612 segments shall carry the 

action code of “ME”; for interchanges other than multi-packs and assemblages, the 

Warehouse Shipping Order 940R W0507 and Warehouse Shipping Advice 945A W0612 

segments shall carry the action code of “A6”. Additionally, the 940R and 945A shall have 

a distribution code of “1”. These action codes and the distribution code of “1” shall 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. MILS-Compliant Systems. If the supply system is MILScompliant, a distribution code of “1” shall be identified to denote the applicability of special 

procedures authorized under this Chapter. Normally DAASC shall transform the 

transactions to/from MILS based on existing maps, except when there is a distribution 

code of “1” in the Material Release Advice/Disposal Shipment Advice 945A messages 

from the transportation system. A distribution code of “1” authorizes the following actions: 

use of AE6/AEJ for unsolicited supply status responses by the transportation system, use 

of transportation hold and delay codes in the AE6/AEJ, rp51 by the transportation system 

in addition to its normal usage in the material release confirmation, and use of AE6/AEJ in 

lieu of the AG6/AGJ as a cancellation response by transportation system to facilitate 

usage of the supply status and transportation hold and delay codes. 
C2-5 CHAPTER 2 

 C2.3.5. RETAIL TRANSPORTATION AND SUPPLY INTERCHANGE. The 

following diagram shows the standard transactions that shall occur between retail supply 

and the transportation activity for the business processes covered in this chapter. 

Note: This process also applies to disposal transactions 

with their applicable DLMS qualifiers and DIC codes

Retail

Source

of Supply

AIS

Retail

TMO

AIS

1.Release Order

940R Material Release/Redistribution Order (W0506=NA/NI)

DIC=A4_/A5_/A2_

2. In-check/Hold Status

945A Material Release Advice (W0611=NO)

DIC=AE6

3a. Status Inquiry 3b. Status Response

940R Material Release Inquiry (W0506=NB)

DIC=AF6

945A Material Release Advice (W0611=NL)

DIC=AE6

4a. Order Cancellation 4b. Order Cancellation Response

940R Material Release Cancellation (W0506=ND)

DIC=AC6

945A Material Release Advice (W0611=NL)

DIC=AE6

5. Shipment Notification

945A Material Release Confirmation (W0611=NJ)

DIC=AR_

Figure 1 – Retail transportation and supply Data Interchange 

 

 C2.3.5.1. DLMS and MILS Transaction Designations. To denote a transaction 

is in support of the Retail Transportation and Supply Receipt and Acknowledgement 

Interchange, it shall 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. EDI 940R W0507 = “A6” 
C2-6 CHAPTER 2 

 C2.3.5.1.1.2. EDI 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. EDI 940R W0507 = “CN” and the EDI 

945A W0612 = “CN” 

 C2.3.5.1.2.2. Assemblages. EDI 940R W0507 = “ME” and the EDI 

945A W0612 = “ME” 

 C2.3.5.1.3. Distribution Code. 

 C2.3.5.1.3.1. EDI 940R and EDI 945A LQ01 = “AK” and LQ02 = “1” 

 C2.3.5.1.3.2. MILS distribution code = “1” 

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

trading partners, DAASC shall transmit copies of the Material Release Order/Disposal 

Release Order/Redistribution Order 940R (A2_/A5_/A5J/A4_) transactions to the 

designated transportation system to be pre-positioned awaiting actual arrival of cargo 

from the supply warehouse. The applicable transactions can be readily identified by use 

of the distribution code = “1”. Additionally, the action code in the EDI 940R W0507 and 

the EDI 945A W0612 will be either “A6, “CN”, or “ME”. 

 C2.3.5.3. Receipt/In-check of cargo by Transportation. Upon physical 

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

Material Release Advice/Disposal Shipment Advice 945A (AE6/AEJ) supply status 

response message to notify the supply activity via DAASC that the property has been 

received. Since there was no initial Material Release Inquiry/Disposal Release Inquiry 

940R (AF6/AFJ) follow-up request prompting the status message, the X12 code of “NO” 

shall be inserted in the W0611 segment to denote that this is being used by transportation 

to report cargo processing status prior to material release confirmation and a code of “A6” 

shall be inserted in the W0612 segment to denote that the supply status response is part 

of the Retail Transportation and Supply Receipt and Acknowledgement Interchange . To 

facilitate mapping of the Material Release Inquiry/Disposal Release Inquiry 945A to a 

MILS AE6/AEJ transaction, the distribution code shall carry a value of “1” to inform 

DAASC 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 material release confirmation where it 

normally is reported. If the material is subsequently placed into a transportation hold 

status, such as awaiting air clearance, a self-initiated Material Release Advice/Disposal 

Shipment Advice 945A supply status message shall be generated for every reportable 

status change, prior to shipment. The Material Release Advice/Disposal Shipment Advice 

945A W0611, LQ and G62 segment values for this step are as follows: 
C2-7 CHAPTER 2 

 C2.3.5.3.1. Incheck Reporting. To report in-check of cargo, W0611 = 

“NO” and W0612 = “A6”; LQ01 = “AK” and LQ02 = “1”; LQ01 = “81” and LQ02 = “BA”; 

G6201 = “17” and G6202 = estimated shipping date in CCYYMMDD format. 

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

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

LQ02 = “1”; LQ01 = “BC” and LQ02 = authorized code values from the Transportation 

Hold Code table located at the following web address: https://wwwtmds.c2.amc.af.mil/TMDS/dtr_index.xsql; G6201 = “17” and G6202 = estimated shipping 

date in CCYYMMDD format. 

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

Material Release Inquiry/Disposal Release Inquiry 940R (AF6/AFJ) message for follow-up 

requests to inquire on the status of a release order turned over to transportation for 

shipping; the W0507 segment shall 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 material release 

order/disposal release order/redistribution order or the estimated shipping date from the 

material release advice/disposal shipment advice, the supply system will initiate the 

inquiry using normal follow-up procedures, with communications via DAASC. The 

transportation system shall respond to a follow-up request with a Material Release 

Advice/Disposal Shipment Advice 945A supply status response message with an “A6” in 

the W0612 segment and the distribution code shall contain a “1” to denote that the supply 

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

Acknowledgement Interchange. The distribution code of “1” 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 material release confirmation where it normally 

is reported. The Material Release Advice/Disposal Shipment Advice 945A W0611, 

W0612, LQ and G62 segment values for this step are as follows: 

 C2.3.5.4.1. Material Release Order. 

 C2.3.5.4.1.1. W0611 = “NL” 

 C2.3.5.4.1.2. W0612 = “A6” 

 C2.3.5.4.1.3. LQ01 = “AK” and LQ02 = “1” 

 C2.3.5.4.2. Disposal Release Order. 

 C2.3.5.4.2.1. W0611 = “NQ” 

 C2.3.5.4.2.2. W0612 = “A6” 

 C2.3.5.4.2.3. LQ01 = “AK” and LQ02 = “1” 
C2-8 CHAPTER 2 

 C2.3.5.4.3. To report the applicable supply status code, LQ01 = “81” and 

LQ02 = authorized code values from DOD 4000.25-1-M, Appendix 2.16. Typical status 

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

processed for release and shipment (inchecked) or “BF” to denote that transportation has 

no record of the document for the follow-up request. When providing a “BA” status, 

G6201 = “17” and G6202 = estimated shipping date in CCYYMMDD format. 

 C2.3.5.4.4. To report a transportation hold and delay status, LQ01 = “AK” 

and LQ02 = “1”; LQ01 = “BC” and LQ02 = authorized code values from the Transportation 

Hold Code table located at the following web address: https://wwwtmds.c2.amc.af.mil/TMDS/dtr_index.xsql; G6201 = “17” and G6202 = estimated shipping 

date in CCYYMMDD format. 

 C2.3.5.5. Cancellation Requests and Responses. The supply system shall 

initiate an Material Release Cancellation/Disposal Release Cancellation 940R (AC6/ACJ) 

message when it wants to issue a cancellation request to the transportation system for 

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

W0507 segment shall carry an “A6” to denote that the cancellation request is part of the 

Retail Transportation and Supply Receipt and Acknowledgement Interchange. Normal 

cancellation request procedures shall apply. The transportation system shall respond to 

the cancellation request with a Material Release Advice/Disposal Shipment Advice 945A 

message, with an “A6” in the W0612 segment. The distribution code shall carry a value of 

“1” to inform DAASC of the use of the supply status response (MILS AE6/AEJ format) as 

part of the Retail Transportation and Supply Interchange. In addition to the distribution 

code “1” identifying the retail interface, it also authorizes the use of supply status codes, 

as a response to the cancellation request. The Material Release Advice/Disposal 

Shipment Advice 945A W0611, W0612 and LQ segment values for this step are as 

follows: 

 C2.3.5.5.1. Material Release Order. 

 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 = “1” 

 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 = “1” 
C2-9 CHAPTER 2 

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

the cancellation response, LQ01 = “81” and LQ02 = authorized code values from DOD 

4000.25-1-M, Appendix 2.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.6. Shipment Notification (Material Release Confirmation). Once the 

material is shipped, the transportation system shall initiate a Material Release 

Confirmation/Disposal Release Confirmation 945A (AR_) material release confirmation 

message to notify the supply system via DAASC that the material has shipped. The 

W0612 segment shall contain an “A6” and the distribution code = “1”. Upon receipt of the 

Material Release Confirmation/Disposal Release Confirmation 945A (AR_), the supply 

system shall transmit via DAASC the required Shipment Advice 856S (AS_) messages to 

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

system shall apply the original distribution code in lieu of the specially assigned code 

value of “1” in the shipment status messages. The Material Release 

Confirmation/Disposal Release Confirmation 945A W0611, W0612, and LQ segment 

values for this step are as follows: 

 C2.3.5.6.1. Material Release Order. 

 C2.3.5.6.1.1. W0611 = “NJ” 

 C2.3.5.6.1.2. W0612 = “A6” 

 C2.3.5.6.1.3. LQ01 = “AK” and LQ02 = “1” 

 C2.3.5.6.2. Disposal Release Order. 

 C2.3.5.6.2.1. W0611 = “NM” 

 C2.3.5.6.2.2. W0612 = “A6” 

 C2.3.5.6.2.3. LQ01 = “AK” and LQ02 = “1” 

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

partialled into multiple TCNs (e.g., alpha character other than “X” in record position 16), 

the W12 subloop 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 section provides 

procedures for use when processing multi-packs. 
C2-10 CHAPTER 2 

 C2.3.6.1. DLMS-compliant supply systems. 

 C2.3.6.1.1. Warehouse Shipping Order 940R. This 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 shall 

be carried in the W0507/0200 segment with a value “CN”. For material and disposal 

release orders and redistribution orders, the N9/0900 segment shall contain the lead 

document number assigned to the multi-pack, from which the transportation control 

number will be derived/assigned. The W01 (Loop ID 0310) shall be repeated for each 

document number associated with the multi-pack including the lead document number 

identified in N9/0900. For follow-up requests, the requests shall only be at the lead 

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

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

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

For cancellation requests, the requests shall contain the single line material release order 

document number, and the transportation system shall 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 DoD 4000.25-

1-M, C3.34-6. 

 C2.3.6.1.2. Warehouse Shipping Advice 945A. This 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 shall be 

carried in the W0507/0200 segment with a value “CN”. For status responses, the 

responses shall only be at the lead document number level, with it identified in the W12 

loop in the N9/0040 segment and the W1207 segment shall carry a “ZZ” with the word 

“MIXED” in the W1208 segment to denote an multi-pack with mixed commodities. For 

cancellation responses, the response shall be at the single line document number level. 

For material release confirmation when the multi-pack is not partialled into multiple TCNs, 

the transaction shall be processed as a single line transaction with the TCN and the lead 

document number identified in the W12 subloop and the W1207 segment shall carry a 

“ZZ” with the word “MIXED” in the W1208 segment. If the multi-pack is partialled into 

multiple TCNs (e.g., alpha character other than “X” in record position 16), the W12 

subloop shall 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 multi-pack identified in the 

N9/0040 segment and the W1207 segment shall carry a “ZZ” with the word “MIXED” in 

the W1208 segment. When the retail supply activity receives the material release 

confirmation, they shall associate it with all the document numbers that were contained in 

the initial material release order, generate the required Shipment Advice 856S Shipment 

Status transactions for the multi-pack, and transmit to DAAS for distribution per existing 

procedures and trading partner profiles. 

 C2.3.6.2. MILS-Compliant Supply Systems. 
C2-11 CHAPTER 2 

 C2.3.6.2.1. Warehouse Shipping Order 940R. This will be transformed by 

DAASC from the MILS release order into a single line item order, as it is normally done 

today. The transportation system shall incheck the multi-pack by either scanning or 

manually loading the lead document number; the transportation operator will then have to 

read the individual DD1348-1A contained within the pack list to incheck the items 

individually and associate them to the lead document number. The TCN shall be derived 

from the lead document number. For follow-up and cancellation requests, the requests 

shall contain the single line material release order document number. For cancellations, 

the transportation system shall 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 DoD 4000.25-1-M, C3.34.6. 

 C2.3.6.2.2. Warehouse Shipping Advice 945A. For status and 

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

the single line item transaction, comparable to the single line item 940R received from the 

supply system; it shall be transformed by DAASC into a single line MILS AE6/AEJ 

transaction at the material release order document number level. For material release 

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

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

DAASC shall transform the message into individual MILS equivalent AR_ transactions 

with the appropriate TCN (or partial TCN) mapped to the document numbers cited in the 

W12 subloop. 

 C2.3.7. ASSEMBLAGE (e.g.., MEDICAL) PROCESSING PROCEDURES. This 

section provides procedures for assemblage processing and the associated transactions 

between supply and transportation for shipment requirements. Refer to DoD 4000.25-M, 

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. Warehouse Shipping Order 940R. This 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 shall be carried in the W0507/0200 segment with a value 

“ME”. The N9/0900 segment will contain the AIN assigned to the assemblage, from 

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

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

assemblage, with the information associated with the AIN being the first loop. For followup and cancellation requests, the requests shall only be at the AIN level, no looping of the 

W01 is required; however, the following values shall 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-12 CHAPTER 2 

 C2.3.7.1.2. Warehouse Shipping Advice 945A. This 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 shall be carried in the 

W0612/0200 segment with a value “ME”. For status and cancellation responses, the 

responses shall only be at the lead AIN level, with it identified in the W12 loop in the 

N9/0040 segment and the W1207 segment shall carry a “ZZ” with the word “MIXED” in 

the W1208 segment to denote an assemblage with mixed commodities; no looping of the 

W12 is required. For material release confirmation when the assemblage is not partialled 

into multiple TCNs, the transaction shall be processed as a single line transaction with the 

TCN and the AIN identified in the W12 subloop and the W1207 segment shall carry a “ZZ” 

with the word “MIXED” in the W1208 segment. If the assemblage is partialled into 

multiple TCNs (e.g., alpha character other than “X” in record position 16), the W12 

subloop shall 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 segment shall carry a “ZZ” with the word “MIXED” in the W1208 segment. 

When the retail supply activity receives the material release confirmation, they shall 

generate the required Shipment Advice 856S shipment status transaction at the AIN level 

for the assemblage. 

 C2.3.7.2. MILS-compliant supply systems. 

 C2.3.7.2.1. Warehouse Shipping Order 940R. This shall be transformed 

by DAASC from the MILS release order into a single line item for the entire assemblage 

as a single unit. The transportation system shall incheck the assemblage by scanning or 

manually loading the AIN and processes the assemblage as a single shipment unit. The 

TCN shall be derived from the AIN. For follow-up and cancellation requests, the requests 

shall only be at AIN level, no looping of the W01 is authorized. 

 C2.3.7.2.2. Warehouse Shipping Advice 945A. For status and 

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

the single line item transaction, comparable to the single line item 940R received from the 

supply system; it shall be transformed by DAASC into a single line MILS AE6/AEJ 

transaction at the AIN level. For material release confirmations, the transportation system 

shall originate the transaction at the single line item level, comparable to the single line 

item 940R received from the retail supply system; DAASC shall transform the message 

into individual MILS equivalent AR_ transactions with the appropriate TCN (or partial 

TCN) mapped to the AIN cited in the W12 subloop. 

C2.4. NON-STOCK SHIPMENTS. Reserved for future use.
 DoD 4000.25-1-M, October 2007 

AP2.12-2 APPENDIX 2.12 

AP2.12. APPENDIX 2.12

DISTRIBUTION CODES

AP2.12.3. Numeric Distribution Codes. Current use of numeric distribution codes are as 

follows: 

CODE USE

1 For use in support of the Retail Transportation and Supply Receipt and Acknowledgement 

Interchange (See DoD 4000.25-M, Volume 3, Chapter 2) 

2 For use by IMMs to identify transactions associated with lateral redistribution of DoD 

consumable assets 

3 For use by IMMs to identify transactions associated with lateral redistribution of DoD 

reparable assets 

4 Use for DoD EMALL requisitions 

5 Reserved for assignment by the DoD MILSTRIP System Administrator 

6 Inter-Component use with the Navy Service Codes N, V, and R 

7 and 8 Inter-Component use with the transmission of MOV requests 

9 Defense Reutilization and Marketing Service 

Federal Center 

Battle Creek MI 49016-3412 
 DoD 4000.25-1-M, October 2007 

AP2.16-3 APPENDIX 2.16 

AP2.16. APPENDIX 2.16

STATUS CODES

REQUISITION TRANSACTION STATUS CODES 

CODE EXPLANATION

BA Item being processed for release and shipment. The ESD is contained in rp 70-73 

when provided in response to a follow-up. For status messages with a distribution 

code in rp54 = “1”, this status indicates that it is used in use in support of the Retail 

Transportation and Supply Receipt and Acknowledgement Interchange in response to 

follow-ups and for initial physical in-check of cargo from a retail supply warehouse 

to a transportation system for movement, etc. See DoD 4000.25-M, Volume 3, 

Chapter 2. 
 DoD 4000.25-1-M, October 2007 

AP2.1-7 APPENDIX 2.1 

AP2.1. APPENDIX 2.1

DOCUMENT IDENTIFIER CODES

DOCUMENT IDENTIFIER CODES

NUMBER OF CHARACTERS: Three 

TYPE OF CODE: Alpha/Numeric 

EXPLANATION: Provides means for identifying a transaction as to the 

system to which it pertains and further identifies such 

transaction as to its intended purpose and usage 

RECORD POSITION(S): 1 through 3 

CODE DOCUMENT TITLE EXPLANATION

AE6 Supply Status To ICP/IMM from storage or reporting activity in 

response to a DI AF6, DI AC6, DI A4_ with Distribution 

Code 2, or A5_, when a DI AR_ or AS6, does not apply. 

Also for use in support of the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange 

(transactions identified by a distribution code = “1”) 

from transportation to retail supply activity to provide 

status, unsolicited, with Distribution Code 1 to provide 

cargo incheck, hold/delay status, supply status, and 

cancellation responses (See DoD 4000.25-M, Volume 3, 

Chapter 2). 

AEJ Disposal Supply Status From storage activity to ICP. Also for use in support of 

the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange (transactions identified by 

a distribution code = “1”) from transportation to retail 

supply activity to provide status, unsolicited, with 

Distribution Code 1 to provide cargo incheck, hold/delay 

status, supply status, and cancellation responses ( See 

DoD 4000.25-M, Volume 3, Chapter 2). 
 DoD 4000.25-1-M, October 2007 

AP2.1-7 APPENDIX 2.1 

AC6 Cancellation From ICP/IMM to Storage Activity or Reporting 

Activity. Also for use in support of the Retail 

Transportation and Supply Receipt and 

Acknowledgement Interchange (transactions identified by 

a distribution code = “1”) from retail supply to 

transportation ( See DoD 4000.25-M, Volume 3, Chapter 

2). 

ACJ Disposal Release 

Cancellation 

From ICP to storage activity. Also for use in support of 

the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange (transactions identified by 

a distribution code = “1”) from retail supply to 

transportation ( See DoD 4000.25-M, Volume 3, Chapter 

2). 

AF6 Follow-up By ICP to storage or reporting activity. Also for use in 

support of the Retail Transportation and Supply Receipt 

and Acknowledgement Interchange (transactions 

identified by a distribution code = “1”) from retail 

supply to transportation ( See DoD 4000.25-M, Volume 

3, Chapter 2). 

AFJ Disposal Release 

Follow-up 

From ICP to storage activity. Also for use in support of 

the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange (transactions identified by 

a distribution code = “1”) from retail supply to 

transportation ( See DoD 4000.25-M, Volume 3, Chapter 

2). 
 DoD 4000.25-1-M, October 2007 

AP2.1-7 APPENDIX 2.1 

A2_ Redistribution Order For shipments as identified in paragraph AP2.1.6. Also 

for use in support of the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange 

(transactions identified by a distribution code = “1”) 

from retail supply to transportation ( See DoD 4000.25-

M, Volume 3, Chapter 2). 

A5_ Materiel Release Order For shipments as identified in paragraph AP2.1.6. Also 

for use in support of the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange 

(transactions identified by a distribution code = “1”) 

from retail supply to transportation ( See DoD 4000.25-

M, Volume 3, Chapter 2). 

A5J Disposal Release Order From ICP to storage activity (may also be used by local 

generating activity) as identified in paragraph AP2.1.6. 

Also for use in support of the Retail Transportation and 

Supply Receipt and Acknowledgement Interchange 

(transactions identified by a distribution code = “1”) 

from retail supply to transportation ( See DoD 4000.25-

M, Volume 3, Chapter 2). 

A4_ Referral Order/Lateral 

Redistribution Order for 

Retail Assets 

For shipments as identified in AP2.1.6. Also for use in 

support of the Retail Transportation and Supply Receipt 

and Acknowledgement Interchange (transactions 

identified by a distribution code = “1”) from retail 

supply to transportation ( See DoD 4000.25-M, Volume 

3, Chapter 2). 

AR_ Materiel Release 

Confirmation 

To ICP from storage. Also for use in support of the Retail 

Transportation and Supply Receipt and 

Acknowledgement Interchange (transactions identified by 

a distribution code = “1”) from retail supply to 

transportation ( See DoD 4000.25-M, Volume 3, Chapter 

2). 
 DoD 4000.25-1-M, October 2007 

AP2.1-7 APPENDIX 2.1 

ARJ Disposal Release 

Confirmation 

From storage activity to ICP. Also for use in support of 

the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange (transactions identified by 

a distribution code = “1”) from retail supply to 

transportation ( See DoD 4000.25-M, Volume 3, Chapter 

2). 
DoD 4000.25-1-M, October 2007 

AP3.10-1 APPENDIX 3.10 

AP3.10. APPENDIX 3.10

SUPPLY STATUS

(ISSUES FROM STOCK)

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DI AE_. 

Routing Identifier 4-6 Enter RI of the supply source furnishing the 

supply status (RI From). If used as a DI AE6 

transaction, enter the RI of the supply source to 

which the transaction will be sent (RI To).1

Media and Status 7 Enter M&S as shown in the original requisition. 

Stock or Part Number 8-22 Enter NSN or part number. 

Unit of Issue 23-24 Enter U/I. 

Quantity 25-29 a. Enter quantity for which status is provided. 

b. For ammunition items only (FSG 13), enter an 

“M” in rp 29 to express in thousands any quantity 

exceeding 99,999. Example: A quantity of 

1,950,000 will be expressed as 1950M (1950 in 

rp 25-28 and an “M” in rp 29). 

Document Number 30-43 Enter document number as shown in the 

requisition. 

Suffix 44 a. Enter suffix applicable to quantity in rp 25-29 

when the requisitioned quantity is divided into 

separate supply actions. 

b. When the requisition quantity is not divided, 

leave this field blank. 

Supplementary Address 45-50 Enter data from original requisition. 

Signal (Hold) 51 Enter data from original requisition.2

Fund 52-53 Enter date from original requisition. 

 

1

 When used by the Material Processing Center (MPC) to notify the Navy customer that material has 

arrived (NL Status) or been delivered (NW or Navy-unique BA Status), rp 4-6 will identify the MPC. 2

 If the Distribution Code in rp54 = “1”and the Status Code (rp 65-66) is blank, then rp 51 contains the 

Hold Code; if a Status Code is present, then rp 51 is the Signal Code. 
DoD 4000.25-1-M, October 2007 

AP3.10-2 APPENDIX 3.10 

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Distribution 54-56 When used as an AE6 to provide status on the 

processing on an LRO, enter 2 for consumables 

or 3 for reparables in rp 54. Otherwise, enter data 

as shown in the requisition.3

Project 57-59 Enter data from original requisition. 

Priority 60-61 Enter data from original requisition. 

Transaction Date 62-64 Enter the day that corresponds with the date of 

this reply. 

Status 65-66 Enter status code to convey the information 

regarding the status of this transaction. 

Routing Identifier 67-69 Enter the “last known source” to which 

authorized follow-up action will be directed. If 

used as a DI AE6 transaction, the RI will be the 

activity preparing the document.4

Estimated Shipping Date 70-73 When designated by the status code, enter the 

four-position ordinal day by which it is estimated 

the materiel will be shipped.5

Multiple Use6&7 74-80 

Unit Price 74-80 Enter unit price of the stock or part number 

shown in rp 8-22. When the status code in rp 65-

66 relates to an erroneously routed requisition, 

this field will be left blank. 

OR 

Blank (74-75) Leave blank. 

Minimum Order Quantity (76-80) For C8 Status, enter the minimum order quantity. 

OR 

Blank (74-75) Leave blank. 

 

3 When used by transportation and supply receipt and acknowledgement interchange, insert Distribution 

Code = “1” 

4

 When used by the Material Processing Center (MPC) to notify the Navy customer that material has 

arrived (NL Status) or been delivered (NW or Navy-unique BA Status), rp 67-69 will repeat the 

identification of the MPC. 

5

 When used by the MPC, this will be the date associated with the material arrival (NL Status) or delivery 

(NW or Navy-unique BA Status). 

6

When used by storage in response to a query by the ICP (DI AE6), this data may be omitted at Component option. 

7

DI AE9 transactions generated by DAAS will always be blank in rp 74-80. 
DoD 4000.25-1-M, October 2007 

AP3.10-3 APPENDIX 3.10 

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Federal Supply 

Schedule Number8

(76-80) For DA Status, enter Federal Supply Schedule 

Number constructed as follows: 

rp 76-77 Group (numeric) rp 78-79 Part 

(numeric) rp 80 Section (alphabetic). 

For DI AE6 Transactions with Status Code BY

 70-71 Leave blank. 

 72 

If status code (rp 65-66) is BY (previously 

denied MRO), enter appropriate denial 

management code. 

 73 Leave blank. 

Unit Price9 74-80 Enter unit price of the stock or part number 

shown in rp 8-22. 

For DI Code AE_ Transactions with Status Code CE

 79-80 

For transactions containing rejection Status 

Code CE in rp 65-66, supply source will enter 

the correct unit of issue in rp 79-8010. 

For DI Code AE_ Transactions with Status Code BD (Army only)

Management Code 72 If status code (rp 65-66) is BD enter denial 

Management Code R, indicating a denial/refusal 

to the Standard Army Retail Supply System 

(SARSS) operating under Army Single Stock 

Fund. 

For DI AE6 Transactions with Status Code BY

 70-71 Leave blank. 

Management Code 72 If status code (rp 65-66) is BY (previously 

denied MRO), enter appropriate denial 

 

8

Requirement to use DA requisition rejection status to indicate the supply source is direct ordering from 

the Federal Supply Schedule last reported as not implemented by USAF. Refer to AMCL 132B. 

9

When used by storage in response to a query by the ICP (DI AE6), this data may be omitted at Component option. 

10Requirement to provide correct unit of issue when original unit of issue on the requisition could not be converted 

last reported as not implemented by USN and DLA (Subsistence). Refer to AMCL 162. 
DoD 4000.25-1-M, October 2007 

AP3.10-4 APPENDIX 3.10 

management code. 

 73 Leave blank. 

Unit Price11 74-80 Enter unit price of the stock or part number 

shown in rp 8-22. 

 

For DI AE6 Transactions with Distribution Code 2 and Status Code CB (Army/DLA Interface Only)

Management Code 72 If status code (rp 65-66) is CB enter 

Management Code S, indicating LRO under 

TAV procedures was denied because it matched 

an existing suffix for the document number. 

 

11When used by storage in response to a query by the ICP (DI AE6), this data may be omitted at Component option. 
DoD 4000.25-1-M, October 2007 

C2-1 CHAPTER 2 

C2. CHAPTER 2 

PREPARATION AND SUBMISSION OF REQUISITIONS, 

CANCELLATIONS, AND FOLLOW-UPS

C2.13 FOLLOW-UPS

 C2.13.1 Follow-ups should be submitted by the requisitioner, SUPADD, or the activity 

designated by a significant entry in rp 54, based on a need for information and criteria prescribed 

herein. For retail transportation and supply activities participating in the supply receipt and 

acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, follow-ups 

should be submitted to the servicing transportation activity in accordance with normal supply 

procedures, with the exception of follow-ups for multi-packs and assemblages (e.g., medical), 

which will be executed at the lead document number, Assemblage Identification Number (AIN) 

respectively.

C2.17 CANCELLATION OF REQUISITIONS

 C2.17.1 Cancellation of requisitions may be initiated by the requisitioner, the SUPADD, 

the activity designated by the entry in rp 54, S/A headquarters, or by authorized command 

elements. If cancellations are initiated by other than the requisitioner, the responsibility for 

advising other interested activities of this action is vested in the activity having initiated the 

cancellation. Cancellation requests can be initiated as single line transactions or by narrative 

message containing one or more single line cancellation transactions. For retail transportation 

and supply activities participating in the supply receipt and acknowledgement interchange, 

documented in DoD 4000.25-M, Volume 3, Chapter 2, cancellation requests shall be submitted 

to the servicing transportation activity in accordance with normal supply procedures, with the 

exception of cancellation requests for assemblages (e.g., medical), which will be executed at the 

Assemblage Identification Number (AIN).
DoD 4000.25-1-M, October 2007 

C3-1 CHAPTER 3 

C3. CHAPTER 3

REQUISITION PROCESSING AND RELATED ACTIONS

C3.1. GENERAL

 C3.1.1. Supply sources receiving MILSTRIP requisitions, modifiers, passing orders, 

referral orders, follow-ups, RDOs, and cancellations, regardless of the method of transmission, 

will process such transactions using these procedures. Supply sources will validate the data 

elements and codes in these transactions and accomplish changes, continue the processing action, 

or reject12 the documents, as indicated in Figure C3-1. See AP2.16 for appropriate requisition 

transaction status codes. For retail transportation and supply activities participating in the 

supply receipt and acknowledgement interchange, see DoD 4000.25-M, Volume 3, Chapter 2, for 

special procedures associated with requisition processing.

C3.15. PREPARING MATERIEL RELEASE ORDERS

C3.15.3. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, 

copies of material release orders shall be submitted to the servicing transportation activity to 

pre-position supply information to facilitate automated check-in of cargo into transportation.

C3.16. MATERIEL RELEASE CONFIRMATION

 C3.16.5. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, the 

supply activity shall receive a material release confirmation from the servicing transportation 

activity to document release of the shipment by transportation. The supply activity will process 

this transaction and provide notice to the supply source of the action. 

C3.21. PROCESSING FOLLOW-UPS

C3.21.16. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, follow-up processing shall be done in accordance with 

normal supply procedures, except as documented in DoD 4000.25-M, Volume 3, Chapter 2.

C3.23. PROCESSING REDISTRIBUTION ORDERS 

C3.23.4. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, 

copies of redistribution orders shall be submitted to the servicing transportation activity to preposition supply information to facilitate automated check-in of cargo into transportation. 

 

12Rejection of transactions will be accomplished only after an attempt has been made to correct the 

questionable data element or code. If rejection actions are applicable to more than one data element or 

code and no other reject status code applies, reject using Status Code CA. 
DoD 4000.25-1-M, October 2007 

C3-2 CHAPTER 3 

C3.33. SUPPLY SOURCE SUBMISSION OF SINGLE LINE CANCELLATION/ 

DIVERSION REQUESTS TO STORAGE ACTIVITIES 

C3.33.8. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, 

cancellation requests shall be submitted to the servicing transportation activity in accordance 

with normal supply procedures.

C3.34. STORAGE ACTIVITY PROCESSING OF SINGLE LINE CANCELLATION/ 

DIVERSION REQUESTS 

C3.34.11. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, 

cancellation requests shall be submitted to the servicing transportation activity in accordance 

with normal supply procedures.

C3.39 DIRECTING MATERIEL TO THE DEFENSE REUTILIZATION AND MARKETING 

SERVICE13

 C3.39.3. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, 

copies of disposal release orders shall be submitted to the servicing transportation activity to 

pre-position supply information to facilitate automated check-in of cargo into transportation.

 

13 See Footnote 27. 
DoD 4000.25-1-M, October 2007 

C4-1 CHAPTER 4 

C4. CHAPTER 4

STATUS

C4.1. GENERAL

 C4.1.1. The MILSTRIP System requires that supply sources or MCAs provide status data 

to designated activities as notice of action taken or being taken on MILSTRIP transactions 

received, using status codes in AP2.16. Activities to receive status data and the type of data 

required are designated by entry of an M&S in rp 7 (see AP2.4). A significant distribution code 

in rp 54 also designates monitoring/control offices to receive all status data. In addition to 

supply sources furnishing status, the DAAS also generates status in selected situations as a result 

of editing the stock number field of requisitions. The DAAS status is furnished using the unique 

DI of AE9 and the DAAS RI (from) is cited in these transactions. 

 C4.1.2. Status data is either “supply status” or “shipment status,” prepared by supply 

sources in the applicable format shown in the “3” series appendices. Status data may be 

informational, or require additional action by recipients based on the status code in the 

transaction. 

 C4.1.3. Status transactions from supply sources will be forwarded to DAAS for 

transmission to status recipients. DAAS will transmit status as indicated in AP2.4. 

 C4.1.4. DAAS will pass DI AFY transactions (requests for DoDAAC information) to the 

RI indicated in rp 4-6. DAAS will route DI ASY response transactions containing DoDAAC 

information, without changing the DI, to all eligible status recipients (rp 30-35, 45-50, and 54).14

C4.1.5. For retail transportation and supply activities participating in the supply receipt 

and acknowledgement interchange, documented in DoD 4000.25-M, Volume 3, Chapter 2, status 

and cancellation responses shall be submitted by the servicing transportation activity to the 

supply activity. Supply activities are still responsible for normal status reporting requirements 

to requisitioners and supply sources. Note: Through use of distribution code “1”, special status 

and cancellation response procedures apply. See DoD 4000.25-M, Volume 3, Chapter 2 for 

details.

 

14 Procedures requesting and/or providing the DoDAAC of the initial shipping activity last reported as not 

implemented by DLA (Subsistence) and GSA. Refer to AMCL 5.