1 of 6 

ADC 198 

Attachment 

ATTACHMENT TO ADC 198 

Revise DS 846P to Provide Capability to Advise When No History is Available in 

 Response to a Transaction History Request (Supply) (Staffed by PDC 207A) 

1. ORIGINATOR: 

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

b. Originator: Ms. Mary Jane Johnson, DLMSO, 703-767-0677 (DSN 427), e-mail: 

Mary.Jane.Johnson@dla.mil.

2. FUNCTIONAL AREA: 

 Primary: Supply 

3. REQUESTED CHANGE: 

a. Title: Revise DS 846P to Provide Capability to Advise When No History is Available 

in Response to a Transaction History Request (Supply). 

b. Description of Change: 

 (1) The capability to identify that no history is available in response to a request for 

transaction history exists in MILSTRAP, but was not incorporated in DLMS. The Defense 

Logistics Agency (DLA) has identified the requirement for this capability for the Defense 

Distribution System (DSS) and Business System Modernization (BSM). DS 846P, Physical 

Inventory Request, is a multipurpose transaction currently used to request physical inventory; to 

respond to a physical inventory request (without asset balances); and to request transaction 

history. This change will add a beginning segment (DS 846P BIA segment) code for the 

capability to respond to a transaction history request when no history is available. 

 (2) This change also adds two new Type of Physical Inventory/Transaction History 

Codes for use with DS 846P when advising that no history is available, to equate to the DZK, 

record position 30-43, 8-fill and 9-fill functionality. An excerpt from MILSTRAP DI Code 

DZK, rp 30-43, explains the purpose of the 8-fill and 9-fill follows: 

FIELD LEGEND RP ENTRY AND INSTRUCTIONS 

Document 

Number 

30-43 When record position 7 of the DI Code DZJ request is W and the storage 

activity has no transactions for the stock or part number requested for the 

dates specified in record positions 25-31, but transactions are available since 

the date of last location reconciliation, 8-fill this field; when no transactions 

are available for the dates specified or since the date of last reconciliation, 9-

fill this field. When record position 7 is X and the storage activity has no 

transactions for the dates specified, 9-fill this field; otherwise, perpetuate 

from the source document. 
2 of 6 

ADC 198 

Att 

 (3) There is no DLMS format designated for MILSTRAP DZK transaction history 

transactions themselves; rather history is sent back in the DLMS format of the original 

transaction, with a "history flag" identified as a beginning segment action code ‘W1’ for 

historical submission. DLA indicates that they need transaction confirmation indicating when 

history is not available, rather than just not receiving history if it is not available. Under 

MILSTRAP, when there is no transaction history available for the requested timeframe, a DZK 

transaction history response is sent with record positions 30-43, either 8-filled or 9-filled. 

Under DLMS, this can be accomplished by adding a new DS 846P beginning segment 

(1/BIA02/20) Report Type Code ‘AD’ to provide a transaction means for the depot to respond 

that no history is available. 

c. Procedures: 

 (1) Revise Type of Physical Inventory/Transaction History Codes (DLMS Data 

dictionary and MILSTRAP AP2.2) to add new codes 8 and 9 as follows:

CODE DEFINITION 

8 Distribution depot/storage activity has no transactions for the stock or part number 

requested for the dates specified, but transactions are available since the date of last 

location reconciliation. For use with DLMS Supplement 846P when beginning segment 

Report Type Code (1/BIA02/20) is ‘AD’. 

9 Distribution depot/storage activity has no transactions available for the dates specified or 

since the date of last reconciliation. For use with DLMS Supplement 846P when 

beginning segment Report Type Code (1/BIA02/20) is ‘AD’. 

 (2) Revise DOD 4000.25-2-M, DLMS, Volume 2, Chapter 6, as follows (change is 

identified by red, bold, italicized text:

C6.4.4. Transaction History. For intra-DoD Component (or inter-DoD Component, based on 

agreement of the DoD Components involved) reconciliation, the owner/IMM may request transaction 

history for analyzing inventory discrepancies. 

 C6.4.4.1. Transaction History Request. The owner/IMM shall request the history using DS 

846P citing the appropriate type physical inventory or transaction history code. Transaction history 

shall consist of all transactions affecting the balance for the requested timeframe. 

 C6.4.4.2. Transaction History Data. The storage activity shall send transaction history by 

submitting the affected transactions with beginning segment action code ‘W1’ indicating a historical 

submission. DLMS transactions containing action code ‘W1’ for historical submission are: 527R, 

867I, 940R, 945A, and 947I. When no history is available for the selected timeframe, submit DS 

846P indicating no history was available (1/BIA02/20 Report Type Code AD) with Type of Physical 

Inventory/Transaction History Code 8 or 9. 
3 of 6 

ADC 198 

Att 

 (3) Revise the “Correlation of MILSTRAP Document Identifier (DI) Code Functionality to 

DLMS Supplement” Chart (available from the DLMSO Web site at http://www.dla.mil/j-6/dlmso/ 

eApplications/LogDataAdmin/dlssdlmscrossreftable.asp). Changes are red, bold, italicized: 

DI 

Code 

MILSTRAP TITLE DS # DS Accredited Standards Committee (ASC) X12

Functional Equivalent to MILSTRAP DI Code 

 Beginning Segment and 

Data Element (DE) ID

Additional Information needed 

DZK Transaction History Transmittal There is no direct map of MILSTRAP DI Code DZK to DLMS. 

Instead, all transactions that were subject to historical submission 

under DZK were given a beginning segment action code ‘W1” for 

historical submissions. DLMS transactions containing action code 

W1 for historical submission are: 527R, 867I, 940R, 945A, 947I. (see 

exception below for response when no transaction history is 

available for the selected timeframe)

DZK Transaction History Transmittal 

When rp 30-43 of DZK is 8 or 9-

filled to indicate that no history was 

available for the selected timeframe, 

submit DS 846P indicating no 

history was available. BIA02 Code 

AD applies. 

Rp 30-43 8-fill indicates when rp 7 

of DZJ history request is W and 

storage activity has no transactions 

for the stock or part number 

requested for the dates specified in 

DZJ rp 25-31, but transactions are 

available since the date of last 

location reconciliation. 

Rp 30-43 9-fill indicates: 

--When rp 7 of DZJ history request 

is W and storage activity has no 

transactions available for the dates 

specified, or since the date of last 

reconciliation. 

--When rp 7 of DZJ is X and the 

storage activity has no transactions 

for the dates specified. 

846P 1/BIA02/020 DE 755 

Report Type code AD 

- Agent/Distributor 

Inventory Report 

2/LQ01/270 Code ‘FC’ Type of 

Physical Inventory/Transaction 

History Code 8 or 9
4 of 6 

ADC 198 

Att 

 (4) Revise DS 846P as follows:

Item

# 

Location Revision to Reason Federal IC 

Impact

1. DLMS 

Introductory 

Notes 

Revise DLMS introductory note 1 (changes are 

highlighted): 

1. Owners and managers use this transaction set to 

request, inquire about, and cancel a physical inventory 

by a distribution depot or storage activity. Owners and 

managers also use this transaction set to request 

transaction history. Distribution depots/storage 

activities use this transaction set to cancel and/or 

reschedule a physical inventory request by an 

owner/manager. Distribution depots/storage activities 

also use this transaction set to respond to a request for 

transaction history when no history is available and 

an inquiry about a request for a physical inventory. 

Distribution depots/storage activities also use this 

transaction set to provide the owner/manager End of 

Day processing accountable transaction count 

information. This transaction encompasses the 

functionality of MILSTRAP Document Identifier (DI) 

Codes DJA, DZJ, DZK when rp 30-43 is 8-filled or

9-filled, and DZM. 

To identify transaction 

uses 

No impact 

2. DLMS 

Introductory 

Notes 

Add ADC 198 to DLMS introductory note 4.d: 

-ADC 198, Revise DS 846P to Provide Capability 

to Advise When No History is Available in 

Response to a Transaction History Request 

(Supply). 

To identify DLMS 

changes included in 

the DS 

No impact 

3. 1/BIA02/20 Add qualifier AD with DLMS note: 

AD Agent/Distributor Inventory Report 

DLMS Note: Use to respond to a Transaction 

History Request when no history is available. 

From distribution depot/storage activity to 

owner/manager. (MILSTRAP DI Code DZK 

functionality when record position 30-43 is 8-

filled or 9-filled.) Use with 2/LQ01/270/FC Type 

of Physical Inventory/Transaction History Code 8 

or 9. NOTE: When history is available, there is 

no direct map of MILSTRAP DI Code DZK to 

DLMS. Instead, all transactions that were 

subject to historical submission under DZK, were 

given a beginning segment action code ‘W1” for 

historical submissions. DLMS transactions 

containing action code W1 for historical 

submission are: 527R, 867I, 940R, 945A, 947I.

To accommodate 

current MILS 

requirement to advise 

when no historical 

transactions are 

available in response 

to a request for history 

Revision 

required 
5 of 6 

ADC 198 

Att 

Item

# 

Location Revision to Reason Federal IC 

Impact

4. 2/LIN02/10 Revise DLMS Note 1 to add code AD:

For 1/BIA02/20 codes AD, 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.

To incorporate 

requirement for new 

Type Report Code 

‘AD’ into existing 

DLMS note 

No impact 

5. 2/LIN02/10 

code ZZ 

Revise note 1 for code ZZ- Mutually Defined:

1. Dual use: 

For 1/BIA02/20 codes AD, 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 4a.

To incorporate 

requirement for new 

Type Report Code 

‘AD’ into existing 

DLMS note 

No impact 

6. 2/LQ01/270 

Code FC 

Add DLMS note to Code FC-Type Physical 

Inventory or Transaction History Code:

DLMS Note: When using with 1/BIA02/20 

Report Type Code AD, only code values 8 and 9 

are authorized. 

To identify Type 

Physical Inventory/ 

Transaction History 

Codes that apply for 

Report Type Code AD 

No impact 

7. 2/QTY01/320 Revise note 1 for code UU-Used:

For BIA02 codes AD, DD, TC, and DF, use to 

comply with X12 syntax requirements. Cite “1” in 

QTY02. Do not use with BIA02 code B1. 

To incorporate 

requirement for new 

Type Report Code 

‘AD’ into existing 

DLMS note 

No impact 

4. REASON FOR CHANGE: To accommodate current MILS requirement to advise when no 

historical transactions are available in response to a request for history. 

5. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Accommodates an existing MILS capability in DLMS 

 b. Disadvantages: None known 

6. IMPACT: 
6 of 6 

ADC 198 

Att 

a. Publication(s): DOD 4000.25-M, DLMS and DLMS Supplement 846P and the Federal 

Implementation Convention (IC) for DS 846P (upon approval of the change, changes to the Federal IC 

will be submitted to the EDISMC/Logistics Functional Work Group for coordination/approval). 

b. DAASC Mapping: DAASC mapping update required. 

c. AUTOMATED Information Systems (AIS). DOD Component AIS may require revision to 

accommodate this DLMS functionality.