1 of 8

ADC 136

Attachment

Attachment to ADC 136, Revision to Defense Logistics Management System

(DLMS) Supplement 846R Location Reconciliation Request to Support CommodityUnique (Mapping Product) Data, and to Support MILSTRAP DZN/DZP 

Functionality (Staffed by PDC 120A)

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Agency (J-3731) (mapping product data) 

and the Defense Logistics Management Standards Office (DLMSO) (DZN/DZP 

Functionality)

 b. Points of Contact: 

(1) For Commodity Unique (Mapping Product) Requirements: Ms. Beth 

Altman or Ms. Brenda Meadows, HQ DLA, Distribution and Reutilization Policy, 

Distribution Management Division, Materiel Accountability and Distribution Policy 

Branch (J-3731) 

 (2) For MILSTRAP DI Code DZP/DZN functionality: Ms. Mary Jane 

Johnson, DLMSO, 703-767-0677, DSN 427-0677, email: Mary.Jane.Johnson@dla.mil

2. FUNCTIONAL AREA: Supply 

3. REQUESTED CHANGE: 

a. Title: Revision to DLMS Supplement (DS) 846R Location Reconciliation 

Request to Support Commodity-Unique (Mapping Product) Data and to Support 

MILSTRAP DZN/DZP functionality 

b. Description of Change: The purpose of this change is to modify the DS for 

the 846R Location Reconciliation Request: (1) to accommodate data requirements for 

commodity unique (mapping products) data; (2) to accommodate the functionality of 

MILSTRAP Document Identifier Codes DZN, Location Reconciliation Notification, and 

DZP, Location Reconciliation History Notification, which were not previously 

incorporated into DLMS; and (3) administrative updates to include incorporating changes 

approved by Approved DLMS Change (ADC) 45 (July 5, 2001), Use of Both Ownership 

Code and Purpose Code in DLMS for Ammunition, and ADC 77 (August 26, 2002), Air 

Force Unique Management Coding for Materiel Management Aggregation Code 

(MMAC). 

 (1) Documents showing data mapping from MILSTRAP DI Codes DZN and 

DZP to DS 846R are at the enclosure. 

 (2) Background for incorporation of commodity unique (mapping products) 

requirements: In April 1998, DLA assumed responsibility for worldwide inventory 
2 of 8

ADC 136

Attachment

management, cataloging, and physical distribution of more than 67,000 hard copy map 

products (i.e., maps, charts and other geodetic materiel) produced by National 

Geospatial-Intelligence Agency (formerly National Imagery and Mapping Agency), as 

well as those produced by other United States government agencies and foreign 

countries. Existing inventory was moved to the new primary distribution facility, Defense 

Distribution Mapping Activity (DDMA), Richmond, Virginia, and Defense Supply 

Center Richmond (Product Center 9), Virginia, assumed Inventory Control Point (ICP) 

responsibilities. DDMA uses DLA’s Distribution Standard System (DSS) to perform 

distribution processes. DSCR Product Center 9 uses another DLA legacy system, 

Defense Mapping Agency Automated Distribution Management System (DADMS), to 

perform ICP processes. DSS communicates with DADMS through a DLA-controlled 

FTP translator. DSS Location Reconciliation Requests (DI Code DZH) were modified to 

include 3 additional DADMS data elements (edition number, edition date, and product 

effective date) not accommodated by the Defense Logistics Standard System. The 

purpose of this proposed change is to modify Defense Logistics Management System 

(DLMS) Supplement 846R, Location Reconciliation Request, to accommodate these 

commodity-unique data. These changes are required to ensure that DSS interface with 

DADMS is uninterrupted as DSS migrates to the Defense Logistics Management System 

(DLMS), as well as to document commodity-unique business rules. [Staffing Note: 

DLA senior executives decided June 6, 2003, that DADMS was not within the scope of 

current Business Systems Modernization (BSM) efforts to replace DLA’s Standard 

Automated Materiel Management System (SAMMS). Incorporation of DADMS 

functionality into BSM will not be addressed until sometime after 2007.] 

c. Procedures: Add the following codes/notes to the 846R Location 

Reconciliation Request, DLMS Supplement. Data requirements submitted by DLA to 

support Commodity unique (mapping products) requirements are at rows #12 and #13 in 

the table below. All other changes are related either to MILSTRAP DI Code DZP/DZN 

requirements, ADCs 45 and 77; or are administrative changes for consistency with other 

DLMS Supplements. 

# Location DS 846R Revision Reason Federal 

IC 

Impact

1 Federal 

Introductory 

Notes 

Revise note 1:

1. Distribution depots and storage activities use 

this transaction set to transmit location 

reconciliation request transactions to owners and 

managers. 

Transaction is no 

longer limited to 

requests. 

Revision 

required.

2 DLMS 

Introductory 

Notes 

Revise DLMS note 1 to read as follows: 

1.Distribution depots and storage activities use a 

single occurrence of this transaction set to 

transmit either location reconciliation request, 

location reconciliation notification, or location 

reconciliation history notification transactions to 

one owner/manager. 

To identify 

expanded 

capability.

No 

impact.
3 of 8

ADC 136

Attachment

# Location DS 846R Revision Reason Federal 

IC 

Impact

3 DLMS 

Introductory 

Notes 

This DLMS Supplement incorporates the 

Proposed DLMS Change and Approved DLMS 

Change (ADC) listed. PDC/ADCs are available 

from the DLMSO website: http://www.dla.mil/j6/dlmso/changes.

-- ADC 45, Use of Both Ownership Code and 

Purpose Code in DLMS for Ammunition

-- ADC 77, Air Force Unique Management 

Coding for Materiel Management Aggregation 

Code (MMAC) .

--ADC 136, Revision to DLMS Supplement 846R 

Location Reconciliation Request to Support 

Commodity-Unique (Mapping Product) Data and 

to Support MILSTRAP DZN/DZP functionality. 

Administrative to 

delete PDC 

120/120A and 

replace them with 

ADC 136, to 

accurately identify 

DLMS Changes 

included in the 

DLMS 

Supplement.

No 

impact.

4. 1/BIA02/020 Add code to BIA02.

 Add code ZZ- Mutually Defined and DLMS 

Note: “Use to identify Location Reconciliation 

History Notification transaction. Storage 

activity sends to owner/manager to advise of the 

number of transaction history transactions being 

forwarded . (MILSTRAP DI Code DZP). An 

ANSI data maintenance action will be taken to 

obtain a more appropriate code for use in a 

future version/release.

Identifies Location 

Reconciliation 

History 

Notification 

transaction

Revision 

required.

5. 1/BIA02/020 Add code to BIA02.

 Add code X4 - Summary Report and DLMS 

Note: “Use to identify Location Reconciliation 

Notification transaction. Storage activity sends 

to owner/manager to advise of the number of 

Location Reconciliation Request transactions 

being forwarded. (MILSTRAP DI Code DZN)”. 

Identifies Location 

Reconciliation 

Notification 

transaction

Revision 

required.

6. 1/BIA02/020 Code LC- revise DLMS note as follows: 

Use to identify location reconciliation request 

transactions (MILSTRAP DI Code DZH). 

Administrative 

change.

No 

impact.
4 of 8

ADC 136

Attachment

# Location DS 846R Revision Reason Federal 

IC 

Impact

7. 1/BIA06/020 Open BIA06 Action Code, for use with data 

element ID 306 qualifiers ‘24’ and ‘Z’ as 

follows: 

Federal note: Use any code 

DLMS notes: 

1. Use to identify the type of location 

reconciliation 

2. For DLMS, only the following codes are 

authorized. 

24 – On Hand 

DLMS notes: 

1. Use to identify that the transaction identified 

in BIA02 is associated with annual location 

reconciliation. 

2. An ANSI data maintenance action taken 

to obtain a more appropriate code for use 

in a future version. 

Z – Mutually Defined 

DLMS notes: 

1. Use to identify that the transaction 

identified in BIA02 is associated with endof-day processing. 

2. An ANSI data maintenance action taken 

to obtain a more appropriate code for use 

in a future version. 

To convey whether 

transaction is for 

annual or end of 

day location 

reconciliation in 

the beginning 

segment, rather 

than carry as a 

table 2 LQ01/270 

code. The 

information was 

carried as a code 

list in DLSS due to 

the constraints of 

the 80 record 

position

transactions. 

DLMS should not 

be constrained in a 

similar manner 

when there is a 

more efficient way 

to convey the 

information. 

Revision 

required.

8 1/N101/080 Change Federal note to the following: 

“Use any code.” 

DLMS Supplement 

authorizes specific 

qualifiers. 

Revision 

required. 

9 1/LQ01/150 Change Federal note to the following: 

“Use any code.”

DLMS Supplement 

authorizes specific 

qualifiers. 

Revision

required. 

10 2/LIN02/010 Change Federal note to the following: 

“Use any code.”

DLMS Supplement 

authorizes specific 

qualifiers.

Revision

required. 
5 of 8

ADC 136

Attachment

# Location DS 846R Revision Reason Federal 

IC 

Impact

11. 2/LIN02/010 Add code and code note to LIN 01: 

Add code ZZ - Mutually Defined and DLMS 

Note: “Use with transactions reporting the 

number of location reconciliation notification 

transactions to comply with ANSI syntax 

requirements.

Satisfies X12 

requirements.

No impact.

12 2/DTM/100 Authorize use of additional data element 374 

(Date/Time Qualifier) code values to identify the 

following DLA map product-unique attributes, 

and add the accompanying DLMS notes:

171 Revision

Proposed DLMS Note: “Use in DLA DDMA 

location reconciliation requests to identify the 

map edition date. Each DLA DDMA location 

reconciliation request should include either an 

edition date (used in conjunction with 

2/REF01/140 edition number) or a product 

effective date, but not both.”

152 Effective Date of Change

Proposed DLMS Note: “ Use in DLA DDMA 

location reconciliation requests to identify the 

cyclical map product effective date. Each DLA 

DDMA location reconciliation request should 

include either an edition date (used in 

conjunction with 2/REF01/040 edition number) 

or a map effective date, but not both.”

Authorizes use of 

codes 171 and 152 

to identify DLA 

map edition date 

and the product 

effective date.

No impact.

13 2/REF01/140 Change Federal note to the following:

“Use any code.”

DLMS Supplement 

authorizes specific 

qualifiers.

Revision 

required.
6 of 8

ADC 136

Attachment

# Location DS 846R Revision Reason Federal 

IC 

Impact

14 2/REF01/140 Add 6G-Map Number, for Map Edition number, 

with DLMS note:

6G Map Number 

DLMS Note: Use in DLA map location 

reconciliation requests to identify the map 

edition number. Component unique 

enhancement.

Use of this qualifier 

is different than 

staffed by PDC 

120A. However it 

was identified as a 

revision by a 

9/21/04 email, 

subject: PDC 

120A Update.

Use of qualifier 

6G-Map Number is 

consistent with 

ADC 133 for DS 

527R and ADC 

71A for DS 970.

No impact.

15 2/LQ01/270 Change Federal note to the following:

“Use any code.”

DLMS 

Supplement 

authorizes 

specific 

qualifiers.

Revision 

required.

16 2/LQ01/270 Replace existing DLMS note for qualifier 

‘FH-Location Reconciliation Request’ 

with the following note:

FH - Type of Location Reconciliation 

Request

DLMS note: Data to be removed from 

transaction in future version. The type of 

location reconciliation (annual or end-ofday) should be conveyed by 1/BIA06/020. 

Type of location 

reconciliation will 

be conveyed in the 

beginning segment, 

rather than a 

2/LQ01/270 code. 

The information 

was carried as a 

code list in DLSS 

due to the 

constraints of the 

80 record position 

transactions. 

DLMS should not 

be constrained in a 

similar manner 

when there is a 

more efficient way 

to convey the 

information.

No 

impact.
7 of 8

ADC 136

Attachment

# Location DS 846R Revision Reason Federal 

IC 

Impact

17 2/QTY01/320 Add code ‘46’ and DLMS note to QTY 01

46 -Total Transactions 

 DLMS Note: “Must use with location 

reconciliation notification transactions 

(1/BIA01/020 codes X4 and ZZ) to indicate the 

number of history or location reconciliation 

request transactions submitted.”

Identifies number 

of location 

reconciliation 

notification 

transactions 

submitted.

Revision 

required.

18 2/LQ01/376 Change Federal note to the following:

“Use any code.”

DLMS Supplement 

authorizes specific 

qualifiers.

Revision 

required.

19 2/LQ01/376 Revise LQ01 DLMS note 1 as follows:

Use either code 99 or A1 (but

not both), except for ammunition where both 

codes may be used. (Use of both codes for 

ammunition is a DLMS enhancement (see 

introductory DLMS note 4a).

Change IAW ADC 

45, Use of Both 

Ownership Code 

and Purpose Code 

in DLMS for 

Ammunition.

No 

impact.

20 2/LQ01/376 Add qualifier GQ, Group Qualifier Code, as 

follows:

GQ Group Qualifier Code

DLMS Note: Use to identify the MMAC for 

NSNs to be managed by a specific manager (i.e., 

system, program, aggregation, selected FSC, 

technology group). This is an Air Force-unique 

data element, meaningful to the Air Force only. 

Non-Air Force Components perpetuate without 

action. 

A data maintenance action was approved in 

version 5010. The approved code/name is 

“MAC-Materiel Management Aggregation code”. 

The code source is identified as the Air Force 

Manual (AFMAN) 23-110, Volumes 1 and 2.

Change IAW ADC 

77, Air Force 

Unique 

Management 

Coding for 

Materiel 

Management 

Aggregation Code 

(MMAC)

No 

impact.

4. REASON FOR CHANGE: This change revises DS 846R to: support componentlevel DLMS implementation for the DLA BSM effort for mapping products; incorporate 

MILSTRAP DZN/DZP functionality in DLMS; incorporate ADC 45 and ADC 77 

revisions; and makes administrative revisions for consistency with other DS. 
8 of 8

ADC 136

Attachment

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports component-level DLMS implementation and 

MILSTRAP functionality. 

b. Disadvantages: None identified. 

6. IMPACT: 

a. Data Content/Procedures: DAAS maps and Component systems 

must incorporate additional capability. 

b. Publication(s): 

 (1) DLMS Supplement, DAASC Maps, and corresponding Federal IC must be 

updated. 

(2) DOD 4000.25-2-M, Volume 2 Supply, Revise Chapter 6 Physical Inventory 

Control to add a new section C6.6.2.3.4, Control of Location Reconciliation, renumber 

current section C6.6.2.3.4 as C6.6.2.3.5, and renumber all subsequent paragraphs. Add 

DLMS, Volume 2, Chapter 6, section C6.6.2.3.4, Control of Location Reconciliation as 

follows: 

“C6.6.2.3.4 Control of Location Reconciliation. Storage activities and 

owners/managers will establish the following provisions for controlling location 

reconciliation: 

C6.6.2.3.4.1 Location Reconciliation Notification Transaction. Storage 

activities will advise intended recipients (owners/managers) of the number of 

transactions being forwarded, and cut-off date, using DS 846R Location 

Reconciliation Notification transaction. 

C6.6.2.3.4.2 Location Reconciliation History Notification transaction. 

When transaction history is required with Location Reconciliation, the storage activity 

will advise intended recipients (owners/managers) of the number of historical 

transactions being forwarded, and the cutoff date, using DS 846R Location 

Reconciliation History Notification transaction. 

C6.6.2.3.4.3 Owners/managers will use these transactions to determine 

receipt of all Location Reconciliation and historical transactions. Where the number 

of transactions to be transmitted does not match what was actually received, the 

owner/manager may reject the Location Reconciliation and Location Reconciliation 

History Notification transactions using DS 824 with Reject Advice Code AY”. 

Enclosure