1

ADC 309 

NOA and NOA Reply Transaction Data Content/Mapping 

including Addition of Type Pack Code for 463L Pallets 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Agency (DLA) 

b. Originators: 

(1) Ms. Ellen Hilert, Chair, Supply Process Review Committee, 703-767-0676; DSN: 

427; e-mail: ellen.hilert@dla.mil

(2) Heidi Daverede, Defense Logistics Mangement Standards Office (DLMSO), 703-

767-5111, DSN 427, e-mail: heidi.daverede@dla.mil

2. FUNCTIONAL AREA: Primary: Supply/MILSTRIP; Secondary: Transportation

3. REFERENCE: 

a. DOD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures (MILSTRIP) 

b. DOD 4000.25-M, Defense Logistics Management System (DLMS) 

c. Type Pack Code Conversion Guide at Defense Logistics Management Standards Office 

Website http://www.dla.mil/j-6/dlmso/eApplications/LogDataAdmin/dlmsansiconverguides.asp 

4. REQUESTED CHANGE: 

a. Description of Changes: This is a multi-purpose change which updates data content 

related to the Notice of Availability (NOA) and NOA Reply. This revision:

(1) Resolves a DLMS/MILS conversion issue between the MILSTRIP AD5 and the 

comparable DLMS 870N, Notice of Availability Reply. Revisions are identified to add a code 

and DLMS note to DLMS Supplement 870N supporting what the DAAS map has already 

implemented, and add a future enhancement to the process to identify the NOA submitter. 

(2) Modifies the location of the type pack code in the DS 856N, Notice of Availability. 

(3) Updates MILSTRIP Appendix 3.30 to correctly identify the authorized data source 

for valid DoD Type Pack Codes. 
2

(4) Updates the Type Pack Code Conversion Guide to add a type pack code for 463L 

pallet and its applicable X12 conversion code.

(5) Updates the DLMS and MILSTRIP Manuals References and Abbreviations sections 

to include a definition of United States Transportation Command’s (USTRANSCOM) Table 

Management Distribution System (TMDS) and its associated URL. 

b. Background: 

(1) During review, a disconnect between the NOA Reply data element for Qualifier CY, 

Country Code, and Qualifier 38, Country Code, was identified. The DAAS mapping document 

currently shows the following: 

Field Name Record Position Conditions DLMS Data Element 

Country RP 19-20 None N101=CY 

N103=38 

N106=FR 

However the qualifier “38” is not a valid value for N103 in the 870N DLMS Supplement. 

USTRANCOM requested that DAASC and DLMSO reconcile the discrepancy, with the 

preferred solution for DLMSO to add “38” to the list of valid code values for N103 in the N1 

segment. DLMSO concurred that there is a gap to identify the “from activity” as required under 

X12. The actual country code is suitable for MILS functionality; however this is not the same as 

the country representative or freight forwarder identification which was the intent of the DLMS 

transaction (as evidenced by the current DLMS notes). DLMSO recommended corrections to 

properly identify current functionality and to identify future enhancements. 

 

(2) The United States Transportation Command, as the Authoritative Data Source, 

moved the DoD Type Pack Code table from the DTR 4500.9-R, Part II to the Table Management 

Distribution System (TMDS). The website URL is as follows: https://wwwtmds.c2.amc.af.mil/TMDS/DTRdata.xsql?result=&view=V_TYPE_PACK&skip=0&max=10. 

During a recent review of the type pack code for 463L pallet, we discovered that this code is 

missing in the DLMSO Type Pack Code Conversion Guide. Furthermore, the X12 conversion 

published by USTRANSCOM for this code is incompatible with the authorized X12 codes for 

the TD101 data element in the DS 856N.

c. Procedures: 

(1) Revise DLMS Supplement 870N (NOA Reply) and associated DAAS map to: 

(a) Designate existing Qualifier CY (country) for identification of the FMS 

country and insert the missing Qualifier 38 (country) to identify the value associated with the 

country code; 

(b) Remove unnecessary qualifiers from the list of enhancement values for 

types of code lists used to identify the transaction originator.
 3

(c) Incorporate planned enhancements for identification of the FF and CR are 

as DLMS enhancements.

# Location DS 870N Notice of Availability Reply Reason 

1. DLMS 

Introductory 

Notes 

Added DLMS Introductory note 4 and ADC 309 :

4. This revision to the DLMS Supplement (DS) incorporates Proposed DLMS 

Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs and ADCs 

are available from the DLMSO website: http://www.dla.mil/j6/dlmso/elibrary/Changes/processchanges.asp 

- ADC 309, NOA and NOA Reply Transaction Data Content/Mapping 

including Addition of Type Pack Code for 463L Pallets.

Identifies DLMS 

Changes included 

in the DLMS 

Supplement 

2. 1/N101/50 Insert new DLMS note 3 and 4 at N101: 

N101 Entity Identifier Code 

DLMS Note: 

1. Use only one of code 98 or CY. 

2. For DLMS use, only the following codes are authorized. 

3. For conversion between MILS and DLMS formats, the transaction 

originator will always be identified by Qualifier CY using the MILSTRIP 

Country Code. 

4. Identification of the Freight Forwarder (FF) or Country Representative 

(CR) are identified as DLMS enhancement; see introductory DLMS note 3a. 

Use of this enhancement requires a second iteration of the N1 loop (refer to 

ADC 309). 

 98 Freight Management Facilitator 

DLMS Note: This is a DLMS enhancement to identify the FF originating the 

transaction set. 

 CY Country 

DLMS Note: 

1. Use to identify the FMS country associated with the NOA reply. 

2. Use as a DLMS enhancement to identify the CR originating the transaction 

set. 

Correction and 

clarification of 

appropriate usage. 

3 1/N102/50 Open N102 with corresponding note: 

N102 Name 

DLMS Note: This is a DLMS enhancement for identification of the FF or CR 

by clear text where coded address is not available.
4

# Location DS 870N Notice of Availability Reply Reason 

4. 1/N103/50 Insert new codes 38 and A2 at N103 with corresponding DLMS notes. Delete 

DUNS numbers, DoDAAC, and RIC as options for the originator of the NOA 

reply. 

N103 Identification Code Qualifier 

38 Country Code 

DLMS Note: 

Use with N101 Qualifier CY to identify the FMS country code (MILSTRIP) 

applicable to the NOA reply. (Must be consistent with the NOA and original 

requisition content). Use of the ISO country code is not authorized for this 

purpose. Note: The code list is the same as DLMS Qualifier Code list for 

Country and Activity Code, Qualifier 85) 

 

A2 Military Assistance Program Address Code (MAPAC) 

DLMS Note: 

This is a DLMS enhancement for use of the constructed MAPAC to identify the 

FF or CR. Requires coordination prior to use. 

 1 D-U-N-S Number, Dun & Bradstreet

 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix

 10 Department of Defense Activity Address Code (DODAAC)

 M4 Department of Defense Routing Identifier Code (RIC)

DLMS Note: The RIC is retained in the DLMS to facilitate transaction 

conversion in a mixed DLSS/DLMS

environment. Continued support of the RIC in a full DLMS environment will be 

assessed at a future date. Typically under the DLMS, the RIC will be replaced 

with a DoDAAC or a commercial identifier.

Clarifies current 

mapping which 

perpetuates the 

MILSTRIP country 

code from the NOA 

Key Document 

number. 

Identifies a more 

appropriate DLMS 

enhancement for 

identification of the 

transaction 

originator and 

removes 

inappropriate 

options. 

(2) Revise 856N Notice of Availability to:

(a) Re-locate the type pack code so that a DoD code may be used without 

requiring use of a conversion table to transmit in the DLMS format.

(b) Remove unnecessary qualifiers from the list of potential enhancement 

values for types of code lists use to identify the transaction originator/recipient.

# Location Revision to 

4010 856N, Notice of Availability 

Reason for 

Change 

1 DLMS 

Introductory 

note 

Add the following DLMS Introductory note 5 and ADC 309:

5. This revision to the DLMS Supplement (DS) incorporates Proposed DLMS 

Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs and 

ADCs are available from the DLMSO website: http://www.dla.mil/j6/dlmso/elibrary/Changes/processchanges.asp 

- ADC 309, NOA and NOA Reply Transaction Data Content/Mapping 

To identify changes 

in the DS. 
 5

including Addition of Type Pack Code for 463L Pallets

2 2/TD101/110 Delete current notes and mark data element “Not Used”

Packaging Code

Federal Note: Use to identify the shipment unit type pack. 

DLMS Note: DLMS users see the Type of Pack Conversion Table for available 

codes.

Type Pack Code is 

re-located to the 

2/LQ02/0350 

eliminating the 

need for use of the 

DLMS Conversion 

Table for the 856N 

and the disconnect 

for migration code 

“PLL” which is not 

authorized for use 

in the source list for 

this data element 

(DE 103). 

3. 2/N103/220 Delete DUNS numbers, DoDAAC, and as potential options for the 

originator/recipient of the NOA. 

 1 D-U-N-S Number, Dun & Bradstreet

 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix

 10 Department of Defense Activity Address Code (DODAAC)

Eliminates 

confusion caused 

by unnecessary 

options. 

4 2/LQ01/350 Add new qualifier and DLMS Note:

40 Type Pack Code 

DLMS Note: Use the DOD code to describe the type of pack for the shipment 

unit. Refer to the Table Management Distribution System (TDMS) available at 

URL: https://www-tmds.c2.amc.af.mil/TMDS/USTRNSCOM_index.xsql for 

applicable code list. (ADC 309 includes an abbreviated listing to facilitate 

implementation within DoD supply systems.) 

Enable entry of the 

DOD Type of Pack 

code. 

(3) Add the following reference to the DOD 4000.25-M, References, and DOD 4000.25-

1-M, References: 

Table Management Distribution System: https://www-tmds.c2.amc.af.mil/TMDS/ 

(4) Add the following acronym to the DOD 4000.25-M, Acronyms and Abbreviations, 

and DOD 4000.25-1-M, Abbreviations: 

TMDS Table Management Distribution System 

(5) Revise DLMS Data Element code list for Type Pack Code (Qualifier 40) and Type 

Pack Code Conversion Guide to include 463L Air Pallet. Note that the use of “PLL” is a 

“migration code”, as designated and coordinated by USTRANSCOM. It only applies to X12 

segments mapped to data element table 211. The use of a “migration code” refers to establishing 

an agreement with all trading partners to use a valid X12 code from a higher version with the 
6

approved X12 definition, at a lower version of X12. Manual intervention will be needed for 

some commercial applications to accept the higher version code. 

Name/Definition DOD Code X12 Code 

463L Air Pallet LP PLL (Note: This is a “migration code” from V4060 DE 211) 

(6) Revise MILSTRIP, Appendix 3.30, FMS NOA Key Document, as shown: 

Field Legend Record Position(s) Entry and Instructions 

Type of Pack 24-25 Identifies the type of pack used for the shipment unit (see 

TMDS DTR)

1

. 

-------------------- 

1. Refer to the TDMS at URL: https://www-tmds.c2.amc.af.mil/TMDS/USTRNSCOM_index.xsql for 

applicable code list. 

Staffing Note: The TMDS is the authoritative source; however this code list is undergoing 

transition to eliminate redundancy; therefore, an abbreviated version is provided at Enclosure 1 

to facilitate implementation within DoD supply systems. 

5. REASON FOR CHANGE: 

a. USTRANSCOM personnel supporting Global Transportation Network Pre-Planned 

Product Improvement (GTN P31) identified a gap between the MILSTRIP format and the 

equivalent DLMS requiring corrective action. 

b. The type pack code for 463L air pallet was missing from the type pack code conversion 

guide to support the 856N, Notice of Availability, DLMS Supplement, and the MILSTRIP 

Appendix 3.30 contained an outdated reference for the authorized data source for the type pack 

code. Since the X12 conversion for the 463L air pallet is incompatible with the current location 

for the type of pack in the 856N, the data element is being moved to the LQ segment, wherein 

the full range of DOD Type Pack Codes is authorized for use. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Corrects inconsistencies and gaps.

b. Disadvantages: None identified.

7. Impact: 

a. Modifies DOD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP) Appendix 3.30 and comparable changes to the DOD 4000.25-M, Defense Logistics 
 7

Management System (DLMS) Manual. 

b. Modifies the Type Pack Code list and Conversion Guide 

c. The DAASC map for the 856N must be updated to reflect the new location for entry of 

the Type Pack Code. 

d. The DAASC map for the 856N needs to be updated to allow for the use of a MAPAC 

to identify the FR (currently it only identifies the mapping for the use of qualifier CY for the 

CR associated with the constructed MAPAC). This gap is not identified above because the 

DLMS format is not impacted. 

e. The DAASC map for the 870N is correct for the mapping of the Country Code, but 

should be updated to identify enhancements for use of the CR/FF as the originator. 

f. DSS and GTN P3I will need to update their 856N message format to reflect the new 

location for entry of the Type Pack Code. Updates may be needed for transaction originator to 

remain consistent with changes identified above (specifically DAAS map gap to identify the 

NOA directed to the FR in paragraph 7.d). Staffing Note: DAASC is requested to coordinate 

with USTRANSCOM IGC PMO after the change is published as an ADC, and at least 90 days prior 

to implementation, in order to determine the exact date the change will be affected. This will 

allow IGC to make the necessary changes to the ETL on their system in order to process the new 

transaction format and not have data fail to load. 

 
 Type Pack (Abbreviated List) 1

Enclosure 1, Type Pack Codes (Abbreviated List) 

Staffing Note: Below is an abbreviated list of the Type Pack Codes derived from the TMDS. 

This is the authorized list for use in the Transportation Control and Movement Document 

(TCMD) 858B Implementation Convention published by USTRANSCOM1

 and may be used as 

the source of type pack codes for the NOA. This list is abbreviated because it eliminates 

redundancies for variations of MSCVAN and SEAVAN due to variation of load and responsible 

parties for loading, etc. The list provides the DoD Code as authorized for use under this ADC in 

the NOA, the applicable X12 Code for those transactions where the Type Pack is mapped to the 

X12 data element, and the associated definition for DoD use (some deviate from the X12 

definition). 

DoD X12 

Code Code DoD Definition

 

AB MSV Military Sealift Command Van (MSCVAN) 

BD BDL Bundle 

BE BAL Bale 

BG BAG Bag, burlap or cloth 

BL BBL Barrel 

BS BSK Basket 

BX BOX Box 

CA CAB Cabinet 

CB CBY Carboy 

CC CNA Household Goods (HHG) containers, wood 

CL COL Coil 

CM CNB Container, MAC-ISO, lt. wgt. 8x8x20 foot air 

CN CAN Can 

CO CNT Container, other than CC, CM, CU, CW, MW, MX 

CR CRT Crate 

CS CAS Case 

CT CTN Carton 

CU CNC Container, Navy cargo transporter 

CW CND Container, commercial highway lift 

CY CYL Cylinder 

DB DUF Dufflebag 

DR DRM Drum 

EC CNE Engine container 

ED CRD Engine cradle or dolly 

EN ENV Envelope 

FK TRK Footlocker (Trunk) 

HA HPR Hamper 

KE KEG Keg 

 

1

 Final Draft 20090424, Department Of Defense Transportation EDI Convention (B) TCMD 
2

LP PLL2 463L Air Pallet 

LS LSE Loose, not packed 

MW CNF Multiwall container secured to warehouse pit 

MX MXD Mixed 

PC PCS Piece 

PL PAL Pail 

PT PLT Palletized unit load other than code MW 

RL REL Reel 

RO ROL Roll 

RT WHE RORO (roll-off, roll-on) 

SA SAK Sack, paper 

SB SKE Skid, box 

SD SKD Skid 

SH SHT Sheet 

SL SPL Spool 

SW SCS Suitcase 

TB TUB Tub 

TC TKR Tank Car 

TK TRU Truck 

TT TKT Tank Truck 

TU TBE Tube 

UX UNT Unitized (use RT for unitized cargo on RORO) 

VC VPK Van chassis 

VE VEH Vehicle 

VO VOC Vehicle in Operating Condition 

VS TBN SEAVAN - TOTE 

WR WRP Wrapped 

X1 CNX CONEX (Gov't owned container) 

YB MLV MILVAN 

ZB SVN SEAVAN 

 

2

 Migration code 
 Comment Resolution 1

Enclosure 2, Comment Resolution 

 Originating 

Component 

Comment Response 

1 DFAS DFAS has no comments or recommendations on PDC 318. 

2 DLA DLA have reviewed the PDC 318 and are in agreement with its 

content. DLA concurs there will be no impact for EBS. 

DLMSO alerted 

DLA that impact 

applies to DSS. 

3 USTRANSCOM The proposed change for the type pack code in the 856N requires 

changes to the ETL in our database for P3I. 

I would ask if it is reasonable for us to get a 90 day notice from 

DAASC before the implement this change in the MILS to EDI 

conversion that they perform (translation). Also, this will require 

close coordination between DAASC and P3I so that when they 

change the mapping (to reflect the changes dictated by this 

change) that we change our ETL at the same time. 

Concur - Lead time 

to be provided 

implementation 

4 DLA J6UEA Other than our goal of finishing our DLMS migration as you 

stated, there is no imminent need to convert NOAs -- 

I am unaware of any 'schedule' for implementation of the 

NOA/reply to DLMS 

Noted 

5 DAASC Since we only receive NOAs for Germany, DAASC passes "all" 

AD1/2/3/4/Rs to a internal pseudo RIC (Y25) which is loaded to 

a DAMES account owned by the German Logistics 

Representative in Wash DC. 

If we were to receive NOAs for other countries our logic would 

have to change. Most likely we would key on the MAPACs in 

the detail records. 

I'm checking all of 2008 but don't believe we ever receive AD5s 

(NOA Reply) which are passed to the RIC in rp 4-6. 

Noted 

6 USASAC 

traffic mgmt 

Concur 

7 Navy NAVSUP interposes no objection to this PDC as written.