ADC 253 

DLMS Material Release Confirmation Enhancements: 

Secondary Transportation Number, Carrier Identification, and POE 

1. ORIGINATOR: 

 a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

 b. Sponsor: Supply PRC, Chair: Ellen Hilert, DLA DLMSO/J-6251, Defense Logistics 

Management Standards Office (DLMSO), 703-767-0676 (DSN 427), ellen.hilert@dla.mil 

2. FUNCTIONAL AREA: Supply 

3. REFERENCES: 

a. DLMSO memorandum dated May 30, 1996, subject: Revised Addendum to Approved 

MILSTRIP Change Letter (AMCL) 138, Revision of the Transportation Control Number (TCN) 

Field in MILSTRIP Transactions. This document provided the business rule update for inclusion 

of the TCN under MILSTAMP (later DTR) structure/rules in the material release confirmation 

and the shipment status transaction formats. 

 b. DLMSO memorandum dated March 19, 2007, subject: Approved Defense Logistics 

Management System (DLMS) Change (ADC) 223, DLMS Shipment Status Enhancements: 

Secondary Transportation Number, Initial Shipping Activity, Carrier Identification, and Port of 

Embarkation (POE). This change supports the implementation of DLMS enhancements to 

provide the secondary transportation number and carrier identification. It also documents correct 

DLMS mapping for the POE content. 

4. REQUESTED CHANGE:

 a. Description of Change: 

 (1) This change provides guidance for implementation of multiple enhancements to the 

DLMS Supplement 945A, Material Release Advise, for use as a Material Release Confirmation. 

This change specifically requests implementation of an enhancement identified during the 

development of the DLMS for a secondary transportation number and carrier identification. It 

also provides clarification on how DLMS handles identification of the Port of Embarkation 

(POE) (for air or water) or the Consolidation and Containerization Point (CCP) which are 

mapped to the same record positions in the MILS and may not be identifiable by code 

characteristics. Implementation of this change will permit the Inventory Control Point 

(ICP)/Source of Supply (SoS) to perpetuate the enhanced DLMS data content when responding 

to customer requests for status when applicable to shipment from Distribution Depots. 

(2) This change identifies ‘authorized DLMS migration enhancements’ for 

implementation by modernized systems under DLMS migration. This data should be adopted 

during, or subsequent to, modernization when applicable to the Component’s business process. 

Prior coordination is not required. Components should ensure that inclusion of this data in a 

DLMS transaction does not cause inappropriate rejection of the transaction. 
(3) This change also includes administrative changes to clarify mapping intent and usage 

instructions. 

 b. Procedures: Changes identified in bold italics.

 (1) Modify the DLMS manual, Vol 2, Chapter 4, as indicated below:

 C4.7.13. Material Release Confirmation (MRC)

 C4.7.13.1. Purpose. The MRC (DS to Federal IC 945A, Material Release Advice)

serves as advice from a storage site to the supply source that initiated the MRO of supply action 

taken. The MRC shall be provided using DLMS Supplement 945A. The MRC shall include 

enhanced data content under DLMS to include: 

 C4.7.13.1.1 Both the TCN, when applicable, and a secondary transportation 

number, such as the small package carrier number, when this is applicable. 

 C5.2.1.2.4 Identification of the carrier when other than United States Postal Service 

(USPS) by Standard Carrier Alpha Code (SCAC). 

 C5.2.1.2.4 For Outside Continental United States (OCONUS) shipments made via 

Defense Transportation System (DTS), GBL/CBL, parcel post, and small package carrier 

shipments, specific identification of the Port of Embarkation (POE) or Consolidation and 

Containerization Point (CCP). The MRC will specify air terminal, water terminal, or CCP by 

applicable qualifier code in the DS. (During MILS/DLMS transition, DAAS may substitute a 

generic terminal qualifier for MRC transactions converted from MILS where the type of 

facility is unknown.) 

(2) Adopt DLMS enhancements per the DS 954A, Material Release Advice, as specified 

in the enclosure. 

 

5. REASON FOR CHANGE: 

a. By agreement with the Supply Process Review Committee, DLMS enhancements are 

to be specifically addressed under the DLMS change (configuration management) process. This 

is necessary to ensure that enhancements identified during DLMS development are still valid. 

Associated procedures must be provided to ensure requirements are understood and 

institutionalized within DOD guidance. 

 

b. The purpose of this change is to improve the data content of the material release 

confirmation under DLMS implementation. The specific enhancements listed are known 

shortcomings of the current MILS format and will substantially improve access to information 

for the Inventory Control Point (ICP)/Source of Supply (SoS). The ICP/SoS will, in turn, be able 

to provide this information for Distribution Depot-shipped material in shipment status 

transactions provided as a result of follow-up status requests. 

 (1) Secondary Transportation Number: When DOD mandated that the 

17-position standard configuration for the transportation control number be reflected in the MILS 
shipment status, this eliminated the space needed to inform the customer of the actual 

transportation number used by the carrier (reference 3.a.). This is often a very useful piece of 

information to the customer, especially for shipment tracing. Inclusion of the secondary number, 

such as the FEDEX number or the registered mail number, in the original shipment status 

eliminates the need to research this information. In order for the SoS to perpetuate this 

information in shipment status, it must be provided in the MRC. 

 (2) Carrier Identification: This will facilitate more timely tracer action on 

urgently needed material, especially when the priority changes after shipment. Inclusion in the 

shipment status will reduce customer requests for this information. In order for the SoS to 

perpetuate this information in shipment status, it must be provided in the MRC. 

 (3) POE/CCP Codes: The intent of the DLMS is to use specific codes to 

indicate the CCP or POE when applicable for OCONUS shipments. This supports the DLMS 

data mapping philosophy and moves away from multi-purpose fields used in the MILS. 

Currently, it is not always possible to distinguish between the three-position codes for air and 

water terminal (air terminal codes are always 3 alpha characters, but water terminals may be all 

alpha or alphanumeric), so DLMS-capable systems must be able to receive any of the specific 

qualifiers for POE/CCP when the status is prepared by a DLMS-capable application, as well as 

the generic all-purpose code used for conversion from the original MILS transaction. 

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Supports DLMS migration. This change directs those systems having 

DLMS capability to adopt additional expanded data content. 

 (1) Provides transportation information to the organization that directed the 

shipment. This will allow the SoS to include transportation information in shipment status in 

response to customer’s inquiry. 

 (2) The adoption of the variable length records provides an opportunity to reinstatement of the original MILS requirement to identify various transportation numbers. This 

capability was lost with the implementation of AMSL 138 (reference 3.a.) due to space 

constraints. 

 (3) The use of the correct qualifiers for POE and CCP supports data integrity 

goals. Under the MILS it was not always possible to distinguish some codes based upon their 

code characteristics. 

 b. Disadvantages: None known. 

7. IMPACT: 

 a. This change impacts DLMS-capable application and those in the process of planning for 

migration. This change may be implemented on a phased and staggered basis without prior 

coordination with trading partners. DLMS-capable receiving applications which have not yet 

adopted these DLMS enhancements should verify that inclusion of the new data will not cause 

transactions to reject. 
 b. This change impacts the Defense Automatic Addressing System (DAAS), Global 

Transportation Network (GTN), and other applications maintaining a historical database and 

query capability so that additional data content may be saved and displayed appropriately. 

Carrier’s SCAC must be linked to carrier name and information. 

Enclosure 
Enclosure 1 - DS 945A, Material Release Confirmation 

Item Location Data Elements 

This is an extract reflecting only that content applicable to 

this change proposal. Changes are indicated by bold italics.

Comments/ 

Reason for Change 

1. cover Revise DLMS introductory note 5 to add this PDC:

5. This DLMS supplement (DS) incorporates the following 

Proposed DLMS Change (PDC) and Approved DLMS 

Changes (ADC) listed. 

PDC/ADCs are available from the DLMSO Web site: 

http://www.dla.mil/j-6/dlmso/Changes. 

- ADC 253, DLMS Material Release Confirmation 

Enhancements: 

Secondary Transportation Number, Carrier Identification, 

and POE

Identifies applicable DLMS 

changes 

2. 1/W0611/20 Revise DLMS notes for the following codes:

NJ Material Release Confirmation 

DLMS Note: Use to provide confirmation on a material 

release order. (This corresponds to DLSS Document 

Identifier ARA, ARB, AR0, AUA, AUB, or AU0) 

NK Material Release Denial 

DLMS Note: Use to provide denial (warehouse refusal) 

information on a material release order. (This corresponds to 

DLSS Document Identifier A6_, except A6J.) 

NL Material Release Advice 

DLMS Note: Use to provide supply status on a material 

release order. (This corresponds to DLSS Document 

Identifier AE6.) 

NM Disposal Release Confirmation 

DLMS Note: Use to provide confirmation on a disposal 

release order. (This corresponds to DLSS Document 

Identifier ARJ, ARK, or ARL.) 

NP Disposal Release Denial 

DLMS Note: Use to provide denial (warehouse refusal) 

information on a disposal release order. (This corresponds to 

DLSS Document Identifier A6J.) 

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 A6_, except A6J.) 

NT Disposal Release Cancellation Advice 

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

cancel a disposal release order. (This corresponds to DLSS 

Document Identifier AGJ.) 

Administrative revision for 

clarification of intended use. 
3. 2/W1201/20 Revise DLMS notes for the following codes:

SA Shipment Quantity Increase 

DLMS Note: Use with W0611 Code NJ (Material Release 

Confirmation) to indicate release of quantity greater than 

requested due to unit pack. Use with W0611 Code NM 

(Disposal Release Confirmation) to indicate release of 

quantity greater than requested. (This corresponds to DLSS 

Document Identifier ARA or ARK.) 

SC Shipment Quantity Decrease 

DLMS Note: Use with W0611 Code NJ (Material Release 

Confirmation) to indicate release of quantity less than 

requested due to unit pack. Use with W0611 Code NM 

(Disposal Release Confirmation) to indicate release quantity 

less than requested. (This corresponds to DLSS Document 

Identifier ARB or ARL.)

Administrative revision for 

clarification of intended use. 

4. 2/N901/40 Revise DLMS note for Code 4C as follows:

4C Shipment Destination Code 

DLMS Note: 1. Shipment Destination Code with note: "Use 

in Commercial Asset Visibility Material Release 

Confirmation transactions to provide a clear text carrier name 

and address. Use N902 to identify the carrier name. Use 

N903 to provide a street address, PO box or other address 

information. Use N907 to provide additional address 

information. Where possible, attempt to cite the address in 

the form of a US Postal Service (USPS) mailing address. For 

shipments outside the US, use 2/LQ01/100 code 85 to identify 

the country." 

2. This is a non-standard mapping. The standard DLMS 

mapping for carrier identification is carried in the N1 

segment at position 0310.

Administrative revision for 

clarification of intended use. 

5. 2/N907/40 Revise DLMS notes as follows:

08 Carrier Assigned Package Identification Number 

DLMS Note: 1. Use to identify carrier package 

identification number when carrier is other than the United 

States Postal Service. Use recommended in conjunction 

with identification of the carrier (2/N101/80 qualifier CA).

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

AW Air Waybill Number 

DLMS Note: 

1. Use to identify the shipment unit air waybill number. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f. 

BL Government Bill of Lading 

DLMS Note: 

Adds authorized DLMS 

enhancement note. 
1. Use to identify the government bill of lading. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f. 

BM Bill of Lading Number 

DLMS Note: 

1. Use to identify the shipment unit commercial bill of lading 

number. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

IZ Insured Parcel Post Number 

DLMS Note: 

1. Use to identify the shipment unit insured parcel post 

number. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

K2 Certified Mail Number 

DLMS Note: 

1. Use to identify the shipment unit certified mail number. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

K3 Registered Mail Number 

DLMS Note: 

1. Use to identify the shipment unit registered parcel post 

number. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

WY Waybill Number 

DLMS Note: 

1. Use to identify the shipment unit surface waybill number. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

ZH Carrier Assigned Reference Number 

DLMS Note: 

1. Use to identify the shipment unit express mail number. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

6. 2/QTY01/55 Revise DLMS notes for the following codes:

01 Discrete Quantity 

DLMS Note: Use in initial material release confirmation,

material release advice and disposal release advice 

transactions to identify the quantity for which status is being 

provided. (This equates to the quantity carried in DLSS 

Document Identifier AR_ or AE6, AEJ, AGJ, or ASZ.) 

03 Discreet Quantity – Rejected Material 

DLMS Note: Use in material release cancellation advice, 

Administrative revision for 

clarification of intended use. 
historical material release cancellation advice, disposal 

release cancellation advice, and historical disposal release 

cancellation advice transactions to identify the quantity which 

was cancelled. (This equates to the quantity carried in 

DLSS Document Identifier AG6.) 

39 Shipped Quantity 

DLMS Note: Use in reply to material release cancellation

request, historical reply to material release cancellation

request, reply to disposal release cancellation request, and 

historical reply to disposal release confirmation request

transactions to identify the quantity which is 

confirmed/shipped. (This equates to the quantity carried in 

DLSS Document Identifier AU_.) 

QC Quantity Disapproved 

DLMS Note: Use in material release denial, historical 

material release denial, disposal release denial, and historical 

disposal release denial transactions to identify the quantity of 

the warehouse refusal. (This equates to the quantity carried 

in DLSS Document Identifier A6_.) 

V1 Retention Quantity 

DLMS Note: Use in disposal release confirmation denial, 

and historical disposal release confirmation transactions to 

identify the quantity actually retained. (Applicable to DLSS 

Document Identifier ARJ, AEJ, AGJ, A6J, ARL, or ARK.)

7. 2/N101/80 

2/N102/80 

2/N103/80 

Revise DLMS notes for code CA as follows:

CA Carrier 

DLMS Note: 

1. Use for material release confirmations, historical material 

release confirmations, disposal release confirmations, and 

historical disposal release confirmations to identify the 

shipment unit carrier when other than the United States 

Postal Service. 

 

2. The carrier shall be Standard Carrier Alpha Code 

(SCAC). The carrier name is optional and may be identified 

in N102. 

3. Authorized DLMS migration enhancement; see 

introductory DLMS 3f.

Add the follow Data Element DLMS note:

DLMS Note: May be used to identify the carrier name. 

Field length will be restricted to 20 positions. 

2 Standard Carrier Alpha Code (SCAC) 

Fed Note: Use as needed to identify the commercial carrier. 

DLMS Note: Authorized DLMS migration enhancement; 

Adds clarification and authorized 

DLMS enhancement note.
see introductory DLMS 3f. 

8. 2/LQ01/100 Revise DLMS notes for Code 36, 37, and 38 as follows:

36 Air Terminal Identifier Code 

DLMS Note: 

1. Use to identify port of embarkation (POE) air terminal 

identifier codes for Outside Continental United States 

(OCONUS) shipments made via Defense Transportation 

System (DTS) air modes. 

2. This DLMS enhancement may be used during initial 

implementation. Authorized DLMS migration enhancement; 

see introductory DLMS 3f. 

3. During the DLSS/DLMS transition period, transactions 

originating as DLSS DI Code AS_, Shipment Status, will 

carry this information in REF01, qualifier TT, Terminal 

Code, due to the translator's inability to distinguish among 

code types. 

37 Water Terminal Identifier Code 

DLMS Note: 

1. Use to identify port of embarkation (POE) water terminal 

identifier codes for OCONUS shipments made via DTS water 

modes. 

2. This DLMS enhancement may be used during initial 

implementation. Authorized DLMS migration enhancement; 

see introductory DLMS 3f. 

3. During the DLSS/DLMS transition period, transactions 

originating as DLSS DI Code AS_, Shipment Status, will 

carry this information in REF01, qualifier TT, Terminal 

Code, due to the translator's inability to distinguish among 

code types. 

38 Consolidation and Containerization Point Code 

DLMS Note: 

1. This DLMS enhancement may be used during initial 

implementation when Used to identify the SEVAN CCP code 

for OCONUS shipments made via DTS. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f. 

3. During the DLSS/DLMS transition period, transactions 

originating as DLSS DI Code AS_, Shipment Status, will 

carry this information in REF01, qualifier TT, Terminal 

Code, due to the translator's inability to distinguish among 

code types. 

Adds clarification and authorized 

DLMS enhancement note. 

9. 2/N901/120 Revise DLMS notes for Code BT, SE, and U3 as follows:

BT Batch Number 

DLMS Note: 

Use to identify the manufacturer's batch/lot number or other 

number identifying the production run. The batch/lot 

Updates to cite unique 

identification (UID) policy field 

size limitations for unique item 

identifier, batch/lot, and serial 

number. UID policy is available at: 

http://www.acq.osd.mil/dpap/UID/.
number may not exceed 20 characters in accordance with 

UID policy. 

SE Serial Number 

DLMS Note: 

Use to identify the serial number. The serial number may 

not exceed 30 characters in accordance with UID policy.

U3 Unique Supplier Identification Number (USIN) 

DLMS Note: 

1. Use to identify the UII. Place UII value in N902. If UII is 

longer than 30 positions, place remainder of UII in N903. 

The UII may not exceed 50 characters in accordance with 

UID Policy. 

2. A data maintenance action was approved in version 5020. 

The approved code/name is "UII - Department of Defense 

Unique Item Identifier”. 

10. N902 

N903 

Delete the following DLMS notes for DE N902 and N903:

For use with REF01 codes BT and SE. When N901 = U3, 

enter the UII value. If the UII value is greater than 30 

positions the value must be split between N902 and N903.

Use when N901 = U3 and UII value must be split between 

N902 and N903.

Current IUID policy limits the UII 

to a 50 character format, so the 

“split” is no longer needed.