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).

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 X12 CODE NAME GENERAL CODE DEFINITION CODE DLMS NOTE
  945A N907-03 W1 Disposal Turn-In Document Number Transaction number under which material was shipped to a DLA Disposition Services Field Office 1. Use to identify the disposal turn-in document (DTID) number when provided as a secondary reference number. The DTID Number is a unique number to identify property turned into a DLA Disposition Service Field Office. 2. Use in conjunction with the controlling document number for the transaction (N901 Code TN). When there is no Suffix Code associated with the controlling Document Number, enter the correlating DTID number in the N907-02. If there is a Suffix Code, enter the DTID in the N907-04. Refer to ADC 466. 3. Authorized for intra-DLA use between DLA Disposition Services Field Offices and DLA Disposition Services. DLMS enhancement.
  945A N907-04
  945A N907-05 GL Geographic Destination Zone Number Use with N901 code 4C to indicate the USPS zip code for the carrier address. Use the 9 digit zip code when available.
  945A N907-06
  945A G6201 09 Process Date Use to indicate the date on which a transaction is processed by the relevant activity (either initiating or receiving) Use with the transaction history to identify the date on which the materiel release advice was processed by the initiating activity.
  945A G6201 11 Shipped on This Date Use to identify date shipped Use in materiel release confirmation, historical materiel release confirmation, disposal release confirmation, and historical disposal release confirmation transactions to identify date materiel was shipped.
  945A G6201 17 Estimated Delivery Date Use for Materiel Obligation Validation (MOV) and excessive quantity verification inquiries to identify the estimated shipping date (ESD) Use in materiel release advice (DIC AE6), materiel release confirmation, disposal shipment confirmation (DIC AEJ), historical materiel release confirmation, disposal release confirmation, and historical disposal release confirmation transactions to identify the estimated shipping date or estimated date materiel will be available for shipment when shipment has not occurred.
  945A G6201 BD Required By For security assistance, identifies the required availability date (a calculated date that is derived from the amount of time remaining from the date of requisition until the materiel is required) 1. Use in materiel release denials to identify the required delivery date from the original materiel release order. 2. Future streamlined data; see introductory DLMS note 4c.
  945A G6201 BH Offered for Delivery Use in materiel release advice and disposal release advice transactions to identify the date materiel is tendered to the carrier for shipment.
  945A G6201 BU Rejection 1. Use in materiel release denial, historical materiel release denial, disposal release denial, and historical disposal release denial transactions to identify the date of warehouse refusal. 2. DLMS enhancement; see introductory DLMS note 4a.
  945A G6201 TR Transfer Use as a general term for the date materiel is released or transfered Use in materiel release advice and disposal release advice transactions to identify the date materiel is transferred to the carrier if a delay occurs prior to actual shipment.
  945A G6202
  945A QTY01 01 Discrete Quantity Use in initial materiel release confirmation, materiel release advice and disposal release advice transactions to identify the quantity for which status is being provided Use in initial materiel release confirmation, materiel release advice and disposal release advice transactions to identify the quantity for which status is being provided. (This equates to the quantity carried in MILSTRIP DIC AR_ or AE6, AEJ, AGJ, or ASZ.)
  945A QTY01 03 Discreet Quantity - Rejected Material Use to identify the quantity which was cancelled Use in materiel release cancellation advice, historical materiel release cancellation advice, disposal release cancellation advice, and historical disposal release cancellation advice transactions to identify the quantity which was cancelled. (This equates to the quantity carried in MILSTRIP DIC AG6)
  945A QTY01 39 Shipped Quantity Use to identify shipped quantity Use in reply to materiel release cancellation request, historical reply to materiel release cancellation request, reply to disposal release cancellation request, and historical reply to disposal release confirmation request transactions to identify the quantity which is confirmed/shipped. (This equates to the quantity carried in MILSTRIP DIC AU_.)
  945A QTY01 QC Quantity Disapproved Use in materiel release denial, historical materiel release denial, disposal release denial, and historical disposal release denial transactions to identify the quantity of the warehouse refusal. (This equates to the quantity carried in MILSTRIP DIC A6_.) (Also applicable to intra-AF RDO denial.)
  945A QTY01 V1 Retention Quantity Use to identify the retention level Use in disposal release confirmation denial, and historical disposal release confirmation transactions to identify the quantity actually retained. (Applicable to MILSTRIP DIC ARJ, AEJ, AGJ, A6J, ARL, or ARK)
  945A QTY02
  945A QTY03
  945A QTY03-01
  945A QTY03-02
  945A AMT01 NT Unit Value Use to identify the standard unit price 1. Use in CAV Materiel Release Confirmation transactions to indicate the unit price of an item. 2. Use to identify the unit price applicable to the materiel identified by the release confirmation supporting NSYs and FRC under DLA industrial activity support agreement. Authorized DLMS enhancement; Refer to ADC 381. 3. DLMS transactions authorize an expanded unit price field size of 9 digits for dollars and 2 digits for cents. The decimal point is passed in the transaction. If conversion to MILS legacy format is required, unit prices exceeding the legacy field size constraint will not be perpetuated. Authorized DLMS migration enhancement. Refer to ADC 221A.
  945A AMT02
  945A W2701
  945A W2702
  945A W2706
  945A N101 CA Carrier Use as needed for directed returns to identify the carrier to be used for the return shipment 1. Use for materiel release confirmations, historical materiel release confirmations, disposal release confirmations, and historical disposal release confirmations to identify the shipment unit carrier when other than the United States Postal Service. 2. The carrier is identified by Standard Carrier Alpha Code (SCAC) using Code CA in N103. The carrier name is identified in N102. 3. Perpetuate from the materiel release order to confirm use of the carrier designated for directed return. Refer to ADC 1164. 4. Authorized DLMS migration enhancement; see introductory DLMS 4e.
  945A N101 CN Consignee Use to identify an entity that is named on shipping documents as the recipient of a shipment Use for materiel release cancellation advice and historical materiel release cancellation advice transactions to identify the consignee.
  945A N101 DA Delivery Address Use to identify the in-the-clear exception ship-to address organization name 1. Use with N102 to identify the in-the-clear exception ship-to address organization name. 2. Use with 2/N2/1101, 2/N3/1102, and 2/N4/1103 to identify the full in-the-clear exception ship-to address information under authorized conditions. Refer to ADC 1290.
  945A N101 DZ Delivery Zone Use to provide the delivery location indicating where the materiel is to be staged/stored 1. Use to provide the delivery location indicating where the materiel has been staged/stored. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 396.
  945A N101 KK Registering Party Use to identify the Component UIT registry 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 should also be sent to a UIT registry for information purposes. Must be used with 2/N106/0800 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. Cite the applicable Routing Identifier in 2/N104. 2. Authorized DLMS enhancement for Air Force and DSS use with PIC NWRM UIT program. For PIC UIT, must use in conjunction with 2/N106 code PK and 1/W0612/0200 Action Code FI and cite the applicable Routing Identifier in 2/N104. 3. Authorized DLMS enhancement for Air Force use under the Retail Transportation and Supply Receipt and Acknowledgement Interchange. For PIC UIT, must use in conjunction with 2/N106 code PK and cite the applicable Routing Identifier in 2/N104. 4. Except as noted above, DLMS enhancement; see introductory DLMS note 4a.
  945A N101 LG Location of Goods 1. Use for LRO advice to identify the alternative supply source when different from the originator of the transaction. 2. Use to identify the physical location of GFP while in CICP custody. The location may be the CICP, the CICP’s warehouse or subcontractor. This location must be identified by DoDAAC. Must use for Air Force GFP accountability. Refer to ADC 1224.
  945A N101 OW Owner of Property or Unit Use to identify the property owner, material owner or owning program manager 1. Use to identify the property owner to receive this transaction when not otherwise identified. 2. For Air Force GFP accountability, use to identify the Air Force program manager in the accountable property system of record (APSR). Must identify the program manager by RIC. If the program manager DoDAAC does not have an assigned RIC, use the generic Air Force GFP APSR RIC with 2/N106=TO and use a second iteration of the N1 loop (repeating Code OW without 2/N106=TO) to provide the program manager DoDAAC. Refer to ADC 1224.
  945A N101 ST Ship To Used to identify a organization to which material is shipped as identified in the requisition or other initiating transaction Use for materiel release confirmations, historical materiel release confirmations, disposal release confirmations, and historical disposal release confirmations to identify the organization to receive the materiel.
  945A N101 UQ Subsequent Owner Use to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel Use for inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify the RIC to which ownership is being transferred (the New Owner RIC). DLMS enhancement. Refer to ADC 1020.
  945A N101 XN Planning/Maintenance Organization 1. Used to identify a Shop Service Center/Shop Store. 2. Use in conjunction with N103 Identification Code Qualifier 92. 3. Refer to ADCs 284A, 381, and 1454 for known applications.
  945A N101 Z1 Party to Receive Status The entity to receive status for the designated document number 1. Use to indicate the organization to receive shipment status as identified on the original requisition. Use multiple iterations to identify all status recipients, as required. 2. The DLMS provides the capability to carry additional status recipients beyond those identified by the legacy MILSTRIP. The Media and Status Code and the Distribution Code will be retained in the DLMS to facilitate transaction conversion in a mixed legacy MILSTRIP-DLMS environment. Additional status recipients identified here cannot be passed to legacy MILSTRIP users.
  945A N101 Z4 Owning Inventory Control Point Use to indicate the source of supply Must use to identify the ICP to receive the transaction set.
  945A N101 Z7 Mark-for Party Use for materiel release confirmations and historical materiel release confirmations to identify an entity located within the ship-to address that is to actually receive the materiel. The Mark-for Party may be identified by DoDAAC, RIC, clear text, or a combination of these. Only one of DoDAAC or RIC may be used. Authorized DLMS enhancement; see introductory DLMS note 4e. Refer to ADC 1009A.
  945A N102
  945A N103 2 Standard Carrier Alpha Code (SCAC) Use to identify the commercial carrier 1. Use with N101 Code CA to identify the commercial carrier by code. Identify the value of the SCAC in N104. 2. Authorized DLMS migration enhancement; see introductory DLMS 4e.
  945A N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations 1. DLMS enhancement; see introductory DLMS note 4a. 2. Authorized for use by Air Force CICP to identify other organizations associated with the transaction by DODAAC.
  945A N103 92 Assigned by Buyer or Buyer's Agent Use to identify the user assigned Shop Service Center/Shop Store Identifier Use with N101 Entity Identifier Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer to ADCs 284A, 381, and 1454.
  945A N103 M4 Department of Defense Routing Identifier Code (RIC) Use to serve multiple purposes; supply source codes, inter-system routing codes, intra-system routing codes, and consignor (shipper) codes
  945A N103 UR Uniform Resource Locator (URL) Use when appropriate to identify the Component Unique Item Tracking (UIT) registry 1. Use when appropriate to identify the Component UIT registry. 2. DLMS enhancement; see introductory DLMS note 4a.
  945A N104
  945A N106 PK Party to Receive Copy 1. Use when appropriate to send an information copy to a Component UIT registry. For use with N101 code KK. 2. Authorized DLMS enhancement for Air Force and DSS use with PIC NWRM UIT program. For PIC UIT, must use in conjunction with 2/N101 code KK and 1/W0612/0200 Action Code FI and cite the applicable RIC in 2/N104. 3. Authorized DLMS enhancement for Air Force use under the Retail Transportation and Supply Receipt and Acknowledgement Interchange. For PIC UIT, must use in conjunction with 2/N101 code KK and cite the applicable RIC in 2/N104. 4. Except as noted above, DLMS enhancement; see introductory DLMS note 4a.
  945A N106 TO Message To Use to identify the party to receive the transaction set Use with the appropriate 2/N101/0800 to indicate that the organization cited in N104 is receiving the transaction set.
  945A LM01 DF Department of Defense (DoD) Executive department of the U.S. federal government charged with coordinating and supervising the U.S. Armed Forces and related functions and agencies.
  945A LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data 1. The MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed legacy MILSTRIP-DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. In a mixed legacy MILSTRIP-DLMS environment, for the inter-service ammunition interfaces, when including BG1/BG2 data, Army must use 2 iterations of LQ to provide DIC AR_ as well as either DIC BG1 or BG2 as applicable, to alert DAAS of the BG1/ BG2 requirement for inter-service ammunition transactions. See ADC 1040.
Page 188  of  195 First   Previous   184  185  186  187  [188]  189  190  191  192  193  Next   Last