ATTACHMENT TO ADC 212 

Revise DLMS Supplement 846R, Location Reconciliation Request to 

Accommodate MILSTRAP DZH Consecutive Transaction Number 

(Supply/MILSTRAP) (Staffed by PDC 311) 

1. ORIGINATOR: 

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

 

b. Originator: Ms. Mary Jane Johnson, DLMSO, MILSTRAP Administrator, 703-767-0677; 

DSN 427-0677; or, e-mail: Mary.Jane.Johnson@dla.mil. 

2. FUNCTIONAL AREA: Supply 

3. REQUESTED CHANGE: 

a. Title: Revise DLMS Supplement 846R, Location Reconciliation Request to 

Accommodate MILSTRAP DZH Consecutive Transaction Number 

b. Description of Change: 

(1) Add new qualifier to DS 846R, 2/ REF01/140 to accommodate the functionality 

of MILSTRAP Document Identifier (DI) Code DZH, record position (rp) 60-66, 

‘consecutive transaction number’. 

(2) Administrative update to identify that a ‘document number’ is a DLMS 

enhancement for location reconciliation requests and therefore requires a proposed DLMS 

change (PDC) to develop associated business rules for use. 

c. Procedures: Revise DS 846R for Location Reconciliation Request as follows:

Item # Location Revision to 

846R, Location Reconciliation Request 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note 

Added ADC 212 to Introductory note 6

- ADC 212, Revise DS 846R Location 

Reconciliation Request to Accommodate 

MILSTRAP DZH Consecutive Transaction 

Number 

To identify DLMS 

changes included in 

the DS 

No update 

needed. 

ADC 212 

Attachment 

1 of 4 
Item # Location Revision to 

846R, Location Reconciliation Request 

Reason Federal IC 

Impact 

2. 2/REF01/140 Add qualifier ‘FJ’ with DLMS note:

FJ Line Item Control Number 

DLMS Note: Used in a mixed 

DLSS/DLMS environment to provide the 

information conveyed by MILSTRAP DI 

Code DZH, rp 60-66 ‘consecutive 

transaction number’. This is a consecutive

number, beginning with 1 in the first 

transaction, to identify each transaction in 

the reconciliation. Used when each 846R is 

limited to being the equivalent of a single 

MILSTRAP DZH location reconciliation 

request. Future streamlined data; see 

introductory DLMS note 4c. See ADC 212. 

To add a qualifier 

for the DZH, rp 60-

66, ‘counter’ 

information for use 

in a mixed DLSSDLMS 

environment. 

No update 

needed. 

3. 2/REF01/140 Revise DLMS note for qualifier ‘TN’.

TN Transaction Reference Number 

 

DLMS Note: Use to identify the 

transaction number (also known as the 

document number). Use of transaction 

number (document number), with location 

reconciliation transactions, is a DLMS 

enhancement and procedures for use must 

be developed. See introductory DLMS 

note 4a. 

To clearly 

document that 

qualifier ‘TN’ is a 

document number; 

and that it is a 

DLMS 

enhancement. 

No update 

needed. 

 4. REASON FOR CHANGE: To accommodate the DZH ‘consecutive transaction 

number’ and to identify that use of a document number with location reconciliation is an 

enhancement: 

 a. Review of Defense Logistics Standard System (DLSS) to DLMS mapping for 

MILSTRAP DI Code DZH Location Reconciliation Request to DLMS 846R during Army 

Logistics Modernization Program (LMP) implementation revealed the DZH rp 60-66, 

‘consecutive transaction number’ was shown as mapping to 846R 2/REF01/140 ‘TNTransaction Reference Number’. In DLMS, the REF01qualifier ‘TN-Transaction Reference 

Number’ is always intended to be the transaction number, (known as document number in 

DLSS). Some DLSS (aka “MILS”) transactions, to include DI Code DZH, did not have a 

document number and the constraints of the 80 record positions DLSS did not allow for a 

document number. Under DLMS, all DLMS transactions have a document number 

(transaction number); however use of a document number with location reconciliation 

requests is a DLMS enhancement. This change will note that 846R REF01-TN is the 

document number, and that it is a DLMS enhancement for which business rules must be 

developed. DLMSO will look into development of a separate PDC to address this enhanced 

capability and business rules. 

ADC 212 

Attachment 

2 of 4 
 b. The DZH ‘consecutive transaction number’ is not a document number, and should 

not map to REF01 qualifier ‘TN’. Under DLMS enhanced capability, a provision for a 

‘counter’ similar to DZH rp 60-66 was included at 2/LIN01/010 which states: “Use to identify 

the count of location reconciliation transactions. In the first 2/LIN/010 loop iteration, cite the 

numeric 1. In each subsequent loop iteration, increase incrementally by one.” However this 

counter would apply when DLMS enhanced looping capability was used, and multiple location 

reconciliation requests were accommodated in a single 846R through use of the LIN looping 

structure. DLMSO discussion with both DLA Distribution Standard System (DSS) and Army 

LMP indicated that their initial implementations of DS 846R location reconciliation requests 

were done as one-for-one DLMS transaction to the MILSTRAP DI Code DZH. A single 846R 

equates to a single DI Code DZH. The LIN01 counter does not lend itself for use as a counter 

in the context of DZH rp 60-66 when each 846R is a separate and distinct transaction as 

implemented by both DSS and LMP. Accordingly, this change adds a new qualifier ‘FJ’ at 

2/REF01/140 for use in place of qualifier TN, for the DZH rp 60-66 data, for initial 

implementations where a single 846R equates to a single DZH. As with document number, use 

of the LIN looping structure to combine multiple location reconciliation requests in a single 

846R is enhanced capability and DLMSO will look into development of a separate PDC to 

address this enhanced capability and associated business rules. 

c. Accommodates the DZH rp 60-66 ‘consecutive transaction number’ which is defined 

in DZH as a “consecutive number beginning with 0000001 in the first transaction, to identify 

each transaction in the reconciliation.” MILSTRAP Chapter 7 procedures require that "Storage 

activities preparing DI Code DZH requests will assure that consecutive transaction numbers by 

RI code are assigned to location reconciliation requests for control purposes." Further, 

MILSTRAP chapter 7, paragraph C7.2.6.2. states that “Storage activities shall prepare location 

reconciliation request transactions by line item (stock number + supply condition code (SCC) = 

line item),...”. Accordingly, REF01 qualifier ‘FJ- Line Item Control Number’ was selected for 

use as the DZH rp 60-66 consecutive transaction number. 

 

5. ADVANTAGES AND DISADVANTAGES: 

 

a. Advantages: Accommodates the DZH rp 60-66 ‘consecutive transaction number’ 

needed in a mixed DLSS/DLMS environment. 

b. Disadvantages: None identified.

6. IMPACT: 

a. Publications: Modify DS 846R. 

b. DAASC maps: Requires update of DAASC maps as needed. 

c. Automated Information Systems (AIS): May impact AIS that have already implemented 

DLMS 846R: 

(1) Army LMP and DLA DSS have implemented this change. 

ADC 212 

Attachment 

3 of 4 
ADC 212 

Attachment 

4 of 4 

(2) DLA Defense Distribution Depot Kuwait/Southwest Asia (DDKS) has 

implemented this change. 

 

(3) DLA reports that Vendor Managed Inventory (VMI) contractors can 

implement this change near term. 

(4) DLA Enterprise Business System (EBS). EBS currently processes 

MILSTRAP DI Code DZH rather than DLMS 846R for location reconciliation requests, 

however DLA indicates this change will impact EBS, therefore request DLA provide an 

EBS implementation date for this change, as well as for implementation of DLMS 846R.

(5) PDC 311 requested that DLMSO be advised of any other systems that 

have implemented DS 846R, so a transition to REF01-FJ could be addressed and an 

interim procedure can be accommodated by DAASC if needed. No other systems 

other than those noted in subparagraphs (1) through (3) above have reported 

implementing 846R. However to accommodate this change DAASC has modified the 

846R mapping for an interim period to recognize the REF*TN (transaction number) or 

REF*FJ (line item control number) inbound to DAASC, but will use REF*FJ outbound 

from DAASC. At the time of the modification all the outbound transactions from 

DAASC were DLSS (MILSTRAP DZH). LMP is in process of implementing 846R, at 

which time DAASC will send 846R outbound from DAASC to LMP, however as noted 

in subparagraph (1), LMP has implemented this change.