Attachment

ADC 412

1 of 13

ATTACHMENT TO ADC 412

Intra-DLA Change - Establish New DLMS Supplement 846C, DLA Disposition Category 

Update Transaction and Procedures for use by DLA Disposition Services under RBI

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION.

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

b. Functional POC: DLA Logistics Information Service Agency-LAR, J6B

2. FUNCTIONAL AREA:

a. Primary Functional Area: Supply/Logistics

b. Secondary Functional Process: Distribution/Disposal

3. REFERENCES:

a. DLA Logistics Management Standards Office memorandum, December 21, 2011, 

subject: ADC 457, Intra-DLA Revisions to Procedures and DLMS 511R Requisition to 

Support Directed Release of Materiel (Post-Post Action) by DLA Disposition Services Field 

Offices under Reutilization Business Integration (RBI) (Staffed as PDC 432), available at 

www.dla.mil/j-6/dlmso/eLibrary/Changes/approved5.asp

b. DLA Logistics Management Standards memorandum, June 20, 2011, subject: PDC 434, 

Intra-DLA Revisions DLMS 527R Receipt and Associated Procedures Under Reutilization 

Business Integration (RBI), available at www.dla.mil/j-6/dlmso/eLibrary/Changes/proposed.asp

(ADC 442 is under development)

c. DLA Logistics Management Standards memorandum, October 31, 2011, subject: PDC 453,

Revisions to Procedures and DLMS 511R Requisition to Support Requisitioning from DLA 

Disposition Services under Reutilization Business Integration (RBI)

d. DOD 4160.21-M, Defense Materiel Disposition Manual, available at: 

www.dtic.mil/whs/directives/corres/pdf/416021m.pdf

e. Defense Reutilization and Marketing Service Instruction (DRMS-I) 4160.14, Operating 

Instructions for Disposition Management, available at:

webfnc.dispositionservices.dla.mil/gov/publications/4160.14/4160.14.shtml

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

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

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

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

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

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

enterprise suite of applications, including the Distribution Standard System (DSS) and the 

Enterprise Business system (EBS).
Attachment

ADC 412

2 of 13

NOTE: Significant changes from PDC 436 are highlighted in yellow throughout ADC.

a. Intent of the transaction: 

1) The Disposition Category Update transaction will be used to communicate a change in 

disposition category code between DLA Disposition Services Inventory Control Point (ICP) (Routing 

Identifier Code (RIC) S9D/S9W) (which uses EBS) and the DLA Disposition Services Field Office

(which uses DSS). The Disposition Category Update Transaction has beginning segment BIA02 Report 

Type Code PC. The Disposition Category Code assigned to a Disposal Turn-In Document (DTID) will 

impact which system will be responsible for issuing the inventory and the stowage process. Disposition 

Category codes are: Reject (RJ), Research (RS), Reutilization (RU), Sales (SL), and Disposal (DS). In 

addition, a Disposition Sub-Category Code will be added, when Disposition Category Code SL applies,

that will alert DSS if the item falls under Commercial Venture (CV) or Scrap Venture (SV).1

2) When EBS assigns Disposition Category Code DS-Disposal, DSS-Ultimate Disposal (DSS-UD) 

has the option of accepting, denying, or requesting a change for the category. When EBS sends DSS an 

846C Disposition Category Update transaction assigning category DS-Disposal for an item, DSS-UD will 

send an 846C Disposition Category Update Response transaction to EBS. The Disposition Category Update 

Response Transaction has beginning segment BIA02 Report Type Code 09. DSS will provide one of the 

following beginning segment BIA06 Action Codes in the Disposition Category Update Response transaction:

2-Change (Update)

CF-Confirm

DE-Deny

3) Summary of 846C Beginning Segment BIA02 Report Type Codes and BIA06 Action Codes:

BIA02 Report Type Code PC – used for the Disposition Category Update Transaction

DLA Disposition Services uses to provide Disposition Category updates. Used to communicate a change in disposition 

category code between DLA Disposition Services (which use EBS) and the DLA Disposition Services Field Offices 

(which use DSS). This transaction may be sent from the DLA Disposition Services ICP to the DLA Disposition 

Services Field Office; or from the Field Office to the ICP.

No BIA06 action codes are associated with a Disposition Category Code Update Transaction

BIA02 Report Type Code 09 - used for the Disposition Category Update Response Transaction

Sent from the DLA Disposition Services Field Office (using DSS) to DLA Disposition Services (using EBS) in 

response to a Disposition Category Update transaction from EBS that assigned Disposition Category Code DSDisposal. DSS-UD has the option of accepting, denying, or requesting a change for Disposition Category Code DSDisposal assigned by EBS. 

BIA06 Action Codes – A 

Response transaction is 

used with one of the 

following action codes:

Brief explanation:

2 - Change (Update) The change action code will be sent to EBS in response to the initial update to 

Disposition Category Code DS (Disposal), sent to DSS-UD. If DSS-UD determines 

that the item really can be sold via the ESales Web Site2, DSS-UD will send EBS a 

Disposition Category Update Response transaction with a change action code, and a 

Disposition Category Code SL (Sales).

 1 Refer to ADC 457 (reference 3a) for a more detailed explanation for the Disposition Services Business Type. 2 The ESales Web Site is the website is for selling disposition services property to the public.
Attachment

ADC 412

3 of 13

BIA06 Action Code: Brief explanation:

CF - Confirm If the disposition category update from EBS, for the disposition category DS 

(Disposal), is accepted by DSS-UD, DSS sends EBS a ‘confirm’ response 

transaction. This confirmation will trigger the update of the item into Disposal

category.

DE - Deny If the disposition category update from EBS, for the disposition category DS 

(Disposal), is not accepted by DSS-UD, DSS sends EBS a ‘deny’ response 

transaction. This denial will not allow EBS to continue processing the transaction 

as a disposal category transaction.

b. Scenario for which the transaction is used:

1) The disposition category code assigned during receipt will have two impacts: 1) the 

category will serve as an impact to DSS’s stow process and 2) the category will determine which 

system will be responsible for issuing the DTID. The DLA Disposition Services ICP (EBS) will

be responsible for issuing DTID records with disposition category codes of Reutilization (RU) or 

Sales (SL). The DLA Disposition Service Field Office (DSS) will be responsible for issuing 

DTID records with a disposition category of Disposal (DS). 

2) As a result of RBI, the DLA Disposition Services Field Offices using DSS are

required to manage the issue of property assigned a Disposition Category Code DS (Disposal). 

Disposal processes include, but are not limited to, Ultimate Disposal and Destruction, Precious 

Metals Recovery Program, De-manufacturing, Return-to-Manufacturer, and Abandonment and 

Destruction processes. DLA Disposition Services ICP (EBS) will not issue Materiel Release 

Order (MRO) transactions for property issued through disposal. 

3) DLA Disposition Services ICP (which uses EBS) will send its field office (which 

uses DSS) an 846C Disposition Category Update Transaction when an item is assigned a 

disposal disposition category code (DS). A DTID’s disposition category code can be updated 

multiple times while on record: 

a) When a generator turns-in material under a DTID into a DLA Disposition 

Services Field Office, the field office will send DLA Disposition Services ICP a synchronous 

real-time transaction to request disposition category assignment. This synchronous interface will 

send a non-DLMS intra-DLA XML transaction from DSS to EBS, and expect a return a nonDLMS intra-DLA XML transaction to be sent from EBS to DSS. The DLA Disposition 

Services ICP will assign one of five Disposition Category Codes depending upon the 

characteristics of the DTID: 

Reject (RJ),

Research (RS),

Reutilization (RU),

Sales (SL),

Disposal (DS). 

(1) After the DLA Disposition Services Field Office receiver verifies 

the receipt disposition category assignment from the DLA Disposition Services ICP (which 

uses EBS), the field office (which uses DSS) will send a DLMS 527R Receipt transaction 
Attachment

ADC 412

4 of 13

with the appropriate disposition category code to the ICP.

3 The DLA Disposition Services 

ICP will still receive a receipt transaction for this item, so that the item can be recorded in 

EBS for auditability purposes. There are also situations that occur if the controlled property 

rules change and the item’s disposition category changes to RU or SL. In this case, EBS 

would send a DLMS 846C Disposition Category Update transaction to DSS to have the 

disposition category flipped from DS to either RU or SL. A re-receipt of the item would not 

be required since the item already exists in EBS.

(2) Upon receiving the 527R Receipt transaction from the field office, 

Disposition Services ICP will evaluate the Disposition Category code of the receipted DTID. If 

the Disposition Category Code is DS, then the Disposition Services ICP/EBS trigger an 846C 

transaction to the field office/DSS. This transaction will notify the field office/DSS that the item 

will be sent to DSS-UD for disposal. When the item has been disposed, DSS will trigger a 

DLMS 867I Issue transaction if it was issued to another DLA Disposition Services Field Office 

(DEMIL Center or Controlled Property Center) or a DLMS 511R Post-Post Directed Materiel 

Release Order (MRO) (Document Identifier Code (DIC) CO_) if the item was issued to a DSS 

Disposal Customer.

(3) In some cases the request for disposition interface may not be 

functional or is disconnected for scheduled maintenance. In these cases, the DLA Disposition 

Services Field Office receiver will manually assign disposition category and include it in the 

527R Receipt transaction. If EBS determines the manually assigned disposition category code 

violates a DLA Disposition Controlled Property Rule when the system connection is restored, 

EBS will send an 846C Disposition Category Update transaction to advise the Field office/DSS 

of the appropriate disposition category code. 

b) The disposition category code is updated during the Reutilization, Transfer, and 

Donation (RTD) inventory aging and screening cycle within EBS. This typically is a 42 day 

cycle that all items go through (some items have a shortened aging cycle). There are four 

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

Programs (DOD) (only DOD and Special Program customers are permitted to requisition items 

while the inventory is in this cycle), General Services Administration (GSA) (other outside 

federal agencies known as Transfer customers are permitted to requisition items while the 

inventory is in this cycle), Donation (DON) (other outside federal agencies known as Donation 

customers are permitted to requisition items while the inventory is in this cycle), and RTD2. 

RTD2 is when all Reutilization customers can requisition items during the two-day period at the 

end of the Donation screening cycle. DTIDs within each screening period will have different 

RTD screening codes. 

c) The RTD screening code assigned to the DTID influences the inventory 

customers permitted to screen and requisition. 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, at that point the item is either assigned to a Disposal category (based on 

Controlled Property Rules) or it is assigned a Sales category. Items assigned a Disposal category 

trigger the 846C to DSS to move the item to DSS UD for disposal. Items assigned Sales 

 3 Refer to PDC 434 (reference 3b) for revisions to the 527R Receipt Transaction/procedures to support RBI.
Attachment

ADC 412

5 of 13

category if eligible for the Commercial Venture (CV) or Scrap Venture (SV) contracts are sent to 

DSS to identify these items as CV-eligible and will be placed in a CV area for the contractor to 

review.4

d) The Commercial Venture and Scrap Venture contracts relate to certain items 

once they become Sales eligible. They are then assigned Disposition Sub-Category Code CV (for 

Commercial Venture Items) or SV (Scrap Venture Items) depending on the item and whether it is 

currently on either of these contracts. This information will be passed to DSS along with the 

additional data elements listed in the mapping table below. This will allow DSS to create an 

internal MRO so that they can then “issue” the items, so that the contractor associated with the 

CV and SV contracts can come to the DLA Disposition Services Field Office and determine if 

they want the available items(s). If the contractor selects the items, then DSS will trigger a 

DLMS 511R Post-Post (DIC CO_) transaction to EBS so that EBS can decrement its inventory 

accordingly. If the items are not selected by the contractor, then DSS will send a DLMS 945A 

Denial to EBS to notify EBS that the items at that point are eligible for disposal or public sales.5

• If the DLA Disposition Services ICP (EBS) updates a DTID with 

a Disposal (DS) disposition category code because an item is not eligible for sale after RTD 

screening, EBS will send a DLMS 846C Disposition Category Update transaction to the DLA 

Disposition Services Field Office (DSS) to advise of the change from Disposition Category 

Code SL-Sales to Disposition Category DS-Disposal. The field office will use the update to 

initiate disposal processing. 

e) If DLA Disposition Services ICP updates a controlled property rule and that 

update results in an update to the disposition category code, the ICP (EBS) will send an 846C

Disposition Category Update transaction in two situations:

(1) If DLA Disposition Services ICP (EBS) updates a DTID to assign 

Disposition Category Code DS-Disposal because an item is no longer eligible for Reutilization

(Disposal Category Code RU) or for Sales (Disposal Category Code SL), EBS will send an 

846C Disposition Category Update transaction to the DLA Disposition Services Field Office 

(DSS) to advise of the change from Disposition Category Code RU or SL to Disposition 

Category Code DS. The field office will use the update to initiate disposal processing.

(2) If an item is currently assigned a Disposition Category Code DS 

(Disposal) and DLA Disposition Services ICP (EBS) determines the item is now eligible for 

Reutilization (RU) or Sales (SL), the ICP will send an 846C Disposition Category Update 

transaction to the field office to advise of the change from Disposal (Disposition Category Code

DS) to Reutilization (code RU) or Sales (code SL). The field office will use the update to 

request an item be pulled from disposal processing. 

f) During the precious metals analysis, the disposition field office determines it is 

more economical to sell DTID material for its precious metals content than to dispose it through 

the Precious Metals Recover Program:

 4 Refer to PDC 453 (reference 3c) for additional information regarding the RTD web process. Please refer to DOD 

4160.21-M (reference 3d) Chapter 5 Reutilization/Transfer Screening and Issue for further details (page 5-1) 5

Refer to ADC 457 (reference 3a) for additional information regarding the 511RPost-Post transaction.
Attachment

ADC 412

6 of 13

• If a DLA Disposition Service Field Office receiver updates a DTID to 

assign a Disposition Category Code SL (Sales) because of a request by a Disposition Services customer

to upgrade an item to sales, DSS will send an 846C Disposition Category Update transaction to DLA 

Disposition Services ICP (EBS) to advise of the change from Disposition Category Code DS (Disposal)

to SL (Sales). The DLA Disposition Services ICP will use the update to initiate sales processing. 

g) Use of 940R Material Release Order (MRO), 940R Redistribution Order

(RDO), 511R Post-Post Directed MRO (DIC CO_), and 867I Issue, associated with 

disposition category code update:

(1) DSS will generate internal DLMS 940R under various situations 

under RBI. All of these issues will be created on behalf of S9D/S9W (EBS). The trigger for 

DSS to generate a DLMS 940R is based upon DSS receiving a DLMS 846C. When the 846C is 

received by DSS, the data in the transaction will identify the Disposition Category Code. When 

it is identified with a Disposition Category Code of DS (Disposal), or SL (Sales) with a 

Disposition Category Sub-Category Code CV (Commercial Venture) or SV (Scrap Venture), 

DSS will generate the applicable 940R when necessary. The Document Number will be unique, 

and will be constructed with the DSS Field Office’s DoDAAC, followed by the current date in 

YJJJ format, followed by a unique serial number, e.g., SY205411390001, SY205411390002, etc.

(2) The DIC cited in the 940R transaction will either be an A2_, 

Redistribution Order, or an A5_, MRO, respectively. The determination of which will depend on 

where the materiel is being shipped. If the materiel is being shipped to another field office, then 

the A2_ Redistribution Order will be generated. If the material is being shipped or picked up by 

the customer, then an A5_ MRO will be generated.

(3) EBS will be notified that the field office has generated an Issue 

Document Number for a shipment via a 940R (Redistribution Order) or a 511R (Post-Post 

Directed MRO). When DSS creates a DLMS 940R on behalf of EBS for any DIC A2_ or A5_ 

transaction, DSS generates an outbound DIC A2_ or A5_ transaction and sends it to DLA 

Transaction Services (formerly DAASC). The DLMS 511R Post-Post and DLMS 867I Issue (D7_ 

functionality) will then be sent to DLA Transaction Services. Once the shipment is confirmed and 

shipped, the DLMS 945A and DLMS 856S will be sent. By sending the DIC A2_ or A5_ to DLA 

Transaction Services, the RDO/MRO, Issue, Confirmation, and Status will be available to those 

inquiring Web Visual Logistics Information Processing System (WebVLIPS), Logistics Data 

Gateway (LDG), etc.

(4) Once the Shipment has been made, DSS will generate an 856S Shipment 

Status to the customer, and a 945A Materiel Release Confirmation will be sent to S9D or S9W.

(5) Since the redistribution/release order were created in DSS, and not 

passed from EBS to DSS, DSS will back-fill DLA Transaction Services with the DIC A2_ or 

A5 transactions in legacy MILS format so that DLA Transaction Services can post the 

transaction on the applicable systems to tie the issue to the shipment status and confirmation.

STAFFING NOTE: This process should transition to DLMS. If MILSTRIP legacy format is 

used, too much of the extra data available in DLMS is dropped. If DLMS cannot be used at this 

time, Disposition Services should plan to transition at a later date. 
Attachment

ADC 412

7 of 13

h) Adding Disposition Category Change Reject Reason Code for the 

Commercial Venture (CV) and Scrap Venture (SV) processing:

(1) Subsequent to staffing of PDC 436, DLA added one additional data 

element, the Disposition Category Change Reject Reason Code, to the 846C Disposition Category 

Update transaction, to further assist the Commercial Venture (CV) and Scrap Venture (SV) process 

between EBS and DSS. 

(2) The Disposition Category Change Reject Reason Code, will be used 

solely by the Commercial Venture process in EBS. During the staging of items eligible for the 

CV contract in EBS, the Controlled Property Verification Officer (CPVO) will review the list of 

eligible CV items to see if any of the items have a data characteristic that would preclude it from 

being made available to the CV Contract vendor. The review of data characteristics includes 

items currently under Demil Code challenge, Demil Code change, Controlled Item Inventory 

Category (CIIC) change, Precious Metals Indicator Code (PMIC), and an additional option to not 

allow the item to be assigned to the CV contract based on additional feedback that could not be 

determined based simply on data characteristics.

(3) The CPVO will review the item’s CV eligibility. If approved for the 

CV contract, an 846C will be sent to DSS, and then it will follow normal processing as outlined 

in section b of this change. 

(4) Items that the CPVO determines are not CV-eligible will still trigger a 

DLMS 846C to DSS, but this 846C will contain Disposition Category Code DS instead of SL, as 

well as a Disposition Category Change Reject Reason Code reflecting the data characteristic or 

reason that the item is not going to be released to the CV contract. The reject reason code will 

alert the receiver that the item in question should be removed from the CV holding area at the 

warehouse (if it was prepositioned there) and that the item should be processed through DSSUltimate Disposal since the item is not eligible for sales.

(5) DLA states that the Disposition Category Change Reject Reason 

Code does not currently exist and will be published in DRMS-I 4160.14 (reference 3e). 

Accordingly, questions on the code, as well as proposed changes/additions/deletions to the code,

must be addressed through the proponent for DRMS-I 4160.14. 

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

no DLMS/DLSS equivalent transaction/process in use today.

5. APPROVED CHANGE(S):

a. Approved change in detail: This change enhances the business process using the new 

DLMS Disposition Category Update transaction for communication of disposition category

between DLA Disposition Services ICP and Field Offices operating under DSS and EBS. This 

change will allow all necessary data be sent between DSS and EBS in order for the disposition 

category to be accurately represented for each DTID. This disposition category will have two 

impacts: 1) the disposition category will serve as an input to the DSS stow process and 2) the 

disposition category will determine which system will process the property. There are five 

possible disposition categories: Reject, Research, Reutilization, Sales, and Disposal.
Attachment

ADC 412

8 of 13

b. Procedures: This change approves new procedures and a new DLMS Disposition 

Category Update transaction for intra-DLA use between the DLA Disposition Services ICP 

(which use EBS) and the DLA Disposition Services Field Offices (which use DSS).

1) EBS will prepare a DLMS 846C Disposition Category Update transaction and 

send the transaction to DSS to communicate an update to the Disposition Category Code. 

a) The disposition category will be one of the following: Reject, Research, 

Reutilization, Sales, or Disposal. The Disposition Category Code will be included on the 846C 

transaction and will have the following impacts:

(1) Serve as an input to the DSS stow process

(2) Determine which system processes the property

b) The Disposal Turn-In Document (DTID) Number will be passed to DSS on 

the 846C transaction from EBS, in addition to the materiel identification (e.g., NSN), in order to 

accurately identify the property for which a disposition category update is being sent. 

c) The DEMIL Code will be included on the 846C transaction. The DEMIL

Code will be used to determine/confirm the disposition category of a property. It will be used as 

an extra validation to ensure that EBS and DSS are in sync and also to confirm that a disposition 

category update should be made. If the code is different in EBS than DSS, then the disposition 

category may be inaccurate.

2) DSS will prepare a DLMS 846C Disposition Category Update transaction and 

send the transaction to EBS to communicate an update to the Disposition Category Code. 

a) The disposition category will be one of the following: Reject, Research, 

Reutilization, Sales, or Disposal. The Disposition category code will be included on the DLMS 

846C transaction and will have the following impacts:

(1) Serve as an input to the DSS stow process

(2) Determine which system will process the property

b) DSS shall pass the Disposal Turn-In Document (DTID) Number to EBS on 

the DLMS 846C transaction, in addition to the materiel identification (e.g., NSN), in order to 

accurately identify the property for which a disposition category update is being sent. 

c) The DEMIL Code shall be included on the DLMS 846C transaction. The 

DEMIL Code will be used to determine/confirm the disposition category of a property. It will be 

used as an extra validation to ensure that EBS and DSS are in sync and also to confirm that a 

disposition category update should be made. If the code is different in EBS than DSS, then the 

disposition category may be inaccurate.

3) DSS shall utilize specific data passed on the DLMS 846C when the Disposition 

Category Code is SL (Sales) and the Disposition Sub-Category Code is CV (Commercial Venture) 

or SV (Scrap Venture). These items have not been issued yet from EBS, so DSS will take the data 

passed on the 846C to generate an internal Material Release Order (MRO), so that the items can be 
Attachment

ADC 412

9 of 13

staged for acceptance/pick-up by the contractor. Once the items have been picked up by the 

contractor, DSS will trigger a DLMS 511R Post-Post to EBS, so that EBS’s inventory can be 

decremented. In the case of CV items, there can be several hundred items per week that will be 

passed to DSS; to minimize the number of pick tickets that can be generated, EBS will also include 

a header document number that will tie all of these items into a single pick ticket. 

4) The same process will occur when a DLMS 846C is sent to DSS and the Disposition 

Category Code is DS (Disposal). EBS will pass all of the appropriate information in the 846C for 

DSS to generate an internal MRO, so the item can be sent to DSS-UD. A DLMS 867I Issue or 

DLMS 511R Post-Post (refer to ADC 457) will be passed to EBS once the item has been issued 

from DSS-UD, so that EBS can correctly decrement its inventory.

c. Alternatives: EBS and DSS will not be able to support the RBI processes of communicating 

a change in disposition category codes using DLMS standard transactions and will need to consider 

nonstandard options.

6. REASON FOR CHANGE: As a result of RBI, DLA Disposition Services will need EBS and 

DSS to communicate Disposition category updates between the DLA Disposition Services ICP

(S9D/S9W) using EBS, and its field offices using DSS. These changes will ensure a more 

streamlined process for changing disposition categories for items that are at the field office storage 

locations. 

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages: DLA EBS and DLA DSS will be able to comply with DLMS standards for 

the RBI process.

b. Disadvantages: None identified.

8. DEFENSE AUTOMATIC ADDRESSING SYSTEM (DAAS) MAPPING: Requires DAAS 

update to process new DS 846C. This is a new DLMS transaction with no Defense Logistics Standard 

System (DLSS) legacy equivalent transaction, so there is no mapping requirement between DLMS and 

DLSS.

9. NOTE ANY REGULATIONS OR GUIDANCE: May require DLA update to appropriate 

DLA Disposition Services publication. See impact paragraph.

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

11. IMPACT:

a. Publications: 

1) Requires creation of a new DLMS 846C, Disposition Category Update transaction.

2) Requires update to DOD 4000.25-M, DLMS, Volume 2, Chapter 16, to add 

procedures for the DLA Disposition Services business rules for the Disposition Category Update 

process.
Attachment

ADC 412

10 of 13

a) Refer to Enclosure 1 for the DLMS procedures for Section C16.6.9., Disposition 

Category Code Assignment and Associated Action.

b) Refer to Enclosure 2 for the DLMS procedures for section C16.6.5., Relocation 

Between DLA Disposition Services Field Offices. 

3) DRMS Instruction (DRMS-I) 4160.14, Operating Instructions for Disposition 

Management (reference 3e), requires update by the appropriate DLA office, to include, as a 

minimum, publication of several new codes used by DLA Disposition Services under RBI as 

documented in this and other RBI-related ADCs. These codes include, but are not limited to, 

Disposition Category Code, Disposition Sub-Category Code, Reimbursement Code, Disposition 

Category Change Reject Reason Code, and Disposition Services Customer Type. DRMS-I 4160.14 

is not under the purview of DLA J627; the requirement to update the DLA Disposition Services 

publication is noted here as a courtesy. 

b. Automated Information Systems (AIS):

1) DLA: Impacts DAAS, EBS, and DSS.

2) Service AIS: No impact. This is an intra-DLA requirement (EBS-DSS interface only)

c. New DLMS Transaction: DLMS Supplement (DS) 846C, Disposition Category Code 

Update transaction.

d. DLMS 846C Data:

1) Data Content Table: Refer to Enclosure 3 for the Data Content Table. A data 

maintenance (DM) is required to establish ASC X12 data element 1270 code DCR -

Disposition Category Change Reject Reason Code.

2) New DLMS Data:

a) Disposition Category Update indicates an update to the disposition category

by Disposition Services.

b) Action Code (846C) (Disposition Category Update Response) - Disposition 

Services Field office uses to accept, deny, or request a change when 

Disposition Services assigned Disposition Category Code DS-Disposal.

c) Consecutive Delivery Order Count is an incremental count of orders against 

the maximum number of orders. To be used only for RBI to identify each 

item that will make up the weekly delivery order sent to DSS. (min/max 1/5)

d) Maximum Delivery Order Count is the maximum number of orders. To be used 

only for RBI to identify each item that will make up the weekly delivery order sent 

to DSS. (min/max 1/5)

e) Disposition Services Container ID [Renames “Disposition Container ID” from

ADC 410.] 

f) Disposition Services ICP Sales Document Number identifies the MRO for DLA 

Disposition Services Field Office when creating an internal MRO transaction.
Attachment

ADC 412

11 of 13

g) Quantity Total to be Issued on a Commercial Venture Contract

h) Demilitarization Integrity Code is used to determine/confirm the disposition category 

of a property.

i) Disposition Services Container Issued in Full Indicator identifies if all the 

contents of a Disposition Services container were sent.

j) Disposition Category Code indicates the current method of asset disposition 

assigned to a Disposal Turn In Document (DTID).

k) Disposition Sub-Category Code indicates how DLA Disposition Services 

ICP shall process a release order based on the sub-category code passed.

l) Disposition Category Change Reject Reason Code provides the reason a 

change in the disposition category was rejected.

m) Disposition Services Complete Container Count represents the total 

number of DTIDs in a specified disposition services container.

n) Date of Contract Expiration - Disposition Services Scrap Venture Contract.

12. PDC 436 COMMENTS DISPOSITION:

# ORGANIZATION COMMENT DISPOSITION

1 DLA Concur, with comments:

2 DLA RBI Lead 

5/10/2011 

Comments

RBI will need the following new fields: 

Unit of Measure; 

Container ID: Some items that have a 

Disposition Category Change, if part of a container 

will need to be identified by that Container ID;

Complete Container Count: This will be 

required if there are multiple items in a container 

that are undergoing a Disposition Category change;

Disposition Category Change Reject Reason 

Code. These will be needed by DSS to identify 

when an item has a disposition category change; 

These codes will need to be added to the Disposition 

Services process manual. These do not currently 

exist anywhere. 

REFER TO THIS ADC, paragraph 4.b.3)h) on 

pages7, for additional information on use of this 

code.

Added. Opened 2/QTY03/3200 Unit of 

Measure. Refer to 846C Data Content 

Table, rows 32-33.

Added Disposition Services Container 

ID at 2/REF01/1400. Refer to Enclosure

3, DS 846C Data Content Table, row 24.

Added Disposition Services Complete

Container Count at 2/QTY01/3200. 

Refer to Enclosure 3, DS 846C Data 

Content Table, row 31.

Added DCR-Disposition Category 

Change Reject Reason Code at 

2/LQ01/3760. Refer to Enclosure 3, 

846C Data Content Table, row 45.

The DLMS office will submit a DM to 

ASC X12 for this code.

NOTE: The “Disposition Category 

Change Reject Reason Codes” will be 

published in DRMS-I 4160.14.
Attachment

ADC 412

12 of 13

# ORGANIZATION COMMENT DISPOSITION

3 DLA RBI Lead 

8/26//2011 

Comment

Commercial Venture Count Mechanism: 

The Commercial Venture (CV) EBS count mechanism 

will be used solely by the process in EBS to aid DSS 

in the bundling of the CV Contractor actual location 

report requirement. This counter must be passed to 

DSS on the 846C to indicate when a Delivery Order 

has been exhausted, thus ensuring that the total 

location information will be sent to GL. 

This counter will be used to identify each item that 

will make up the weekly delivery order sent to DSS. 

This counter will allow DSS to validate that each 

item on the weekly delivery order is received by 

validating each item via the counter passed in this 

field. It is quite possible that the weekly delivery 

order for CV can consist of several thousand items. 

Since each 846C sent to DSS will only be for one 

item, there needs to be a way for DSS to verify that 

they have received all of the transactions for the 

weekly CV order.

The CV counter will be used to identify when all 

DLMS 846C transactions have been received and 

processed to a DLMS 940R, and staged for CV, 

then a list can be generated for the CV Contractor.

Added requirement for a count 

mechanism by opening up the 

2/MEA/0400 segment and adding 2 

distinct qualifiers to provide the

Consecutive Delivery Order Count and the 

Maximum Delivery Order Number. 

Refer to Enclosure 3, 846C Data Content 

Table, rows 18-21.

4 DLA RBI Lead 

10/19/2011 

Comment

RBI Lead comment: In discussions with DLA J6O -

we have one additional field that we need to add to 

the 846C. This is an action code that will be sent on 

the 846C from DSS-UD to EBS, in response to an 

846C EBS sends to DSS-UD when a Disposal status 

is assigned for an item. DSS-UD has the option of 

accepting the Disposal status assigned by EBS or 

Rejecting the status. There will be three codes used 

these codes are:

RQ-request for change, CF-confirm or DN-deny

It could go in the BIA06 Header field - this field is 

identified as an Action Code field and we think it is 

most appropriate one to use since it is being used in 

response by DSS-UD in response to an 846C sent 

by EBS. EBS will process transaction sent back 

from DSS-UD based on what is populated in this field.

DLA Logistics Management Standards 

recommends using a BIA02 Report Type 

Code for the Response transaction, with 

BIA06 Action Codes to identify: Request

for Change; Confirm; and Deny.

This approach is consistent with design of

the 846A transaction which uses BIA02 

Report Type Code to identify a Response 

transaction with BIA06 Action codes for 

the specific types of responses.

Refer to Enclosure 3, 846C Data Content 

Table, rows 7 and 11.

DLA response 10/24/2011: 

DSS and EBS agree with proposed 

transaction layout.

5 DLA RBI Lead

12/22/2011

Remove the serial number from 846C transaction. Closed the LS LOOP containing serial 

number. Refer to Enclosure 3, 846C Data 

Content Table, rows 50-53.

6 Air Force Concurs without comment Noted.

7 Navy Concurs as written. Noted.

8 Marine Corps Concurs as written. Noted.

9 Army Concurs without comment Noted.
Attachment

ADC 412

13 of 13

# ORGANIZATION COMMENT DISPOSITION

10 DFAS No comment. Noted.

11 DLA Logistics 

Management 

Standards office

MILSTRIP 

Administrator

These MRO data elements are included in 846C so 

that DSS can create internal MRO, are in the post-post 

transaction format and may even be required. My 

point was that DSS team needed guidance for the data 

fields and not a decision to put the data elements into 

the 846C (at least for some of the data). It seems like 

there is no variable data applicable to the internal 

MRO applicable to Disposition Category DS or SL 

that would require EBS to decide how the fields 

should be filled and then pass that information to DSS 

so that DSS can build the post-post transaction. 

Therefore, it doesn't seem right to ask both sides to 

program this capability for the 846C. I was looking 

for an EBS response saying which data elements can 

be dropped from the 846C format since they will never 

be populated (left blank because optional) and which 

need a default value in DSS due to a required entry (if 

any have variable data applicable to DS or SL, then 

they would need to be retained). I was looking for 

someone to verify my interpretation and provide the 

guidance. 

If I have misunderstood the applicability of the data 

elements or the process then I can withdraw the 

comment.

Project Code -- I suspect this is never going to be 

applicable Priority;

Designator Code -- I suspect this should be a default of 

15 in the post-post;

Advice Code -- I suspect that this is never going to be 

applicable;

Supply Condition Code -- don't know if this could vary 

or if a default would be appropriate; Management 

Code -- I suspect that this is never going to be 

applicable;

Ownership Code -- I suspect that this should be a 

default of 2 (for DLA);

Distribution Code -- I suspect that this is not 

applicable to this process (or possibly a default for 9).

Yes, the post-post must be created by DSS based upon 

information provided by EBS, However I am 

specifically questioning the need for EBS to pass the 

values needed to build the post-post transaction for 

selected data elements listed (since these data elements 

seem to be either never applicable to this type of postpost action or would never vary). 

RBI Lead Response:

EBS will provide default values for the 

fields DSS needs to process MRO on their 

end. We have worked with Chris Oxley 

to identify the fields and default values 

we will pass.

Enclosures
Enclosure 1-Procedures, Section C16.6.9

ADC 412

1 of 4

ENCLOSURE 1 to ADC 412

Revise DOD 4000.25-M, DLMS, Volume 2, Chapter 16, section C16.6.9., as follows. 

These procedures are new in their entirety and were not staffed with PDC 436. Paragraph 

numbering is approximate pending full re-write of this chapter for RBI-related changes.

C16.6.9. Disposition Category Code Assignment and Associated Action. When generators turn-in 

material under a DTID to a DLA Disposition Services Field Office, the Field Office shall send DLA 

Disposition Services a non-DLMS synchronous real-time transaction to request disposition category 

assignment. Depending upon the characteristics of the DTID property, DLA Disposition Services’ 

response shall assign one of the following five Disposition Category Codes: Reject (RJ), Research 

(RS), Reutilization (RU), Sales (SL), or Disposal (DS). After the DLA Disposition Services Field Office 

receiver verifies the receipt disposition category assignment from DLA Disposition Services, the Field 

Office will send a DLMS 527R Receipt transaction with the appropriate disposition category code (see 

paragraphs C16.6.8.1. and C16.6.8.2. above). 

C16.6.9.1. The Disposition Category Code assigned to a DTID determines how the property is 

processed subsequent to receipt; e.g. reutilization, disposal, etc. In addition, the category will 

determine the Field Office stow process, and which activity will be responsible for the issue of DTID 

property. The DLA Disposition Services will be responsible for issuing DTID records with Disposition 

Category Codes of RU or SL, except when the SL Disposition Category Sub-Category Code is CV 

(Commercial Venture) or SV (Scrap Venture). The Disposition Service Field Office will be responsible 

for issuing DTID records with a disposition category of Disposal (DS), or Sales (SL) with a Disposition 

Category Sub-Category Code CV or SV.

C16.6.9.2. The DLA Disposition Service Field Office shall issue DTID property based on 

the Disposition Category Code and additional data reflected in the DLMS 846C. For these 

issues, the Field Office shall create an internal DLMS 940R (either Redistribution Order or 

Material Release Order, as appropriate). For material release to customers of DS material, or 

SL material with subcategory CV or SV, see paragraph C16.6.9.4. For relocation/redistribution 

of DS material to another DLA Disposition Services Field Office, see paragraph C16.6.5. 

C16.6.9.3. There are multiple situations when DLA Disposition Services and the DLA Disposition 

Services Field Office validate or change the Disposition Category Code assigned to a DTID in the initial 

527R Receipt transaction. The 846C Disposition Category Update transaction (Report Type Code PC

update), shall be used by DLA Disposition Services for these communications. For instances where a 

response is warranted, the 846C, Disposition Category Update Response transaction (Report Type Code 

09 response), will be used by DLA Disposition Field Offices. A summary of when the 846C is used to 

validate/change initially assigned disposition category codes are as follows:

C16.6.9.3.1. Upon receiving the Receipt transaction from the Field Office, DLA 

Disposition Services shall validate the disposition category code of the receipted DTID. If Disposition 

Category Code DS is assigned, and DLA Disposition Services agrees, a DLMS 846C Disposition 

Category Update transaction shall be generated to the Field Office citing category code DS. This 

transaction will notify the Field Office that the item shall be sent to Ultimate Disposal and shall 

contain data required by the DLA Disposition Field Office to construct internal MROs or RDOs as 
Enclosure 1-Procedures, Section C16.6.9

ADC 412

2 of 4

required to issue the property. Upon receipt of the 846C Disposition Category Update transaction 

indicating Ultimate Disposal, the Field Office will generate a DLMS 846C Disposition Category 

Update Response to DLA Disposition Services confirming, changing or denying the assigned DS

category code. If confirmed, the Field Office will subsequently generate the DLMS 867I Issue 

transaction to DLA Disposition Services if the property is issued to another DLA Disposition Services 

Field Office (DEMIL or Controlled Property Center) (see paragraph C16.6.5.3.2.) or the DLMS 511R 

(post-post Directed MRO (DIC C0_)) if the property is issued to a disposal customer (see C16.6.9.4.).

C16.6.9.3.2. If DLA Disposition Services updates/changes a controlled property 

rule, the Disposition Category Code of the DTIDs affected by this change may be updated. This 

can occur prior to or during the Reutilization, Transfer, and Donation (RTD) screening cycle. 

DLA Disposition Category Codes can be changed among DS (Disposal), RU (Reutilization) or 

SL (Sales). If the property goes through the complete RTD cycle and is not requisitioned, it shall 

be assigned Disposal Category Code DS or Disposition Category Code SL-Sales via generation 

of the 846C update transaction by DLA Disposition Services. This transaction shall contain data 

required by the DLA Disposition Field Office to construct internal MROs. Items assigned a 

disposal category are processed as described above. Some DTID property assigned Disposition 

Category Code SL-Sales are further identified by a disposition sub-category code in the 846C as 

being eligible for Commercial Venture (CV) or Scrap Venture (SV) contracts and are processed 

as described below.

 

C16.6.9.3.2.1. Sales Category (SL) Sub-Category Commercial Venture 

(CV). DLA Disposition Services has a partnership with a commercial venture firm to sell DoD 

surplus property following the RTD screening cycle. DLA Disposition Services shall identify 

property categorized for CV and send the DLMS 846C Disposition Category Update transaction 

to the Field Office to initiate processing. Upon receipt of the 846C indicating commercial 

venture, the Field Office shall generate the DLMS 846C Disposition Category Update Response 

transaction to DLA Disposition Services confirming or changing the assigned disposition 

category codes.

 

C16.6.9.3.2.1.1. When the Controlled Property Verification 

Officer (CPVO) at the Field Office determines material is not CV eligible, the Disposition 

Category Update Response transaction shall contain disposition category of DS instead of SL, as 

well as a Disposition Category Change Reject Reason Code, as published in DRMS-I 4160.14, 

reflecting the data characteristic or reason the item will not be released to the CV contract. DLA 

Disposition Services shall in turn send the update 846C to the Field Office. The reject reason 

code shall cause the Field Office to remove the property from the CV holding area at the 

warehouse and allow the item to be processed through Ultimate Disposal. 

C16.6.9.3.2.1.2. When the Field Office determines the material is 

CV eligible, the Field Office shall send the DLMS 511R (post-post directed MRO) transaction to 

DLA Disposition Services for inventory issued to the CV customer (see C16.6.9.4.).

C16.6.9.3.2.2. Sales Category (SL) Sub-Category Scrap Venture (SV). 

DLA Disposition Services has a partnership with a scrap venture firm to manage the receipt, 

marketing and sale of surplus scrap property generated by DoD installations. DLA Disposition 

Services shall identify property categorized for SV and send the DLA Disposition Services Field 
Enclosure 1-Procedures, Section C16.6.9

ADC 412

3 of 4

Office an 846C Disposition Category Update to initiate SV processing. The Field Office shall 

send DLMS 511R (post-post directed MRO) transactions to DLA Disposition Services for all 

inventory issued to the SV customer (see C16.6.9.4.).

NOTE: Section C16.6.9.4. below is also published by ADC 457:

C16.6.9.4. Directed Release of Disposal and Sales DTID Property (Post-Post Action). 

DLA Disposition Services Field Offices shall send the DLMS 511R, DLA-Directed MRO (DI 

Code C0_) Type Transaction Code A0/Action Code J, to DLA Disposition Services after property 

has been issued. Upon receipt, DLA Disposition Services shall drop its inventory balance. In 

this instance, no materiel release order is sent to the Field Office, as this 511R is for inventory 

reduction vice shipping (the material has already been delivered or picked up).

C16.6.9.4.1. For these issues, the Field Office shall create an internal DLMS 940R 

MRO using a unique document number constructed by using the Field Office DoDAAC and 

current ordinal date, followed by a unique 4-digit serial number, e.g., SY205411390001, 

SY205411390002, etc. The Field Office shall then decrement the owner balance, create and exit 

the 511R directed MRO, position the MRO for release, and once released, generate the DLMS 

945A Materiel Release Confirmation to the owner and 856S Shipment Status to the customer. 

Materiel release confirmations for both scrap and commercial venture property shall use the 

transportation mode code for “Bearer, Walk-Thru (Customer Pickup of Material)” to indicate 

no physical shipment is involved.

C16.6.9.4.2. The DIC cited in the internal 940R will be A5_, MRO since the 

property is being shipped or picked up by a customer.

C16.6.9.4.3. Since these transactions are internal to the Field Office, a copy shall 

be passed to DLA Transaction Services to be posted in the DAAS so that the complete issue, 

confirmation, and status history are maintained. 

C16.6.9.5. Post-post requisitions from the DLA Disposition Services Field Office shall be 

identified by Disposition Category Code and Disposition Sub-Category Code. A Disposition 

Category Code DS indicates the material has already been issued. As discussed above, 

Disposition Category Code SL (Sales) with the Disposition Sub-Category Code CV (Commercial 

Venture) indicates the property was issued to the commercial venture customer. Use of 

Disposition Category Code SL with Disposition Sub-Category Code SV indicates the property 

was issued to a scrap venture customer.

C16.6.9.6. DLA Disposition Services specific DLMS 511R DLA-Directed MRO 

transactions will always display a RIC-To S9W or S9D. RIC-To S9W shall be used to indicate 

property issued from a Recycling Control Point; RIC-To S9D shall be used to indicate property 

issued from a DLA Distribution Services Field Office. 

C16.6.9.7. Upon receipt of these types of DLMS 511R transactions, DLA Disposition 

Services shall determine the type of post-post order that should be generated based upon the 

Disposition Category Code/Disposition Sub-Category Code. Disposition Category Code DS 

shall indicate a DLA Disposition Services post-post disposal order and will prompt a search for 

the Disposal Consolidation Number (DCN). 
Enclosure 1-Procedures, Section C16.6.9

ADC 412

4 of 4

C16.6.9.7.1. The Field Office shall include the DCN on the 511R. It is used by 

DLA Disposition Services to tie multiple post-post disposal order transactions to a common sales 

document. The DCN is used to facilitate item grouping in a common shipment and to reduce the 

amount of sales documents required. 

C16.6.9.7.2. DLA Disposition Services shall include the inventory on the 511R to 

an existing sales document when a match is found. If no match is found, a new internal disposal

post-post sales order shall be created.

C16.6.9.8. DLA Disposition Services Post-Post SV Orders. The DLA Disposition Services 

Field Office shall send DLMS 511R post-post requisitions using Disposition Sub-Category Code 

SV to DLA Disposition Services each time SV customers remove property for a scrap DTID from 

a DLA Disposition Services Field Office. DLA Disposition Services shall create a post-post 

sales order for each DLMS 511R DLA-Directed MRO transaction received from the Field Office. 

DLA Disposition Services shall assign DTID Numbers associated with the material on the postpost order based on First In-First Out (FIFO) order, limiting selection to DTID numbers with an 

available quantity on the DTID Table. DLA Disposition Services shall first add a new record to 

the Sales Order DTID Table and include: DTID Number, post-post order number, quantity, 

date, and order type; and then update the inventory record by decreasing the available quantity 

for the DTID.

C16.6.9.9. DLA Disposition Services Post-Post CV Orders. The DLA Disposition Services 

Field Office shall send DLMS 511R post-post requisitions using Disposition Sub-Category Code 

CV to DLA Disposition Services each time CV customers remove property for a commercial 

venture DTID from a DLA Disposition Services Field Office. DLA Disposition Services shall 

create a post-post order for each 511R DLA-Directed MRO transaction received from the Field 

Office and add a record to the Sales Order DTID Table to include: DTID Number, post-post 

order number, quantity, date, and order type; and then update the inventory record by 

decreasing the available quantity for the DTID.

C16.6.9.10. Billing for Material. The DLMS 511R transactions for scrap and commercial 

venture will indicate non-Interfund billing to the contractor (Fund Code XP) and the customer 

shall be billed prior to removal of the material. The DoDAAC of the commercial or scrap 

venture firm will be identified as both the ordered-by and ship-to activity. For 511R DS 

transactions, the Signal Code M shall to indicate there will be no billing. In addition, the 

DoDAAC of the disposal customer will be identified as both the ordered-by and ship-to activity. 

When a Unit of Use LSN is being issued, the DLMS 511R shall carry both the Unit of Use LSN 

and the cross-reference LSN. The Unit of Use Indicator defines the quantity and unit of measure 

applicable to the unit of use.

C16.6.9.11. For DLMS 511R directed MROs with Disposition Category Code DS 

involving the disposal of SA/LW, the serial number/UII will not be populated on the transaction. 

The serial number/UII will only be present on the 945A confirmation. 
Enclosure 2-Procedures, section C16.6.5

ADC 412

1 of 3

ENCLOSURE 2 to ADC 412

Revise DOD 4000.25-M, DLMS, Volume 2, Chapter 16, section C16.6.5., as follows. 

These procedures are new in their entirety and were not staffed with PDC 436. Paragraph 

numbering is approximate pending full re-write of this chapter for RBI-related changes.

NOTE: The section C16.6.5 procedures and transactions below are not specific only to the 

process addressed by this ADC, but they were not published by any other ADC:

C16.6.5. Relocation Between DLA Disposition Services Field Offices. 

C16.6.5.1. In all instances when relocation of materiel between DLA Disposition Services 

Field Offices is necessary, the DLA Disposition Services will direct this action by using the 

DLMS 940R, Redistribution Order (Transaction Type Code NI), and sending it to the shipping 

Field Office, except when the Disposal Category Code for the DTID is DS Disposal. The 

shipping Field Office shall always provide a DLMS 856S, Shipment Status (Transaction Type 

Code AS), to the receiving Field Office and the DLMS 945A, Redistribution Order Shipment

Confirmation (Transaction Type Code NJ), to DLA Disposition Services upon shipment. 

C16.6.5.2. For all relocation actions between Field Offices, DLA Disposition Services 

shall generate a DLMS 527D, Prepositioned Material Receipt (PMR) (Transaction Type Code 

DE), to the Field Office designated to receive the relocated material. The PMR shall contain 

2/LIN01/10 code N (Return to inventory of material relocated between storage activities without 

change in ownership (MILSTRAP DIC DWK functionality)). DLA Disposition Services shall 

include the DTID number in the PMR in order for DTID number accountability to be maintained 

across multiple locations. The DTID value 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. Additionally, when 

an entire container is identified for transfer between Field Offices, the PMR shall contain the 

Disposition Services Container ID. Upon receipt of the materiel, the receiving Field Office shall 

provide the DTID and the Disposition Services Container ID provided in the PMR to DLA 

Disposition Services using DLMS 527R, Receipt, (Transaction Type Code D4) identified by 

2/LIN01/10 code N (MILSTRAP DIC D6K functionality).

C16.6.5.3. Relocation of Disposal Category Code DS (Disposal) Items Between DLA 

Disposition Services Field Offices. 

 C16.6.5.3.1. Turn-in material to a DLA Disposition Service Field Office under a 

DTID may initially or subsequently be assigned Disposal Category Code of DS (Disposal) (see 

C16.6.9.). DLA Disposition Service Field Offices are responsible to manage the issue of 

property assigned Disposition Category Code DS (Disposal) and to update DLA Disposition 

Services’ owner record for all property managed by DLA Disposition Services Field Offices, to 

include Disposal category property. 

C16.6.5.3.2. The 867I, Issue (Relocation) transaction (Product Transfer Type Code 

BJ), will be used to track material issues between DLA Disposition Service Field Offices for 
Enclosure 2-Procedures, section C16.6.5

ADC 412

2 of 3

disposal items required to be relocated to another DLA Disposition Service Field Office; e.g., 

DEMIL Field Office. In these cases, the DLA Disposition Service Field Office shipping the 

materiel shall send DLA Disposition Services the DLMS 867I Issue transaction for each DTID or 

Scrap LSN quantity being relocated. DLA Disposition Services uses the Issue transaction to 

update the owner record.

C16.6.5.3.2.1. For these issues, the Field Office shall create an internal DLMS 

940R Redistribution Order using a unique document number constructed using the Field Office 

DoDAAC and current Julian date, followed by a unique 4-digit serial number, e.g., 

SY205411390001, SY205411390002, etc. The Field Office shall then decrement the owner 

balance, create and exit the DLMS 867I Issue, position the Redistribution Order for release, and 

once released, generate the DLMS 945A Redistribution Order Shipment Confirmation to the 

owner and the DLMS 856S Shipment Status to the receiving Field Office using the Defense 

Automatic Addressing System (DAAS). 

 C16.6.5.3.2.2. The MILSTRIP DIC cited in the internal DLMS 940R will be 

A2_, Redistribution Release Order (RDO) since the materiel is being shipped to another Field 

Office.

 

 C16.6.5.3.2.3. Since these transactions are internal to the Field Office, a copy 

shall be passed to DLA Transaction Services to be posted in the DAAS so that the complete issue, 

confirmation and status history are maintained. 

 C16.6.5.3.3. Disposal Consolidation Number (DCN). DLA Disposition Services 

requires the use of a unique DCN to support the grouping of property relocated during the 

disposal process. A unique DCN will be generated for each group of items that are issued 

(relocated) in a single shipment. Each DLMS 867I Issue, shall contain the DTID as a secondary 

number in the transaction to support identifying inventory at a level lower than the document 

number or DCN. DLA Disposition Services shall compile each individually received Issue 

(Relocation) transaction with the same DCN into one Redistribution Order (RDO) document, 

thus reducing the volume of RDO documents created. The DCN is a unique 10-digit number 

with positions 1-3 equal to the DLA Disposition Service Field office RIC and positions 4-10 

equal to a unique alphanumeric serial number. There is only one DCN per RDO.

 

 C16.6.5.3.4. Upon receipt of the DLMS 867I Issue transaction, DLA Disposition 

Services will decrement the on-hand balance record for the submitting DLA Disposition Service 

Field Office and generate an internal RDO or modify an existing internal RDO. For these 

relocations, no RDO (DLMS 940R, Type Transaction Code NI) will exit the DLA Disposition 

Services system.

 C16.6.5.3.5. DLA Disposition Services will check the DCN on the DLMS 867I Issue 

transaction against previously created internal RDOs. If the DCN is present on an existing 

RDO, the DTID will be added as a new line item. If the DCN is not present on an existing RDO, 

the DLA Disposition Services system will create a new internal RDO. 
Enclosure 2-Procedures, section C16.6.5

ADC 412

3 of 3

 C16.6.5.3.6. The quantity on the DLMS 867I Issue transaction shall be used to 

populate the RDO quantity field and shall be reflected as in-transit until the DLMS 527R Receipt 

transaction is processed from the receiving DLA Disposition Services Field Office.

 C16.6.5.3.7. If property which requires DEMIL needs to go to a different Field Office 

(DEMIL Facility) and the size and/or weight limits the use of one conveyance, partial shipments 

may occur. The first partial shipment shall include two document numbers - the RDO document 

number (i.e., the controlling document number) and the original DTID from the issuing/losing 

field office as a secondary reference number. This document number shall be reported by the 

DLA Disposition Services Field Office on the DLMS 527R Receipt transaction submitted to DLA 

Disposition Services. 

 C16.6.5.3.8. When the second partial shipment arrives at the DEMIL facility, the RDO 

document number cannot identify the receipt by itself due to the disposition services duplicate 

DTID business rule. Therefore, a Unique Control Number (UCN) shall be created by Field Office 

personnel to receipt the remainder of the property, causing three document numbers to be 

associated with the shipment/receipt transaction: (1) the original RDO document number serving 

as the primary document number for the new receipt, (2) the original DTID from the issuing/losing 

Field Office (secondary reference number), which is perpetuated from the RDO, (3) plus the UCN 

generated to prevent DTID re-use. These document numbers are all linked and all three will be 

reported on the DLMS 527R Receipt transaction submitted to DLA Disposition Services
Enclosure 3

ADC 412

1 of 15

ENCLOSURE 3 TO ADC 412

DLMS 846C (X12 Version/Release 4030), Disposition Category Update

Transaction, 

Data Content Table

Data requirements which were not identified in PDC 436 are highlighted at rows 7, 11, 18-21, 

24, 31, 32, 33, and 46

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

1. Introductory 

cover page 

Notes

Federal Notes 1. Inventory Control Point/owners and storage activities 

use this transaction set to convey changes in the 

disposition category of material. 

2. Use one occurrence of this transaction set to transmit a 

single or multiple transactions.

3. DoD logistics users should refer to the Defense 

Logistics Management System (DLMS) Supplement to the 

Federal Implementation Convention (IC) available at 

URL: www.dla.mil/j-6/dlmso. The DLMS Supplement 

provides specific business rules, conditions, and 

authorized codes necessary for appropriate use of this IC 

within the DLMS.

2. Introductory 

cover page 

Notes

DLMS Notes 1. This The Disposition Category Update transaction is 

used between the DLA Disposition Services Inventory 

Control Point (ICP) and the DLA Disposition Services

Field Offices to communicate a change in Disposition 

Category. The Disposition Category Update transaction 

may be sent from the DLA Disposition Services ICP to the 

DLA Disposition Services Field Office; or from the field 

office to the ICP. The Disposition Category Update 

Response transaction is sent from the field office to the 

Disposition Services ICP. This transaction represents a 

DLMS enhancement in its entirety. There are no DLSS 

equivalent transactions.

2. Users operating under the Defense Logistics 

Management System (DLMS) must reference the Unit of 

Issue and Purchase Unit Conversion Table, 

Transportation Mode of Shipment Conversion Table and 

Accounting Classification Appendix which can be found 

on the DLA Logistics Management Standards web site at 

www.dla.mil/j-6/dlmso.

3. This DLMS Supplement 846C contains data associated 

with a DLMS enhancement authorized for implementation 

by DLA Disposition Services. This data should be adopted 

during, or subsequent, to modernization when applicable 

to the DLA Disposition Services business process.

4. This transaction may be used to provide Unique Item 

Identifier (UII) information. Refer to the Unique 

Identification (UID) web at URL: 

www.acq.osd.mil/dpap/sitemap.html for DoD policy and 
Enclosure 3

ADC 412

2 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

business rules.

5. This revision to the DLMS Supplement incorporates 

Proposed DLMS Change (PDC) and Approved DLMS 

Change (ADC) listed. PDCs/ADCs are available from the 

DLA Logistics Management Standards web site 

www.dla.mil/j6/dlmso/elibrary/Changes/processchanges.asp

- ADC 412, Intra-DLA Change - Establish New DLMS 

Supplement 846C, DLA Disposition Category Update 

Transaction and Procedures for use by DLA Disposition 

Services Under Reutilization Business Integration (RBI) 

(Supply)

3. 1/ST01/0100 Transaction Set 

Identifier Code 

Code uniquely identifying a Transaction Set 3/3

4. 1/ST02/0100 Transaction Set 

Control Number 

Identifying control number that must be unique within the 

transaction set functional group assigned by the originator 

for a transaction set.

4/9

5. 1/ST03/0100 Implementation 

Convention 

Reference

Reference Assigned to Identify Implementation 

Convention

DLMS Note: Use to indicate this transmission uses the 

846C DLMS Supplement. Enter the DLMS Supplement: 

004030F846C0CA00

16/16

6. 1/BIA01/0200 Transaction Set 

Purpose 

Code identifying purpose of transaction set

00 Original

77 Simulation Exercise

DLMS Note: Use to identify a simulated mobilization 

exercise transaction set. Activities initiating simulated 

mobilization exercises must ensure complete coordination 

with all activities involved. All transaction set recipients 

must use extreme caution to ensure that individual 

transactions do not process as action documents which 

affect accountable records.

ZZ Mutually Defined

DLMS Note: 1. Use to identify the Unit of Use Indicator. 

When included, the quantity and unit of measure values 

associated with this transaction are applicable to the unit 

of use.

2. Authorized for DLA Disposition Category Update.

2/2
Enclosure 3

ADC 412

3 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

7. 1/BIA02/0200 Report Type Code Code indicating the title or contents of a document, report , 

or supporting item

PC Process Change Notice

DLMS Note: Use to identify a Disposition Category 

Update transaction. DLA Disposition Services uses to 

provide Disposition Category updates. This transaction 

may be sent from the DLA Disposition Services ICP to the 

DLA Disposition Services Field Office; or from the field 

office to the ICP.

09 Progress Report

DLMS Note: Use to identify a Disposition Category 

Update Response transaction. DLA Disposition Services 

Field office uses with DSS-Ultimate Disposal to respond to 

DLA Disposition Services ICP (which uses EBS) to accept, 

deny, or request a change when EBS assigned Disposition 

Category Code DS-Disposal. Must use with one of BIA06 

Action Codes 2, CF, or DE.

2/2

8. 1/BIA03/0200 Reference 

Identification 

Reference information as defined for a particular 

Transaction Set or as specified by the Reference 

Identification Qualifier

Federal Note: Use Code “Z” for this data element to 

satisfy mandatory X12 syntax requirements

1/50

9. 1/BIA04/0200 Date Date expressed as CCYYMMDD

Federal Note: This date is the date of transaction set 

preparation and corresponds to the Universal Time 

Coordinate (UTC)

8/8

10. 1/BIA05/0200 Time Time expressed in 24-hour clock time as follows: HHMM, 

or HHMMSS, or HHMMSSD, or HHMMSSDD, where H 

= hours (00-23), M = minutes (00-59), S = integer seconds 

(00-59) and DD = decimal seconds; decimal seconds are 

expressed as follows: D = tenths (0-9) and DD = 

hundredths (00-99)

Federal Note: 1. Express the originating activity's time of 

transaction set preparation in UTC.

2. Express time in a six-position (HHMMSS) format.

6/6
Enclosure 3

ADC 412

4 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

11. 1/BIA06/0200 Action Code Data element level notes:

Federal Note: Use any code

DLMS Note: Action codes are only used with Disposition 

Category Update Response transactions (BIA02 code 09). 

In DLMS, only the following codes are authorized.

Code indicating a type of action

2 Change (Update)

DLMS Note: Use in conjunction with BIA02 code 09 

only. DLA Disposition Services Field Office uses to notify 

the Disposition Services ICP that the proposed Disposition 

Category Code DS-Disposal will be overturned with a

Disposition Category Code SL-Sales.

CF Confirm

DLMS Note: Use in conjunction with BIA02 code 09 

only. DLA Disposition Services Field Office uses to

confirm the Disposition Category Code DS-Disposal 

assigned to the DTID by the Disposition Services ICP.

DE Deny

DLMS Note: Use in conjunction with BIA02 code 09 only. 

DLA Disposition Services Field Office uses to deny the 

Disposition Category Code DS-Disposal assigned to the 

DTID by the Disposition Services ICP.

12. 1/N101/0800 Entity Identifier 

Code 

Code identifying an organizational entity, a physical 

location, property or an individual

SB Storage Area

DLMS Note: Use to identify a DLA Disposition Services 

Field Office depot or storage activity. 

Z4 Owning Inventory Control Point

DLMS Note: Use to identify the DLA Disposition 

Services ICP. 

2/2

13. 1/N103/0800

1/N104/0800

Identification Code 

Qualifier 

Identification code

Code designating the system/method of code structure 

used for Identification Code (67)

10 DoDAAC

M4 DoD RIC

Code identifying entity

2/2

2/80

14. 1/N106/0800 Entity Identifier 

Code 

Code identifying an organizational entity, a physical 

location, property or an individual

FR Message From

Federal Note: Must use in conjunction with 1/N101/0800 

code SB or Z4 to identify that the organization cited in 

N104 is originating the transaction set.

2/3
Enclosure 3

ADC 412

5 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

15. 2/LIN02/0100

2/LIN03/0100

Product/Service ID 

Qualifier

Product/Service ID

LIN02 level notes:

Federal Note: Use any code.

DLMS Note: 1. Use only one of codes FS or SW to 

identify the material. 2. For DLMS use only the following 

codes are authorized.

FS National Stock Number

SW Stock Number

DLMS Note: Use to identify a local stock number (LSN).

STAFFING NOTE: RBI team stated that only NSN or 

LSN will be used.

2/2

1/48

16. 2/LIN04/0100

2/LIN05/0100

Product/Service ID 

Qualifier

Product Service ID

FS National Stock Number

DLMS Note: The NSN is provided as a cross-reference 

when unit of use indicator is included and the unit of use 

Local Stock Number (LSN) is identified as the primary 

materiel identification. Authorized for use by DLA 

Disposition Services.

SW Stock Number

DLMS Note: 1. Use to identify the local stock number 

(LSN).

2. The LSN is provided as a cross-reference when unit of 

use indicator is included and the unit of use LSN is 

identified as the primary materiel identification. 

Authorized for use by DLA Disposition Services.

2/2

1/48

17. 2/LIN06/0100

2/LIN07/010

Product/Service ID 

Qualifier 

Product Service ID

Code identifying the type/source of the descriptive 

number used in Product/Service ID (234)

Federal Note: Use any code.

DLMS Note: 1. DLA Disposition Services uses to identify 

the Reference Materiel Number when materiel turned in to 

a Disposition Field Office was determined to be scrap and 

a scrap LSN was cited at LIN02/03. The NSN/LSN which 

the generator identified when material was turned in is 

populated as the Reference Material Number. 

2. For DLMS use only the following codes are authorized.

FS National Stock Number

SW Stock Number

DLMS Note: Use to identify the local stock number 

(LSN) 

2/2

1/48
Enclosure 3

ADC 412

6 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

18. 2/MEA/0400 Commercial 

Venture Count 

Mechanism

Measurements

Open Segment 2/MEA/0400 for use in DS 846C

This counter will only be used for the Commercial 

Venture (CV) process. It will not be used for any other 

processes that are part of the RBI project. 

This counter will be used to identify each item that will 

make up the weekly delivery order sent to DSS. This 

counter will allow DSS to validate that each item on the 

weekly delivery order is received by validating each item 

via the counter passed in this field. It is quite possible that 

the weekly delivery order for CV can consist of several 

thousand items. Since each 846C sent to DSS will only be 

for one item, there needs to be a way for DSS to verify that 

they have received all of the transactions for the weekly 

CV order.

To specify physical measurements or counts, including 

dimensions, tolerances, variances, and weights

Segment Level DLMS Note: Must use two iterations with 

Commercial Venture processing to provide a Commercial 

Venture Count Mechanism. The Commercial Venture 

Count Mechanism is made up of 2 fields: the 

consecutive delivery order count and the maximum 

delivery number (e.g., for CV count 1001 of 2000: 1001 

is the consecutive delivery order count; 2000 is the 

maximum delivery number)

19. 2/MEA01/0400 Measurement 

Reference ID

Code identifying the broad category to which a 

measurement applies

CT Counts

DLMS Note: Use with Commercial Venture processing to 

indicate that Consecutive Delivery Order Count and 

Maximum Delivery Order Number information is 

provided.

2/2

20. 2/MEA02/0400 Measurement 

Qualifier

Code identifying a specific product or process 

characteristic to which a measurement applies

UG Usage

DLMS Note: Use with Commercial Venture processing to 

provide the Consecutive Delivery Order Count. 

MX Maximum

DLMS Note: Use with Commercial Venture processing to 

provide the Maximum Delivery Order Number.

2/2

21. 2/MEA03/0400 Measurement Value NOTE: DLA Dispositions Services stated that the 

Consecutive Delivery Order Count and Maximum 

Delivery Order Number will be a maximum of 5 positions.

1/20
Enclosure 3

ADC 412

7 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

22. 2/DTM01/1000

2/DTM02/1000

Date/Time 

Qualifier 

Date

Code specifying type of date or time, or both date and time

097 Transaction Creation

DLMS Note: Use to identify date the transaction was 

prepared.

093 Contract Expiration

DLMS Note: Use to advise DSS which Scrap Venture 

items are going to expire on the SV contract. The date 

listed will be the last day that item is valid for the contract

3/3

8/8

23. 2/CTP02/1100 Price Identifier 

Code

STA Standard Price

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to ‘DS-Disposal’ or ‘SL-Sales’. This field 

is required for the DLA Disposition Services Field Office 

to create an internal Materiel Release Order (MRO) 

transaction.

3/3

24. 2/REF01/1400 Reference 

Identification 

Qualifier

Code identifying Disposition Services Container ID

98 Container/Packaging Specification Number

DLMS Note: Use to identify the Disposition Services 

Container Identification (ID).

2/2

25. 2/REF01/1400 Reference 

Identification 

Qualifier

TN Transaction Reference Number

DLMS Note: This is the controlling document number. 

STAFFING NOTE: The W1 DTID qualifier is only 

added when the DTID is needed as a secondary reference 

in addition to the controlling document number (TN). 

Otherwise the DTID maps to the document number field 

(TN). For the 846C, DLA Dispositions did not identify a 

requirement for DTID as a secondary reference to be used 

at the composite in conjunction with a controlling 

document number in REF01.

2/2

26. 2/REF01/1400 Reference 

Identifier Qualifier 

FU Fund Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction. 

2/2
Enclosure 3

ADC 412

8 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

27. 2/REF01/1400

2/REF02/1400

Reference 

Identification 

Qualifier 

Reference 

Identifier

SM Sales Office Number

DLMS Note: 1. Use to identify the DL A Disposition 

Services ICP Sales Document Number.

2. This field is only used when the DLA Disposition 

Services ICP is updating the Disposition Category Code to 

DS-Disposal or SL-Sales. This field is required for the 

DLA Disposition Services Field Office to create an 

internal MRO transaction.

STAFFING NOTE: When a MRO is sent to DSS for a 

sales order line item, the header level document number 

will be passed. By passing this number, DSS will be able 

to tie in individual MROs together into one pick ticket 

This will reduce the workload for the Field Office 

employees. EBS will pass the EBS sales document number 

to DSS to enable them to group all inventory.

2/2

1/60

28. 2/PER01/1500 Contact Function 

Code

Code identifying the major duty or responsibility of the 

person or group named

IC Information Contact

DLMS Note: Use to identify the point of contact.

2/2

29. 2/PER03-PER09

/1500

Communication 

Number Qualifiers

This segment will use standard IC configuration for PER 

segment.

30. 2/QTY01/3200 Quantity Qualifier Requirement: Qualifier for Issue Quantity

TO Total

DLMS Note: 1. Use to identify the total quantity that will 

be issued for the items sourced to the CV contract. 

2. This field is only used when the DLA Disposition 

Services ICP is updating the Disposition Category Code to 

DS-Disposal or SL-Sales. This field is required for the 

DLA Disposition Services Field Office to create an 

internal MRO transaction.

2/2

31. 2/QTY01/3200

2/QTY02/3200

Quantity Qualifier

Quantity

Requirement: Qualifier for Disposition Services 

Complete Container Count

OC Order Count

DLMS Note: DLA Disposition Services uses to identify 

the disposition services complete container count. This 

represents the total number of DTIDs in a specified 

disposition services container.

2/2

1/15
Enclosure 3

ADC 412

9 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

32. 2/QTY03/3200 Composite Unit of 

Measure

Open Data Element QTY03 (Unit of Measure) 2/2

33. 2/QTY03-

01/3200

Unit or Basis for 

Measurement Code

Open Data Element QTY03-01/355 and add the following 

note:

Federal Note: Use any code other than ZZ.

DLMS Note: DLMS users see the Unit of Issue and 

Purchase Unit Conversion Table for available codes. 

2/2

34. 2/LM01/3750 Agency Qualifier 

Code 

DF Department of Defense

STAFFING NOTE: RBI indicates that the following LQ 

codes (and other codes that reference for use to ‘spin up 

the MRO’) are needed so that the DLA Disposition 

Services Field Office (using DSS) can create an internal 

MRO for their processing.

This data will not exist in DSS for these items. This data 

is normally provided when the ICP generates an MRO in 

EBS and sends it to the Field Office using DSS. RBI 

Team advises that the 846C will act like the MRO in this 

case since the ICP (EBS) is not truly issuing the item. The 

Field Office (DSS) needs the data in order to create the 

internal MRO so a pick ticket can be created for the item.

DOD MILSTRIP Administrator Comment 

subsequent to the PDC staffing: While it is 

correct that the MRO from the ICP would provide 

any applicable data for the Project Code, Priority 

Designator Code, Advice Code, Supply Condition 

Code, Management Code, and Ownership Code to 

DSS, it is not clear why these data elements are 

needed for the internal MRO transaction applicable 

to Disposition Category DS or SL. Since there are 

no prior requisitions establishing a requirement for 

these data elements to be populated with 

unique/meaningful content, it is not apparent how 

EBS will fill these fields on the 846C or why they 

should be passed transactionally. Refer to ADC 

412 Attachment, paragraph 12, PDC COMMENT 

TABLE, row 11.

2/2

35. 2/LQ01/3760 Code List Qualifier 

Code

78 Project Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3
Enclosure 3

ADC 412

10 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

36. 2/LQ01/3760 Code List Qualifier 

Code 

79 Priority Designator Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3

37. 2/LQ01/3760 Code List Qualifier 

Code 

80 Advice Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3

38. 2/LQ01/3760 Code List Qualifier 

Code 

83 Supply Condition Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3

39. 2/LQ01/3760 Code List Qualifier 

Code 

84 Management Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP (using EBS) is updating the 

Disposition Category Code to DS-Disposal or SL-Sales. 

This field is required for the DLA Disposition Services 

Field Office (using DSS) to create an internal Materiel 

Release Order(MRO) transaction.

2/3

40. 2/LQ01/3760 Code List Qualifier 

Code 

A1 Ownership Code 

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3

41. 2/LQ01/3760 Code List Qualifier 

Code 

AK Distribution

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3
Enclosure 3

ADC 412

11 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

42. 2/LQ01/3760 Code List Qualifier 

Code 

Add new local code Qualifier DMI with DLMS notes:

DMI Demilitarization Integrity Code

DLMS Notes: 1. Authorized DLMS enhancement for use 

by DLA Disposition Services. 

2. At this time a local code DMI is established for use in 

846C, version 4030. A data maintenance action has been 

submitted for establishment of ‘DMI Demilitarization 

Integrity Code’ in a future version.

STAFFING NOTE: DEMIL Integrity Code is used to 

determine/confirm the disposition category of a property. 

It is a code that signifies the status of a currently assigned 

demilitarization (DEMIL) code. DEMIL Integrity Codes 

(IC) are management codes to be used by the DoD 

Components to determine the validity of an items DEMIL 

code as assigned by the Primary Inventory Control 

Activity and verified by the DoD DEMIL Coding 

Management Office (DCMO). 

Code List: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, null

RBI advises this is an existing FLIS code. DRN 0152.

2/3

43. 2/LQ01/3760 Code List Qualifier 

Code 

Disposition Services Container Issued in Full Indicator

Add new local code Qualifier DSI with DLMS notes:

DSI Disposition Services Indicator 

DLMS Notes: 

1. The following Disposition Services Indicator is 

authorized for use in the Disposition Category Update 

transaction: CIF. CIF = Disposition Services Container

Issued in Full. The indicator will be conveyed in LQ02, 

where LQ01 conveys DSI. Refer to ADC 412.

2. At this time a local code DSI is established for use in 

846C, version 4030. A data maintenance action has been 

submitted for establishment of ‘DSI Disposition Services 

Indicator’ in a future version.

2/3
Enclosure 3

ADC 412

12 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

44. 2/LQ01/3760 Code List Qualifier 

Code 

Add new local code Qualifier DCT with DLMS notes:

DCT Disposition Category Code 

DLMS Notes: 1. DLA Disposition Services uses the 

Disposition Category Code to indicate the current method 

of asset disposition assigned to a Disposal Turn In 

Document (DTID). Disposition Category Codes are: DS, 

RJ, RS, RU, and SL. The code value will be conveyed 

in LQ02, where LQ01 conveys DCT. Explanation for 

the codes are as follows:

DS Disposal

RU Reutilization

RJ Reject

RS Research

SL Sales

2. At this time a local code DCT is established for use in 

846C, version 4030. A data maintenance action has been 

submitted for establishment of ‘DCT - Disposition 

Category Code’ in a future version.

2/3

45. 2/LQ01/3760 Code List Qualifier 

Code

Add new local code Qualifier DCS with DLMS notes:

DCS Disposition Sub-Category Code 

DLMS Notes: 1. DLA Disposition Services uses the

Disposition Sub-Category Code to indicate how DLA 

Disposition Services ICP shall process a release order 

based on the sub-category code passed. Disposition SubCategory Codes authorized for use in this transaction 

are: CV and SV. The code value will be conveyed in 

LQ02, where LQ01 conveys DCS. Explanations for the

codes are as follows:

CV Commercial Venture 

SV Scrap Venture 

2. At this time a local code DCS is established for use in 

846C, version 4030. A data maintenance action has been 

submitted for establishment of ‘DCS Disposition SubCategory Code’ in a future version.

2/3
Enclosure 3

ADC 412

13 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

46. 2/LQ01/3760 Code List Qualifier 

Code

Add new local code Qualifier DCR with DLMS notes:

DCR Disposition Category Change Reject Reason 

Code

DLMS Notes: 1. DLA Disposition Services uses to 

identify the Disposition Category Change Reject Reason 

Code. Codes to be published by DRMS Instruction 

(DRMS-I) 4160.14. 

2. At this time a local code DCR is established for use in 

846C, version 4030. A data maintenance action has been 

submitted for establishment of ‘DCS - Disposition 

Category Change Reject Reason Code’ in a future 

version.

2/3

47. 2/LQ01/3760 Code List Qualifier 

Code 

FD Demilitarization Code

DRN 0167

2/3

48. 2/LQ01/3760 Code List Qualifier 

Code 

DE Signal Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS-Disposal or SL-Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3

49. 2/LQ01/3760 Code List Qualifier 

Code 

DF Media and Status Code

DLMS Note: This field is only used when the DLA 

Disposition Services ICP is updating the Disposition 

Category Code to DS Disposal or SL Sales. This field is 

required for the DLA Disposition Services Field Office to 

create an internal MRO transaction.

2/3

50. 2/LS01/3800 Loop Identifier 

Code 

Closing the LS 

LOOP because the

serial number is 

not required in 

846C per DLA 

comment.

Refer to the ADC 

Attachment, 

paragraph 12, PDC 

436 Comments 

Disposition, row 5

The loop ID number given on the transaction set diagram 

is the value for this data element in segments LS and LE

Segment Level Federal Note: Use in each 2/QTY/3200 

loop to prevent a syntax error in the use of the 2/REF/3900 

loop.

Federal Note: Cite REF to indicate the 2/REF/3900 loop.

1/6
Enclosure 3

ADC 412

14 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

51. 2/REF01/3900 Reference 

Identification 

Qualifier 

Closing the REF 

LOOP. The serial 

number is not 

required in 846C 

per DLA 

comment.

Refer to the ADC 

Attachment, 

paragraph 12, PDC 

436 Comments 

Disposition, row 5

SE Serial Number

DLMS Notes: 1. Use to identify the serial number when 

UII is not required. If UII is required in addition to the 

serial number, enter serial number in REF04.

2. This transaction will support item identification based 

upon the unique item identifier (UII) or the serial number, 

and provides flexibility to accommodate tracking by UII or 

serial number.

3. DLA Disposition Services use to identify the serial 

number for Small Arms/Light Weapons (SA/LW).

U3 Unique Supplier Identification Number (USIN) 

DLMS Notes: 1. The UII may not exceed 50 characters 

in accordance with IUID Policy. ANSI data maintenance 

was approved in version 5020. The approved code/name is 

“UII-Department of Defense Unique Item Identifier”.

2. DLA Disposition Services uses to identify the UII for 

SA/LW.

52. 2/REF04-

01/3900

Reference 

Identification 

Qualifier 

See rows 50 & 51 

above.

SE Serial Number 

DLMS Note: 1. Use to identify the serial number when 

UII is entered in REF01 and serial number is also used.

2. DLA Disposition Services use to identify the serial 

number for Small Arms/Light Weapons (SA/LW).

53. 2/LE/4400

2/LE01/4400

Loop Identifier 

Code 

See rows 50 & 51 

above.

The loop ID number given on the transaction set diagram 

is the value for this data element in segments LS and LE

Segment Level Federal Note: Use in each 2/QTY/3200 

loop to terminate any 2/REF/3900 loop iteration

Federal Note: Repeat the content of 2/LS/3800.

1/6

54. 2/N101/4500 Entity Identifier 

Code 

Code identifying an organizational entity, a physical 

location, property or an individual

BT Bill to Party

SB Storage Area

DLMS Note: Use to identify the DLA Disposition Services 

Field Office (depot or storage activity). 

ST Ship To

Z4 Owning Inventory Control Point

DLMS Note: Use to identify the DLA Disposition 

Services ICP.

2/2
Enclosure 3

ADC 412

15 of 15

DS 846C

Data Location

DS 846C Data 

Content Usage Notes Field 

Length

55. 2/N103/4500

2/N104/4300

Identification Code 

Qualifier 

Identification code

Code designating the system/method of code structure 

used for Identification Code (67)

10 DoDAAC

M4 DoD RIC

2/2

2/80

56. 2/N106/4500 Entity Identifier 

Code 

Code identifying an organizational entity, a physical 

location, property or an individual

TO Message To

DLMS Note: Must use in conjunction with 2/N101/4500 

code SB or Z4 to identify that the organization cited in 

N104 is organization the transaction set is being sent to.

2/2

57. SE01 – SE02 SE02 – Transaction 

Set Control Number

Federal Note: Cite the same number as the one cited in 

ST02.