1 of 4 

 ADC 356 

Attachment 

ATTACHMENT TO ADC 356 

Revise DS 846I, Asset Status Report to Address Intra-Navy Requirements for Navy 

Document Identifier BA7, Cyclic Asset Status Report - Mobile Activities (Supply) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

 a. Technical POC: Navy Supply Process Review Committee (SPRC) representative on 

behalf of Navy ERP, NAVSUP E4, DSN 430-7510, commercial (717) 605-7510 

 b. Functional POC: Navy SPRC representative on behalf of Navy ERP, NAVSUP E4, 

DSN 430-7510, commercial (717) 605-7510 

2. FUNCTIONAL AREA: Primary/Secondary Functional Area: Supply 

3. BACKGROUND: 

a. Intent of the transaction: Organizations use this transaction set to inform another 

organization about inventory information. 

b. Scenario for which the transaction is used: Reporting assets status (inventory 

balances) to the inventory manager. 

c. Procedures, transactions, data elements, processing details in use today: Navy end-use 

activities own their inventory and do not report their balances to the Inventory Control Point (ICP). 

When their allowances are increased they requisition new material using funds designated for 

allowance increases. Under this “pull” process the ICP is unable to validate that the requisitioning 

site is below their allowance and qualifies to use these funds. The modernized Navy ERP system 

changes the process to a “push” scenario. Under the “push” scenario the ICP will track when the 

sites are below their allowances and then send the material to the sites. The Navy systems use the 

BA7 transaction to notify the Navy Inventory Control Point (NAVICP) about inventory balances. 

These transactions allow the NAVICP to keep track of the inventory balances for these items. Data 

mapping requirements between Navy Document Identifier (DI) Code BA7 (Cyclic Asset Status 

Report - Mobile Activities) and DS 846I are provided at the enclosure. 

4. PROPOSED CHANGE(S): 

a. Revise DS 846I, Asset Status Inquiry/Report, as shown in Change Table Below: 

Item # Location DS 846I Revision Reason 

1. DLMS 

Introductory 

Note 1 

Revise DLMS Note 1 to read:

DLMS Note: 1. DLSS functionality allows for Service/ 

Agency data in various record positions (rp). Data 

conveyed therein will require Service/Agency 

identification to DLMSO and incorporation into the 

DLMS. This transaction encompasses functionality of 

MILSTRAP Document Identifier (DI) Codes DZA, DZE, 

and DZF. This transaction also accommodates the 

functionality of Army DI Code BSS for intra-Army use

and Navy DI Code BA7 for intra-Navy use.

Add Navy unique BA7 

transaction to the 846I. 
2 of 4 

ADC 356

Attachment

Item # Location DS 846I Revision Reason 

2. DLMS 

Introductory 

Note 6 

Add ADC 356 to DLMS Introductory note 6:

- ADC 356, Revise DS 846I, Asset Status Report 

to Address Intra-Navy Requirements for Navy 

Document Identifier BA7, Cyclic Asset Status 

Report - Mobile Activities (Supply) 

To identify PDC/ADC in 

the DS. 

3. 2/REF01/140 Add qualifiers 06, BO, FSN, and YL with DLMS 

notes:

06 System Number 

DLMS Note: Navy uses to cite the type of system 

the activity is using to manage their materiel. 

Authorized for intra-Navy use only, to identify the 

system type. For all other use this is a DLMS 

enhancement; see introductory DLMS note 4a. 

Refer to ADC 356. 

BO Bin Location Number 

DLMS Note: Authorized for intra-Navy use 

only, to identify the warehouse bin location. For 

all other use this is a DLMS enhancement; see 

introductory DLMS note 4a. Refer to ADC 356. 

FSN Assigned Sequence Number 

DLMS Note: Authorized for intra-Navy use 

only, to identify the Automated Shore Interface 

Sequence Number of the last allowance calculated 

for the activity. For all other use this is a DLMS 

enhancement; see introductory DLMS note 4a. 

Refer to ADC 356. 

YL - Allowance Recipient Identification 

DLMS Note: Authorized for intra-Navy use 

only, to identify the Allowance Type Indicator. 

Values are O’ for General Stores and ‘Q’ for 

Restricted Stores. For all other use this is a 

DLMS enhancement; see introductory DLMS note 

4a. Refer to ADC 356. 

To add qualifiers for the 

following Navy DI Code 

BA7 data: 

 

-System Type; 

-Warehouse Bin 

Location; 

- Automated Shore 

Interface (ASI) Sequence 

Number; 

- Allowance Type 

indicator 
3 of 4 

ADC 356

Attachment

Item # Location DS 846I Revision Reason 

4 2/QTY01/320 Add new qualifiers ‘92’ and ‘MA’ with DLMS notes:

92 Allotted Usage Quantity 

DLMS Note: Navy uses to identify the sum of the 

Coordinated Shipboard Allowance List (COSAL) 

allowances for General Stores or Restricted Stores 

items. Authorized DLMS migration enhancement for 

intra-Navy use only. For all other use this is a DLMS 

enhancement; see introductory DLMS note 4a. Refer 

to ADC 356. 

MA Miscellaneous Allowance 

DLMS Note: Navy uses to identify the allowance 

quantity being reported for the Load List, Fleet Issue 

Load List (FILL), or the Aviation Consolidated 

Allowance List (AVCAL). Authorized DLMS 

migration enhancement for intra-Navy use only. For 

all other use this is a DLMS enhancement; see 

introductory DLMS note 4a. Refer to ADC 356. 

To provide for Navy 

quantity requirements 

b. Proposed procedures: Revise DOD 4000.25-M, DLMS, Volume 2, Chapter 22 __ to 

add new paragraph C22.2.4 addressing intra-Navy use of 846I as follows: 

“C22.2.4. Intra-Navy Use. Navy also uses the DLMS Asset Status Report Transaction on an 

intra-Navy basis for reporting allowance based assets that are below the wholesale distribution 

system to the ICP. This allows the ICP to determine when the activity requires more material 

due to being below their allowance.”

 c. Alternatives: 

 1) Develop modernized Navy system using non-DLMS transaction. 

 2) Change multiple legacy Navy systems to output BA7 DIC or 846I DLMS transactions. 

5. REASON FOR CHANGE: Navy modernized system development is being programmed 

to be DLMS compliant. The legacy systems DI Code BA7 matches well with the DLMS 

equivalent 846I Inventory Inquiry/Advice transaction, but has never been mapped to it. 

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages (tangible/intangible): Allows development of only a DLMS compliant 

solution for the 846I functionality. 

 b. Disadvantages: None. 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Expected implementation 

date is February 2010. Expected testing is January 2010. 
4 of 4 

ADC 356

Attachment

8. IMPACT: 

a. DOD 4000.25-M, DS 846I. 

b. DAASC mapping. DAASC translate Navy DI Code BA7 transactions to DLMS 846I 

transactions when sending them to a DLMS compliant Navy system. This is a one-way 

translation requirement since Navy does not require translation from DLMS 846I to DI Code 

BA7. Navy Force Inventory Management Analyst Reporting System (FIMARS) and Navy RSupply are the two legacy systems creating DI Code BA7. 

c. Automated Information Systems . This change is for intra-Navy use only. No 

change/impact to other Component systems, to include no change/impact to the DLA 

Distribution Standard System. 

d. New data Element not used in any other DLMS transactions to date. This change 

proposes adding the following data to DS 846I to support the Navy DI Code BA7 data 

requirements:

 Warehouse Bin Location. The warehouse bin location.

 Automated Shore Interface Sequence Number. The Automated Shore Interface 

Sequence Number is the reference number of the last allowance calculated for the activity.

 System Type. Identifies the type of system that the activity is using to manage their 

material. 

 Allowance Type Indicator. Navy states that the indicator will be published in NAVSUP 

Pub 485, and that the values are ‘O’ for General Stores and ‘Q’ for Restricted Stores. The 

Restricted Stores are things like Nuclear material. 

 COSAL Quantity. A quantity for the Coordinated Shipboard Allowance List (COSAL). 

Navy states that NAVSUP Pub 485 defines COSAL as a basic and unique guide for determining the items 

and quantities which should be stocked by the Supply Department to support the equipment installed 

onboard. This list can also be used to define the basis for which an item is stocked by the ship. It also 

contains nomenclature and nameplate data on equipment and identification data for repair parts.

 Miscellaneous Allowance Quantity. A quantity for Miscellaneous Allowances which 

includes the allowance quantity being reported for the Load List, Fleet Issue Load List (FILL), or the 

Aviation Consolidated Allowance List (AVCAL). Navy states that NAVSUP Pub 485 defines ACAL and 

FILL as follows::

o Aviation Consolidated Allowance List (AVCAL). A document that lists the items 

and quantities of aeronautical material authorized to be stocked by an aircraft carrier/MALS to support the

maintenance and operations of assigned or embarked aircraft. It is tailored for each aircraft carrier/MALS; 

LPH/LHA and the items listed are selected for all ARRs/ALs that apply to the assigned or embarked aircraft.

o Fleet Issue Load List (FILL). Consolidated listing of material to be carried onboard 

combat stores ships for the support of operating afloat forces to ensure maximum fleet readiness. It is based on 

actual past demands of those items most commonly requested by the fleet units
ADC 356 

Enclosure 

ENCLOSURE TO ADC 356 

Revise DLMS Supplement (DS) 846I, Asset Status Report to Address Intra-Navy 

Requirements for Navy DI Code BA7, Cyclic Asset Status Report - Mobile Activities

1. Embedded Navy spreadsheet identifies Navy DI Code BA7 data mapping to DS 846I: 

D:\Documents and 

SettBA7 to 846I Map.

2. Navy BA7 format from NAVSUP P-485 Volume II - Supply Appendices, Appendix 28, 

MILSTRIP/MILSTRAP Formats, Section IX: 

BA7 Format 

Field 

Positions M/O Field Legend Explanation 

1-3 M Document Identifier “BA7” 

4-6 M Routing Identifier “NRP” 

7 M Allowance Type Indicator Set “O” for General Stores and “Q” for Restricted Stores 

8-20 M National Stock Number Perpetuate the NSN 

21-22 O SMIC Perpetuate the SMIC, if applicable 

23-24 M Unit of Issue Perpetuate the Unit of Issue 

25-29 M On Hand Purpose Code A 

Quantity 

Perpetuate the General Stores or Restricted Stores total onhand quantity as appropriate for NAS sites (zero filled) 

30-34 M On Hand Purpose Code W 

Quantity 

Perpetuate the General Stores or Restricted Stores total onhand quantity as appropriate for all “V” and “R” service 

code activities (zero filled) 

35-39 M Due-In Perpetuate the General Stores or Restricted Stores total 

due-in quantity as appropriate 

40-44 M COSAL Sum the COSAL allowances for General Stores or 

Restricted Stores item 

45-49 M Load List/FILL/AVCAL Perpetuate the allowance quantity for the Load List, FILL 

value, or AVCAL allowance being reported 

50-54 M Requisitioning Objective Perpetuate the General Stores or Restricted Stores total 

Requisitioning Objective quantity as appropriate 

55-60 O Primary Location 

Provide the primary location of stock record item from the 

General Stores or Restricted Stores item record, when 

available 

61-69 M ASI Sequence Number Provide the last ASI number processed by the activity 

(zero filled) 

70-71 M Cognizance Symbol Perpetuate from Cognizance Symbol 

72 O Material Control Code Perpetuate the Material Control Code, when available 

73-75 M Routing Identification Code Perpetuate the Routing Identification Code (RIC) of the 

activity generating the report 
ADC 356

Encl

Field 

Positions M/O Field Legend Explanation 

76-79 M Date Perpetuate the Julian Date of the DOCID BA7 transaction 

80 M Required A0 Format for 

push 

1 = Legacy system (Micro SFM)(A0_ 117 Card Column 

format)) 

2 = Ported SNAP and RSupply End Use (A0_ 120 Card 

Column format) 

3 = SUADPS-RT (A0_ 80 Card Column format) 

4 = RSupply NWCF (Restricted COSALs) will use the 

80 Card Column format; and, for normal SRI items, to 

include all General Stores, a DWK format.