1 of 11 

ADC 164 

Attachment 

Attachment to ADC 164 

Revision to DS 846P, Physical Inventory Request, to Accommodate Functionality of End of 

Day Transaction Count and to Provide Transaction Clarification and Administrative 

Changes (Supply) 

 

1. ORIGINATOR:

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

b. Point of Contact: Ms. Mary Jane Johnson, DLMSO/J-6251, Email: Mary.Jane.Johnson@dla.mil. 

c. Functional Area: Supply (MILSTRAP) 

2. REQUESTED CHANGE: 

a. Title: Revision to DS 846P, Physical Inventory Request, to Accommodate 

Functionality of End of Day Transaction Count (MILSTRAP DZM) and to Provide Transaction 

Clarification and Administrative Changes (Supply) (Staffed by PDC 166).

b. Description of Change: This change modifies the DLMS Supplement (DS) 846P, 

Physical Inventory Request to:

(1) Incorporate data elements necessary to support the functionality of MILSTRAP DI Code 

DZM, End of Day Accountable Transaction Count. Under this functionality, the transaction is 

sent by distribution depot/storage activity to owner/manager to advise owner/manager of the 

number of accountable (balance affecting) transactions that were forwarded during the daily 

course of business. Accountable transactions for this purpose are: Receipts (DS 527R with 

1/BR02 code D4); Issues (DS 867I); Inventory Adjustment-Increases (DS 947I with 2/W1916 

code AJ); Inventory Adjustment-Decreases (DS 947I with 2/W1916 code AD); Inventory 

Adjustments-Dual (DS 947I with 2/W1916 code DU). Receipts are not separated by 

procurement and non procurement in the DS 846P count of receipt transactions processed.

 NOTE: DS 846P End of Day count deviates from MILSTRAP in that it does not 

provide for the storage activity to send counts of the DLMS equivalent of DI code DZ_ as 

the MILSTRAP Administrator does not believe DI Code DZ_ are balance affecting 

transactions. This requirement in MILSTRAP likely related to DI Code DZC, Logistics 

Reassignment (LR) Storage Information transaction (DS 846S), but the MILSTRAP 

Administrator believes that corresponding MILSTRAP DI Code D8E/F and D9E/F (DS 

947I) would be used to effect balance changes related to logistics reassignment, not the 

DZC transaction itself. Under PDC 166, DLMSO asked that the Components comment if 

there was a need to include providing for end of day count for the DLMS equivalent of 

MILSTRAP DI Code DZ_ transactions, in DS 846P. DLMSO received no comments. 

 A single DS 846P transaction provides the end of day transaction count information 

formerly conveyed by several MILSTRAP DI Code DZM transactions. For example, if the 

depot sends an owner issue transactions, inventory adjustment increase transactions, and 

inventory adjustment decrease transactions, and no other balance affecting transactions were 

processed by the depot that day, the depot would process 4 separate DZM transactions under 
2 of 11 

ADC 164 

Attachment 

MILSTRAP, one DZM to identify how many different transactions “types” were processed, in 

this case 3 (Issue, Inventory Adjustment Increase, and Inventory Adjustment Decrease); and 

three additional DZMs to provide transaction counts for each specific transaction type. 

 Under DLMS, the depot would process a single DS 846P transaction End of Day 

Transaction count (DS 846P with 1/BIA02/20 code B1) to the owner, using multiple iterations 

of the 2/LIN/10 loop as needed to convey all of the end of day transaction count information. 

One LIN loop iteration would identify how many transaction “types” were being reported and 

additional iterations of the LIN loop would provide the transaction count for each specific 

accountable transaction type reported. 

(2) Clarify DS 846P transaction use associated with beginning segment (1/BIA02/20) Report 

Type Code DD-Distribution Inventory Report; and code TC-Physical Inventory request. Each 

code relates to different aspects of the functionality of MILSTRAP DI Code DJA-Physical 

Inventory Request as follows (this table shows all MILSTRAP DI Code functionality 

accommodated by DS 846P): 

MILSTRAP

DI Code 

MILSTRAP TITLE DS 846P Beginning Segment 

Functional Equivalent to 

MILSTRAP DI Code 

1/BIA02/ 020 

Report Type Code ‘TC’ - Physical 

Inventory Request 

 

DJA Physical Inventory Request:

When DJA is used as a request to initiate, 

follow up on, or cancel a physical inventory, 

BIA02 Code TC applies. 

When DJA is used as a response to the request 

cited above (without inventory balances), 

BIA02 Code DD applies. Use as a response 

relates to DJA with rp 72 Management Codes R 

(No record of stock number or no record of 

ownership); S (Physical inventory in workload 

bank or in process; and Y (Response to followup when inventory already complete). 

1/BIA02/ 020 

Report Type Code ‘DD’ - Distributor 

Inventory Report 

DZJ Transaction History Request 1/BIA02/ 020 

Report Type Code ‘TF’ - Transaction 

History Request 

DZM End of Day Transaction Count 1/BIA02/020 

Report Type Code ‘B1’ - Batch Report 
3 of 11 

ADC 164 

Attachment 

c. Procedures: 

(1) DOD 4000.25.M. Make the following revision to DoD 4000.25-M, DLMS, Volume 2 

Supply, Chapter 6 (Physical Inventory Control), paragraph C6.2.6.2, (change is identified by 

bold, italicized text) (NOTE: This also makes an administrative correction to paragraph 

C6.2.6.2 to change “asset status” to “location reconciliation request”):

C6.2.6.2. Preparing Asset Status Location Reconciliation and End of Day 

Accountable Transaction Count. Storage activities shall prepare asset status

location reconciliation request transactions (DS to Federal IC 846R) by line-item 

(stock number + supply condition code = line item), type of pack, and date 

packed/expiration date for subsistence, for each record transaction affecting the balance 

(including zero balance), and for no physical inventory adjustment required (DS to 

Federal IC 947I, Inventory Adjustment, with zero quantity). The storage activity shall 

also submit an End of Day Accountable Transaction Count (DS to Federal IC 846P) 

to advise the owner/manager of the number of balance affecting transactions that 

were forwarded during the daily course of business. This End of Day count 

transaction is compared to the actual number of transactions received by the 

owner/manager to identify missing transactions and aid in unreconciled balance 

(URB) research. The five accountable transaction types for which the storage 

activity shall provide the owner/manager end of day transaction counts using a 

single DS 846P are as follows: 

Receipts (DS 527R with 1/BR02 Transaction Type Code D4); 

Issues (DS 867I); 

Inventory Adjustment-Increases (DS 947I with 2/W1916 Inventory Transaction 

Type Code AJ); 

Inventory Adjustment-Decreases (DS 947I with 2/W1916 Inventory Transaction 

Type Code AD); 

Inventory Adjustments-Dual (DS 947I with 2/W1916 Inventory Transaction Type 

Code DU) 

(2) DS 846P. Make the following revisions to DS 84P Physical Inventory Request (NOTE: 

no comments were received to PDC 166 which staffed these changes):

# Location DS 846P Revision Reason Federal IC 

Impact 

1 DLMS 

Introductory 

Notes 

Revise DLMS note 1 to add two new 

sentences at the end as follows:

“...Distribution depots/storage activities 

also use this transaction set to provide the 

owner/manager End of Day processing 

accountable transaction count. This 

transaction encompasses the functionality 

of MILSTRAP Document Identifier (DI) 

Codes DJA, DZJ, and DZM. 

The functionality 

of DI Code 

DZM, End of 

Day Transaction 

Count, is being 

added to DS 

846P by this 

change. 

No impact. 
4 of 11 

ADC 164 

Attachment 

# Location DS 846P Revision Reason Federal IC 

Impact 

2 DLMS 

Introductory 

Notes 

Revise DLMS note 2 as follows: 

2. Use a single occurrence of this 

transaction set to exchange transactions 

between a single owner/manager and a 

single or multiple distribution 

depots/storage activities, or between a 

single distribution depot/storage activity 

and a single or multiple owners/managers. 

For use as an end of day transaction 

count, depot/storage activity sends a 

single occurrence of this transaction to 

a single owner/manager.

The functionality 

of DI Code 

DZM, End of 

Day Transaction 

Count, is being 

added to DS 

846P by this 

change. 

No impact. 

3 DLMS 

Introductory 

Notes 

Revise DLMS note 5 to add: 

-ADC 164, Revision to DLMS Supplement 

846P, Physical Inventory Request, to 

Accommodate Functionality of End of Day 

Transaction Count (MILSTRAP DZM) and to 

Provide Transaction Clarification and 

Administrative Changes (Supply)

Identifies DLMS 

Changes included 

in DLMS 

Supplement. 

No Impact. 

4 1/BIA02/20 Add new code B1 and DLMS note:

B1 - Batch Report 

DLMS Note: 

1. Use to provide end of day accountable 

transaction count information. 

(MILSTRAP DI Code DZM functionality). 

2. Sent by distribution depot/storage 

activity to owner/manager to advise 

owner/manager of the number of 

accountable (balance affecting) 

transactions that were forwarded during the 

daily course of business. Only the 

following qualify as accountable 

transactions for this purpose: Receipts (DS 

527R with 1/BR02 code D4); Issues (DS 

867I); Inventory Adjustment-Increases

(DS 947I with 2/W1916 code AJ); 

Inventory Adjustment-Decreases (DS 947I 

with 2/W1916 code AD); Inventory 

Adjustments-Dual (DS 947I with 2/W1916 

code DU). 

Identifies End of 

Day Accountable 

Transaction 

Count 

transaction. 

Revision 

required. 
5 of 11 

ADC 164 

Attachment 

# Location DS 846P Revision Reason Federal IC 

Impact 

5 1/BIA02/20 Revise DLMS notes for existing codes DD, 

TC, and TF as follows:

DD Distribution Inventory Report 

DLMS Note: Use to identify a response to 

a physical inventory request transaction 

(does not include asset balances). From 

distribution depot/storage activity to 

owner/manager. (MILSTRAP DI Code 

DJA functionality when used as a 

response.) 

TC Physical Inventory Request 

DLMS Note: Use to identify a physical 

inventory request. From owner/manager 

to initiate, follow up on, or cancel a 

physical inventory. From distribution 

depot/storage activity to initiate or cancel a 

physical inventory. (MILSTRAP DI Code 

DJA functionality.) 

 

TF Transaction History Request 

DLMS Note: Use to identify a transaction 

history request. (MILSTRAP DI Code DZJ 

functionality). 

Provides 

clarification of use 

for Report Type 

Codes DD, TC, and 

TF. 

No impact. 

6 2/LIN/10 Add segment level DLMS note 2:

DLMS note 2. For End of Day Transaction 

count (1/BIA02/20 code B1), repeat the 

LIN loop as needed to provide the 

transaction number and accountable 

transaction count information. Use one 

iteration to identify the number of different 

transaction “types” being reported. Use 

additional iterations as needed to provide 

transaction counts for the specific 

transaction types. 

To provide 

guidance for use as 

an End of Day 

Transaction Count. 

No impact. 

7 2/LIN02/10 Add Federal note:

Use any code. 

Administrative 

update. The DS 

identifies specific 

codes used. 

Revision 

required. 
6 of 11 

ADC 164 

Attachment 

# Location DS 846P Revision Reason Federal IC 

Impact 

8 2/LIN02/10 Revise DLMS note 1 and add a new DLMS 

note 2:

1. For 1/BIA02/20 codes DD, TC, and TF, 

use only one of codes A1, A2, A4, FB, FS, 

MG, YP, or ZZ to identify the item of 

inventory. Must use National Stock 

Number (NSN) when known except when 

appropriate brand name 

subsistence items are identified by the 

Subsistence Identification Number. 

2. For 1/BIA02/20 code B1, only use ZZ.

3. For DLMS use, only the following codes 

are authorized. 

Administrative 

update for 

consistency with 

other DS and to 

provide 

clarification. 

No impact. 

9 2/LIN02/10 Add code ZZ and DLMS note:

ZZ - Mutually Defined 

DLMS Note: 

1. Dual use: 

For 1/BIA02/20 codes DD, TC, and TF, use to 

identify nonstandard material when all 

other authorized codes do not apply or 

cannot be determined (includes 

management control numbers and locally 

assigned control numbers). May be used 

for DLSS-to-DLMS conversion when the 

translator cannot determine a more 

appropriate code. DLMS enhancement, 

see introductory DLMS note 4.a. 

For 1/BIA02/20 code B1 End of Day 

accountable transaction count 

transactions, must use to comply with 

ANSI syntax requirements. Indicate ZZ in 

LIN03. 

Satisfies X12 

requirements for 

end of day 

accountable 

transaction count 

transactions. 

For other 

transaction types, 

provides an 

administrative 

Update for 

materiel 

identification for 

consistency with 

other DS.

No impact. 

10 2/LIN02/10 Delete the DLMS note from code FS. Use of NSN is 

covered by the 

DLMS note 1 at 

LIN02 Ref ID 

level. 

No impact. 
7 of 11 

ADC 164 

Attachment 

# Location DS 846P Revision Reason Federal IC 

Impact 

11 2/LIN02/10 Add the following as DLMS note 2 to codes 

A1, A2, F4, FB, MN, SN, and YP.

DLMS Note 2: DLMS enhancement. See 

introductory DLMS note 4.a. 

Administrative 

update. 

No impact. 

12 2/LIN04/10 Add the following as DLMS note 2.

DLMS Note 2: DLMS enhancement. See 

introductory DLMS note 4.a.

Administrative 

update. 

No impact. 

13 2/DTM/100 Add DLMS segment level note 2: 

2. Do not use with End of Day 

Accountable Transaction Count 

transactions (1/BIA02/20 code B1)

Clarification. No impact. 

14 2/REF/140 Add segment level DLMS note 2 as follows:

2. For End of Day Accountable Transaction 

Counts (1/BIA02/20 code B1) use to cite the 

accountable transaction count information: 

To identify 

segment use. 

No impact. 

15 2/REF01/140 Add code FI and DLMS note:

Add code FI - File Indicator 

DLMS Note: Use with 1/BIA02/20 code B1. 

Use to indicate that the number of different 

types of accountable transactions is being 

reported in 2/QTY01-02/320. Enter “1” in 

REF02 for this purpose. 

Identifies type of 

end of day 

accountable count 

transaction. 

No impact. 
8 of 11 

ADC 164 

Attachment 

# Location DS 846P Revision Reason Federal IC 

Impact 

16 2/REF01/140 Add code 8X and DLMS note

8X - Transaction Category or Type 

DLMS Note: Use to identify the specific 

transaction types for which transaction counts 

are being provided in 2/QTY/320 (i.e., receipt, 

issue, inventory adjustment increase, inventory 

adjustment decrease, inventory adjustment 

dual.) 

For Receipts (DS 527R with 1/BR02 code D4); 

Issues (DS 867I); Inventory AdjustmentIncreases (DS 947I with 2/W1916 code AJ); 

Inventory Adjustment-Decreases (DS 947I with 

2/W1916 code AD); Inventory AdjustmentsDual (DS 947I with 2/W1916 code DU), cite 

the appropriate code in REF02 as follows: 

For Receipts, cite 527R in REF02. 

For Issues, cite 867I in REF02. 

For Inventory Adjustment Increases, cite 

947IAJ in REF02. 

For Inventory Adjustment Decreases, cite 

947IAD in REF02.

For Inventory Adjustments Dual, cite 947I DU 

in REF02.

Indicates the 

“type” of the 

balance affecting 

transaction. 

No impact. 

17 2/REF01/140 Add DLMS note to code TN

TN Transaction Reference Number 

DLMS Note: DLMS enhancement. See 

introductory DLMS note 4.a.

Administrative 

update to identify a 

DLMS 

enhancement. 

Transaction number 

(i.e, document 

number) is not used 

in the corresponding 

MILSTRAP 

transactions (DI 

Codes DJA, DZJ, 

DZM). 

No impact. 

18 2/QTY/320 Delete Federal segment note. Administrative 

update. 

Revision 

required. 
9 of 11 

ADC 164 

Attachment 

# Location DS 846P Revision Reason Federal IC 

Impact 

19 2/QTY01/320 Add code 46 and DLMS note: 

46 -Total Transactions 

DLMS Note: Use with BIA02 code B1 End of 

Day transaction count and 2/REF01 code FI to 

indicate the total number of balance affecting 

transaction types being reported in this 

transaction. For the purpose of this transaction 

there are 5 possible transaction types for which 

end of day counts can be reported (receipts, 

issues, inventory adjustment increases, 

inventory adjustment decreases, and inventory 

adjustment dual.) 

Identifies total 

number of balance 

affecting 

transaction types. 

No impact. 

20 2/QTY01/320 Add code TT and DLMS note: 

TT -Total Production Volume and DLMS 

DLMS Note: Use with BIA02 code B1 End of 

Day count to indicate the daily volume of 

balance affecting transactions applicable to the 

transaction category/type identified in 

2/REF01/140 code 8X (e.g. if 36 receipt 

transactions are being reported, REF01 = 8X; 

REF02 = 527R; QTY01 = TT; QTY02 = 36.) 

Identifies daily 

volume of balance 

affecting 

transactions. 

No impact. 

21 2/QTY01/320 Revise DLMS note for UU as follows:

UU Used 

DLMS note: For BIA02 codes DD, TC, and 

DF, use to comply with X12 syntax 

requirements. Cite “1” in QTY02. Do not use 

with BIA02 code B1. 

Administrative 

update to clarify 

code use. 

No impact. 

22 2/QTY02 Delete Federal note. Use of QTY02 is 

explained in 

associated QTY01 

codes. 

Revision 

required. 

4. REASON FOR CHANGE: This change supports component-level DLMS 

implementation by incorporating MILSTRAP DI Code DZM, End of Day Transaction Count, 

functionality in DLMS. This change also provides transaction clarification and administrative 

updates. 

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports DLMS implementation.

b. Disadvantages: None identified.
10 of 11 

ADC 164 

Attachment 

6. IMPACT: 

a. Data Content/Procedures: Component systems must incorporate DS 846P End of Day 

Accountable Transaction Count capability. 

b. Publication(s): DLMS manual; DLMS Supplement and corresponding Federal IC. 

c. DAASC Maps. DAASC maps must be revised to incorporate DZM End of Day 

functionality in DS 846P. DAASC maps may need to be updated to reflect the intended use of 

1/BIA02/20 code DD, if not already documented. 

MILSTRAP DI Code DZM data maps to DS 846P as shown in the following table:

DZM FIELD DZM RP DZM EXPLANATION Corresponding DS 846P Data Location

Document 

Identifier 

1-3 Enter DI Code DZM. 1/BIA02/020 code B1 equates to DZM 

Routing 

Identifier 

(TO) 

4-6 Enter RI code identifying the 

owner/manager to which the transaction 

is being forwarded. 

2/N101/450 = Z4 

2/N103/450 = M4 (RIC) 

2/N104/450 = RIC Value 

2/N105/450 = TO

Type of 

Accountable 

Transaction 

Count 

7 Enter 1 to identify the number of 

transactions included in this 

transmission. 

or 

 

Enter 2 to identify the individual 

balance affecting transaction. 

2/REF01/140 code F1 

2/REF02/140 = 1 

Eliminated by intent. 

The presence of 2/REF01/140 code 8X, and 

2/QTY01 code TT indicates that information is 

being provided for individual balance affecting 

transactions. 

Blank 8-27 Leave blank. ---------- 
11 of 11 

ADC 164 

Attachment 

DZM FIELD DZM RP DZM EXPLANATION Corresponding DS 846P Data Location

Accountable 

Transaction DI 

Code 

28-29 Enter the first two positions of the 

balance affecting transactions (D4, D6, 

D7, D8, D9, DA, DZ*). Leave blank 

if record position 7 is equal to 1. 

*No provision was made to 

provide end of day count for 

“DZ” transactions in DLMS (DS 

846P). See paragraph 2.b(1) in 

this attachment. 

2/REF01/140 = 8X Transaction Category or Type 

2/REF02/140 = value 

For Receipts (DS 527R with 1/BR02 code D4); 

Issues (DS 867I); Inventory Adjustment-Increases

(DS 947I with 2/W1916 code AJ); Inventory 

Adjustment-Decreases (DS 947I with 2/W1916 

code AD); Inventory Adjustments-Dual (DS 947I 

with 2/W1916 code DU), cite the appropriate 

code in REF02 as follows:

Receipts: REF02 = 527R 

Issues: REF02 = 867I

Inventory Adjustment Increases: REF02 = 947IAJ

Inventory Adjustment Decreases: REF02 = 947IAD

Inventory Adjustments Dual: REF02 = 947I DU 

Accountable 

Transaction 

Count 

30 Enter the number of transactions 

included in this transmission. Leave 

blank if record position 7 is equal to 2. 

2/QTY01/320 = 46 

2/QTY02/320 = value 

Blank 31-37 Leave blank. -------------- 

Number of 

Balance 

Affecting 

Transactions 

38-43 Enter the daily volume of balance 

affecting transactions applicable to the 

reported DI code in record position 28-

29. Leave blank if record position 7 is 

equal to 1. 

2/QTY01/320 = TT 

2/QTY02/320 = value 

Blank 44-66 Leave blank. ------------ 

Routing 

Identifier 

(FROM) 

67-69 Enter the RI code identifying the 

storage activity preparing the 

transaction. 

1/N101/80 = SB 

1/N103/80 = M4 (RIC) 

1/N104/80 = RIC Value 

1/N106/80 = FR

Date 

(Transaction) 

70-73 Enter the ordinal day on which the 

transaction took place. 

1/BIA04/20 

Blank 74-80 Leave blank. ---------------