1 of 2 

ADC 270 

Attachment 

ATTACHMENT TO ADC 270 

Administrative Revision to DLMS Supplement (DS) 846P to Clarify Date Qualifiers in 

Transaction History Requests (Supply/MILSTRAP) 

1. ORIGINATOR:

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO) 

b. Originator: Ms. Mary Jane Johnson, DLMSO, MILSTRAP Administrator, e-mail: 

Mary.Jane.Johnson@dla.mil; (703) 767-0677; and, DSN 427-0677.

2. FUNCTIONAL AREA: Supply/MILSTRAP 

3. REFERENCE: DoD 4000.25-2-M, Military Standard Transaction Reporting and 

Accounting Procedures (MILSTRAP), available at: 

http://www.dla.mil/j-6/dlmso/elibrary/Manuals/MILSTRAP/default.asp. 

4. REQUESTED CHANGE:

a. Title: ADC 270, Administrative Revision to DLMS Supplement (DS) 846P to 

Clarify Date Qualifiers in Transaction History Requests (Supply/MILSTRAP) 

b. Description of Change: Administrative update to revise DLMS Supplement 846P, Physical 

Inventory Request. Transaction to clarify use of the transaction history request report start and end dates 

c. Procedures: Revise DLMS 846P DS as follows: 

Item 

# 

Location Revision to DS 846P 

Physical Inventory Request 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Notes 

Added new DLMS Introductory note 5: 

- ADC 270, Administrative Revision to DLMS 

Supplement (DS) 846P to Clarify Date Qualifiers in 

Transaction History Requests (Supply/MILSTRAP) 

To identify 

changes in 

the DLMS 

Supplements 

No changes 

required 

2. 2/DTM01/100 Revise DLMS note for 090-Report Start code to read: 

090 Report Start 

DLMS Note: Use in transaction history requests to 

identify the transaction history reporting start date. 

(Report start date equates to MILSTRAP DI Code 

DZJ rp 25-28 transaction history start date.) 

To clarify 

intent of 

“report start” 

date for 

transaction 

history 

requests. 

No changes 

required 

3. 2/DTM01/100 Revise DLMS note for 091-Report End code to read: 

091 Report End 

DLMS Note: Use in transaction history requests to 

identify the transaction history reporting end date. 

(Report end date is a date equivalent for MILSTRAP 

DI Code DZJ rp 29-31 which is the total number of 

prior days transaction history required. Accordingly, 

the report end date will precede the report start date.) 

To clarify 

intent of 

“report end” 

date for 

transaction 

history 

requests. 

No changes 

required 
2 of 2 

ADC 270 

Attachment 

5. REASON FOR CHANGE: There has been some confusion expressed over how the 

report start and report end dates for DS 846P transaction history requests are intended to be used. 

This change clarifies use of the date qualifiers, and explains how they were derived from the 

corresponding DOD 4000.25-2-M, MILSTRAP, transaction history request transaction 

(MILSTRAP Appendix AP 3.64, Document Identifier Code DZJ). 

6. ADVANTAGES AND DISADVANTAGES:

 a. Advantages: Clarifies how the DS 846P ‘report start’ and ‘report end’ dates are 

intended to be used for DLMS transaction history requests. 

b. Disadvantages: None Identified 

7. IMPACT: Modifies DS 846P Physical Inventory Request with administrative update to 

DLMS notes in DTM segment, DTM01: 

090 Report Start 

DLMS Note:

Use in transaction history requests to identify the transaction history reporting start date. 

(Report start date equates to MILSTRAP DI Code DZJ rp 25-28 transaction history start date.) 

091 Report End 

DLMS Note:

Use in transaction history requests to identify the transaction history reporting end date. 

(Report end date is a date equivalent for MILSTRAP DI Code DZJ rp 29-31, which is the total 

number of prior days transaction history required. Accordingly, the report end date will 

precede the report start date.)