DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

January 4, 2021

MEMORANDUM FOR THE RECORD

SUBJECT: Approved Defense Logistics Enterprise Standards Change (ADC) 1214A,

Addendum to ADC 1214 New DLMS Implementation Convention (IC) 824W 

Disposal Turn-In Document (DTID) and Hazardous Material/Hazardous Waste 

Profile Sheet (HWPS) Validation and Associated Procedures (Supply)

The attached change to Enterprise Business Standards, as outlined in the attachment, is 

approved for implementation. This administrative update replaces ADC 1214 in its entirety.

Addressees may direct questions to Ms. Tonja Carter, e-mail: Tonja.Carter@dla.mil. 

Others must contact their designated PRC representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. 

THOMAS A. DELANEY 

Director, Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD(Logistics)

OUSD(C) 

OUSD(A&S/DPC)
Attachment ADC 1214A

Page 1

ADC 1214A

Addendum to ADC 1214 New DLMS IC 824W Disposal Turn-In 

Document (DTID) and Hazardous Material/Hazardous Waste Profile 

Sheet (HWPS) Validation and Associated Procedures 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Technical POC:

EBSO Supply, Ms. Tonja Carter, e-mail: Tonja.Carter@dla.mil. 

2. REFERENCE:

a. Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1214, 

New DLMS Implementation Convention (IC) 824W Disposal Turn-In Document (DTID) and 

Hazardous Material/Hazardous Waste Profile Sheet (HWPS) Validation and Associated 

Procedures, May 30, 2017.

b. ADC 416, Hazardous Material/Hazardous Waste (HM/HW) Profile Transaction, 

DLMS 996H, in Support of Reutilization Business Integration (RBI), dated October 25, 2011

c. ADC 422, Revises DLMS Implementation Convention 856S, Shipment Status, in 

Support of Reutilization Business Integration (RBI), dated October 6, 2011

d. ADC 1111, Revise Procedures for Intransit Control of Materiel Turned in to DLA 

Disposition Services and Establish Use of the DLMS 527R for a New Disposition Services TurnIn Receipt Acknowledgement (TRA) Transaction, dated August 27, 2014

e. ADC 1131, Phase II Implementation of New DLMS 841W Hazardous 

Material/Hazardous Waste Profile (HWPS) and 856W Hazardous Material/Hazardous Waste 

(HM/HW) Shipment Status Implementation Conventions and Associated Procedures Supporting 

Turn-Ins to DLA Disposition Services, dated November 25, 2015

f. ADC 1371, Cancellation of the DLMS 996H, dated May 13, 2020

g. DLM 4000.25, Defense Logistics Management Standards, Volume 2, dated June 13, 

2012

h. DTR 4500.9-R, Defense Transportation Regulation, Part II, Appendix L

3. APPROVED CHANGE(S): Substantive updates subsequent to staffing of PDC 1214 are 

highlighted in green. Updates related to ADC 1214A are highlighted in blue. 

a. Brief Overview of Change: This administrative update replaces ADC 1214 in its 

entirety and corrects the DoD reject advice codes in the existing diagram, Turn-In Activity 

Cannot Process DLMS 824W Scenario Flow diagram included in Enclosure 1. 

(1) Based on ADC 1214, the only time a DLMS 824W would be sent in reference 

to the DLMS 856W is when the 856W fails DITD validation. The DLMS 824W is not used for 
Attachment ADC 1214A

Page 2

Acceptance of the DLMS 856W, it is only used if the DLMS 856W fails DTID Validation 

deleting box 7 from diagram. 

(2) Additional corrections update the Reject Advice Codes associated with the 

DLMS 824R and replaced by the following:

(a) HZ-HWPS Rejections 

(b) DZ-DTID Rejections 

(3) This change establishes the DLMS 824W Disposal Turn-in Document 

(DTID) and HWPS Validation transaction, which will replace the GenComm Standard Version 

5.0 Log File that the DLA Distribution Standard System (DSS) sends back to the hazardous 

waste generator. The DLMS 824W will identify the waste profile sheet (WPS) and DTID 

numbers that processed along with the reject advice code for data content that is rejected.

(4) This change also revises the DLMS 856W HM/HW Shipment Status to

change the length of the document number to 14 characters, instead of a minimum 14, maximum 

15. The current 856W transaction combines the 1-character suffix code with the 14-character 

document number, which results in a 15-character field. However, under DLMS, the character 

suffix is in a separate data element. This change will update the DLMS 856W to appropriately 

map the suffix code to a distinct position so that the two codes are separate. 

(1) Background: DLA Disposition Services is a worldwide presence within the 

Department of Defense, with disposal specialists in 16 countries, 2 U.S. territories, and 41 states. 

The DLA Disposition Services’ mission is to execute disposition solutions for excess military 

property.

(2) ADC 416 established an interface through DAAS to convey HWPS 

electronically and shipment status information for shipments to DLA Disposition Service Field 

Offices (Reference 3.a.). The interchange accommodated the existing GenComm pipe-delimited 

and XML schema transaction formats. DAAS converted these transactions to a DLMS 996H 

Hazardous Material/Hazardous Waste Profile and DLMS 856S Shipment Status for routing to 

the applicable DLA Disposition Service Field Office. The DLMS 996H had limited 

functionality as it only served to wrap the pipe-delimited/XML formats into an Accredited 

Standards Committee (ASC) X12 Electronic Data Interchange (EDI) transaction. The DLA 

Disposition Services Field Offices had recently migrated to the DLMS compliant DLA 

Distribution Standard System (DSS), and chose the initial implementation for Phase I, in part, to 

minimize the impact to Component systems. ADC 416 documented the intent under Phase II to 

modernize the GenComm standard fully by implementing a more comprehensive set of DLMS 

transactions with the goal of eliminating data redundancies in the legacy file format and 

structuring the transaction to facilitate future enhancements to data content without being limited 

to a flat file format.

(3) ADC 422 documented additional enhancements to the DLMS 856S Shipment 

Status to accommodate the required DTID data content for HM/HW turn-ins (Reference 3.b.).

ADC 422 also advised the Components of DLA Disposition Services intention to sunset the 

GenComm server and indicated Component systems should implement a direct interface with the 
Attachment ADC 1214A

Page 3

Defense Automatic Addressing System (DAAS) (formerly Transaction Services) for the 

HM/HW turn-in shipment status and HWPS processes.

(4) The following ADCs incrementally established new DLMS transactions and 

procedures in support of the GenComm server retirement:

(a) ADC 1111 established the DLMS 527R Disposition Services Turn-in 

Receipt Acknowledgement (TRA) transaction (Reference 3.c).

(b) ADC 1131 documented the creation of the DLMS 841W HWPS to 

include the capability to transmit multiple profile sheets in one transaction. The DLMS 856W 

HM/HW Shipment Status supports documenting the DTID information associated with an 

HM/HW disposal turn-in; its functionality is similar to the DLMS 856S Shipment Status

(MILSTRIP Legacy Documentation Identifier Code (DIC) AS3) (Reference 3.d).

(c) This ADC establishes the DLMS 824W DTID and HWPS 

Acceptance/Rejection and documents new procedures to use the DLMS 824R Reject Advice 

transaction to notify DLA Disposition Services Field Offices when transmitting a DLMS 824W 

to a system that is not DLMS-compliant.

(d) A future PDC will establish a DLMS 870W HM/HW Supply Status 

transaction to allow the DLA Disposition Services Field Offices to report status to the turn-in 

customer.

(5) Effective May 25, 2012, under Hazard Communication 2012, the Department 

of Labor’s Occupational Safety and Health Administration modified its Hazard Communication 

Standard (HCS) to conform to the United Nation’s Globally Harmonized System of 

Classification and Labeling of Chemicals (GHS). Modification to the standard includes a 

specified format for safety data sheets and renaming of the term Material Safety Data Sheets 

(MSDS) to Safety Data Sheet (SDS) to reflect the terminology of the GHS.

(6) Interoperability Issues Caused by a 15-character Document Number

(a) ADC 416 authorized the use of the 996H transaction to allow 

hazardous waste generators to upload a DD Form 1348-1, HWPS, and document number (used 

to indicate the DTID) into the GenComm server. The DLMS 996H contains a minimum 14, 

maximum 15-character document number. The 14/15 field length is based on the GenComm file 

format and equates to a document number (14) + suffix code (1) for a possible total of 15 

characters. A suffix code is authorized in accordance with DLMS procedures (Reference 3.e.); 

however, it is a distinct data element and is not a part of the document number. The document 

number and suffix code can be difficult to distinguish if the suffix code immediately follows the 

document number; in some cases, information systems display the two codes as a 15-character 

block of data. The 14/15 length document number is problematic because it is not compatible 

with the standard 14-character document number format used throughout the rest of the DOD 

supply chain. DLMS procedures define the length of the document number as 14 characters 

(Reference 3.e.).
Attachment ADC 1214A

Page 4

(b) The DLMS 996H was a temporary solution to give the Components 

time to modernize their systems to be able to accommodate a fully DLMS compliant solution 

and to implement a connection with DAAS. ADC 1131 established the DLMS 856W, which 

implements a DLMS-compliant solution for providing shipment status of HM/HW turn-ins. 

However, the DLMS 856W perpetuated the 15-character document number.

(c) This change revises the DLMS 856W to contain a 14-character 

document number. The DLMS 996H will be discontinued in the near future after the eventual 

retirement of the GenComm server and ADC 1131 implementation.

b. Approved Change in Detail:

(1) Corrects details in three of the four diagrams in the original Enclosure 1 from 

ADC 1214: 

(a) HWPS Rejection Scenario

(b) HM/HW DTID Rejection Scenario

(c) Turn-In Activity Cannot Process DLMS 824W Scenario

(d) The Implementation Convention (IC) DLMS note one for the 824W

(2) DLMS 824W DTID and HWPS Validation Transaction: This change 

establishes the DLMS 824W DTID and HWPS Validation transaction. This transaction will 

replace the functionality of the GenComm log file. The DLMS 824W will communicate 

acceptance or rejection of a DLMS 841W based on whether DSS successfully processes the 

HWPS or rejects it due to one or more data elements failing validation. The DLMS 824W will 

also be used to communicate the rejection of a DLMS 856W based on the validation of the DTID 

data elements. The DLMS 527R Turn-in Receipt Acknowledgment (TRA) will communicate 

the receipt of DTID materiel (Reference 3.c.). 

(3) HWPS and DTID Validation Procedures

(a) Acceptance and Rejection of the HWPS

1. Upon receipt of a DLMS 841W, DSS will parse the HWPS 

information and store the individual records by waste profile number. 

2. After processing the DLMS 841W, DSS will transmit a DLMS 

824W containing both accepted and rejected waste profile numbers to the turn-in activity. The 

DLMS 824W will contain a separate Original Transaction Identification (OTI) loop for each 

waste profile number, identifying acceptance or rejection as applicable. 

a. OTI01/Code IA (Item Accept) indicates that DSS has 

accepted the waste profile number. 
Attachment ADC 1214A

Page 5

b. OTI01/Code IR (Item Reject) indicates that DSS has 

rejected the waste profile number. 

c. OTI02/Qualifier WPN indicates that the 824W contains 

a waste profile number. 

3. If one or more HWPS records are invalid, the DLMS 824W will 

contain an HWPS reject code describing the reason for rejection.

4. Turn-in activities, upon receipt of a DLMS 824W with one or 

more rejected waste profile sheets, will review the HWPS, correct the invalid data element(s), 

and submit a new DLMS 841W referencing the original waste profile numbers that rejected. 

5. Upon receipt of the new DLMS 841W from the turn-in activity, 

DSS will transmit a new DLMS 824W to communicate acceptance or rejection of the 

resubmitted waste profile sheets until all invalid data elements have been corrected. 

(b) Rejection of the DTID

1. Upon receipt of a DLMS 856W HM/HW shipment status, DSS 

will parse the HM/HW turn-in information and store the individual records by DTID number. 

2. DSS will convey acceptance of the DTID through the 527R 

Turn-in Receipt Acknowledgment (TRA) transaction as described in Reference 3.c.

3. If the DTID in the DLMS 856W contains one or more invalid 

data elements, DSS will transmit a DLMS 824W containing the rejected DTID numbers to the 

turn-in activity. The DLMS 824W will contain a separate OTI loop for each DTID number 

rejected. 

a. OTI01/Code IR (Item Reject) indicates that DSS has 

rejected the DTID identified in OTI03.

b. OTI02/Qualifier TN indicates the DLMS 824W 

contains a DTID number. 

4. If the DTID is invalid, DSS will transmit a DLMS 824W 

containing a DTID reject code describing the reason for rejection. 

5. Turn-in activities, upon receipt of a DLMS 824W with rejected 

DTIDs, will correct the invalid data element(s) and submit a new DLMS 856W referencing the 

original DTID number rejected.

6. Upon receipt of the new DLMS 856W, DSS will validate the 

resubmitted DTID data elements. DSS will transmit additional DLMS 824W transactions with 

failed DTID numbers and associated reject advice codes to the turn-in activity until all data 

elements are valid. 
Attachment ADC 1214A

Page 6

(4) This change updates MILSTRAP Appendix 2.8, Reject Advice Codes to 

include D-Series and H-series codes for DTID and HWPS rejections respectively and DLMS 

Volume 2, Chapter 16 to include tables documenting DTID and HWPS data element formats 

along with the associated reject codes and definitions. 

(5) DAAS Processing of the DLMS 824W

(a) DAAS will forward the DSS-generated 824W to the DoDAAC

identified in Segment N101/Code HZ (Hazardous Waste Generator).

(b) If the turn-in activity is not capable of processing the DLMS 824W 

due to non-DLMS compliance, DAAS will terminate the transaction and transmit a DLMS 824R 

to DSS with Reject Advice Code HZ for HWPS rejections, and Reject Advice Code DZ for 

DTID rejections. Upon receipt of the DLMS 824R from DAAS, the DLA Disposition Services 

Field Office will communicate with the turn-in activity through alternative methods. 

(6) DLMS 856W HM/HW Shipment Status Update: According to the current 

DAAS translation map for the DLMS 856W, when present, the 15th character of the document 

number represents the suffix code and is mapped to 2/REF04/1500. This DLMS change updates 

the field length of the document number conveyed in 2/REF01/1500 qualifier TN to a minimum 

and maximum of 14 characters (14/14). The W8 qualifier in the 2/REF04-01/1500 conveys the 

suffix code, and the actual 1-character code value will still be mapped to 2/REF04-02/1500. 

c. Revisions to Defense Logistics Manuals:

(1) Update DLM, Volume 2, Chapter 16. See Enclosure 2.

(2) Update DLM Volume 2, Appendix 2.8. See Enclosure 3.

(3) Add new DLMS 824W IC. See Enclosure 4.

d. Approved Transaction Flow:

(1) Component generating systems will transmit the DLMS 841W containing 

multiple waste profile sheets to DAAS, which will pass the transaction to the DLA DSS for 

processing by the field office designated in the transaction. DSS will parse the HWPS 

information into its database and use the DLMS 824W to convey acceptance or rejection of the 

DLMS 841W. 

(2) Component generating systems will transmit a DLMS 856W Shipment Status

to the receiving field office in advance of the physical turn-in of HM/HW. The 856W will 

contain the DTID number associated with the HM/HW shipment. If the shipment contains 

multiple DTIDs, the Component generating systems will transmit a separate 856W for each of 

the DTID. If the associated DTID fails validation, the field office will use the DLMS 824W to 

reject the HM/HW shipment status with the applicable status code. 
Attachment ADC 1214A

Page 7

(3) If the turn-in activity is not fully DLMS capable, DAAS will reject the DLMS 

824W with a DLMS 824R to DSS citing Reject Advice Code DZ for DTID content rejections 

and HZ for HWPS rejections. 

e. Alternatives: With the sunset of the GenComm server and the requirement for systems 

to become DLMS compliant, there are no other alternatives to generate and transmit these 

required data for HM/HW turn-ins to DLA Disposition Services. 

4. REASON FOR CHANGE: This change implements a fully DLMS compliant solution for 

the HWPS and HM/HW shipment status for HM/HW turn-ins to DLA Disposition Services. The 

GenComm server will sunset and all future communications must go through DAAS for proper 

routing to the DLA Disposition Services Field Offices using DSS. The DLMS 996H, developed 

under ADC 416, was a temporary solution to provide the Components time to modernize their 

systems to accommodate a fully DLMS compliant solution and to establish a connection with 

DAAS.

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The DLMS 824W solution implements a comparable capability to what 

was resident in the legacy GenComm version 5.0 feedback file. This will enable HM/HW 

customers to receive reporting status between the Field Office and Turn-In Customers.

b. Disadvantages: This change requires systems changes to DLA’s DSS and 

Component generating systems. 

6. ADDITIONAL COMMENTS TO CONSIDER: This DLMS change is the second of 

several future DLMS changes required to migrate the current GenComm server functionality to 

standard DLMS transactions using DAAS as the routing mechanism.

7. ADDITIONAL FUNCTIONAL REQUIREMENTS: This change will require the 

Components to establish a direct interface with DAAS and bypass the GenComm server. As a 

result, Components should coordinate directly with DLA Disposition Services when they are 

ready to implement this DLMS Change. 

8. ESTIMATED TIMELINE/IMPLEMENTATION TARGET: Staggered implementation 

is authorized. 

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: This change will allows the retirement of the 

GenComm server and will leverage existing transaction routing/translation services at DAAS.

IMPACT:

a. New/Changes Data Elements: This change establishes new reject advice codes to 

notify the submitter of an HWPS or DTID that may have missing or invalid data elements. 

These codes are a subset of the DLM Volume 2, Reject Advice Codes, Appendix 2.8.
Attachment ADC 1214A

Page 8

b. Automated Information Systems (AIS):

(1) DOD Component systems generating HM/HW turn-ins need to accept the 

DLMS 824W. During development, Component systems must pay special attention to the 

business rules identified in this DLMS change to include special mapping conversions between 

legacy GenComm data requirements and X12.

(2) Integrated Data Environment – Global Transportation Network Convergence 

(IGC) should treat the DLMS 856W like a normal shipment status transaction for purposes of in 

transit visibility. 

(3) DSS will require a system change to properly map and process the following 

information within the DLMS 824W DTID and HWPS Validation transaction:

• Sender Internal Control Number (ICN)

• HWPS Number

• HWPS Reject Code

• DTID Number

• DTID Reject Code

• DTID Reject Data Element

• Generator Data

c. Defense Automatic Addressing System (DAAS):

(1) Upon the request of a Component generating system implementing this 

DLMS change, DAAS must negotiate the required agreements and security protocols to enable 

connection to DAAS for purposes of transacting the DLMS 824W. Future DLMS changes will 

document additional transactions sent to generating systems. 

(2) There are no MILSTRIP legacy DIC equivalents for the DLMS 824W. The 

DLMS 824W is similar to the DLMS 824R, but the data content is modified to accommodate 

unique procedures associated with HM/HW requirements.

(3) System changes are required to allow DAAS to determine whether the 

generating system is capable of receiving DLMS data. If the generating system is not DLMScompliant, a DLMS 824R will be created and transmitted to the system sending the DLMS 

824W.

(4) Updates to the DAAS translation mapping table for the DLMS 856W are 

required. See Enclosure 5.

b. Non-DLM Publications: Components should update local procedures as necessary to 

align with this DLMS change. DLA Disposition Services should update internal procedures, 

DOD 4160.21-M Defense Materiel Disposition Manual, and other guidance as applicable.
Attachment ADC 1214A

Page 9

11. PDC 1214 Comment Response Table:

Component Component Responses Received DLMSO Response

Air Force Concur without comment. Noted.

Army No response received. N/A

DLA Concur without comment. Noted.

USMC Concur without comment. Noted.

Navy Concur without comment. Noted.

DAAS Concur without comment. Noted.

USTRANSCOM Concur without comment. Noted.
Enclosure 1, ADC 1214A

Page 1

Enclosure 1

HWPS Acceptance/Rejection and DTID Validation Process Flows

Update HWPS Acceptance, Rejection, and HM/HW DTID Rejection and Turn-in Cannot Process Flow 

Diagrams to reflect the current process as shown below.

3(a). Physical HM/HW Turn-in

DAAS

1. DLMS 841W HWPS

2. DLMS 824W HWPS

Acceptance

3(b). DLMS 856W HM/HW

Shipment Status

4. DLMS 527R Turn -Receipt 

Acknowledgement

Disposi�on Services

Field Office

Turn-In Ac�vity 

(HM/HW Generator )

HWPS Acceptance Scenario

DAAS

1. DLMS 841W HWPS

2. DLMS 824W HWPS

Rejec�on

3. DLMS 841W HWPS

(Corrected)

4. DLMS 824W HWPS Acceptance

Steps 5-7 (Not Shown)

5. Turn-In Ac�vity physically ships HM/HW

6. Turn-In Ac�vity transmits DLMS 856W HM/HW Shipment Status

7. Disposi�on Services Field Office transmits DLMS 527R/TRA for Acceptance

Disposi�on Services

Field Office

Turn-In Ac�vity 

(HM/HW Generator )

HWPS Rejec�on Scenario
Enclosure 1, ADC 1214A

Page 2 

3(a). Physical HM/HW Turn-in

DAAS

1. DLMS 841W HWPS

2. DLMS 824W HWPS

Acceptance

3(b). DLMS 856W HM/HW

Shipment Status

4. DLMS 824W DTID Rejec�on

Steps 5-7 (Not Shown)

5. Turn-In Ac�vity sends a corrected DLMS 856W MW/HW Shipment Status

6. Disposi�on Services Field Office transmits DLMS 527R Turn -in Receipt Acknowledgement (TRA)

Disposi�on Services

Field Office

Turn-In Ac�vity 

HM/HW DTID Rejec�on Scenario
Enclosure 2, ADC 1214A

Page 1

Enclosure 2

Volume 2, Chapter 16 Updates

This change updates the following paragraphs as indicated, showing insertions in red, bold, italics and 

deletions in double strikethrough.

C16.5. DOCUMENTATION REQUIRED FOR SHIPMENTS TO DLA DISPOSITION 

SERVICES 

Intervening paragraphs not shown

C16.5.2.1. Shipment Status. The DLA Disposition Services Field Offices will use the 

DLMS 856W to electronically capture and validate information about inbound HM/HW 

property from a customer that is shipping property to a DLA Disposition Services Field Office 

prior to physical receipt. The information contained within the transaction is used by DLA 

Disposition Services Field Offices to schedule inbound shipments and to match the inbound 

shipment to a Hazardous Waste Profile Sheet (HWPS). In addition to data requirements for 

shipment status of non-hazardous materials, shipment status for HW/HM will add the 

following: DTID number or DTID number and suffix number, HWPS number, disposal 

authority code, disposition services indicator code, item nomenclature, SCC, special materiel 

identification code, materiel management aggregation code, and DEMIL code. This 

additional information will assist the DLA Disposition Services Field Offices with the receipt, 

inspection, and materiel identification of the HM/HW turn-ins. The DLMS 856S/legacy DIC 

AS3 should not be transmitted when the 856W is provided. See DLA Disposition Services 

Instruction 4160.14, “Operating Instructions for Disposition Management,” for appropriate 

code value lists. 

C16.5.2.1.1. HM/HW DTID Validation. DSS will validate the DTID content 

contained in the DLMS 856W to check for missing or invalid data elements. If the DTID 

contains one or more erroneous data elements, DSS will transmit a DLMS 824W 

containing the rejected DTID number and reject advice code to the generating activity. 

Generating activities will resubmit corrected DTID content in a new DLMS 841W citing 

the original DTID number. Table C16.T1. identifies the HM/HW DTID Reject Advice 

Codes.

The following codes are used in defining record formats:

• Mandatory (M)

• Optional (O)

• Alpha (A)

• Numeric (N)

• Alpha/Numeric (A/N)
Enclosure 2, ADC 1214A

Page 2

Table C16.T1. HM/HW DTID Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/

N

Field 

Length 

(Min/Max

)

Reje

ct 

Code

Reason for 

Reject

Reject Definition

M Federal 

Supply Class

N 4 DA Erroneous 

Value if FSC 

is 

Missing/Invali

d

FSC Missing/Invalid. 

Mandatory if DTID is used.

M NIIN/Local 

Stock Number

A/

N

5-9 DB Erroneous 

Value if 

NIIN/LSN is 

Missing/Invali

d

NIIN or LSN Missing/Invalid. 

Mandatory if DTID is used.

M Unit of Issue A 2 DC Erroneous 

Value if Unit 

of Issue is 

Missing/Invali

d

Unit of Issue Missing/Invalid. 

Mandatory if DTID is used.

M Quantity N 1-5 DD Erroneous 

Value if 

Quantity is 

Missing/Invali

d

Quantity Missing/Invalid. 

Mandatory if DTID is used.

M Hazardous 

Waste/Materia

l Code

A 1 DE Erroneous 

Value if 

Hazardous 

Waste/Materia

l Code is 

Missing/Invali

d

Hazardous Waste/Material 

Code Missing, Mandatory if 

DTID is used. “W” for 

hazardous and non-regulated 

and “N” for all other property 

turn-ins to Disposition 

Services.

M Unit Price N 1-5 DF Erroneous 

Value if Unit 

Price is 

Missing/Invali

d

Unit Price Missing/Invalid, 

Mandatory if DTID is used.

M Supply 

Condition 

Code

A 1 DG Erroneous 

Value if 

Supply 

Condition 

Code 

Missing/Invali

d

Supply Condition Code 

Missing/Invalid. Mandatory if 

DTID is used.
Enclosure 2, ADC 1214A

Page 3

Table C16.T1. HM/HW DTID Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/

N

Field 

Length 

(Min/Max

)

Reje

ct 

Code

Reason for 

Reject

Reject Definition

M Demilitarizatio

n Code

A 1 DH Erroneous 

Value if 

Demilitarizati

on Code is 

Missing/Invali

d

Demilitarization Code 

Missing/Invalid, Mandatory if 

DTID is used.

M Contact Name A 4-18 DI Erroneous 

Value if 

Contact Name 

is 

Missing/Invali

d

Contact Name 

Missing/Invalid, Mandatory if 

DTID is used.

M Contact 

Phone

A/

N

4-21 DJ Erroneous 

Value if 

Contact 

Phone is 

Missing/Invali

d

Contact Phone 

Missing/Invalid. Mandatory if 

DTID is used.
Enclosure 2, ADC 1214A

Page 4

Table C16.T1. HM/HW DTID Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/

N

Field 

Length 

(Min/Max

)

Reje

ct 

Code

Reason for 

Reject

Reject Definition

M Total Disposal 

Cost

N 4-5 DK Erroneous 

Value if Total 

Disposal Cost 

is 

Missing/Invali

d

Total Disposal Cost 

Missing/Invalid. Mandatory if 

DTID is used.
Enclosure 2, ADC 1214A

Page 5

Table C16.T1. HM/HW DTID Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/

N

Field 

Length 

(Min/Max

)

Reje

ct 

Code

Reason for 

Reject

Reject Definition

M Fund Code A/

N

2 DL Erroneous 

Value if Fund 

Code is 

Missing/Invali

d

Fund Code Missing/Invalid. 

Mandatory if DTID is used.

M Chemical 

Name

A 2-60 HH Erroneous 

Value if 

Chemical 

Name is 

Missing/Invali

d

Chemical Name is missing or 

invalid.

M Chemical 

Concentration

A/

N

1-30 HI Erroneous 

Value if 

Chemical 

Concentratio

n is 

Missing/Invali

d

Chemical Concentration if 

missing or invalid.
Enclosure 2, ADC 1214A

Page 6

Table C16.T1. HM/HW DTID Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/

N

Field 

Length 

(Min/Max

)

Reje

ct 

Code

Reason for 

Reject

Reject Definition

M Chemical 

Range

A/

N

2-30 HJ Erroneous 

Value if 

Chemical 

Range is 

Missing/Invali

d

Chemical Range is missing or 

invalid.

M Chemical 

Abstract 

(CAS) Number

A/

N

2-11 HK Erroneous 

Value if CAS 

Number is 

Missing/Invali

d

CAS Number is missing or 

invalid.

CONTAINER NUMBER IS MANDATORY BELOW THIS LINE, BUT OTHER FIELDS ARE 

OPTIONAL. MULTIPLE ITERATIONS ARE ALLOWED BASED ON THE NUMBER OF 

CONTAINERS

M Container/Dru

m Number

A/

N

4-15 HO Erroneous 

Value if 

Container 

Number is 

Missing/Invali

d

Container Number Missing. If 

Container is identified, there 

must be a container number. 

If there is no container, the 

code should be blank.

O Storage 

Location

A/

N

0-16 Location item 

is Stored

Location within the building.

O Container 

Weight/Volum

e

N 0-6 The Container 

Weight

The weight of the container.

O Accumulation 

Start Date

N 8 Date 

Accumulation 

Begins

Date (CCYYMMDD)

Intervening text not shown

C16.5.3. Receipt of Hazardous Material/Hazardous Waste and Processing Related 

Hazardous Waste Profile Sheet. Upon receipt by a DLA Disposition Services Field Office of 

the DLMS 841W HM/HW Profile Sheet from DAAS, the supporting system will parse the 

information into its database and store the individual HWPS records by HWPS reference 

number and DTID number. The DLA Disposition Services Field Office will validate 

HWPS records to check for missing or invalid data elements, and DSS will 

subsequently transmit a DLMS 824W to the generating activity to acknowledge 

acceptance or rejection of the HM/HW profile sheets. The DLMS 824W will contain a 

list of HWPS numbers processed successfully and HWPS numbers rejected. If one or 

more HM/HW profile sheets are rejected, the DLMS 824W will contain the rejected 

HWPS number and reject advice code. Generating activities will review the HWPS and
Enclosure 2, ADC 1214A

Page 7

correct the error(s), and then resubmit the corrected HM/HW profile sheet in a new 

DLMS 841W citing the original HWPS number. The DLA Disposition Services Field 

Office will maintain a history of changes for the HWPS. When HM/HW is turned in to the 

DLA Disposition Services field office, the system will search for a DLMS 527D Pre-positioned 

Materiel Receipt (PMR) to facilitate automated check-in. In the absence of a PMR, a search 

for the matching DLMS 856W shipment status will be conducted. Once the matching record 

is found, the system will use the DTID number or DTID number and suffix, and the HWPS 

reference number from the shipment status to pull the matching HWPS for the shipment to be 

receipted. If no electronic records are on file for the DTID number or DTID number and 

suffix, and the HWPS, the DLA Disposition Services Field Office personnel will be manually 

prompted to enter the information into their system based on the hard copy documentation 

accompanying the shipment. Table C16.T2. identifies the HWPS Reject Advice Codes.

The following codes are used in defining record formats:

• Mandatory (M)

• Optional (O)

• Alpha (A)

• Numeric (N)

• Alpha/Numeric (A/N)

Table C16.T2. HWPS Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/N

Field 

Length 

(Min/Max)

Reject 

Code

Reason for 

Reject

Rejection Definition

M Waste Profile 

Number

A/N 5-20 HA Erroneous 

Value if Waste 

Profile Number 

is 

Missing/Invalid

Waste Profile Sheet 

Number is missing or 

invalid. 

M Generator 

Name

A/N 2-30 HB Erroneous 

Value if 

Generator 

Name is 

Missing/Invalid

Generator Name is 

missing or invalid.

M Facility 

Address Line 1

A/N 3-30 HC Erroneous 

Value if 

Facility 

Address is 

Missing/Invalid

Facility Address is 

missing or invalid.

M Facility 

Address Line 3

A/N 2-30 HD Erroneous 

Value if 

Facility City 

and State is 

Missing/Invalid

Facility City and State is 

missing or invalid.
Enclosure 2, ADC 1214A

Page 8

Table C16.T2. HWPS Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/N

Field 

Length 

(Min/Max)

Reject 

Code

Reason for 

Reject

Rejection Definition

M Facility ZIP 

Code Line 4

A/N 5-10 HE Erroneous 

Value if 

Facility Zip 

Code is 

Missing/Invalid

Facility Zip Code is 

missing or invalid.

M Technical 

Contact

A/N 2-30 HF Erroneous 

Value if 

Technical 

Contact is 

Missing/Invalid

Technical Contact is 

missing or invalid.

M Technical 

Phone 

A/N 4-21 HG Erroneous 

Value if 

Technical 

Phone is 

Missing/Invalid

Technical Phone is 

missing or invalid.

DATA BELOW THIS LINE ARE OPTIONAL, BUT IF ONE FIELD IS POPULATED, ALL DATA IS 

REQUIRED. CAN HAVE MULTIPLE ITERATIONS BASED ON CHEMICAL COMPOSITION FOR 

HWPS

M Chemical Name A 2-60 HH Erroneous 

Value if 

Chemical 

Name is 

Missing/Invalid

Chemical Name is 

missing or invalid. 

Mandatory if Chemical 

Concentration, Chemical 

Range, and CAS Number 

are used.

M Chemical 

Concentration

A/N 1-30 HI Erroneous 

Value if 

Chemical 

Concentration 

is 

Missing/Invalid

Chemical Concentration 

is missing or invalid. 

Mandatory if Chemical 

Name, Chemical Range, 

and CAS Number are 

used.

M Chemical 

Range

A/N 2-30 HJ Erroneous 

Value if 

Chemical 

Range is 

Missing/Invalid

Chemical Range is 

missing or invalid. 

Mandatory if Chemical 

Name, Chemical 

Concentration, and CAS 

Number are used.

M Chemical 

Abstract (CAS) 

Number

A/N 2-11 HK Erroneous 

Value if CAS 

Number is 

Missing/Invalid

Chemical Abstract 

Service Number is 

missing or invalid. 

Mandatory if Chemical 

Name, Chemical 

Concentration, and 

Chemical Range are used.
Enclosure 2, ADC 1214A

Page 9

Table C16.T2. HWPS Reject Advice Codes, Reason for Reject, and Definitions

M/O Field Name A, 

N, 

or 

A/N

Field 

Length 

(Min/Max)

Reject 

Code

Reason for 

Reject

Rejection Definition

DATA BELOW THIS LINE ARE NOT REQUIRED, BUT IF ONE FIELD IS POPULATED, ALL 

DATA ARE REQUIRED. CAN HAVE MULTIPLE ITERATIONS BASED ON EPA NUMBER FOR 

HWPS.

M EPA Hazardous 

Waste Number

A/N 4 HL Erroneous 

Value if EPA 

Hazardous 

Waste Number 

is 

Missing/Invalid

EPA Hazardous Waste 

Number is missing or 

invalid. Must be NONE, 

but is mandatory if EPA 

Range and EPA Units are 

used.

M Chemical 

Range

N 2-20 HM Erroneous 

Value if 

Chemical 

Range is 

Missing/Invalid

Chemical Range of 

Concentration missing. 

Mandatory if Waste 

Number and EPA Units 

are used.

M EPA Units A/N 2-5 HN Erroneous 

Value if EPA 

Units is 

Missing/Invalid

EPA Units missing. 

Mandatory if EPA 

Hazardous Waste Number 

or Range are used.

M Container/Drum 

Number

A/N 4-15 HO Erroneous 

Value if 

Container 

Number is 

Missing/Invalid

Container Number 

Missing. If container is 

identified, there must be a 

container number. If 

there is no container, the 

code must be blank.

C16.5.4. DAAS Processing of the DLMS 824W DTID and HWPS Validation 

Transaction. If the turn-in activity is not fully DLMS-compatible and cannot process 

the DLMS 824W, DAAS will transmit a DLMS 824R with Reject Advice Code DZ for 

824W DTID rejection and HZ for 824W HWPS rejection to the DLA Disposition Services 

Field Office. In response to Reject Advice Codes DZ or HZ, the DLA Disposition 

Services Field Office will use alternative methods of communicating with the turn-in 

activity.1

1 Refer to ADC 1214
Enclosure 3, ADC 1214A

Page 1

Enclosure 3

DLM, Volume 2, AP2.8. Appendix 2.8 Updates

Add the D and H Series HM/HW DTID Reject Advice Codes shown in the table below to the existing 

AP2.8 list. 

AP2.8. APPENDIX 2.8

REJECT ADVICE CODES

AP2.8.1. All A B, D and H series reject advice codes not listed in this appendix 

are reserved for future use and are not to be used unless authorized and disseminated 

by the DoD MILSTRAP Administrator. All other series are reserved for intraComponent use.

NUMBER OF CHARACTERS: Two

TYPE OF CODE: Alphabetic

EXPLANATION: Identifies to the originator of a transaction, the reason 

for rejection, and indicates return of the transaction for 

correction and resubmission.2

MILSTRAP RECORD POSITION: 79-80

DLMS SEGMENT/QUALIFIER: LQ Segment, LQ01 Data Element ID 1270

Qualifier “ET – Reject Advice Code”

CODE EXPLANATION

Preceding codes not shown

DA Rejected. FSC Missing/Invalid. 

DB Rejected. NIIN or LSN Missing/Invalid.

DC Rejected. Unit of Issue Missing/Invalid.

DD Rejected. Quantity Missing/Invalid.

DE Rejected. Hazardous Waste/Material Code Missing/Invalid.

DF Rejected. Unit Price Missing/Invalid.

DG Rejected. Supply Condition Code Missing/Invalid.

2 Codes in the A_, and B_, D_, and H_, series not listed above are reserved for future use and are not to be used unless 

authorized and disseminated by the DoD MILSTRAP Administrator. Codes in the C through Z All other series are 

reserved for intra-Component use.
Enclosure 3, ADC 1214A

Page 2

CODE EXPLANATION

DH Rejected. Demil Code Missing/Invalid. 

DI Rejected. Contact Name Missing/Invalid. 

DJ Rejected. Contact Phone Missing/Invalid.

DK Rejected. Chemical Abstract Service Number is Missing/Invalid.

DL Rejected. Fund Code Missing/Invalid. 

DZ Rejected. Turn-in activity cannot process DLMS-formatted 

transactions. DTID rejection must be communicated through 

alternative methods.

HA Rejected. Waste Profile Sheet Invalid or Missing/Invalid. 

HB Rejected. Generator Name Missing/Invalid.

HC Rejected. Facility Address Missing/Invalid.

HD Rejected. Facility City and State Missing/Invalid.

HE Rejected. Facility Zip Code Missing/Invalid.

HF Rejected. Technical Contact Missing/Invalid.

HG Rejected. Technical Phone is Missing/Invalid.

HH Rejected. Chemical Name Missing/Invalid.

HI Rejected. Chemical Concentration is Missing/Invalid.

HJ Rejected. Chemical Range is Missing/Invalid.

HK Rejected. Chemical Abstract Service Number is Missing/Invalid.

HL Rejected. EPA HW Number Missing/Invalid.

HM Rejected. Range of Concentration Missing/Invalid.

HN Rejected. Unit of Issue Incorrect.

HO Rejected. Container Number Missing/Invalid.

HZ Rejected. Turn-in activity cannot process DLMS-formatted 

transactions. HWPS acknowledgment must be communicated through 

alternative methods.
Enclosure 4

New DLMS 824W Implementation Convention

DLMS 824W 

Disposal Turn-In Document and Hazardous 

Material/Hazardous Waste Profile Sheet Validation
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 4 September 14, 2016

824 Application Advice

Functional Group=AG

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Application Advice Transaction Set 

(824) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the ability to 

report the results of an application system's data content edits of transaction sets. The results of editing transaction sets can be reported at the 

functional group and transaction set level, in either coded or free-form format. It is designed to accommodate the business need of reporting the 

acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used in place of a transaction set 

designed as a specific response to another transaction set (e.g., purchase order acknowledgment sent in response to a purchase order).

DLMS Note:

1. This 824W, Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) 

Validation transaction is intended for use by DLA’s Distribution Standard System to provide a notice of the acceptance or rejection of the 

DLMS 841W HM/HW Waste Profile (HWPS) and rejection of DLMS 856W HM/HW Shipment Status transactions.

2. This entire DLMS Implementation Convention (IC) is considered an authorized DLMS enhancement authorized for implementation by 

modernized systems under DLMS migration. This transaction should be adopted during, or subsequent, to modernization when applicable to 

the Component’s business process. Prior coordination with DLMSO is not required.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Logistics Management

Standards Program Office Web site at URL: http://www.dla.mil/j-6/dlmso.

4. This DLMS IC incorporates the Proposed DLMS Change and Approved DLMS Change (ADC) listed. PDC/ADCs are available from the 

Defense Logistics Management Standards Program Office Web site: http://www.dla.mil/j-6/dlmso/elibrary/Changes/processchanges.asp.

- ADC 1214, New DLMS Implementation Convention (IC) 824W, Disposal Turn-In Document (DTID) and Hazardous Material/Hazardous 

Waste Profile Sheet (HWPS) Validation transaction, and Associated Procedures.

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BGN Beginning Segment M 1 Must use

LOOP ID - N1 >1

0300 N1 Name O 1 Used

* 0400 N2 Additional Name Information O 2 Not Used

* 0500 N3 Address Information O 2 Not Used

* 0600 N4 Geographic Location O 1 Not Used

* 0700 REF Reference Identification O 12 Not Used

* 0800 PER Administrative Communications 

Contact

O 3 Not Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - OTI >1 N2/0100L

0100 OTI Original Transaction Identification M 1 N2/0100 Must use

* 0200 REF Reference Identification O 12 N2/0200 Not Used

* 0300 DTM Date/Time Reference O 2 N2/0300 Not Used

* 0400 PER Administrative Communications 

Contact

O 3 N2/0400 Not Used

* 0500 AMT Monetary Amount O >1 N2/0500 Not Used

* 0600 QTY Quantity O >1 N2/0600 Not Used

* 0650 NM1 Individual or Organizational Name O 9 N2/0650 Not Used

* LOOP ID - TED >1

0700 TED Technical Error Description O 1 Used

0800 NTE Note/Special Instruction O 100 Used

0820 RED Related Data O 100 N2/0820 Used

LOOP ID - LM >1 N2/0850L
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 5 September 14, 2016

0850 LM Code Source Information O 1 N2/0850 Used

LOOP ID - LQ 100

0860 LQ Industry Code M 1 Must use

* 0870 RED Related Data O 100 N2/0870 Not Used

0900 SE Transaction Set Trailer M 1 Must use

Notes: 

2/0100L The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this application 

acknowledgment.

2/0100 The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this application 

acknowledgment.

2/0200 The REF segment allows for the provision of secondary reference identification or numbers required to uniquely identify the original 

transaction set. The primary reference identification or number should be provided in elements OTI02-03.

2/0300 The DTM segment allows for the provision of date, time, or date and time information required to uniquely identify the original 

transaction set.

2/0400 The PER segment should be utilized if administrative communications contact information is important to the unique identification of 

the original transaction set.

2/0500 The AMT segment should be utilized if monetary amount information is important to the unique identification of the original 

transaction set.

2/0600 The QTY segment should be utilized if quantity information is important to the unique identification of the original transaction set.

2/0650 The NM1 segment allows for the provision of entity identification information required to uniquely identify the original transaction set.

2/0820 The RED segment may be used to provide data related to the error condition specified in the associated TED01 element.

2/0850L The LM loop is used to identify industry-based or proprietary application error conditions.

2/0850 The LM loop is used to identify industry-based or proprietary application error conditions.

2/0870 The RED segment may be used to provide data related to the error condition specified in the associated LQ02 element.
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 6 September 14, 2016

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Must use

Purpose: To indicate the start of a transaction set and to assign a control number

Semantics: 

1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction 

set definition (e.g., 810 selects the Invoice Transaction Set).

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate 

implementation convention to match the transaction set definition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

 

Description: Code uniquely identifying a 

Transaction Set

M ID 3/3 Must use 1

Code Name

824 Application Advice

ST02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set

DLMS Note: Use to identify a unique 

number assigned by the originator of the 

transaction set. This number may be system 

generated. 

M AN 4/9 Must use 1

ST03 1705 Implementation Convention Reference

 

Description: Reference assigned to identify 

Implementation Convention

DLMS Note: Use to indicate this 

transmission uses the DLMS IC 824W. Enter 

the DLMS IC (e.g., 004030F824W0WA00).

O AN 1/35 Used 1
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 7 September 14, 2016

BGN Beginning Segment Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

User Option (Usage): Must use

Purpose: To indicate the beginning of a transaction set

Syntax Rules: 

1. C0504 - If BGN05 is present, then BGN04 is required.

Semantics: 

1. BGN02 is the transaction set reference number.

2. BGN03 is the transaction set date.

3. BGN04 is the transaction set time.

4. BGN05 is the transaction set time qualifier.

5. BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BGN01 353 Transaction Set Purpose Code

 

Description: Code identifying purpose of 

transaction set

M ID 2/2 Must use 1

Code Name

00 Original

BGN02 127 Reference Identification 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

DLMS Note: Use to identify the unique 

reference number (document number) 

assigned to this DLMS 824W transaction, 

not the reference number (document 

number or waste profile number) identifying 

the transaction that is being rejected. 

M AN 1/50 Must use 1

BGN03 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year

DLMS Note: 1. Use to identify the date this 

824W transaction was originated.

2. DLMS users, this date corresponds to the 

Universal Time Coordinate (UTC). 

M DT 8/8 Must use 1

BGN04 337 Time

 

Description: 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)

DLMS Note: 1. Express the originating 

activity's time of transaction preparation in 

UTC.

2. Express time in a four (HHMM) or sixX TM 4/8 Used 1
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 8 September 14, 2016

position (HHMMSS) format with seconds 

optional. 

BGN05 623 Time Code 

Description: Code identifying the time. In 

accordance with International Standards 

Organization standard 8601, time can be 

specified by a + or - and an indication in 

hours in relation to Universal Time 

Coordinate (UTC) time; since + is a 

restricted character, + and - are substituted 

by P and M in the codes that follow

O ID 2/2 Used 1

Code Name

UT Universal Time Coordinate

BGN07 640 Transaction Type Code

 

Description: Code specifying the type of 

transaction

O ID 2/2 Used 1

Code Name

ZG Report of Approved Work Candidate 

DLMS Note:

Use to identify HM/HW and DTID Content Acceptance.

ZT Report of Rejection or Return of Work Candidate 

DLMS Note:

Use to identify HM/HW and DTID Content Rejection.
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 9 September 14, 2016

N1 Name Pos: 0300 Max: 1

Heading - Optional

Loop: N1 Elements: 3

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual

M ID 2/3 Must use 1

Code Name

FR Message From 

DLMS Note:

Use to identify the DLA Disposition Services Field Office transmitting the DLMS 824W 

transaction.

HZ HM/HW Generator 

DLMS Note:

Use to identify the HM/HW Generator to whom the DLMS 824W transaction is being sent. The 

TO address is the originator of the HWPS or DTID transaction being referenced in 

2/OTIU/0100.

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

Identification Code (67)

X ID 1/2 Used 1

Code Name

10 Department of Defense Activity Address Code (DODAAC)

N104 67 Identification Code

 

Description: Code identifying a party or 

other code

X AN 2/80 Used 1
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 10 September 14, 2016

OTI Original Transaction Identification Pos: 0100 Max: 1

Detail - Mandatory

Loop: OTI Elements: 3

User Option (Usage): Must use

Purpose: To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, 

or accepted-with-change edit result

Syntax Rules: 

1. C0908 - If OTI09 is present, then OTI08 is required.

Semantics: 

1. OTI03 is the primary reference identification or number used to uniquely identify the original transaction set.

2. OTI06 is the group date.

3. OTI07 is the group time.

4. If OTI11 is present, it will contain the version/release under which the original electronic transaction was translated by the receiver.

5. OTI12 is the purpose of the original transaction set, and is used to assist in its unique identification.

6. OTI13 is the type of the original transaction set, and is used to assist in its unique identification.

7. OTI14 is the application type of the original transaction set, and is used to assist in its unique identification.

8. OTI15 is the type of action indicated or requested by the original transaction set, and is used to assist in its unique identification.

9. OTI16 is the action requested by the original transaction set, and is used to assist in its unique identification.

10. OTI17 is the status reason of the original transaction set, and is used to assist in its unique identification.

Comments: 

1. OTI02 contains the qualifier identifying the business transaction from the original business application, and OTI03 will contain the original 

business application identification.

2. If used, OTI04 through OTI08 will contain values from the original electronic functional group generated by the sender.

3. If used, OTI09 through OTI10 will contain values from the original electronic transaction set generated by the sender.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

OTI01 110 Application Acknowledgment Code 

Description: Code indicating the application 

system edit results of the business data

M ID 1/2 Must use 1

Code Name

IA Item Accept 

DLMS Note:

Use to indicate acceptance of the document identified in OTI03.

IR Item Reject 

DLMS Note:

1. Use to indicate rejection of the document identified in OTI03.

2. Must provide at least one Reject Advice Code in 2/LQ/0860.

OTI02 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification

M ID 2/3 Must use 1

Code Name

TN Transaction Reference Number 

DLMS Note:

Use to identify the document number of the rejected HM/HW DTID

WPN Waste Profile Number 

DLMS Note:

1. Use to identify a Waste Profile Number on the rejected HWPS.

2. At this time a local code ‘WPN’ is established for use in the 856W, version 4030. A data 
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 11 September 14, 2016

maintenance action has been submitted for establishment of ‘WPN – Waste Profile Sheet 

Number” in a future version.

OTI03 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier

M AN 1/50 Must use 1
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 12 September 14, 2016

LM Code Source Information Pos: 0850 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use the 2/LM/085 loop to identify coded information maintained in department or agency documentation. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD) 
DLMS Implementation Convention (IC) 824W ADC 1214 DLM 4000.25

Disposal Turn-In Document (DTID) and Hazardous Materiel/Hazardous Waste (HM/HW) Waste Profile Sheet (HWPS) Validation

004030F824W0WP00 13 September 14, 2016

LQ Industry Code Pos: 0860 Max: 1

Detail - Mandatory

Loop: LQ Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

Use to identify rejection advice code(s) as appropriate.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

 

Description: Code identifying a specific 

industry code list

O ID 1/3 Used 1

Code Name

ET Reject Advice Code 

DLMS Note:

Use to identify reason original transaction was rejected.

LQ02 1271 Industry Code

 

Description: Code indicating a code from a 

specific industry code list

X AN 1/30 Used 1
004030F824W0WP00 14 September 14, 2016

SE Transaction Set Trailer Pos: 0900 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending 

(SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SE01 96 Number of Included Segments

 

Description: Total number of segments 

included in a transaction set including ST 

and SE segments

M N0 1/10 Must use 1

SE02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set

DLMS Note: Cite the same number as the 

one cited in ST02.

M AN 4/9 Must use 1
Enclosure 5, ADC 1214A

Page 1

Enclosure 5

DAAS MAPPING OF GENCOMM 5 TO DLMS 841W and 856W

(Last Update: 11/25/2015 12:32 PM)

PURPOSE: The below tables maps generator data for Waste Profile Sheets (WPS) and Disposal TurnIn Documents (DTID) from a flat file based on the GenComm 5.0 standard to the appropriate Defense 

Logistics Management Standard (DLMS) implementation convention (IC).

BACKGROUND: Currently, GenComm transactions can carry multiple WPS, multiple Disposal 

Turn-In Documents (DTID), or multiples of both. In 2011, to facilitate a quick DLMS capability, ADC 

416 created a means to encapsulate GenComm WPS and DTID data into an X12 996 transaction set. 

ADC 422 also had DAAS extract DTID data from GenComm transactions to create a DLMS 856S 

transaction since a DTID mapping to the 856S had already been developed as part of the Reutilization 

Business Initiative (RBI) co-development into DLMS. To develop a more DLMS conformant solution, 

the goal is to define a mapping from GenComm flat file and XML file formats to generate a new 

DLMS IC 841W for WPS data and new 856W for HM/HW DTID data.

APPROACH: Based on the GenComm standard, the mapping will support one to many WPS (841W) 

and/or DTIDs (856W). Each WPS can have one to many records for chemical composition data, and 

one to many records for EPA waste number records. DTIDs may include a container record, an EPA 

waste code record, and/or a state waste code record.

I. Description of columns

A. Generic Data Element: A generic element name that may better clarify the intent of the data to be 

carried in the data element of the file format(s).

B. Min Length: The minimum number of characters/digits for a data element when included in any of 

the file formats. A value of “0” (zero) implies the element is optional. Any value 1 implies the element 

is required. Elements for the end of record indicator of the flat file format do not accept any 

characters/digits and so the minimum length is not applicable (N/A).

C. Max Length: The maximum number of characters/digits for a data element when included in any 

of the file format. A value of “V” identifies elements that do not have a set maximum length (i.e. 

variable length). Elements for the end of record indicator of the flat file format do not accept any 

characters/digits and so the maximum length is not applicable (N/A).

D. GenComm v5.0: Identifies the data element as defined in the “Generator Communications 

Interface Standard 5.0.0, dated April 17, 2008. Mappings should be aware of the following file 

formatting information extracted from the standard:

1) Fields will be delimited by the pipe symbol ("|") in the bar delimited files. However, there 

will not be a trailing pipe ("|").

2) Records will be delimited by the carriage return <CR>, technically stored as the carriage 

return line feed (LF) combination. This will be represented as End of Record Indicator in the record 

formats.
Enclosure 5, ADC 1214A

Page 2

3) At the end of any record there are three options:

a) Continue with the next record.

b) Terminate the section or subsection with its trailer and start a new section or 

subsection.

c) Terminate the section or subsection with its trailer and quit (End of file).

The flat file format includes explicit elements to indicate in the data file where record loops begin and 

end. Since looping can be inferred in the XML and EDI data files based on their defined structures, 

these header and trailer record indicators are unique to the flat file.

E. GenComm XSD: The XML schema follows from the GenComm v.5.0 flat file format, sans the 

header and trailer record indicators of the flat file format. The full element hierarchy is provided to 

ensure there is no confusion between instances of the same element in different parts of the schema.

F. DLMS: This column identifies the appropriate mapping to convey the data in the DLMS 841W or 

856W. Mappings include qualifiers in other segment positions which provide the context needed to 

define the GenComm data content.

1) Mapping Nomenclature. The mapping column uses the following nomenclature to identify 

where in the 841W and 856W the data from the GenComm transaction is recommended to be mapped:

<Transaction Section>/<Segment ID><Segment Position>/<Transaction Position>

Transaction Section: X12 transaction sets can be divided into major sections; 1 = Header Section, 2 = 

Detail Section, and 3 = Summary Section. Header sections tend to identify the intent of the transaction 

and information common to rest of the detail data. Detail sections are the meat of the transaction, and 

often support many iterations for multiple records of the same type. Summary section are only used 

when the transaction would include tallies to sum up the details. The 841 does not have a summary 

section.

Segment ID: This is a two to three character identifier of a data segment that is part of the section of 

the transaction.

Transaction Position: This is a sequential number identifying where within the transaction section the 

segment is relative to other segments.

Segment Position: This is a sequential number identifying the position of an element within the 

segment.

2) Mapping Color Coding. Many mappings require the use of codes to qualify the data. Where 

the version 4030 of the X12 standard lacked an appropriate code value to use the map has included a 

recommended mapping that fit into one of three categories.

Migration Codes: When a good code is available in a more recent version of the X12 standard, it is 

possible to program the translator to recognize this code as if it were part of the 4030 version. The 

Defense Logistics Manual (DLM) 4000.25, Volume 1 defines the use of such codes as migration codes 

and explains the circumstances for using migration codes. There are four recommended migration 

codes in the mapping highlighted in green.
Enclosure 5, ADC 1214A

Page 3

Local Codes: When there is no code available (even in current X12 standards) then a local code is 

recommended to be programmed as a valid code. When local codes are approved in DLMS changes, 

DLMSO submits the codes to X12 so that they will be included in a future release of the standard and 

become migration codes. There are five recommended local codes in the mapping highlighted in 

yellow.

Agency Codes: Some segments support the ability for identifying codes maintained outside the X12 

standard. The mapping recommends a number of elements be qualified using codes managed by DLA 

Distribution Services. The suggested codes are highlighted in blue below.

G. Notes: Additional mapping and processing information for the element.

II. GenComm to DLMS 856W Mapping
Enclosure 5, ADC 1214A

Page 4

# Generic Data 

Elements

A,N 

or 

A/N

Min/

Max

GenComm v5.0 GenComm

XSD

856W Notes

1. Transaction Set 

Identifier

N 3/3 1/ST01/100 = 856

2. Transaction Set 

Control Number

A/N 4/9 1/ST02/100={Serial 

Number}

3. Implementation 

Convention 

Reference

A/N 1/35 1/ST03/100 = {DLMS 

IC

Version Number}

Sample data: 

004030F856W0 

WP00

4. Transaction Set 

Purpose Code

A/N 2/2 1/BSN01/0200 = 00

Or

1/BSN01/0200 = 77

5. Shipment 

Identification

A/N 2/30 1/BSN02/0200 = ZZ

6. Generator’s File 

Transfer 

DoDAAC

A/N 6/6 DoDAAC DRMO_FILE_G

EN / 

GENCOMM_DO

DA AC

2/HL01/0100 =

2/HL03/0100 = V

2/N101/2200 = HZ

2/N103/2200 = 10

2/N104/2200 = 

{Generator’s DoDAAC}

2/N106/2200 = FR

7. Transaction 

Date

N 7/7 Date DRMO_FILE_G

EN / DATE

1/BSN03/0200 = 

{Transaction Date}

DAAS will need 

to convert 

CCYYJJJ in flat 

file to X12 

standard format 

CCYYMMDD; all 

DLMS IC 

times/dates are 

in UTC.

8. Transaction 

Time

N 4/4 Time DRMO_FILE_G

EN / TIME

1/BSN04/0200 = 

{Transaction Time}

Express time in 

HHMM; all 

DLMS IC 

times/dates are 

in UTC.

9. Transaction 

Type Code

A/N 2/2 1/BSN06/0200 = AZ
Enclosure 5, ADC 1214A

Page 5

10. Transaction File 

Format

A/N 1/5 DRMO_FILE_G

EN / 

GENCOMM_FIL

E_F

2/HL01/0100 = 2

2/HL03/0100 = W

11. DLA Disposition 

Services Filed 

Office RIC

3/4 DRMO RIC DRMO_FILE_G

EN / 

DRMO_RIC

2/HL01/0100 = 1

2/HL03/0100 = V

2/N101/2200 = ZD

2/N103/2200 = M4

2/N104/2200 = {Site 

ID}

2/N106/2200 = TO

Convert DLA 

Disposition 

Services Filed 

Office RIC + 

Suffix to 

Applicable DSS 

Site ID per latest 

version of cross 

reference 

included as 

Enclosure (4) of 

ADC 416.

Recommend 

DSS be 

identified as the 

source, and will 

responsible for 

notifying DAAS 

of any updates 

to the table.

12. Generator’s 

Software 

Release Version 

Number

1/50 Form Version DRMO_FILE_G

EN / 

APPLICATION_

VER SION

2/HL01/0100 = 2

2/HL03/0100 = W

1/REF01/1500 = V0

1/REF02/1500 = 

{Generator’s Software 

Version Number}

X12 restricts this 

data field to a 

maximum of 50 

characters.

DAAS will 

truncate if 

necessary.

13. Transaction 

Header Record 

End of Record 

Indicator

End of record 

indicator

See Section II above for mapping of WPS records into DLMS 841W

14. DTID Section 

Header

12/12 DTID Section 

Header

2/HL01/0100 = 2

2/HL03/0100 = W

A literal of

"beg_dtid_sect" 

Identifies the 

start of a DTID 

loop for the flat 

file format.

Each DTID 

record triggers a 

new 856W 

transaction with 

identical 

mapping of the 

GenComm 

Header Record 

Since there is 

only one DTID 
Enclosure 5, ADC 1214A

Page 6

per 856W, 

2/HL03/0100

(Hierarchical ID) 

will always be 

“2” for the DTID 

record. DTIDs 

indicate they 

are child 

records of the 

HL loop which 

identifies the 

receiving DLA 

Disposition 

Services Field 

Office (i.e. “1”).

15. DTID Section 

Header End of 

Record Indicator

End of Record 

Indicator

16. Federal Supply 

Class

4/4 Federal Supply 

Class

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / FSC

2/LIN02/0200 = FT

2/LIN03/0200 = 

{Federal Supply Class}

17. NIIN/Local Stock 

Number

9/9 NIIN/Local Stock 

Number

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / NIIN

2/LIN04/0200 = FS

2/LIN05/0200 = 

{FSC+NIIN}

or

2/LIN04/0200 = NN

2/LIN05/0200 = {NIIN}

or

2/LIN04/0200 = SW

2/LIN05/0200 = 

{Local Stock 

Number}

Or

2/LIN04/0200 = ZZ

2/LIN05/0200 = 

{Mutually Defined}

If the FSC field 

contains a valid 

four character 

value and the 

first position of 

the NIIN value 

equals “0”, then 

LIN04=FS, else 

if first position 

equals ‘0”, then 

LIN04=NN, else 

if first two 

positions equal 

“DS”, then 

LIN04=SW,

else, LIN04=ZZ 

to indicate that 

the value is not 

recognized as 

either a valid 

NIIN or 

Disposition 

Services LSN.

NOTE: “NN” is 

not valid in X12 

version 4030; it 

is an authorized 

X12 migration 

code.

18. Additional Data 0/2 Additional Data DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

2/LM01/3400 = DF

2/LQ01/3500 = GQ

2/LQ02/3500 = 

{Additional Data} Or

2/LM01/3400 = DF

Use GQ if Air 

Force. Use SMI 

if Navy.
Enclosure 5, ADC 1214A

Page 7

ADDITIONAL_D

ATA

2/LQ01/3500 = SMI

2/LQ02/3500 = 

{Additional Data}

19. Document 

Number

14/15 Document 

Number

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

PMR_DTID_N

O

2/REF01/1500 = TN

2/REF02/1500 = 

{Document 

Number}

2/REF04-01/1500 = 

W8

2/REF04-02/1500 = 

{Document Number 

Suffix}

This is the 

DTID. When 

present, the 

15th

character (a 

suffix) is 

mapped to 

2/REF04-

02/1500.

20. Suffix Code 1/1 Suffix Code 2/REF04-01/1500 = 

W8

2/REF04-02/1500 = 

Suffix

Use to 

identify the 

suffix 

code, if 

applicable, 

associate 

to the 

document 

number 

(REF01=TN

).

21. Unit of Issue 2/2 Unit of Issue DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_R

EC / ITM_UI

2/SN103/0300 = {UoM} Convert to valid 

X12 codes per 

unit of issue 

conversion 

table.

22. Issued Quantity 1/5 Quantity DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / PMR_QTY

2/SN102/0300 = 

{Quantity}

Express as a 

whole number 

with no 

decimals.

23. Disposal 

Authority Code

0/1 Disposal 

Authority Cd

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

DSPSL_AUTH_

CD

2/LQ01/3500 = 88

2/LQ02/3500 = 

{Disposal Authority 

Code}

Loop segment 

2/LM01/3400 =

DF if not already 

opened for 

another LQ 

mapped 

element.

24. Hazardous 

Waste/Material 

Code

1/1 Hazardous 

Waste/Mat Code

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

DTID_HM_HW

_CD

2/LQ01/3500 = DSI

2/LQ02/3500 = 

{Disposition Services 

Indicator}

Loop segment 

2/LM01/3400 =

DF if not already 

opened for 

another LQ 

mapped 

element.

Map legacy field 

value to new 

DSI code 

values as 

follows: M=HM

(Hazardous 

Material), 

W=HW

(Hazardous 
Enclosure 5, ADC 1214A

Page 8

Waste), N=US 

(Useable), 

S=SC (Scrap), 

and P=SS 

(Special 

Services).

Refer to ADC 

422 for 

establishment of 

HM/HW DSI 

codes. NOTE: 

“DSI” is not valid 

in X12 version 

4030; it is an 

authorized X12 

migration code;.

25. Issue Unit Price 1/8 Unit Price DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / ITM_UP

2/REF01/1500 = PA

2/REF02/1500 = {Unit 

Price}

26. Item 

Nomenclature

A/N 2/60 Item 

Nomenclature

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

PMR_ITM_NAM

E

2/LIN06/0200 = CN

2/LIN07/0200 = {Item

Nomenclature}

Use with LIN04 

codes SW or ZZ 

when no NIIN is 

available.

27. Supply 

Condition Code

1/1 Supply 

Condition Code

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

SPLY_COND_

CD

2/LQ01/3500 = 83

2/LQ02/3500 = 

{Supply Condition 

Code}

Loop segment 

2/LM01/3400 =

DF if the not 

already opened 

for another LQ 

mapped 

element.

28. Demilitarization 

Code

1/1 Demil Code DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

ITM_DEMIL_C

D

2/LQ01/3500 = FD

2/LQ02/3500 = 

{Demilitarization 

Code}

Loop segment 

2/LM01/3400 =

DF if the not 

already opened 

for another LQ 

mapped 

element.

29. Accumulation 

Start Date

0/7 Accumulation 

Start Date

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_R

EC / 

ACCUM_STAR

T_D T

2/DTM01/2000 = 051

2/DTM02/2000 = 

{Accumulation Start 

Date}

DAAS will need 

to convert Julian 

date 

(YYYYDDD) to 

CCYYMMDD.

30. Waste Profile 

Sheet Number

A/N 5/20 Waste Profile 

Sheet No

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

WST_PRFL_NO

2/REF01/1500 = WPN

2/REF02/1500 = 

{Waste Profile 

Sheet Number}

WPN is not a 

valid X12 Code 

– See note in 

the 824 IC, 

above.
Enclosure 5, ADC 1214A

Page 9

31. MSDS Number 0/15 MSDS

Number

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / MSDS_NO

2/REF01/1500 = MS

2/REF02/1500 = 

{MSDS Number}

32. Receipt Manifest 

Number

A/N 0/17 Receipt Manifest 

Number

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

REC_MNFST_N

O

2/REF01/1500 = MDN

2/REF02/1500 

= {Receipt 

Manifest 

Number}

33. Type of 

Container

A/N 0/60 Type of 

Container

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

CNTNR_DES

CR

2/PKG01/1000 = F

2/PKG02/1000 = CB

2/PKG05/1000 = {Type 

of Container}

This is a free 

form field that 

includes a 

narrative of the 

container type 

and its volume 

(e.g., 55 gallon 

drum)

34. Disposal Total 

Weight/Volume

N 0/6 Total Wt/Vol DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

TOT_WT_OR_V

OL

2/MEA01/0800 = WA

2/MEA02/0800 = VWT

2/MEA03/0800 = {Total 

Weight/Volume}

35. Disposal Total 

Weight/Volume 

Unit

0/1 Total Wt/Vol 

Code

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

WT_OR_VOL_C

D

2/MEA04/0800 = 

{UoM}

Convert to X12 

UoM values 

(GENCOMM > 

X12):

P > LB 

T > NS; 

G > GA; 

Y > CY; 

K > KG; 

M > MP; 

L > LT; 

C > CR

36. Organization 

Code

0/6 Org Code DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

ORG_CD

2/N101/2200 = PW

2/N102/2200 = 

{Organization 

Code}

This represents 

the shop (e.g., 

motor pool, 

paint shop) that 

generated the 

waste for turnin.

37. Building 0/6 Building DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

STG_LOC_CD

2/N301/2200 = 

{Building}

Use with N101 = 

PW. This 

represents the 

Receipt in Place 

building number 

of the Pickup 

DoDAAC.

38. Type Operation A/N 0/60 Type Operation DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / TYPOP

2/N201/2200 = {Type 

Operation}

Use with N101 = 

PW

3 position code 

or equivalent 

narrative.
Enclosure 5, ADC 1214A

Page 10

Source is 

RCRA BiAnnual Report 

(US EPA 

Instruction 

3700.13).

39. Contact Name 4/18 Contact Name DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / POC

2/PER01/1510 = IC

2/PER02/1510 = 

{Contact Name}

40. Contact Phone 4/21 Contact Phone DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

POC_TFONE

2/PER03/1510 = TE

2/PER04/1510 = 

{Contact Phone}

41. Waste 

Description 

Line 1

0/60 Waste 

Description line 

1

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

HAZ_DESCR_1

2/PID01/0700 = X

2/PID03/0700 = DL

2/PID04/0700 = WDL1

2/PID05/070

0 = {Waste 

Description 

Line 1}

42. Waste 

Description 

Line 2

0/60 Waste 

Description line 

2

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

HAZ_DESCR_2

2/PID01/0700 = X

2/PID03/0700 = DL

2/PID04/0700 = WDL2

2/PID05/070

0 = {Waste 

Description 

Line 1}

43. Waste 

Description 

Line 3

0/60 Waste 

Description line 

3

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

HAZ_DESCR_3

2/PID01/0700 = X

2/PID03/0700 = DL

2/PID04/0700 = WDL3

2/PID05/070

0 = {Waste 

Description 

Line 1}

44. Waste 

Description 

Line 4

0/60 Waste 

Description line 

4

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_RE

C / 

HAZ_DESCR_4

2/PID01/0700 = X

2/PID03/0700 = DL

2/PID04/0700 = WDL4

2/PID05/070

0 = {Waste 

Description 

Line 1}

45. Contract 

Number

A/N 0/13 Contract 

Number

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_R

EC / 

CONTR_NO

2/REF01/1500 = CT

2/REF02/1500 = 

{Contract Number}

46. HIN 6/6 HIN DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_R

EC / HIN

2/REF01/1500 = C7

2/REF02/1500 = 

{CLIN/HIN}
Enclosure 5, ADC 1214A

Page 11

47. Total Disposal 

Cost

N2 4/8 Total Disposal 

Cost

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

TOTAL_DISP

_COS T

2/SAC01/3200 = C

2/SAC03/3200 = DL

2/SAC04/3200 = 

TDC

2/SAC05/3200 = 

{Total Disposal Cost}

In X12, this is a 

datatype N2, 

which means 

last two 

positions of the 

value are 

understood to 

be cents.

48. Fund Code 2/2 Fund Code DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / FD_CD

2/REF01/1500 = FU

2/REF02/1500 = {Fund 

Code}

49. Bill to DoDAAC 0/6 Bill to DoDAAC DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

BILL_TO_DODA

AC

2/N101/2200 = BT

2/N103/2200 = 10

2/N104/2200 = {Bill to 

DoDAAC}

50. Pickup DoDAAC 0/6 Pickup DoDAAC DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

PICKUP_DODA

AC

2/N103/2200 = 10

2/N104/2200 = {Pickup 

DoDAAC}

Use with N101 = 

PW

51. Number of 

Containers

0/4 Number of 

Containers

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

NUM_CNTRS

2/MEA01/0800 = CT

2/MEA03/0800 = 

{Number of 

Containers}

52. Media and 

Status Code

1/1 2/LQ01/3500 = DF

2/LQ02/3500 = 0

Loop segment 

2/LM01/3400=”

DF” if not 

already opened 

for another LQ 

mapped 

element.

53. DTID Record 

End of Record 

Indicator

End of Record 

Indicator

54. DTID Container 

Subsection 

Header

13/13 Container 

Subsection 

Header

2/HL01/0100 = 

{Hierarchical ID} 

2/HL02/0100 = 2

2/HL03/0100 = CN

A literal of 

"beg_cont_sect"

. Identifies the 

start of a DTID 

container record 

loop within a 

DTID record 

loop for the flat 

file format.

Since there is 

only one DTID 

per 856W, when 

there are DTID 
Enclosure 5, ADC 1214A

Page 12

Container 

Subsection 

records each 

will be mapped 

to a child HL 

loop pointing to 

the parent DTID 

HL loop. (i.e.

HL02 = “2”).

55. DTID Container 

Subsection 

Header End of 

Record 

Indicator

End of Record 

Indicator

56. Document 

Number

14/

15

Document 

Number

DRMO_FILE_

GEN / 

DTID_SECT / 

DTID_SECT_

REC / 

CONT_SECT / 

CONT_ROW / 

PMR_DTID_N

O

This is the DTID 

used by 

GenComm files 

to match DTID 

subsections to 

the parent DTID 

record. The 

hierarchical 

nesting of the 

records in the 

856W negates 

the need to 

repeat the entry 

in this HL loop 

and risk a 

mismatch error 

being sent to the 

receiving 

application; 

however, DAAS 

will confirm the 

DTID of the 

DTID Container 

Subsection 

matches the 

DTID of the 

parent DTID 

Section (See 

row #19 above).

57. Container 

Number

A/N 1/15 Container 

Number

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

CONT_SECT / 

CONT_ROW / 

CNTNR_NO

2/REF01/1500 = 98

2/REF02/1500 = 

{Container Number}

58. Storage 

Location Code

0/16 Storage 

Location Code

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

CONT_SECT / 

CONT_ROW / 

CNTNR_STG_L

2/REF01/1500 = M1

2/REF02/1500 

= {Storage 

Location 

Code}
Enclosure 5, ADC 1214A

Page 13

OC

_CD

59. Container 

Weight/Volume

0/6 Container 

WT/VOL

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

CONT_SECT / 

CONT_ROW / 

CNTNR_WT_O

R_V OL

2/MEA01/0800 = WT

2/MEA02/0800 = VWT

2/MEA03/0800 = 

{Container 

Weight/Volume}

60. Accumulation 

Start Date

0/7 Accumulation 

Start Date

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

CONT_SECT / 

CONT_ROW / 

CNTNR_ACUM

_ST ART_DT

2/DTM01/2000 = 051

2/DTM02/2000 = 

{Accumulation Start 

Date}

DAAS will need 

to convert Julian 

date 

(YYYYDDD) to 

CCYYMMDD.

61. DTID Container 

Record End of 

Record 

Indicator

End of Record 

Indicator

62. DTID 

Container 

Subsection 

Trailer

13/13 Container 

Subsection 

Trailer

A literal of 

"end_cont_sect"

. Identifies the 

end of a DTID 

container record 

loop within a 

DTID record 

loop for the flat 

file format.

63. DTID Container 

Subsection 

Trailer End of 

Record 

Indicator

End of Record 

Indicator

64. DTID EPA 

Waste Code 

Subsection 

Header

16/16 EPA Waste 

Code 

Subsection 

Header

2/HL01/0100 = 

{Hierarchical ID} 

2/HL02/0100 = 2

2/HL03/0100 = HE

A literal of 

"beg_dtidepa_se

ct ". Identifies 

the start of a 

DTID EPA 

waste code 

record loop 

within a DTID 

record loop for 

the flat file 

format.

Since there is 

only one DTID 

per 856W, when 

there are DTID 

EPA Waste 
Enclosure 5, ADC 1214A

Page 14

Code 

Subsection 

records each 

will be mapped 

to a child HL 

loop pointing to 

the parent DTID 

HL loop. (i.e.

HL02 = “2”).

65. DTID EPA 

Waste Code 

Subsection 

Header End of 

Record 

Indicator

End of Record 

Indicator

66.

Document 

Number

14/15 Document 

Number

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

DTIDEPA_SEC

T / 

DTIDEPA_ROW 

/ 

PMR_DTID_NO

This is the DTID 

used by 

GenComm files 

to match DTID 

subsections to 

the parent DTID 

record. The 

hierarchical 

nesting of the 

records in the 

856W negates 

the need to 

repeat the entry 

in this HL loop 

and risk a 

mismatch error 

being sent to the 

receiving 

application; 

however, DAAS 

will confirm the 

DTID of the 

DTID Container 

Subsection 

matches the 

DTID of the 

parent DTID 

Section (See 

row #20 above).

67. DTID EPA 

Waste Codes

4/4 DTID EPA 

Waste Codes

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_RE

C / 

DTIDEPA_SEC

T / 

DTIDEPA_ROW 

/ EPA_CD

2/REF01/1500 = CAL

2/REF02/1500 = {DTID 

EPA

Waste Codes}

69. DTID EPA 

Waste Code 

Subsection 

Trailer

16/16 EPA Waste 

Code 

Subsection 

Trailer

A literal of 

"end_dtidepa_se

ct ". Identifies 

the end of a 

DTID EPA 

waste code 
Enclosure 5, ADC 1214A

Page 15

record loop 

within a DTID 

record loop for 

the flat file 

format.

70. DTID EPA 

Waste Code 

Subsection 

Trailer End of 

Record 

Indicator

End of Record 

Indicator

71. DTID State 

Waste Code 

Subsection 

Header

16/16 State Waste 

Code 

Subsection 

Header

2/HL01/0100 = 

{Hierarchical ID} 

2/HL02/0100 = 2

2/HL03/0100 = ST

A literal of 

"beg_dtidsta_se

ct ". Identifies 

the start of a 

DTID state 

waste code 

record loop 

within a DTID 

record loop for 

the flat file 

format.

Since there is 

only one DTID 

per 856W, when 

there are DTID 

State Waste 

Code 

Subsection 

records each 

will be mapped 

to a child HL 

loop pointing to 

the parent DTID 

HL loop. (i.e.

HL02 = “2”).

72. DTID State 

Waste Code 

Subsection 

Header End of 

Record 

Indicator

End of Record 

Indicator

73. Document 

Number

14/15 Document 

Number

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

DTIDSTA_SEC

T / 

DTIDSTA_ROW 

/ 

PMR_DTID_NO

This is the DTID 

used by 

GenComm files 

to match DTID 

subsections to 

the parent DTID 

record. The 

hierarchical 

nesting of the 

records in the 

856W negates 

the need to 

repeat the entry 

in this HL loop 

and risk a 

mismatch error 
Enclosure 5, ADC 1214A

Page 16

being sent to the 

receiving 

application; 

however, DAAS 

will confirm the 

DTID of the 

DTID Container 

Subsection 

matches the 

DTID of the 

parent DTID 

Section (See 

row #20 above).

74. DTID State 

Waste Codes

4/10 DTID State 

Waste Codes

DRMO_FILE_G

EN / 

DTID_SECT / 

DTID_SECT_R

EC / 

DTIDSTA_SEC

T / 

DTIDSTA_ROW 

/ STATE_NR

2/REF01/1500 = CAN

2/REF02/1500 = {DTID 

State

Waste Codes}

75. DTID State 

Waste Code 

Record End of 

Record 

Indicator

End of Record 

Indicator

76. DTID State 

Waste Code 

Subsection 

Trailer

16/16 State Waste 

Code 

Subsection 

Trailer

A literal of 

"end_dtidsta_se

ct ". Identifies 

the end of a 

DTID state 

waste code 

record loop 

within a DTID 

record loop for 

the flat file 

format.

77. DTID State 

Waste Code 

Subsection 

Trailer End of 

Record 

Indicator

End of Record 

Indicator

78. DTID Section 

Trailer

13/

13

DTID Section 

Trailer

A literal of 

"end_dtid_sect

". Identifies the 

end of a DTID 

record loop for 

the flat file 

format.

79. DTID Section 

Trailer End of 

Record 

Indicator

End of Record 

Indicator
Enclosure 5, ADC 1214A

Page 17

80. Transaction 

Included 

Segment Count

1/10 3/SE01/0200={# of 

segments}

81. Transaction 

Control Trailer

4/9 3/SE02/0200={serial 

number}