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     

 
Category Details
IC 869F
SEGMENT CODE REF
SEGMENT NAME Reference Identification
POSITION 105
REF REF01
ID 128
X12 MIN MAX '2/3
ELEMENT NAME Reference Identification Qualifier
ELEMENT DLMS NOTE 1. In 2/HL/010 transaction loops, use only one of codes 1I, FQ, MF, NS, S6, WL, ABV, or XD to identify the materiel requisitioned. Must use the National Stock Number (NSN) when known, except, when appropriate for brand name subsistence items identified by a Subsistence Identification Number. 2. For 2/HL/010 UIT loops, use multiple repetitions with codes BT, LT and SE only, to identify the characteristics(s) not defined in the 2/LIN/050 segment. The 2/N1/110 segment may be used to identify the manufacturer associated with the UIT information. When the manufacturer differs, a new 2/HL/010 loop is required. 3. Supply sources only use one of codes CT or W4 to advise a procurement activity of the contract or procurement request (PR) information.
CODE CT
X12 CODE NAME Contract Number
GENERAL CODE DEFINITION A standard unique identification of a DoD procurement contract (contract number) that specifically differentiates one contract from all other contracts
CODE DLMS NOTE Use to identify the contract number PIID or obligation Agreement number associated with the requisition. When procurement is authorized under a PIID call/order number (F in 9th position), provide the value in the PIID field. For Other Transaction (OT) agreements, the type of instrument (9th position of PIID) will be a 3 for Research OTs or 9 for Prototype and Production OTs. Refer to ADC 1161A or ADC 1420.
PROPOSED CODE CHANGES
DLMS MIN MAX 1/13
DOD AND OTHER NAMES Procurement Instrument Identifier (PIID) or PIID/Call/Order Number (Parent)
FLIS DRN
ADC
DATA ELEMENT SOURCE Defense Federal Acquisition Regulation (DFARS), https://www.acquisition.gov/dfars, FEDERAL LOGISTICS INFORMATION SYSTEM (FLIS), Cataloging Data and Transaction Standards, https://www.dla.mil/Logistics-Operations/Training-and-Reference/#flis
REFERENCED SERVICE OR AGENCY
ADDITIONAL COMMENTS