ADC 448

ADC 448

Implementation of ISO 3166-1 Codes for the Identification of Names of Countries 

and their Subdivisions

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Service/Agency: DLA Logistics Management Standards, DLA J627

b. Originator: DLA Logistics Management Standards 

2. FUNCTIONAL AREA: DODAAD/MAPAD/Supply/Finance

3. REFERENCES: 

a. OSD(AT&L) Policy Memorandum, dated June 6, 2011, subject; 

“Department of Defense Country Code Standard”, Linked at DoD Country Code Memo.

b. OSD(CIO) Policy Memorandum, dated May 5 2010, subject; “Monitoring 

Country Code Standard Transition”, Linked at Country Code Standard Transition

c. Military Standard (MIL-STD) 129P, Change 4; dated September 19, 

2007, subject; “Department of Defense Standard Practice, Military Marking for Shipment 

and Storage”

d. DOD 4000.25- Defense Logistics Management System

e. DOD 4000.25-1-M Military Standard Requisition and Issue Procedures 

(MILSTRIP)

f. DOD 5105.38-M Security Assistance Management Manual (SAMM),

Chapter 4, Table C4.T2 

g. Approved DLMS Change 318, DOD Activity Address Directory 

(DODAAD) Country Codes in the DODAAD (Staffed as PDC 325)

4. REQUESTED CHANGE:

a. Description of Change: This change:

(1) Implements DoD policy within the DLMS to transition to the use 

the International Organization for Standardization (ISO) 3166-1, “Codes for the 

representation of names of countries and their subdivisions – Part 1: Country Codes” by 

September 30, 2012, in accordance with References 3.a and 3.b. ISO 3166-1 contains 

two alphabetic code lists: digraph (two characters) and trigraph (three characters). DLMS 

will implement the ISO 3166-1 two character (digraph) alpha code structure and code list
ADC 448

Page 2

in order to minimize the impact on databases, application logic, and outputs that are 

currently reliant and restricted to two characters. Prior to the end of calendar year 2017, 

the Defense Logistics Management Standards PRCs will initiate action to assess the value 

and implementation requirements in migrating from ISO 3166-1 digraph to the tri-graph 

code structure.

(2) Approves a related enhancement to use country short names in 

DoDAAD and MAPAD last address line in lieu of country codes to meet the ISO and 

United States Post Office (USPS) postal addressing rules.

(3) Replaces the existing DLMS MILSTRIP “Country and Activity 

Code” with the “Security Cooperation Customer Code” and removes values not 

associated with Security Assistance so that this data element will become exclusively 

used to support Security Assistance requisitioning and the establishment of the Military 

Assistance Program Address Codes (MAPACs). Note: A “Legacy MILSTRIP” code set 

will be maintained in the DoDAAD Country Code Mediation Table to support mitigation 

and legacy code users pending transition to ISO.

(4) Highlights in bold italics denote significant changes from PDC 

474.

b. Background: 

(1) The need to adopt a single country code standard within DOD and

among its trading partners, including DOD, Federal and commercial, has long existed. 

OSD(AT&L), Division of International Cooperation, is currently coordinating with

ISO to formally establish the DoD Country Code Profile for adoption as part of the 

ISO-1 standard. In support of that effort a the Defense Information Systems Agency 

has established a DOD Country Code Tiger Team to (a) develop the initial DoD 

Country Code Profile of code values within the ISO 3166-1 standard framework, (b) 

develop and document the DOD configuration management process for maintaining 

the DOD Country Code Profile, and (c) develop a mediation service among existing 

country code standards code values and the ISO code values to support the transition 

period. The DoD profile is necessary to obtain lSO-3166-1 locally assigned codes for 

locations for which there is a FIPS or MILSTRIP country code, but not an established 

ISO 3166-1 code. These locally assigned codes will replace the “pseudo codes” 

established by Defense Logistics Management Standards in DoDAAD and MAPAD 

that were previously established to fill that void.

 

(2) Currently, there are multiple country code related standards used

by the DoD logistics trading partners’ information systems. The codes in use are:

(a) MILSTRIP “Country and Activity” Code. These two 

character codes are used within the Defense Logistics Standard System (DLSS) and 

DLMS logistics business transactions governed by the DOD 4000.25-M family of 

manuals. These codes are currently a mixture of codes assigned by Defense Security 

Cooperation Agency (DSCA) described below and codes assigned by the MILSTRIP 

Administrator to meet other operational needs. See reference e, Appendix 2.18.
ADC 448

Page 3

(b) Federal Information Processing Standard (FIPS) 10-4 

FIPS has been withdrawn and its usage will sunset at the end of calendar year 2012. The 

General Services Administration Federal Supply System uses FIPS internal to its

systems.

(c) ISO 3166-1. The DOD Activity Addressing Directory 

(DoDAAD) and Military Assistance Program Directory (MAPAD) previously 

transitioned to the ISO 3166-1 standard, both digraph and trigraph. The digraph values 

are currently used as the primary database key in DoDAAD/MAPAD and for purposes 

including constructing the last line of the address in some cases. Trigraph values were 

included to allow for mediation, if and when required. DoDAAD and MAPAD currently 

contain Defense Logistics Management Standards assigned “pseudo” codes, for 

physical locations supported by MILSTRIP or FIPS, but not by ISO 3166-1. See ADC 

318.

(d) Security Cooperation Customer Code (also referred to 

as Foreign Military Sales (FMS) Customer Code). DSCA uses a two character code to 

represent the country, international organization, region or program authority associated 

with transactions recorded in Security Cooperation systems and associated with programs 

implemented in the FMS Trust Fund (see reference f). The code values in the table do 

not refer exclusively to countries. DSCA will continue using the existing code values;

there is no change to these codes as a result of the migration to ISO 3166-1. Therefore,

there will be no change to the code values used in the second and third positions of 

MAPACs, document numbers, or transportation control numbers for Military 

Assistance Program/Grant Aid requisitions and their follow-on business transactions. 

DSCA will be issuing a policy memo to update the title of the code to “Security 

Cooperation Customer Code” in the Security Assistance Management Manual 

(SAMM) reference f. and other formal guidance referencing the code and will request

the SFIS T-21 attribute title be changed accordingly. 

(3) DLA Logistics Management Standards and DLA Transaction 

Services implemented a mediation table among the four standards in use in logistics 

when the DoDAAD was reengineered. It contains four country code standards and five 

code list values:

(a) International Standards Office (ISO), two and three 

character code list values (only the two character is currently used in logistics)

(b) Federal Information Processing Standard (FIPS) 10-4

(c) Foreign Military Sales (FMS)

(d) MILSTRIP Country and Activity Codes

(4) The existing mediation table, amended as described in the 

procedures below, will support the logistics systems transition to meet the policy mandate 

to adopt the ISO 3166-1 in all systems by the September 30, 2012.
ADC 448

Page 4

(5) Country code name guidance from the United States Post Office 

(USPS) states, “The last line of the address block area must include only the complete 

country name (no abbreviations) written in uppercase letters.” See 

http://www.usps.com/international/addressingintlmail.htm. ISO 3166-1 has similar 

guidance that states “ISO3166-1 is not generally used in postal addressing.” Procedures 

to display country names on the last line of the address are below.

c. Procedures: The following procedures are approved.

(1) Country Code Mediation Table Changes. 

(a) General Usage: The existing Country Code Table that is 

published on the DLA Logistics Management Standards Web site (Country Code Table) 

and available from DLA Transaction Services via data replication will be saved to the 

DLA Logistics Management Standards website for reference of legacy values for an 

indefinite period of time. When the existing country code table was initially established, 

pseudo ISO codes were assigned by DLA Logistics Management Standards for countries 

that were in other standards, but not in the ISO 3166-1 standard. With the formal 

adoption of ISO 3166-1 as a DoD wide standard, the pseudo codes are being replaced by 

ISO approved user assigned codes in accordance with ISO procedures and the DoD 

Country Code Profile. The new country code mediation table at (New Country Code 

Table) includes those newly assigned codes that are replacing the former pseudo codes. 

Note: As of the date of the issuance of this ADC, the DoD Country Code Profile has 

not been finalized. The New Country Code Table entries are based on the best 

information available at this time. When the DoD Country Code Profile is finalized, 

an administrative addendum will be issued to change the New Country Code Table to 

match the code values of the profile. However, Components should commence the 

planning, programming code changes, testing and documentation changes needed to 

implement. Implementation in production environments should be planned for no 

sooner than 1 July 2012 and no later than 30 September 2012. It should also be noted

that the Country Code Mediation Table hosted by the DLA Transaction Service will 

exist indefinitely. When the DoD Country Code Tiger Team completes its work and 

provides an authoritative enterprise mediation service, the DLA Transaction Service 

will subscribe to that service to maintain the table it hosts. Therefore, system designers 

can rely on the DLA-hosted Country Code Mediation Table indefinitely for reliable and 

timely information. 

The column headings of the Current Country Code Mediation Table and the New 

Country Code Mediation Table are shown below.

CURRENT COUNTRY CODE MEDIATION TABLE

A B C D E F G H

COUNTRY 

NAME

MILSTRIP 

CC

FIPS 

CC

SA/FMS 

CC

ISO 

CC

3 

POS 

CC

INACTIVE 

COUNTRY 

OR 

ACTIVITY 

CODE

PSEUDO_ISO
ADC 448

Page 5

NEW COUNTRY CODE MEDIATION TABLE

A B C D E F G H I J K

COUNTRY

NAME

MILSTRIP

LEGACY 

CODES

(PHYSICAL 

LOCATIONS)

FIPS 

CC

SECURITY 

COOPERATION

CUSTOMER 

CODES

(PHYSICAL 

LOCATIONS)

ISO 

DIGRAPH

PLUS DOD 

PROFILE 

CODES

ISO

TRIGRAPH

PLUS DOD 

PROFILE 

CODES

INACTIVE 

COUNTRY 

LEGACY 

PSEUDO 

ISO 

INDICATOR

LEGA

CY 

ISO 2

LEGACY 

ISO 3

Non US 

City/Postal 

Code Flag

(b) Specific changes to the existing Country Code Mediation 

Table to create the new Country Code Mediation Table. 

(1) Drop "JAN MAYEN" row. Jan Mayen and 

Svalbard are the same country, and Svalbard is the most common usage.

(2) Columns “B” through “F” will retain their data 

values but columns “E” and “F” will be updated to reflect the DoD supplied User 

Defined ISO values. Columns “I” and “J” will contain the legacy pseudo ISO values. 

After implementation, Columns “I” and “J” will no longer be updated and will only be 

used for historical and mediation purposes.

(3) The table rows for data values in Column “B” 

(renamed “MILSTRIP Legacy Codes”) will no longer be associated with Logistics Data 

Resources Management System (LOGDRMS) data qualifier table 85 or MILSTRIP 

Appendix 2.18. The codes listed will only be those associated with physical locations 

rather than Security Assistance programs. These codes will be maintained for historical 

purposes/mediation and to support legacy code users (e.g. Army systems) pending 

transition to ISO codes for physical countries. The table rows for data values in Column 

“D” (renamed “Security Cooperation Customer Code”) will be derived from LOGDRMS 

data qualifier 85 and MILSTRIP Appendix 2.18; however, only codes associated with 

physical locations will be reflected in the mediation table.

(4) Establish Columns “E” and “F” to support DoD 

Profile of ISO and ISO locally assigned codes used by DoD. Populate these columns 

with new values accordingly.

(5) Establish Column “K” entitled “Non US City/Postal 

Code Flag”. This new column will determine the ordering of the City Name and Postal 

Code data elements when constructing the next-to-the-last address line (see paragraph (4).

(6) The new Country Code mediation table after all the 

changes above have been effected is linked New Country Code Table.

http://www.dla.mil/j6/dlmso/eLibrary/Documents/DoDAAD/NewConsolidatedCountryCodeList.xlsx.
ADC 448

Page 6

(2) DLMS Supplement Changes. 

(a) Clear text address changes: Clear text addressing in 

DLMS Transactions list the country code in the N404 segment. The ICs impacted by this 

change are: 511M, 511R, 842A, 842D, 842R, 856M, 846R, 856S, 856, 869F and 940R. 

DLMS notes indicate that this is an authorized DLMS enhancement. The code value to 

be used is currently identified as the MILSTRIP code. Transactions associated with 

requisitioning with exception addressing also support use of the DLA unique 3-position 

country code. Change to these supplements to read “After September 30, 2012 you must 

use the ISO 3166-1 two character country code in this field. The authoritative source of 

the country code values used by DoD will be included in the Country Code portion of 

the Global Informational Grid (GIG) Technical Profile (GTP). The changes to the 

DLMS Supplements for the impacted ICs are identified in Enclosure 2. PDC 474

requested that any Component employing this DLMS enhancement specifically identify 

their usage by transaction and indicate their capability to transition to the ISO code on 

schedule and identify earlier implementation date as applicable. No comments were 

received. Simultaneous implementation on October 1, 2012 will be required to ensure 

consistent meaning of the two digit code values (ISO versus MILSTRIP) in 

transactions at any point in time.

(b) “Security Cooperation Customer Code” Changes. The 

MILSTRIP Country and Activity Code is currently passed as a discrete data element 

under DLMS in the LQ Segment. The original intent was to allow for identification of 

the Security Cooperation customer separately so that the MILSTRIP document number 

could be constructed without embedded codes. When transactions are prepared in the 

legacy format, DLA Transaction Services populates this data field during conversion to 

DLMS. The changes to the impacted supplements is shown in Enclosure 2: 511R, 

511M, 842A, 842D, 842R, 856M, 846R, 856S, 856, 869F and 940R.

(3) DLA Transaction Services changes:

(a) Establish the new mediation table for use in the DoDAAD, 

MAPAD and for MILS and DLMS transaction mediation where the transaction contains 

the country code.

(1) The mediation table will be used to support a 

Component phased transition to ISO-2 Country Code usage for those MILS and DLMS 

transactions that carry the country code data element. DLA Transaction Services will 

modify the code values in transactions to ensure that the sending and receiving Service 

systems Country Code Standard in use is mediated between the systems exchanging 

transactions.

(2) Logistics Metrics Analysis Reporting System 

(LMARS) will be changed to accommodate the new country code standard and overseas 

area designations under a separate PDC. 
ADC 448

Page 7

(3) DoD WebSDR (Supply Discrepancy Reporting) 

will be updated to revise the screen display name for the International Logistics Data 

“Country” to read “Customer Code”. The drop down selection values will be reviewed to 

ensure they are consistent with the code set applicable to the Security Cooperation

Customer Code. Internal DoD WebSDR changes to SDR records are not required. 

(4) DLA Transaction Services archived historical 

transactions will not be converted. However, future special reports will need to 

accommodate and mediate and account for legacy transactions and transactions 

containing the new ISO 3166-1 standard code values. 

(b) Modify the DoDAAD and MAPAD update application

daily delimited files and databases and DAASINQ/eDAASINQ as follows:

(1) Modify DoDAAD to allow for addition of a fifth 

address line. Note that the procedures below would retain the ISO 3166-1 country 

code in the next to the last line of address for an indeterminate period of time to 

support systems that are only capable of receiving four address lines. 

(2) For non United States addresses, where the “Free 

Form” indicator is not set, construct the last two address lines of all DoDAAD and 

MAPAD addresses as follows:

a. Use the new mediation table and compare 

column “E” to column “I” if they contain different values then match Column “I” the ISO

2 code in the DoDAAD and MAPAD databases and replace when matches are found, 

replace the ISO 2 and 3 character codes in the DoDAAD and MAPAD databases with the 

values in Column “E” and Column “F” respectively. 

b. If Column “K” (Non US Postal Flag) of the 

Country Code mediation table is not checked, construct the next-to-the-last address line 

in “City Name,” “ISO 2 Country Code,” and “Postal Code” order. If column “K” (Non 

US Postal Flag) is checked, then construct the next-to-the-last address line in “Postal 

Code,” “City Name,” ISO 2 Country Code order.

c. Construct a new last address line containing

the Country Name from Column “A” of the country code mediation table.

d. Rebuild the existing last address lines in the 

DoDAAD and MAPAD databases according to the criteria immediately above and 

provide subscribing systems with the changes via database replication, daily delimited 

files, or legacy TA_ batch transaction broadcasts according to their normal subscription 

medium. A precautionary note is that this update may need to be accomplished in phases 

to limit the volume of changes in any one broadcast.
ADC 448

Page 8

(4) MILSTD 129P Military Shipping Label (MSL) printing 

instructions and the DTR Changes. Both will need to be reconciled/amended to 

accommodate 5th address line to support the in-the-clear country name. The ISO Short 

Country name will be used for the clear text country name to satisfy both the USPS and 

ISO requirement. See page 132 of MIL-STD-129P w/CHANGE 4 that states, “DoDAAC

addresses from https://dodaac.wpafb.af.mil are structured as 4 lines of 35 characters -- the 

5th line in the “Ship To” and “Consignee” address blocks are to accommodate DLA 

addressing options, foreign military sales addressing, and foreign nation addresses.” 

USTRANSCOM will separately staff and publish any required changes to the DTR 

regarding the 5th line. Army, as the lead agent for the 129P will also need to separately 

staff a change to the 129P to address the 5th line requirement. The change will be 

coordinated and staffed by the Chief, Logistics Support Activity, Packaging, Storage and 

Containerization center, ATTN: AMXLS-AT. .All respondents were requested to 

identify other uses that may exist for the 5th line in the “Ship To” and “Consignee” 

addresses blocks that would preclude its use for identification of the in the clear text 

country name. Only DLA responded, indicating that DLA already uses the fifth 

address line to add the county short name.

(5) LOGDRMS Changes: Change LOGDRMS table title and 

description for qualifier table 85 to become the Security Cooperation Customer Code as 

shown in Enclosure 3. NOTE: The legacy MILSTRIP codes will be retained in 

LOGDRMS qualifier 85 and 85* until September 30, 2012 to support use for DLMS 

clear text addressing, at which time they will be removed upon simultaneous 

implementation of DoD Profile ISO-3166-1 code values for that process.

6) MILSTRIP “Country and Activity Code” Changes

(a) The MILSTRIP Appendix 2.18, Country and Activity Codes” 

will become “Security Cooperation Customer Codes.” This data element identifies the 

SAMM (reference f) as the authoritative source. Code values are contained in 

LOGDRMS qualifier table 85 and *85 “COUNTRY AND ACTIVITY CODE”, which is

revised as noted above. To convert to the original codes set for MILSTRIP Country and 

Activity Code to the code set for Security Cooperation Customer Code, eliminate the 

values assigned for purposes other than Security Cooperation Customer support as 

identified in enclosure 1. Changes to MILSTRIP Appendix 2.18, “Country and Activity 

Codes” to document the Security Cooperation Customer Code are shown in Enclosure 

4. NOTE: Legacy MILSTRIP codes removed by this change will be retained in the 

DLA Transaction Services mediation table indefinitely. Additionally, the legacy 

MILSTRIP codes will be retained in LOGDRMS qualifier 85 and 85* until September 

30, 2012 to support use for DLMS clear text addressing, at which time they will be 

removed upon simultaneous implementation of the DoD Profile ISO3166-1 code values 

for that process.

(b) Other applicable changes to MILSTRIP are shown in 

enclosures 5 through 7.
ADC 448

Page 9

(7) Component System Changes:

(a) Research hard coded logic based on country code values 

and modify when necessary to the new ISO-2 code values (such as restricting shipments 

to a certain country due to a JCS order).

(b) The Component Central Service Points (CSPs) responsible 

for their Component’s DoDAAC maintenance and the Component International Logistics 

Control Offices (ILCOs) responsible for MAPAC addresses will need to review their 

non-United States addresses that were originally entered as “Free Form” and modify the 

last two address lines according to the criteria in paragraphs 4.c.3) (b) (2) above.

(c) When displaying country information on Web Screens, 

reports, labels, and other outputs intended for human usage, preference should be given to 

the displaying the actual in-the-clear country name rather than the code whenever 

possible to avoid possible ambiguities.

(d) Army and Air Force will need to change their legacy 

DoDAAD Web maintenance, database and query capability to agree with the changes 

enumerated above for DLA Transaction Services DoDAAD applications.

(e) Applications using DoDAAD (MAPAD addresses already 

accommodate 5 address lines) data via database replication or legacy TA_ transaction 

broadcast of the batch changes to subscribing systems will need to be updated to 

accommodate the new 5th address line. For those legacy systems getting changes via 

TA_ transactions the old last address line will be indicated as a “Change” transaction and 

the new last address line will be indicated as an “Add”.

(f) Decide if the Component historical/archive transaction 

histories/databases will be updated to reflect the new country codes. If transaction 

histories are not changed, then any reports or queries against those archives will need to 

note the date of the transition to the new country codes and compensate for the before and 

after code for a given country. The DLA Transaction Services mediation table can be 

used to modify history or to compensate for the use of two or more code standards for the 

same country over a historical timeline.

5. REASON FOR CHANGE:

a. Because of the sunset of the FIPS 10-4, DoD must migrate to the ISO 

3166-1 Country code Standard by September 30, 2012. 

b. Accomplishing related changes facilitates efficiencies in system 

programming.
ADC 448

Page 10

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages:

(1) This change achieves DoD policy to implement ISO 3166-1 at the 

lowest cost. The ISO 3166-1 digraph (2 character code structure) country code is the 

most widely used standard in the world. By implementing ISO 3166-1 digraph to replace 

the existing 2 character standards, DoD logistics systems avoid cost associated with 

expanding an existing data field size in systems program logic, databases, and 

transactions.

(2) Using country code short names in lieu of codes supports USPS 

and ISO goals.

(3) Ensures consistency among MILSTRIP and DSCA codes values

used for DSCA logistics business transactions.

b. Disadvantages: Expenses are incurred to make the changes identified in 

this ADC. However, they are far outweighed by the increased interoperability from 

adoption of a single standard.

7. IMPACT:

a. Implementation: 

(1) DLA Transaction Service will drop the "JAN MAYEN" row as 

soon as possible.

(2) DOD profile ISO 3166-1 codes will be implemented for clear text 

addressing in DLMS transaction starting on October 1, 2012 to ensure consistent 

meaning of the two digit code values (ISO versus MILSTRIP) in all transactions. DLA 

(ICP and Distribution Depot will need to discontinue use of the internal 3- position 

country code.

(3) DLA Transaction Service will implement all other designated 

changes in this ADC no later than July 1, 2012.

(4) The Components will implement the ADC changes designated to 

them, between July 1, 2012 and September 30, 2012. 

b. Publication: The publication changes will be incorporated into the 

publications identified below prior to July 1, 2012, including a universal change from 

Country and Activity Code to Security Cooperation Customer Code, where applicable:

(1) DOD 4000.25-M (or its successor), Defense Logistics 

Management System
ADC 448

Page 11

(2) DOD 4000.25-1-M (or its successor) Military Standard Requisition 

and Issue Procedures (MILSTRIP) Note: Enclosure 5 through 8 identify changes to 

DoD 4000.25-1-M.

 

(3) The DoDAAD Standard Operating Procedures

(4) The DLMS Country Code Mediation Table

(5) The DoDAAD training, DLMS training Module 7

(6) DoDAAD file layout

(7) USTRANSCOM identified no applicable changes to the DTR 

regarding the 5th line.

(8) USTRANSCOM 856A may need to be updated to use ISO 3166-1. 

USTRANSCOM will need to review this IC and any other ICs using country codes

(9) Army, as the lead agent for the 129P may need to separately staff a 

change to the 129P to address the 5th line requirement. Applicable changes will be 

coordinated and staffed by the Chief, Logistics Support Activity, Packaging, Storage and 

Containerization center, ATTN: AMXLS-AT.

(10) Further changes, if required, will be addressee in a subsequent

administrative ADC adendum. 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: The ISO 3166-1 digraph code is the same 

length as the FIP 10-4. By maintaining a two digit code structure the costs associated 

with a field size change are avoided. 
Enclosure 1

ENCLOSURE 1

TRANSITIONING MILSTRIP COUNTRY AND ACTIVITY CODES TO

SECURITY COOPERATION CUSTOMER CODES 

The following country/activity codes are currently available in the mixed-purpose code set 

used for MILSTRIP/LOGDRMS. These codes must be removed in order to leave only 

valid Security Cooperation Customer Codes. The legacy MILSTRIP codes will be retained 

in LOGDRMS qualifier 85 and 85* until September 30, 2012 to support use for DLMS clear 

text addressing, at which time they will be removed upon simultaneous implementation of the 

DoD Profile ISO-3166-1 code values for that process.

COUNTRY NAME MILSTRIP 

CC

SA/FMS 

CC

AMERICAN SAMOA AQ

ANTARCTICA AY

ASCENSION ISLAND AX

ASHMORE AND CARTIER ISLANDS AI

BAKER ISLAND FQ

BOUVET ISLAND BV

CHRISTMAS ISLAND KT

CLIPPERTON ISLAND IP

COCOS (KEELING) ISLANDS CK

CORAL SEA ISLANDS CL

DIEGO GARCIA DG

FRENCH SOUTHERN AND ANTARCTIC ISLAND FS

GUAM GQ

GUERNSEY GK

HEARD AND MCDONALD ISLANDS HM

HOWLAND ISLAND HQ

JAN MAYEN JN

JARVIS ISLAND DQ

JERSEY JE

JOHNSTON ATOLL JQ

KINGMAN REEF KQ

MAN, ISLE OF IM

MAYOTTE YT

MIDWAY ISLANDS MQ

NO MAN’S ISLAND NM

NORTHERN MARIANA ISLANDS CQ

OCEANA OS

PALMYRA ATOLL LQ

PARACEL ISLANDS PF

PUERTO RICO PQ

SVALBARD SV

TRUK ISLAND TR

TRUST TERRITORY OF THE PACIFIC ISLANDS PS

VIRGIN ISLANDS (US) VQ

WAKE ISLAND WQ

WALLIS AND FUTUNA ISLANDS WF
Enclosure 1

Page 2

NOTE: The MILSTRIP/LOGDRMS Code 85 table is corrected as follows:

Change “YI(RB)” to read “RB(YI)” – “RB is the current code used for Serbia.
Enclosure 2

ENCLOSURE 2

REVISIONS TO DLMS SUPPLEMENTS

Section A - DS 511M Requisition Modification

# Location DS 511M Requisition Modification

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/210 Revise notes as follows:

26 Country Code

Federal Note:

Use to identify the country. Data element 1270, code 85 - Country 

and Activity Code, lists applicable code values.

Use to identify the country.

DLMS Note:

Pending transition to ISO, use for the Requisition Exception Data 

Transaction (DLA DI Code YRZ-Transaction Codes ST, MA and NA) 

with the N101 Codes DA and IF (when other than U.S.), and IAD for 

final address line to reflect the country code. May reflect DLA 3-

position country code. (DLA DI Code YRZ-Country Code in field

positions 43-45). See Introductory DLMS note 3f.

After September 30, 2012, use the ISO 3166- 1 two character 

country code in this field. See Introductory DLMS Note: 

Refer to ADC 448.

Clarification to 

implement ISO codes.

3 2/LQ01/140 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For MAP/GA transactions, use only when the coded 

address in the transaction number does not identify the type of 

country or activity. Use to identify the Security Cooperation

Customer Code (previously known as the MILSTRIP 

Country and Activity Code). Refer to ADC 448.

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

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 2

Page 2

Section B - DS 511R Requisition

# Location DS 511R Requisition 

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/210 Revise notes as follows:

26 Country Code

Federal Note:

Use to identify the country.

DLMS Note:

Pending transition to ISO, use for the Requisition Exception Data 

Transaction (DLA DI Code YRZ-Transaction Codes ST, MA and NA) 

with the N101 Codes DA and IF (when other than U.S.), and IAD for 

final address line to reflect the country code. May reflect DLA 3-

position country code. (DLA DI Code YRZ-Country Code in field 

positions 43-45). See Introductory DLMS note 3f.

After September 30, 2012, use the ISO 3166- 1 two character 

country code in this field. See Introductory DLMS Note Refer to 

ADC 448. 

Clarification to 

implement ISO codes.

3 2/LQ01/140 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For MAP/GA transactions, use only when the coded 

address in the transaction number does not identify the type of 

country or activity. Use to identify the Security Cooperation

Customer Code (previously known as the MILSTRIP 

Country and Activity Code). Refer to ADC 448.

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

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 2

Page 3

Section C - DS 4030 842A/R Standard Supply Discrepancy Report (SDR) Reply

# Location DS 842A/R SDR Reply

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/4400 Add Federal note and revise DLMS note as follows:

26 Country Code

Federal Note:

Use to identify the country.

DLMS Note:

1. Until September 30, 2012 use code values for Data element 

1270, Code 85, Security Cooperation Customer Code (previously 

known as the MILSTRIP Country and Activity Code), lists 

applicable code values. 

After September 30, 2012 use the ISO 3166- 1 two character 

country code in this field. See to introductory Note Refer to 

ADC 448.

2. WebSDR field length = 2

Clarification to 

implement ISO codes.
Enclosure 2

Page 4

Section D - DS 4030 842A/W SDR, Follow-up, Correction, Cancellation, & 

Reconsideration Request

# Location DS 842A/W SDR, Follow-up, Correction, Cancellation, & 

Reconsideration Request

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2 2/LQ01/1050 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For MAP/GA transactions, use only when the coded 

address in the transaction number does not identify the type of 

country or activity. Use to identify the Security Cooperation

Customer Code (previously known as the MILSTRIP 

Country and Activity Code). Refer to ADC 448.

2. For 85: WebSDR field length = 2

Clarification of data 

element name and 

elimination of obsolete 

information.

3. 2/N404/3100 Add Federal note and revise DLMS note as follows:

26 Country Code

Federal Note:

Use to identify the country.

DLMS Note:

1. Until September 30, 2012 use code values for Data Element 

1270, Code 85, Security Cooperation Customer Code (previously 

known as the MILSTRIP Country and Activity Code), lists 

applicable code values. 

After September 30, 2012, use the ISO 3166- 1 two character 

country code in this field. See introductory note Refer to 

ADC 448.

2. WebSDR field length = 2

Clarification to 

implement ISO codes.
Enclosure 2

Page 5

Section E - DS 856 Advance Shipment Notice (ASN)

# Location DS 856 Advance Shipment Notice (ASN)

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/250 Revise notes as follows:

26 Country Code

Federal Note:

Use only when other than the United States

Use to identify the country.

DLMS Note:

Until September 30, 2012 use code values for Data Element 1270, 

Code 85, Security Cooperation Customer Code (previously 

known as the MILSTRIP Country and Activity Code)lists

applicable code values. 

After September 30, 2012, use the ISO 3166- 1 two character 

country code in this field. See introductory note Refer to 

ADC 448.

Clarification to 

implement ISO codes.
Enclosure 2

Page 6

Section F - DS 4030 856R Shipment Status Material Returns

# Location (4030) DS 856R Shipment Status Material Returns

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/2500 Add Federal note and revise DLMS note as follows:

26 Country Code

Federal Note:

Use to identify the country.

DLMS Note:

1. Until September 30, 2012 use code values for Data element 

1270, Code 85, Security Cooperation Customer Code (previously 

known as the MILSTRIP Country and Activity Code) , lists 

applicable code values. 

After September 30, 2012 you must use the ISO 3166- 1 two

character country code in this field. The authoritative source of 

the country data is the GIG Technical Profile (GTP).

Clarification to 

implement ISO codes.
Enclosure 2

Page 7

Section G - DS 4030 856S Shipment Status

# Location DS 856S Shipment Status

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/2500 Add Federal note and revise DLMS note as follows:

26 Country Code

Federal Note:

Use to identify the country.

DLMS Note:

1. Until September 30, 2012 use code values for Data element 

1270, Code 85, Country and Activity Code, lists applicable code 

values. 

After September 30, 2012 you must use the ISO 3166- 1 two

character country code in this field. The authoritative source of 

the country data is the GIG Technical Profile (GTP).

Clarification to 

implement ISO codes.

3. 2/LQ01/3500 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For MAP/GA transactions, use only when the coded 

address in the transaction number does not identify the type of 

country or activity. Use to identify the Security Cooperation

Customer Code (previously known as the MILSTRIP 

Country and Activity Code). Refer to ADC 448.

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

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 2

Page 8

Section H - DS 869F Requisition Follow-up

# Location DS 869F Requisition Follow-Up

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/140 Add Federal note and revise DLMS note as follows:

26 Country Code

Federal Note:

Use to identify the country.

DLMS Note:

1. Until September 30, 2012 use code values for Data element 

1270, Code 85, Security Cooperation Customer Code (previously 

known as the MILSTRIP Country and Activity Code), lists applicable 

code values. 

After September 30, 2012 you must use the ISO 3166- 1 two

character country code in this field. The authoritative source of 

the country data is the GIG Technical Profile (GTP).

2. Use for the Requisition Exception Data Transaction (DLA DI Code 

YRZ-Transaction Codes ST, MA and NA) with the N101 Codes DA and 

IF (when other than U.S.), and IAD for final address line to reflect the 

country code. May reflect DLA 3-position country code. (DLA DI Code 

YRZ-Country Code in field positions.

Clarification to 

implement ISO codes.

3. 2/LQ01/180 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For MAP/GA transactions, use only when the coded 

address in the transaction number does not identify the type of 

country or activity. Use to identify the Security Cooperation

Customer Code (previously known as the MILSTRIP 

Country and Activity Code). Refer to ADC 448.

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

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 2

Page 9

Section I - DS 940R Material Release 

# Location DS 940R Material Release

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/N404/1103 Add Federal note and revise DLMS note as follows:

26 Country Code

Federal Note:

Use to identify the country.

DLMS Note:

1. Use to identify the country. Until September 30, 2012 use code 

values for Data element 1270, Code 85, Security Cooperation 

Customer Code (previously known as the MILSTRIP Country and 

Activity Code)lists applicable code values. After September 30, 

2012 you must use the ISO 3166- 1 two character country code in 

this field. The authoritative source of the country data is the GIG 

Technical Profile (GTP).

2. Use when transaction includes Component-unique MRO exception 

data (when other than U.S.) to reflect the country code. 

3. See introductory DLMS note 4e.

Clarification to 

implement ISO codes.

3. 2/LQ01/1300 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For MAP/GA transactions, use only when the coded 

address in the transaction number does not identify the type of 

country or activity. Use to identify the Security Cooperation

Customer Code (previously known as the MILSTRIP 

Country and Activity Code). Refer to ADC 448.

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

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 2

Page 10

Section J - DS 810L Logistics Bill

# Location DS 810L Logistics Bill

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2. 2/LQ01/230 Add Federal note and revise DLMS note as follows:

85 Country and Activity Code

Federal Note:

Use to identify the country.

DLMS Note:

1. Use to identify the country. Until September 30, 2012 use code 

values for Data element 1270, Code 85, Country and Activity Code, 

lists applicable code values. After September 30, 2012 you must 

use the ISO 3166- 1 two character country code in this field. The 

authoritative source of the country data is the GIG Technical 

Profile (GTP).

Clarification of data 

element name and 

elimination of obsolete 

information.

3. 2/LQ01/310 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For MAP/GA transactions, use only when the coded 

address in the transaction number does not identify the type of 

country or activity. Use to identify the Security Cooperation

Customer Code (previously known as the MILSTRIP 

Country and Activity Code). Refer to ADC 448.

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 2

Page 11

Section K - DS 870S Supply Status 

# Location DS 870S Supply Status

Revision 

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical 

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2 2/LQ01/145 Revise DLMS notes as shown:

85 Country and Activity Code

DLMS Note:

1. For Security Assistance (SA) transactions, use when the 

coded address in the transaction number does not identify the 

type of assistance and financing. . Use to identify the 

Security Cooperation Customer Code (previously known as 

the MILSTRIP Country and Activity Code). Refer to ADC 

448.

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

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 2

Page 12

Section L - DS 870N Notice of Availability Reply 

# Location DS 870N Notice of Availability Reply

Revision

Reason

1. Introductory 

Notes

Add guidance with location of the authoritative source for ISO 

country code set to the DLMS Introductory notes.

Subsequent to September 30, 2012, DLMS users must 

employ the International Organization for Standardization 

(ISO) Country Codes when providing geographic location 

by country. The authoritative source for ISO Country 

Codes is the Global Informational Grid (GIG) Technical

Profile (GTP). The existing DLA Transaction Service 

country code mediation table which will be updated from 

the authoritative source when it becomes available.

Add ADC 448 to DLMS Introductory note:

- ADC 448, Implementation of International Organization 

for Standardization (ISO) 3166-1 Codes for the 

Identification of Countries and their Subdivisions.

To identify code source.

To identify DLMS 

Changes included in the 

DLMS Supplement.

2 2/N103/50 Revise DLMS notes as shown:

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) Use to identify the Security 

Cooperation Customer Code (previously known as the 

MILSTRIP Country and Activity Code). Refer to ADC 448

Clarification of data 

element name and 

elimination of obsolete 

information.
Enclosure 3

ENCLOSURE 3 

CHANGES TO LOGDRMS

NAME COUNTRY AND ACTIVITY CODE

SECURITY COOPERATION CUSTOMER CODE

DEFINITION: SECURITY COOPERATION CUSTOMER CODE IS A TWO DIGIT 

CODE USED BY DEFENSE SECURITY COOPERATION AGENCY 

(DSCA) TO REPRESENT THE COUNTRY, INTERNATIONAL 

ORGANIZATION, REGION, OR PROGRAM AUTHORITY 

ASSOCIATED WITH TRANSACTIONS RECORDED IN SECURITY 

COOPERATION SYSTEMS AND ASSOCIATED WITH PROGRAMS 

IMPLEMENTED IN THE FOREIGN MILITARY SALES TRUST FUND. 

IDENTIFIES THE SHORT NAMES AND TWO POSITION COUNTRY AND

ORGANIZATION CODES ASSIGNED FOR FMS PURPOSES (E.G., FOR 

ASSIGNMENT OF LETTERS OF OFFER AND ACCEPTANCE (LOA)

IDENTIFIERS OR SECURITY ASSISTANCE COMMUNICATIONS). THE 

COUNTRY CODES ARE GENERALLY CONSISTENT WITH NATIONAL 

INSTITUTE OF STANDARDS (NIST) CODES IN NIST PUBLICATION 10-

4, FEDERAL INFORMATION PROCESSING STANDARDS MAINTAINED 

BY NATIONAL GEOSPACIAL-INTELLIGENCE AGENCY (NGA). IF FMS 

AND NIST CODES DIFFER, NIST CODES ARE LISTED IN PARENTHESES 

TO THE RIGHT OF THE FMS CODE.

REMARKS: REFER TO DOD 5105.38-M SECURITY ASSISTANCE MANAGEMENT 

MANUAL (SAMM) CHAPTER 4 TABLE C4.T2. ALSO, REFER TO DOD 

4000.25-1-M MILITARY STANDARD REQUISITIONING AND ISSUE 

PROCEDURES (MILSTRIP), AP 2.18 (APPENDIX 2.18) AND DOD 

4000.25-M (DLMS) VOLUMES 1 AND 2. LOGISTICS QUALIFIER *85 

LISTS COUNTRY AND INTERNATIONAL CODES IN ALPHABETIC 

SEQUENCE WITHIN COUNTRY/TERRITORY AND WITHIN 

ORGANIZATION NOTE: THIS TABLE CONTAINS LEGACY 

MILSTRIP CODES UNTIL SEPTEMBER 30, 2012 TO SUPPORT 

USE FOR DLMS CLEAR TEXT ADDRESSING, AT WHICH TIME 

THEY WILL BE REMOVED UPON SIMULTANEOUS 

IMPLEMENTATION OF THE DOD PROFILE ISO-3166 CODE 

VALUES FOR THAT PROCESS.

SOURCE: DEFENSE SECURITY ASSISTANCE MANAGEMENT MANUAL (SAMM), 

DOD 5105.38-M CHAPTER 4 TABLE C4.T2 

AVAILABLE 

FROM:

DEFENSE SECURITY COOPERATION AGENCY (DSCA) 
Enclosure 3

Page 2

ABSTRACT: THE SAMM PROVIDES A COMPREHENSIVE SET OF POLICIES AND 

PROCEDURES RELATED TO SECURITY ASSISTANCE MATTERS WITHIN 

THE DEPARTMENT OF DEFENSE. 
Enclosure 4

ENCLOSURE 4

CHANGES TO MILSTRIP APPENDIX 2.18

AP2.18. APPENDIX 2.18

COUNTRY AND ACTIVITY CODES

SECURITY COOPERATION CUSTOMER CODES 

NUMBER OF CHARACTER: Two

TYPE OF CODE: Alpha-Alpha or Alphanumeric

EXPLANATION: Country and Activity Codes Security Cooperation Customer Codes are 

listed on the Defense DLA Logistics Management Standards Office 

(DLMSO) Web site under: Logistics Qualifier Search/Select Qualifier 

Code from Table of Contents/Key Word “Country and Activity”

“Security Cooperation Customer” at http://www.dla.mil/j6/dlmso/eApplications/Logdrms/logview/LQVSearch.asp. The country 

and activity Security Cooperation Customer Code is a two-digit code 

used by Defense Security Cooperation Agency to represent the 

country, international organization, region, or program authority 

associated with transactions recorded in Security Cooperation systems 

and associated with programs implemented in the Foreign Military 

Sales Trust Fund. Activity codes may be applied to organizations, 

regions, territories, or programs which do not have established country 

codes. NOTE: Inclusion of a country or activity in this appendix does 

not, of itself, indicate that the country or activity is now or ever has 

been or will be a recipient of Security Assistance. The authoritative 

source for these values is DOD 5105.38-M Security and Assistance 

Manual (SAMM) Chapter 4, Table C4.T2. 1

RECORD POSITION(S):

 

31-32

 1 Legacy MILSTRIP codes will be retained in LOGDRMS qualifier 85 and 85* until September 30, 2012 

to support use for DLMS clear text addressing, at which time they will be removed upon simultaneous

implementation of the DoD Profile ISO-3166 code values for that process.
Enclosure 5

ENCLOSURE 5 

Changes to MILTRIP CHAPTER 6

C6. CHAPTER 6

SECURITY ASSISTANCE PROGRAM

C6.1 GENERAL

C6.1.1. The provisions of MILSTRIP apply to all phases of requisitioning and issue to support the 

Security Assistance Program; however, this chapter provides special procedures and instructions for 

preparing and processing Foreign Military Sales (FMS) and Grant Aid requirements (see AP2.19) which 

are exceptions to other areas of the manual.

C6.2. RESERVED

C6.3. REQUISITION FORMATS

C6.3.1. Requisitions for FMS and Grant Aid materiel vary from the construction of requisitions in 

support of U.S. Forces. Codes peculiar to FMS and Grant Aid requisitions are listed in the designated 

appendices and the DLM 4000.25 Volume 6, chapter 3, together with their meanings and applications. 

Specific FMS and Grant Aid requisition entries are as follows:

C6.3.1.1. Grant Aid

C6.3.1.1. Requisitioner Field (rp 30-35)

C6.3.1.2. Rp 30 will contain the FMS and Grant Aid service assignment code (AP2.2) 

of the U.S. Service Implementing Agency responsible for administering the Military Assistance Program 

(MAP) Grant Aid Program line.

C6.3.1.3. Rp 31-32 will contain the country/activity Security Cooperation Customer

code (AP2.18).

C6.3.1.4. Rp 33 will contain the customer-within-country/activity code to indicate the 

recipient or place of discharge within the country/activity (see MAPAD), with the exception of requisitions 

containing DI A05 with special one-time shipping instructions entered in the Remarks block of the 

requisition. In this instance, a DI A05 requisition may contain a zero in rp 33. The special instruction will 

include an address to receive documentation when documents are not to be forwarded to the ship-to 

address. The use of DI A05 requisitions will be limited to one-time situations where it is not practicable to 

designate the addresses by coded entries in the requisition and in the MAPAD.

C6.3.1.5. Rp 34 will contain a numeric zero (0).

C6.3.1.6. Rp 35 will contain the appropriate MAP Grant Aid type of 

assistance/financing code (AP2.19).

C6.3.1.2. Supplementary Address Field (rp 45-50)

C6.3.1.2.1. Rp 45 will contain Y to indicate that the data entered in rp 46-50 are 
Enclosure 5

Page 2

nonsignificant to the overall systems but are to be perpetuated in all subsequent documentation.

C6.3.1.2.2. Rp 46-50 will contain the Record Control Number (RCN). This number is 

assigned by the appropriate Service activity and is constructed as follows:

C6.3.1.2.3. Rp 46 will contain the last digit of the program year in which the 

requisitioned item was approved and funded.

C6.3.1.2.4. Rp 47-50 will contain the four-position program line item number 

(alpha/numeric) or the program.

C6.3.2. Foreign Military Sales

C6.3.2.1. Requisitioner Field (rp 30-35)

C6.3.2.1.1. Rp 30 will contain the FMS and Grant Aid Service assignment code 

(AP2.2) of the U.S. Service Implementing Agency responsible for administering the FMS Case.

C6.3.2.1.2. Rp 31-32 will contain the country/international organization Security 

Cooperation Customer code (AP2.18).

C6.3.2.1.3. Rp 33 will contain the customer-within-country code. This code will be 

assigned and recognized in conjunction with entries in rp 46-47. The application of the customer-withincountry code in relation to coded entries in rp 46-47 is explained in paragraph C6.3.2.3., below. When a 

customer-within-country code is not applicable, a zero will be entered.

C6.3.2.1.4. Rp 34 will contain the FMS delivery term code (see Defense 

Transportation Regulation (DTR) or DLMS Dictionary (Logistics Data Resources Management System 

(LOGDRMS) for code definition and applicable values) to convey the point of delivery condition 

negotiated under the case agreement and must correspond to delivery terms specified in the applicable 

Letter of Offer and Acceptance.

C6.3.2.1.5. Rp 35 will contain the appropriate FMS type of assistance/financing code 

(AP2.19).

C6.3.2.2. Supplementary Address Field (rp 45-50)

C6.3.2.2.1. Rp 45 will contain the FMS Service code (AP2.2) of the customer 

country’s requisitioning Service, which is published in the Military Assistance Program Address Directory

(MAPAD).

C6.3.2.2.2. Rp 46 will contain the applicable country FMS offer/release option code 

(A, Y, or Z) or code X to denote that the United States is responsible for transportation arrangements, as 

determined by negotiations between the customer CR and the U.S. Service responsible for administering 

the FMS case, and as reflected in the Case Agreement. Country FMS offer/release option codes are listed 

in the definitions and terms section of this manual with explanations of their application and recognition 

under FMS offer and release procedures. 

C6.3.2.2.3. Rp 47 will contain a code to designate the recipient of shipments and 

documentation and will be the FMS country representative/freight forwarder (CR/FF) code as published in 

the MAPAD. This entry and the use of code X or W will be applied and recognized in conjunction with the 

entry in rp 33 as explained in paragraph C6.3.2.3., below.

C6.3.2.2.4. Rp 48-50 will contain the specific FMS case designator consisting of a 

three-position alpha/numeric code. The first position will always be alphabetic and the second and third 
Enclosure 5

Page 3

positions may be alphabetic or numeric. All correspondence (such as letters and messages) will always 

include the appropriate country/international organization Security Cooperation Customer Code, U.S. 

Service Implementing Agency and case designator (e.g. BN-B-ABC) as part of the identification data.

C6.3.2.3. Designation of Shipment Addresses for Foreign Military Sales

C6.3.2.3.1. The means of expressing ship-to and/or mark-for addresses in requisitions 

are the entries shown in rp 33 (customer-within-country) and rp 47 (CR/FF), respectively. The designation 

of such addresses will be consistent with delivery terms contained in the case agreement. Specific codes 

will not be utilized in requisitions until such time as the codes and corresponding addresses are published in 

the MAPAD.

C6.3.2.3.1.1. The DAAS will reject requisitions, referral orders, passing orders,

DI AT_ follow-ups, and DI AM_ modifiers, containing Military Assistance Program Address Code

(MAPACs) that do not have valid ship-to and mail-to addresses in the MAPAD, to the submitting 

International Logistics Control Office (ILCO). (Supply Status (DI AE9) with Status Code DP applies.)

C6.3.2.3.1.2. The ICPs may reject requisitions received off-line (mail, message, 

courier, fax, telephone) which contain MAPACs that do not have valid ship-to and mail-to addresses in the 

MAPAD, to the submitting ILCO. This includes remarks/exception type DI A05/A0E requisitions 

directing materiel to various shipping points. (DI AE_ with Status Code CX applies).

C6.3.2.3.1.3. When shipment is to be made to a CR/FF or to a point designated 

by a CR/FF in response to a Notice of Availability (NOA), a specific code other than an X or W will be 

entered in rp 47. In this instance, the ship-to address will be the address listed in the MAPAD for the 

CR/FF or the address provided in response to the NOA. The mark-for address will be the address listed in 

the MAPAD for the code in rp 33. For those countries which have elected not to publish clear-text 

addresses for rp 33 codes, there will be no mark-for address, but supply and shipping activities will 

perpetuate the rp 33 code in all related documentation. When a customer-within-country code is not 

applicable, a zero will be entered.

C6.3.2.3.1.4. When shipment is to be made to an assembly point or staging 

area, a XW will be entered in rp 46-47 and a clear-text address will be conveyed in an exception 

requisition. See paragraph C6.3.2.4.3. The rp 33, if required, will designate the mark-for address.

C6.3.2.3.1.5. When shipment is to be made to an address within the customer 

country, an XX will be entered in rp 46-47 and the in-country ship-to address will be the address listed in 

the MAPAD for the code in rp 33. See paragraph C6.3.2.4.3.

C6.3.2.3.1.6. The foregoing instructions apply to all customer countries except 

Canada. For Canada, shipment address codes are contained in rp 46 and 47.

C6.3.2.4. Country FMS Offer/Release Option Codes

C6.3.2.4.1. Country FMS offer/release option codes are used in requisitions for 

shipments to be made or offered to CR/FFs. These codes specify whether shipments are to be made 

automatically or under one of two types of NOAs and will be consistent with the conditions of the FMS 

case agreements. Country FMS offer/release option codes are not applicable to requisitions for Canada 

since FFs are not utilized for Canada and both rp 46 and 47 are used to denote shipment addresses.

C6.3.2.4.2. Country FMS offer/release option codes and their explanations are 

contained in the definitions and terms section of this manual.

C6.3.2.4.3. If, consistent with the conditions of the FMS case agreements, 

transportation arrangements for shipments will be accomplished by the U.S. Service, an X will be entered 
Enclosure 5

Page 4

in rp 46 in lieu of a country FMS offer/release option code. When an X is authorized and entered in rp 46, 

an X or W, denoting shipment to an address within the customer country or shipment to an assembly point 

or staging area, must be entered in rp 47.

C6.4. RESERVED

C6.5. REQUIRED AVAILABILITY DATES

C6.5.1. Requisitions for FMS and Grant Aid requirements for major weapons systems, end items, 

and concurrent spares will be prepared to reflect the amount of time remaining from dates of requisitions 

until RADs become effective. In FMS cases the Required Availability Date (RAD) will be computed by 

adding the lead time stated on the Letter of Offer and Acceptance (LOA) to the date of acceptance by the 

purchaser. For Grant Aid, the RAD will be computed by adding the ICP determined lead time to the date 

of the MAP order.

C6.5.2. The requisition RAD will be expressed as the number of months remaining from the date of 

the requisition to the computed RAD which will be entered in rp 63-64 of the requisition. The character A 

will be inserted in rp 62. This technique enables supply source, ILCO, and customer control of 

requisitions, provides for recognition of firm commitments to foreign governments, and helps assure that 

materiel requirements are ready for delivery by the approved RAD. The actual date for calculation of the 

RAD will be the last day of the month depicted by the rp 62-64 entries. Shipment of materiel will be made 

at the time of initial requisition processing to the extent that releasable assets are available regardless of the 

number of lead time months shown in rp 63-64 of the RAD entry. Materiel not immediately available 

should be acquired and shipped by the last day of the month depicted by the rp 63-34 entries. However, 

depending on availability, materiel may be acquired and shipped after the RAD expires and cancellations 

are submitted. Appropriate status will be provided to the address(es) designated in the requisition.

C6.5.3. For Grant Aid, as soon as practicable, but not later than 120 days after receipt of an 

approved funded order, the Security/Agency (S/A) Departments will place a RAD on the requisitions for 

major items, and the associated support equipment and initial issue parts, as determined by the S/A.

C6.5.4. RAD time begins with the date of the requisition (i.e., the date contained in the requisition 

document number (See Appendix 2.14)) and does not have the effect of holding release of the materiel.

C6.5.5. Requisition originators will modify the RADs when contract forecast delivery dates indicate 

availability of items at a time other than designated by the previously established RADs. In inter-S/A 

actions, when requisitions or other documents bear a RAD with a shorter lead time than when the materiel 

will be available, the supplying S/A will promptly provide the requesting S/A with status reflecting the true 

availability date. This will be accomplished by use of DI AE_ with Supply Status Code BB, BV, or B3, as 

appropriate. The requesting S/A will adjust all records to reflect the new availability date information. 

When the supplying S/A is aware that the established RAD will not be met, that S/A’s supply source will 

advise the appropriate ILCO that the RAD will not be met due to slippage and internal processing. The 

advice of RAD slippage will be furnished the ILCO by letter, message, or DI AE_ with Supply Status Code 

B3.

C6.5.5.1. An extended Required Delivery Date (RDD) in an FMS requisition will be 

expressed with the letter S in rp 62, and the number of months from the date of the requisition before which

delivery is required entered in re 63-34 of the requisition. The release date is defined as 5 days prior to the 

last day of the month indicated in rp 63-64 Releasable assets will be held until 50 days prior to the last day 

of the month indicated.

C6.6. RESERVED

C6.7. REQUISITION PREPARATION AND SUBMISSION
Enclosure 5

Page 5

C6.7.1. Requisitions will be prepared and transmitted by FMS purchasers and SAOs to the 

applicable ILCO in the appropriate MILSTRIP format as prescribed by the U.S. Service. The ILCO will 

transmit FMS and Grant Aid requisitions to the appropriate supply source in the prescribed DoD 

MILSTRIP format.

C6.7.2. Requisitions prepared by the U.S. Service for FMS and Grant Aid requirements will be 

transmitted to the appropriate supply source in the prescribed MILSTRIP format.

C6.7.3. ILCOs will enter a Cooperative Logistics Support Program Code (CLPSC) (AP2.22) in rp 

72 of applicable requisitions and passing orders, in order to convey programmed/nonprogrammed status of 

a requisition to an ICP/IMM. Supply support, provided under CLSSA agreements, is intended to provide 

support to the requiring nation on the same basis that support is provided to U.S. Forces, within assigned 

priority (based upon Force or Activity Designator (F/AD)) and with all other coding being equal. 

However, such support cannot be provided if the combat effectiveness of U.S. Forces would be impaired 

thereby. Consequently, CLSSA support is not to be provided on the same basis as for U.S. Forces until 

after the expiration of a lead time period necessary to augment U.S. Stocks to support the agreement. 

CLSSA requisitions received before the expiration of required lead time may be filled from existing supply 

source stocks only if stock levels do not drop below the established reorder point. If sufficient stock 

balances are not available to fill such requisitions without dropping below the reorder point, supply sources 

will initiate procurement action to fill the CLSSA requirement. CLSSA requisitions received prior to 

expiration of the established lead times are considered to be “unprogrammed” requirements. 

Unprogrammed CLSSA requisitions and passing orders will contain CLPSC 2 in rp 72 (AP2.22). CLSSA 

requisitions and passing orders received after expiration of the lead time required to augment stock levels 

will be processed in the same manner as U.S. demands. Such requisitions and pass order are considered to 

be “programmed” requirements and will contain CLPSC 1 in rp 72. If rp 72 is blank when the requisition 

is received by the ICP/IMM, the requisition will be processed as an unprogrammed requirement.

C6.7.4. Certain FMS and Grant Aid requisitions will be subject to a restriction in quantity when it is 

determined that the total requirement for an item will result in more than 25 shipment units. This constraint 

is employed to preclude the assignment of non-MILSTRIP TCNs, which occurs when the number of 

shipment units exceeds 25 and which causes a loss of identity to the shipment. The Services will specify 

those items of equipment to which the quantity restriction applies. Generally, these items will be 

equipment such as wheeled/tracked vehicles or other items when a unit of issue of one each will constitute 

a single shipment unit.

C6.8. RESERVED

C6.9. STATUS IN GENERAL2

C6.9.1. Supply sources will provide status only to the ILCO or other monitoring activities identified 

in rp 54 of AP3 formats. DI AE3 will be used on supply status, and DI AS3 will be used on shipment 

status in response to follow-ups. However, DI AE8/AS8 will be used in supply source initiated status. It is 

the responsibility of the ILCO or monitoring activity to furnish status to the appropriate country status 

recipient.

C6.9.2. Status from the ILCO/monitoring activity to the MAPAD country status recipient will be 

transmitted through the DAAS.

C6.9.3. Status to FMS customers is sent to the MAPAD Type of Assistance Code or Transportation 

Account Code (TAC) 4 country status recipient.

C6.9.4. Status to Grant Aid customers is sent to the MAPAD TAC 3 purchaser/in-country SAO 

 2 Revised FMS status procedures last reported as not implemented by DLA (Subsistence). Refer to AMCL 

156.
Enclosure 5

Page 6

status recipient.

C6.9.5. The M&S entry in rp 7 should be zero to preclude unnecessary status output. The 

transmission medium is determined by DAAS.

C6.10. STATUS UPON REQUISITION INITIATION OR SUBMISSION3

C6.10.1. General. Status is provided by the ILCO to the customer when the requisition enters the 

supply system.

C6.10.2. Service Initiated Requisitions. When FMS requisitions are prepared and introduced by a 

U.S. Service, a supply status document representing the U.S. prepared requisition will be transmitted by the 

introducing U.S. Service to the appropriate MAPAD status recipient. The supply status document may also 

be prepared for CONUS generated Grant Aid transactions and, when prepared, will be transmitted to the 

appropriate in-country SAO. The supply status (DI Code AE_) will contain a code A thru E in the third 

position to reflect the type of stock number being requisitioned. It is desired that the latest available unit 

price be entered in rp 74-80; however, this is an optional entry depending on the capability of the Service 

involved. Status Code BU will be entered in rp 65-66 and the ESD in rp 70-73 may be left blank.

C6.10.3. Customer Initiated Requisitions.

C6.10.3.1. When purchaser prepared FMS requisitions are forwarded to supply sources by 

the ILCO, supply status with DI AE2 citing Status Code BW will be provided to the customer.

C6.10.3.2. When Grant Aid requisitions prepared by the in-country SAO are forwarded to 

supply sources by the ILCO, supply status with DI AE1 citing Status Code BW will be provided to the 

customer/SAO.

C6.10.3.3. The latest available unit price may be entered in rp 74-80, and the ESD in rp 70-73 

may be left blank.

C6.11. FOLLOW-UPS AND STATUS RESPONSES4

C6.11.1. As authorized, follow-ups, modifiers, and cancellations for FMS and Grant Aid 

transactions may be submitted by RCS or in-country SAOs to the sources(s) designated by the individual 

U.S. Service administering the FMS case or MAP Grant Aid program line.

C6.11.2. When follow-ups are submitted to the ILCO/monitoring activity, the latest status 

information will be furnished to the CR by the ILCO/monitoring activity.

C6.11.3. FMS requisition status will contain DI AE2 or AS2.

C6.11.4. Grant Aid requisition status will contain DI AE1 or AS1.

C6.11.5. When current status information is not available on requisitions that have been submitted 

to the supply system, the ILCO/monitoring activity may transmit the follow-up to the appropriate supply 

source or provide interim status to the customer pending completion of ILCO/monitoring activity follow-up 

action. In either case, a supply status document containing Status Code BW or BM (as indicated by the 

U.S. Service) and a blank ESD field may be provided to the customer. When requisitions have not been 

introduced into the supply system, the ILCO/monitoring activity will provide a written reply to the 

customer originated follow-ups.

 3 See Footnote 1.

4 See Footnote 1.
Enclosure 5

Page 7

C6.12. CANCELLATION AND REJECTION STATUS5

C6.12.1. Cancellation and rejection status from the supply source will be provided to the 

ILCO/monitoring activity citing DI AE3 and the appropriate status code.

C6.12.2. DI AE1/AE2 supply status transactions will not be produced by the supply source on FMS 

and Grant Aid requisitions.

C6.13. STATUS ON FOREIGN MILITARY SALES NOTICE OF AVAILABILITY6

C6.13.1. When FMS requisitions are processed and an NOA is forwarded to the CR/FF, a DI AE2 

supply status transaction containing Status Code BL will be furnished to authorized status recipients at the 

same time the NOA is forwarded. The BL status advises that the item is available for shipment and was 

offered to the CR/FF on the date entered in rp 70-73.

C6.14. MODIFICATION OF COUNTRY FOREIGN MILITARY SALES OFFER/ RELEASE OPTION 

OR FREIGHT FORWARDER7

C6.14.1. Unusual circumstances may require a change in the country FMS offer/release option code 

or freight forwarder code for an FMS case or for individual requisitions within an FMS case. When this 

condition exists, FMS customers or ILCO/monitoring activity may initiate DI AM_ requisition modifier to 

change the coded data in FMS requisitions that have been released to the supply system.

C6.14.2. FMS requisition modifier transactions will be initiated under chapter 2, paragraph C2.19. 

Entries in the requisition modifier transaction may differ from those in the original requisition only to 

reflect changes to one or any combination of the following:8

C6.14.2.1. Media and Status, rp 7.

C6.14.2.2. Country FMS Offer/Release Option, rp 46.

C6.14.2.3. Freight Forwarder, rp 47.

C6.14.2.4. Signal, rp 51.

C6.14.2.5. Fund, rp 52-53.

C6.14.2.6. Distribution, rp 54.

C6.14.2.7. Project, rp 57-59.

C6.14.2.8. Priority Designator, rp 60-61.

C6.14.2.9. Required Availability Date, rp 62-64.

C6.14.2.10. Advice, rp 65-66.

C6.14.3. Modifiers which change the country FMS offer/release option or FF must be submitted to 

 5 See Footnote 1.

6 See Footnote 1.

7 See Footnote 1.

8 Revised requisition modifier procedures last reported as not implemented by USMC. Refer to AMCL 

123C.
Enclosure 5

Page 8

procurement for manual amendment of contracts. Customers are responsible for additional charges which 

may accrue. To limit manual processing and avoid additional contract charges, modifiers which change the 

country FMS offer/release options or FFs should be submitted only when the change is mandatory. When 

LOAs have not been amended to reflect the changes, FMS customers must coordinate with the Service 

ILCO/monitoring activity before requesting requisition modification.

C6.15. RELEASE OF FOREIGN MILITARY SALES SHIPMENTS

C6.15.1. General

C6.15.1.1. The procedures to be followed in releasing shipments of FMS materiel from 

storage activities are normally dependent upon the entry in rp 46 of requisitions or related transactions. 

The exceptions to use of the country FMS offer/release option code in rp 46 in the release of shipments are:

C6.15.1.1.1. When the shipment is unclassified and is to be accomplished by parcel 

post/small parcel delivery service, the shipment will be released automatically without an NOA regardless 

of the entry in rp 46 and should be either insured, certified, or registered. Evidence of shipment must be 

provided for all FMS shipments regardless of shipment size, weight, or value. Classified shipments always 

require use of an NOA, as indicated below.

C6.15.1.1.2. When an export release is required from SDDC under DoD 4500.9-R

(DTR), Chapter 203 (Shipper, Transshipper, and Receiver Requirements and Procedures), the shipping 

activity will submit a request for export release to the SDDC Operations Center before shipment. An NOA 

will be furnished to the CR/FF and will indicate that an export release has been requested. The export 

release provided by the SDDC releasing authority will include shipping instructions as coordinated with the 

CR/FF.

C6.15.1.1.3. When the shipping activity determines that the shipment includes 

materiel that is dangerous/hazardous, sensitive, or otherwise requires a high degree of protection or control 

within CONUS, but does not require an export release. Note that Offer/Release Option Z procedures must 

be followed if any unusual transportation factors apply. This includes oversize or overweight shipments, 

hazardous materiel shipments, classified shipments, sensitive shipments, and ammunition, arms and 

explosives shipments or any other factor that mandates coordinated release procedures (this does include 

Canada). Shipment must not be made until a response from the NOA is received.

C6.15.1.1.4. From SDDC, an NOA will be furnished to the CR/FF regardless of the 

entry in rp 46 and the shipment will be held pending receipt of release and shipping instructions from the 

CR/FF. NOAs for classified shipments will be forwarded to the CR identified in the MAPAD.

C6.15.1.1.5. For shipments not subject to the exceptions outlined in paragraph 

C6.15.1.1., above, the entry in rp 46 will prescribe procedures to be followed in releasing shipments of 

FMS materiel from storage activities. When Country FMS Offer/Release Options Y and Z are entered in rp 

46, notification to the designated CR/FF is required prior to release of the shipment. When rp 46 contains 

Country FMS Offer/Release Option A or X, the shipment will be released automatically, without providing 

an NOA to the CR/FF.

C6.15.1.1.6. U.S. shipping activities use the NOA to notify the designated CR/FF 

addressee that materiel is ready for shipment. A manual NOA will be prepared for all FMS purchases

except those customers specifically requesting mechanized NOAs such as the Federal Republic of 

Germany. Countries desiring to receive the mechanized NOA will submit a request to the Director, 

Defense Logistics Management Standards Office. All purchasers requesting the mechanized NOA will be 

identified in this paragraph. Procedures for NOA preparation are contained in paragraphs C6.15.2. and 

C6.15.3., below.
Enclosure 5

Page 9

C.16.15.1.1.7.The NOA document, manual or mechanized, will be assigned a notice 

number. The FMS notice number will be the Transportation Control Number (TCN) assigned to the 

shipment and created In accordance with guidance in the DTR 4500.9, Appendix L.

C6.15.2. Manual Notice of Availability

C6.15.2.1. The DD Form 1348-5, Notice of Availability/Shipment, will serve as a cover 

document for individual copies of the DD Form 1348-1A applicable to each line item in a shipment unit. 

Together, these documents will comprise the original NOA. The data to be entered on the DD Form 1348-

5 are that which describe the shipment unit, while the supporting copies of the DD Form 1348-1A provide 

individual item data. All blocks of the DD Form 1348-5 from the top of the form to the portion captioned 

“TO BE COMPLETED BY ADDRESSEE” will be completed by initiating activities when the applicable 

shipment units are consolidated. In instances of single-line item shipment units, the following data are not 

mandatory entries on the DD Form 1348-5 if they are contained in the accompanying copies of the DD 

Form 1348-1A; type pack, pieces, weight, and cube. All data blocks are self-explanatory, except that the 

NOA date (the date notice is transmitted) will be entered in the block titled “Notice of Availability/ 

Shipment.” The “Notice Number” block will contain the control number (such as the TCN or GBL) 

assigned to the shipment. When an export release is required from the SDDC, the DD Form 1348-5 will be 

annotated or stamped in the lower left corner “EXPORT RELEASE REQUIRED.” The shipping activity 

will also annotate or stamp brief notes applicable to materiel discussed in paragraph C6.15.1.1.3., when 

appropriate. The manual NOA will be mailed to the notice recipient specified in the MAPAD except that 

the NOAs covering classified shipments will be forwarded to the country representative. Distribution of 

DD Form 1348-5 (AP1.4) will be as follows:

COPY NO. USE

1 Retained by the shipping activity pending receipt of shipment release instructions.

2, 3 Furnished to the appropriate CR/FF address (as designated in the MAPAD to receive the 

NOA) with copies of the DD Form 1348-1A, for insertion of shipment release instructions 

on the third copy and return to the shipping activity. The second copy will be retained by 

the CR/FF.

C6.15.2.2. Replies to manual NOAs will be accomplished by two different methods. When 

an export release is required, the CR/FF will furnish specifying consignment instructions, if any, and 

coordinate these or other shipment or delivery instructions with SDDC releasing authority. When an export 

release is not required, the reply will be accomplished by insertion of shipment release instruction on the 

third copy, which will be returned to the issuing activity. Shipment release instructions will provide for 

shipment or delivery of materiel to a single destination by shipment unit. Instructions to CR/FFs regarding 

replies to NOAs will specify the need for coordinated instructions when an export release is required and 

include provisions for the following minimum data in the replies to other NOAs:

C6.15.2.2.1.The complete name and address of the consignee except when materiel 

will be picked up by the CR/FF.

C6.15.2.2.2. The date materiel is to be shipped or the date the materiel will be picked 

up by the CR/FF.

C6.15.2.2.3. The complete name and telephone number(s) of the individual(s) who 

will be available and authorized to receive on behalf of the purchaser, for the specific classified shipment 

covered by the NOA advising of the availability of a classified shipment.

C6.15.2.3. In instances where the shipment does not require an export release or the shipping 

activity has determined that there is no requirement for a high degree of protection or control and Country 

FMS Offer/Release Option Y is contained in rp 46, the shipment will be released to the CR/FF on the 15th

calendar day after the NOA date, unless alternate shipping instructions are received. When an export 
Enclosure 5

Page 10

release is required, the shipment will be held pending receipt of release and shipping instructions from the 

SDDC releasing authority and if such instructions are not received within 15 calendar days after the NOA 

date, a follow-up only to SDDC will be made in lieu of transmitting a duplicate NOA. In instances where 

the shipping activity has determined a need for a high degree of protection of control or Country FMS 

Offer/Release Option Z is contained in rp 46, the shipment will be held pending receipt of release and 

shipping instructions from the CR/FF. Should such instructions not be received within 15 calendar days 

after the NOA date, a duplicate of the NOA will be transmitted to the designated notice recipient, with the 

same shipment unit number assigned. This duplicate NOA will be annotated to indicate that the shipment 

delay is caused by the CR/FF’s failure to furnish release and shipping instructions. Two copies of the DD 

Form 1348-5, Notice of Availability/Shipment, together with the DD Form 1348-1A, will constitute the 

delay NOA. The Service focal point will be advised of the problem for Army and Air Force sponsored 

shipments; the Navy freight forwarder assistance office will be advised for Navy and Marine Corps 

sponsored shipments.

C6.15.3. Mechanized Notice of Availability. Except for classified shipments or unclassified 

shipments to be accomplished by parcel post/small parcel delivery service, the mechanized FMS NOA is 

provided to customers having a need to receive mechanized data for FMS shipments when Country FMS 

Offer/Release Option Y or Z is entered in rp 46 of requisitions or when an export release is required. The 

mechanized NOA consists of the following documents:

C6.15.3.1. The FMS NOA key document will contain shipment unit information and will 

accompany the FMS NOA detail document. The initial key document will contain DI AD1 when an export 

release is not required and DI ADR when an export release is required. When release instructions have not 

been received within 15 days of the DI ADR NOA date, a follow-up will be made to the SDDC releasing 

authority and a delay NOA key document, DI AD3, will not be prepared or transmitted to the CR/FF. 

When Country FMS Offer/Release Option Z applies and release instructions have not been received within 

15 calendar days of the DI AD1 NOA date, a delay NOA key document containing DI AD3 will 

accompany the delay NOA detail documents.

C6.15.3.2. The FMS NOA detail document will contain line item information as contained in 

the issue/release document; such as, the MRO or DD Form 1348-1A. The initial detail document will 

contain DI AD2. When Country FMS Offer/Release Option Z applies and release instruction have not been 

received within 15 calendar days of the NOA date, a delay detail document containing DI AD4 will be 

prepared for each initial detail document which accompanied the initial key document.

C6.15.3.3. The FMS reply document (DI AD5) will always be used when replying to a 

mechanized NOA other than DI ADR. When replying to a DI ADR NOA key document the specifying 

consignment instructions and/or other shipment or delivery instructions will be provided to the SDDC 

releasing authority to facilitate provision of a coordinated (export) release to the shipping activity. In 

replying to mechanized NOA other than DI ADR, the following rules apply:

C6.15.3.3.1. When shipment release is to be made to the addresses identified by coded 

entries in the MAPAD, the AD5 document will contain an R in rp 60.

C6.15.3.3.2. When shipment release instructions are being mailed under separate 

cover, the AD5 document will contain an E in rp 60. The shipment release instructions that are mailed may 

be accomplished by letter, country designated forms, or other appropriate communications; however, such 

instructions must reach the shipping activity within 15 days for transactions coded with Country FMS 

Offer/Release Option Y. Otherwise, the shipment will be release automatically to the appropriate address 

contained in the MAPAD. The S/A’s implementation of these procedures will provide for such replies to 

be transmitted to the activity designated by the RI contained in rp 4-6 of the NOA documents.

C6.15.3.3.3. When a country replies to an NOA and rejects the shipment because the 

shipment unit contains materiel that will constitute a duplicate shipment, the shipping activity will 

withdraw the rejected materiel from the shipment and prepare a new NOA (AD1 and AD2 or ADR and 

AD2).
Enclosure 5

Page 11

C6.15.3.3.4. Shipments from Procurement (to be finalized).

C6.15.3.3.5. Storage or staging charges may accrue when a NOA response (or failure 

to respond) requires the items to be held for an extended period of time. Any storage costs are charged to 

the FMS case.

C6.16. RESERVED

C6.17. CONSOLIDATION AND MARKING OF FOREIGN MILITARY SALES SHIPMENTS

C6.17.1. Consolidation. The shipment planning process should recognize and assure compatibility 

of codes in requisitions and related documents when configuring shipment units. Requisitions with an N or 

E in rp 62, or 777 in rp 62-64, will not be held for consolidation, but the NOA requirements remain in 

effect. To assure compatibility of codes, rp 30-34, rp 45-50, and rp 57-61 must be considered for FMS 

nonassembly shipments; rp 55 and 56 must be considered in addition to rp 30-34, rp 45-50, and rp 57-61 

for FMS assembly shipments; and rp 30-33, rp 35, and rp 57-61 must be considered for Grant Aid.

C6.17.1.1. FMS assembly shipments may be consolidated into containers or shipment units if 

under the same U.S. Service program manager, recipient country, customer within country, delivery term 

code, in-country service, offer/release option code, FF code, FMS case, case line number, project codes (if 

applicable), and PD. The criteria for FMS nonassembly shipments are the same as for assembly shipments 

with the following exception; nonassembly shipments may be consolidated regardless of CLN.

C6.17.1.2. Grant Aid assembly and nonassembly shipments may be consolidated into 

containers or shipment units if under the same U.S. Service program manager recipient country, customer 

within country, type of assistance, project code (if applicable), and PD.

C6.17.1.3. Consolidation will also be limited by the following conditions:

C6.17.1.3.1. Physical characteristics of items should be compatible with other items in 

the same shipment unit.

C6.17.1.3.2. Explosives or other dangerous articles will not be consolidated with other 

items

C6.14.1.3.3. Aircraft, missiles, engines, and large (excess dimension) spares or 

assemblies for any item of equipment subject to special handling or construction or requiring movement as 

a single shipment unit will not be consolidated with other line items.

C6.17.1.3.4. Radioactive or magnetic materiel will not be consolidated together or 

with other materiel.

C6.17.1.3.5. When shelf-life items are included in a consolidated shipment, the 

exterior of the consolidated shipping container will be marked under the multipack requirements of MILSTD-129.

C6.17.2. Address Marking. The manner of designating ship-to and/or mark-for addresses in 

requisitions is described in subparagraph C6.3.2.3. After determining the specific coded entries and their 

use as a ship-to and/or mark-for address in a given requisition, the corresponding clear-text address for 

container markings will be obtained from the MAPAD.

C6.17.3. IRRD (DD Form 1348-1A or DD Form 1348-2) Continuation Page. All references in this 

chapter to DD Form 1348-1A and DD Form 1348-2 and its distribution will by direct association also apply 

to its continuation page as described in Chapter 5. The continuation page contains encoded information for 

the automated processing of multiple serialized items in a shipment.
Enclosure 5

Page 12

C6.18. RESERVED

C6.19. DOCUMENT DISTRIBUTION

C6.19.1. Military Assistance program Grant Aid Documents

C6.19.1.1. DD Form 1348-1A. Documentation to accompany shipments will be two copies 

of the DD Form 1348-1A, Issue Release/Receipt Document. See Figure C6-1.

C6.19.1.2. DD Form 250. On direct deliveries from vendors, a copy of the DD Form 250, 

Material inspection and Receiving Report, procurement shipping and receiving document, will be 

forwarded to the SAO of the country.

C6.19.2. Foreign Military Sales Documents

C6.19.2.1. DD Form 1348-1A. Documentation to accompany shipments will be two copies 

of the IRRD. See Figure C6-1. For shipments requiring and NOA, three copies of the DD Form 1348-1A 

will accompany the NOA.

C6.20. RESERVED

C6.21. SPECIAL GRANT AID PROCEDURES

C6.21.1. When issues of excess materiel are made in support of reimbursable Grant Aid 

requisitions, the following action will be initiated:

C6.21.1.1. Change signal code to D.

C6.21.1.2. Furnish BN supply status to designated address(es).

C6.21.2. When issues of DoD DWCF stocks are made in support of reimbursable Grant Aid 

requisitions, type of Assistance (TA) Code C is currently being used. DWCF activities are billing for those 

after the fact.

C6.22. RESERVED

C6.23. CANCELLATION OF REQUISITIONS

C6.23.1. The same rules governing cancellation of requisitions for Troop Support (see chapter 2, 

paragraph C2.17.; chapter 3, paragraph C3.27.; and chapter 8) will apply to FMS and Grant Aid except for 

special procedures herein.

C6.23.2. When individual line items with a Grant Aid program RCN are to be canceled, or FMS 

cases/program are to be canceled, the canceling Agency/activity will submit single-line cancellation 

requests under the appropriate Service policy.

C6.23.3. FMS/Grant Aid single-line cancellation requests will be processed under chapter 3, 

paragraph C3.27except that:

C6.23.3.1. No tracer action will be initiated for FMS shipments to foreign purchasers that

move in commercial transportation channels to commercial FFs and are therefore not available for 

cancellation after turnover to the carrier, post office, or FF. Storage activities will furnish supply sources 

with shipment status documents (DI AU_).
Enclosure 5

Page 13

C6.23.3.2. Supply sources will advise the ILCO of contractual agreements that will result in 

cost conditions if cancellations, diversions, or holding are accomplished. The ILCO decide whether the 

cancellation, diversion, or hold actions will be suspended or continued. Decisions to continue cancellations 

or diversions will be provided the supply source by narrative message containing the notation: “Decision 

for cancellation or diversion by ILCO.”

C6.23.4. FMS/Grant Aid mass cancellation requests will be processed under chapter 8, 

except that Security Assistance Program mass cancellation requests will be submitted with the required 

codes for identification of one of the following, for which cancellation of all requisitions is requested:

C6.23.4.1. U.S. MAP Service code and - Security Cooperation Customer Code (rp 

30-32).

C6.23.4.2. U.S. MAP Service code and country/activity Security Cooperation

Customer Code (rp 30-32) and project code (rp 57-59).

C6.23.4.3. FSC or FSG when associated with U.S. MAP Service code and 

country/activity Security Cooperation Customer Code (rp 30-32).

C6.23.5. Transportation (such as the terminal costs associated with stopping, holding, and 

returning materiel to depots or storage) and procurement termination costs incident to actual 

diversion/cancellation of FMS requisitions will be charged under DoD 7000.14-R (DoD Financial 

Management Policy).

C6.23.6. Grant Aid shipments that meet the criteria for shipment diversion under mass 

cancellation conditions will be diverted to the predesignated storage sites of the canceling Service by the 

DTS. Storage sites in receipt of Grant Aid cancellation shipment(s) will report the receipt(s) to the 

applicable Service ICP/ILCO and the materiel will be accounted for as MAP suspended materiel pending 

receipt of disposition instructions. Service ILCOs will provide disposition instructions under the provisions 

of DoD 5105.38-M (Part II).

C6.23.7. Navy sponsored FMS shipments from vendor sources will be diverted to 

predesignated Navy storage sites by the DTS. FMS shipments sponsored by the other Services and Navy 

sponsored shipments from DoD/GSA storage activities will be diverted under chapter 8, paragraph C8.5.1.

C6.24. RESERVED

C6.25. RETURN OF DISCREPANT FOREIGN MILITARY SALES MATERIEL

C6.25.1. Discrepancies in FMS shipments are reported on a Supply Discrepancy Report (SDR) (via 

SF 364, Report of Discrepancy, or equivalent under DLMS), by the receiving FMS customer through the 

applicable ILCO. The required data entries and procedures for processing SDRs are provided by the DoD 

400.25, DLMS Manual, Vol II, Chapter 15. DLAI 4140.22, AR 735-11-2, SECNAVINST 4355.18A, 

AFJMAN 23-215).

C6.25.2. When it is determined that materiel reported on a SDR is to be returned to U.S. supply 

systems stocks, the U.S. supply source shall provide the SDR reply to the applicable ILCO for distribution 

to the FMS customer. The supply source, or the applicable ILCO, shall prepare the DD Form 1348-1A to 

be used to return the materiel, shall contain entries shown in AP3.50. All DLA shipments, resulting in an 

SDR due to a wrong item received, shall be returned to a CONUS DLA depot as part of the SDR process.

C6.25.3. The DTS will be used to return discrepant FMS materiel when appropriate. This can be 

accomplished in two ways.

C6.25.3.1. If a transshipment point has not been specified and the SAO has the 
Enclosure 5

Page 14

capability/capacity to perform this function, the SAO will arrange for movement through the DTS.

C6.25.3.2. If a transshipment point has been designated, the transshipment point will arrange 

for movement through the DTS.

C6.25.3.3. The transshipment point should be a U.S. activity located in the FMS country that 

submitted the SDR and/or be reasonably accessible to the FMS country.

C6.25.3.4. The transshipment point will, as a minimum, provide legible copies of the signed 

DD Form 1348-1A (evidencing receipt) to the U.S. supply source identified in rp 67-69, the appropriate CR 

listed in the MAPAD, and, if requested, to the consignor. The latter two copies may be reproductions of 

the copy furnished to the supply source.

C6.25.3.5. Coordination between the U.S. supply source and the focal point listed in DLAR 

4140.60, et al. is required prior to initial designation as transshipment point of an S/A other than that of the 

supply source.

C6.25.3.6. When the DTS is not used for return of discrepant FMS materiel, the holding FMS 

country will arrange for movement through the CR/FF to the activity designated in Block 3 of the DD Form 

1348-1A. CONUS inland shipments will be effected by the use of a collect CBL convertible to a GBL 

upon receipt. Reimbursement of transportation charges between the holding FMS country and the CR/FF 

will be requested by the CR to the U.S. supply source identified in rp 67-69 of the DD Form 1348-1A.

C6.25.3.7. Regardless of the method of transporting return-eligible discrepant FMS materiel, 

all shipments pursuant to these procedures must be completed within 180 days of the date of document 

preparation entered in Block 5 of the DD Form 1348-1A.

DOCUMENT NO. OF COPIES DISTRIBUTION

DD Form 1348-1A Three Two copies will accompany all shipments. (One copy 

must be the first carbon copy.) A minimum of one 

copy will be on the outside if not in conflict with other 

applicable directives. The original will be retained by 

the shipper unless an automated capability is available 

to prove a shipment has been made. When DD Form 

1348-1A contains bar coding, one of the two copies to 

accompany all shipments will be the original copy.

DD Form 1348-1A One Forwarded via priority mail to the activity designated in 

the MAPAD to receive the document (Type Address 

Codes 5 and 6; if blank, see Type Address Codes1 and 

2, respectively).

Figure C6.F1. Distribution of DD Form 1348-1A 

C6.26. FMS TRANSPORTATION. FMS transportation guidance may be found in the Security Assistance 

Management Manual (SAMM), DoD 5105.38M and the DTR, 4500.9-R, Part II.

C6.26.1. FMS detention and demurrage charges are located in the Security SAMM, Chapter 7.

C6.26.2. FMS document retention requirements are defined in the DTR, Appendix E, Paragraph Q.
Enclosure 6

ENCLOSURE 6

CHANGES MILSTRIP CHAPTER 7

C7. CHAPTER 7

VALIDATION OF MATERIEL OBLIGATION

Extract:

C7.2.3.4. The machine listings, when required, will be prepared in sequence by Service (rp 30), country

Security Cooperation Customer Code (rp 31-32), and document number, major or minor, and reflect 

subtotal document count by country Security Cooperation Customer Code (rp 31-32) and grand total for 

the listing. The validation requests, with listing when desired, will be sent by priority mail to the ILCO 

designated in rp 54 of the original requisition. However, supply sources may elect to forward the requests 

and listings by routine mail, in lieu of priority mail, in instances where the ILCO is geographically close to 

the supply source. Scheduled MOV validation requests will be transmitted not later than 10 days after the 

established cutoff date. Transmission will be by the DISN message system, when feasible, under the 

procedure specified in section I, paragraph C7.1.8, of this chapter.
Enclosure 7

ENCLOSURE 7

CHANGES TO MILSTRIP APPENDIX 3

AP3.3. APPENDIX 3.3

SECURITY ASSISTANCE PROGRAM 

REQUISITION

FIELD LEGEND

TYPE REQUISITION BLOCK

NUMBER(S) (MANUAL)

RECORD POSITION(S) (MECHANICAL) ENTRY AND INSTRUCTIONS

Country Security 

Cooperation Customer 

Code

31-32

(First and Second 

Position)

Enter the appropriate recipient 

country/organization for the Security 

Assistance materiel.

AP3.30. APPENDIX 3.30

FOREIGN MILITARY SALES NOTICE OF 

AVAILABILITY KEY DOCUMENT

AP3.30.1. The mechanized FMS NOA is provided to customers having a need to received mechanized data for FMS 

shipments when FMS Offer/Release Option Y of Z is entered in rp 46 of requisitions. This FMS NOA Key document will 

accompany the FMS NOA detail documents.

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Country Security 

Cooperation Customer Code

19-20 Enter. Security Cooperation Customer Code
DoD 4000.25-1-M, October 2007

Enclosure 8

ENCLOSURE 8

CHANGES TO MILSTRIP DEFINITIONS

DEFINITIONS

COUNTRY CODE. A code used to identify the country, international organization, or 

account which is (1) the recipient of materiel or services sold, leased, loaned, transferred, 

exchanged, or furnished under FMS or (2) the recipient of materiel or services furnished 

under MAP Grant Aid.

SECURITY COOPERATION CUSTOMER CODE. The Security Cooperation 

Customer Code is a two-digit code used by Defense Security Cooperation Agency to 

represent the country, international organization, region, or program authority 

associated with transactions recorded in Security Cooperation systems and associated 

with programs implemented in the Foreign Military Sales Trust Fund.