1 of 4 Attachment, ADC 458

ATTACHMENT TO ADC 458

Documentation of Intra-Army Use of Army Data Elements for MILSTRAP DZA and DLMS 846I 

Asset Status Transactions (Supply/MILSTRAP)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION

a. Technical POC: LOGSA Contractor, EDI Support, DSN 256.645.9754, Commercial 256-

955-9754

b. Functional POC: USAMC LOGSA, Soldier Support Center, DSN 256-645-9788, 

Commercial 256-955-9788

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, www.dla.mil/j-6/dlmso/eLibrary/Changes/approved3.asp

b. DLMSO Memorandum, January 12, 2009 , subject: Approved DLMS Change (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), www.dla.mil/j-6/dlmso/eLibrary/Changes/approved4.asp)

4. BACKGROUND:

a. Intent of the transaction: The MILSTRAP Document Identifier Code (DIC) DZA Asset 

Status transaction will be used between Army and other Military Services or within the Army in 

decentralized distribution systems, to transmit asset status data from the accountable stock control 

activities to the non-accountable activities. The DZA Asset Status transaction maps to DLMS 

Supplement (DS) 846I. Army seeks to implement additional data mapping to 846I to add value for 

Army.

 b. Scenario for which the transaction is used: Assets within the wholesale distribution 

system are reported in accordance with DOD 4000-25-M, Volume 2, Chapter 5. DLMS 846I, Asset 

Status transactions, may be used between DOD Components by mutual agreement. Asset status 

transactions are transmitted between DOD Components based on schedules established by mutual 

agreement.

 c. Procedures, transactions, data elements, processing details in use today: The 

MILSTRAP legacy DIC DZA format allots a significant portion of the format to “multiuse” fields 

that provide for Intra-Component data. Army’s implementation has a DZA format that allows for 

reporting of Requirements Objective, Safety level, Location of Goods, Project Code, and 

Stockage List Code, in the multi-use fields. With the exception of Project Code and Stockage 
2 of 4 Attachment, ADC 458

List Code, this data was previously documented for DZA and 846I by ADC 250 (reference 3b). 

This is consistent with DOD 4000.25-2-M, MILSTRAP, Chapter 8, Paragraph C8.2.1. as revised 

by ADC 250, which states that: 

“DoD Components must identify to the DLMS office any Component prescribed data in DIC

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

Logistics Management System (DLMS) transactions. This is necessary so that the DLMS 

office can incorporate the Component data in the DLMS Supplement (DS) 846I Asset Status

transaction. DS 846I is available for Component review to ascertain data content at:

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

5. REQUESTED CHANGE(S):

a. Requested change in detail: Army requests that the MILSTRAP DIC DZA format multiuse

fields be updated to reflect Amy’s use of Stockage List Code and Project Code; and that DLA Transaction 

Services mapping between MILSTRAP legacy DZA and DLMS 846I be updated accordingly. Stockage 

List Code and Project Code have been added previously to 846I to support Army unique DIC BSS (refer 

to ADC 308 (reference 3b)). 

1) Stockage List Code identifies the type of stocking requirements, for the materiel and 

Single Stock Fund (SSF) site, and is used to identify stocking criteria and review requirements for 

items on the Authorized Stockage List. The publication source for Stockage List Code is Army 

Regulation (AR) 710-2, Supply Policy Below the National Level. 

2) Project Code is used to identify requisitions, related documents, and shipments of 

materiel for specific projects, programs, or maneuvers. It identifies specific programs to provide 

funding and costing at the requisitioner or supplier level, to satisfy program costs and analysis, 

including an indicator of transactions within or outside of the federal government.

b. Army requests that Defense Automated Addressing System (DAAS) mapping for DS 846I 

DZA transaction, Asset Status Report, be modified to include:

1) For Army use of DIC DZA transaction, Project Code, record position (rp) 55-57 

mapped to LQ01=78, LQ02=rp55-57.

2) For Army use of DIC DZA transaction, Stockage List Code, rp 78, mapped to LQ01=SLC,

LQ02=rp78.

c. MILSTRAP Procedure: Update DOD 4000.25-2-M, MILSTRAP Appendix 3.56, DIC DZA, 

Asset Status, as shown in the enclosure.

d. Update DLMs Supplement 846I as shown below:

# Location DS 846I Asset Status Inquiry/ Report

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 458 to DLMS Introductory Note 6:

- ADC 458, Documentation of Intra-Army Use of Army Data Elements 

for MILSTRAP DZA and DLMS 846I Asset Status Transactions 

(Supply/MILSTRAP)

Identifies DLMS 

Changes included in 

the DS.
3 of 4 Attachment, ADC 458

# Location DS 846I Asset Status Inquiry/ Report

Revision

Reason

2. 2/LQ01/376

Add new DLMS note 3:

78 Project Code

DLMS Note: 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 DIC BSS, rp 55-57.) 

See Refer to ADC 308.

3. For intra-Army use to identify the Project Code associated with Asset 

Status Reports. Associated with Army use of MILSTRAP legacy DZA, 

rp 55-57. Refer to ADC 458.

Supports intra-Army 

requirement.

3. 2/LQ01/376

Revise DLMS note 1:

SLC Stockage List Code

DLMS Note: 1. For intra-Army use only. This is the Army Stockage List 

Code. See introductory DLMS note 4f. Use of this data is meaningful to 

Army only and equates to intra-Army DIC BSS, rp 78, and MILSTRAP 

legacy DZA, rp 78. The code source for Stockage List Code is Army 

Regulation 710-2, Supply Policy Below the National Level. See Refer to

ADC 308 and ADC 458.

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".

Supports intra-Army 

requirement.

 e. Alternatives: None Known.

6. REASON FOR CHANGE: Documents and incorporates Stockage List Code and Project Code 

into the Army use DIC DZA data requirements in DLMS. The data provides value-added information 

for Army.

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages (tangible/intangible) Supports Army implementation of DLMS migration effort 

by incorporating additional Army required data elements into DIC DZA (Asset Status Report).

b. Disadvantages: None known

8. ESTIMATED IMPLEMENTATION TARGET: Army identified a target implementation 

date as 90 days from the date of this ADC. 

9. IMPACT:

a. Automated Information Systems (AIS):

1) Army systems: Intra-Army use of data. See paragraph 8 for Army’s target implementation 

date.
4 of 4 Attachment, ADC 458

2) Defense Automatic Addressing System (DAAS) Mapping: Requires that DLA 

Transaction Services update DAAS mapping. Army proposes mapping as follows for intra-Army

DIC DZA:

Field Name Army use of 

DIC DZA rp

Conditions DLMS Data Element

Project Code 55-57 IF rp1-3 = DZA LQ01=78

LQ02=rp55-57

Stockage List 

Code

78 IF rp1-3 = DZA LQ01=SLC

LQ02=rp78

3) DOD Component systems should ensure that inclusion of the data described in this change 

for DLMS 846I does not cause inappropriate rejection of the transaction. 

b. New DLMS Data Elements: None. 

c. Changes to DLMS Data Elements: None.

d. Publications: DOD 4000.25-2-M, MILSTRAP and DOD 4000-25-M, DLMS. 

10. PDC 498 RESPONSES:

# Organization Response

1 Army Concur.

2 Air Force Concurs without comment.

3 USTRANSCOM Abstains.

4 DLA Concurs as written.

Enclosure
1 of 2 Enclosure, ADC 458

Enclosure to ADC 458

Request Documentation of Intra-Army Use of Army Data Elements for MILSTRAP DZA and DLMS 

846I Asset Status Transactions (Supply/MILSTRAP)

Revise AP 3.56 as revised by ADC 250, as shown in highlighted bold, red italics.

AP3.56. APPENDIX 3.56

ASSET STATUS

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DIC DZA.

Routing Identifier (TO) 4-6 Enter RI code of the ICP to which this transaction 

is being forwarded.

Card Overflow 7 Enter codes A through Z (Except I and O) when 

any quantity exceeds the number of digits allotted.

Stock or Part Number 8-22 Enter stock or part number of item reported.

Unit of Issue 23-24 Enter UI of item.

Quantity (On hand) 25-30 Enter quantity of the item on hand, preceding 

significant digits with zeros.

Quantity (Due-In) 31-36 Enter quantity of the item due-in, preceding 

significant digits with zeros.

Quantity (Backordered) 37-41 Enter quantity of the item on backorder, preceding 

significant digits with zeros.

Multi-use 42-66 When used between Components, leave blank. 

When used within a Component, enter data 

prescribed by that Component. See rows below for 

specific Component use.

For Army, the following data is entered in rp 43-64 of the multi-use field1.

Quantity (Requirements 

Objective

43-48 Army enters requirements objective established 

for purpose code in rp 70.

Quantity (Safety Level) 49-54 Army enters quantity that reflects the safety level 

requirement.

Project Code 55-57 Army enters project code.

Routing Identifier 

(Storage Activity)

58-60 Army enters code of storage activity at which 

item is stored if different from activity preparing 

this transaction (FROM RI Code, rp 67-69).

 1 Refer to ADC 250.
2 of 2 Enclosure, ADC 458

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Date (Transaction 

Preparation)

61-64 Army enters Julian date of asset status (date on 

which transaction was prepared).

Routing Identifier 

(FROM)

67-69 Enter RI code of the ICP preparing the 

transaction.2

Ownership/Purpose 70 When used between Components, enter ownership 

code of the item. When used within a Component, 

enter purpose code of the item.

Supply Condition 71 Enter supply condition code of the item.

Multiuse 72-80 For intra-Component use, enter data prescribed by 

the Component. For inter-Component use, leave 

blank. See rows below for specific Component 

use.

The following DoD Component data is identified for rp 72-77 multiuse field:

Time 72-77 Army enters time of transaction preparation in 

HHMMSS Format expressed in universal time 

coordinate. Refer to ADC 250.

Date (Transaction 

Preparation)

73-75 Navy enters transaction preparation date. Navy 

uses this date to determine the most current asset 

posture when more than one asset report is 

received within the same cycle. Refer to ADC 

355.

Stockage List Code 78 Army enters the Stockage List Code. This is an 

intra-Army code and use of this data is 

meaningful to Army only. Refer to ADC 458.

 2 For Army/DLA interface, based upon mutual agreement, a DLA storage activity may prepare the DZA on behalf of the 

DLA ICP. The DLA ICP RI Code SMS appears in rp 67-69. (Refer to ADC 250.)