ADC 406 

 

ADC 406 

DOD Activity Address Directory (DoDAAD) Removal of Unused Fields 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

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

b. Originator Robert Hammond, DLA J627, DoDAAD Process Review 

Committee Chair, e-mail Robert.hammond@dla.mil

2. FUNCTIONAL AREA: DoDAAD and Supply 

3. REFERENCE: 

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

Volume 6 (DoD Logistics Systems Interoperability Support Services), 

Chapter 2 - Department of Defense Activity Address Directory 

4. REQUESTED CHANGE:

a. Description of Change: The DoDAAD database contains some unused 

fields, which leads to confusion in the user community. This Change corrects 

the problem by removing the unused fields.

1) Changes from PDC are highlighted in yellow. The Delete Indictor 

field has been removed in the ADC because it was determined during 

staffing that the Delete Indictor is used and supported by DLA 

Transaction Services. The “Distribution” field is not currently used, 

but its potential use is under review, so it will not be deleted.

b. Background:

1) What fields are to be removed and why: 

a. “Longitude and Latitude” have never been populated and opens the 

DoDAAD up to a classification level that is contrary to its purpose. 

It was determined these fields should be removed. 

b. “RIC” was added to the DoDAAD database during reengineering 

for a single Routing Identification Code (RIC) to DoDAAC 

association, however, this feature could not be implemented due to 

the one to many relationship of RICs to a DoDAAC. Note that 

dropping the RIC field will not affect the ability to view the RICs 

associated with a DoDAAC. All RICs associated with a DoDAAC 

are displayed within DAASINQ and eDAASINQ and are 

contained in DoDAAC downloads. The data replication also 

provides all RICs associated with a DODAAC when the customer 

requests it. 

c. “Geo Location” was used only by one Service and never 
ADC 406

 

maintained after the initial partial load of the DoDAACs. 

a. “Delete Indicator” It was determined during staffing the 

Delete Indictor is being used, so it will not be deleted. 

b. “Distribution Code” Distribution Code is not used, but its 

potential use is under review. Staffing Note: this is not the 

same as DIST_CD code, which is used for internal 

processing within DAAS, and it will also not be deleted. See 

enclosure 1. 

2) Removing the fields will eliminate confusion and will obviate the need 

to explain why unused fields exist in the DoDAAD database. 

3) For information, the link to DoDAAD Master Layout is at 

http://www.dla.mil/j-6/dlmso/eLibrary/Documents/DoDAAD/GSADoDAAD-File-Layout.docx.

c. Procedures: The following change are to be made:

1) Remove the GEO Location, Longitude and Latitude fields from the 

DoDAAD update page.

2) Remove GEO Location from the eDAASINQ Transportation tab.

3) Remove the following fields from replication data processing. 

(GEO_LOC, LONG, LATIT, RIC, and DISTRIBUTION) from 

replication data processing. This will require coordination of the 

replication partners to resynchronize the replicated data. 

4) Update the DoDAAD master file layout on the DLA Logistics 

Management Standards website to drop (GEO_LOC, LONG, LATIT, 

and RIC, and DISTRIBUTION) from the DoDAAD layout. 

5) Because of the programming ramifications, the fields (GEO_LOC, 

LONG, LATIT, RIC) will only be removed from disseminating files 

(queries, downloads, replication), but will not be removed from the 

DoDAAD database at DLA Transaction Services. DLA Transaction 

Services will: 

o Coordinate with Components regarding changes to queries, 

download and replication to avoid disruption. 

o Add note to eDAASINQ download page to warn users the 

download files will be changed. The note will contain an 

implementation date of six month in the future to give Components 

time to update their processes. 

5. REASON FOR CHANGE: These fields are no longer used and their existence 

creates confusion and requires recurring explanation to our ever-changing user 

community. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Only fields with valid data will exist in the DoDAAD database. 

b. Disadvantages: None noted. 

7. IMPACT: 
ADC 406

 

a. Implementation: DLA Transaction Service will implement the change to the 

DoDAAD database as soon as possible.

b. Publication: No publication changes required. 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None noted.
 ADC 406 

 

Enclosure 

DIST_CD Field Description

The DIST_CD field is for INTERNAL DLA TRANSACTION SERVICES USE ONLY. 

It was created as a "flag" field which DLA Transaction Services might use for any 

purpose to indicate to the DMARS routing program to initiate some required action. The 

only current use is if there is a "3" present, the program will make a copy of transactions 

being routed to that DoDAAC and send it the DLA Transaction Services "special cross 

reference" for that DoDAAC. The "special cross reference" is a numerical value that 

represents a COMM RI that identifies a profile identifying a specific electronic interface. 

The DIST_CD and "special cross reference" are manually updated by DLA Transaction 

Services. This fields is utilized to satisfy a customer request to temporarily receive 

copies of transactions for a DoDAAC. It can be turned on/off through manual file 

maintenance action.