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
  511R MEA04-01 FT Foot
  511R MEA04-01 GA Gallon
  511R MEA04-01 HJ Horsepower
  511R MEA04-01 IN Inch
  511R MEA04-01 KG Kilogram
  511R MEA04-01 LB Pound
  511R MEA04-01 LT Liter
  511R MEA04-01 MR Meter
  511R MEA04-01 OZ Ounce - Av
  511R MEA04-01 P1 Percent
  511R MEA04-01 P2 Pounds per Foot
  511R MEA04-01 PT Pint
  511R MEA04-01 QT Quart
  511R MEA04-01 R4 Calorie
  511R MEA04-01 SF Square Foot
  511R MEA04-01 SM Square Meter,
  511R MEA04-01 SY Square Yard
  511R MEA04-01 TG Gross Ton
  511R MEA04-01 TN Net Ton 2,000 LB.
  511R MEA04-01 VA Volt-ampere per Kilogram
  511R MEA04-01 WA Watts per Kilogram
  511R MEA04-01 YD Yard
  511R NTE01 ORI Order Instructions Use with Requisition Exception Data Transaction (DLA DIC YRZ-Line Counters 01-20) to indicate technical/descriptive exception information for procurement purposes. Segment may be repeated up to 20 times with same NTE01 qualifier. A maximum of 60 positions (including spaces) may be sent for each occurrence of the NTE01. A maximum of 120 positions of text (including spaces) may be sent. Pick, pack, and special delivery type instructions (DLA DIC YRZ-Line Counters 01-06) may also be entered as exception data to be forwarded to a DS storage activity, as part of an exception MRO. This type of data is limited to 360 positions (including spaces) which would be the segment, repeated up to 6 times, with the same NTE01 qualifier. Also used for USAF descriptive data associated with part numbered requisitions (A02/A0B rp 67-80). See introductory DLMS note 3e.
  511R NTE01 PDS Product Specification Use with Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code PN) to indicate an extended part number. Only a single instance of the segment is used with this NTE01 qualifier. A maximum of 60 positions of text (including spaces) may be sent. See introductory DLMS note 3e.
  511R 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.
  511R 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. Use two iterations to identify requisition DIC and Requisition Exception Data Transaction (DLA DIC YRZ), when applicable. 3. Future streamlined data; see introductory DLMS note 3c.
  511R LQ01 67 Type of Assistance Code 1. For SA transactions, use when the coded address in the transaction number does not identify the type of assistance and financing. 2. DLMS enhancement; see introductory DLMS note 3a.
  511R LQ01 78 Project Code Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes 1. Use to identify special programs, exercises, projects, operations, and other purposes. 2. For DoD SLOA/Accounting Classification compliance the Project Code may be repeated as a Project Identifier (FA201 Qualifier ‘90’). Refer to ADC 1043.
  511R LQ01 79 Priority Designator Code A code to communicate the relative importance to the requisitioner's mission based upon its force activity designator (FAD) and urgency of need designator (UND) Recommend using in all requisitions.
  511R LQ01 80 Advice Code Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action 1. Use to convey information to the supply source which is considered essential to the supply action. , 2. Use in requisition or referral order to identify the type of action desired when directing disposition of previously purchased materiel. This is a restricted use applicable when a Service has entered into an MOA with DLA relative to Service-owned stocks, centrally-managed/stored by DLA (1/BR06/020, Code RI).
  511R LQ01 83 Supply Condition Code Classifies materiel in terms of readiness for issue and use or to identify action underway to change the status of materiel 1. Use to indicate the lowest acceptable condition of materiel when requisitioning from DLA Disposition Services. 2. Use to indicate condition of previously purchased materiel. This is a restricted use applicable when a Service has entered into an MOA with DLA relative to Service-owned stocks, centrally-managed/stored by DLA (1/BR06/020, Code RI). 3. Also authorized on an Intra-Army basis with BR02 transaction type code A0 and BR06 action code “J” to indicate the condition of materiel post-post issued by Army Single Stock Fund activities. 4. When requisitioning specific reparables for induction under Depot Maintenance Inter-Service Agreement (DMISA) or comparable inter-Service agreement, cite the supply condition code (SC) applicable to the reparable item requested. Authorized SCs include D, F, G, and Q. Requisitions for induction of a Product Quality Deficiency Report (PQDR) exhibit for warrantied maintenance will cite SC Q. Refer to ADC 176.
  511R LQ01 84 Management Code 1. Authorized on an Intra-Army basis with BR02 transaction type code A0 to provide required management code information in order to accurately process transactions relative to image and post-post requisitions submitted by Army Single Stock Fund activities (Refer to ADC 243) 2. Authorized DLMS enhancement under DLA industrial activity support agreement. (Refer to ADC 352, ADC 359 and ADC 375). 3. Authorized on an intra-Navy basis with BR02 transaction type code BN to provide required management code information to accurately process transactions relative to referrals to the inventory manager. (Refer to ADC 363) 4. Authorized on an Intra-Air Force basis with BR02 transaction type code A0 to provided required management code information on the reason for the requisition. (Refer to ADC 1390).
  511R LQ01 87 Subsistence Type of Pack Code Use to indicate the degree of protection to be provided subsistence items
  511R LQ01 89 Cooperative Logistics Program Support Code For FMS transactions, must use to identify programed, nonprogrammed, and termination/drawdown requirements.
  511R LQ01 94 Identification Code Use in FMS transactions to identify the customer country's requisitioning Service Code Must use in FMS transactions to identify the customer country's requisitioning Service Code: B, D, K, P, or T. This is the SA program Customer Service Designator (codes derived from Qualifier 71, Service and Agency Code). A - data maintenance action was approved in version 5010. The approved code/name is "CSD - Customer Service Designator".
  511R LQ01 95 Offer and Release Option Code 1. For FMS transactions, must use to advise the supply source of the type of notice required prior to shipping the materiel. 2. Also authorized on an Intra-Army basis with BR02 transaction type code A0 for identification of the ownership of materiel post-post issued by Army Single Stock Fund activities.
  511R LQ01 97 Ultimate Recipient Code , 1. Use to identify the buyer of DoD materiel to allow full payment for materiel supplied to a non-DoD customer. 2. DLMS enhancement; see introductory DLMS note 3a.
  511R LQ01 99 Purpose Code Provides the owner of materiel with a means of identifying the purpose or reason for which an inventory balance is reserved 1. Use in CAV transactions. 2. DLMS enhancement; see introductory DLMS note 3a. 3. Also authorized on an Intra-Army basis with BR02 transaction type code A0 and BR06 action code “J” to identify the purpose of materiel post-post issued by Army Single Stock Fund activities.
  511R LQ01 A1 Ownership Code Provides a means of segmenting inventory balances, accounted for in inventory control records of a Military Service/DLA, but which are owned by others 1. Use in requisition or referral order to identify the ownership of previously purchased materiel. This is a restricted use applicable when a Service has entered into an MOA with DLA relative to Service-owned stocks, centrally-managed/stored by DLA (1BR06/020, Code RI). 2. Use on a referral order to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify the new/gaining (to) ownership code. DLMS enhancement. Refer to ADC 1020. 3. Also authorized on an intra-Army basis with BR02 Transaction Type Code A0 and BR06 Action Code J J - for identification of the ownership of materiel post-post issued by Army Single Stock Fund activities.
  511R LQ01 A2 Customer Within Country Code 1. For SA transactions, use when the coded address in the transaction number does not identify the customer-within-country. 2. DLMS enhancement; see introductory DLMS note 3a.
  511R LQ01 A3 Delivery Term Code For FMS transactions, use when the coded address in the transaction number does not identify the delivery term.
  511R LQ01 A5 Subcase Number 1. Use in FMS transactions based on Service requirements. 2. DLMS enhancement; see introductory DLMS note 3a.
  511R LQ01 A6 Freight Forwarder Number Must use in FMS transactions to identify the country representative or freight forwarder to receive shipments and documentation.
  511R LQ01 A7 Record Control Number Must use in MAP/GA transactions to identify the program line item number.
  511R LQ01 A8 Program Year Code Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was approved and funded.
  511R LQ01 A9 Supplemental Data A distinctive identification of specific units, activities and organizations within the Department of Defense (DoD), commercial activities which enter into materiel and service contracts with the DoD and activities of other Federal agencies which maintain logistics support arrangements with the DoD 1. Use to identify supplementary address/supplemental data. 2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the MILSTRIP Supplementary Address (SUPAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 3d. , 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 3a. 4. Under full DLMS, the requirement to pass activity address information within the supplemental data field will be streamlined. Activity address data previously contained in the SUPAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c. 5. During legacy MILSTRIP/DLMS transition, use on a referral order to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel and no billing. Cite Signal Code M and Project Code CYK in conjunction with the supplemental data field constructed as follows: Service/Agency Code Y followed by the old (from) ownership code, the RIC to which ownership is transferred, and the new/gaining (to) ownership code. Refer to ADC 1020.
  511R LQ01 AJ Utilization Code Use to identify a specialized purpose of the transaction 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.
  511R LQ01 AK Distribution Code Future streamlined data; see introductory DLMS note 3c.
  511R LQ01 AL Special Requirements Code Use to identify precedence, special handling, and processing requirements 1. Under legacy MILSTRIP, this is caried in the required delivery date field. 2. DLMS enhancement; see introductory DLMS note 3a. 3. Use in conjunction with 2/LQ01/Code RC, Requirement Code, to complete the Air Force unique NMCS/MICAP data requirement.
  511R LQ01 BD Transportation Priority Code 1. Use to identify a transportation priority which is different than that associated with the requisition priority. 2. DLMS enhancement; see introductory DLMS note 3a.
Page 12  of  141 First   Previous   8  9  10  11  [12]  13  14  15  16  17  Next   Last