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	846I
SEGMENT NAME	N1-Name
REF	N106
ID	98
X12 MIN MAX	'2/3
ELEMENT NAME	Entity Identifier Code
CODE	FR
CODE NAME	Message From
GENERAL CODE DEFINITION	Use to identify the party originating the transaction set
CODE DLMS NOTE	1. Must use in conjunction with the appropriate 1/N101/080 code to indicate the organization cited in N104 is originating the transaction set. 2. Use to identify the activity preparing the consumption report (GFM) or asset status report, except as noted below. 3. For DLA industrial activity support agreement, cite code ‘SB’ to identify the DLA DS storage activity preparing the Asset Status Report on behalf of the owning ICP. The owning ICP, when not the activity originating the transaction set, appears in 2/N101/450. 4. For Army/DLA DKS interface in a mixed DLS/DLMS environment, based upon agreement, the DLA storage activity may prepare the 846I on behalf of the DLA ICP, with the DLA ICP RI Code SMS entered as the ‘Message From’ activity originating the transaction. This is an interim DKS approach in the mixed DLMS/DLS environment to accommodate Army’s requirement for the owning ICP to map to the DLS DIC DZA rp 67-69, which is identified as the RI Code of the ICP preparing the transaction. As Army transitions to DLMS, the 1/N106/080 FR should reflect the true activity preparing the transaction set, and the appropriate qualifier for storage activity or ICP preparing the transaction should be used. The information on the owning ICP or storage activity, when not the activity originating the transaction set, should appear in 2/N101/450. See ADC 250. Any future DLA Distribution Standard System (DS) implementation should use the alternative approach documented in ADC 250.
PROPOSED CODE CHANGES
DLMS MIN MAX	Jan-60
DOD AND OTHER NAMES
FLIS DRN
ADC	055, 088, 250, 326, 374, 412, 431, 471, 1098, 1227A, 1349
VALID INPUT CODES	DLM 4000.25, Volume 2, AP7.3-1 APPENDIX 7.3, https://www.dla.mil/Defense-Data-Standards/Publications/Appendices/
REFERENCED SERVICE OR AGENCY
ADDITIONAL COMMENTS