DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J . KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060·6221 

November 19, 2014 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 

1135, DLMS 832N Catalog Data Support Mapping Update at DLA Transaction 

Services to Support Navy Fleet Readiness Center (FRC) (Supply) 

The attached proposed change to DLM 4000.25, Defense Logistics Management System, 

and DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP), is 

approved for implementation. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 

703-767-0676, DSN 427-0676, or e-mail: Ellen.Hilert@dla.mil, or Ms. Heidi Daverede, DOD 

MILSTRIP Alternate, 703-767-5111 ; DSN 427-5111 or email: Heidi.Daverede@dla.mil. Others 

must contact their Component designated Supply PRC representative available at 

https://www2.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp 

Attachment 

As stated 

cc: ODASD (SCI) 

o~~ irector 

efense Logistics Management 

Standards Office 
Attachment, ADC 1135

Page 1

Attachment to ADC 1135

DLMS 832N Catalog Data Support Mapping Update at DLA Transaction 

Services to Support Navy Fleet Readiness Center (FRC)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: Defense Logistics Agency, Aviation – BATB, DSN: 695-3412

b. Functional POC: Defense Logistics Agency, Aviation – BATB, DSN: 695-3412

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Tech/Quality

3. REFERENCES:

a. Approved DLMS Implementation Convention 832N Catalog Data Support available 

at: www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp.

b. DOD 4100.39-M, Federal Logistics Information System (FLIS) Procedures, available 

at: www.dlis.dla.mil/flis_procedures.asp.

c. ADC 360, Procedures and Content Requirements for Catalog Data Support under 

Navy and Marine Corps Base Reassignment and Closure (BRAC), January 05, 2010

d. ADC 360A, Revised Catalog Data Support under Navy BRAC to Add Catalog 

Transaction Purpose Codes and Drawing Commercial and Government Entity (CAGE), October 

06, 2011

4. APPROVED CHANGE(S):

a. Brief Overview of Change: In support of BRAC Retail Supply, Storage, and

Distribution (SS&D)/Inventory Management and Stock Positioning (IMSP), the DLMS 832N

Catalog Data Support requires updates to the data mapping for successful use by the Navy Fleet 

Readiness Center (FRC). This addendum supplements, but does not replace the original ADC

360 as revised by ADC 360A (references 3.c. and 3.d.). This change also contains updates to the 

DLMS manual guidance for use of the Catalog Data Support transaction.

b. Background:

(1) As a result of the 2005 BRAC decision, retail supply, storage and distribution

functions and associated infrastructure supporting the Navy industrial/maintenance sites will

transfer to DLA. The intent of the directive is to significantly improve combat effectiveness

while reducing costs by developing a world-class, cost-effective supply chain focused on

readiness. In accordance with the signed Concept of Operations (CONOPS), DLA has agreed to 
Attachment, ADC 1135

Page 2

provide SS&D/IMSP support to the FRC and Naval Shipyard (NSY) sites, including catalog data

support which is supported via the DLMS 832N. 

(2) Navy Industrial Activity (IA) item drawing data is accommodated by 

Enterprise Business System (EBS) via four new fields on the EBS materiel master and 

communicated to NSY/Fleet Readiness Center (FRC) systems via the DLMS 832N. Three fields 

were accommodated by ADC 360: Drawing Number, Detailed Drawing Piece Number, and 

Drawing Revision Number. The final field, Drawing Commercial and Government Entity 

(CAGE) Code, was accommodated via ADC 360A. However, as the result of integrated testing

between DLA and the Navy FRC, additional requirements have been identified to fully support

catalog maintenance due to differences in data mapping within the Navy system.

(3) At DLA, the master record is built using the part number (PN) and CAGE 

combinations based on the following FLIS Reference Number Control Codes (RNCC) / 

Reference Number Variation Code combinations (RNVC): 3/2, 3/3, 5/2, 5/3 or 8/2. The only 

exception occurs when the CAGE is a Government CAGE, as DLA does not build records for 

Government CAGEs. Instead, DLA builds “drawing packages/specifications” using the 

drawing/specification number, drawing/specification piece part number, drawing/specification

revision, and drawing/specification CAGE. This is an acceptable process for most trading 

partners using the Catalog Data transaction. However, the Navy FRC system requires the 

materiel identification be provided using the PN/CAGE combination rather than as a Drawing 

Package/specification, even when the CAGE is a Government CAGE. Failure to provide the data 

in the expected manner prevents the Navy from properly processing the transaction. 

(4) The guidance for using the Catalog Data Support transaction in support of 

hazardous materiel is clarified and expanded in this ADC. When the Navy requires a hazardous 

material, they have to look in the Navy Regional Hazardous Inventory Control System (RHICS) 

to determine which local stock number (LSN) (beginning with ‘LLN’) is associated to the 

chemical or compound required. RHICS materials are established by Naval Sea Systems 

Command (NAVSEA) to standardize their hazardous materiel inventory. The RHICS system has 

been established at the NAVSEA installations and requirements are in place for those sites to 

utilize the RHICS LSN specific to the chemical they need. When the Navy point of contact has 

the LLN #, they then request the Materiel Master from DLA’s EBS and will continue to utilize the 

number for other transactions. For example: this means all of the NSYs are mandated to utilize 

the same LLN # for toluene, another LLN # for acetylene, and another LLN # for 60% isopropyl 

alcohol.

c. Approved Change in Detail: Request DLA Transaction Services intervene during

the transmission of DLMS 832N Catalog Data transactions sent by DLA to FRC DoDAACs 

(currently N65888, N65886, and N65923) to update the transaction as described in this change. 

This update is necessary to provide a manufacture’s part number/CAGE combination when the 

drawing package/specification information is provided in lieu of the manufacture’s part 

number/CAGE combination. This gap can be recognized by the presence of a 

drawing/specification CAGE value (Code ZM) that is not used as a manufacturer’s CAGE value 

(Code W7). No other Catalog Data transactions sent to other parties will be impacted by this 

change, including those copied from the same original transmission. DLA Transaction Services 
Attachment, ADC 1135

Page 3

will use existing data content in the transaction to build a new Reference (REF) Segment; no data 

will be deleted or removed. The new REF Segment will contain a manufacturer’s part number 

and Manufacturer’s CAGE (to compensate for the data not provided by DLA). 

(1) Manufacturer’s part number is derived by copying:

 The reference drawing number (REF01 Code QZ) to the 

manufacturer’s part number (REF01 Code MF) if, and only if, there is not already a 

manufacturer’s part number (Code MF) with this value. 

 If the reference drawing number (REF01 Code QZ) is NOT provided 

in the transaction, use the drawing number (REF01 Code DG) to map to the manufacturer’s part 

number (REF01 Code MF) if, and only if, there is not already a manufacturer’s part number 

(Code MF) with this value. 

(2) Manufacturer’s CAGE is derived by copying the drawing cage (REF01 Code 

ZM) to the manufacturer’s CAGE (REF04-01 Code W7).

(3) For example:

Extract from Original 832N 

Transaction Created by DLA

DLA 

Transaction 

Services

Processing

Modified 832N Transaction

for FRC

REF~DG~NAS75-4-113 

REF~ZM~78286 

REF~MF~NAS75-4-113~~W7@80205

REF~DG~NAS75-4-113 

REF~ZM~78286 

REF~MF~NAS75-4-113~~W7@80205

REF~MF~NAS75-4-113~~W7@78286

Staffing Note: Typically the part number and CAGE will differ, but not always. In drawing 

situations, it is common for manufacturers to utilize the drawing number for their part number. 

So several CAGE’s have similar/same part numbers.

d. Revisions to DLM 4000.25:

(1) Revise 832N IC as shown:

Item 

#

Location DLMS 4030 832N

Catalog Data Support

Reason

1.

DLMS 

Introductory 

Notes

Add ADC 1135 to DLMS Introductory Note 5:

- ADC 1135, DLMS 832N Catalog Data Support Mapping Update at 

DLA Transaction Services to Support Navy Fleet Readiness Center 

(FRC)

Identifies DLMS

Changes included in the

DLMS IC.

2. 2/REF01/0400 Revise DLMS Notes for Code MF as shown:

DG Drawing Number

QZ Reference Drawing Number

Provided to document 

the data mapping 

requirement.
Attachment, ADC 1135

Page 4

DLMS Note: Identifies the Detailed Drawing Piece Number. 

Indicates the specific item within the drawing being referenced.

MF Manufacturers Part Number

DLMS Note:

1. Use to identify the part number when the primary identification is 

an LSN. Identify the CAGE in REF-04.

2. For Navy FRC, this may be the value originally provided by DLA 

as the drawing reference number (REF01 Code QZ) or, if not 

available, the drawing number (REF01 Code DG), remapped to this 

position by DLA Transaction Services to facilitate Navy processing 

of this transaction. Refer to ADC 1135.

ZM Manufacturer Number

DLMS Note:

Use to identify the manufacturer’s CAGE Code associated with the 

drawing number.

3. 2/REF04-

01/0400

Revise DLMS Notes for Code W7 as shown:

W7 Commercial and Government Entity (CAGE) Code

DLMS Note: 

1. Use with part number to identify the manufacturer’s CAGE.

2. Where authorized, use the 2/N101-02/2300 to provide the 

manufacturer/supply name if the manufacturer’s CAGE is not known 

or not assigned.

3. For Navy FRC, this may be the value originally provided by DLA 

as the drawing number CAGE (REF01 Code ZM) remapped to this 

position by DLA Transaction Services to facilitate Navy processing 

of this transaction. Refer to ADC 1135.

Provided to document 

the data mapping 

requirement.

(2) Revise DLM 4000.25, Volume 2, Chapter 23, Catalog Data Support as shown 

in the enclosure.

e. Transaction Flow: No change to current transaction flow. This change will result in 

832N transactions directed to FRCs being altered by DLA Transaction Services DAAS and, thus 

these transactions will differ from the same transaction disseminated to other recipients, such as 

DLA Distribution Standard System (DSS).

f. Alternatives: Navy would need to change Navy Depot Maintenance System (NDMS) 

to read and store the REF Code QZ/DG/ZM values from the 832N.

g. Proposed DLMS Change 1135 Staffing Response/Comment Resolution:

Originator Response/Comment Disposition

1. DLA Concur Noted.

2. Air Force Concur Noted.

3. Marine Corps Concur Noted.
Attachment, ADC 1135

Page 5

Originator Response/Comment Disposition

4. USTRANSCOM Abstains. There is no impact to USTRANSCOM.

systems based on this change.

Noted.

5. REASON FOR CHANGE: FRC sites use NDMS as the system to receive and process the 

832N from DLA. NDMS stores all of the CAGE/PN combinations in a table and an NDMS user 

selects a single CAGE and part number per stock number for association in the NDMS Materiel 

Master. The drawing number and revision data is not stored in NDMS, so the Navy system 

doesn’t capture part identification when a part number/Government CAGE is applicable. The 

mapping adjustment for the inbound transaction to NDMS will allow the Navy to receipt the 

materiel properly, reduces potential reporting of discrepancies, and removes potential for 

production delays. The approach used for a mapping change at DLA Transaction Services 

minimizes impact to all the other trading partners.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: DLA Enterprise Business System (EBS) and NDMS will reflect the 

same PN/CAGE per stock number without significant reprogramming by the FRC or DLA. 

b. Disadvantages: Authorizes a DLA Transaction Services mapping change as an 

approved alternative to proper mapping by the receiving system.

7. ADDITIONAL FUNCTIONAL REQUIREMENTS: There will be an ongoing 

requirement for DLA to advise DLA Transaction Services should any additional FRC DoDAACs 

need to be added to these procedures for 832N mapping adjustment.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Implementation scheduled 

for November 2014.

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Use of the DAAS mapping technique provides 

cost avoidance for either sending or receiving trading partner(s).

10. IMPACT:

a. New DLMS Data Elements: None.

b. Changes to DLMS Data Elements: None.

c. Automated Information Systems (AIS): None.

d. DLA Transaction Services: Remapping of 832N as documented above.

e. Non-DLM 4000.25 Series Publications: None identified.
Enclosure, ADC 1135

Page 1

Enclosure, DLM Revisions

Revise DLM 4000.25, Volume 2, Chapter 23, Catalog Data Support as indicated in red, bold 

italics. Additionally, an administrative update is required throughout this chapter to change 

“shall” to “will”.

C23.3. PROCEDURES – NAVY INTERFACE

C23.3.1. Upon data conversion, all the current LSNs and non-DLA managed materiel 

masters from the FRC and NSY systems shall migrate to EBS. DLA managed items will be 

identified and materiel master record will extended to each site as applicable. This shall 

provide a base line for the materiel currently used at the BRAC sites. 

C23.3.2. The catalog data shall be applicable to new item inductions, FLIS change notices 

for DLA items and non-DLA managed items, as well as Navy-assigned LSNs. Manual updates 

for user unique data elements will be included in the process. Since DLA shall purchase, store, 

and sell these items to industrial activities, DLA shall have this data resident in EBS and shall 

provide visibility and updates to the Navy systems via the DLMS 832N IA Catalog Data Support 

transaction. 

C23.3.3. EBS shall also maintain site specific materiel master records for Depot Level 

Repairable, Nuclear Support Consumables, or Program Owned Material (even cognizance 

(COG)) items to provide updates pertaining to FLIS data or user unique data elements to the 

FRC or NSY sites. DLMS 832N IA Catalog Data Support change transactions shall be provided 

to applicable sites based on FLIS updates or end user changes to user defined data elements for 

these items.

C23.3.4. Web-based Query. When new items are needed by any of these sites, the 

capability is required to create new materiel masters or update user defined data elements to 

existing materiel masters directly into EBS through a user unique screen. This application within 

EBS shall prompt users for mandatory fields and user defined fields for new entries, that may be 

optional depending upon the site (FRC/NSY). The screen shall allow the user to query the 

current EBS data base and determine if an NSN or LSN already exists within EBS. 

C23.3.5. If an existing record is found, and EBS does not currently reflect the materiel 

master is extended to the user site, based on user response, the materiel shall be extended to the 

user site and an DLMS 832N IA Catalog Data Support transaction shall be sent to user site and 

identified as an ‘ADD’ record. 

C23.3.6. When no record is found within EBS, the system shall query the FLIS reference 

master data environment (RMDE) to identify any associated NSN. Once the materiel master is 

created in EBS, an DLMS 832N IA Catalog Data Support transaction shall be sent to the 

applicable FRC or NSY site. If found, the user shall have the option to build a materiel master 

record created with FLIS data and any mandatory user unique data elements in EBS based on 

user response/input. EBS shall then format a DLMS 832N IA Catalog Data Support transaction. 

This DLMS 832N IA Catalog Data Support transaction shall be identified as an ‘ADD’ and shall 

be sent to the appropriate NSY/FRC site via DLA Transaction Services. 
Enclosure, ADC 1135

Page 2

C23.3.7. If no NSN is found in FLIS, the user shall have the option to add a materiel 

master identified by an EBS assigned LSN. EBS has logic that defaults specific mandatory FLIS 

data elements, and prompts the user for those for which a default cannot be determined. EBS 

shall then format a DLMS 832N IA Catalog Data Support transaction identified as an “ADD”

and send it to the site identified by the user and also furnish a copy to the instance of DSS at the 

same site. 

C23.3.8. Materiel Identification. Cataloging data shall be categorized by two methods of 

materiel identification

C23.3.8.1. Items identified by NSN. For these, DLA shall relay FLIS catalog 

information in the absence of a Navy-FLIS interface. DLA shall also incorporate additional 

DLA/Navy unique content.

C23.3.8.2. Items identified by LSN. There shall be four configurations of LSN 

materiel numbers within EBS. 

C23.3.8.2.1. Items Cataloged with an NSN but issued to the Navy by Unit of 

Use. EBS shall assign a unique LSN using the existing data associated with the original NSN. 

All transactions for this item shall be recorded within EBS under the LSN. There shall be a 

cross-reference on the materiel master from the LSN to the NSN, and on the NSN to the LSN. 

LSNs in this category shall use the following construct: 5975-U0-000-1234.

C23.3.8.2.2. Items Identified within a Navy System (e.g., Materiel Access 

Technology (MAT) or Manufacturing Resource Planning II (MRP II)) by LSN. These LSNs 

shall be migrated into EBS. EBS shall continue to process transactions against these numbers 

and modification shall be done through user unique screen application by end users. Updates 

shall be sent to applicable sites based on these updates. LSNs in this category will use the 

following construct: 5315- L*-00-9876. 

C23.3.8.2.3. Items with no current LSN or NSN assigned to the Cage and Part 

Number combination within EBS or FLIS. EBS shall allow end users to create a materiel master 

for these items via the user unique screen application and systemically assign an LSN. Updates 

shall be sent to applicable sites based on the initial creation and any subsequent updates based on 

end user input. These LSNs will be established based on Federal Supply Classification (FSC) 

with a serial number range of LN0000001 through LN9999999.

C23.3.8.2.4. Hazardous Materiel under Regional Hazardous Inventory Control 

System (RHICS). For items for which a materiel master is needed to identify hazardous materiel 

under RHICS, an LSN identifying the RHICS cataloged or created “LLN” numbers shall be used 

if no NSN is assigned. LSNs in this category will use the following construct: 6810-LL-N00-

0001.

C23.3.8.2.4.1. EBS will determine if there is an existing materiel master 

record of the RHICS materiel beginning with LLN (first 3 digits). When there is an existing 

materiel master, user will be prompted to enter user unique data elements to extend MMR and 

EBS will return a DLMS 832N Catalog Data Support transaction identified as an “ADD” 
Enclosure, ADC 1135

Page 3

record containing all agreed to data elements to build a record in MAT and pass a copy to 

DSS.

C23.3.8.2.4.2. If no materiel master record exists for the RHICS 

hazardous materiel, the user will be prompted for mandatory fields and user defined fields for 

new entries using the RHICS data base elements. The key is that only one RHICS LLN 

number will be used for like materiel, thereby having only one LLN number per hazardous 

materiel for all users. When the query is for an LLN, the DLMS 832N Catalog Data Support 

transaction will be an output transaction to MAT and a copy will be furnished to the 

applicable DSS site. 

C23.3.8.2.5. Navy Nuclear Material numbers shall be created in EBS, via the 

user unique screen application and the user shall assign an “LLR” material number. These 

materials are unique and shall only have one per material. LSNs in this category shall use the 

following construct: LL-R**-****.

C23.3.8.3. New Records. Upon creation of new materiel identification content 

applicable to this process, EBS shall build the materiel master, apply the catalog data to the 

identified sites (extend to the user sites), and format an DLMS 832N IA Catalog Data Support 

transaction citing Catalog Purpose Code AA, New Catalog Record Added, that shall be sent to 

the appropriate NSY/FRC site via Defense Automatic Addressing System (DAAS). EBS shall 

provide a copy of DLMS 832N IA Catalog Data Support transactions for items identified as 

LSNs to the applicable DSS site.

C23.3.8.4. Modified Records. When the user entry modifies an existing record via the 

user unique screen application, the user shall be prompted to save changes. This shall trigger 

EBS to generate a DLMS 832N Catalog Data Support transaction citing Catalog Purpose Code 

CC, Catalog Record Changed. This record shall contain all applicable data elements to build a 

record within Navy systems (allowing overlay, vice transmission of only the modified content). 

If the change is to an existing LSN record previously provided to a DSS site, a copy of the 

change shall also be furnished. 

C23.3.8.5. Transaction Query. NSY sites shall have the additional capability to inquire 

EBS materiel master records using an DLMS 832N IA Catalog Data Support transaction citing 

Catalog Purpose Code QU, Site Query for Catalog Record, to determine if NSN or LSN or 

CAGE Code and Part Number combination exists in the EBS data base when there is no existing 

record on the internal table within the NSY Navy system. 

C23.3.8.5.1. If there is an existing materiel master within EBS for the inquired 

NSN, EBS shall extend the materiel master to the inquiry site and return an DLMS 832N IA 

Catalog Data Support transaction citing Catalog Purpose Code AA, New Catalog Record 

Added, containing all mandatory data elements to build a record in the MAT system. 

C23.3.8.5.2. If there is no materiel master within EBS for the inquired NSN, EBS 

shall inquire FLIS. When the response is positive, EBS shall build a materiel master and return 

an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA, New 

Catalog Record Added, containing all mandatory data elements to build a record in MAT system.
Enclosure, ADC 1135

Page 4

C23.3.8.5.3. If the response from FLIS for the inquired NSN is negative EBS 

shall return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code 

NN, No record exists for NSN query. MAT shall output for manual review.

C23.3.8.5.4. If there is an existing material master within EBS for the inquired 

LSN, EBS shall extend the materiel master to the inquiry site and return an DLMS 832N IA 

Catalog Data Support transaction citing Catalog Purpose Code AA, New Catalog Record 

Added, containing all mandatory data elements to build a record in MAT system. 

C23.3.8.5.5. If the response for the inquired LSN is negative EBS shall return an 

DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code NL, No record 

exits for LSN query. MAT shall output for manual review. The user may at this point enter data 

into the EBS user unique entry screen indicating the need to create a record.

C23.3.8.5.6. If there is an existing materiel master within EBS for the inquired 

‘Part Number/CAGE’, EBS shall extend the materiel master to the inquiry site and return an 

DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code AA, New 

Catalog Record Added, containing all mandatory data elements to build a record in MAT system. 

C23.3.8.5.7. If there is NO existing materiel master within EBS for the inquired 

‘part number/CAGE’, EBS shall invoke a query to FLIS. 

C23.3.8.5.7.1 When the FLIS response is positive and only one NSN is 

returned, EBS shall build the materiel master to the inquiry site and return an DLMS 832N IA 

Catalog Data Support transaction citing Catalog Purpose Code AA, New Catalog Record Added, 

containing all mandatory data elements to build a record in the MAT system. 

C23.3.8.5.7.2. When the FLIS response is positive and multiple NSNs are 

returned, EBS shall return an DLMS 832N IA Catalog Data Support transaction citing Catalog 

Purpose Code MN: Multiple NSNs for Part Number/CAGE. MAT shall output record for 

manual review. The user shall determine which NSN is applicable for their use and shall have 

the option to inquiry against the specific NSN or build the record through the EBS on-line input. 

C23.3.8.5.7.3. When the FLIS response is negative, EBS shall return an 

DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose Code NP, No NSN or 

LSN Found for Part Number/CAGE, to MAT for manual review. 

C23.3.9 Special Processing at DLA Transaction Services for Transactions to FRCs. 

In order to compensate for data mapping inconsistencies between DLA and the FRC, DLA 

Transaction Services is required to apply special mapping logic to 832N transactions 

addressed to FRC locations. These transactions will be reviewed for drawing package 

information that must be re-used to create a unique part number/CAGE combination to be 

inserted in the outgoing transaction. The new part number (REF01 Code MF) will be created

using existing data from the reference drawing number (REF01 Code QZ) or, if not available, 

the drawing number (REF01 Code DG). The associated manufacturer’s CAGE (REF04-W7) 

will be created using the drawing CAGE (REF01 Code ZM).