*DLM 4000.25, Volume 2, November 26, 2019*

*Change 13*

**AP7.9. APPENDIX 7.9**

**SUPPLEMENTARY ADDRESS**

AP7.9.1.  The supplementary address (SUPADD)/supplemental data field is a multi-purpose data element.  Usage rules vary for U.S. Forces and Security Assistance, by the intent of the transaction originator, as well as based upon the transaction format (legacy MILSTRIP vs. DLMS) used to communicate the information.  Regardless of usage or format, the originator’s SUPADD/supplementary data shall be perpetuated in all subsequent transactions and documentation.

AP7.9.2.  U.S. Forces

	AP7.9.2.1. Under legacy MILSTRIP, the SUPADD (located in rp 45-50) in transactions for support of U.S. Forces, when significant, will contain a DoD activity address code (DoDAAC).  The entry in the first position (Service) or first and second position (Federal Agency, if numeric-numeric, or special program activity, if numeric-alpha) shall always be the appropriate character(s) identifying the Service/Agency (S/A) or program (see Appendix 7.2. Service and Agency Codes).  The DoDAAC shall be established in the authoritative DLA Transaction Services DoD Activity Address Directory (DoDAAD) database by S/A designated DoDAAD Central Service Points for dissemination in a variety of formats.  Each code so established will contain address(es) in detail to permit the shipping and billing of materiel.  (See the DLM 4000.25, Volume 6, Chapter 2, DoD Activity Address Directory (DoDAAD).)

	AP7.9.2.2.  Under DLMS, the SUPADD shall be replaced by a generic supplemental data field.  DoDAACs provided for the purpose of identifying a ship-to and/or bill-to activity are carried as discrete data elements in the DLMS transaction address segment with specific data qualifiers indicating the exact purpose.  

		AP7.9.2.2.1.  In a mixed legacy/DLMS environment, the supplemental data field is used to perpetuate/populate the legacy MILSTRIP SUPADD.  During this time, field size for the supplemental data field is restricted to 6 positions.  When containing a DoDAAC, the value carried in the supplemental data field must also be repeated in the applicable DLMS address segment to identify the ship-to/bill-to activity.

		AP7.9.2.2.2.  Under full DLMS, the requirement to pass activity address information within the supplement data shall be terminated and the supplementary data field will be used for miscellaneous data only.  Under full DLMS, the field length shall be expanded to 30 positions. 

	AP7.9.2.3.  Non-significant Supplemental Data.  The Service/Agency Code Y in the first position shall be used to denote that the field is being used for data rather than a ship-to/bill-to DoDAAC.  When the originator of the transaction uses the SUPADD/supplemental data field for data rather than addressing, the entry shall be considered non-significant to the receiving activity except by coordinated prior agreement or authorized procedures for inter-Service ownership transfer of ammunition/ammunition-related materiel.

	AP7.9.2.4.  Inter-Service Ownership Transfer of Ammunition/Ammunition-related Materiel

		AP7.9.2.4.1  When used for inter-Service ownership transfer of ammunition or ammunition-related materiel located in a Single Manager for Conventional Ammunition (SMCA) storage activity where no physical movement of materiel or billing applies, the Referral Order (DLMS 511R/DIC A4_) shall cite Signal Code M and Project Code CYK in conjunction with a SUPADD/supplemental data field beginning with Service/Agency Code Y (a ship-to DoDAAC is not applicable).  In a mixed DLMS/legacy environment, the required additional data content to support this process will be concatenated in the SUPADD/supplemental data field as follows:

· First position:  Service/Agency Code Y

· Second position:  Old (from) ownership code

· Third-fifth position:  New owner RIC

· Last position:  New/gaining (to) ownership code

		AP7.9.2.4.2  Materiel release orders (MROs) (DLMS 940R/DIC A5_) directed to an SMCA storage activity for inter-Service transfer of ammunition or ammunition-related materiel with no physical movement or billing will cite the SUPADD/supplemental data constructed as in AP7.9.4.1  in combination with Signal Code M.  All subsequent transactions will perpetuate this construct.

		AP7.9.2.4.3  Under DLMS, the originating system will also provide the discrete data elements where applicable, mirroring those contained in the supplemental data.  This redundancy will be retained until all parties are using DLMS and the supplemental data field may be repurposed for unrelated information.

	AP7.9.2.5.  When the first position of the document number contains a valid S/A alpha designator and the first position of the SUPADD/data field contains a zero (0), DAAS shall change the zero (0) to Y.

AP7.9.3.  Security Assistance

	AP7.9.3.1.  For Security Assistance transactions, the legacy MILSTRIP SUPADD, as well as the mixed environment DLMS supplemental data field, is used for a concatenation of  multiple distinct data elements.

		AP7.9.3.1.1.  For Foreign Military Sales (FMS), the first position (legacy format rp 45) shall contain the in-country Service designating the military service within the Security Assistance customer country.  For Grant Aid, the first position shall contain Service/Agency Code Y.  Note that the Y is subsequently converted to an X for establishment of the applicable Military Assistance Program Address Code (MAPAC).

		AP7.9.3.1.2.  The contents of the remaining positions vary for both FMS and Grant Aid, according to the Security Assistance country and the originator’s intent.  (See  Chapter 25 and Appendix 8.3 or DLM 4000.25, Volume 6, Chapter 3, Military Assistance Program Address Directory (MAPAD), for detailed guidance.)

	AP7.9.3.2.  In a mixed legacy/DLMS environment, the supplemental data field shall be interpreted during DLA Transaction Services’ DAAS processing and separated into its discrete data elements for transmission to DLMS-compliant applications.  Under full DLMS, the originating system shall provide the discrete data elements applicable to the transaction including:  customer within country code, offer and release option code, FMS case number, program line number, record control number.

AP7.9-1

APPENDIX 7.9