ADC 466 Attachment, Page 1

ADC 466

Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA

Disposition Services under Reutilization Business Integration (RBI)

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: DLA Logistics Information Service, 269.961.5723

b. Functional POC: DLA Disposition Services, 269.961.5906

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/ Logistics

b. Primary/Secondary Functional Process: Requisitioning

3. REFERENCES:

a. ADC 410/410A, Approved DLMS Change (ADC) 410, Intra-DLA Revision to Procedures 

and DLMS 527D Pre-Positioned Materiel Receipt (PMR) to Add Disposition Container ID for use 

with Relocation of Material between DLA Disposition Field Offices Under RBI (Addendum Adds 

Defense Turn-in Document (DTID) Number), dated February 25, 2011 and October 12, 2011.

b. ADC 422, Revises DLMS Supplement 856S, Shipment Status, in Support of RBI, dated 

October 6, 2011.

c. ADC 434, Intra-DLA Revisions to the DLMS 940R, Materiel Release, and Associated 

Procedures to Support Directed Release of Materiel under RBI, dated November 09, 2011.

d. ADC 449, Intra-DLA Revisions to the DLMS 945A, Materiel Release Advice, Cancellation 

Reason Code, Management Codes, and Associated Procedures under RBI, dated November 21, 2011.

e. ADC 455/455A, Revisions to Procedures and Supply Status (DLMS 870S/Document 

Identifier Code (DIC) AE_) from DLA Disposition Services under RBI, dated February 6, 2012.

f. ADC 459/459A, DLMS Transactions, Discrepancy Codes, SDR Type/Disposition Services 

Type Codes, and Associated Procedures to Support Supply Discrepancy Reports (SDRs) under RBI,

November 28, 2011 and December 30, 2011.

g. ADC 460, Revises DLMS Supplement 869C, Requisition Cancellation, and Associated 

Procedures in Support of RBI, dated February 21, 2012.

4. BACKGROUND: The DLA Disposition Services (formerly Defense Reutilization and Marketing 

Service) 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 military property. The Reutilization Business Integration 

(RBI) project will replace the DLA Disposition Services Automated Information System (DAISY) by 

integrating DLA Disposition Services’ business processes within the DLA enterprise suite of 
ADC 466 Attachment, Page 2

applications, including the DLA Distribution Standard System (DSS) and the Enterprise Business 

System (EBS). Staffing Note: Significant revisions subsequent to staffing of the proposed change are 

highlighted.

a. Intent of the revisions: 

(1) In addition to Service supply system-generated requisitions, under RBI, two additional 

source systems will transmit 511R Requisition transactions for Disposition Services’ property to EBS: 

U.S. General Services Administration (GSA) Personal Property for Reuse and Sale 

(http://www.gsa.gov/portal/category/21045) and the DLA Disposition Services’

Reutilization/Transfer/Donation (RTD) (www.dispositionservices.dla.mil/rtd03/index.shtml) web 

applications. This ADC will describe the process for 511R requisition transactions generated from 

these two systems to EBS. Additional data elements will need to be added to the 511R transaction to 

account for requisition processes from GSA and the RTD Web.

(2) Changes to the overall requisition process as it relates to RBI will be explained in 

greater detail in section 4.b. below.

(3) In addition, this change further updates numerous DLMS transactions previously 

modified to support RBI under referenced ADCs. These updates are to accommodate inclusion of the 

controlling document number suffix code and/or a Defense Turn-In Document (DTID) Number Suffix 

Code when either or both of these are applicable. This requires flexible mapping to allow variations in 

content. This DLMS Change identifies revisions to the following DLMS transactions: 511R, 511M, 

527D, 527R, 842A/W, 856S, 869C, 869F, 870S, 940R, and 945A. 

b. Scenario applicable to requisitioning:

(1) The process starts when property is turned in to DLA Disposition Services and is 

assigned to a disposition category of Reutilization (RU). This category is assigned when the receiver 

at the DLA Disposition Services Field Office sends EBS information related to the item being turned 

in via the synchronous interface. The receiver will, upon receiving the disposition category from EBS, 

submit a DLMS 527R (D6A/B) receipt to EBS. 1

(2) When EBS receives the item, it goes into an inventory and aging cycle. This typically 

is a 42-day cycle that all items go through that determines the day of the cycle the item is in, who is 

eligible to requisition the item (some items have a shortened aging cycle). There are four different 

screening periods within the RTD formal screening cycle within CONUS: DOD Formal and Special 

Programs2 (Screening Cycle Code DOD), General Services Administration (Screening Cycle Code 

GSA), Donation (Screening Cycle Code DON), and a second RTD screening cycle for items that are 

eligible to RTD customers (Screening Cycle Code RTD2). OCONUS cycles are FEPP (for DOD, 

DOD special Programs, and Federal Civil Agencies; FEPD (for Donation); and RTD2 for all. DOD

customers can requisition an item at any time during the cycle; however, other agencies and groups 

only have access to the item once it reaches a certain day within that 42-day cycle. If the item goes 

through the full 42-day cycle and it is not requisitioned, the item is either assigned to a Disposal 

 1 Refer to ADC 412 (PDC 436), Intra-DLA Change - Establish New DLMS Supplement 846C, DLA Disposition Category 

Update Transaction and Procedures for use by DLA Disposition Services under RBI, for additional description of this 

process.

2 Refer to ADC 384A Addendum, Special Programs for Non-DoD/Non Federal Agency Requisitioners; Additions in 

Support of DLA Disposition Services Under RBI, for additional information about special programs
ADC 466 Attachment, Page 3

disposition category (based on controlled property business rules), or it is assigned a Sales status. 

Items assigned a Disposal status trigger the 846C to DSS to move the item to DSS Ultimate Disposal 

(UD) for disposal. Items assigned “Sales” category, if eligible for the Commercial Venture (CV) or 

Scrap Venture (SV) contracts, are sent to DSS to identify these items as CV-eligible/SV-eligible and 

will be placed in a CV/SV area for the contractor to review.3

(3) Items that are within the 42-day screening cycles are reported daily via a property 

characteristics flat file to the RTD Web (if the Screening Cycle Code is DOD or RTD2) and to GSA (if 

in Screening Cycle Code GSA or DON). This daily file to RTD Web and GSA notifies both systems 

of the available items.

(4) With one exception, all requisitions that are generated from the RTD Web and GSA are 

free-issue items (non-cost issue). The only exception is Foreign Military Sales (FMS) which may 

generate property and transportation costs. These transportation costs will be identified on the 

requisition and will also be accompanied by a Funds Appropriation (Fund Cite/Line of Accounting). 

These costs are determined by the RTD Web based on the customer profile and passed to EBS on the 

requisition. This Funds Appropriation/Funds Cite will be perpetuated to the Materiel Release Order 

(MRO) at the time the item is issued. (See staffing note on page 9 for the Funds Appropriation.)

(5) Items that are sent to the RTD Web and GSA are eligible to be requisitioned by RTD 

Web and GSA customers. The RTD Web and GSA maintain rules and regulations that determine who 

is eligible to requisition specific items. The processes are described below.

(a) RTD Web:

1. When the RTD Web receives the property characteristics file from EBS

(these will be items applicable to Screening Cycle Codes DOD or RTD2), DLA Disposition Services

will show these items on the web to all eligible customers. As documented above, the RTD Web 

contains business rules and regulations that determine what property (identified by Disposal Turn-in 

Document (DTID) Number) are eligible to be viewed and requisitioned by eligible customers. In 

addition to this, the RTD Web uses prioritization logic to assign precedence to requisitions based on 

the type of customer requisitioning the item. For example, a DOD Military Service customer will 

receive a higher priority than a special programs customer. After priority is assigned to the requisition,

the RTD Web determines the customer that will receive the property. The prioritization logic will be 

applied in a 24-hour cycle. As requisitions are generated in the RTD Web, these are sent to EBS via 

DLA Transaction Services. EBS will perform the processing of the requisitions for that 24-hour 

period. RTD Web customers are able to setup customized want-lists within the RTD Web. The want 

lists enable an automatic search of inventory and provide email notification if an item they specified 

enters inventory. The customer must login to the RTD Web to initiate the requisition request if a 

desired item enters inventory (or generate a requisition from the Service supply system). At the end of 

this 24-hour cycle, depending upon the timing of the request and the highest priority for the 

requisitioned item, the property will be awarded. Priority will be verified by the RTD Web based on 

customer rules used to determine the priority of the customer. All other requisitions related to this item 

are subsequently cancelled via a notification from EBS to the RTD Web. When lower priority orders 

are cancelled, the customer will be notified from the RTD Web based on the information that EBS 

passes. Prioritization will be applied to customers based on the following criteria: 

 3 Refer to DRAFT ADC 412 for more information regarding the CV and SV process as it relates to the 846C. Refer to 

ADC 457, Intra-DLA Revisions to Procedures and DLMS 511R Requisition to Support Directed Release of Materiel (PostPost Action) by DLA Disposition Services Field Offices under RBI for additional information about this process.
ADC 466 Attachment, Page 4

• U.S. DOD military customers can assign Priority Code 1-15 (based upon Force/Activity 

Designator and Urgency of Need).

• All special programs and walk-ins default to Priority Code 15

• Humanitarian Assistance Program (HAP) Priority Code 15 only

• Law Enforcement Support Office (LESO) can update to Priority Code 15

• DOD or Service Museums Priority Code 15 only

• Computers for Learning (CFL) Priority Code 15 only

• National Guard Units can update to Priority Code 12-15. (Deploying units will be assigned

new DoDAAC with a higher priority.)

• Senior Reserve Officers Training Corp (SROTC) can update to Priority Code 12-15

• Morale, Welfare, Recreation Activities (MWRA) Priority Code 15 only

• Military Affiliated Radio System (MARS) Priority Code 15 only

• Civil Air Patrol (CAP) Priority Code 15 only

• DOD contractors Priority Code 15 only

• Foreign Military Sales (FMS) Priority Code 15 only

2. The RTD web will pass an 870S with Supply Status BQ indicating 

cancellation to the Service’s supply system, if the requisition originated from one of these systems. If 

the requisition originated from the RTD Web, then the RTD Web will simply cancel the requisition. 

When the user logs into the system he/she will see the cancellation listed in their account.

3. Two scenarios can occur that will alter this 24-hour processing cycle. 

The first scenario that can occur is for a customer who walks into the DLA Disposition Services Field 

Office and triggers a requisition from the Field Office via the RTD Web. These requisitions will be 

identified on the requisition transaction sent to EBS as “walk-in” requisitions (identified by 

Disposition Services Indicator = WALK, Utilization Code = L, and unique document number serial 

number beginning with L). EBS will verify any pending requisitions for this item (by DTID Number), 

and if the priority of the pending requisitions is lower than the walk-in requisition, this requisition will 

be processed immediately and the 24-hour process cycle will be bypassed. If, however, a “walk-in” 

requisition request is passed to EBS from the RTD Web and there is a pending order with higher 

priority, then the “walk-in” requisition will not be able to be awarded in full. If the higher priority, 

pending requisition is not for the full available quantity of the DTID, then the “walk-in” requisition 

will be awarded the difference. But, if it was for the full available quantity of the DTID, then the 

“walk-in” will not be awarded at all. Instead, EBS will send a requisition status update via the realtime interface to the RTD Web indicating if the “walk-in” requisition was able to be awarded and for 

what quantity.

4. The other scenario that will alter the 24-hour cycle is Foreign Military 

Sales (FMS). FMS customers have access to the RTD Web, and they have the option of freezing items 

that they would like to acquire. The reason items are frozen is there is an approval process 

(Department of State process) that occurs before the FMS customer is eligible to requisition the item. 

While the approval process occurs, the items are identified as frozen both in DLA Disposition Services 

(EBS) and at the Field Office (DSS), and the item will not be able to be advertised on the RTD Web to 

other customers. To freeze an item, a unique (non-DLMS) XML transaction is sent to EBS; 

Disposition Services (EBS) then “freezes” these items. If an FMS freeze is in place, the property will 

NOT be available for screening for any other customer. The daily property file sent to RTD Web will 

identify these as frozen items. Once the FMS customer receives approval to acquire the item, then a 
ADC 466 Attachment, Page 5

requisition will be sent to Disposition Services (EBS) from the RTD Web, and the item will be issued 

to the FMS customer. The process wherein Disposition Services works to determine if frozen property 

should be awarded to the FMS customer with the State Department is done outside of EBS or RTD 

Web. The FMS team at Disposition Services works with the State Department by creating a case 

number for each sale, and once approval is given by the State Department to the FMS personnel, the 

requisition is processed in the RTD Web. Personnel at the Field Offices will be able to view (via the 

RTD Web) a list of all items that are currently frozen and print out a placard to place on the frozen 

items, so that walk-in customers know that item is being held for FMS customers. 

5. The RTD Web will provide a daily asset inventory file to DLA 

Transaction Services so that the Services can generate MILSTRIP Requisitions that will originate from 

their own source systems based on the asset inventory file. DLA Transaction Services has a 

documented agreement with each customer to provide the asset inventory file under Integrated 

Development Environment (IDE). Once these requisition transactions are generated, they will be 

routed to the RTD Web. The RTD Web will verify the priority status for each requisition, include any 

additional data that is required (see attached mapping below) and then send the requisition to EBS via 

DLA Transaction Services. The standard 24-hour cycle will apply to each of these transactions once 

they are received by EBS. 

(b) General Services Administration (GSA): Items (identified by DTID number) that 

are in the GSA or DON screening cycle will be sent as part of the daily characteristics file to GSA for 

CONUS and for OCONUS FEPP and FEPD screening cycle. GSA customers will then be able to 

requisition these items by generating a MILS/DLMS requisition. A daily batch file will be sent to 

DLA Transaction Services. MILSTRIP legacy 80-record position legacy format requisitions will be 

converted by DLA Transaction Services into DLMS 511R requisitions, which will be sent to the RTD 

Web for processing. The item control number GSA passes on each requisition is the Disposal Turn in 

Document (DTID). GSA passes this along with a Document Number for each requisition passed to the 

RTD Web.

(6) MILSTRIP Requisitions by NSN: The Services have the capability to order property 

by National Stock Number (NSN) without regard to specific DTID numbers contained within the 

inventory. A Service legacy or ERP system may submit a MILSTRIP requisition, which will be routed 

by DLA Transaction Services to the RTD Web for processing (prior to transmitting the requisition to 

DLA EBS for ICP processing). The requisition, formatted as a DLMS 511R or MILSTRIP legacy 80 

record position (rp) transaction, may or may not contain the DTID. Once the RTD Web receives this 

requisition, the DLA Disposition Services’ inventory will be searched, without regard to property 

location if the DTID number is not identified by the customer (exception DLA Disposition Services 

may exclude CONUS/OCONUS, as applicable). If there is a match of property to NSN, a requisition 

document with updated information will be generated by the RTD Web for transmission to EBS. In 

some instances, the property will be physically located in multiple locations or will require multiple 

DTID numbers to satisfy the requisition quantity. When this occurs, a partial action, identified by the 

original document number sent by the customer will be filled with the DTID quantity on hand for the 

order. For the remaining open requisition quantity, RTD Web will be required to generate separate 

requisitions to DLA Disposition Services including the customer document number and sequentially 

assigned suffix codes as needed to fill the requested quantity. As these requisition transactions with 
ADC 466 Attachment, Page 6

suffix codes are being generated, RTD web will provide Supply Status (DLMS 870S/DIC AE_) with 

notification of the document number/suffix code combination.

4

Staffing Note: Use of the controlling document number suffix code as described above to provide 

separate transactions for each DTID is not consistent with MILSTRIP suffixing to identify split 

shipments. However, the DLA Disposition Services requires accountability down to the DTID level 

and only supports a single occurrence of the DTID for each document number. The originally 

proposed RTD procedure to generate unique document numbers for each DTID Number was not 

considered acceptable since these document numbers would not be recognized by the Component’s 

supply system creating a disconnect between the original requirement/due-in and the DLA 

Disposition Services response/shipment. The use of suffix codes in the manner described above will 

leverage existing Component legacy system processing to recognize and recognize/retain suffix 

codes provided via supply status and will simultaneously create the one-to-one relationship 

necessary. More extensive redesign is not feasible. Suffixing by document number to uniquely 

identify each associated DTID is, therefore, employed here as a less intrusive business model for 

RBI.

For background, under DAISY processing, the majority of transactional requisitions come in as

MILSTRIP legacy DIC A0_ transactions. If a requisition follow-up transaction (DIC AT_) is received, 

it is interpreted as a new requisitions if no matching requisition exists according to MILSTRIP. The 

materiel release order is issued by DAISY as a MILSTRIP legacy DIC A5_ to the appropriate DLA 

Disposition Services Field Office (there may be more than one issued by DAISY to satisfy one 

requisition). DAISY provides supply status transaction (legacy DIC AE8) to provide a status to the 

requesting customer. This follows Appendix B-16 of the MILSTRIP manual. The shipment status 

(legacy DIC AS_) is provided to the customer and applicable status recipients. The matching and 

selection logic is internal to DLA Disposition Services; it is not visible to the requesting customer. 

The RTD Web will continue the processing of requisitions currently being done by DAISY by 

receiving and processing the requisition transactions. EBS will handle all materiel release order 

generation. The RTD Web will be responsible for sending all requisition status updates to customers. 

The RTD Web will send supply status updates via a DLMS 870S/DIC AE_ transaction to each of its 

customers as the status of the requisition is changed/updated.

(7) Local Stock Number (LSN). LSN requisitioning will only be available via RTD Web. 

All items marketed on the RTD Web, will be either by usable LSN (Disposition Services LSN) or by 

the NSN. This provides the customers a quick reference to research items (in the case of NSN) online 

for additional information. In the case where an item is made available for requisitioning in less than 

the standard unit of issue, the resulting requisition transaction passed between the RTD Web and EBS 

will include the “Unit of Use” Indicator to define the quantity and unit of measure as applicable to unit 

of use. All subsequent transactions prepared by DLA systems will retain the “Unit of Use” Indicator. 

The LSN will be identified as the primary identification and the NSN will be provided for cross 

reference.

(8) Electronic Want List: The Services leverage an electronic want list within the RTD 

Web to reflect a future demand for specific items that may or may not be in the active DLA 

Disposition Services’ inventory. When a DTID is received within EBS, if an item has been identified 

 4 ADC 455A (PDC 496), Revisions to Procedures and DLMS 870S Supply Status from DLA Disposition Services under 

Reutilization Business Integration (RBI).
ADC 466 Attachment, Page 7

by the Service on their Want List, the Service will be notified of the item and quantity available via the 

RTD Web. The Service may submit a requisition to the RTD Web or via MILSTRIP requisition 

through the Service supply system. The item will not be automatically requisitioned. The requisition

will follow normal processing as identified above.

(9) Containerization: To facilitate RTD, DLA Disposition Services employs a 

containerization process where RTD Web will market items online by container. This allows

customers the option of either acquiring items by the full container or individual items in the container. 

In either scenario, a separate requisition number (Original Document Number) will be generated for 

each item in the container. Code R will be used in the first position of the document number serial 

number to identify an individual line item associated with an RTD Web requisition from a Disposition 

Services container. The DLMS Utilization Code will carry the corresponding code R. The generation 

of a distinct document number for each item ordered allows the customer to have visibility and status 

relative to the processing of each requisition, maintains container synchronization, and facilitates 

inventory control. When the customer selects the entire container, each individual 511R Requisition 

(Transaction Type Code A0) generated to DLA Disposition Services will include an indicator which 

communicates that the whole container is being requisitioned. The requisition number will never be 

generated at the container level. To support this process, additional data fields will be added to the 

DLMS 511R as follows: Disposition Services Container ID, Disposition Services Container Count, 

and Disposition Services Full Container Requisition Indicator. When DLA Disposition Services 

receives a requisition with the “full container ordered” indicator they will use the information to ensure 

that all requisitions for the container are received and processed appropriately. MROs generated by 

DLA Disposition Services for requisitioned items associated with a container will have the container 

ID identified on the MRO. These data elements are applicable to the requisition generated by the 

RTD Web and are not provided by any customer ordering from their internal Component ordering 

system (see MILSTRIP Requisitions by NSN section). The only way the customer will know the item 

is part of a container is by viewing items in the RTD Web. Systemically, the RTD Web will generate a 

unique requisition for each DTID contained within a DLA Disposition Services container if the 

requisitioner chooses to requisition the full DLA Disposition Services container. Each item will be 

displayed on the screen with the customer’s DoDAAC, Julian Date, and sequential serial number. 

Each item will have a Document Number assigned for each line item that makes up that container. 

Please note that this can only happen when the customer generates a requisition on the Web. 

Customers requisitioning outside the Web will not have visibility of containers and, consequently, will 

only send a requisition for a specific NIIN/DTID. Subsequently, a separate shipment status will be 

provided for each DTID within said container. Every customer using RTD Web must be assigned at 

least one DoDAAC that is used to submit requisition requests. Customers have the ability to view the

current status of all their submitted requisitions via the RTD Website. If the Services generate a 

requisition, then the RTD Web will perform identification of the item by DTID/container and include 

this information in the requisition passed to EBS. While the Services may not care about the DTID, 

Disposition Services tracks all inventory by the DTID. The DTID is viewed, in this case, as a property 

characteristic. 

(10) Post-issue tracking: DLA Disposition Services will insert an additional data element 

on the 511R Requisition called the Disposition Services Indicator. The indicator will be used 

internally to facilitate post-issue tracking. It will be generated by RTD Web based on customer rules, 

not input by a customer. It will not be perpetuated beyond the requisition. There are five different 

types of post-issue tracking applicable to the requisition. DLA Disposition Services (EBS) will store 

these Disposition Services Indicator values for future tracking of the items. The five different types of 

post-issue tracking are: Materiel Receipt Acknowledgement Required, DEMIL Certification Required, 
ADC 466 Attachment, Page 8

Mutilation Certification Required, Overseas Delivery, and Certificate of Recycling Required. The 

Disposition Services Indicator is a recurring data element and will be repeated with the applicable 

value for each applicable tracking requirement. Refer to Staffing Note for DLA Disposition Services 

on Attachment page 8.

(11) DTID and associated suffix. The DTID and associated suffix would also be on the 

Materiel Release Advice (DLMS 945A) for a denial or cancellation sent back to DLA Disposition 

Services. If at any point during the life cycle of a requisition, a change, cancellation, status update, or 

shipment status is required, the DTID and its associated suffix will be passed as part of the transaction. 

This applies to the requisition cancellation (869C), supply status (870S), requisition modification 

(511M), requisition follow-up (869F), and shipment status (856S). Note that there are exceptions

where the original DTID and associated suffix may not be retained for accountability and future 

requisitioning. This occurs only by exception when the DTID and associated suffix do not provide the 

unique accountability required by RTD (e.g., when the quantity received is found to be in different 

conditions or when the DTID and associated suffix values used by the turn-in activity match a previous 

turn-in). By exception, a Unique Control Number (UCN) will be assigned within DSS and, for this 

subset of property; the UCN will be used for accountability and will be made available for the 

subsequent requisitioning. The UCN usage will be transparent to the customer requisitioning by 

DTID. Staffing Note: The procedures in this paragraph for requisitioning by DTID and associated 

suffix are consistent with current MILSTRIP requisitioning procedures; they are called out in this 

ADC for clarification and to document transaction format updates to incorporate the DTID Suffix 

Code. The original PDC 453 documentation incorrectly stated that requisitioning by DTID suffix 

would not be supported by RBI. DTID Suffixing: Under RBI, requisitions submitted to DLA 

Disposition Services may include a DTID Suffix Code in addition to the DTID value. The DTID 

Suffix Code equates to the suffix used on the original property turn-in and retained by DLA 

Disposition Services for accountability and tracking. Turn-in property shipped under a DTID suffix

will be received at the DLA Disposition Services Field Offices with the corresponding DTID and 

associated suffix. This DTID and suffix combination will normally be passed to the RTD Web and 

GSA as part of the inventory files to each respective system. Customers will requisition against the 

DTID and suffix, passing it on the requisition to DLA Disposition Services for processing as a 

secondary document number on the 511R. When the requisition is processed, a Materiel Release 

Order (DLMS 940R) will pass the DTID with its associated suffix to DSS for release and issue of the 

specific requisitioned property. Once this is accomplished, a Materiel Release Confirmation (DLMS 

945A) will be sent back to DLA Disposition Services including the

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

GSA and the RTD Web send MILSTRIP (DIC A0_) requisitions to DAISY for processing. These are 

daily batched files sent directly to DAISY for processing. Military Service customers may order via 

RTD or submit MILSTRIP/DLMS requisitioning transactions to DLA Disposition Services (Routing 

Identifier Code (RIC) S9D), which are routed through the DLA Transaction Services Defense 

Automated Addressing system (DAAS) to DAISY.

d. MILSTRIP Document Numbers associated with DLA Disposition Services Record 

Position (rp) 40/DLMS Utilization Code. Under existing procedures prescribed by MILSTRIP 

Appendix AP2.7.5.3, the following alphabetic codes have been identified for use in rp 40 (first position 

of the document number serial number). Under DLMS this is considered an embedded data element 

and has been established as a separate data element called the Utilization Code. The currently assigned 

values are modified as follows to support RBI and reflect discontinued use of obsolete codes. 

Reserved codes are not authorized for use by requisitioning activities. Requisitions prepared within 
ADC 466 Attachment, Page 9

DLA Disposition Services Field Offices for walk-in customers and RTD-generated requisitions, 

including those described above as RTD “spin-offs” from standard MILSTRIP requisitioning, 

will therefore; use these values in the document number and the DLMS Utilization Code. The 

list of available values is updated as follows. Staffing Note to DOD Components: Values 

identified as reserved are not authorized for use in MILSTRIP requisitioning in the previously 

assigned context or any other. Subsequent to staffing, the Air Force reported a disposal-specific use 

for the document number serial number beginning with Y. To preclude reuse for another purpose, 

the Air Force may submit a DLMS Change Proposal documenting their requirement. The Y value 

will be removed from the available list of MILSTRIP-assigned codes as shown below. The Air 

Force also identified that the assigned value S is being used for requisitioning from DLA 

Disposition Services as originally intended, so the definition is updated and retained below.

CODE EXPLANATION

K Use to identify requisitions submitted to DRMS, DRMO, or GSA for excess property located at 

a DRMO that is requested as a result of reviewing manual screening lists; for example, EPPLs and 

GSA Regional Catalog listings. Reserved.

L Use to identify requisitions submitted to DRMOs DLA Disposition Services which that result 

from physical screening of property at the DRMO DLA Disposition Services Field Office. This type 

of screening is referred to as “Local Area Screening” without any consideration of the distance traveled 

by the screener. This type of requisition is referred to as a “Walk-In Requisition.”

N Use to identify requisitions and related transactions/documents for materiel provided through 

the reclamation process. Reserved.

R Use to identify requisitions submitted to DRMS/DRMOs from ICPs or IMMs based on a Final 

Asset Screening notice of surplus personal property document numbers generated within the DLA 

Disposition Services’ Reutilization/Transfer/Donation (RTD) Web to accommodate processing of 

the individual lines associated with requisitioning a Disposition Services container.

S Use to identify requisitions submitted to DLA Disposition Services DRMS/DRMOs from ICPs 

or IMMs based on a Front End Screening notice of excess personal property. 

T Use to identify requisitions submitted to DRMS/DRMOs from ICPs/IMMs based on a 

management decision for recoupment of known transfers to disposal. Use to identify Electronic TurnIn Document (ETID) prepared shipments/transfers to DLA Disposition Services.5

Y Use to identify requisitions resulting from interrogation of the Interrogation Requirements Information System. (See DOD 4160.21-M.)

 5 ADC 464 (PDC 484), Intransit Control System (ICS), Shipment Status (DLMS 856S/Document Identifier Code (DIC) 

AS3), and Disposal Shipment Confirmation Follow-up (DLMS 940/ DIC AFX/AFZ) under RBI
ADC 466 Attachment, Page 10

5. APPROVED CHANGE(S):

a. Approved change in detail:

(1) DLA Disposition Services will require the use of a requisition walk-in indicator to 

identify requisitions that generate from a walk-in customer at the Field Office. 

(2) DLA Disposition Services will use Disposition Services Indicator(s) to identify postissue tracking requirements on the 511R requisition provided by the RTD Web to DLA Disposition 

Services (EBS). The rules related to which customers will require post-issue tracking will be 

maintained in the RTD Web. The RTD Web will send the appropriate post-issue tracking indicator to 

EBS so that Disposition Services’ personnel will be notified that this particular customer will require 

post-issue tracking. If any of the post-issue tracking documents are required for an item, as indicated 

by being passed on the 511R, then EBS will compile the required tracking via the requisition. This 

information is then passed to the E-Docs system where it will be stored for future tracking. The postissue tracking required for certain items is to ensure the tracking documents are received when the item 

has been shipped or picked up by the customer. This tracking is maintained for the entire life of the 

item while being used by that particular customer. These post-issue tracking requirements become 

important at the time of disposal to ensure that the customer applies the appropriate procedures (e.g.,

was DEMIL certificate turned in with the item). If tracking requirements become overdue, a

notification will be sent to the appropriate person at DLA Disposition Services to follow up on the 

missing documentation. The five post-issue tracking categories are: 

(a) Materiel Receipt Acknowledgement (MRA) Required. This indicator will be 

applied to requisitions for DLA Disposition Services property that would fall outside the standard 

MRA requirements under MILSTRAP/DLMS. DOD activities requisitioning from DLA Disposition 

Services are required to provide an MRA (DLMS 527R/DIC DRA) under current procedures.

Staffing Note for DLA Disposition Services: A proposed DLMS change will be required to expand 

applicability of MRA procedures beyond those currently prescribed by MILSTRAP Chapter 

6/DLMS Volume 2. The proposal must include clarification of the applicable circumstances and 

how the receipt acknowledgement will be communicated to DLA Disposition Services. 

(b) Demilitarization (DEMIL) Certification Required. DEMIL-certificationrequired items require confirmation when demilitarization is performed on property. Before this item 

can be turned in or disposed of by the customer, proof will be provided to DLA Disposition Services 

that it was demilitarized.

(c) Mutilation Certification Required. Mutilation-certification-required items must 

be destroyed when the item is no longer needed or in use to the extent that prevents its reuse or 

reconstruction; documentation must be received by DLA Disposition Services to verify that mutilation 

was completed.

(e) Certificate of Recycling Required. Certificate of recycling items must be 

confirmed to have been recycled. The customer will provide proof to DLA Disposition Services via 

documentation that the item was recycled when no longer needed or in use by the customer.

(3) DEMIL Condition of Sale. Some items that will be available to the public are 

required as part of public sale to have parts of the item demilitarized upon completion of the sale. This 

indicator is passed from the Disposition Services eSales Website to DLA Dispostion Services (EBS) 
ADC 466 Attachment, Page 11

on the requisition. This indicator will be passed on the Materiel Release Order (MRO) to DSS, so that 

Disposition Services personnel are alerted to the action that is needed to be taken for the newly sold 

item. In some cases, they will be able to demilitarize the item on the spot, in other cases the customer 

is required to arrange for the demilitarization. The DEMIL as Condition of Sale will work differently 

than the DEMIL required indicator. Not all items with the DEMIL required indicator will end up 

going to public sales, whereas a particular item that may not normally have the DEMIL required 

indicator, may need to have DEMIL performed as a condition of sale due to it being sold to the public. 

This indicator will alert the DLA Disposition Services Field Office personnel for the impending sale to 

be completed the public customer either needs to perform the Demilitarization of the item on site 

before removing the item; or the item must be taken to an approved Demilitarization site for the item to 

have demilitarization performed there. When this indicator is applicable, DLA Disposition Services 

will not pay for any shipping costs for shipping these items for demilitarization. It will be done at the 

expense of the customer. The DEMIL required indicator means the item needs to have demilitarization 

completed regardless of the customer.

(4) Funds Appropriation (Fund Cite) for FMS Requisitions. DLA Disposition Services 

will require that a Fund Appropriation field be added to the 511R for FMS requisitions transportation 

charges associated with the requisition. This fund cite can be perpetuated to the DLA Disposition 

Field Office via the Materiel Release Order (MRO). The Field Office must provide the fund cite to the 

Transportation Management Office (TMO), so that they know whom to charge for transportation costs. 

There is no bill generated for FMS orders; there is a pool of money set aside every fiscal year to cover 

the costs of shipping these items. Staffing Note for USTRANSCOM: Request review this

procedure for compliance with Standard Financial Information Structure (SFIS) guidance. 

Components are advised that the DOD is in the process of implementing SFIS for all systems 

carrying/processing financial information (e.g., lines of accounting, fund codes). ADC 435 

provides DLMS procedures for SFIS. While use of DLMS Qualifier 18 will be authorized at this 

time to support RBI legacy processes noted here during transition to SFIS, Components and 

Agencies will be required to migrate to SFIS procedures. Additional process changes will be 

addressed in future change proposals. 

(5) Containerization. To support the containerization process, DLA Disposition Services 

requires a Disposition Container ID, Container Count, and Full Container Flag on the 511R 

Requisition. Refer to Enclosure 1.

(6) Customer Pick-up Required. The RTD-generated requisition transaction provided to 

EBS shall include a Disposition Services Indicator to indicate that the customer will pick up the 

property. This information must be perpetuated to the materiel release order prepared by DLA 

Disposition Services (EBS) for transmission to DSS to alert the DLA Disposition Services Field 

Office. 

(7) Customer Contact Information. RTD Web will include the customer name and 

phone number on the DLMS 511R so that this information can be perpetuated to the materiel release 

order sent by DLA Disposition Services (EBS) to the Field Office (DSS) for property that will be 

picked up by the customer. The Field Office needs this information to facilitate creation of the pick 

list. Multiple DLA Disposition Services' customers utilize the same DoDAAC representing their 

location/organization, DSS currently generates pick lists by DODAAC so without the additional 

information, DSS could not generate a customer-specific pick list. In order for DSS to create a pick 

list filtered to a specific customer, the customer name and telephone number will be passed on the 

MRO. The inclusion of the telephone number will facilitate contacting the customer when necessary.
ADC 466 Attachment, Page 12

b. Approved procedures: 

(1) The RTD Web will send EBS requisitions that will identify if all items in the container 

are being acquired by a customer or just certain items in the container. The “complete container”

identifier will alert EBS that an entire container has been requisitioned and will also enable EBS to 

validate that all items from the container are accounted for within requisitions received from the RTD 

Web.

(2) The addition of the Disposition Services Indicators for post-issue tracking will allow 

DLA Disposition Services to know when certain items (identified by DTID) need to be tracked long 

term and if the item is ever disposed of, turned in, or donated to another entity, that the proper steps 

were taken to properly handle the item. Customers are obligated to perform these actions, and if they 

are found to not have properly disposed of these items, there may be negative ramifications. If an item

requires post-issue tracking, EBS will be able to provide this information. DLA Disposition Services 

will perform follow-up service with these customers to verify that the proper steps were taken.

c. Alternatives: None identified.

6. REASON FOR CHANGE: As a result of the RBI project, the requisition process needs to be 

updated to account for a newly re-designed DLA Disposition Services process.

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages:

(1) The Requisition walk-in indicator will notify EBS that the requisition originated from a 

walk-in customer and will process the requisition

(2) Container information will help to minimize physical handling of materiel.

(3) Post-issue tracking provides additional traceability for items.

b. Disadvantages: There are no known disadvantages.

8. NOTE ANY REGULATIONS OR GUIDANCE: Changes will be needed for manuals DOD

4160.21-M and DRMS-I 4160.14. 

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: March 2012.

10. ESTIMATED SAVINGS/COST AVOIDANCE: Not Applicable

11. IMPACT:

a. New DLMS Data Elements: New data elements are identified below. 

(1) Disposition Services Indicator: Refer to Enclosure 4. This new data element 

identifies various types of information associated with processing requisitions and other transactions 

associated with DLA Disposition Services. For example, this data element is used to identify a walk-in 

customer and various forms of post-issue tracking that may be required.
ADC 466 Attachment, Page 13

(2) Containerization: The containerization process requires the addition of the Container 

Count, Disposition Service Container ID, Disposition Services Container Sequence Number, and the

Disposition Services Indicator for Container Issued in Full to the 511R.

b. Changes to DLMS Data Elements: Utilization Code values are updated as shown above in 

3.d.

c. Publications: 

(1) Requires update to DOD 4000.25-M, DLMS, Volume 2, to add procedures for the DLA 

Disposition Services requisition processing under RBI. 

(2) MILSTRIP Appendix AP2.7 is updated to reflect the rp 40 values (Utilization Code) as 

shown above in 3.d.

(3) MILSTRIP Appendix AP 3.2 is updated to reflect updated terminology for DLA 

Disposition Services. Additionally, reference to the Excess Report Number (ERN) is removed as 

obsolete. (See Enclosure 2.)

(4) MILSTRIP Appendix AP 3.48-4 is updated to remove references to the ERN on the DD 

1348-1A or DD 1348-2 for shipments from DLA Disposition Services.

(5) MILSTRIP Acronym List (front matter) is updated to remove the acronym ERN.

(6) DLMS Supplement revisions are shown at Enclosure 3. This DLMS Change identifies 

revisions to the following DLMS transactions: 511R, 511M, 527D, 527R, 842A/W, 856S, 869C, 

869F, 870S, 940R, and 945A. Staffing Note: Subsequent to staffing of the proposed change, it was 

identified that the requisition related transactions needed to be updated to support RTD-generated 

suffixing of the customer document number (as described above). It was also identified that the

requisition related transactions and all the follow-on transactions needed to have flexibility to identify 

the DTID number in multiple locations within the secondary reference composite data field (due to the 

addition of the RTD-assigned suffix code). This has resulted in significant updates to the DLMS 

Supplements during the comment resolution phase. Refer to Enclosure 6, Response to PDC Staffing 

and Comment Resolution, for additional clarification. 

d. DLA Transaction Services: The DAAS mapping for the requisition and subsequent 

transactions must be updated to reflect the DTID suffix.
ADC 466 Enclosure 1, Page 1

Enclosure 1, Data Content

The following table lists data content passed from the RTD Web to DLA Disposition Services on the 

511R, Requisition. 

DS 511R Data Content Usage Notes Field 

Length

1. Original Document NumberRequisition Number generated by either the RTD Web or 

GSA.

14

2. Document Number Suffix 

Code

RTD Web may assign a suffix code to requisitions prepared 

outside RTD Web and submitted to DLA Disposition Services 

via MILSTRIP/DLMS transaction.

1

3. DTID Number Disposal Turn In Document Number – this is the level at 

which the item will be requisitioned. This is a required data 

element when the requisition is passed from RTD to EBS.

14

4. DTID Suffix Code This is the suffix code associated with the DTID. It is normally identified by the customer on the requisition to specifically 

identify the property ordered.

1

5. Requisition Costs RTD Web and GSA items will be free issue – FMS items may 

have transportation costs associated.

9

6. Materiel ID This is the NSN or DLA Disposition Services LSN. It is required as well as the DTID.13

7. Unit of Use Indicator Used to indicate that the quantity and unit of measure are related to a unit of use rather than the standard unit of issue.1

8. Required Delivery Date Standard MILSTRIP usage. 8

9. Requisition Create Date Date Requisition was created. 8

10. Unit of Measure The unit of measure for the DTID requisitioned. 3

11. Priority Code Identifies the priority of the RTD Web requisition. 2

12. Media and Status Code This is a required data element. Standard MILSTRIP usage. 1

13. Signal Code This is a required data element. Standard MILSTRIP usage. 1

14. Quantity The quantity of the DTID for the requisition. 9

15. Supplementary Address Standard MILSTRIP usage. When populated, the ship-to and 

bill-to data fields (N1 segment) are also be populated, as applicable.

6

16. Fund Code Standard MILSTRIP usage indicating free issue. Not applicable for FMS.2
ADC 466 Enclosure 1, Page 2

DS 511R Data Content Usage Notes Field 

Length

17. Distribution Code Standard MILSTRIP usage. 1

18. Advice Code Standard MILSTRIP usage. 2

19. Project Code Standard MILSTRIP usage. 3

20. RIC-To Routing Identifier Code – this will be S9D. 3

21. Disposition Services 

Container Identification 

Disposition Services Container ID will identify DTIDs that 

are part of the container. Only applicable if the DTID is part 

of container.

10

22. Disposition Services 

Container DTID Sequence 

Number

A sequential number for DTIDs that make up a container. 

Only applicable if an entire container is requisitioned. 

4

23. Disposition Services 

Container DTID Count

This is a count of the total number of DTIDs in a single 

container. Only applicable if an entire container is 

requisitioned.

9

24. Disposition Services 

Indicator - Container Issued in Full

Indicates that a full container is requisitioned. 4

25. Disposition Services 

Indicator - Walk-In 

Customer 

This will identify if item was requisitioned by a walk-in 

customer. Identifies immediate processing.

4

26. Disposition Services 

Indicator - Receipt 

Acknowledgement 

Required

Applicable for post-issue tracking. 4

27.

Disposition Services 

Indicator - DEMIL 

Certification Required

Applicable for post-issue tracking. 4

28. Disposition Services 

Indicator - Mutilation 

Certification Required

Applicable for post-issue tracking. 4

29. Disposition Services 

Indicator - Certificate of 

Recycling Required

Applicable for post-issue tracking. 4

30. Disposition Services 

Indicator – DEMIL 

Condition of Sale Indicator

This will notify the Field Office of necessary action for 

DEMIL of property upon release to a public sales customer.

4
ADC 466 Enclosure 1, Page 3

DS 511R Data Content Usage Notes Field 

Length

31. Appropriation Number 

(Fund Cite) 

Required for FMS orders that have additional costs. 75

32. Utilization Code Required for orders where the document number is created 

using during RTD processing for containerized property or for 

walk-in customers

1

33. Disposition Services -

Indicator Customer Pick-up

This indicator will be populated to let the DLA Disposition 

Services Field Office know that a customer will be picking up 

the item. This indicator will be perpetuated from ICP system 

to the Field Office on the MRO. 

4

34. Customer Name This is the specific person who requisitioned the property and 

will identify for contact on the pick up. 

60

35. Customer Phone Number This is the number the site would call to contact the pick up 

person. The data element field length allows for an 

international number and six digit extension. 

19
ADC 466 Enclosure 2, Page 1

Enclosure 2, MILSTRIP Revisions

AP3.2. APPENDIX 3.2

REQUISITION

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Send to Block A6 Not Applicable Enter the appropriate in-the-clear 

name and address corresponding to 

the RI, if applicable.

Requisition Is From Block B Not Applicable Enter the appropriate in-the-clear 

name and address of the requisitioner, 

if applicable.

Document Identifier Block 1 1-3 Enter DI A0_ or AM_.

Routing Identifier Block 2 4-6 Enter RI indicating the supply source 

to which the document is being 

submitted.

Media and Status Block 3 7 Enter the M&S code.

Stock Number7 Blocks 4, 5, 6 8-22 Enter the stock or part number of the 

item being requisitioned. For 

subsistence items, enter the type of 

pack in rp 21.

Unit of Issue Block 7 23-24 Enter the unit of issue.

Quantity Block 8 25-29 Enter the quantity requisitioned. For 

ammunition requisitions only (items 

in FSG 13), enter an “M” in rp 29 to 

express in thousands any quantity 

exceeding 99,999. Example: A 

quantity of 1,950,000 will be 

expressed as 1950M (1950 in rp 25-28 

and an “M” in rp 29).

 6

See the AP2 series of appendices for an explanation of the data fields.

7

Requisitions to DLA Disposition Services DRMS (RI S9D) cannot reflect an entry in rp 21-22 other than a DTID number 

suffix in rp 21, when applicable.
ADC 466 Enclosure 2, Page 2

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Document Number Blocks 9-12 30-43 Enter document number as assigned 

by the preparing activity.

Demand8 Block 13 44 Enter the demand; otherwise, leave 

blank.

Supplementary 

Address

Blocks 14-15 45-50 When applicable, enter the coded 

SUPADD of the ship-to or bill-to 

activity; otherwise, leave blank. 

When coded data is not significant to 

the supply source (other than an 

AAC), enter an alphabetic “Y” in rp 

45.

Signal Block 16 51 Enter the signal code.

Fund Block 17 52-53 Enter the fund code as directed by the 

Component.

Distribution Block 18 54 When applicable, enter the 

distribution code of the activity to 

receive status information in addition 

to the requisitioner or the SUPADD.

55-56 Enter the code as directed by the 

Components.

Project Block 19 57-59 When applicable, enter the 

appropriate code under Component 

instructions.

Priority Block 20 60-61 Enter priority designator.

Required Delivery 

Date/Required 

Delivery Period9

Block 21 62-64 Enter data requirements from AP2.14, 

as applicable; otherwise, leave blank.

Advice Block 22 65-66 Enter advice code to convey 

instructions to the supply source; 

otherwise, leave blank.

Date of Receipt of 

Requisition10,11,12 

Block 23 67-69 Leave blank.

 8 On an Intra-Army basis a suffix code entry is authorized for identification of post-post partial issues of materiel by Army 

Single Stock Fund Activities. These requisitions will contain Army Edit Action Code IV in rps 74-75. 9 Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL 148. 10 Processing Points passing DI AM_ transactions to another supply source for continued processing will enter their RI code 

in rps 67-69.
ADC 466 Enclosure 2, Page 3

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Blank Block 23 70-80 Leave blank on inter-Component 

requisitions forwarded to the DLA 

and GSA supply sources.

a. This field is optional for intraComponent use.13,14, 15, 16, 17, 18

b. This field may be used for internal 

purposes on retained copies of 

requisitions.

GOVERNMENT-FURNISHED MATERIEL REQUISITION ENTRIES.

19

Manufacturer’s 

Directive Number

54-56 If required by the Component 

contracts, enter the MDN.

Contract Call Order 

Number

69-72 If required by the Component 

contracts, enter the appropriate 

contract call order number.

Contract Identification 73-80 At the option of the Component, enter 

the last eight positions of the PIIN in 

rp 73-80 in lieu of the MDN in rp 54-

56. This entry is mandatory if the 

MDN is not entered in rp 54-56.

 11 The Map Support Office Distribution System (MSODS) will enter the MSODS RI Code SD& in A0_ transactions 

returned to Mapping Agency Automated Distribution Management System (DADMS)(HM8) for processing. This will 

indicate to DADMS that this is not the initial processing of the requisition (requisition was previously reviewed and 

forwarded to MSODS, which was unable to fulfill).

12 On Intra-Army basis a RI code entry is authorized for identification of the storage site related to post-post issues of 

materiel by Army Single Stock Fund Activities. These post-post requisitions will contain Army Edit Action Code IV in rps 

74-75. 13 On Intra-Army requisitions rp 70 will contain the ownership/purpose code and rp 71 will contain the supply condition 

code of the materiel post-post issued by Army Single Stock Fund Activities. These post-post requisitions will contain 

Army Edit Action Code IV in rps 74-75. 14 On Intra-Army basis both post-post and image Single Stock Fund Activity requisitions may contain a management code 

in rp 72 to facilitate processing.

15 On Intra-Army basis requisitions may contain an Army Edit Action Code in rps 74-75 to indicate the actions required by 

the receiving system in order to process transactions and direct authorized follow-on actions. This code is meaningful to 

the Army only and is used on both post-post and image requisitions. 16 On Intra-Army basis requisitions may contain the date generated in rps 77-80. This date is required to accurately process 

transactions relative to image, post-post and working requisitions submitted by Army Single Stock Fund activities. 17 For intra-Air Force lateral requisitions, the supply source identified in rp 4-6 is another Air Force base, the Routing 

Identifier of the requisitioner is identified in rp 73-75, and the Routing Identifier of the DoD Source of Supply is identified 

in rp 78-80. Refer to ADC 266. 18 For intra-Air Force requisition modification, the unit price may be identified in rp 71-80. Refer to ADC 263.

19 Procedures to control access to DOD materiel inventories by defense contractors last reported as not implemented by 

USA (Retail). Refer to AMCL 1A.
ADC 466 Enclosure 2, Page 4

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

MANAGEMENT CONTROL ACTIVITY ENTRIES: Entries Required for Requisitions for 

Government-Furnished Materiel.20

Routing Identifier 4-6 Enter the RI code of the supply 

source.

Distribution 54-56 Enter the distribution code of the 

MCA validating the transaction or the 

MDN consisting of the MCA’s 

distribution code in rp 54 and two 

other alpha/numeric characters in rp 

55-56.

Routing Identifier 74-76 If required by the Component, enter 

the RI code of the validating MCA in 

rp 74-76.

DEFENSE REUTILIZATION AND MARKETING DLA DISPOSITION SERVICES

ENTRIES: Entries Required When Requisitioning a Specific Item From Disposal.21

Disposal Turn-in 

Document Number or 

Excess Report Number

67-80 This entry is optional on DI 

A01/A0A/A05/A0E requisitions and 

is mandatory on DI A04/A0D 

requisitions. If applicable, the DTID 

suffix will be entered in rp 21.

DEFENSE REUTILIZATION AND MARKETING DLA DISPOSITION SERVICES

ENTRIES: Entries Required on Requisitions to Disposal When a Specific Item is Not 

Required.22

Blank 70 Leave blank.

Condition Code 71 Enter lowest acceptable supply 

condition code under Component 

criteria furnished to DRMS DLA 

DISPOSITION SERVICES. See 

Chapter C2, paragraph C2.21. for 

requirement.

Blank 72-80 Leave blank.

 20 See Footnote 6.

21 Procedures, formats, and codes for requisitioning materiel from disposal last reported as not implemented by DLA. 

Refer to AMCL 139A.

22 See Footnote 8.
ADC 466 Enclosure 3, Page 1

Enclosure 3, DLMS Supplement Revisions

A. Revise the DLMS 511R Requisition as follows:

# Location 511R Requisition Reason

1. DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and 

Transaction Exchange associated with DLA Disposition Services under 

Reutilization Business Integration (RBI)

Identifies DLMS 

Changes included 

in the DS.

2. 1/G6101/110 Revise DLMS note for Existing Qualifier IC:

IC Information Contact

Federal Note:

Use to identify the point of contact.

DLMS Note: 

DLA Disposition Services uses in conjunction with the Ordered By 

DoDAAC to perpetuate the customer contact name and phone number

from the Reutilization/Transfer/Donation (RTD) Web Application to DLA 

Disposition Services. Refer to ADC 466.

Supports RBI 

requirement.

3. 2/N901/20 Add new Qualifier 98 with DLMS note:

98 Container/Packaging Specification Number

DLMS Note: DLA Disposition Services uses to identify the Disposition 

Services Container Identification (ID). DLA Disposition Services uses 

container ID on requisitions to link the DTID Number to the applicable 

container. DLMS enhancement; refer to ADC 466.

Supports RBI 

requirement.

Staffing Note: 

The mapping of 

this data element is 

revised to 

deconflict with 

content required in 

the N907.

4. 2/N907-01/20 Revise DLMS notes for existing Qualifier W1 for administrative changes:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use with N901 code TN to identify the transaction number under which 

material was shipped to a Defense Reutilization and Marketing Office 

(DRMO). Use only when requisitioning a specific item from Defense 

Reutilization and Marketing Service (DRMS).

1. Use in conjunction with the controlling requisition document number for

the transaction cited (N901 code TN) when requisitioning a specific item 

from DLA Disposition Services. 

2. For DLA Disposition Services Reutilization/Transfer/Donation (RTD) 

Web Application, when there is no Suffix Code associated with the 

customer’s Document Number, enter the correlating DTID in the N907-

02. If there is a Suffix Code (N907 Code W8), then enter the DTID in the 

This information is 

replicated here 

from ADC 457. 

No substantive 

updates are 

required for this 

ADC.
ADC 466 Enclosure 3, Page 2

# Location 511R Requisition Reason

N907-04. DLMS enhancement, see ADC 466.

3. Use on 511R DLA-Directed MROs (DIC C0_) applicable to DLA 

Disposition Services inventory to identify the DTID number when provided 

as a secondary reference number. The DTID number is used by DLA 

Disposition Services as a unique number to identify property that was 

turned into a DLA Disposition Service Field Office. The value of the 

DTID may be the original turn-in document number or may be a unique 

control number (UCN) assigned by the Field Office during receipt 

processing when the original DTID number is not adequate to uniquely 

identify the property. Must use with Disposition Sub-Category Code SV. 

May be used with Disposition Category Code DS. Refer to ADC 457. 

Revise DLMS notes for existing Qualifier W8:

W8 Suffix

DLMS Note:

1. Use with N901 Code TN to identify the document number suffix. Use is 

limited to when the transaction is identified as a referral order with BR02 

transaction type code BN and is referring a quantity less than the original 

requisition quantity to another supply source.

2. Also authorized on an Intra-Army basis with BR02 transaction type code 

A0, BR06 action code “J” and N901 code TN for identification of the postpost partial issue of material by Army Single Stock Fund activities.

3. Use with N901 Code F8 to identify the prior requisition document 

number suffix if applicable. Authorized DLMS enhancement for BRAC 

IMSP only. Refer to ADC 352 and ADC 359.

4. When used in the requisition alert (BR06=83), or when used in 

association with the Requisition Alert Document Number (Qualifier PWC, 

above), this will be the requisition alert document suffix. Use with BR02 

Qualifier BN only. The requisition alert document number suffix is an 

authorized DLMS enhancement under DLA industrial activity support 

agreement. Refer to ADC 381.

5. DLA Disposition Services uses on an intra-DLA basis for requisitions 

processed between the RTD Web Application and DLA Disposition 

Services. The RTD Web-sequentially assigned suffix code is used for 

open requisition quantity on externally submitted requisitions when 

required to establish separate requisition transactions to DLA Disposition 

Services by DTID Number and, when applicable, the associated DTID 

Suffix Code. Refer to ADC 466.

Supports RBI 

requirement for 

RTD Web. 

5. 2/N907-01/20 Add new Qualifier 55 with DLMS notes:

55 Sequence Number

DLMS Note:

DLA Disposition Services uses in conjunction with the Disposition 

Services Container ID (N901 Code 98) to identify the Disposition Services 

Container DTID Sequence Number. This is a sequential number 

assigned for the requisitioned DTIDs that make up a container. Only 

applicable if an entire container is requisitioned. Refer to ADC 466.

Used for tracking 

to ensure that all 

requisitions are 

received when the 

entire container has 

been requisitioned.
ADC 466 Enclosure 3, Page 3

# Location 511R Requisition Reason

6. 2/N907-03/20 Remove Qualifier SS and notes: 

SS Split Shipment Number

Federal Note:

Use with N907-1 code W1 to identify the Disposal Turn-In Document 

(DTID) transaction number suffix.

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (N907 Code W1) to 

identify the DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in N907-02, enter the correlating 

DTID Suffix using this location. DLMS enhancement, see ADC 466.

Add new Qualifier W1 with DLMS notes:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the requisition document number (N901 Code 

TN) when requisitioning a specific item from DLA Disposition Services.

2. For DLA Disposition Services Reutilization/Transfer/Donation (RTD) 

Web Application, when there is no Suffix Code associated with the 

customer’s Document Number, enter the correlating DTID in the N907-

02. If there is a Suffix Code, then enter the DTID in the N907-04. 

DLMS enhancement, see ADC 466.

The qualifier used 

to identify the 

DTID Number 

Suffix Code is 

changed from SS to 

60. This is to 

deconflict usage of 

the qualifier which 

supports to the 

transportation 

domain. 

Adds the DTID 

suffix at multiple 

locations within the 

composite to allow 

for flexibility of 

data content.

7. 2/N907-05/20 Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (N907 Code W1) to 

identify the DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in N907-04, enter the correlating 

DTID Suffix using this location. DLMS enhancement, see ADC 466.

Adds the DTID 

suffix at multiple 

locations within the 

composite to allow 

for flexibility of 

data content.
ADC 466 Enclosure 3, Page 4

# Location 511R Requisition Reason

8. 2/LQ01/140 Add new local code Qualifier DSI with DLMS notes:

DSI Disposition Services Indicator 

DLMS Note: 

1. DLA Disposition Services uses to provide relevant information 

applicable to the DLA Disposition Services business process supported by 

this transaction on an intra-DLA basis. Use multiple repetitions of the 

LQ Segment to include all applicable codes. Authorized DLMS 

enhancement for use by DLA Disposition Services. Refer to ADC 466.

2. The following Disposition Services Indicator values are available for 

use in the requisition transaction:

 MRA – Materiel Receipt Acknowledgment Required. 

 DMIL – DEMIL Certification Required. 

 MUTL – Mutilation Certification Required. 

 RCYL– Certificate of Recycling Required. 

 CIF – Container Issued in Full. 

 WALK–Walk-in Customer. 

 PICK- Customer Pick-up Required.

 CS – DEMIL Condition of Sale Indicator

3. At this time a local code ‘DSI’ is established for use in 511R, version 

4010. A data maintenance action has been submitted for establishment of 

‘DSI-Disposition Services Indicator’ in a future version.

Supports RBI 

requirement. 

Required for postissue tracking.

9. 2/QTY01/150 Open QTY segment and add the following qualifier:

OC Order Count

DLMS Note: DLA Disposition Services uses to identify the total number 

of DTIDs in a specified container (i.e., the container count) when the 

entire container is being requisitioned. DLMS enhancement; Refer to 

ADC 466.

Identifies the total 

count so that the 

application will 

know how many 

requisitions are 

applicable to the 

full container.

10. 2/FA201/ 286 Add Qualifier 18 and associated DLMS notes:

18 Funds Appropriation

DLMS Note:

1. Use to indicate the basic appropriation number.

2. Authorized DLMS enhancement for DLA Disposition Services to 

provide fund cite for FMS transportation billing. Refer to ADC 466.

3. Components are advised that the DoD is in the process of 

implementing Standard Financial Information Structure (SFIS) for all 

systems carrying/processing financial information (e.g., lines of 

accounting, fund codes). DLMS Qualifier 18 will be authorized at this 

time to support RBI legacy processes during transition to SFIS.

Supports RBI 

requirements.

The Qualifier 181 

had been 

previously deleted 

and is now 

reinstated.
ADC 466 Enclosure 3, Page 5

B. Revise the DLMS 511M Requisition Modification as follows. The DLMS 511M carries all data 

content included in the DLMS 511R to facilitate use as a new requisition in the absence of the original 

requisition transaction.

# Location 511M Requisition Modification Reason

1. DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and 

Transaction Exchange associated with DLA Disposition Services under 

Reutilization Business Integration (RBI)

Identifies DLMS 

Changes included 

in the DS.

2. 1/G6101/110 Revise DLMS note for Existing Qualifier IC:

IC Information Contact

Federal Note:

Use to identify the point of contact.

DLMS Note: 

DLA Disposition Services uses in conjunction with the Ordered By 

DoDAAC to perpetuate the customer contact name and phone number

from the Reutilization/Transfer/Donation (RTD) Web Application to DLA 

Disposition Services. Refer to ADC 466.

Supports RBI 

requirement.

3. 2/N901/20 Add new Qualifier 98 with DLMS note:

98 Container/Packaging Specification Number

DLMS Note: DLA Disposition Services uses to identify the Disposition 

Services Container Identification (ID). DLA Disposition Services uses 

container ID on requisitions to link the DTID Number to the applicable 

container. DLMS enhancement; refer to ADC 466.

Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (N907 Code W1) to 

identify the DTID Number Suffix Code, when applicable. DLMS 

enhancement, see ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

4. 2/N907-01/20 Update for administrative revisions as follows:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use with N901 code TN to identify the transaction number under which 

material was shipped to a Defense Reutilization and Marketing Office 

(DRMO). Use only when requisitioning a specific item from Defense 

Reutilization and Marketing Service (DRMS) in conjunction with the 

requisition document number (N901 Code TN) when requisitioning a 

specific item from DLA Disposition Services.

2. When there is no Suffix Code (N907 Code W8), associated with the 

customer’s Document Number, enter the correlating DTID in the N907-

02. If there is a Suffix Code, then enter the DTID in the N907-04. 

DLMS enhancement, see ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.
ADC 466 Enclosure 3, Page 6

# Location 511M Requisition Modification Reason

5. 2/N907-01/20 Revise DLMS notes for existing Qualifier W8:

W8 Suffix

DLMS Note:

1. Use with N901 code TN to identify the document number suffix. Use is 

limited to when the initial 511R transaction is identified as a referral order 

with BR02 transaction type code BN and is referring a quantity less than 

the original requisition quantity to another supply source, with the 

exception of a modifications from the supply source to a procurement 

activity. For these modifications, enter the suffix as shown in the 

procurement request; otherwise leave blank.

2. Also authorized on an Intra-Army basis with N901 code TN for 

identification of the post-post partial issue of material by Army Single 

Stock Fund activities when the initial 511R transaction BR02

transaction type code is A0 and BR06 action code is “J”.

3. Use with N901 Code F8 to identify the Prior requisition document 

number suffix if applicable. Authorized DLMS enhancement for BRAC 

IMSP only. Refer to ADC 352 and ADC 359.

4. When used in modification of the requisition alert (BR06=83), or when 

used in association with the Requisition Alert Document Number 

(Qualifier PWC, above), this will be the requisition alert document

suffix. Use with BR02 Qualifier BN only. The requisition alert document

number suffix is an authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381.

5. DLA Disposition Services uses on an intra-DLA basis for requisitions 

processed between the RTD Web Application and DLA Disposition 

Services. The RTD Web-sequentially assigned suffix code is used for 

open requisition quantity on externally submitted requisitions when 

required to establish separate requisition transactions to DLA Disposition 

Services by DTID Number and, when applicable, the associated DTID 

Suffix Code. Refer to ADC 466.

Supports RBI 

requirement for 

RTD Web. 

6. 2/N907-01/20 Add new Qualifier 55 with DLMS notes:

55 Sequence Number

DLMS Note:

DLA Disposition Services uses in conjunction with the Disposition 

Services Container ID in N901 to identify the Disposition Services 

Container DTID Sequence Number. This is a sequential number 

assigned for the requisitioned DTIDs that make up a container. Only 

applicable if an entire container is requisitioned. Refer to ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.
ADC 466 Enclosure 3, Page 7

# Location 511M Requisition Modification Reason

7. 2/N907-03/20 Remove Qualifier SS and notes: 

SS Split Shipment Number

Federal Note:

Use with N907-1 code W1 to identify the Disposal Turn-In Document 

(DTID) transaction number suffix.

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

Add new Qualifier W1 with DLMS notes:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the requisition document number (N901 Code 

TN) when requisitioning a specific item from DLA Disposition Services.

2. When there is no Suffix Code associated with the customer’s 

Document Number, enter the correlating DTID in the N907-02. If there 

is a Suffix Code, then enter the DTID in the N907-04. DLMS 

enhancement, see ADC 466.

The qualifier used 

to identify the 

DTID Suffix Code

is changed from SS 

to 60. This is to 

deconflict usage of 

the qualifier which 

supports to the 

transportation 

domain. The DTID 

Number Suffix 

Code is re-mapped 

to the N901 to 

reduce confusing 

double mapping.

8. 2/LQ01/140 Add new local code Qualifier DSI with DLMS notes:

DSI Disposition Services Indicator 

DLMS Note: 

1. DLA Disposition Services uses to provide (or modify) relevant 

information applicable to the DLA Disposition Services business process 

supported by this transaction on an intra-DLA basis. Use multiple 

repetitions of the LQ Segment to include all applicable codes. Authorized

DLMS enhancement for use by DLA Disposition Services. Refer to ADC 

466.

2. The following Disposition Services Indicator values are available for 

use in the requisition transaction:

 MRA – Materiel Receipt Acknowledgment Required. 

 DMIL – DEMIL Certification Required. 

 MUTL – Mutilation Certification Required. 

 RCYL– Certificate of Recycling Required. 

 CIF – Container Issued in Full. 

 WALK–Walk-in Customer. 

 PICK- Customer Pick-up Required.

 CS – DEMIL Condition of Sale Indicator

3. At this time a local code ‘DSI’ is established for use in 511M, version 

4010. A data maintenance action has been submitted for establishment of 

‘DSI-Disposition Services Indicator’ in a future version.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

This data element 

is identified as 

modifiable on a 

511M.
ADC 466 Enclosure 3, Page 8

# Location 511M Requisition Modification Reason

9. 2/QTY01/150 Open QTY segment and add the following qualifier:

OC Order Count

DLMS Note: DLA Disposition Services uses to identify the total number 

of DTIDs in a specified container (i.e., the container count) when the 

entire container is being requisitioned. DLMS enhancement; Refer to 

ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

10. 2/FA201/ 286 Add Qualifier 18 and associated DLMS notes:

18 Funds Appropriation

DLMS Note:

1. Use to indicate (or modify) the basic appropriation number.

2. Authorized DLMS enhancement for DLA Disposition Services to 

provide fund cite for FMS transportation billing. Refer to ADC 466.

3. Components are advised that the DoD is in the process of 

implementing Standard Financial Information Structure (SFIS) for all 

systems carrying/processing financial information (e.g., lines of 

accounting, fund codes). DLMS Qualifier 18 will be authorized at this 

time to support RBI legacy processes during transition to SFIS.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

This data element 

is identified as 

modifiable on a 

511M.

C. Revise DLMS 527D Prepositioned Materiel Receipt (PMR) as follows:

# Location 527D PMR Reason

1 DLMS

Intro

Notes

Add ADC 466 to DLMS Introductory note 5:

- ADC 466, Procedures to Support Requisitioning by DTID and 

Associated DTID Suffix from DLA Disposition Services under RBI

Identifies changes 

included in DS.

2 2/N907-

01/030

Qualifier W1 DTID Number:

W1 Disposal Turn-In Document Number

DLMS Note: 1. Use to identify the Disposal Turn-In Document 

(DTID) Number when provided as a secondary reference number. The 

DTID number is used by DLA Disposition Services as a unique number 

to identify property that was turned into a DLA Disposition Service 

Field Office. The value of the DTID may be the original turn-in document number or may be a unique control number (UCN) assigned by 

the Field Office during receipt processing when the original DTID 

number is not adequate to uniquely identify the property.

2. Authorized for DLA Disposition Services use in Prepositioned 

Materiel Receipt transactions for relocation (1/BR02/20 code DE with 

2/LIN01/10 code N). Use in conjunction with the controlling document 

number cited at 2/N901/030/TN. Refer to the Addendum to ADC 410.

Included for context. 

The Addendum to 

ADC 410 added the 

DTID number as a 

secondary reference 

number for PMRs

associated with 

relocation.
ADC 466 Enclosure 3, Page 9

# Location 527D PMR Reason

3 2/N907-03/030 Add new Qualifier 60 and associated DLMS Note:

60 Account Suffix Code

DLMS Note: Use in conjunction with the DTID Number (N907-01 

Code W1) to identify the DTID Suffix Code, when applicable. DLMS 

enhancement, refer to ADC 466. 

Adds capability to 

identify the DTID 

number suffix code 

when DTID number 

is a secondary reference number at 

N907-01.

Adds the DTID suffix 

added as a composite 

at N907-03/04.

4 2/N901/90 Revise DLMS note1 for existing qualifier W8, and delete note 2:

DLMS Note:

1. Use in connection with the transaction document number cited in 

2/N901/30.

2. Future streamlined data; see introductory DLMS note 4c.

Administrative update to the DLMS 

notes for the document number suffix 

code.

D. Revise the DLMS 527R Receipt as follows. 

# Location 527R Receipt Reason

5 DLMS

Intro

Notes

Add ADC 466 to DLMS Introductory note 5:

- ADC 466, Revised Procedures to Support Requisitioning and 

Transaction Exchange associated with DLA Disposition Services under 

Reutilization Business Integration (RBI)

Identifies changes 

included in DS.

6 2/N907-01/030 Add qualifier W1 with DLMS Notes:

W1 Disposal Turn-In Document Number

DLMS Note: 1. Use to identify the Disposal Turn-In Document (DTID) 

Number when provided as a secondary reference number. The DTID number is used by DLA Disposition Services as a unique number to identify 

property that was turned into a DLA Disposition Service Field Office. The 

value of the DTID may be the original turn-in document number or may be 

a unique control number (UCN) assigned by the Field Office during receipt 

processing when the original DTID number is not adequate to uniquely 

identify the property.

2. The DTID, as a secondary reference number, will be populated when a 

turn-in is split into multiple shipments when sent to the Field Office (DSS). 

DLA Disposition Services requires each split shipment results in creation of 

a new Unique Control Number (UCN) upon receipt at the Field Office 

(DSS). When this occurs, the original DTID number will be populated 

2/N901/030/TN as controlling document number with the associated suffix 

at 2/N901/90. The UCN will be populated in the DTID field as a secondary 

reference. 

3. The DTID, as a secondary reference number, may also be populated 

when a receipt expected in one SCC is received in multiple SCCs; DLA 

Disposition Services requires each receipt differentiated by creation of a 

new Unique Control Number (UCN) upon receipt at the Field Office (DSS). 

Included for 

Context.

ADC 442 added this 

data and scenarios

for requirement.
ADC 466 Enclosure 3, Page 10

# Location 527R Receipt Reason

When this occurs, the original DTID number will be populated 

2/N901/030/TN as controlling document number. The UCN will be 

populated in the DTID field. (DLA Disposition Services uses this UCN 

process in place of the MILSTRAP Receipt Suffix Code whereby a receipt 

suffix code is assigned when all data elements are the same, except the 

SCC of materiel, for materiel being received).

4. Authorized for DLA Disposition Services use in receipt and historical 

receipt transactions. Use in conjunction with the controlling document 

number cited at 2/N901/030/TN. Refer to ADC 442.

7 2/N907-03/030 Open N907-03 and add qualifier ‘Q5’_with DLMS note: 

Q5 Property Control Number

DLMS Note: 1. This is used to represent a DLA Disposition Services 

Unique Control Number assigned to prevent DTID re-use. This is used

with shipments to a DEMIL facility, when a Traffic Management Office 

partialed a shipment of material and there are three document numbers 

associated with the receipt transaction at the DEMIL facility. Used in 

conjunction with the original 940R Materiel Release Order (MRO) 

document number serving as the controlling document number for 

the receipt, and the original DTID from the losing DLA Disposition 

Services Field Office. All three numbers will be reported on the 

DLMS 527R when applicable. Refer to ADC 442.

2. Authorized for DLA Disposition Services use in receipt and historical 

receipt transactions. Use in conjunction with the controlling document 

number cited at 2/N901/030/TN and the DTID cited at 2/N907-01/030/W1. 

Included for 

Context.

ADC 442 added RBI 

requirement to have 

capability when 

needed for a UCN as 

a third document 

number, as 

described in DLMS 

note.

8 2/N907-03/030 Add new Qualifier 60 and associated DLMS Note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (N907-01 Code W1) to 

identify the DTID Suffix Code, when applicable, when code Q5 for a 

UCN is not required. If using N907-03/04 to provide code Q5, then enter 

the DTID Suffix Code in N907-05/06. DLMS enhancement, see ADC 

466. 

Adds capability to 

identify the DTID 

number suffix code 

when DTID number 

is a secondary reference number at 

N907-01.

Adds the DTID suffix 

added as a composite 

at N907-03/04, when 

N907-03/04 is not 

used for qualifier Q5;

otherwise DTID suffix is entered as a 

composite at N907-

05/06. 
ADC 466 Enclosure 3, Page 11

# Location 527R Receipt Reason

9 2/N907-05/030 Add new Qualifier 60 and associated DLMS Note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (N907-01 Code W1) to 

identify the DTID Suffix Code, when applicable. DLMS enhancement, 

see ADC 466. 

Adds capability to 

identify the DTID 

number suffix code 

when DTID number 

is a secondary reference number at 

N907-01, and N907-

03 is used for qualifier Q5 UCN.

Adds the DTID suffix 

added as a composite 

at N907-05/06, when 

N907-03/04 is used 

for qualifier Q5. 

E. Revise the DLMS 842A/W SDR Report as follows:

# Location 842A/W SDR Reason

1. DLMS 

Introductory 

Note

Add ADC 466 to DLMS Introductory note 5:

- ADC 466, Revised Procedures to Support Requisitioning and 

Transaction Exchange associated with DLA Disposition Services under 

Reutilization Business Integration (RBI)

To identify DLMS 

changes included 

in the DS

2. 2/REF04-

01/0700

Revise DLMS Note for existing Code W1 as shown:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the controlling document number for the 

transaction cited in REF01 code TN. 

2. The DTID number is used by DLA Disposition Services as a 

unique number to identify property that was turned into a DLA 

Disposition Service Field Office. The value of the DTID may be the 

original turn-in document number or may be a unique control number 

(UCN) assigned by the Field Office during receipt processing when 

the original DTID number is not adequate to uniquely identify the 

property. Applicable on the SDR for intra-DLA use when the 

controlling document number for the shipment is not the DTID used 

for tracking the property. Refer to ADC 459.

3. When there is no Suffix Code (REF04 Code W8), associated with the 

controlling Document Number, enter the correlating DTID in the 

REF04-02. If there is a Suffix Code, then enter the DTID in the REF04-

04. DLMS enhancement, see ADC 466.

Allows for a cross 

reference to the 

DTID.

Adding the DTID at 

both levels of the 

composite data 

element to enable 

X12 compliance, in 

the absence of a 

suffix code to the 

document number.
ADC 466 Enclosure 3, Page 12

# Location 842A/W SDR Reason

3. 2/REF04-

03/0700

Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to 

identify the DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in REF04-02, enter the 

correlating DTID Suffix using this location. DLMS enhancement, see 

ADC 466.

Add new Qualifier W1 with DLMS notes:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the controlling document number (REF01

Code TN) to identify the applicable DTID Number. Applicable on the 

SDR for intra-DLA use when the controlling document number for 

the shipment is not the DTID used for tracking the property. 

2. When there is no Suffix Code (REF04 Code W8), associated with the 

controlling Document Number, enter the correlating DTID in the 

REF04-02. If there is a Suffix Code, then enter the DTID in the REF04-

04. DLMS enhancement, see ADC 466.

Adds the DTID 

Suffix Code; adding 

the suffix at two 

locations within the 

composite allows for 

flexibility of data 

content.

Adding the DTID at 

both levels of the 

composite data 

element to enable 

X12 compliance, in 

the presence or 

absence of a suffix 

code to the 

document number.

4. 2/REF04-

05/0700

Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to 

identify the DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in REF04-04, enter the 

correlating DTID Suffix using this location. DLMS enhancement, see 

ADC 466.

Adds the DTID 

Suffix Code; adding 

the suffix at two 

locations within the 

composite allows for 

flexibility of data 

content.

F. Revise the DLMS 856S Shipment Status as follows:

# Location 4030 856S Shipment Status Reason

1. DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and Transaction 

Exchange associated with DLA Disposition Services under Reutilization Business 

Integration (RBI)

Identifies DLMS 

Changes included 

in the DS.
ADC 466 Enclosure 3, Page 13

# Location 4030 856S Shipment Status Reason

2. 2/REF01 

/1500

Add new Qualifier 60 and associated DLMS Note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to identify the 

DTID Suffix Code, when applicable. DLMS enhancement, see ADC 466. 

Adds capability 

to identify the 

DTID Suffix perpetuated from the 

requisition to follow-on transactions.

3. 2/REF04-01 

/1500

Existing qualifier and notes shown for context:

W1 Disposal Turn-In Document Number

DLMS Note:

1. Use to identify the DTID number when provided as a secondary reference number. The DTID number is used by DLA Disposition Services as a unique number to 

identify property that was turned into a DLA Disposition Service Field Office. The 

value of the DTID may be the original turn-in document number or may be a unique 

control number (UCN) assigned by the Field Office during receipt processing when 

the original DTID number is not adequate to uniquely identify the property. DLMS 

Enhancement, see ADC 422

2. For DLA Disposition Service Field Office shipments, when there is no Suffix 

Code associated with the customer’s Document Number, enter the correlating DTID 

in the REF04-02. If there is a Suffix Code, then enter the DTID in the REF04-04. 

DLMS enhancement, see ADC 422.

Included for context. 

ADC 422 added 

the DTID at both 

levels of the 

composite data 

element to enable 

X12 compliance, 

in the absence of 

a suffix code to 

the document 

number.

4. 2/REF04-03 

/1500

Existing qualifier and notes shown for context:

W1 Disposal Turn-In Document Number

DLMS Note:

1. Use to identify the DTID number when provided as a secondary reference number. The DTID number is used by DLA Disposition Services as a unique number to 

identify property that was turned into a DLA Disposition Service Field Office. The 

value of the DTID may be the original turn-in document number or may be a unique 

control number (UCN) assigned by the Field Office during receipt processing when 

the original DTID number is not adequate to uniquely identify the property. DLMS 

Enhancement, see ADC 422.

2. For DLA Disposition Service Field Office shipments, when there is no Suffix 

Code associated with the customer’s Document Number, enter the correlating DTID 

in the REF04-02. If there is a Suffix Code, then enter the DTID in the REF04-04. 

DLMS enhancement, see ADC 422.

Included for context. 

G. Revise the DLMS 869C Requisition Cancelation as follows:

Location 869C Requisition Cancelation Reason

1. DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and Transaction 

Exchange associated with DLA Disposition Services under Reutilization Business 

Integration (RBI)

Identifies DLMS 

Changes 

included in the 

DS.
ADC 466 Enclosure 3, Page 14

Location 869C Requisition Cancelation Reason

2. 2/REF04-01 

/105

Existing qualifier and notes shown for context:

W1 Qualifier Identifying Disposal Turn-In Document Number (DTID)

DLMS Note: 

1. This is a unique number to identify property turned into a DLA Disposition Services Field Office. Use in conjunction with the controlling requisition document 

number identified in REF01 code TN, to identify the DTID associated with the 

property being cancelled by a DLA Distribution Services customer. 

2. The DTID Number is required when cancelling a requisition from DLA Disposition Services via DLA Disposition Services’ Reutilization/Transfer/Donation (RTD) 

Web Application or GSA Surplus Property Program Web Application. The DTID 

Number value should also be accommodated in Component supply systems preparing the cancellation under DLMS business rules. Use a separate requisition cancellation for each DTID Number associated with the customer requisition document 

number being cancelled. 

3. When there is no Suffix Code associated with the customer’s Document Number, 

enter the correlating DTID in the REF04-02. If there is a Suffix Code, then enter 

the DTID in the REF04-04. 

4. DLMS enhancement; refer to ADC 460.

Included for 

context. 

ADC 460 added 

the DTID at both 

levels of the 

composite data 

element to 

enable X12 

compliance in 

the presence, or 

absence, of a 

suffix code for 

the requisition 

cancellation 

document 

number.

3. 2/REF04-

03/105

Existing qualifier and notes shown for context:

W1 Disposal Turn-In Document Number (DTID)

DLMS Note: 

1. This is a unique number to identify property turned into a DLA Disposition Services Field Office. Use in conjunction with the controlling requisition document 

number identified in REF01 code TN, to identify the DTID associated with the 

property being cancelled by a DLA Distribution Services customer

The DTID Number value should also be accommodated in Component supply systems preparing the cancellation under DLMS business rules. 

2. Use a separate requisition cancellation for each DTID Number associated with 

the customer requisition document number being cancelled. 

3. When there is no Suffix Code associated with the customer’s Document Number, 

enter the correlating DTID in the REF04-02. If there is a Suffix Code, enter the 

DTID in the REF04-04. 

4. DLMS enhancement; refer to ADC 460.

Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to identify the 

DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in N907-02, enter the correlating DTID 

Suffix using this location. DLMS enhancement, see ADC 466.

Included for 

context. 

Adds the DTID 

Suffix Code; 

adding the suffix 

at two locations 

within the composite allows for 

flexibility of 

data content.
ADC 466 Enclosure 3, Page 15

Location 869C Requisition Cancelation Reason

4. 2/REF04-

05/105

Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to identify the 

DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in N907-04, enter the correlating DTID 

Suffix using this location. DLMS enhancement, see ADC 466.

Adds the DTID 

Suffix Code; 

adding the suffix 

at two locations 

within the 

composite allows 

for flexibility of 

data content.

H. Revise the DLMS 869F Requisition Follow-up as follows. The DLMS 869F carries data content included in 

the DLMS 511R to facilitate use as a new requisition in the absence of the original requisition transaction.

# Location 869F Requisition Follow-up Reason

1. DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and 

Transaction Exchange associated with DLA Disposition Services under 

Reutilization Business Integration (RBI)

Identifies DLMS 

Changes included 

in the DS.

2. 2/REF01/105 Add new Qualifier 98 with DLMS note:

98 Container/Packaging Specification Number

DLMS Note: DLA Disposition Services uses to identify the Disposition 

Services Container Identification (ID). DLA Disposition Services uses 

container ID on requisitions to link the DTID Number to the applicable 

container. DLMS enhancement; refer to ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

3. 2/REF01/105 Add Qualifier 60 and associated notes: 

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to 

identify the DTID Suffix Code, when applicable. DLMS enhancement, 

see ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

4. 2/REF04-01/105 Update for administrative revisions as follows:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use with N901 code TN to identify the transaction number under which 

material was shipped to a Defense Reutilization and Marketing Office 

(DRMO). Use only when requisitioning a specific item from Defense 

Reutilization and Marketing Service (DRMS) in conjunction with the 

controlling requisition document number for the transaction (N901 Code 

TN) when requisitioning a specific item from DLA Disposition Services.

Revise DLMS notes for existing Qualifier W8:

W8 Suffix

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.
ADC 466 Enclosure 3, Page 16

# Location 869F Requisition Follow-up Reason

DLMS Note:

1. Use with 2/REF/105 REF01 code TN to identify the document number 

suffix. Use is restricted to when initial 511R is a referral order identified 

with BR02 transaction type code BN.

2. Also authorized on an Intra-Army basis for identification of the post-post 

partial issue of material by Army Single Stock Fund activities. This use is 

allowed when the initial 511R is a requisition identified with BR02 

transaction type code A0 and BR06 action code is “J”.

3. Use with REF01 Code F8 to identify the prior requisition document 

number suffix if applicable. Authorized DLMS enhancement for BRAC 

IMSP only. Refer to ADC 352 and ADC 359.

4. When used in the requisition alert follow-up (BSI09=83), or when used 

in association with the Requisition Alert Document Number (Qualifier 

PWC, above), this will be the requisition alert document

suffix. The Requisition Alert Document Number Suffix is an Authorized 

DLMS enhancement under DLA industrial activity support agreement. 

Refer to ADC 381.

5. DLA Disposition Services uses on an intra-DLA basis for requisitions 

processed between the RTD Web Application and DLA Disposition 

Services. The RTD Web-sequentially assigned suffix code is used for 

open requisition quantity on externally submitted requisitions when 

required to establish separate requisition transactions to DLA Disposition 

Services by DTID Number and, when applicable, the associated DTID 

Suffix Code. Refer to ADC 466.

5. 2/REF04-01/105 Add new Qualifier 55 with DLMS notes:

55 Sequence Number

DLMS Note:

DLA Disposition Services uses in conjunction with the Disposition

Services Container ID (REF01 Code 98) to identify the Disposition 

Services Container DTID Sequence Number. This is a sequential

number assigned for the requisitioned DTIDs that make up a container. 

Only applicable if an entire container is requisitioned. Refer to ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.
ADC 466 Enclosure 3, Page 17

# Location 869F Requisition Follow-up Reason

6. 2/REF04-03/105 Remove Qualifier SS and notes: 

SS Split Shipment Number

Federal Note:

Use in conjunction with REF04-01 code W1 to identify the Turn-in 

document number suffix.

Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to 

identify the DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in REF04-02, enter the 

correlating DTID Suffix using this location. DLMS enhancement, see 

ADC 466.

Add new Qualifier W1 with DLMS notes:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the requisition document number (REF01

Code TN) when requisitioning a specific item from DLA Disposition 

Services.

2. When there is no Suffix Code (REF04 Code W8), associated with the 

customer’s Document Number, enter the correlating DTID in the 

REF04-02. If there is a Suffix Code, then enter the DTID in the REF04-

04. DLMS enhancement, see ADC 466.

The qualifier used 

to identify the 

DTID Suffix Code

is changed from SS 

to 60. This is to 

deconflict usage of 

the qualifier which 

supports to the 

transportation 

domain. 

Adds the DTID 

Suffix Code; 

adding the suffix at 

two locations 

within the 

composite allows 

for flexibility of 

data content.

7. 2/REF04-05/105 Add new Qualifier 60 with DLMS note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Code W1) to 

identify the DTID Number Suffix Code, when applicable. 

2. When the DTID Number is provided in REF04-04, enter the 

correlating DTID Suffix using this location. DLMS enhancement, see 

ADC 466.

Adds the DTID 

Suffix Code; 

adding the suffix at 

two locations within 

the composite 

allows for flexibility 

of data content.
ADC 466 Enclosure 3, Page 18

# Location 869F Requisition Follow-up Reason

8. 2/LQ01/140 Add new local code Qualifier DSI with DLMS notes:

DSI Disposition Services Indicator 

DLMS Note: 

1. DLA Disposition Services uses to provide relevant information 

applicable to the DLA Disposition Services business process supported by 

this transaction on an intra-DLA basis. Use multiple repetitions of the 

LQ Segment to include all applicable codes. Authorized DLMS 

enhancement for use by DLA Disposition Services. Refer to ADC 466.

2. The following Disposition Services Indicator values are available for 

use in the requisition transaction:

 MRA – Materiel Receipt Acknowledgment Required. 

 DMIL – DEMIL Certification Required. 

 MUTL – Mutilation Certification Required. 

 RCYL– Certificate of Recycling Required. 

 CIF – Container Issued in Full. 

 WALK–Walk-in Customer. 

 PICK- Customer Pick-up Required.

3. At this time a local code ‘DSI’ is established for use in 869F, version 

4010. A data maintenance action has been submitted for establishment of 

‘DSI-Disposition Services Indicator’ in a future version.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

9. 2/QTY01/150 Open QTY segment and add the following qualifier:

OC Order Count

DLMS Note: DLA Disposition Services uses to identify the total number 

of DTIDs in a specified container (i.e., the container count) when the 

entire container is being requisitioned. DLMS enhancement; Refer to 

ADC 466.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.

10. 2/FA201/ 286 Add Qualifier 18 and associated DLMS notes:

18 Funds Appropriation

DLMS Note:

1. Use to indicate the basic appropriation number.

2. Authorized DLMS enhancement for DLA Disposition Services to 

provide fund cite for FMS transportation billing. Refer to ADC 466.

3. Components are advised that the DoD is in the process of 

implementing Standard Financial Information Structure (SFIS) for all 

systems carrying/processing financial information (e.g., lines of 

accounting, fund codes). DLMS Qualifier 18 will be authorized at this 

time to support RBI legacy processes during transition to SFIS.

Supports RBI 

requirement.

Mapping is 

comparable to the 

DLMS 511R.
ADC 466 Enclosure 3, Page 19

I. Revise the DLMS 870S Supply Status as follows:

# Location 870S Supply Status Reason

1.

DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and Transaction 

Exchange associated with DLA Disposition Services under Reutilization Business 

Integration (RBI)

Identifies 

DLMS Changes 

included in the 

DS.

2. 2/REF04-

01/ 87

Existing qualifier and notes shown for context:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use in conjunction with the controlling document number for the transaction 

cited in REF01 Code TN. 

2. Use for DLA Disposition Services requisition supply status to identify the 

specific DTID number shipped under the controlling document number/suffix code. 

Authorized DLMS enhancement. Refer to ADC 455A.

Included for 

context. 

Note: Double 

mapping within 

the composite 

data field is not 

required for this 

transaction 

because the 

supply status 

document 

number suffix is 

already mapped 

to a different 

location: 

2/P101/150.

3. 2/REF04-

03/ 87

Add new Qualifier 60 and associated DLMS Note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (REF04 Qualifier W1) to identify 

the DTID Suffix Code, when applicable. DLMS enhancement, see ADC 466. 

Adds capability 

to identify the 

DTID Suffix 

perpetuated 

from the requisition to followon transactions.

J. Revise the DLMS 940R Materiel Release as follows:

# Location 940R Materiel Release Reason

1. DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and Transaction 

Exchange associated with DLA Disposition Services under Reutilization Business 

Integration (RBI)

Identifies 

DLMS Changes 

included in the 

DS.
ADC 466 Enclosure 3, Page 20

# Location 940R Materiel Release Reason

2. 2/N901 

/0400

Add new Qualifier 60 and associated DLMS Note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (N907 Code W1) to identify the 

DTID Suffix Code, when applicable. DLMS enhancement, see ADC 466. 

Adds capability 

to identify the 

Staffing Note:

DTID Suffix.

Suffix is 

mapped here 

due to lack of 

space within the 

N907. If all 

available locations in the 

composite data 

field are used 

for other content.

3. 2/N907-01 

/0400 

Modify DLMS Note 2:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use to identify the Disposal Turn-In Document (DTID) number when provided as 

a secondary reference number. The DTID Number is a unique number to identify 

property turned into a DLA Disposition Service Field Office.

2. Use in conjunction with the controlling document number for the transaction 

cited N901 code TN. When there is no Suffix Code associated with the controlling 

Document Number, enter the correlating DTID in the N907-02. If there is a 

Suffix Code, enter the DTID in the N907-06. Refer to ADC 466.

3. Authorized for intra-DLA use between DLA Disposition Services and DLA Disposition Field Offices. DLMS enhancement; Refer to ADC 434. 

Included for 

context. 

ADC 434 added 

the DTID as a 

secondary 

reference 

number to 

support RBI. 

Adding the 

DTID at both 

levels of the 

composite data 

element enables 

X12 compliance 

in the presence, 

or absence, of a 

suffix code for 

the materiel 

release order 

document 

number.
ADC 466 Enclosure 3, Page 21

# Location 940R Materiel Release Reason

4. 2/N907-03/ 

0400

Existing qualifier and notes shown for context:

0I Comparable Property Sale Reference Number

DLMS Note: 

1. Use to identify the DLA Sales Order Reference Number when provided as a secondary reference number. 

2. Use in conjunction with the controlling document number for the transaction cited N901 code TN and the DTID Number cited in N907 code W1. 

3. Authorized for intra-DLA use between DLA Disposition Services and DLA Disposition Field Offices. DLMS enhancement; Refer to ADC 434.

Included for 

context. 

5. 2/N907-05/ 

0400

Add new qualifier W1 and associated notes as shown:

W1 Disposal Turn-In Document Number (DTID)

DLMS Note: 

1. This is a unique number to identify property turned into a DLA Disposition 

Services Field Office. Use in conjunction with the controlling requisition document number identified (N901 Code TN), to identify the DTID associated with the 

property being requisitioned by a DLA Distribution Services customer

2. When there is no Suffix Code associated with the controlling Document Number, enter the correlating DTID in the N907-02. If there is a Suffix Code, enter 

the DTID in the N907-06. 

4. DLMS enhancement; refer to ADC 466.

Adding the 

DTID at both 

levels of the 

composite data 

element enables 

X12 compliance 

in the presence, 

or absence, of a 

suffix code for 

the Materiel 

Release Order 

document 

number.

6. 2/N101/110 Revise DLMS Note:

Z7 Mark-for Party

DLMS Note:

1. Use in redistribution orders, materiel release orders, historical materiel release

orders, materiel release order modifications, disposal release orders, historical

disposal release orders, and disposal release order modifications, to identify an

entity located within the ship-to address that is to actually receive the materiel.

2. For DLA Disposition Services public sales, the customer shall be identified as

the Mark-for Party using N102. Use in conjunction with N101, Code BS, Bill and

Ship To, identifying the unique DLA Disposition Services public sales DoDAAC.

No physical shipment is involved; public sales are designated for pick-up only.

Refer to ADC 463.

3. DLA Disposition Services uses to identify the Reutilization/Transfer/Donation 

(RTD) Web Application customer for pick-up of requisitioned property. The customer’s requisitioning DoDAAC will be identified as the Mark-For Party and the

customer name and phone number will be provided in the subsequent Point of 

Contact information (PER Segment). Refer to ADC 466.

3. DLMS enhancement; see introductory DLMS note 4a.

Allows 

additional use 

for RTD Web 

Customer Pickup.
ADC 466 Enclosure 3, Page 22

# Location 940R Materiel Release Reason

7. 2/PER01/

1120

Open PER Segment and PER01. Add Qualifier IC with DLMS notes as shown:

IC Information Contact

DLMS Note:

1. Use to identify the point of contact.

2. DLA Disposition Services uses to perpetuate the customer contact name and 

phone number provided by the RTD Web Application to the DLA Disposition Services Field Office. Use in the N1 Segment identifying the Mark For Party. Refer 

to ADC 466.

Supports RBI 

requirement to 

provide the 

customer POC 

information to 

DSS.

8. 2/PER02/

1120

Open PER02 and add DLMS note.

Name

DLMS Note: Provided the last name, first name, middle initial and rate/rank/title, 

as required, of the individual named as point of contact. Include blank spaces between name components and periods after initials.

Supports RBI 

requirement to 

provide the 

customer POC 

information to 

DSS.

9. 2/PER03/ 

1120

Open PER03 and add Qualifier TE.

TE Telephone

Supports RBI 

requirement to 

provide the 

customer POC 

information to 

DSS.

10. 2/LQ01/

1300

Revise DLMS Note as shown:

DSI Disposition Services Indicator

DLMS Note:

1. Use to provide relevant information applicable to the DLA Disposition Services

business process supported by this transaction on an intra-DLA basis. Use

multiple repetitions of the LQ Segment to include all applicable codes. Authorized

DLMS enhancement for use by DLA Disposition Services. Refer to ADC 434.

2. The following Disposition Services Indicator values are available for use in the

materiel release transaction:

CIF – Container Issued in Full. Use to indicate that all DTID Numbers

applicable to the specified container is issued on the same release order.

CM – Cancellation Mandatory. Use to indicate to the DLA Disposition Field

Office that the cancellation of the materiel release is mandatory.

CO – Cancellation Optional. Use to indicate to the DLA Disposition Field

Office that the cancellation of the materiel release is optional.

CS – DEMIL Condition of Sale Indicator.

3. At this time a local code ‘DSI’ is established for use in 940R, version 4030. A

data maintenance action has been submitted for establishment of ‘DSI-Disposition

Services Indicator’ in a future version.

Supports 

additional 

requirement for 

Condition of 

Sale.
ADC 466 Enclosure 3, Page 23

K. Revise the DLMS 945A Materiel Release Advice as follows:

# Location 945A Materiel Release Advice Reason

1. DLMS 

Introductory 

Notes

Add ADC 466 to DLMS Introductory Note 5:

- ADC 466, Revised Procedures to Support Requisitioning and Transaction 

Exchange associated with DLA Disposition Services under Reutilization Business 

Integration (RBI)

Identifies DLMS 

Changes included 

in the DS.

2. 2/N901 /40 Add new Qualifier 60 and associated DLMS Note:

60 Account Suffix Code

DLMS Note: 

1. Use in conjunction with the DTID Number (N907 Code W1) to identify the 

DTID Suffix Code, when applicable. DLMS enhancement, see ADC 466. 

Adds capability 

to identify the 

DTID Suffix.

Staffing Note:

DTID Suffix.

Suffix is mapped 

here match the 

DLMS 940R. To 

facilitate 

implementation, 

it is preferred that 

the mapping 

between the 

Materiel Release

Order and the 

Materiel Release 

Advice be as 

consistent as 

possible within 

the X12 standard.

3. 2/N907-

01/40 

Modify DLMS notes shown:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use to identify the disposal turn-in document (DTID) number when provided as 

a secondary reference number. The DTID Number is a unique number to identify 

property turned into a DLA Disposition Service Field Office.

2. Use in conjunction with the controlling document number for the transaction 

cited N901 code TN. When there is no Suffix Code associated with the controlling Document Number, enter the correlating DTID in the N907-02. If there is a 

Suffix Code, enter the DTID in the N907-04. Refer to ADC 466.

3. Authorized for intra-DLA use between DLA Disposition Services Field Offices 

and DLA Disposition Services. DLMS enhancement; Refer to ADC 449. 

Included for 

context; 

clarifying notes 

added. 

ADC 449 added 

the DTID as a 

secondary 

reference number 

to support RBI. 
ADC 466 Enclosure 3, Page 24

# Location 945A Materiel Release Advice Reason

4. 2/N907-

03/40

Add new qualifier W1 and associated notes as shown:

W1 Disposal Turn-In Document Number

DLMS Note: 

1. Use to identify the disposal turn-in document (DTID) number when provided 

as a secondary reference number. The DTID Number is a unique number to 

identify property turned into a DLA Disposition Service Field Office.

2. Use in conjunction with the controlling document number for the transaction 

(N901 Code TN). When there is no Suffix Code associated with the controlling 

Document Number, enter the correlating DTID number in the N907-02. If there 

is a Suffix Code, enter the DTID in the N907-04. Refer to ADC 466.

3. Authorized for intra-DLA use between DLA Disposition Services Field Offices 

and DLA Disposition Services. DLMS enhancement.

Adding the DTID 

at both levels of 

the composite 

data element 

enables X12 

compliance in the 

presence, or 

absence, of a 

suffix code for 

the materiel 

release order 

confirmation 

document 

number.
ADC 466 Enclosure 4, Page 1

Enclosure 4, Disposition Services Indicator

Disposition Services Indicator is a new code list to be added to the DLMS Data Dictionary. It addresses

DLA Disposition Services requirements for various indicators in the DLMS transactions to support business processes under RBI. The presence of the indicator value indicates that the specific condition applies 

(the equivalent of a positive yes/no indicator); if the condition does not apply the specific value will not be 

included in the transaction exchange. This data element is always mapped to LQ/1270 Qualifier ‘DSIDisposition Services Indicator’ and is used in multiple DLMS transactions. 

Dictionary Definition: The indicator addresses the DLA Disposition Services’ requirement to communicate unique property and/or materiel location information supporting their business processes.

Field Length: Min 2; Max 4

Indicators known to date are:

DIPSOSITION SERVICES INDICATOR:

INDICATOR EXPLANATION DESCRIPTION

AP Abandoned Property The AP indicator is used to specifically identify Abandoned Property, 

which is personal property left at an installation. All abandoned property is 

immediately assigned a SL (Sales) status at time of disposition. This value 

will be used at time of disposition so that a business rule can be created in 

EBS to trigger off the Abandoned Property indicator and assign the SL 

status. If this status is not included, EBS would treat this item as a normal 

re-utilizable item. (Refer to ADC 442.)

CIF Container Issued in Full Indicate all DTIDs in a container are on the same sales order.

CM

or

CO

Cancellation Mandatory

 or

Cancellation Optional 

This indicator will alert DSS to know whether a cancellation is mandatory 

(CM) or optional (CO). A cancellation is determined to be mandatory or 

optional based on the reason for rejection on the order. For example, if 

something about the property was determined to have changed (property

was re-identified, there was a DEMIL challenge, etc), then the cancellation 

is mandatory. 

DI DEMIL Instructions 

Available

Indicates directions were presented at receipt for how to DEMIL the 

property. 

HM Hazardous Materiel Hazardous Materiel.

HW Hazardous Waste Hazardous Waste.

HWPS Hazardous Waste Profile 

Sheet (HWPS) Available

Indicates an HWPS was turned in when the property was receipted

IC Inert Certificate 

Available

Inert Certificate is available.

RIP Receipt-In-Place Indicates property is receipted at a DLA Disposition Services Field Office, 

but is not physically located there. For example, if a large truck was being 

stored in a field, that truck wouldn’t necessarily be driven to a DLA 

Disposition Services Field Office to be brought on the inventory record. 

Instead it would be “receipted in place.” 
ADC 466 Enclosure 4, Page 2

DIPSOSITION SERVICES INDICATOR:

INDICATOR EXPLANATION DESCRIPTION

SALW Small Arms and Light 

Weapons 

The SALW indicator will be used to identify small arms and light weapons 

and enable rules based processing against these specific types of receipts. 

(Refer to ADC 442.)

WP Wash Post Indicates property was receipted as “Wash Post.” These items are tied to a 

Wash Post contract. These are items which are not brought onto the DLA 

Disposition Services inventory record until they are removed from their 

storage location, which is not at a DLA Disposition Services Field Office. 

At time of removal, DSS will send a goods receipt with the Wash Post 

Indicator populated to EBS. 

MRA Materiel Receipt 

Acknowledgment 

Required

Use to indicate that the customer ordering this materiel is subject to MRA 

procedures.

DMIL DEMIL Certification 

Required. 

Use to indicate to the DLA Disposition Field Office that post-issue tracking

is required to ensure that a certificate of demilitarization is provided by the 

customer prior to disposal or resale.

 

MUTL Mutilation Certification 

Required. 

 

Use to indicate to the DLA Disposition Field Office that post-issue tracking

is required to ensure that a certificate of mutilization is provided by the 

customer prior to disposal or resale. 

 

RCYL Certificate of Recycling 

Required.

Use to indicate to the DLA Disposition Field Office that post-issue tracking

is required to ensure that a certificate of recycling is provided by the 

customer prior to disposal or resale. 

WALK Walk-In Customer Use to identify a DLA Disposition Services walk-in customer who is 

ordering property while physically located at the Field Office.

PICK Customer Pick-up 

Required

Use to indicate to the DLA Disposition Field Office that the customer will 

pick-up property ordered.

CS DEMIL Condition of 

Sale Indicator.

Some items that will be available to the public are required as part of public 

sale to have parts of the item demilitarized upon completion of the sale. 

This indicator is passed from the Disposition Services eSales Website to 

DLA Dispostion Services (EBS) on the requisition. This indicator will be 

passed on the MRO to DSS, so that Disposition Services personnel are 

alerted to the action that is needed to be taken for the newly sold item. 
ADC 466 Enclosure 5, Page 1

Enclosure 5, DLMS Manual Revisions

Revise DOD 4000.25-M, Volume 2, Chapter 16, as follows. The text below overlaps (and supersedes) 

previously approved procedures. Paragraph numbering is approximate pending full re-write of this 

chapter for RBI-related changes.

C16.1.2. Submission of Requisitions to DLA Disposition Services 

C16.1.2.1. General. When DLA Disposition Services is notified of a turn-in to a DLA Disposition Services Field Office, via DLMS 527R Receipt transaction containing Disposition Category 

Code ‘RU’ Reutilization (see C16.6.?), the DTID and/or property is considered eligible for requisitioning and placed in a reutilization cycle which determines eligibility to requisition the item. There 

are four different CONUS screening periods within the RTD formal screening cycle: DoD Formal 

and Special Programs (Screening Cycle Code = DOD), General Services Administration (Screening 

Cycle Code = GSA), Donation (Screening Cycle Code = DON), and a second RTD screening cycle 

for items eligible to RTD customers (Screening Cycle Code = RTD2). OCONUS cycles are FEPP 

(for DOD, DOD special Programs, and Federal Civil Agencies; FEPD (for Donation); and RTD2 

for all. DoD customers can requisition an item at any time during the cycle; however, other agencies and groups only have access to the item once it reaches a certain day within that cycle. 

C16.1.2.1.1. All customers must have a valid DoDAAC in order to requisition DLA 

Disposition Services’ RTD property. Requisitions may be generated for DLA Disposition Services’ 

property via the DLA Disposition Services RTD Web, GSA Web or from Service/Agency supply systems. However, RTD Web will be the single interface by which DLA Disposition Services receives 

requisitions. GSA Web and Service supply system orders shall be routed by DLA Transactions Services to RTD Web prior to DLA Disposition Services. Once processed by RTD Web, any additional 

information/data elements which are maintained within RTD to facilitate processing shall be added 

to the requisition documents and transmitted to DLA Disposition Services. 

C16.1.2.1.2. All requisitions sent to DLA Disposition Services for ‘RU’ DTIDs are 

considered free-issue, except requisitions from FMS customers, which generate transportation costs. 

These transportation costs will be identified on the DLMS 511R Requisition transaction identified 

by a Funds Appropriation, e.g., Fund Cite or Line of Accounting. These costs are determined by the 

RTD Web based on the FMS customer’s profile and passed to DLA Disposition Services on the 

DLMS 511R Requisition. This Funds Appropriation/Funds Cite shall be perpetuated to the Field 

Office on the DLMS 940R Materiel Release Order (MRO) at the time the item is issued. 

C16.1.2.1.3. DTID and Suffix on Requisitions. Service System generated requisitions for DLA Disposition Service owned property are routed by DLA Transaction Services to RTD 

Web and are not required to cite a DTID, or DTID and Suffix, unless a specific property turn-in is 

being requested to fill the order. All customer requisitions originating via the RTD Web and GSA 

requisitions submitted to RTD Web are required to site specific DTID, or DTID and Suffix, as applicable. All requisitions forwarded from RTD Web to DLA Disposition Services for fulfillment, including Service System requisitions initially submitted without a DTID, will cite a DTID, or DTID 

and Suffix, as applicable. 
ADC 466 Enclosure 5, Page 2

C16.1.2.1.4. Want Lists. RTD Web customers are able to set up customized want-lists 

within RTD Web. Want Lists enable an automatic search of inventory and provide email notification if the specific property becomes available. Customers must log in to RTD Web to initiate the 

requisition request, or generate a requisition from the Service supply system. 

C16.1.2.2. Submission of Service System Generated Requisitions. RTD Web shall provide a 

daily asset inventory file to DLA Transaction Services to enable the Services to generate 

MILS/DLMS requisitions originating from their own supply systems based on the asset inventory 

file. DLA Transaction Services has a documented agreement with each customer to provide the asset inventory file under the Integrated Data Environment (IDE) initiative. Military Service/Agency 

supply systems, external to the DLA Disposition Services’ RTD Web, may direct requisitions to DLA 

Disposition Services (RIC S9D) without regard to specific DTID numbers contained within DLA 

Disposition Services’ inventory. These requisitions shall be forwarded by the DLA Transaction 

Services to the RTD Web for processing. 

C16.1.2.3. RTD Generated Requisitions. Items that are within the reutilization cycles are 

reported daily by DLA Disposition Services via a property characteristic flat file to RTD Web when 

the Screening Cycle Code is DOD or RTD2. This daily file to the RTD Web notifies the Web 

application of the available items. RTD Web maintains rules which determine eligibility to 

requisition specific items. For all requisitions prepared/generated within RTD Web, the document 

numbers shall be constructed using the customer’s DoDAAC, the current Ordinal date, and a serial 

number. The serial number may begin with a specific letter value based upon the applicable 

business process as discussed below.

 C16.1.2.3.1. Submission of Requisitions for Items Identified to a Container. To facilitate RTD, DLA Disposition Services employs a containerization process whereby the DTID of similar 

turned-in items is associated to a container and made visible to customers. Using this visibility, customers have the option of either requisitioning the whole container [through RTD only] or certain 

items from within the container. A separate requisition identifying the Disposition Container ID is 

sent for each item ordered by the customer whether the customer orders selected items within the container or not. If the customer selects the entire container, a separate requisition is still generated for 

each item within the container. Where multiple document numbers are needed to support customers 

ordering of containerized property, the RTD Web-generated document number shall assign serial 

numbers beginning with R. The generation of a distinct document number for each item ordered allows the customer to have visibility and status relative to the processing of each requisition, maintains 

container synchronization, and facilitates inventory control. In addition to the Disposition Container 

ID mentioned above, when the customer selects the entire container, each individual 511R Requisition 

(Transaction Type Code A0) shall include an indicator to communicate that the whole container is 

being requisitioned and total number of DTIDs within the container. 

C16.1.2.3.2. Local Stock Number (LSN) Requisitioning. LSN requisitioning will only 

be available via RTD Web. All property marketed via RTD Web will be by DLA Disposition Services’ 

LSN or NSN. In cases where an item is available for requisitioning in less than the standard unit of 

issue, the resulting DLMS 511R Requisition transaction sent to DLA Disposition Services shall include the ‘unit of use’ indicator to define the quantity and unit of measure as applicable to unit of use. 

The LSN will be identified as the primary identification and the NSN will be provided for cross reference.
ADC 466 Enclosure 5, Page 3

C16.1.2.4. General Services Administration (GSA) Web Requisitioning. Items that are 

within the reutilization cycles are reported daily by DLA Disposition Services via a property 

characteristic flat file to the GSA Web when the Screening Cycle Code is GSA or DON for CONUS, 

and FEPP or FEPD for OCONUS. This daily file to GSA notifies the Web of the available items. 

GSA Web maintains rules that determine who is eligible to requisition specific items. GSA 

customers are then able to requisition these items by generating a requisition. A daily batch file will 

be sent to DLA Transaction Services. Legacy 80-record position requisitions will be converted by 

DLA Transaction Services into DLMS 511R Requisition transactions and sent to RTD Web for 

processing. GSA shall use the DTID as the item control number which, along with a document 

number for each requisition, shall be sent to RTD Web.

==================================================================

C16.1.4. Processing Requisitions by DLA Disposition Services and the RTD Web

C16.1.4.7. Military Service/Agency Supply System Generated Requisitions. Once the RTD 

Web receives Military Service/Agency supply system generated requisitions, if a DTID is not identified, the DLA Disposition Services’ inventory shall be searched regardless of property location. 

C16.1.4.7.1. When a DTID number is not cited on a requisition transaction, the RTD 

Web will determine the applicable DTID number(s) necessary to fill the requisition, since DLA 

Disposition Services’ property is managed by LSN/NSN and DTID number. Each LSN/NSN and 

DTID number combination must be associated with a separate transaction. Therefore, in instances 

where property is physically located in multiple locations, or multiple DTID numbers are required to 

satisfy the requisition quantity, the RTD Web will be required to generate separate requisitions to 

DLA Disposition Services including the customer-assigned document number and sequentially 

assigned suffix codes as needed to fill the requested quantity. 

C16.1.4.7.2. When this occurs, the first partial fill action will be identified by the 

original document number submitted by the customer and shall cite Suffix Code A. For the open 

quantity remaining on the requisition, RTD Web will select the next available DTID and generate 

additional document number suffix codes as needed. 

C16.1.4.7.3. RTD Web will provide processing status via the 870S Supply Status 

transactions for the original customer document number including any suffix codes assigned by 

RTD Web.

C16.1.4.8. RTD Web Requisitioning. 

C16.1.4.8.1. When RTD Web receives the property characteristics file from DLA 

Disposition Services for items applicable to screening cycle codes DOD or RTD2, these items shall 

be visible on the web to all eligible customers. RTD Web uses prioritization logic to assign 

precedence to requisitions based on the type of customer requisitioning the item. The prioritization 

logic will be applied in a 24-hour cycle. As requisitions are generated in RTD Web, they are sent to 

DLA Disposition Services via DLA Transaction Services. At the end of the 24-hour cycle, 

depending upon the timing of the request and the highest priority for the requisitioned item, RTD 

Web shall determine which requisition(s) to fill. All other requisitions for the property/DTID shall 

be cancelled via notification from DLA Disposition Services to RTD Web. If the requisition 
ADC 466 Enclosure 5, Page 4

originated from the RTD Web, RTD Web shall cancel the requisition. When the user logs on, the 

cancellation(s) shall be visible in their account. If the requisition originated from a Service/Agency 

supply system, RTD web shall generate the 870S Supply Status with Status Code BQ to the Service’s 

supply system indicating cancellation. 

 C16.1.4.8.2. Customer Pick-up Required. The RTD-generated requisition 

transaction provided to DLA Transaction Services shall include a Disposition Services Indicator to 

indicate that the customer will pick up the property when applicable. The customer’s name and 

phone number will be included. This information must be perpetuated to the materiel release order 

to alert the DLA Disposition Services Field Office and to facilitate preparation of a customerspecific pick-list. 

C16.1.4.8.3 Prioritization will be applied to customers based on the following criteria: 

• U.S. DOD Military Customers, Priority Designator (PD) 1-15 (based upon 

Force/Activity Designator (F/AD) and Urgency of Need Designator (UND)).

• Law Enforcement Support Office (LESO), PD 15

• Senior Reserve Officers Training Corp (SROTC), PD 12-15 

• National Guard Units, PD 12-15 

• Deploying National Guard Units, based upon DoDAAC and/or F/AD assignment. 

• All Special Programs and walk-ins, PD 15

• Humanitarian Assistance Program (HAP), PD 15 

• DOD or Service Museums, PD 15

• Computers for Learning (CFL), PD 15

• Morale, Welfare, Recreation Activities (MWRA), PD 15

• Military Affiliated Radio System (MARS), PD 15 

• Civil Air Patrol (CAP), PD 15

• DOD Contractors, PD 15 

• Foreign Military Sales (FMS), PD 15 

C16.1.4.8.4. The two exceptions which can alter the 24-hour processing cycle are 

customer walk-in requisitions and FMS requisitions. 

C16.1.4.8.3.1. Customers who walk-in to a DLA Disposition Services Field 

Office and wish to requisition property must do so via RTD Web. These requisitions shall be 

identified on the 511R Requisition transaction sent to DLA Disposition Services by the entry of 

Disposition Services Indicator and unique document number with serial number beginning with L. 

These walk-in requisitions shall be processed immediately. DLA Disposition Services shall verify 

any pending requisitions for this item by DTID Number and fill all, part, or none of the walk-in 

requisition quantity, based upon the presence or absence of higher priority orders. 

C16.1.4.8.3.2. FMS customers with access to RTD Web have the option of 

freezing property by DTID. The capability to freeze items is provided to facilitate the State Department approval process for FMS customer eligibility. During the approval process, the items are 

flagged as ‘frozen’ both in DLA Disposition Services and at the Field Office, and are not advertised 

on the RTD Web to other customers. Once the FMS customer receives approval to acquire the item, 
ADC 466 Enclosure 5, Page 5

a requisition will be sent to DLA Disposition Services from RTD Web, and the item will be issued. 

Using RTD Web, Field Offices will be able to view a list of all items that are currently frozen and 

print out a placard to place on the frozen items, to insure walk-in customers know the item is not 

available. If an FMS freeze is in place, the property will NOT be available for screening for any 

other customer.

C16.1.4.9. Providing Status to Customers

C16.1.4.9.1. For Service/Agency supply system generated requisitions and GSA Web 

submitted requisitions, RTD Web will provide processing status via the 870S Supply Status transaction, citing the applicable status code found in DOD 4000.25-1-M, Appendix 2.16. As supply status 

on these requisitions is updated, RTD Web will provide supply status updates to ensure customers 

have the most current information available on their requisitions.

C16.1.4.9.2. For requisitions originated within RTD Web customers will have the 

ability to view current status of all their submitted requisitions on their account at the RTD Website. 

No DLMS 870S Supply Status transaction shall be generated for these requisitions. 

C16.1.4.9.3. Regardless of method of submission, when shipment occurs against a 

requisition, the DLA Disposition Services Field Office shall generate a DLMS 856S Shipment Status 

to the customer.

C16.1.4.10. Post-Issue Tracking. DLA Disposition Services shall use Disposition Services 

Indicator(s) to identify post-issue tracking requirements on the DLMS 511R requisition provided by 

RTD Web to DLA Disposition Services. Rules regarding requirements for post-issue tracking will 

be maintained in RTD Web, which shall send the appropriate post-issue tracking indicator to DLA 

Disposition Services to indicate which particular transaction requires post-issue tracking. If postissue tracking is required, DLA Disposition Services shall compile and store the requirement to facilitate future tracking. Record of the post-issue tracking requirement is maintained for the entire 

life of the item while being used by that particular customer. Post-issue tracking requirements are 

essential at time of disposal to ensure appropriate procedures have been followed, e.g., DEMIL Certificate turned in with the item. Post-issue tracking categories are described below. 

 C16.1.4.10.1. Materiel Receipt Acknowledgement (MRA) Required. This indicator will be 

applied to requisitions for DLA Disposition Services’ property falling outside standard MRA requirements under MILSTRAP/DLMS. DOD activities requisitioning from DLA Disposition Services are required to provide the 527R MRA (MILSTRAP DRA functionality) under current procedures.23

 C16.1.4.10.2. Demilitarization (DEMIL) Certification Required. Providing DEMIL documentation confirms when demilitarization was performed on property. Before this item can be 

turned in or disposed of by the customer, proof shall be provided to DLA Disposition Services.

 23 Expanded requirements for materiel receipt acknowledgment by DLA Disposition Services’ non-DoD customers are to 

be defined via future DLMS Change Proposal.
ADC 466 Enclosure 5, Page 6

 C16.1.4.10.3. Mutilation Certification Required. Providing Mutilation Certification 

when the item is no longer needed, prevents is reuse or reconstruction. Documentation must be received by DLA Disposition Services to verify that mutilation was completed.

 C16.1.4.10.4. Certificate of Recycling. The customer will provide proof via documentation 

that the item was recycled when no longer needed. 

 C16.1.4.1.5. Processing Requisitions Identified to a Container. When DLA Disposition Services 

receives a requisition with the Container Issued in Full indicator, the information will be used to 

insure all requisitions for that container are received and processed appropriately. Materiel Release 

Orders (MROs) generated by the DLA Disposition Services for requisitioned items associated with a 

container shall have the Disposition Container ID identified on the DLMS 940R Materiel Release. In 

addition to the Disposition Container ID, DLMS 940R Materiel Release transactions generated based 

on the customer ordering the entire container will contain a Container Issued in Full indicator and 

the count of total number of DTIDs within the container. This will allow DLA Disposition Services 

Field Offices to insure that an MRO for each item/DTID associated with a container is received and 

processed. Upon shipment of the materiel for each MRO, the DLA Disposition Services Field Offices 

will send the DLMS 856S Shipment Status transaction to the customer, containing DTID, original 

document number, and associated Disposition Container ID.
ADC 466 Enclosure 6, Page 1

Enclosure 6, Response to PDC Staffing and Comment Resolution

Originator Response/Comment Disposition

1. Navy The Navy concurs with PDC453 as written and 

submits no additional changes or amendments. 

However, the provisions of this PDC may impact 

NAVSUP Logistics Operation Center ammunition 

processes. It will require a business case analysis to 

determine the most appropriate method to handle the 

implementation of this PDC after it is approved and 

released by DLA Logistics Management Standards as 

an Approve DLMS Change.

Ammunition is outside the scope 

of DLA Disposition Services. 

Related property may be 

applicable.

2. Marine Corps Concur. Noted.

3. Air Force (AF) The AF non-concurs with comments. 

AO solicited AFGLSC Wings and Groups to review 

PDC 453 (T1). The 591 SCMG commented on a 

portion of para 3.b.(6): which states: "For the 

remaining open requisition quantity, the RTD Web 

will select the next available DTID, spin up a new 

document number using the DoDAAC/Julian Date of 

the original requisition and populate the serial number 

portion of the document number with Y001. This 

serial number will sequentially increase with this same 

format YXXX until the entire quantity of the 

requisition is filled.” Our two concerns are: 

- The Stock Control System (SCS) subsystem 

Reutilization/Disposition System (RDS, D035G) 

generates disposal release orders (DIC A5J) with 

document number serial numbers that begin with "Y". 

If the above scenario occurs for a requisition from the 

AF, it's possible the RTD Web-generated document 

numbers will duplicate document numbers generated 

from RDS. (Per later research codes R or T in rp 40 do 

not conflict with MILSTRIP.)

- If requisitions are filled with document numbers not 

initiated by an AF supply system, receipt transactions 

for those requisitions will fail in the supply systems.

Therefore, IAW DoD 4000.25.25-M, Military 

The ADC has been modified to 

use suffixing of the original 

document number rather than 

spinning up new document 

numbers (where the document 

number was provided via 

Service supply system 

requisition, as proposed for the 

Y-based serial number). 

However, this does not solve the 

apparent disconnect for RTD 

Web ordering, in general. 

Where the RTD-web must use 

multiple document numbers for 

the Web customer ordering a 

container, the document numbers 

will be begin with S to avoid 

conflict with the Air Force. 

Note to Air Force: Air Force 

may submit a DLMS Change 

Proposal documenting their 

requirement for use of document 

number serial numbers 

beginning with Y. Pending 

approval of a coordinated 

meaning for the Y, it has been

removed from the available list 
ADC 466 Enclosure 6, Page 2

Originator Response/Comment Disposition

Standard Requisitioning and Issue Procedures 

(MILSTRIP), we recommend using document number 

suffixes vice generating new document numbers. 

Unclear if they are going to create a new document 

number or if they were creating a new DTID number 

when they had to ship from several locations (para 

3.b.(6) on page 4 & 5). This would cause problems 

for the receiving community if they were talking about 

creating a new document number. This could also 

cause problems for ECSS when we try to receipt an 

item that we did not order. We should try to keep the 

processes the same across DOD and not make up new 

processes for just RBI (suffix codes, etc.). 

Also, the change in the document serial number (page 

7) would also cause changes to RDS; some of the 

codes they use today are being changed to "Reserved". 

This area would have no impact on ECSS at this time 

but would need to be accounted for in Release 2.

---Y was chosen for user-initiated disposals. Z is user 

for system generated disposals. And S is used for the 

requisitions for DRMO transactions. In order to meet 

PDC 496's requirement a CSRD is required for 

D035G, therefore the AF will not be prepared to 

receive the change.

of codes under MILSTRIP.

Under the approved procedures, 

shipment status will be provided 

regardless of whether the order 

originated in RTD Web or the 

Air Force supply system. 

Therefore, the Air Force RTD 

Web customer may be required 

to manually establish a due-in 

for the Air Force supply system 

or the shipment status may be 

used to systemically establish a 

due-in so that the receipt will 

post properly. 

Codes identified as Reserved in 

MILSTRIP are not considered to 

be available to the Services for 

internal use. 

4. Army Concur Noted.

5. MILSTRIP 

Administrator in 

coordination 

with J33

1. The spin-off document numbers using the “Y” in 

the first position of the serial number will used for 

RTD-web generated document numbers resulting from 

Component supply system MILSTRIP requisitioning. 

Will the “Y” indicator also apply to RTD-web 

generated document numbers resulting from full 

container ordering directly from the RTD Web?

2. Supply Status (870S) will be provided to 

customers order from their Component Supply 

System. RTD Web customers will get status via from 

RTD Web. How does EBS/RTD know which 

requisitions where created within RTD vs. submitted 

1. Under the ADC, the value Y 

will not be used at all due to a 

conflict with the Air Force. The 

value R will be applied 

exclusively to orders where 

multiple document numbers 

must be used to requisition 

property from a container. Use 

of a spin off document number 

subsequent to external supply 

system requisitioning has been 

replaced by business rules for 

suffixing the customer’s 

document number.
ADC 466 Enclosure 6, Page 3

Originator Response/Comment Disposition

from outside? How does RTD Web get the status to 

display for the customer (is there a communication 

from EBS to provide status)?

3. GSA customer orders are processed though DLA 

Transaction Services to RTD Web. How does the 

GSA customer get status? 

4. The FMS customer priority is identified as PD 

15 (lower than DoD customers). If the FMS customer 

places a freeze on an item while awaiting approval, 

will it be made available for a (late-requisitioning) 

DoD customer (with a higher priority) or will the FMS 

customer’s lower priority prevail? 

5. In PDC 543, Requisition under RBI, we are

updating the MILSTRIP requisition format to remove 

the DTID Suffix and I also removed the reference to 

the using EITHER a DTID or ERN (to order a specific 

item), so that it says customer can just enter the DTID. 

I didn't explain why the ERN reference was dropped. 

And I actually need to remove the ERN reference 

from the DD 1348-1A appendix and from the manual 

procedures (these too say enter DTID or ERN). 

Would you say we are removing the term ERN 

because it is obsolete terminology? I can make the 

remaining fixes for the ADC.

2. The ADC now clarifies that 

RTD Web customers must view 

status from the RTD Web. The 

RTD Web will recognize Webbased ordering vs. externally 

submitted requisitions. The 

status will be provided from 

RTD web and not EBS. 

3. GSA Web customers will 

receive supply status 

transactions.

4. If an FMS freeze is in place, 

the property will NOT be 

available for screening for any 

customer.

5. Yes, remove ERN as it has no 

meaning for Disposition 

Services.

6. USTRANSCOM USTRANSCOM agrees with the following comment:

"Due to required updates to USTRANSCOM systems 

in support of this PDC it is requested that the 

approved ADC, when released, include instructions 

that implementation date occur no sooner than 90 days 

from ADC release. This request will allow sufficient 

time to make necessary changes to affected systems."

Noted. 

7. DLA Concur. Noted.
ADC 466 Enclosure 6, Page 4

Originator Response/Comment Disposition

8. DLA J33 “If we’ve correctly captured procedures from the 

PDC, the only check for a higher priority requisition is 

done during “walk-in” requisition processing. Here an 

FMS customer can freeze an asset and that freeze 

prevents ALL others from obtaining that item – even 

during the approval process – regardless of the other 

customer’s priority, e.g., U.S. Forces. Is that really 

what you want?”

RBI Response: A Walk-in 

Customer would not be able to 

requisition property frozen for an 

FMS customer. The FMS 

property has already “ran” 

through the allocation process 

and has followed all priority 

procedures. FMS freezes should 

"run" in the nightly batch as with 

all other requests/ requisitions. 

They should be "allocated" the 

same as all other 

requests...priority code, then first 

come first served. For example, 

if an FMS freeze is input at 1300 

hrs, and another customer input a 

request at 0800 and they have 

the same priority, the 0800 

requisition should be approved, 

the fms freeze is not applied. If 

the FMS freeze is the first 

request and there are no other 

priority requests, the freeze 

should be put in place (after the 

batch runs), and the property is 

taken off of screening (just as it 

would if a "normal" requisition 

was approved)
ADC 466 Enclosure 6, Page 5

Originator Response/Comment Disposition

9. J33 “How would we know which guard unit is deploying 

based upon DoDAAC? Which PD are assigned to this 

group?”

RBI Response: This is a manual 

verification. Currently, if a 

guard unit requisitions with other 

than 15, we verify the DoDAAC 

in DLA TS and accept the PD as 

shown.

10. Disposition 

Services

Subsequent to staffing of the proposed change, it was 

identified that the requisition related transactions 

needed to be updated to support RTD-generated 

suffixing of the customer document number. This will 

allow the RTD application to support externally 

transmitted MILSTRIP/DLMS requisitions which do 

not identify a specific DTID Number and require 

Disposition Services to pull multiple DTID Numbered 

items to satisfy the quantity requisitioned. The 

addition of the requisition document number suffix 

code on the requisition will impact all transactions 

subsequent to the requisition. 

Subsequent to staffing of the proposed change, it was 

identified that the customer must be able to requisition 

by both DTID Number and the associated DTID 

Number Suffix Code. The DTID Number Suffix Code 

is retained from the original turn-in and is used for 

accountability of property within Disposition Services. 

This requirement was not correctly addressed in the 

proposed change. The addition of the DTID Suffix 

Code on the requisition will impact all transactions 

subsequent to the requisition.

Applicable transaction formats 

have been updated.

In most transactions, the DTID 

Suffix Code is mapped to a 

composite data field for 

secondary reference numbers. 

The composite data field can 

carry up to three pieces of 

secondary reference information, 

such as the document number 

suffix and the DTID Number. 

The placement of this data 

within the composite varies 

based upon which elements are 

used in a specific transaction. 

If the requirement for suffixing 

on the requisition document 

number and the DTID number 

throughout these transactions 

where identified during initial 

documentation for RBI, the 

mapping solution would have 

been simplified to move the 
ADC 466 Enclosure 6, Page 6

Originator Response/Comment Disposition

DTID number out of the 

composite data field. At this 

point, with implementation 

approaching, there is no 

opportunity to change the 

mapping for the DTID number, 

and so the DTID number suffix 

code follows the pattern used for 

DTID number (i.e., double 

mapping using multiple 

positions within the composite to 

allow for variations in the 

content. The exception to this is 

for the DLMS 940R (where the 

composite may be field due to 

other content) and the DLMS 

945A (to be consistent with the 

DLMS 940R).

11. J33 Is there any impact to the DTID (including DTID 

w/Suffix or UCN) used for accountability, if only a 

portion of the quantity under that DTID is 

requisitioned/issued. That is, will only the quantity 

available be updated and the controlling DTID value 

stay the same, or does the controlling DTID value 

need to be changed as well?

In terms of tracking remaining 

quantities as DTIDs are partially 

issued, we wouldn't need to 

change the controlling DTID 

when those quantities are issued.

The DTID will show the 

remaining quantity and would be 

available for customers to 

requisition until the full quantity 

of the DTID was exhausted. 

We don't do any type of 

suffixing of the DTID with the 

remaining quantity. The only 

updates that occur are to the 

quantities associated with the 

DTID. 

In EBS, we track total quantity 

of DTID at time of turn in, 

available quantity, and restricted

quantity (quantity that is 

currently attached to an open 

requisition).
ADC 466 Enclosure 6, Page 7

Originator Response/Comment Disposition

12. DLA Disposition 

Services

The screening cycles identified are applicable to 

CONUS. There are separate cycles for OCONUS.

ADC updated to show OCONUS 

cycles are FEPP (for DOD, DOD 

special Programs, and Federal 

Civil Agencies; FEPD (for 

Donation); and RTD2 for all. 

GSA flat file will be provided 

for OCONUS screening cycles

FEPP and FEPD.