Attachment ADC 424 

 Page 1 

ADC 424

DOD Activity Address Directory (DoDAAD) Modification to Break Bulk Point (BBP) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

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

b. Originator: DLA Logistics Management Standards 

2. FUNCTIONAL AREAS: DOD Activity Address Directory (DoDAAD) and Supply 

3. REFERENCE: 

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

Logistics Systems Interoperability Support Services), Chapter 2 - Department of 

Defense Activity Address Directory 

4. REQUESTED CHANGE:

a. Description of Change: This change approves interim and longer term procedures 

to correct inconsistent Break Bulk Points (BBPs) for TAC1 and TAC2 addresses. 

b. Background:

1) There are two BBP fields on the DoDAAD update page. One is associated 

with the TAC 1 and another associated with the TAC 2. 

2) The inconsistent loading of these fields has led to confusion in the user 

community. It is possible to have the BBP in TAC 1 and 2 be different. 

3) The CSPs manually enter the BBP in the appropriate TAC (1 or 2) to be used 

for shipping. 

4) Army and Air Force only have one BBP field, so BBP sent in from Army or 

Air Force is always applied based on the active TAC. If there is an active 

TAC 2, the incoming BBP field is stored in the TAC 2 BBP field of the 

DoDAAD. If TAC 2 is not active or no TAC 2 exists, the BBP is stored in the 

TAC 1 BBP field. 

5) Only the TAC 1 BBP field is used in the data replication process that provide 

DODAAD changes from the authoritative DLA Transaction Services 

(formally DAASC) DoDAAD database to external systems. If TAC 2 is 

active in the DoDAAD, that value is placed in the TAC 1 replicated data field. 

If TAC 2 is not active or no TAC 2 exists, the TAC 1 BBP field of the 

DoDAAD is stored in the TAC 1 BBP field of the replicated data. 

6) Batch transaction distribution of DoDAAD changes to external systems is 

handled differently. The TAC 1 or TAC 2 BBP field associated with the 

changed TAC is always used in batch. If the DoDAAC TAC 1 is changed, 

only the TAC 1 BBP field is used and only the TAC 1 transaction is created 

for the batch processing. If the DoDAAC TAC 2 is active, the TAC 2 BBP 

field is used and the TAC 2 transaction is generated for batch processing. 
Attachment ADC 424 

Page 2 

Please note the TAC designation is part of the batch processing. Each batch 

transaction indicates if it is a TAC 1, 2 or 3 within the TA_ record. 

c. Procedures: The following procedures are approved:

1) Phase 1 – Changes to update processing: 

o Change the DoDAAD update screen to use one BBP field. Move the BBP 

input field into the “transportation” section of the update screen. Apply 

the value entered in the BBP field to either the TAC 1 or TAC 2 BBP 

fields. If a TAC 2 is active, the TAC 2 would contain the BBP. If the 

TAC 2 is inactive or nonexistent, the TAC 1 BBP field would be used. 

o If the TAC 2 is deleted, the BBP field will be cleared. The CSP will be 

prompted to enter a new BBP, if the TAC 1 is now to be used as a SHIPTO address. 

2) Phase 2 Cleanup – DLA Transactions Services will provide a report of BBP 

differences between TAC 1 and TAC 2 records, if both BBP fields contain 

values. This information will be sent to the CSPs and DLA Logistics 

Management Standards for review. CSPs will respond back to DLA 

Transactions Services and DLA Logistics Management Standards within 30 

days with verification that the correct BBP has been entered. 

3) Phase 3 – Drop the TAC 2 BBP field from the replicated data and the 

download files used in eDAASINQ. 

4) Phase 4 – Drop the TAC 2 BBP field from the DoDAAD database. Until 

batch transmission is discontinued, batch processing will be modified to insert 

the TAC 1 BBP into the TAC 2 BBP batch record when creating “TA_” 

records for TAC 2 inserts and updates. STAFFING NOTE: Alternative update 

logic would be to add the same BBP value to both TAC 1 and TAC 2 BBP. 

This is not good choice for a couple of reasons. First, the goal is to eventually 

have only one BBP per DoDAAC. Second, there is logic in place to validate 

the BBP. An OCONUS BBP is invalid for a CONUS address. It is possible to 

have a TAC 1 address in CONUS and a TAC 2 address which is OCONUS. 

Thus this alternative will not work in this case. 

5. REASON FOR CHANGE:

a. There should only be one BBP value per DoDAAC. Having two BBP fields in the 

database, sometimes with different values, has led to confusion in the user 

community. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: This change will eliminate confusion about which BBP field is the 

correct BBP field. 

b. Disadvantages: None noted. 

7. IMPACT: 

a. Implementation: DLA Transaction Service will implement the change as soon as 

possible.

b. Publication: No publication changes required. 
Attachment ADC 424 

Page 3 

c. DLMS Data. There are no new data elements associated with this proposal 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None noted.