Attachment, ADC 447 

Page 1 

ADC 447 

Intra-DLA Revisions to the DLMS Supplement 832N, 

Catalog Data Support and Associated Procedures under RBI 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

 a. Technical POC: DLA Logistics Information Service Agency-LAR, J6B, phone: 

269.961.5723 

 b. Functional POC: DLA Logistics Information Service, J6B, phone: 269.961.5356 

2. FUNCTIONAL AREA:

 a. Primary/Secondary Functional Area: Primary: Supply/Logistics 

 b. Primary/Secondary Functional Process: Primary: Inventory Storage and 

Distribution, Material Cataloging 

3. REFERENCE: DLA J627 memorandum dated January 5, 2010, subject: Approved 

Defense Logistics Management System (DLMS) Change (ADC) 360, Procedures and Content 

Requirements for Catalog Data Support under Navy and Marine Corps BRAC (Staffed as PDC 

360/360A/360B)

4. BACKGROUND: Significant revisions subsequent to staffing are identified in yellow 

highlighting. 

 a. General: The DLA Disposition Services (formerly Defense Reutilization and 

Marketing Services (DRMS) is a worldwide presence within the Department of Defense, with 

disposal specialists in 14 foreign countries, two U.S territories, and 39 states. DLA Disposition 

Services’ mission is the execution of disposition solutions for excess and surplus property. The 

Reutilization Business Integration (RBI) project will replace the DRMS Automated Information 

System (DAISY) by integrating DLA Disposition Services business processes within the DLA 

enterprise suite of applications, including the Enterprise Business system (EBS) and the 

Distribution Standard System (DSS).

 b. Intent of the transaction: 

1. A DLA Disposition Services receiver will use a Disposition Services Local Stock 

Number (LSN) when a suitable National Stock Number (NSN) cannot be found for the turn-in 

item. EBS will only accept/process receipts for items that contain either a valid NSN or a valid 

DLA Disposition Services LSN (which will be maintained in EBS). If there is any other material 

identification associated with the turned-in item other than an NSN or Disposition Services LSN, 

the receipt will fail to process in EBS. If an item is turned in with a Military Services LSN, the 

receiver will include this information on the receipt, but it will only serve as reference 

information for the item when it is marketed on the DLA Disposition Services’ 
Attachment, ADC 447 

Page 2 

Reutilization/Transfer/Donation ((RTD) Web.1 EBS will maintain and be the source of all the 

Disposition Services LSNs. An LSN may fall into one of three categories: Usable LSNs, Scrap 

LSNs, and Batch Lot LSNs. Among these three categories there are five LSN types. A 

Disposition Services LSN Type Code is used to identify the type as: Scrap, Usable NonHazardous, Usable Hazardous Materiel, Usable Hazardous Waste, Batch Lot. Usable LSNs will 

be identified by a valid Federal Supply Class (FSC) as part of the numbering convention of the 

LSN. Scrap LSNs will be identified by using a material group (similar to FSC) of SCRP. All 

scrap LSNs will use this material group identification as well as containing a Scrap Classification 

Code (SCL). This is a three-character Disposition Services code to identify different types of 

scrap. EBS will use this list to create a unique scrap LSN by using each SCL in the number 

schema of the LSN. The numbering convention for these items will be a thirteen character 

material identification (the same number as a NSN). An example of a usable LSN would look 

like this: 1035DSGUNGT3M. An example of a scrap LSN would look like this: 

SCRPDS000A01A. The A01 is a Disposition Services SCL and the receiver would know this is 

a LSN for Scrap steel based on the SCL. The Batch Lot LSN will also be based upon the FSC. 

An example of a Batch Lot LSN would look like this: 2340DSBAT2340. 

c. Scenario for which the transaction is used: Whenever a DLA Disposition Services 

Property Disposal Specialist creates or updates an LSN, EBS will transmit to DSS an 832N 

transaction containing the LSN's data elements. Note: The 832N transaction will not be used 

for communication of Unit of Use LSNs. 

 d. Procedures, transactions, data elements, processing details in use today: Currently 

within DAISY, there aren't any checks to keep receivers from creating any LSN that they want. 

5. APPROVED CHANGE(S): 

 a. Requested change in detail: EBS plans to leverage the existing 832N transaction to 

transmit catalog information to DSS when EBS creates or updates a LSN. EBS will use an LSN 

when a DLA Disposition Services item cannot be identified by a NSN or when an item is turned 

into a DLA Disposition Services Field Office as a quantity less than the FLIS unit of measure. 

 b. Approved procedures: 

1. Since EBS will be the source for Disposition Services LSNs, EBS must notify 

DSS when it creates, changes, or deletes an LSN. EBS will use the DLMS 832N transaction to 

do so. 

2. When a Disposition Services receiver receives an item, after determining that a 

NSN cannot be identified for this item, a second search is executed to determine if an appropriate 

Disposition Services LSN exists that the receiver can use on the receipt. If an acceptable LSN 

exists, the receiver will assign this LSN to the turn in item. If through his/her research an 

acceptable usable LSN does not exist, the receiver will notify via email/phone the Disposition 

Services personnel responsible for maintaining these LSNs that a new LSN has to be created for 

this particular turn-in item. The Disposition Services LSN maintainer will perform research to 

verify that the LSN is indeed required, and will create the appropriate record in EBS. The 

 

1

 Please refer to PDC 434 (under development), Intra-DLA Revisions to Procedures and DLMS 527R Receipt by 

DLA Disposition Services under Reutilization Business Integration, for additional details. 
Attachment, ADC 447 

Page 3 

receiver, while he/she is waiting for the LSN to be created, will put the item aside until the LSN 

is provided.

3. Once the LSN record is created in EBS, EBS will generate an 832N transaction to 

DSS, so that it can create the LSN record as well. The triggering of the 832N will also occur if a 

change or deletion occurs with any existing Disposition Services LSN record in EBS. Note that 

Disposition Services LSNs are meant to be treated as "generic" materials since they can 

potentially cover a large and diverse number of items, so they are meant to have as little data as 

possible to account for the varied items. The required data elements are listed in the mapping 

(Enclosure 1). If there is any specific data related to the item, it will be associated at the 

Disposal Turn-In Document (DTID) Number level and not at the LSN level.

4. The rationale for the process stated in the above paragraph is to ensure that only 

one system creates and maintains the LSNs. This process is a way to ensure that there is a 

standardized set of LSNs that will be maintained in a single system. Since EBS will feed any 

LSN updates/creations related to Disposition Services LSNs to DSS, Disposition Services 

personnel just have to query DSS to get the most current list of LSNs.

5. This process only relates to a new category of LSN, the Disposition Services 

LSNs, and does not address or relate to any of the BRAC Inventory Management and Stock 

Positioning (IMSP) LSNs that will be created. If any of the BRAC IMSP Spiral 2 LSNs are used 

on the receipt, the item will fail to process.

6. If an item is turned in to the Disposition Services Field Office, and the receiver 

identifies a NSN for the item, but realizes the item is less the FLIS Unit of Issue, the receiver 

will create a new LSN in DSS by replacing the first character of the NIIN with an "R". EBS and 

DSS will each maintain a table that contains an agreed upon conversion factor for what will be 

the lowest possible assigned unit of measure for each valid FLIS Unit of Issue. When the "R" 

material is received by EBS, logic will be executed that will link it back to the NSN.

7. Enclosure 1 identifies the data content to be captured in the 832N, Catalog Data 

Support. 

8. Refer to Enclosure 2 for DLMS Supplement revisions.

9. Refer to Enclosure 3 for the DLMS Manual revisions.

 c. Alternatives: None available 

6. REASON FOR CHANGE: As a result of RBI, when a DLA Disposition Services 

Property Disposal Specialist creates an LSN in EBS, EBS is required to send to DSS the LSN 

data elements. EBS will use the DLMS 832N to transmit this data. 

7. ADVANTAGES AND DISADVANTAGES:

 a. Advantages (tangible/intangible): EBS and DSS will comply with the DLMS 832N, 

which will allow the real time transmission of LSN data to DSS when a create, change, delete 

action is triggered in EBS. 
Attachment, ADC 447 

Page 4 

 b. Disadvantages: None identified. 

8. NOTE ANY REGULATIONS OR GUIDANCE: DOD 4160.21-M, Defense Materiel 

Disposition Manual

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: January 2011 

10. IMPACT: 

 a. Publications: 

1. Requires update to DLMS 832N as noted. 

2. Requires update to DOD 4000.25-M, DLMS, to add procedures for the DLA 

Disposition Services RBI business process. 

3. Requires update to DRMS-I 4160.14 and any related Standard Operating 

Procedures. 

 b. Automated Information Systems (AIS): 

1. DLA: Impacts EBS and DSS. 

2. Service AIS: The Services systems will not be impacted by this change. This 

change to the 832N transaction/process does not impact systems external to DLA. 

3. DLMS DATA CONTENT: 

 a. New DLMS Data Elements: There is one new DLMS data element 

established for the Disposition Services LSN Type Code (definition and code values shown in 

Enclosure 1). Existing data elements have been added to the catalog data exchange per 

Enclosure 2.

 b. Changes to DLMS Data Elements: Catalog Purpose Code is updated to 

include an additional value CP (DLA Disposition Services Catalog Data Support).
Encl 1, ADC 447 

Page 1 

Enclosure 1, 832N Data Content 

This table is based upon data content approved for use in the ADC 360 (reference 3.a) and is 

provided to illustrate data content applicable to this interface. Refer to the DLMS Supplement 

832N for specific mapping and syntax requirements. 

DS 832N 

Data Content

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements

Field 

Length

1. Catalog Purpose 

Code 

Identifies the purpose of the catalog exchange as DLA Disposition Services 

Catalog Data Support. 

Code ‘CP’ is assigned for this usage. 

2 

2. Receiver (Activity 

To) 

Identifies the activity to receive the transaction. DoDAAC only. 

For DLA Disposition Services, these transactions will always be sent to the 

DoDAAC of the DLA Disposition Services Field Office operating under DSS. 

6 

3. Submitter (Activity 

From) 

Identifies the activity preparing this transaction. DoDAAC only. 

For DLA Disposition Services, these transactions are always from SC4400. 

6 

4. Catalog Transaction 

Purpose Code 

Identifies the purpose of the catalog data transaction. 

Applicable codes for DLA Disposition Services: 

AA: New Catalog Record Added. 

CC: Catalog Record Changed. 

DD: Catalog Record Deleted. 

2 

5. Material 

Identification 

(primary and 

secondary): 

Local Stock Number 

(LSN) 

or

National Stock 

Number (NSN) 

or 

CAGE and 

Part Number 

The primary material identification is normally the number identification by 

which the material is to be stored. The secondary material identification is the 

cross reference information for interpretation or further description of the 

primary identification (for example, if the primary material identification is an 

LSN, the secondary/cross-reference information might be the CAGE and part 

number). 

For Add and Change records, the primary material ID will be either an NSN or 

LSN. 

 

13 

6. Commodity Name Nomenclature/description for the item. 48 

7. Item Description Clear text description of the item. Input as10 lines up to 80 characters each. 10x80 

8. Price The 11 position acquisition price which will be transmitted as 9 digits dollars, 

decimal point, and 2 digits cents. 

R9.2 

9. Unit of Issue Local Stock Numbers will be the unit of issue as designated by the end user 

when an LSN is assigned. 

2 

10. Precious Metals 

Indicator Code 

Code used to identify items that have precious metals as part of their content. 

FLIS DRN 0802 

1 

 

2

 Identification of the Data Record Number (DRN) denotes an established data element within FLIS. The value 

carried in the catalog data support transaction will equal that in FLIS. FLIS Procedures, Volume 12 identifies and 

describes all item-of-supply and management data element, terms, and acronyms in the FLIS that have been 

assigned a DRN. 
Encl 1, ADC 447 

Page 2 

DS 832N 

Data Content

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements

Field 

Length

11. Controlled Inventory 

Item Code 

Code indicating the security classification or security risk or pilferage controls 

required for storage and transportation of DoD assets. 

FLIS DRN 2863 

1 

12. Demilitarization 

Code 

Code indicating to what degree an item must be destroyed or mutilated prior to 

disposal. Inclusion of the DEMIL Code is optional. FLIS DRN 0167 

1 

13. Hazardous Materiel 

Content Code 

Code used for storage purposes to ensure that incompatible hazards are not 

stored next to one another. The hazardous characteristics code visible in the 

Federal Logistics Information System (FLIS) pertains to the latest formulation of 

this item. Additional information may reside in the Hazardous Material 

Information System (HMIS) for a different formulation of the same CAGE/part 

number. 

2 

14. Disposition Services 

LSN Type Code 

Code identifies the type of Disposition Services LSN applicable to the three LSN 

categories, Usable LSNs, Scrap LSNs, and Batch Lot LSNs. In this context, a 

batch lot is the physical grouping of like items that would appeal to 

Reutilization/Transfer/Donation customers. A batch lot consolidates multiple 

DTIDs under a single "cover" DTID. The objective of a batch lot is to reduce 

time and costs related to physical handling and administrative processes required 

for receiving items individually. 

S Scrap 

N Usable Non-Hazardous 

M Usable Hazardous Material 

W Usable Hazardous Waste 

B Batch Lot 

1 
Encl 2, ADC 447 

Page 1 

Enclosure 2, DLMS Supplement Revisions 

Location DS 832N Revisions Reason 

1. Page 1-2, Introductory 

Notes 

Add ADC 447 to Introductory note 

- ADC 447, Intra-DLA Revisions to the DLMS Supplement 

832N, Catalog Data Support, and associated Procedures 

under RBI. 

Revise existing Federal Note as shown: 

1. This transaction provides visibility of cataloging data used 

for requisitioning, inventory management, storage and 

distribution functions supporting maintenance/Industrial 

activities (IAs) and DLA Disposition Services. 

Add new DLMS Note 2 as follows and renumber subsequent 

notes: 

2. This transaction may be used for the DLA Disposition 

Services Catalog Data Support Transaction. This 

transaction supports the DLA Reutilization Business 

Integration (RBI). The resulting interface has 

applicability for DLA Disposition Services, DLA 

Distribution Depots, and DLA Disposition Services Field 

Offices. 

Add new DLMS Note 6(e) as follows: 

(e) Items received by DLA Disposition Services Field 

Offices that cannot be identified to a NSN that are 

assigned an LSN.

 

To identify 

DLMS changes 

included in the 

DS and clarify 

new usage. 
Encl 2, ADC 447 

Page 2 

Location DS 832N Revisions Reason 

2. 1/BCT01/0200 Add New Qualifier and DLMS Note: 

CP Customized Catalog 

DLMS Note: 

Use to identify catalog data support communicated 

between DLA Disposition Services, DLA Disposition 

Services Field Offices, and Distribution Depots supporting 

Reutilization Business Integration (RBI). Catalog data 

support transactions identified by BCT01=CP are referred 

to in this document as ‘DLA Disposition Services Catalog 

Data Support.” 

A new value is 

added to 

distinguish 

catalog data 

support for DLA 

Disposition 

Services. 

3. 2/LIN01/0100 Add new Note 2 for Assigned Identification:

1. Must use to identify the purpose of the transaction. Cite 

the applicable Catalog Purpose Code: 

2. For DLA Disposition Services Catalog Data Support 

(Catalog Purpose Code CP) only codes AA, CC, and DD 

are applicable. 

AA: New Catalog Record Added. 

CC: Catalog Record Changed. 

DD: Catalog Record Deleted. 

QU: Site Query for Catalog Record 

MN: Multiple NSNs for Part Number/CAGE 

NN: No record exists for NSN query 

NL: No record exists for LSN query 

NP: No NSN or LSN Found for Part Number/CAGE 

RN: NSN Replaced 

RS: Use NSN When Exhausted 

SN: NSN Substituted 

NS: NSN Superseded 

DN: NSN Discontinued; no Replacement 

Identifies 

planned usage. 
Encl 2, ADC 447 

Page 3 

Location DS 832N Revisions Reason 

4. 2/LIN06/0100 Add new Qualifier TP and associated note. 

TP Product Type Code 

DLMS Note: Use only for DLA Disposition Services 

Catalog Data Support (Catalog Purpose Code CP) to 

identify the Disposition Services LSN Type Code. Use only 

with LIN04=SW. Each Disposition Service LSN will be 

assigned to a specific category/type using the following 

values. 

S Scrap 

N Usable Non-Hazardous 

M Usable Hazardous Material 

W Usable Hazardous Waste 

B Batch Lot 

Identifies 

planned usage. 

5. 2/LQ01/3400 Add new Qualifier HMC and associated notes. 

HMC Hazardous Materiel Content Code 

DLMS Note: 

1. Use only for DLA Disposition Services Catalog Data 

Support (Catalog Purpose Code CP) to identify the 

applicable Hazardous Materiel Content Code. (FLIS DRN

2579) 

2. Implementation Note: This is an X12 Migration Code 

approved for use in Version 5020. Implementers must 

manually update 4030 software to recognize this code.

Identifies 

planned usage. 

6. 2/CTP05-01/1700 Add new Note 2 for Unit or Basis for Measurement Code

DLMS Note: 

1. Must use to identify the standard Unit of Issue. 

2. Also used for LSNs where unit of use is not applicable.

Provides 

clarification 

 
Encl 3, ADC 447 

Page 1 

Enclosure 3, DLMS Manual Revisions 

Revise DoD 4000.25-M, Volume II, Chapter 16 as follows: 

16.6. PROCESSING MATERIAL AND MAINTAINING ACCOUNTABILITY BY THE DLA 

DISPOSITION SERVICES AND THE DLA DISPOSITION SERVICES FIELD OFFICES 

 16.6.1. Local Stock Numbers (LSN) and Unit of Use. There are several instances when an 

LSN shall be used by the DLA Disposition Services Field Office and supported activities. 

These LSNs fall into three categories: Usable LSNs, Scrap LSNs, and Batch Lot LSNs. 

Within these three categories, are five different LSN types: Scrap, Usable Non-Hazardous, 

Usable Hazardous Materiel, Usable Hazardous Waste, and Batch Lot. 

 16.6.1.1. Usable Local Stock Numbers (LSN). When property is turned in to 

the Disposition Services Field Office identified by an LSN, cannot be further identified to an 

NSN, and is determined to be usable, a Disposition Services LSN shall be assigned (if one does 

not already exist) and shall be used as identification of the property throughout the disposition 

services process. Usable LSNs shall be identified by valid FSC as part of the numbering 

convention, e.g., 1035-DS-GUN-GT3M. The original LSN used by a generator to turn in 

material shall be included as a reference on the receipt and shall serve as reference 

information for the item when it is marketed on the RTD website. 

 16.6.1.2. Scrap LSN. Property downgraded to scrap during or subsequent to 

receipt shall be assigned a Scrap LSN. Scrap LSNs shall be identified by using a materiel 

group of SCRP. All scrap LSNs shall use this materiel group identification as well as 

containing a Scrap Classification Code (SCL). The SCL is a three-character disposition 

services code to identify different types of scrap and appears in positions 11-13 of the Scrap 

LSN, e.g., SCRP-DS-000-A01A. 

 16.6.1.3. Batch Lot LSN. Batch Lot LSNs are used to identify the physical 

grouping of like items that would appeal to reutilization/transfer/donation customers. A batch 

lot consolidates multiple DTIDs under a single “cover” DTID. The objective of a batch lot is 

to reduce time and costs related to the physical handling and administrative processes for 

receiving items individually. Batch Lot LSNs will be identified by a valid FSC as part of the 

numbering convention, e.g., 2340-DS-BAT-2340. 

 16.6.2. Unit of Use. When the materiel turned in to the DLA Disposition Services 

Field Office can be identified to an NSN but the quantity is less than the FLIS Unit of Issue, 

the DLA Disposition Services Field Office will create a new LSN by replacing the first 

character of the NIIN, e.g., 5965-R1-123-4567, with an "R". DLA Disposition Services and 

Field Offices’ use of DLMS transactions, including the DLMS 869C, Customer Cancellation 

Request, the DLMS 940R, MRO and the DLMS 945A Material Release Confirmation, shall 

carry the Unit of Use LSN, the Cross-Reference NSN, and the Unit of Use Indicator. When 

the Unit of Use Indicator is present in the transaction, the quantity and unit of measure values 

associated with this transaction are applicable to the unit of use. However, the property shall 
Encl 3, ADC 447 

Page 2 

be identified to its NSN for RTD. This form of LSN for Unit of Use will not be visible to the 

customer, as its use shall only be between DLA Disposition Services and their Field Offices. 

 16.6.3. DLA Disposition Services shall be the source for all Disposition Services LSNs and 

will notify DLA Disposition Services Field Office via a DLMS 832N, Catalog Data Support 

transaction when it creates, changes or deletes an LSN. These DLMS 832N transactions shall 

identify both the LSN and the LSN Type Code (S-Scrap, N-Usable Non-Hazardous, M-Usable 

Hazardous Material, W-Usable Hazardous Waste, and B-Batch Lot). The DLA Disposition 

Services Field Office will use the DLMS 832N to create or update its LSN records. 

 16.6.4. The DLMS 832N shall not be used between DLA Disposition Services and their 

Field Offices for creation or update of Unit of Use LSNs, rather both shall maintain tables 

which contain agreed upon conversion factors for what will be the lowest possible assigned 

unit of measure for each valid Federal Logistics Information System (FLIS) Unit of Issue. 

When receipts for Unit of Use LSN materiel are processed by DLA Disposition Services, 

internal logic shall link the materiel back to the NSN. 
Encl 4, ADC 447 

Page 1 

Enclosure 4, Response to PDC Staffing 

Originator Response/Comment Disposition 

1. Navy Navy concurs with PDC 435 as written and submits no 

additional changes or amendments. 

Noted. 

2. Army HQDA DCS G-44(S) concurs without comment. Noted. 

3. Marine Corps Concur with comment: 

1. This process will not impact the Marine Corps as long 

as it remains localized to the DLA family of systems. 

2. Currently no major system controlling Marine Corps 

inventory will allow for local NSN assignments for the 

purpose of disposing assets. 

3. GCSS—MC will not accept LSNs within its process 

Noted. 

4. DFAS DFAS has no comment. Noted. 

5. USTRANSCOM USTRANSCOM Abstains Noted. 

6. DLA Comments from RBI team subsequent to staffing: 

1. We have to add one additional data element to the 

832N transaction (PDC 435). The new field is HCC 

(Hazardous Category Code). This will be required for 

hazardous LSNS to be correctly identified with this 

code, so Disposition Services Receiver knows where to 

properly store the item in the warehouse. Here is a short 

write-up with definitions for the Disposition Service 

LSN Type Code. 

2. Yesterday in the phone call to discuss adding the type 

of LSN it was mentioned that DSS would allow updates 

to the LSNs that EBS has assigned for Disposition 

Services. This PDC clearly states EBS will maintain 

and be the source of all of the Disposition Services 

LSNS. It sounds like you will need a process for 

Disposition Services to process an update/deletion/etc. 

which would invoke the DLMS 832N to be sent to DSS 

for the appropriate update/deletion/etc. 

3. Insert new code to identify the Disposition Services 

LSN Type Code. Each Disposition Service LSN will be 

assigned to a specific category/type using the following 

values. 

 S Scrap 

 N Usable Non-Hazardous 

 M Usable Hazardous Material 

 W Usable Hazardous Waste 

 B Batch Lot 

1. HCC added to ADC. 

2. The DLA Disposition 

Services Catalog Data Support 

transaction currently allows 

EBS to send addition, change, 

and deletions to DSS. 

However, this ADC does not 

include procedures for DSS to 

systemically send changes to 

EBS. If Field Office personnel 

need a LSN changed they will 

reach out to the material 

maintainer at Disposition 

Services HQ to make the update 

which will trigger an 832N 

update to DSS. 

3. Disposition Services LSN 

Type Code added to ADC 

(definition of Batch Lot 

provided by RBI team for 

inclusion in DLMS dictionary). 
Encl 4, ADC 447 

Page 2 

Originator Response/Comment Disposition 

7. The following comments are from DLA Disposition. 

1. Insert excess and surplus property in the following 

sentence: DLA Disposition Services mission is the 

execution of disposition solutions for excess military 

property. 

2. PDC states: If there is any other material 

identification associated with the turned-in item other 

than an NSN or Disposition Services LSN, the receipt 

will fail to process in EBS. 

Is a 917 Reject Form completed at this point? 

3. PDC states: EBS will maintain and be the source of 

all the Disposition Services LSNs. 

Will the LSN list include DEMIL codes and unit of 

issue for established LSNs? If not, who will determine 

the DEMIL code and the unit issue for established 

LSNs? 

4. Replace with Property Disposal Specialist in the 

following sentence: Disposition Services Product 

Specialist creates or updates an LSN, EBS will transmit 

to DSS an 832N transaction containing the LSN's data 

elements. 

5. PDC states: If an acceptable LSN exists, the receiver 

will assign this LSN to the turn in item. 

Who determines the DEMIL code? 

6. PDC states: The receiver, while he/she is waiting for 

the LSN to be created, will put the item aside until the 

LSN is provided. 

Is this a 917? If so, how will we capture this in the 

automated system? Does the receiver place the item in a 

regular 917 area? How long will the receiver wait for a 

response? Are time frames associated with the reject 

and hold? 

7. Replace with Property Disposal Specialist in the 

following sentence: Specialist creates an LSN in EBS, 

EBS is required to send to DSS the LSN data elements. 

8. Price: Is this a unit price or extended price? 

9. Who determines PMIC for a LSN item? Is it 

1. Done. 

2. Coordination will be required 

between DSS and EBS to 

update the receipt with the 

appropriate material and the 

receipt will be reprocessed. 

3. If there is to be an associated 

DEMIL Code for the item it 

will be determined by the 

property disposal specialists at 

time of material creation in 

EBS. Otherwise, the receiver 

will assign a DEMIL Code if 

during inspection it is deemed 

necessary for the item. The 

majority of LSNs will have a 

unit of issue of EA except in the 

cases where the commodity is a 

weight or liquid item and then 

the appropriate unit of issue will 

be used for these LSNs. 

4. Done 

5. DEMIL Code will be 

determined by the receiver at 

the time of turn-in. Based on 

Receiver’s visual inspection of 

the item and possible previous 

experience working with the 

item. He/she will be able to 

determine if an appropriately 

assigned DEMIL Code is 

needed. 

6. There will be a holding area 

for these items at the Field 

Office location. The receiver 

will contact the material 

specialist at Disposition 

Services HQ, and explain the 

item. The property disposal 

specialist will create the LSN 

record in EBS which will 
Encl 4, ADC 447 

Page 3 

Originator Response/Comment Disposition 

included on the list of generic LSNs? 

10. DEMIL code is identified as option. Does this 

indicate that a DEMIL Code will be optional upon 

receipt of a LSN? Who determines the DEMIL code on 

a LSN? 

11. Under Publications, insert “Update to DRMS-I 

4160.14 and any related SOPs (Standard Operating 

Procedures)” 

trigger an 832N to DSS for 

creation. This process will take 

approximately an hour from 

first notification to creation of 

record in DSS. 

7. Done 

8. This will be a unit price. 

9. PMIC can be determined by 

the actual LSN record created in 

EBS or it can be determined by 

the receiver at time of turn-in 

based on a physical inspection 

of the item. 

10. It will not be required for 

LSNs unless property disposal 

specialists feel need to create a 

“specific” DEMIL Code LSN. 

This DEMIL Code will be 

identified by receiver at time of 

turn-in during physical 

inspection. 

11. Done. 

8. DLA's AIT team provided this comment: "LSN from 

different entities may overlap and be for different items 

(i.e. duplicate LSN from different entities). This may 

cause confusion and wrong disposition instruction to be 

generated." 

All LSNs will be managed in 

EBS. There cannot be duplicate 

LSN information. If a Service 

turns in an item using a Serviceassigned LSN, it will be 

assigned a Disposition Services 

LSN with the Service’s LSN 

maintained in reference field.