1 

ADC 377 

Attachment 

 

ADC 377 

Transaction Copies Required for DLA Support of Navy BRAC SS&D/IMSP 

DLRs, Navy Program-Managed Materiel, and Nuclear Consumable Support Materiel 

1. ORIGINATOR: Defense Logistics Agency, DLA J-331, 703-325-1924 (DSN 427)

2. FUNCTIONAL AREA: Primary: Supply/ Logistics.

3. REFERENCES: 

a. Functional Requirements for DLA’s implementation of Base Realignment and Closure 

(BRAC) Retail Supply, Storage And Distribution (SS&D)/Inventory Management and Stock 

Positioning (IMSP) Spiral 2 

b. Proposed DLMS Supplements on the DLMSO internet site eLibrary under DLMS 

Supplements to Federal Implementation Conventions - Transaction Sets, available at: 

http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp. 

c. AT&L Memorandum transmitted April 21, 2010, subject: Proposed Changes in support of 

Navy BRAC Inventory Management and Stock Positioning (IMSP) Spiral II. This memorandum 

documents ADUSD(L&RM)SCI direction provided to DLA and Navy authorizing immediate 

implementation of this DLMS change. 

4. REQUESTED CHANGE: Revisions subsequent to staffing are highlighted in yellow.

a. Description of Change: This change establishes procedures to provide visibility to DLA 

of the Navy Shipyards (NSY) and Fleet Readiness Centers (FRCs)-prepared requisitions for DLR, 

Navy program-managed materiel, and nuclear consumable support materiel requisitions, and 

subsequent transactions, in support of the Navy-DLA BRAC 2005 SS&D concept of operations 

(CONOPS). This change establishes a requirement for the Defense Automatic Addressing System 

(DAAS) to provide a copy of requisition (including modification, cancellation, and follow-ups), 

supply status, and receipt acknowledgement transactions to DLA based upon transaction content and 

prescribed business rules. Comment resolution/concurrence is provided at Enclosure 2. 

b. Background: As a result of the 2005 BRAC decision, retail supply, storage, and 

distribution functions and associated infrastructure supporting the Navy industrial/maintenance sites 

will transfer to DLA. The Navy sites consist of 2 NSYs and 3 FRCs. The intent of the directive is to 

significantly improve combat effectiveness while reducing costs by developing a world-class, costeffective supply chain focused on readiness; taking every opportunity to eliminate waste, reduce 

touches, reduce cost, and improve readiness. In accordance with the signed CONOPS, DLA has 

agreed to provide SS&D/IMSP support to the FRC and NSY sites, including DLR, Navy programmanaged materiel, and nuclear consumable support materiel requisitioned by the Navy industrial 

activity (IA) directly from a Source of Supply (SoS) other than DLA. Although DLA will not fill 

requisitions for these categories of materiel, DLA will be responsible for performing Materiel 

Obligation Validation (MOV) and some follow-up actions with SoS on behalf of the Navy. In order to 

do so, DLA must receive a copy of the requisition (including modification, cancellation, and follow-
 ADC 377 

Attachment 

2

ups) and subsequent supply status and materiel receipt acknowledgment (MRA) transactions. 

c. Detailed Procedures 

(1) General 

(a) DAAS will prepare a copy of the applicable transaction and forward to DLA 

under the following circumstances: 

1. Navy requisitions, requisition modifications, follow-ups, and cancellations 

when the originating Navy IA identifies DLA as the intended recipient of a copy of the transaction. 

2. Navy DLR, Navy program-managed materiel, and nuclear consumable 

support materiel supply status transactions, which are recognized by a Cognizance Symbol (COG) 

where the first character is equal to 0, 2, 4, 6, 7, 8, and the status recipient DoDAAC is one of the 

identified Navy IA sites. Note: This is a temporary requirement intended to ensure that copies are 

provided for requisitions created prior to “Day Two.” Day Two of BRAC implementation involves the 

transfer of ownership of certain inventories from the Navy to DLA and the roll-out of applicable 

information technology functions.

3. Navy DLR, Navy program-managed materiel, and nuclear consumable 

support materiel supply status transactions reflecting the DLA Distribution Code 51. Note: This will 

ensure that copies are provided to DLA for requisitions generated after Day 2. 

4. Navy MRAs when the originating Navy IA identifies DLA as the 

intended recipient of the MRA report. 

(b) The Navy COG is a two-digit numeric-alpha code found in MILS-formatted 

transactions in record positions 55-56 as the last two positions of the Distribution Code field, or in 

DLMS-formatted transactions in the LQ segment using Qualifier COG. The COG identifies a stocknumbered item with the Integrated Materiel Manager (IMM) and indicates whether the material is 

managed in the Navy wholesale or retail accounting system. 

(c) Navy FRC and NSY IA sites applicable to this proposal are: 

 FRC EAST Cherry Point N65923 

 FRC SE, Jacksonville N65886 

 FRC SW San Diego N65888 

 PHNSY & IMF Pearl Harbor N32253 

 PNSY Portsmouth NH N39040 

 NNSY Norfolk N42158 

 PSNS & IMF Puget Sound N4523A 

(2) Requisition Detailed Procedures 

1. Navy IA will submit a 511R (A3_) requisition for a DLR, Navy programmanaged materiel, and nuclear consumable support materiel to the appropriate SoS. The requisition 

 

1

 Refer to ADC 369, Alternative Procedures for Material Obligation Validation (MOV) under Navy BRAC SS&D/IMSP 

(staffed as PDC 386), for establishment of DLA Distribution Code 5. 
 ADC 377 

Attachment 

3

originating system will include the DLA Distribution Code 5, and identify DLA as the party to receive 

a copy in the DLMS requisition format. DAAS (using the 511R party to receive copy as a trigger) 

will prepare an image copy of the transaction and forward to DLA (RIC SMS). DAAS will indicate 

that the 511R transaction is an image copy using a qualifier in the beginning segment (BR06=FI) to 

allow immediate recognition that the transaction is not an actionable requisition for DLA. This is also 

necessary for the 511M, and 869F where the modification or follow-up may act as an original 

requisition if unmated to a prior requisition record. DLA Enterprise Business System (EBS) will 

establish edits identifying the requisition as an image copy versus a live order, based on the image 

qualifier. EBS will establish a “read-only sales order record” in EBS for the Navy IA requisition, 

taking no financial action or logistics action to fill/refer/reject the requisition. The sales order record 

will be used as the basis for follow-up actions with the SoS and when DLA performs MOV with the 

SoS in support of the Navy IA sites.2

 

2. This requisition requirement is applicable to the following transactions: 

 511R, Requisition (A3_) 

 511M, Requisition Modification (AM_) 

 869A, Requisition Inquiry (AF_) 

 869F, Requisition Follow-up (AT_) 

 869C, Requisition Cancellation (AC_) 

(3) Supply Status Detailed Procedures: 

1. Temporary Requirement based on COG. When the DLR, navy 

program-managed materiel, or nuclear consumable support materiel SoS provides supply status using 

DLMS 870S or MILS AE_ for one of the above requisitions (identified by COG identified in 

paragraph 4.c.(1)(a)2 above) to the Navy IA (identified by the DoDAACs listed in paragraph 4.c.(1)(c) 

above), DAAS will prepare an additional status transaction and forward to DLA. The DLA 

(DoDAAC=SL4701) will be identified as a status recipient. 

2. Standard Requirement based upon Distribution Code. When the DLR, 

Navy program-managed materiel, or nuclear consumable support materiel SoS provides supply status 

using DLMS 870S or MILS AE_ for one of the above requisitions, the SoS will perpetuate the 

Distribution Code 5 to the supply status under MILSTRIP rules. DAAS will prepare the status 

transaction and forward to DLA. DLA (DoDAAC=SL4701) will be identified as a status recipient. 

3. DLA will update the status of the original read-only sales order record. If 

supply status unmatched to a sales order record within EBS, the supply status will be suspended for 

manual review. Staffing Note: To preclude a high initial volume of unmatched status transactions, IA 

site requisition history (for requisitions initiated prior to Day Two) may be made available to DLA. 

4. Using UMMIPS standards, DLA will follow-up with other SoS on behalf of 

the Navy. This follow-up will occur when BB status (requisition is back-ordered against due in stock) 

 

2

 ADC 369 (PDC 386) establishes procedures for DLA support of MOV functions including DAAS re-routing of MOV 

transactions to DLA. 
 ADC 377 

Attachment 

4

has been provided and the estimated shipment date has elapsed, but no updated supply status has been 

received. DLA will also follow-up to the SoS when no supply status is received subsequent to the 

requisition. 

(4) MRA Detailed Procedures: When the Navy IA sends MRA using DLMS 527R 

(DR_), to the DLR, Navy program-managed materiel, and nuclear consumable support materiel SoS 

for the receipt acknowledgement, the originating system will identify DLA as an additional party to 

receive reports. DAAS (using the 527R party to receive reports as a trigger) will prepare a copy of the 

MRA and forward to DLA. Upon receipt of the MRA, DLA will update the status of the read-only 

sales order record, closing the order so that it is no longer considered for follow-up actions. If 

unmatched to a record, the MRA will be suspended for manual review. Staffing Note: As above, in 

order to preclude a high initial volume of unmatched MRA transactions, IA site requisition history (for 

requisitions initiated prior to Day Two) may be made available to DLA. 

(5) DLMS Supplements. Revise as shown in the Enclosure 1. 

d. Alternatives: None identified. 

5. REASON FOR CHANGE: As a result of BRAC 2005 SS&D, DLA has assumed additional 

functions described above for Navy BRAC IA sites. The Navy no longer has support personnel or full 

systems capability to continue to perform MOV and follow-up actions. In order to accomplish these 

functions on behalf of the Navy, DLA EBS requires a copy of the applicable requisition, supply status, 

and MRA transactions applicable to Navy IA. Adding the DAAS business rules for generation of 

copies and updating the DLMS Supplements supports this capability. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: EBS, NSYs, and FRCs will be able to comply with required functionality 

using DLMS standards for the BRAC IMSP Spiral 2 process.

b. Disadvantages: None identified.

7. IMPACT: 

a. DAASC: 

(1) DAASC must respond to the inclusion of the applicable qualifiers in requisitionrelated transactions and the MRA to trigger a copy of the transaction to DLA. 

(2) DAASC must react to specified logic based upon COG and DoDAAC to trigger 

of an additional supply status transaction to DLA, as well as the new DLA Distribution Code 5. 

b. DLMS Data: There are no new DLMS data elements associated with this change. This 

change expands usage of DLMS functionality and data. 

c. Materiel Receipt Acknowledgement (MRA) Follow-up (DLMS 527R/DI Code DRF) 

Concern. This ADC does not provide a copy of the MRA Follow-up (DRF) transaction to DLA for 

DLRs, Navy program-managed materiel, and nuclear consumable support materiel. Since the Navy 

cannot process these DRF, DLMSO has identified this as a gap for further review. A process (manual 

or automated) should be in place to recognize and respond to MRA Follow-ups. If a DAAS 
 ADC 377 

Attachment 

5

intervention is required for the 527R/DRF, a DLMS change addendum will be published. 

d. DLMS Procedures: DLMS manual procedures will be provided separately. 

e. Planned Implementation: Testing may begin June 2010. The first site goes live January 

2011, the EBS functionality will be put in production December 2010.
 ADC 377 

Enclosure 1 

1

Enclosure 1, DLMS Supplements 

Revise as shown in the tables below: 

# Location DS 511R Requisition 

Revision Reason 

1 DLMS 

Introductory 

Notes 

Added ADC 377 to DLMS Introductory note 5:

- ADC 377, Transaction Copies Required for DLA Support of 

Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed 

Materiel, and Nuclear Consumable Support Materiel 

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2 1/BR06/20 Revise DLMS notes for existing qualifier “FI” as follows: 

FI File 

DLMS Note: 

1. Use with BRO2 Code AO or BN to identify a requisition 

image transaction where the original transaction has bypassed 

the normal DAAS transaction flow. All transaction set recipients 

must use extreme caution to ensure that individual transactions 

do not process as action documents which affect accountable 

records. 

2. Used where the original transaction has bypassed the 

normal DAAS transaction flow (e.g. CHA/CH1 transactions). 

Refer to ADC 86. 

3. Used on image transactions provided to DLA for Navy 

requisitions submitted directly to other Component SoS, so that 

DLA will be able to support follow-on actions on behalf of the 

Navy industrial activity (IA) under a DLA industrial activity 

support agreement. Refer to ADC 377. 

 

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands and clarifies 

existing usage for image 

transactions. 

3 2/N101/180 Revise DLMS notes for existing qualifier “PK” as follows:

PK Party to Receive Copy 

DLMS Note: 

1. Use as needed to identify an organization to be provided a 

copy of this transaction. Use with N103, qualifier M4 (Routing 

Identifier) and N106, qualifier To (Message To). 

2. Must be used between Army and DLA for their integrated set 

assembly program, when an assembly component part being 

ordered by the Army is not managed by DLA, and DLA is 

acquiring it in support of the Army medical mission. Refer to 

ADC 276.

3. Used between Navy and DLA for Navy requisitions 

submitted directly to other Component SoS, so that DLA will 

be able to support follow-on actions on behalf of the Navy 

industrial activity (IA) under a DLA industrial activity support 

agreement. Refer to ADC 377.

4. DLMS enhancement; see introductory DLMS Note 3a. 

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands existing usage for 

Party to Receive Copy. 
 ADC 377 

Enclosure 1 

2

# Location DS 511M Requisition Modification 

Revision Reason 

1 DLMS 

Introductory 

Notes 

Added ADC 377 to DLMS Introductory note 5:

- ADC 377, Transaction Copies Required for DLA Support of 

Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed 

Materiel, and Nuclear Consumable Support Materiel 

Identifies DLMS Changes 

included in the DLMS 

Supplement. 

2 1/BR06/20 Add new qualifier “FI” as follows: 

FI File 

DLMS Note: 

1. Use with BRO2 Code AM to identify a requisition 

modification image transaction. All transaction set recipients 

must use extreme caution to ensure that individual 

transactions do not process as action documents which affect 

accountable records. 

2. Used on image transactions provided to DLA for Navy 

requisitions submitted directly to other Component SoS, so that 

DLA will be able to support follow-on actions on behalf of the 

Navy industrial activity (IA) under a DLA industrial activity 

support agreement. Refer to ADC 377. 

 

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands usage for image 

transactions to the 511M. 

3 2/N101/180 Revise DLMS notes for existing qualifier “PK” as follows:

PK Party to Receive Copy 

DLMS Note: 

1. Use as needed to identify an organization to be provided a 

copy of this transaction. Use with N103, qualifier M4 (Routing 

Identifier) and N106, qualifier To (Message To). 

2. Must be used between Army and DLA for their integrated set 

assembly program, when an assembly component part being 

ordered by the Army is not managed by DLA, and DLA is 

acquiring it in support of the Army medical mission. Refer to 

ADC 276.

3. Used between Navy and DLA for Navy requisitions 

submitted directly to other Component SoS, so that DLA will 

be able to support follow-on actions on behalf of the Navy 

industrial activity (IA) under a DLA industrial activity support 

agreement. Refer to ADC 377.

4. DLMS enhancement; see introductory DLMS Note 3a. 

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands existing usage for 

Party to Receive Copy. 

# Location DS 869A Requisition Inquiry 

Revision Reason 

1 DLMS 

Introductory 

Notes 

Added ADC 377 to DLMS Introductory note 3:

- ADC 377, Transaction Copies Required for DLA Support of 

Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed 

Materiel, and Nuclear Consumable Support Materiel

Identifies DLMS Changes 

included in the DLMS 

Supplement. 
 ADC 377 

Enclosure 1 

3

# Location DS 869A Requisition Inquiry 

Revision Reason 

2 2/N101/110 Revise to add qualifier and note:

PK Party to Receive Copy 

DLMS Note: Used between Navy and DLA for Navy 

requisitions submitted directly to other Component SoS, so that 

DLA will be able to support follow-on actions on behalf of the 

Navy industrial activity (IA) under a DLA industrial activity 

support agreement. Refer to ADC 377.

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands existing usage for 

Party to Receive Copy. 

# Location DS 869C Requisition Cancellation 

Revision Reason 

1 DLMS 

Introductory 

Notes 

Added ADC 377 to DLMS Introductory note 3:

- ADC 377, Transaction Copies Required for DLA Support of 

Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed 

Materiel, and Nuclear Consumable Support Materiel

Identifies DLMS Changes 

included in the DLMS 

Supplement. 

2 2/N101/110 Revise to add qualifier and note:

PK Party to Receive Copy 

DLMS Note: Used between Navy and DLA for Navy 

requisitions submitted directly to other Component SoS, so that 

DLA will be able to support follow-on actions on behalf of the 

Navy industrial activity (IA) under a DLA industrial activity 

support agreement. Refer to ADC 377.

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands existing usage for 

Party to Receive Copy. 

# Location DS 869F Requisition Follow-up 

Revision Reason 

1 DLMS 

Introductory 

Notes 

Added ADC 377 to DLMS Introductory note 5:

- ADC 377, Transaction Copies Required for DLA Support of 

Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed 

Materiel, and Nuclear Consumable Support Materiel

Identifies DLMS Changes 

included in the DLMS 

Supplement. 
 ADC 377 

Enclosure 1 

4

# Location DS 869F Requisition Follow-up 

Revision Reason 

2 1/BSI09/20 Open BSI09, Action Code, and add qualifier “FI” as follows: 

FI File 

DLMS Note: 

1. Use with BSI08 Code IN to identify a requisition follow-up 

image transaction. All transaction set recipients must use 

extreme caution to ensure that individual transactions do not 

process as action documents which affect accountable records. 

2. Used on image transactions provided to DLA for Navy 

requisitions submitted directly to other Component SoS, so that 

DLA will be able to support follow-on actions on behalf of the 

Navy industrial activity (IA) under a DLA industrial activity 

support agreement. Refer to ADC 377. 

 

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands usage for image 

transactions to the 869F. 

3 2/N101/110 Revise DLMS notes for existing qualifier “PK” as follows:

PK Party to Receive Copy 

DLMS Note: 

1. Use as needed to identify an organization to be provided a 

copy of this transaction. Use with N103, qualifier M4 (Routing 

Identifier); and, N106, qualifier To (Message To). 

2. Must be used between Army and DLA for their integrated set 

assembly program, when an assembly component part being 

ordered by the Army is not managed by DLA, and DLA is 

acquiring it in support of the Army medical mission. Refer 

ADC 276. 

3. Used between Navy and DLA for Navy requisitions 

submitted directly to other Component SoS, so that DLA will 

be able to support follow-on actions on behalf of the Navy 

industrial activity (IA) under a DLA industrial activity support 

agreement. Refer to ADC 377.

4. DLMS enhancement; see introductory DLMS Note 4a. 

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands existing usage for 

Party to Receive Copy. 

DS 870S Supply Status No revisions to the DS are required. 

# Location DS 527R MRA 

Revision Reason 

1 DLMS 

Introductory 

Notes 

Added ADC 377 to DLMS Introductory note 5:

- ADC 377, Transaction Copies Required for DLA Support of 

Navy BRAC SS&D/IMSP DLRs, Navy Program-Managed 

Materiel, and Nuclear Consumable Support Materiel

Identifies DLMS Changes 

included in the DLMS 

Supplement. 
 ADC 377 

Enclosure 1 

5

# Location DS 527R MRA 

Revision Reason 

2 2/N101/210 Add new DLMS note 3 for existing qualifier “ZD” as follows:

ZD Party to Receive Reports 

DLMS Note: 

1. Use in MRA transactions to cite additional organizations 

requiring MRA. 

2. Use in Navy Commercial Asset Visibility (CAV) receipts to 

identify the party to receive report. CAV expresses party to 

receive report as a DODAAC (N903 code 10). CAV use is an 

authorized DLMS migration enhancement. See DLMS 

introductory note 5g. 

3. Used between Navy and DLA for Navy MRAs submitted 

directly to other Component SoS, so that DLA will be able to 

support follow-on actions on behalf of the Navy under a DLA 

industrial activity support agreement.. Refer to ADC 377.

Supports functionality for 

DAAS generation of a copy 

transaction required under 

IMSP. 

Expands existing usage for 

Party to Receive Reports. 
 

 1 

ADC 377 

Enclosure 2 

Enclosure 2, DLMS Change Concurrence/Comment Resolution 

 Submitter Response Response 

1. DLA Concur 

Question: 

869 Transaction: IC shows the N101=PK for the 

869A, 869C and the 869F transactions to provide 

EBS a copy of a Navy transaction submitted 

directly to Navy ERP so EBS can support follow 

on actions. However, IC only shows the 

additional action code (BSI09=FI) in the 

869F/AT_(Follow Up) transaction to also indicate 

image transactions. Should this be in all 3 869s 

(see DLMS note below)? 

DLMS Note: 

1. Use with BSI08 Code IN to identify a 

requisition follow-up image transaction. All 

transaction set recipients must use extreme 

caution to ensure that individual transactions do 

not process as action documents which affect 

accountable records. 

2. Used on image transactions provided to DLA 

for Navy requisitions submitted directly to other 

Component SoS, so that DLA will be able to 

support follow-on actions on behalf of the Navy 

industrial activity (IA) under BRAC IMSP. Refer 

to PDC 404. 

Response to question: 

The 869F/AT_ (Follow Up) needs the image 

indicator to ensure that it is not treated like a 

live requisition (if unmatched to EBS 

database). The 869A and 869C do not need 

the image indicator because they cannot be 

used to create a live requisition if unmatched. 

The 869A and 869C are supposed to match 

to a previously established requisition image 

in EBS, but if they are unmatched, EBS 

could highlight for manual attention; 

however there is no need to systemically 

recognize an image copy vs. a production 

order as there is for 511R, 511M, and 869F. 

No additional data elements needed. 

2. Navy Concur 

3. Army Concur 

4. Air Force Concur 

5. ADUSD(L&MR)

SCI 

See Reference 3.c. 

6. DAASC It is not clear to me here how the copy of the 870S 

supply status is going to be made for DLA by 

DAASC. Is it a function of how the original 

demand transaction is filled out or do you need a 

DMARS business rule? Some sections sounds like 

you would do that in DMARS business rule to 

look for the appropriate COG and DoDAAC and 

generate a copy to EBS but then it indicates that a 

Z1 qualifier would be used which indicates that 

1. Originally (under PDC 404) we were 

expecting DAAS to intercept status based 

upon COG and DoDAAC. However, under 

PDC 385, DLA agreed to create a new 

Distribution Code associated with DLA, so 

existing MILSTRIP distribution rules will 

support the status copies to DLA (although 

this will not satisfy requirements for MOV 

due to conflict with media and status code 
 ADC 377 

Enclosure 2 

2

the EBS DoDAAC might actually be designated 

as a status addressee in the transaction. If that 

were the case then you wouldn't need to do 

anything out of the ordinary to send status to EBS. 

... can you clarify how this is suppose to work ? 

2. Why it is necessary in 511R, 511M, 869F to 

use the "FI" Qualifier in the beginning segment. 

In the earlier use of N1*PK to send a copy to EBS 

for TEWLS they said they did not require that and 

would just key on the qualifier to know that it was 

an image and not the original. Why are we 

changing this now? 

requirements (Refer to ADC 369 for PDC 

385). 

The Navy has agreed to use the new 

Distribution Code 5 for the Navy DLRs, 

Navy Program-Managed Materiel, and 

Nuclear Consumable Support Materiel 

requisitions, thereby eliminating the need for 

DAAS COG-based copy DAAS rules. 

2. The FI is used because there is an 

essential difference to DLA between the 

TEWELS images and those under PDC 404. 

For TEWELS, DLA uses the image to take a 

financial action. For the Navy BRAC 

transaction images, there is no financial 

action. The FI will be associated with posting 

as an information record without financial 

action. 

7. USTRANSCOM Abstains