DLMS Data Dictionary

The Authoritative Resource for DLMS X12 Data Elements and Codes

This Data Dictionary is the authoritative reference for all data elements used across Defense Logistics Management Standards (DLMS) Implementation Conventions (ICs). It provides standardized definitions and technical specifications for DLMS and its underlying ANSI ASC X12 data structures.

What This Dictionary Provides:

  • Clear Definitions: Find the official business definition and purpose for every data element used in DLMS transactions.
  • Technical Specifications: Get the exact technical format, length, and structure for each element as it appears in an X12 transaction.
  • DLMS to X12 Mapping: Understand exactly how a DLMS business term maps to a specific X12 segment and element (e.g., "Ship-To Address" maps to N1*ST in the 511R transaction).
  • Authoritative Code Lists: Access the complete and current lists of approved codes and qualifiers used in logistics transactions, such as status codes, discrepancy codes, and unit of issue codes.

Who Should Use This Resource:

  • System Developers & Integrators: To correctly build, map, and test DLMS-compliant applications.
  • Logistics & Supply SMEs: To understand the precise meaning and proper use of data in our business processes.
  • Data Analysts & Managers: To ensure data quality, standardization, and interoperability across systems.

Key Implementation Notes:

  • Relationship to Implementation Conventions (ICs): This Data Dictionary is a reference tool that enhances and supports the DLMS Implementation Conventions (ICs); it does not replace them. For proper implementation, users must consult the detailed guidance and business rules contained within the applicable IC.
  • Governing Standards: All data elements are governed by the Accredited Standards Committee X12 (ASC X12) and the policies within DLM 4000.25, Defense Logistics Management Standards (DLMS). The ASC X12 is the governing source for X12, which is an electronic data interchange (EDI) standard.
Browse records in that    Search     

View ICSorted by ascending REF CODE CODE NAME GENERAL CODE DEFINITION CODE DLMS NOTE
  856S LQ01 A9 Supplemental Data 1. Use to identify supplemental address/data. 2. Future streamlined data; see introductory DLMS note 2c.
  856S LQ01 AJ Utilization Code 1. Use to identify a specialized purpose for which the requisition is submitted. 2. Under legacy MILSTRIP, this is the first position of the document serial number within the document number. 3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 4. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 AK Distribution Code Future streamlined data; see introductory DLMS note 2c.
  856S LQ01 AL Special Requirements Code 1. Must use to identify special handling and priority codes when applicable. Under legacy MILSTRIP, this is caried in the required delivery date field. 2. Authorized DLMS migration enhancement for optional use; see introductory DLMS 2f.
  856S LQ01 BC Transportation Holding Delay Code 1. This is the Shipment Hold Code. 2. Use to identify the reason a shipment unit is not shipped. This includes delays occurring immediately after materiel is picked, packed, marked and made ready for shipment.
  856S LQ01 BD Transportation Priority Code 1. Use to identify the applicable transportation priority when available. 2. Authorized DLMS migration enhancement; see introductory DLMS 2f.
  856S LQ01 DE Signal Code Use to accommodate legacy system requirements. Use only in LRO shipment status to indicate the activity to receive credit and pseudo shipment status to perpetuate the signal code from the materiel release order.
  856S LQ01 DF Media and Status Code
  856S LQ01 FD Demilitarization Code For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter Demilitarization Code per the Generator Communication (GenCom) Standard. DLMS enhancement, see ADC 42.
  856S LQ01 GQ Group Qualifier Code 1. Use to identify the Materiel Management Aggregation Code (MAC) for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. 2. A data maintenance action was approved in version 5010. The approved code/name is "MAC - Material Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN) 23-10, Volumes 1 and 2. 3. For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter MAC per the Generator Communication (GenCom) Standard data element “Additional Data” in the DTID record. DLMS enhancement, see ADC 42.
  856S LQ01 R3 Delivery Rank (Priority) 1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an urgency of need within the maintenance shop and must be delivered within one hour of receipt of the issue request. Value will be X (1 hour issue) when applicable. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 3. A data maintenance action was approved in version 5030. The approved code/name is DPC - Delivery Priority Code. DoD systems will continue to use Qualifier R3 to represent the Delivery Priority/Special Processing Code until such time as a new ADC directs otherwise.
  856S LQ01 COG Cognizance Symbol Use to identify the materiel cognizance symbol (COG) of the end item. Indicate NSL for non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.
  856S LQ01 DSI Disposition Services Indicator Code 1. For Hazardous Material/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter the applicable indicator in the LQ02 to identify type of material sent to DLA Disposition Services. 2. DLA Disposition Services uses the following Disposition Services Indicators in the shipment status transaction: HHMM - Hazardous Material S - Special Services HW - Hazardous Waste 3. A data maintenance action was approved in version 6050. The approved code/name is “DSI - Disposition Services Indicator Code”.
  856S LQ01 IMC Item Management Code Use to identify the Item Management Code (IMC) for integrated material management. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.
  856S LQ01 MCC Material Control Code Use to identify the Material Control Code (MC) for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.
  856S LQ01 SMI Special Material Identification Code 1. Use to identify the Special Material Identification Code (SMIC) for an end item. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter SMIC per the Generator Communication (GenCom) Standard data element “Additional Data” in the DTID record. DLMS enhancement, see ADC 42.
  856S LQ01 T05 Inspection Parameters 1. Use to identify the Quality Inspection Code indicating the level of quality inspection to which the item must be procured and inspected. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  861P ST01 861 Receiving Advice/Acceptance Certificate
  861P BRA03 0 Original Indicates the initial transaction Use regardless of the type of acceptance report, unless a cancelation or Correction.
  861P BRA03 1 Cancelation Future enhancement; not used for initial implementation.
  861P BRA03 CO Corrected Future enhancement; not used for initial implementation.
  861P BRA04 8 Acceptance Certificate Not used at this time; reserved for future enhancement.
  861P BRA04 9 Authorized Representative in Receipt of an Acceptance Alert Use to identify a party in receipt of an acceptance alert Advance Shipment Notice (ASN) for destination acceptance (equates to MILSCAP PKN).
  861P BRA04 A Authorized Representative Not in Receipt of an Acceptance Alert Use to identify a party not in receipt of an acceptance alert Advance Shipment Notice (ASN) for destination acceptance (equates to MILSCAP PKP).
  861P BRA07 24 On-Hold Use to indicate status of materiel received. Use only when full vendor shipment cannot be Accepted/placed in suspended status.
  861P BRA07 80 Reconcile Use to reconcile quantity Accepted when a partial quantity has been Accepted previously in separate transaction; when partial quantity has been Accepted and status of remaining quantity is not identified on this transaction; or when partial quantity has been suspended.
  861P BRA07 WQ Accept Use when full vendor shipment quantity has been Accepted.
  861P REF01 FS Final Sequence Number Use, if applicable, to identify the final shipment suffix Z.
  861P REF01 SI Shipper's Identifying Number for Shipment (SID) WAWF will concatenate the final shipment suffix with the shipment number.
  861P PER01 KC Accepting Official Use to provide name of receipt examiner Use to provide name of receipt examiner. Must also provide telephone number below.
  861P PER03 TE Telephone
  861P PER05 EM Electronic Mail
  861P DTM01 50 Received
  861P DTM01 144 Estimated Acceptance 1. Use in interim reports when LQ01 cites code 10 and LQ02 cites code D. 2 - This is a former MILSCAP functionality not currently used under DLMS; reserved for future enhancement.
  861P DTM01 201 Acceptance Use to indicate the date the materiel was accepted
  861P DTM01 517 Inspected
  861P N101 BK Bank Use to identify the bank that issued the Government Credit Card.
  861P N101 C4 Contract Administration Office Use to identify the DODAAC of the CAO. For MOCAS-administered contracts, identify the DCMR ADP point as a transaction recipient.
  861P N101 CJ Automated Data Processing (ADP) Point 1. Use to indicate routing of transaction. 2. Use to identify the WAWF-RA as the transaction recipient in response to an advance shipment notice.
  861P N101 KK Registering Party 1. Use to identify the Component UIT registry. May be used by a Component when their UIT process requires that a copy of the transaction also be sent to a UIT registry for information purposes. Must be used with 2/N106/130 code ‘PK-Party to Receive Copy’ to identify that this is only an information copy of the transaction, for use with the Component UIT registry. 2. Future enhancement; not used for initial implementation.
  861P N101 KZ Acceptance Location Use to indicate acceptance is at other than origin or destination Use when acceptance is performed at a location other than the ship-to address.
  861P N101 L1 Inspection Location
  861P N101 ST Ship To 1. Use to identify the ship-to address. 2. This will be the transaction originator.
  861P N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations. The first position indicates the Component or other Government element of ownership or sponsorship. The remaining five positions are assigned under established products by the Service point of the participating Component
  861P N103 31 Bank Identification Code Use to indicate the card issuing bank identification number of the bank when code BK is cited in N101. This is the first six positions of the credit card number.
  861P N103 UE Unique Entity Identifier Approved for use in X12 version 8020.
  861P N103 UR Uniform Resource Locator (URL) 1. Use when appropriate to identify the Component UIT registry. 2. Future enhancement; not used for initial implementation.
  861P N103 ZZ Mutually Defined Use to identify WAWF-RA as the transaction recipient. Enter “WAWF” in N104.
  861P N106 FR Message From Use to identify the party originating the transaction set Use to indicate that the organization cited in N104 transmitted the transaction set.
  861P N106 PK Party to Receive Copy 1. Use when appropriate to send an information copy of the transaction to a Component UIT registry. For use with N101 code K. 2. Future enhancement; not used for initial implementation.
Page 93  of  141 First   Previous   89  90  91  92  [93]  94  95  96  97  98  Next   Last