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 IC REF CODESorted by ascending CODE NAME GENERAL CODE DEFINITION CODE DLMS NOTE
  180M BGN01 0 Original Indicates the initial transaction
  180M 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. Future streamlined data; see introductory DLMS note 2c.
  511M BR01 0 Original Indicates the initial transaction
  511M 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 BR01 0 Original Indicates the initial transaction
  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.
  517G BR01 0 Original Indicates the initial transaction
  517G 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. Future streamlined data; see introductory DLMS note 3c.
  517M BR01 0 Original Indicates the initial transaction
  517M 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. (Applicable only to DIC AP8 and AP9). 2. Future streamlined data; see introductory DLMS note 3c.
  517M 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. Future streamlined data; see introductory DLMS note 3c.
  527D BR01 0 Original Indicates the initial transaction
  527D 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 4c.
  527R BR01 0 Original Indicates the initial transaction
  527R 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. In a mixed DLS-DLMS environment, when including BG1/BG2 data for Inter-Service Ammunition interface, must use 2 iterations of LQ to provide DIC D6_ as well as either DIC BG1 or BG2 as applicable, to alert DAS of BG1/ BG2 requirement for non-DLMS Ammunition system trading partners: Naval Operational Logistics Support Center (NOLSC) Ordnance Information System-Wholesale (OIS-W), Program Manager for Ammunition, Marine Corps Systems Command (MARCORSYSCOM) Ordnance Information System-Marine Corps (OIS-M),and Warner Robins Air Logistics Center Combat Ammunition System (CAS). 3. Future streamlined data; see introductory DLMS note 5c.
  536L BR01 0 Original Indicates the initial transaction
  536L 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 legacy MISTRAP DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the legacy MILSTRAP DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 4c. 2 - Chanel of Distribution Code: Use in the 2/HL/010 contract loop.
  536R BR01 0 Original Indicates the initial transaction
  567C BC01 0 Original Indicates the initial transaction Use code 0 regardless of the type of contract completion status report.
  567C LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data
  650A BGN01 0 Original Indicates the initial transaction
  650A 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 DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Use in the End Item Data, Assemblage Control, and Component Data lops. 3. Future streamlined data; see introductory DLMS note 3b. 33 - Air Commodity and Special Handling Code: Use in the Component Data loop.
  650C BGN01 0 Original Indicates the initial transaction
  650C 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 DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 3b.
  810L BIG08 0 Original Indicates the initial transaction
  810L LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data May be FS1, FS2, GS1 or GS2 only.
  810L 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 6c.
  812L BCD11 0 Original Indicates the initial transaction
  812L 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 4c.
  812L 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 4c.
  812R BCD11 0 Original Indicates the initial transaction
  812R 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 5c.
  812R 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Future streamlined data; see introductory DLMS note 5c.
  824R BGN01 0 Original Indicates the initial transaction
  824R 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 DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. The DIC is not to be applicable to every rejection transaction. 3. May use 2 iterations of LQ01 code 0 when the rejected transaction contained an LQ01 code 0. Use one iteration with LQ02 code value DZG, when applicable, to represent DLMS 824R equated to MILSTRAP DIC DZG in a mixed DLS/DLMS environment. Use another iteration of LQ01 code 0 with the code value from the transaction being rejected when applicable. 4. Future Streamlined data; See introductory DLMS note 6c.
  830D BFR01 0 Original Indicates the initial transaction
  830D LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data Use “CD” to indicate the data reflects DE Projected Supply Plan requirements. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
  830R BFR01 0 Original Indicates the initial transaction
  830R 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. Future Streamlined data; see DLMS introductory note 4c. 2. The DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
  830W BFR01 0 Original Indicates the initial transaction
  830W 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. Future Streamlined data; see introductory DLMS note 3c. 2. The DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
  832N BCT10 0 Original Indicates the initial transaction Must use to satisfy syntax requirements. Refer to the LIN segment for the purpose code (ad, change, delete).
  842A-W BNR01 0 Original Indicates the initial transaction 1. Use to identify a new submission. 2. Transaction Set Purpose Code 0 is also used on WebSDR-forwarded SDRs where the original SDR was directed to the wrong action activity (associated with disposition/status reply code 504). It will appear as a new SDR to the new action activity, but will include identification of the forwarding activity and date forwarded (Qualifier 514).
  842P BNR01 0 Original Indicates the initial transaction Used when the Originator forwards to the Screening Point. Originators are required to execute this transaction set within 24 hours of discovery for Category I and three calendar days of discovery for Category I PQDRs.
  846A BIA01 0 Original Indicates the initial transaction
  846C BIA01 0 Original Indicates the initial transaction
  846D BIA01 0 Original Indicates the initial transaction
  846D 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. Future Streamlined data; see introductory DLMS note 5c. 2. The DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
  846F BIA01 0 Original Indicates the initial transaction
  846F 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. Future Streamlined data; see DLMS Introductory note 4c. 2. The DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
Page 1  of  141 First   Previous   [1]  2  3  4  5  6  7  8  9  10  Next   Last