ADC 355 

Attachment 

Page 1 of 3 

ATTACHMENT TO ADC 355 

Revise DS 846I Asset Status Inquiry/Report to Address Intra-Navy Use of Transaction 

Preparation Date in Multiuse Field of MILSTRAP DZA Transaction (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 inventory balances to 

inventory manager. 

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

 (1) The format for MILSTRAP Document Identifier (DI) Code DZA, Asset Status, 

provides for intra-Component data in various record positions (rp) designated as “multiuse”. 

Components must identify to DLMSO the intra-Component MILSTRAP DZA data entered in 

these multiuse fields which is required under DLMS. Once identified, DLMSO can incorporate 

the data in DLMS 846I and DAASC mapping can be updated to reflect the requirement. 

 (2) Legacy Navy systems report their balances to the Inventory Control Point (ICP) using 

DZA transactions. These transactions allow the NAVICP to keep track of the inventory balances for 

these items. Navy cites a transaction preparation date (or as of date) in the DZA multiuse field at rp 

73-75. The Navy uses the date associated with the inventory report to determine the most current 

asset posture when more than one asset report is received within the same cycle. 

 (3) Administrative changes from PDC 390 to capture Navy use of DZA multiuse field in 

the MILSTRAP manual are highlighted in yellow in this ADC.

4. PROPOSED CHANGE(S): 

a. Revise DS 846I, Inventory Inquiry/Advice, as shown in Change Table Below: 

Item # Location DS 846I Revision Reason 
ADC 355 

Att

Page 2 of 3

Item # Location DS 846I Revision Reason 

1. DLMS 

Introductory 

Note 6 

Add ADC 355 to DLMS Introductory note 6:

- ADC 355, Revise DS 846I, Asset Status 

Inquiry/Report to Address Intra-Navy Use of 

Transaction Preparation Date in Multiuse Field of 

MILSTRAP DZA Transaction (Supply) 

To identify PDC/ADC in 

the DS. 

2. 2/DTM01/100 Add new DLMS note 3 to existing qualifier 600:

600 As Of 

DLMS Note: 3. Navy uses this date to determine the 

most current asset posture when more than one asset 

report is received within the same cycle. This equates 

to Navy prescribed data in MILSTRAP DZA multiuse 

field, rp 73-75. Refer to ADC 355.

To add Navy usage of 

qualifier. 

b. Proposed procedures: Navy cites the transaction preparation date in DZA intra-Component 

multiuse field rp 73-75. Navy requests this date be mapped to the DLMS 846I, DTM01 qualifier 

‘600-As Of’ date. Revise DAASC MILS to DLMS mapping to add if RP4=N, P, Q, R, or V then 

DTM01=600, DTM02=RP 73-75. No change to the procedures in DOD 4000.25-2-M, Volume 2. 

c. Revise DOD 4000.25-2-M, MILSTRAP, as revised by ADC 250, as follows (change is 

identified by red, bold, italics:

DZA FIELD LEGEND RECORD POSITION ENTRY AND INSTRUCTIONS 

Multiuse 72-80 

For intra-Component use, enter data 

prescribed by the Component. For inter 

Component use, leave blank. 

For Army, The following Component-unique 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. 

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. 

 d. Alternatives: 

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

 2) Change multiple legacy Navy systems to output 846I DLMS transactions. 
ADC 355 

Att

Page 2 of 3

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

programmed to be DLMS compliant. The legacy systems DI Code DZA data reflected in 

intra-Component multiuse field needs to be mapped to the 846I Asset Status Inquiry/Report 

transaction. 

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. 

8. IMPACT: 

a. DOD 4000.25-M, DLMS 846I. 

b. DAASC mapping. DAASC translate Navy generated DI Code DZA transactions (rp 

73-75) transactions to DLMS 846I DTM01 qualifier ‘600-As of’ when sending them to a 

DLMS compliant Navy system. 

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: None.