1 of 12 

ADC 250 

Attachment 

ATTACHMENT TO ADC 250 

Revise DLMS Supplement 846I and MILSTRAP DZA Asset Status Transactions to 

Support Army Distribution Operations, and Revise DS 846I for Administrative 

Updates (Supply) (Staffed by PDC 270) 

1. ORIGINATOR: 

a. Service/Agency: Army Headquarters, United States Army Material Command 

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

2. FUNCTIONAL AREA: Supply 

3. COMMENTS RECEIVED FOR PDC 270: 

Component COMMENT 

DLA DLA concurs. DLA DDKS has the capability to transmit the 846I/DZA transaction upon 

approval. All programming has been completed and tested at DDKS. 

DAASC DAASC can implement this change within a week of approval. 

Army a. Army (National Level Supply Management Business Area) concurs to PDC 270. 

b. NLT October 2007, Army (LSSO) expects to have CCSS ready to accept/implement 

the changes required by PDC 270. 

Subsequent comment: 

Army Implementation date based on the funding issue currently being resolved at AMC 

Headquarters. Implementation date may need to be revised. 

c. At this time, RI Code AJ2 is not part of the LMP plan; therefore, there is no 

anticipated DLMS implementation date or timeframe. 

4. REQUESTED CHANGE: 

 a. Title: 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 and for Administrative Updates 

 b. Description of Change: 

(1) Revises DS 846I transaction preparation date at 2/DTM01/100 qualifier 600 (As Of) to 

specify that the date is in Universal Time Coordinate (UTC). This change may impact systems that 

have already implemented DS 846I. See the subparagraph 3.d(3) Change Table, row 3. 

(2) Incorporate DS 846I changes to support Army requirements for Asset Status 

Report and the corresponding Defense Logistics Standard System (DLSS) (aka MILS) 

MILSTRAP Document Identifier (DI) Code DZA Asset Status transaction, to accommodate

recording the on hand quantity of assets being held in the DLA ownership Routing Identifier 

(RI) Code SMS (Defense Logistics Agency) at RI Code S5F (DDKS, Defense Distribution 

Depot Kuwait) to support an Army requirement. Currently MILSTRAP addresses the flow 
2 of 12 

ADC 250 

Attachment 

of DZA asset status transactions between ICPs. This change expands concept for use 

between DLA DDKS and Army TACOM-Rock Island, by mutual agreement. This provides 

a systematic means for the DLA DDKS to provide the Army ICP information on DLA ICP 

(SMS) assets stored at the depot. DLA is operating in DLMS and will use DS 846I, while 

Army is currently operating in DLSS using DI Code DZA. 

a) Add 2/QTY01/320 Qualifier RY (Requirement Quantity) to identify the 

“Requirements Objective” which corresponds to Army unique use of DZA multiuse rp 43-48.

b) Utilize the existing DLMS Qualifier 2/QTY01/320 = XY (Safety Level)

to identify the safety level quantity for the requirements, which corresponds to Army unique 

use of DZA multiuse rp 49–54. 

c) Utilize the existing DLMS Qualifier 2/N101/450 = LG (Location of Goods)

to identify the activity at which the item is stored if different from the activity preparing the 

transaction, which corresponds to Army unique use of DZA multiuse rp 58–60. For these 

transactions, the value would be RI Code S5F (DDKS). 

d) Utilize the existing DLMS Qualifier 2/DTM01/100 code 600 (As Of), for 

transaction preparation date, which corresponds to Army use of DZA multiuse rp 61–64. 

e) Open DS 846I Qualifier 2/DTM03-04/100 to identify the time and specify 

that time is expressed in Universal Time Coordinate (UTC) in HHMMSS format. Used to 

identify the most current asset posture for assets stored under DLA/SMS ownership and will 

allow the Army system to process the correct balance when more than one DZA with the same 

data is received within the same cycle. Corresponds to Army use of DZA multiuse rp 72–77 for 

time. 

(3) This change also incorporates DLMS administrative updates in DS 846I 

which are not specific to the Army/DLA requirement. These administrative changes 

include, but are not limited to, limiting the lot/batch number and unique item identifier (UII) 

field lengths in accordance with unique identification (UID) policy. See the UID Web site 

for most current UID policy and guidance at http://www.acq.osd.mil/dpap/UID/.

 c. Background: Army provides the following procedures for the requisitioning of materials to 

support Army Central Command (CENTCOM) operations [STAFFING NOTE: During a June 28, 

2007, telecon between DLMSO and Army, to include the Army SPRC representative, Army recommended 

that the MILSTRAP/DLMS transaction notes for this change not be specific to CENTCOM and DDKS, as 

Army may want more widespread use of DZA/846I in this manner in the future. Accordingly, the notes 

added to DZA and 846I by PDC 270 were generic for Army/DLA use. However the only DLA depot 

affected by ADC 250 is DDKS (see impact paragraph 6.e) Further a specific note is being added to DS 

846I by this change to address the unique DDKS processing to accommodate Army’s MILSTRAP DZA 

mapping requirement is only intended for DDKS. Should this concept be extended to DSS at some point in 

the future, the alternative identified at para 3.e. will be strongly considered in lieu of unique DLMS 

processing:

(1) Requisitions being submitted from CENTCOM Units (Southwest Asia Theatre) 

that are identified as Afghanistan (AF), Kuwait (KU) Iraq (IQ), Qatar (QU), Djibouti (DJ) 

and Egypt (EG) are labeled with a country code designator in CCSS. 
3 of 12 

ADC 250 

Attachment 

(2) When a requisition is received by RI Code AJ2 (TACOM Rock Island) and 

identified by CCSS with a country code of AF, KU, IQ, QU, DJ and EG the search pattern 

will reflect the below pattern: 

 

(a) RI Code AJ2 owned assets at RI Code W7A (Camp Arifjan, Kuwait) until closed 

(b) RI Code AJ2 owned assets at RI Code S5F (DDKS) 

(c) Check DDKS asset posture for DLA-owned assets. If available, send to RI Code 

SMS (DLA ICP within CONUS). If not available the current process would continue to search Germany 

sites, then National Source of Supply and off-installation/out-of-theater sites. 

(d) Pass to National Level Source of Supply. 

(3) When there are not sufficient assets on hand for RI Code AJ2 ownership being 

reported from S5F or W7A the following logic will apply: 

The DS 846I asset status transaction will be produced by DDKS (RI Code S5F) on behalf 

of DLA ICP RI Code SMS. As an interim measure in a mixed DLSS/DLMS environment, 

when DDKS creates 846I, SMS will appear as the 846I transaction originator (Message 

From) and map to DI Code DZA transaction preparer in rp 67-69, to accommodate an 

Army requirement that the owning ICP appear in the DZA field designated as 

transaction preparer. DDKS will prepare DS 846I and forward via DAASC to RI Code AJ2 

whenever the SMS balance at S5F has been affected, which may result in multiple asset status 

transactions (846I/DZA) in the same cycle. DAASC will convert DS 846I to MILS DI Code 

DZA until such time as Army RI Code AJ2 is DLMS compliant. The 846I/DZA transactions 

will require a time stamp so that Army CCSS can ensure that the latest/current balance is the 

recorded asset posture. 

(4) Upon recording the asset balance for RI Code AJ2, incoming requisitions that 

have been identified as being within the theatre of operation will access this information if 

the total quantity could not be filled out of the Army storage sites. The quantity remaining on 

the requisition (may also be the full quantity requested) will be matched against the quantity 

on hand at S5F for assets reflected in the SMS account. When the SMS quantity is equal to 

or greater than the amount remaining on the requisition the requisition will be passed to SMS 

for filling out of S5F. When the asset posture at S5F for SMS managed items is less than the 

quantity remaining on the requisition the requisition will continue the current search pattern 

and the priority and dollar value rules will apply as currently coded in the Army Commodity 

Command Standard System (CCSS) for Non-Army Managed Items (NAMI). 

(5) When it is determined to directly pass the requisition to RI Code SMS for 

filling within theatre Army requirements the passing logic currently designed will apply 

(i.e., replenishments will be funded by NAMI and the requisition will be modified prior 

to passing with NAMI data, etc.). 

 d. Procedures: 

(1) Revise DOD 4000.25-M, DLMS, Volume 2, Chapter 5, paragraph C5.1.1 as 

follows (change is identified by red, bold italics): 
4 of 12 

ADC 250 

Attachment 

“C5.1.1. In Storage Assets. 

C5.1.1.1. Asset within the wholesale distribution system are reported in accordance with 

this volume. DS to Federal IC 846I asset status transactions may be used between Components 

by mutual agreement. Transmit asset status transactions between Components based on 

schedules established by mutual agreement. 

 C5.1.1.2. Assets below the wholesale distribution system shall be reported when 

requested by the owner/manager. Use DS to Federal IC 846I, Asset Status Inquiry/Report, 

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

from the below wholesale distribution system.” 

(2) Revise DOD 4000.25-2-M, MILSTRAP, Chapter 8, section C8.2 as follows 

(change is identified by red, bold italics): 

“C8.2. ASSETS WITHIN THE DISTRIBUTION SYSTEM 

 C8.2.1. Prepare DI Code DZA asset status transactions as outlined in appendix 

AP3.56. Due to the number of record positions devoted to entries prescribed by the 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 

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

DLMSO 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: 

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

[Note: Army, see DLMSO staffing note at Enclosure 1] 

 C8.2.2. Asset status transactions may be used between a Service ICP and a 

DLA storage activity by mutual agreement. 

 C8.2.3. Transmit asset status transactions between Components based on 

schedules established by mutual agreement.” 

(3) Revise DS 846I as shown in Change Table below (change from PDC 270 is 

highlighted in blue at row 2) [NOTE: administrative changes are shown separately in the 846I 

table at subparagraph (4)]: 

 

Item # Location 846I Change Table 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note 6. 

Added ADC 250 to DLMS Introductory 

note 6.

- ADC 250, Revise DLMS Supplement 846I 

and MILSTRAP DZA Asset Status 

Transactions to Support Army Distribution 

Operations, and revise DS 846I for Use of 

Universal Time Coordinate and for 

Administrative Updates. 

To identify DLMS changes 

included in the DS. 

No 

update 

required. 
5 of 12 

ADC 250 

Attachment 

Item # Location 846I Change Table 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

2. 1/N106/080 Add DLMS note to FR-Message From:

FR Message From 

DLMS Note: For Army/DLA DDKS 

interface in a mixed DLSS/DLMS 

environment, based upon agreement, the 

DLA storage activity may prepare the 846I 

on behalf of the DLA ICP, with the DLA 

ICP RI Code SMS entered as the ‘Message 

From’ activity originating the transaction. 

This is an interim DDKS approach in the 

mixed DLMS/DLSS environment to 

accommodate Army’s requirement for the 

owning ICP to map to the DLSS DI Code 

DZA rp 67-69, which is identified as the RI 

Code of the ICP preparing the transaction. 

As Army transitions to DLMS, the 

1/N106/080 FR should reflect the true 

activity preparing the transaction set, and 

the appropriate qualifier for storage activity 

or ICP preparing the transaction should be 

used. The information on the owning ICP 

or storage activity, when not the activity 

originating the transaction set, should 

appear in 2/N101/450. See ADC 250. 

Any future DLA Distribution Standard 

System (DSS) implementation should 

consider the alternative approach 

documented in ADC 250. 

To document unique Army/DLA 

interface requirement in a mixed 

DLMS/DLSS environment where the 

DLA storage activity prepares the 

846I for Army on behalf of the DLA 

ICP, but the DLA ICP RI Code SMS 

appears as the ‘Message From’ 

activity preparing the transaction set. 

Use of the 1/N1/080 in this manner is 

an interim approach in a mixed 

DLSS/DLMS environment to 

accommodate an Army DLSS 

requirement until Army transitions to 

DLMS. In a full DLMS 

environment, where translation to 

DLSS DZA is not required, 

2/N101/450/KA would be used in the 

scenario addressed by this PDC to 

identify RI Code SMS; the DDKS RI 

Code S5F would be entered in 

1/N101/080/ SB with N106/FR; 

TACOM RI Code AJ2 would be 

entered in 2/N101/450/Z4 with 

N106/TO. 

SEE ALTERNATIVE at 

subparagraph 3.e. 

No update 

required. 

3. 2/DTM01/100 For existing qualifier 600, revise note 1 and 

add new DLMS Note 2.

600 As Of 

DLMS Notes: 1.Use for asset status 

reports to identify the date associated with 

the inventory information (date transaction 

was prepared). Express this date in 

Universal Time Coordinate.

2. Used between the Army and DLA to 

determine the most current asset posture for 

assets stored under DLA/SMS ownership 

when more than one asset report is received 

within the same cycle. 

To document Army/DLA interface 

requirement. 

To document providing the ‘As Of’ 

date in UTC. 

The UTC is used almost universally 

to designate date/time information 

that is time sensitive and requires 

identification to a specific time zone 

for pin-pointing actual time in other 

time zones. 

Use of UTC will impact any system 

which has already implemented DS 

846I and did not use UTC. 

No 

updated 

required. 
6 of 12 

ADC 250 

Attachment 

Item # Location 846I Change Table 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

4. 2/DTM03/100 Open DTM03 Time with DLMS notes:

DLMS Notes: 1. Use in conjunction with 

DTM01 code 600 only to identify the time 

the transaction was prepared. 

2. Express time in a six-position 

(HHMMSS) format in UTC. 

3. DLMS enhancement. See introductory 

DLMS note 4.a. 

4. Used between the Army and DLA to 

determine the most current asset posture for 

assets stored under DLA/SMS ownership 

when more than one asset report is received 

within the same cycle. 

To provide the time the transaction 

was prepared. 

The UTC is used almost universally 

to designate date/time information 

that is time sensitive and requires 

identification to a specific time zone 

for pin-pointing actual time in other 

time zones. 

Revision 

required. 

5. 2/DTM04/100 Open DTM04 Time Code with qualifier 

‘UT’: 

UT Universal Time Coordinate 

To identify time is expressed in 

UTC. 

Revision 

required. 

6. 2/REF01/140 Add new qualifier W8-Suffix with DLMS 

note:

W8 Suffix 

DLMS note: Used in a mixed DLMS/ 

DLSS environment for asset status reports 

to accommodate conversion to DLSS 

when quantities exceed allowable DLSS 

positions. Equates to MILSTRAP DI 

Code DZA record position 7. Enter A 

through Z (except I and O). Future 

streamlined data which will be eliminated 

in a full DLMS environment when the 

expanded quantity field size is used.

Provides for MILSTRAP DI Code 

DZA record position 7 entry in a 

mixed DLSS/ DLMS environment. 

The rp 7 requirement was initially 

omitted from DS 846I by intent, 

when developed, in anticipation of 

using the expanded quantity field 

size under DLMS. However when 

interfacing with DLSS, use of the 

expanded quantity field size could 

not be converted to the DLSS 

transaction if greater than the 

allowable DLSS field size. 

Accordingly this code is being added 

for use in DLMS while in a mixed 

DLSS/DLMS environment. 

No update 

required. 

7. 2/QTY01/320 Add new qualifier ‘RY-Requirements 

Quantity’ with DLMS Note: 

RY Requirements Quantity 

DLMS note: 1. DLMS enhancement. See 

introductory DLMS note 4.a

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

3.. Also used between Army and DLA. If 

none, or agreement does not require data, 

then zero fill. 

To document Army DLSS DZA use 

of requirements objective in DS 846I, 

and to document Army/ DLA 

interface requirement. 

No update 

required. 
7 of 12 

ADC 250 

Attachment 

Item # Location 846I Change Table 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

8. 2/QTY01/320 Added the following DLMS Note 2 for 

existing qualifier XY

XY Safety Level 

DLMS Note 2: Army uses to identify the 

safety level requirement. This equates to 

Army prescribed data in MILSTRAP DZA 

multiuse field, rp 49-54. 

3.. Also used between Army and DLA. If 

none, or agreement does not require data, 

then zero fill. 

To document Army DLSS DZA use 

of safety level in DS 846I, and to 

document Army/DLA interface 

requirement 

No update 

required. 

9. 2/QTY02/320 Revise DLMS note for quantity:

DLMS Note: A field size exceeding 6 

positions for QTY01 qualifiers 17, BA, 

XU, XV, and XY (eight positions for 

FSG 13 ammunition); and 5 positions 

for QTY01 qualifier BQ (seven 

positions for FSG 13) , may not be 

received or understood by recipients 

automated processing system. See 

introductory DLMS note 4.d. 

Original DLMS note addressed a 5 

position quantity field, however most 

MILSTRAP DZA/DZF quantity 

fields are 6 positions. 

Additionally there are quantity fields 

in DS 846I which are DLMS 

enhancements not subject to a 

corresponding DLSS field size. 

No update 

required. 

10. 2/N101/450 Add new qualifier KA-Item Manager with 

DLMS note, and revise existing Z4 note:

KA Item Manager 

DLMS Note: Use for asset status reports 

to identify the owning ICP when different 

from the 1/N101/080 organization 

originating the transaction set, and the 

2/N101/450/Z4 organization is not the 

owning ICP. 

Z4 Owning Inventory Control Point 

1. Use to indicate the owning inventory 

control point to which the transaction is 

being forwarded. 

2. Also used to identify the ICP to which 

the transaction is being forwarded when 

that activity is not the owning ICP. When 

the activity is not the owning ICP, then 

qualifier KA must also be used to identify 

the owning ICP.

To provide for identification of 

owning ICP when not the 

transaction originator or the 

2/N101/450/Z4 recipient. 

Qualifier Z4 was already existing 

in DS 846I as the TO address 

ICP. Added qualifier KA to 

accommodate an owning ICP 

when different than the TO ICP, 

as is required by this change. 

In a full DLMS environment, 

where translation to DLSS DZA 

is not required, 2/N101/450/KA 

would be used in the scenario 

addressed by this PDC to identify 

RI Code SMS; the DDKS RI 

Code S5F would be entered in 

1/N101/080/ SB with N106/FR; 

TACOM RI Code AJ2 would be 

entered in 2/N101/450/Z4 with 

N106/TO. 

No update 

required. 
8 of 12 

ADC 250 

Attachment 

(4) Administrative Changes. Revise DS 846I for administrative changes as shown below: 

Item # Location 846I Administrative Changes 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

Admin 

change 1 

DLMS 

Introductory 

Note 4. 

Revise DLMS introductory note 4 to add subparagraph e:

e. Data associated with a DLMS enhancement authorized 

for implementation by modernized systems under DLMS 

migration. This data (including expanded field sizes) 

should be adopted during, or subsequent to, modernization 

when applicable to the Component’s business process. 

Prior coordination is not required. Components should 

ensure that inclusion of this data in a DLMS transaction 

does not cause inappropriate rejection of the transaction. 

Administrative 

change to incorporate 

standard DLMS 

introductory note for 

authorized DLMS 

migration 

enhancements. 

No 

update 

required. 

Admin 

change 2 

2/REF01/140 Revise DLMS note for qualifier TN-Transaction Number:

TN Transaction Number 

DLMS note: Use to identify the transaction number. 

Authorized DLMS migration enhancement. See DLMS 

introductory note 4.e.

Administrative 

change to acknowledge 

that use of the 

transaction number 

(document number) is 

an authorized DLMS 

migration enhancement. 

Transaction number is 

used in all DLMS 

transactions. The 

corresponding 

MILSTRAP 

transactions (DI Codes 

DZA/DZE/ DZF) did 

not have a document 

number. 

No update 

required. 

Admin 

change 3 

2/LQ01/270 

and 

2/LQ01/376 

Update DLMS notes for qualifier A9 

A9 Supplemental Data

DLMS Notes: 

1. Use to identify supplemental address/data. 

2. During the DLSS/DLMS transition, this field will be 

used to perpetuate/populate the DLSS Supplemental 

Address (SUPAAD) field. During this time, field size is 

restricted to 6 positions; see introductory DLMS note 

4d. 

3. Expanded use of this field for supplemental data 

without size restriction is a DLMS enhancement; see 

introductory DLMS note 4a. 

4. Under full DLMS, the requirement to pass activity 

address information within the supplemental data field 

will be streamlined. Activity address data previously 

contained in the SUPAAD will be reflected exclusively 

in the N1 segment. Future streamlined data; see 

introductory DLMS note 4c. 

Administrative 

change for consistency 

with standard DLMS 

notes for qualifier A9. 

No update 

required. 
9 of 12 

ADC 250 

Attachment 

Item # Location 846I Administrative Changes 

Asset Status Inquiry/Report 

Reason Federal IC 

Impact 

Admin 

change 4

2/LQ01/270 

and 

2/LQ01/376 

Update qualifier GQ DLMS note for ANSI data 

maintenance, second paragraph, to reflect that a qualifier 

was approved for USAF MMAC in version 5010:

A data maintenance action was approved in version 

5010. The approved code/ name is "MAC –Material 

Management Aggregation Code". The code source is 

identified as the Air Force Manual (AFMAN) 23-110, 

Volumes 1 and 2.

Administrative 

change to acknowledge 

approved ANSI data 

maintenance request. 

No update 

required. 

Admin 

change 5 

2/REF01/390 Update qualifier BT DLMS Note 1 to limit batch/lot 

number field to 20 positions:

BT Batch Number 

DLMS Note 1. Use to identify the manufacturer's batch/lot 

number or other number identifying the production run 

when UII and/or serial number are not required. If UII 

and/or serial number are required in addition to the 

batch/lot number, enter the batch/lot number in REF04. 

The batch/lot number may not exceed 20 characters 

in accordance with IUID policy.

Administrative 

change to document 

maximum 20 position 

length for batch/lot 

IAW UID policy. UID 

PMO authorizes 20 

position maximum 

batch/lot size. 

No update 

required. 

Admin 

change 6 

2/REF01/390 U3 Unique Supplier Identification Number (USIN) 

DLMS Note: 1. Use to identify the UII Place UII value in 

REF03. The UII may not exceed 50 characters in 

accordance with IUID Policy. An ANSI data 

maintenance was approved in version 5020. The approved 

code/name is “UII-Department of Defense Unique Item 

Identifier”. 

2. Authorized DLMS migration enhancement. See DLMS 

introductory note 4.e. 

Administrative 

change to:

1) document maximum 

50 position length for 

UII IAW UID policy; 

2) identify UII as an 

authorized DLMS 

migration enhancement

No update 

required. 

Admin 

change 7 

2/REF04/390 

C040-first 

use of BT 

Update qualifier BT DLMS Note to limit batch/lot number 

field to 20 positions:

BT Batch Number 

DLMS Note 1. Use to identify the manufacturer's batch/lot 

number or other number identifying the production run 

when UII and/or serial number are not required. If UII or 

serial number is entered in REF0, and batch/lot is the only 

other identifying number. The batch/lot number may not 

exceed 20 characters in accordance with IUID policy. 

Administrative 

change to document 

maximum 20 position 

length for batch/lot 

number IAW UID 

policy. UID PMO 

authorizes 20 position 

maximum batch/lot 

size. 

No update 

required. 

Admin 

change 8 

2/REF04/390 

C040-second 

use of BT 

Update qualifier BT DLMS Note to limit batch/lot number 

field to 20 positions:

BT Batch Number 

DLMS Note 1. Use to identify the manufacturer's batch/lot 

number or other number identifying the production run 

when UII is entered in REF01 and serial number is entered 

in REF04-01. The batch/lot number may not exceed 20 

characters in accordance with IUID policy.

Administrative 

change to document 

maximum 20 position 

length for batch/lot 

number IAW UID 

policy. UID PMO 

authorizes 20 position 

maximum batch/lot 

size. 

No update 

required. 
10 of 12 

ADC 250 

Attachment 

(5) Revise DOD 4000.25-2-M, MILSTRAP, AP3.56, DI Code DZA, Asset Status, as 

follows (change identified by red, bold, italics): 

AP3.56 ASSET STATUS

DZA FIELD LEGEND

RECORD 

POSITION ENTRY AND INSTRUCTIONS

DS 846I mapping for new data. This column will not appear in MILSTRAP 

Document Identifier 1-3 Enter DI Code 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. 

Multiuse 42-66 When used between Components, leave blank. 

When used within a Component, enter data 

prescribed by that Component. 

 For Army, the following data is used in rp 42-64 multiuse field 1:

 Quantity (Requirements 

Objective) 

43-48 Army enters requirements objective established 

for purpose code in rp 70. 

2/QTY01/320 = RY 

2/QTY02/320 = qty

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

level requirement. 

2/QTY01/320 = XY 

2/QTY02/320 = qty

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

2/N101/450 = LG 

2/N103/450 = M4 

2/N104 = value

 Date (Transaction 

Preparation) 

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

which transaction was prepared). 

2/DTM01/100=600 

2/DTM02/100 = date 

 

1

 See ADC 250. 
11 of 12 

ADC 250 

Attachment 

DZA FIELD LEGEND

RECORD 

POSITION ENTRY AND INSTRUCTIONS

DS 846I mapping for new data. This column will not appear in MILSTRAP 

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. 

 For Army, the following data is used in rp 72-77 multiuse field:

 Time 72-77 Army enters time of transaction preparation in 

HHMMSS Format expressed in universal time 

coordinate. 

2/DTM03/100 = time 

(HHMMSS) 

2/DTM04/100 = UT 

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. (See ADC 250.)

 e. Alternative. The following alternative was not adopted for the ADC 250 Army-DLA 

DDKS interface implementation, but will be strongly considered for any future 

implementations involving the DLA Distribution Standard System (DSS). Army has indicated 

that TACOM Rock Island, IL (AJ2) is not part of the Army Logistics Modernization Program (LMP) 

at this time, therefore, there is no anticipated DLMS implementation date or timeframe for AJ2. This 

alternative would preclude the need for DSS unique DLMS 846I processing required to 

accommodate the Army DLSS requirement that DLA ICP SMS appear in DI Code DZA, rp 67-69, 

rather than the transaction preparer, when the transaction is prepared by the DLA depot: 

 In the 846I, identify the true organization originating the transaction set, which would be 

DDKS, in 1/N1/080 using: 1/N101/SB-Storage activity, with 1/N103/M4-RIC, 1/N104/S5F, and 

1N106/FR-Message From. 

 Identify SMS as the Owning ICP when different from the ICP the transaction is being 

sent to, in 2/N1/450 as 2/N101/KA, with 2/N103/M4-RIC, and 2/N104-SMS. 

 Identify the ICP the transaction is being sent to (AJ2), in 2/N1/450 as 2/N101/Z4, 

with 2/N103/M4-RIC, 2/N104-AJ2, and 2/N106/TO-Message To. 

In this alternative approach, when the 846I for DI Code DZA is created by the depot and sent 

to Army, DAASC would map the 2/N101/450/KA entry to DZA, rp 67-69 when the 846I/DZA 

is sent to AJ2. DAASC, would provide a DAASC solution for the Army’s MILS requirement 

that SMS map to the rp 67-69 of DZA when the depot prepares the transaction. This would 

preclude the need for DLA DSS reprogramming of the 846I process when Army becomes 

DLMS compliant and unique processing or mapping for conversion to the MILS DZA is no 

longer required. 
12 of 12 

ADC 250 

Attachment 

5. REASON FOR CHANGE: Documents and incorporates DLSS and DLMS requirements for 

Army and DLA support for CENTCOM distribution operations at DLA DDKS. Guidance is 

generic so that it is available for use if desired by mutual agreement beyond immediate Army 

CENTCOM/DDKS (see impact paragraph 6.e.). The data requirements identified by Army for 

inclusion in DS 846I, are used by Army in MILSTRAP DI Code DZA multiuse fields which allow 

for intra-Component use of Component unique data (see Enclosure 1 for Army unique data use in 

DI Code DZA, see Enclosure 2 for Army DZA format). Such data is not visible to DLMSO for 

incorporation in DLMS until such time as the requiring Component submits a PDC documenting 

the requirement. This change identifies the Army’s data requirement for inclusion in DLMS, and 

also identifies an inter-Component requirement for use of the data between Army and DLA DDKS. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports the Army Materiel Command (AMC) sourcing of requisitions repairs 

and returns to inventory to support unit readiness needs and support CENTCOM distribution 

operations to provide material to the warfighter in a timely manner. Also supports Army 

implementation of DLMS by identifying select Army prescribed MILSTRAP DZA asset status 

transaction data elements for inclusion in the corresponding DS 846I asset status transaction. 

 b. Disadvantages: None identified. 

7. IMPACT: 

a. DLMS/MILSTRAP. Requires revision to DS 846I, corresponding DLMS XML, 

MILSTRAP DI Code DZA, and DLMS/MILSTRAP procedures as noted by this change. 

b. DOD Component publications. May require update of Component publications 

implementing these changes. 

c. DAASC Maps. Requires update of DAASC maps and conversion processing. 

d. Automated Information Systems (AIS). Impacts DLA Defense Distribution 

Depot Kuwait/Southwest Asia (DDKS) and Army AIS to accommodate procedures 

and/or data requirements identified herein. The unique DS 846I processing identified for the 

transaction set ‘Message From’ organization, to accommodate the Army MILSTRAP DI Code DZA 

mapping requirement, will require modification when Army ICP RI Code AJ2 implements DLMS. 

e. Additional AIS Consideration: DDKS is a non-DLA Distribution Standard System (DSS) 

storage activity and any changes being made to accommodate this process at DDKS will not have 

any affect on DLA storage activity systems beyond DDKS. Expansion of DZA/846I usage between 

Army and DLA Defense Distribution Depots other than DDKS will require additional coordination 

and could take some time to develop and implement a DSS systems change request. DSS 

implementation cycles are semi-annual, it is unlikely that any requested changes could be completed 

in the near term. 

Enclosures 
ADC 250 

Enclosure 1 

ENCLOSURE 1 TO ADC 250 

Army Data Elements in DI Code DZA multiuse Fields 

Record Field Legend Entry and Instructions 

Position

42-66 Blank When used between components, leave 

 blank. When used within a component enter 

 the data prescribed by that component. 

For Army CENTCOM Operations Support rp 42-66 data: 

42 Reporting code Enter code 0 or 4 to indicate the type of 

 reporting being accomplished for SIMS-X. 

 **This would be blank**

43-48 Requirements objective Enter the RO quantity established for each 

 purpose code shown in rp 70. 

 **This would be zero filled** 

49-54 Safety level Enter the quantity that reflects the safety 

 level requirements. 

 **This would be zero filled**

55-57 Project code **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); 

 otherwise, leave blank. 

 **This should be S5F ** 

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

 prepared. 

65-66 Blank Leave blank. 

_____________________________________________________________________________ 

72-80 Multiuse For intra-component use, enter data 

 prescribed by the component. For inter- 

 Component use, leave blank. 

For Army CENTCOM Operations Support rp 72-80 multiuse data field: 

72-77 DODAAC Time Time that the transaction 

 was prepared in HHMMSS format. 

78 Stockage list code **Leave Blank**

79-80 Blank Leave blank. 

* DLMSO STAFFING NOTE FOR ARMY: Highlighted data indicates Army-unique DZA 

data which Army identified for mapping to DS 846I for use in Army modernized systems 

using DLMS. Army was to identify the Army prescribed DZA data (DZA multiuse fields) 

which Army will require under DLMS, by PDC 270. Army has not identified Army 

prescribed DZA data fields other than those highlighted above, for inclusion in DLMS 846I. 
ADC 250 

Enclosure 2 

ENCLOSURE 2 to ADC 250 

DI Code DZA (Asset Status) Format Provided by Army: 

Record 

Position Field Legend Explanation 

1-3 Document identifier code Enter DI Code DZA. 

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

**This would be AJ2**

7 Suffix code Enter codes A through Z (Except I and O) when any quantity exceeds the 

number of digits allotted, or different condition or purpose codes apply. 

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 Enter quantity of the item on hand for each purpose and condition code 

combination in rp 70 and 71. 

31-36 Due-in Enter quantity of the item due-in for each purpose and condition code 

combination in rp 70 and 71. **This would be zero filled**

37-41 Backorder Enter quantity of the item on backorder for each purpose and condition 

code combination in rp 70 and 71. **This would be zero filled**

42 Reporting code Enter code 0 or 4 to indicate the type of reporting being 

Accomplished for SIM-X. **This would be blank**

43-48 Requirements objective Enter the RO quantity established for each purpose code shown in rp 70. 

**This would be zero filled**

49-54 Safety level Enter the quantity that reflects the safety level requirements. 

**This would be zero filled**

55-57 Project code **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); otherwise, 

leave blank. **This should be S5F ** 

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. 

**This should be SMS **

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 DODAAC Time Enter the time DODAAC. **This should be HHMMSS*

78 Stockage list code **Leave Blank** 

79-80 Blank Leave blank.