1 of 11 

ADC 308 

Attachment 

ATTACHMENT TO ADC 308 

Administrative Update to DLMS Chapter for Asset Status Reporting and Migrate Army 

Single Stock Fund (SSF) Asset Balance Reporting Transaction, Document Identifier (DI) 

Code BSS, to DLMS 846I, Asset Status, for Intra-Army Use (Supply) (Staffed by PDC 327)

1. ORIGINATOR: 

 a. Service/Agency: Army Headquarters, United States Army Materiel Command (AMC) 

 b. Originator: Army, Logistics Modernization Program (LMP), commercial phone: 856-

988-4878 

2. FUNCTIONAL AREA: Supply 

3. REFERENCES: 

 

 a. DLMSO Memorandum, July 30, 2007, subject: Approved DLMS Change (ADC) 

250, Revise DLMS Supplement (DS) 846I and MILSTRAP DZA Asset Status 

Transactions to Support Army Distribution Operations, and revise DS 846I for Use of 

Universal Time Coordinate (UTC) and for Administrative Updates, http://www.dla.mil/j6/dlmso/eLibrary/Changes/approved3.asp 

 b. Army Regulation (AR) 710-2, Supply Policy Below the National Level, March 28, 2008, 

http://www.army.mil/usapa/epubs/pdf/r710_2.pdf 

4. REQUESTED CHANGE: 

 a. Title: Administrative Update to DLMS Chapter for Asset Status Reporting and 

Migrate Army Single Stock Fund (SSF) Asset Balance Reporting Transaction, Document 

Identifier (DI) Code BSS, to DLMS 846I, Asset Status, for Intra-Army Use (Supply) 

 b. Description of Change: 

(1) DLMSO is revising DoD 4000.25-M, DLMS, to establish a separate chapter for 

Asset Status Reporting and for administrative updates to the chapter to incorporate 

correlation of the DS 846I beginning segment Report Type Code to the corresponding DoD 

4000.25-2-M, MILSTRAP DI code, for information in a mixed DLMS/DLSS environment 

consistent with other MILSTRAP related DLMS chapters. In addition to these 

administrative changes, DLMSO will revise the chapter to address the intra-Army use of DS 

846I Asset Status Report transaction for the function associated with Army DI Code BSS. 

(2) ARMY requests that Army-unique DI Code BSS (Single Stock Fund (SSF) 

Asset Balance Reporting Transaction) data requirements be incorporated into DS 846I, 

Asset Status Report. Army DI Code BSS serves a dual purpose: 
2 of 11 

ADC 308 

Attachment 

• When used from the Single Stock Fund to the National level systems, the transaction 

represents a report to update the Requisitioning Objective, Reorder Point and Retention 

Limit. The Requisitioning Objective (already included in DS 846I by ADC 250 (reference 

3.a)) represents a level of stock that is required to support an individual SSF site, and is 

protected from being used by the National Level to fill other requisitions due to stock 

shortages. 

• When used during a Logistics Reassignment outside the Army by the Losing Item Manager, 

the transaction informs the Army manager for Non-Army Managed Items (NAMI), Routing 

Identifier Code AJ2 (TACOM Rock Island), of the Requisitioning Objective and Safety 

Level to be set in their systems to be able to monitor and maintain the SSF stocking levels. 

 c. BSS Data Requirements: Some of the data required for the DI Code BSS was previously 

incorporated in DS 846I by ADC 250 in support of Army use of MILSTRAP DZA multiuse fields 

(i.e., Requirements Objective, Safety Level, and Transaction Preparation Date). Other BSS data was 

already present in DS 846I (e.g., Reorder Point Quantity, Retention Quantity, Location of Goods, and 

Storage Activity). The two new data requirements identified for 846I to support BSS are Project 

Code (BSS rp 55 – 57) and Stockage List Code (BSS rp 78): 

(1) Authorize the use of the data element 1270 LQ01 = 78 (Project Code). 

 (2) At the time of PDC 327, there was no existing LQ 1270 qualifier for “Stockage List Code” 

and all established LQ 1270 qualifiers are associated with specific industry code lists. Accordingly 

DLMSO submitted an Accredited Standards Committee (ASC) X12 data maintenance (DM) request to 

establish a new X12 1270 qualifier ‘SLC’ for “Stockage List Code” in a higher X12 version. A new 

Local Code ‘SLC-Stockage List Code’ was identified for use with data element 1270 in the LQ 

segment at that time, however the ANSI DM has since been approved and 1270 qualifier ‘SLCStockage List Code’ was approved for use in version 6020 . Once the code was approved by X12, the 

DLMS ‘local code’ became a DLMS ‘migration code’ for use with DS 846I, version 4010. An 

alternative to using a local/migration code would have been to “borrow” a 1270 code that represented a 

code list other than stockage list code. Descriptions for ‘local code’, ‘migration code’ and ‘borrowed 

code’ are as follows. 

Local Code: A local code is a code value that is not in the current version, and has not yet been 

established at a higher ASC X12 version. A DM action is submitted to establish the code in a higher 

version. Once approved by ASC X12, the local code becomes a ‘migration code’. 

Use of a “local code” to identify code SLC for Stockage List Code refers to establishing an agreement 

with all trading partners involved to use a code not yet recognized in X12. Manual intervention may be 

needed for some commercial applications to accept the local code. 

Migration Code: A migration code is when a code from a higher (but existing) ASC X12 version is 

used in a lower version. The semantic meaning and syntax are consistent with the higher version. Use of 

a “migration code” refers to establishing an agreement with all trading partners involved to use a valid 

X12 code from a higher version, with its approved X12 definition, at a lower version of X12. Manual 

intervention may be needed for some commercial applications to accept the higher version code. 

In this instance, once the DM action for ‘SLC-Stockage List Code ’was approved by X12, local code 

‘SLC’ became a migration code when used in 846I, version 4010. ‘SLC’ is approved at version 6020. 
3 of 11 

ADC 308 

Attachment 

Borrowed Code: 

Use of a “borrowed code” refers to establishing an agreement with all trading partners to use a valid 

X12 code at the correct version by altering the code’s semantic meaning (i.e., the code is only used 

for its syntax). The borrowed value must be a value that is otherwise un-used by the trading partners 

allowing its definition to be mutually changed. In the case of data element 1270, existing codes are 

associated with a specific industry code list. DLMSO has submitted the ASC X12 DM for a new 1270 

code ‘SLC-Stockage List Code” which would likely be approved for use in ANSI ASC X12 version 

6010 or higher. In this instance, the borrowed code used in the interim would be ‘SH-Source of Lead’. 

If used, ‘SH-Source of Lead’ would be understood by trading partners to mean Stockage List Code. 

‘SH’ would represent ‘stockage list code’ in DLMS transactions below version release 6010, despite its 

true association with an industry code list for another purpose. Any transaction created in version 6010 

would be able to use the actual approved value ‘SLC’, however it is not known if the Department of 

Defense will ever migrate to version 6010 to take advantage of code ‘SLC’. 

There is a trade off to using any of the alternative code documentation methods listed above. What is 

gained in semantic clarity with migration codes is lost in syntactic validation. What is gained in 

syntactic validation with borrowed code is lost in semantic clarity as the data element is not used as it 

was intended. 

 d. BSS Data use: 

(1) Reorder Point (ROP) is utilized in the same manner as other ROP reporting, to identify 

to the National level the ROP for the specified material and SSF site and is used to assist in supply 

planning. Use existing Qualifier 2/QTY01/320 = YW (Reorder Point Quantity) (BSS rp 37-41) 

(2) Retention Limit. NOTE: In PDC 327 Army indicated that Retention Limit serves 

the same purpose as Safety Level, however the MILSTRAP Administrator found that while they 

share a field in the Army DI Code BSS (rp 49-54), they are not identical data elements and they 

require distinct qualifiers in DLMS: 

• Safety Level = 2/QTY01/320 qualifier “XY-Safety Level” 

• Retention Limit = 2/QTY01/320 qualifier “V1-Retention Quantity” 

By this change Army defined Retention Limit as: “Retention Limit identifies the maximum 

authorized stockage level for the specified material and SSF site, and is used to determine excess 

stocking conditions.” 

AR 710-2 defines Safety Level as: “Quantity of stock intended to permit continued support in the 

event of minor interruption of stockage replenishment or unpredictable fluctuation in demand rate, or 

both.” 

(3) Stockage List Code (SLC) identifies the type of stocking requirements, for the 

material and SSF site, and is used to identify stocking criteria and review requirements for items 

on the Authorized Stockage List. DLMSO is establishing a local code for data element 1270 at 

2/LQ/376 as ‘SLC-Stockage List Code’. The authorized stockage list code values according to 

AR 710-2 (reference 3.b), paragraphs 3-8b and 4-8b are as follows: 
4 of 11 

ADC 308 

Attachment 

 (i) D – Stocked demand. Stockage is based on restricted levels may have a 

critical worldwide shortage and the requisitioning objective is determined by the national ICP 

and the MACOM, high dollar value restriction imposed by MACOM. 

 (ii) F - Stocked other. Non-demand supported item. This applies to Operational 

Readiness Float (ORF) stocks. ORF stocks are designed to assist in maintaining the readiness 

posture of combat units and specialized activities. The ORF is an additional controlled level of 

selected, mission essential items of equipment authorized to be on hand to meet unprogrammed 

maintenance requirements when repair of similar items from a unit cannot be accomplished in a 

specified time. Reviewed annually to validate requirements. 

 (iii) M - Stocked numeric. Non-demand supported item with expected use. The 

requisitioning objective (RO) for combat essential low density end item’s repair parts will be 

the quantity needed to repair one piece of equipment and the reorder point (ROP) will be zero. 

Reviewed annually to validate requirements. 

 (iv) P - Stocked provisioning. Non-demand supported item; stocked to support 

a newly introduced end item for up to 2 years until forecast requirements is based entirely upon 

actual demands. Initial stockage and item demand data is reviewed after 1 year. If the item 

has met the retention criteria of three demands it will be converted to SLC “Q.” Items may be 

deleted from stockage after 1 year if the retention criterion is not met and no demands are 

anticipated for the second year. At the end of 2 years, items failing to meet the retention criteria 

will be deleted from stockage unless justified under SLC “M” criteria. Increases to stockage 

quantities prescribed in the SLAC are not authorized unless supported by recurring demands. 

Quantities may be increased based upon actual demand data. 

 (v) Q - Stocked demand. Demand supported item. Stockage is based upon 

actual recurring demands in a 360-day period. Items may be added to the ASL based on the 

ninth recurring demand within a 360-day period, and deleted when the item has not received at 

least three demands in the most recent 360-day period. 

 (vi) R – Decrement stock. 

 (vii) X - Army prepositioned stocks (APS). Authorized on hand levels of APS 

material stocks 

 (viii) Z - Non-stocked items. Non-demand supported items. These items will 

not have a set RO. Inventory and use data will be recorded but replenishment will not be 

made. These items are in excess and must be turned in. 

 

 d. Procedures: 
5 of 11 

ADC 308 

Attachment 

(1) Revise DoD 4000.25-M, DLMS, Volume 2. The Asset Status Reporting 

procedures are currently published in DLMS Volume 2, chapter 5 (Status Reporting), along 

with Supply Status and Shipment Status procedures. However, this approved change 

establishes Assert Status Reporting as a separate chapter:

(a) Revise chapter 5, Status Reporting, to remove the Asset Status Reporting 

procedures by deleting section C5.1 and renumbering remaining sections. 

(b) Establish new chapter for Asset Status Reporting as shown at Enclosure 1. 

The new chapter includes: 

[1] Asset status reporting procedures formerly published by chapter 5, section C5.1. 

[2] Administrative updates to incorporate a correlation between the DLMS 846I 

beginning segment Transaction Type Codes and the corresponding MILSTRAP DI Codes. 

This provides information beneficial in a mixed Defense Logistics Standard System (DLSS) 

(aka MILS) -DLMS environment and positions the chapter for the DLMSO initiative to 

combine the MILSTRAP manual with the DLMS manual. To that end, the new chapter also 

incorporates functional procedures from MILSTRAP, which are currently absent in the DLMS 

chapter. 

(2) Revise DS846I as follows to support Army DI Code BSS: 

Item 

# 

Location Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note 1 

Revise DLMS introductory Note 1:

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.

To identify DI Code of 

transaction functionality 

incorporated in DS 846I. 

No impact. 

2. DLMS 

Introductory 

Note 4 

Add new DLMS introductory note 4.f:

4.f. Data required to accommodate 

Component-unique transaction 

requirements (e.g., B-series 

transactions).

 

Add standard DLMS note 

addressing Component unique 

data. 

No impact. 
6 of 11 

ADC 308 

Attachment 

Item 

# 

Location Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

3. DLMS 

Introductory 

Note 6 

Added ADC 308 to DLMS Introductory 

note 6:

- ADC 308, Administrative Update to 

DLMS Chapter for Asset Status 

Reporting and Migrate Army Single 

Stock Fund (SSF) Asset Balance 

Reporting Transaction, Document 

Identifier (DI) Code BSS, to DLMS 

846I, Asset Status, for Intra-Army Use 

(Supply) 

To identify DLMS changes 

included in the DS 

No impact. 

4. 2/QTY01/320 Modified DLMS Note 2 for existing 

qualifier RY:

RY Requirement Quantity 

DLMS Note 2. For intra-Army use, 

Army uses to identify the Requirements 

Objective quantity established by 

purpose code. This equates to Army 

prescribed data in MILSTRAP DZA 

multiuse field, rp 43-48, and intraArmy DI Code BSS, rp 43-48.

To support Army DLMS 

migration efforts. 

No impact. 
7 of 11 

ADC 308 

Attachment 

Item 

# 

Location Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

5. 2/QTY01/32

0 

For existing qualifier XY, add the 

following new DLMS Note 4:

XY Safety Level 

DLMS Note: 4. Authorized for intraArmy use, see DLMS introductory note 

4f. The Army losing item manager 

(LIM) uses during a Logistics 

Reassignment outside the Army to 

inform the Army manager for Non-Army 

Managed Items (NAMI) of the safety 

level to be set in their systems to be able 

to monitor and maintain the single stock 

fund (SSF) stocking levels. (Army DI 

Code BSS, rp 49-54) See ADC 308.

To support Army DLMS 

migration efforts. 

DLMSO NOTE: Under 

the 80 record position DI 

Code BSS format, Army 

uses BSS, rp 49-54, for 

safety level OR retention 

limit. Therefore, in a 

mixed DLMS/BSS 

environment, if DAASC is 

converting DI Code BSS 

to DS 846I, the rp 49-54 

field will be mapped to 

2/QTY01/130/XY-safety 

level since DAASC would 

not be able to discern 

whether 49-54 

represented the safety 

level or the retention 

limit. Likewise, if DAASC 

must convert a DS 846I to 

DI Code BSS, both 

qualifier XY (safety level) 

and V1 (Retention 

Quantity) will convert to 

BSS, rp 49-54. 

Should both XY and V1 be 

present in the DLMS 846I 

to be converted to BSS, 

then XY will map to BSS 

rp 49-54 and V1 will be 

dropped. 

This will not be a problem 

when Army creates DLMS 

846I and sends the 846I to 

an Army DLMS trading 

partner. When Army 

generates an 846I 

transaction, Army must 

identify retention limit 

using qualifier V1; and 

safety level using qualifier 

XY. The Army DLMS 

trading partner will then 

receive the 846I with the 

appropriate qualifier. 

No impact. 
8 of 11 

ADC 308 

Attachment 

Item 

# 

Location Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

6. 2/QTY01/320 For existing qualifier YW, and add new 

DLMS Notes:

YW Reorder Point Quantity 

DLMS Notes: 1. DLMS enhancement. 

See introductory DLMS note 4a. 

2. For intra-Army use only, Army uses 

to identify the Reorder Point Quantity 

at a Single Stock Fund site to the 

National Level. (Army DI Code BSS, rp 

37-41) See ADC 308. 

To support Army DLMS 

migration efforts. 

No impact. 

7. 2/QTY01/320 For existing qualifier V1, add the 

following DLMS Note 3:

V1 Retention Quantity 

DLMS Notes: 3. Authorized for intraArmy use, see DLMS introductory note 

4f. Army uses on an intra-Army basis 

from the single stock fund (SSF) to the 

National level systems, to update 

retention level quantity. (Army DI Code 

BSS, rp 49-54.) See ADC 308. 

To support Army DLMS 

migration efforts. 

See NOTE at row 5 above 

(2/QTY01/320 qualifier 

XY-Safety Level.) 

No impact. 

8. 2/LQ01/376 Add qualifier “78” with the following 

DLMS Notes:

78 Project Code 

DLMS Notes: 1. DLMS enhancement. 

See introductory DLMS note 4a. 

2. For intra-Army use only, Army uses 

to identify the project code associated 

with Logistics Reassignment actions 

and for reporting from Single Stock 

Fund sites to the National level. (Army 

DI Code BSS, rp 55-57.) See ADC 308. 

To support Army DLMS 

migration efforts. 

No impact. 
9 of 11 

ADC 308 

Attachment 

Item 

# 

Location Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

9. 2/LQ01/376 Add new qualifier ‘SLC’ with the 

following DLMS Note:

SLC Stockage List Code 

DLMS Note: 1. For intra-Army use 

only. This is the Army Stockage List 

Code. See introductory DLMS note 4.f. 

Use of this data is meaningful to Army 

only and equates to intra-Army DI Code 

BSS, rp 78. The code source for 

Stockage List Code is Army Regulation 

710-2, Supply Policy Below the 

National Level. See ADC 308. 

2. At this time a migration code ’SLC’ is 

established for use in 846I, version 

4010. A data maintenance action was 

approved in version 6020. The 

approved code/name is "SLC - Stockage 

List Code". 

To support Army DLMS 

migration efforts, 

establishing local code 

‘SLC’ for Army’s stockage 

list code in 846I. 

Use of a local code requires 

agreement with all trading 

partners. 

Once ANSI approves SLC 

for use in a higher version, 

its use in version 4010 will 

be updated to reflect that it 

is a ‘migration code’ 

No impact. 

 

(3) While DS 846I is open for revision under this PDC, the MILSTRAP 

Administrator is making the following administrative updates: 

Item # Location Administrative Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

1 1/BIA02/020 Revise DLMS Notes for TI and TJ: 

TI Asset Status Inquiry 

DLMS Note: Use to identify a 

Request for Asset Status Report 

transaction. (MILSTRAP DI Code 

DZE functionality) 

TJ Asset Status Advice 

DLMS Note: Use to identify an 

Asset Status Report transaction. 

(MILSTRAP DI Code DZA and DZF 

functionality). 

Administrative update

to provide correlation 

of the MILSTRAP DI 

Code to the beginning 

segment Report Type 

Code consistent with 

other MILSTRAP 

related DS. 

No impact 
10 of 11 

ADC 308 

Attachment 

Item # Location Administrative Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

2 2/LIN02/010 Add “DLMS enhancement” Note 2 to 

qualifiers A4, F4, FB, MN, SN, and 

YP.

A4 Subsistence identification 

Number 

DLMS Note 2. DLMS enhancement. 

See introductory DLMS note 4a. 

F4 Series Identifier 

DLMS Note 2. DLMS enhancement. 

See introductory DLMS note 4a. 

FB Form Number 

DLMS Note 2. DLMS enhancement. 

See introductory DLMS note 4a. 

MN Model Number 

DLMS Note 2. DLMS enhancement. 

See introductory DLMS note 4a. 

SN Serial Number 

DLMS Note 2. DLMS enhancement. 

See introductory DLMS note 4a. 

YP Publication Number 

DLMS Note 2. DLMS enhancement. 

See introductory DLMS note 4a. 

Administrative update No impact 

3 2/LIN02/010 Delete DLMS notes from qualifier FS:

FS National Stock Number 

1. Must use NSN when known.

2. DLMS enhancement. See 

introductory DLMS note 4a.

Administrative update. 

“Must use NSN when 

known” is stated in the 

note at LIN02 and is 

redundant at the code 

level. 

NSN is not a DLMS 

enhancement. 

No impact 
11 of 11 

ADC 308 

Attachment 

Item # Location Administrative Revision to DS 846I 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

4 2/LIN04/010 Delete DLMS enhancement note from 

qualifier ZB:

ZB Commercial and Government 

Entity (CAGE) Code 

2. DLMS enhancement. See 

introductory DLMS note 4a.

Administrative update. 

Use of CAGE with a 

Part number is not 

specifically called out in 

MILS formats, but when 

a part number is entered 

in the ‘stock or part 

number’ field in MILS, 

the first 5 positions are 

understood to be a 

CAGE. Under variable 

length DLMS, CAGE is 

identified as a distinct 

data element separate 

from part number. 

No impact 

 e. Alternatives: None known. 

5. REASON FOR CHANGE: Documents and incorporates Army’s intra-Army use DI Code 

BSS data requirements in DLMS. The data provides value-added information for Army. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports Army implementation of DLMS migration effort by 

incorporating Army-unique DI Code BSS (SSF Asset Balance Reporting Transaction) data 

requirements into DS 846I 

b. Disadvantages: None identified. 

7. IMPACT: 

a. Updates DoD 4000.25-M, DLMS, Volume 2, as shown in Enclosure 1.

 b. Modify DS 846I and DAASC conversion maps to incorporate Army DI Code 

BSS data requirements.
CXX-1 

ADC 308 

Enclosure 1 

ENCLOSURE 1 TO ADC 308 

Administrative Update to DLMS Chapter for Asset Status Reporting and Migrate Army 

Single Stock Fund (SSF) Asset Balance Reporting Transaction, Document Identifier Code 

BSS, to DLMS 846I, Asset Status, for Intra-Army Use (Supply) 

CXX. CHAPTER XX

ASSET STATUS REPORTING 

Cxx.1. GENERAL

 Cxx.1.1 Purpose. This chapter prescribes Asset Status Reporting procedures for the 

interchange of asset status information between the DoD Component wholesale and below 

wholesale distribution systems and owners/managers. 

 Cxx.1.2. Transactions. This chapter addresses the procedures applicable to the 

following ASC X12 transaction functions identified by their beginning segment (1/BIA02) 

report type codes and their DLSS (MILSTRAP) counterparts identified by their document 

identifier (DI) codes. Both are covered to allow for processing in a mixed DLMS/DLSS 

environment. Other formats, such as XML, are also available. See the DLMSO website 

for available DLMS and DLSS formats: http://www.dla.mil/j6/dlmso/elibrary/TransFormats/140_997.asp. 

 Cxx.1.2.1. DS to Federal IC 846I, Asset Status Inquiry/Report, is used for the 

following transaction functions identified by the beginning segment Report Type Code: 

 Cxx.1.2.1.1. Request for Asset Status Report is identified by Report Type 

Code TI - Asset Status Inquiry. This transaction provides MILSTRAP DI Code DZE 

functionality. 

 Cxx.1.2.1.2. Asset Status Report is identified by Report Type Code TJ - 

Asset Status Advice. This transaction provides MILSTRAP DI Code DZA and DZF 

functionality. 

Cxx.2. IN STORAGE ASSETS 

 Cxx.2.1. Assets within the wholesale distribution system. 

 Cxx.2.1.1. For assets within the wholesale distribution system, Asset Status 

Report Transactions may be used between DoD Components by mutual agreement. Send 

Asset Status Report Transactions (DI Code DZA) between DoD Components based on 

schedules established by mutual agreement. 

 Cxx.2.1.2. Asset status transactions may be used between a Service ICP and a 

DLA storage activity by mutual agreement. 
CXX-2 

ADC 308 

Enclosure 1 

 Cxx.2.1.3. Under MILSTRAP, due to the number of record positions in DI Code 

DZA devoted to entries prescribed by the DoD Components for use within Component 

distribution systems, each Component is authorized to procure a printed format suitable to its 

needs. DoD Components must identify to DLMSO any Component prescribed data in DI 

Code DZA which will be required in the Component’s modernized system using the 

DLMS. This is necessary so that DLMSO can incorporate the Component data in the DS 

846I Asset Status Report Transaction. 

 Cxx.2.2. Assets below the wholesale distribution system. Assets below the 

wholesale distribution system shall be reported when requested by the owner/ manager. 

 Cxx.2.2.1. Use the Request for Asset Status Report Transaction, with the 

appropriate asset status code to request, change, or discontinue asset status reporting from the 

below wholesale distribution system. 

 Cxx.2.2.2. For the total asset visibility program, use the Request for Asset Status 

Report Transaction to request the report of assets above the requisitioning objective using DS 

to Federal IC 180M, Material Returns Reporting (MILSTRIP DI Code FTE). Use with the 

asset visibility program is based on agreement of the DoD Components involved. 

 Cxx.2.2.3. Transmit Request for Asset Status Report Transactions to central points 

designated by DoD Components. Each DoD Component designated activity shall be 

responsible for notifying their reporting activities of the reporting requirements shown in the 

Request for Asset Status Report Transactions received from the other Components. The 

Component activities designated to receive the requests are: 

Component ACTIVITY ROUTING 

IDENTIFIER CODE

Army USAMC Logistics Support Activity 

ATTN: AMXLS-V 

Building 5307, Sparkman Center 

Redstone Arsenal, Al 35898-7466 

AGT 

Navy Navy Fleet Materiel Support Office 

Mechanicsburg, PA 17055-5000 

N47 

Air Force Headquarters 

Air Force Materiel Command 

4375 Chidlaw Road, Suite 6 

Wright-Patterson Air Force Base 

Dayton, OH 45433-5006 

FNA 

Marine Corps Commanding General 

Marine Corps Logistics Base 

Albany, GA 31704-1128 

MPB 

 Cxx.2.2.4. Always show dates for commencement of reporting (Asset Status 

Reporting Code C and D) and change of reporting (reporting codes H and J) in the Request for 

Asset Status Report Transaction as the first day of a month. In these instances, send the request 

transaction not later than 60 calendar days before the commencement date. 
CXX-3 

ADC 308 

Enclosure 1 

 Cxx.2.2.5. Provision is made for requesting earlier commencement of reporting by 

use of Asset Status Reporting Code M. In this instance, the Services’ central points shall 

ensure that reporting commences as soon as possible after receipt of the request. 

 Cxx.2.2.6. When a one-time asset status report is required on an expedited basis, the 

Request for Asset Status Report Transaction shall contain Asset Status Reporting Code Z and the 

date the report is required. The Component central point or the reporting activity in receipt of the 

request shall take no further action if the date the report is required is already past. 

 Cxx.2.2.7. When a one-time asset status report is required for the asset 

visibility/redistribution program, the Request for Asset Status Report Transaction shall 

contain Reporting Code N and the date the report is required. Use with the asset visibility 

program is based on agreement of the Components involved 

 Cxx.2.2.8. Use the Request for Asset Status Report Transaction to request termination 

of reporting by citing Asset Reporting Code E. Show dates for termination of reporting in the 

transaction as the last day of the month. Send the Request for Asset Status Report Transaction 

termination request not later than 60 calendar days prior to the termination date entered in the 

transaction. 

 Cxx.2.2.9. Activities below the distribution system (base, post, camp, or station) 

shall use Asset Status Report Transactions, to report assets to the requesting ICP. Report on 

hand balances by each separate supply condition of material held. Under the constraints of the 

MILSTRAP fixed length format, the DI Code DZF Asset Status Report Transaction is 

designed to provide for use of multiple transactions when either or both of the following apply: 

 Cxx.2.2.9.1. More than two conditions of materiel are held. 

 Cxx.2.2.9.2. Requisitioning objective, due-in, or reserved quantities 

exceed 999,999. 

 Cxx.2.2.10. The asset status reporting code cited in the Asset Status Report 

Transaction shall indicate the type of reporting being accomplished. 

Cxx.2.3. Intra-Army Use. Army also uses the DLMS Asset Status Report 

transaction on an intra-Army basis for Army Single Stock Fund Asset Balance 

Reporting. This use serves a dual purpose: 

 Cxx.2.3.1. When used from the Single Stock Fund to the National level 

systems, the Asset Status Report transaction represents a report to update the 

Requisitioning Objective, Reorder Point, and Retention Limit. 

 Cxx.2.3.2. When used during a Logistics Reassignment outside the Army by 

the Losing Item Manager, the Asset Status Report transaction informs the Army 

manager for Non-Army Managed Items (NAMI) of the Requisitioning Objective and 

Safety Level to be set in their systems to be able to monitor and maintain the Single Stock 

Fund stocking levels. 
1 of 1 

ADC 308 

Enclosure 2 

Enclosure 2 to ADC 308 

Army DI Code BSS Format

Record 

Position

Field Legend Explanation

1 – 3 Document identifier code Enter DI Code BSS

4 – 6 Routing identified code-to Enter RI code of the ICP to which this transaction is being 

forwarded

7 Suffix code Leave Blank

8 – 22 National stock number Enter the NSN of the item reported

23 – 24 Unit of issue Enter the UI of the item

25 – 30 On hand quantity Enter on hand quantity. If quantity = 0, zero filled

31 – 36 Due-in quantity Enter due in quantity. If quantity = 0, zero filled

37 – 41 Reorder Point (ROP) quantity Enter ROP quantity. If quantity = 0, zero filled

42 Blank Leave blank

43 – 48 Requirements objective (RO) 

quantity

Enter the RO quantity established for each purpose code shown in 

rp 70.

49 – 54 Safety level/Retention Limit 

Quantity

Enter the quantity that reflects the Retention Safety Level or 

Retention Limit requirements

55 – 57 Project code If purpose code is E, V, or R, then mandatory, otherwise leave 

blank

58 – 60 Routing identifier code Enter the code identifying the activity at which the item is stored if 

different from the activity preparing the transaction (rp 67-69)

61 – 64 Date prepared Enter Julian date on which the transaction was prepared

65 – 66 Blank Leave Blank

67 – 69 Routing identifier code Enter the RIC that identifies the activity preparing this transaction.

70 Ownership or purpose code Enter the ownership or purpose code as prescribed in MILSTRAP

71 Supply condition code Enter the condition code of the item as prescribed in MILSTRAP

72 – 77 Blank Leave blank.

78 Stockage list code Enter the appropriate Stockage List Code

79 – 80 Blank Leave Blank
1 of 2 

ADC 308 

Enclosure 3 

Enclosure 3 to ADC 308 

Proposed DAASC Mapping for Intra-Army DI Code BSS

Field Name DI Code BSS

Record Position 

Conditions DLMS Data Element 

Transaction Set Identifier 

Code 

None None ST01=846 

Transaction Set Control 

Number 

None None ST02= Serial Number 

Beginning Segment None If RP1=D 

If RP1-3=BSS 

If RP1-3=BSS RP61-64 

BIA01=00 

BIA02=TJ 

BIA03=Z 

BIA04=()CCYYMMDD 

BIA05=()HHMM 

Storage Area 67-69 If RP1-3 = BSS AND 

RP67-69 is not blank 

N101=SB 

N103=M4 

N104=RP 67-69 

N106=FR 

National Stock Number 8-20 If RP12-13=00 or 01 LIN02=FS 

LIN03=RP 8-20 

Code Source Information None Department of Defense LM01=DF 

Document Identification 

Code 

1-3 None LQ01=0 

LQ02=RP 1-3 

DI Code in DLMS is available for a 

transition period in a mixed DLSSDLMS environment. DI Code is 

identified for streamlining in a full 

DLMS environment. 

1/BIA02/020 Report Type Code TJ 

is for Asset Status Report 

Quantity on Hand 25-30 If RP1-3=BSS AND 

RP 25-30 <> “000000” 

QTY01 = 17 

QTY02 = RP 25-30 

Unit Of Issue 23-24 None QTY03= RP23-24 

Code Source Information None None LM01=DF 

Project Code 55-57 If RP1-3=BSS LQ01=78 

LQ02=RP 55-57 

Supply Condition Code 71 If RP1-3=BSS LQ01=83 

LQ02=RP 71 

Purpose Code 70 If RP1-3=BSS LQ01=99 

LQ02=RP 70 

Ownership Code 70 If RP1-3=BSS LQ01=A1 

LQ02=RP 70 

Stockage List Code 78 If RP1-3=BSS LQ01 = SLC 

LQ02 = RP 78 

Due-In Quantity 31-36 If RP1-3=BSS 

RP 31-36 <> “000000” 

QTY01 = BA 

QTY02 = RP 31-36 

Reorder Point Quantity 37-41 If RP1-3=BSS 

RP 37-41 <> “000000” 

QTY01=YW 

QTY02 = RP 37-41 
2 of 2 

ADC 308 

Enclosure 3 

Field Name DI Code BSS

Record Position 

Conditions DLMS Data Element 

Requisitioning Objective 

quantity 

43-48 If RP1-3=BSS QTY01 =XV 

QTY02=RP 43-48 

Safety Level/Retention Limit 

quantity 

49-54 If RP1-3=BSS QTY01=XY 

QTY02=RP 49-54 

Owning Inventory Control 

Point 

4-6 If RP1-3=BSS N101=Z4 

N103=M4 

N104=RP 4-6 

N106=TO 

Storage Site 58-60 If RP1-3 = BSS N101=LG 

N103=M4 

N104=RP 58-60 

Number Of Included 

Segments 

None None SE01=Total Number Of Segments 

Serial Number None Must Equal ST02 SE02=Serial Number