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     

 
Category Details
IC 842A-W
SEGMENT NAME LQ-Industry Code Identification
REF LQ01
ID 1270
X12 MIN MAX '1/3
ELEMENT NAME Code List Qualifier Code
CODE D
CODE NAME Court Document Type Code
GENERAL CODE DEFINITION
CODE DLMS NOTE 1. Must use to identify the Discrepancy Report Document Type Code to identify the type of discrepancy report and type of shipment involved. This data element is required for the DoD WebSDR interface. 2. Valid entries are for SDR types are: • 5 - Storage Quality Control Report (SQCR) • 6 - Customer originated, direct vendor/contractor delivery. This type is used primarily for shipment of requisitioned materiel sourced by the item manger by contracted vendor shipment rather than from stock. • 7 - Customer originated, depot/lateral shipment/other. This type is used primarily for shipment of requisitioned materiel sourced by the item manager from stock; may be used for other customer SDRs. • V - Customer originated, lateral shipment under TAV. This type is used exclusively for customer reported discrepancies resulting from item manager directed lateral redistribution (initiated via MILSTRIP DIC Code A4_ with Distribution Code 2 or 3). • 8 - Depot originated, depot receipt from non-procurement source other than RDO. • A - Storage site receipt, customer return/other (Note: Comparable to Type 8, but originated outside DS; requires authorization prior to use.) • 9 - Depot originated procurement source receipt • D - DLA Distribution Field Office originated (Note: Used in conjunction with Disposition Services SDR Type Code to further distinguish the type of shipment scenario involved.) • P - Storage site receipt procurement source receipt (Note: Comparable to Type 9, but originated outside DS; requires authorization prior to use.) • R - Depot originated, redistribution order receipt. • N - Storage site receipt, depot shipment (RDO) (Note: Comparable to Type R, but originated outside DS; requires authorization prior to use. • W - Transhipper originated SDR. This type is used exclusively by ports and CPs for discrepancies discovered while materiel is in transit. Because this type of SDR may apply to a shipment unit (rather than a single document number), data element requirements differ significantly from other SDR types. 3. For future consideration, a data maintenance action was approved in version 5030. The approved code/name is "TDC - Discrepancy Report Type Code".
PROPOSED CODE CHANGES
DLMS MIN MAX
DOD AND OTHER NAMES
FLIS DRN
ADC
VALID INPUT CODES
REFERENCED SERVICE OR AGENCY
ADDITIONAL COMMENTS