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
  869A N101 ST Ship To 1. Use with code BT for reimbursable materiel. Use in requisition inquiry to identify the organization to receive the materiel, when different from the activity being billed for the materiel. Use precludes the use of code BS. 2. Future streamlined data; see introductory DLMS note 2c.
  869A N101 XN Planning/Maintenance Organization 1. Used to identify a Shop Service Center/Shop Store. 2. Use in conjunction with N103 Identification Code Qualifier 92. 3. Refer to ADCs 284A, 381, and 1454 for known applications.
  869A N101 Z1 Party to Receive Status The entity to receive status for the designated document number Use multiple iterations of the 2/N1/10 loop to identify additional status recipients when different from Service/Agency prescribed status recipients.
  869A N101 Z3 Potential Source of Supply Use in supply assistance requests as needed to identify potential alternative sources for the required materiel.
  869A N101 Z5 Management Control Activity Use for all Government Furnished Materiel (GFM) related transactions to identify the MCA associated with the GFM transaction.
  869A N101 Z7 Mark-for Party 1. Use to identify an entity located within the ship-to address that is to actually receive the materiel. 2. The Mark-for Party may be identified by DODAAC, RIC, clear text, or a combination of these. Only one of DODAAC or RIC may be used. 3. Maximum length of the mark for party is 24 positions: Mark-for clear text (with no DODAAC or RIC) displays on DoD shipment documents as two lines of 12 characters each. If text is combined with a DODAAC, up to 17 clear text characters will be allowed. If text is combined with a RIC, up to 20 clear text characters will be allowed. A slash (/) will be inserted during printing of shipment documentation to separate the DODAAC or RIC from clear text; do not perpetuate the slash (/) in the DLMS transaction. 4. Authorized DLMS enhancement; see introductory DLMS note 2f. Refer to ADC 109A. 5. Also use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MF) to identify mark-for delivery information. See introductory DLMS note 2e.
  869A N101 Z8 Last Known Source of Supply Use to identify the supply source.
  869A N101 ZE End Item Manufacturer Use in supply assistance requests to identify the manufacturer of the end item (Make). When using, cite the actual name of the end item manufacturer in N102.
  869A N101 ZS Monitoring Party Use to identify the International Logistics Control Office.
  869A N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations. The first position indicates the Component or other Government element of ownership or sponsorship. The remaining five positions are assigned under established products by the Service point of the participating Component
  869A N103 33 Commercial and Government Entity (CAGE) Use when the organization is a contractor not assigned a DODAAC.
  869A N103 92 Assigned by Buyer or Buyer's Agent Use with N101 Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer to ADCs 284A, 381, and 1454.
  869A N103 A2 Military Assistance Program Address Code (MAPAC) Use to identify the consignee in transportation documents and to obtain clear-text address and other shipment information from the military assistance program address directory (MAPAD) Use to indicate the Security Assistance (SA) structured address data. Interpretation of this data may require additional codes cited elsewhere in the transaction.
  869A N103 M4 Department of Defense Routing Identifier Code (RIC) Use to serve multiple purposes; supply source codes, inter-system routing codes, intra-system routing codes, and consignor (shipper) codes
  869A N106 FR Message From Use to identify the party originating the transaction set 1. Must use with the appropriate 2/N101/10 code to indicate the organization cited in N104 is originating the transaction set. 2. For DLMS requests for shipment tracing resulting from conversion of the original MILSTRIP DIC AFT, the originating activity will be identified as DASC. 3. For DLMS follow-up requests for the DODAAC of the initial transportation shipping activity resulting from conversion of the original MILSTRIP DIC AFY, the originating activity will be identified as the requisitioner due to lack of a from address in the MILS format.
  869A N106 TO Message To Use to identify the party to receive the transaction set Must use with the appropriate 2/N101/10 code to indicate that the organization cited in N104 is receiving the transaction set.
  869A PER01 IC Information Contact Must use in the first repetition to identify the primary POC and communication number.
  869A PER01 SU Supplier Contact
  869A PER03 AU Defense Switched Network
  869A PER03 EM Electronic Mail
  869A PER03 FX Facsimile
  869A PER03 IT International Telephone Include country and city code.
  869A PER03 TE Telephone
  869A PER03 TL Telex
  869A PER03 TX TWX
  869A PER05 AU Defense Switched Network
  869A PER05 EM Electronic Mail
  869A PER05 EX Telephone Extension Use immediately following code AU, IT, or TE to identify the telephone extension.
  869A PER05 FX Facsimile
  869A PER05 IT International Telephone Include country and city code.
  869A PER05 TE Telephone
  869A PER05 TL Telex
  869A PER05 TX TWX
  869A PER07 AU Defense Switched Network
  869A PER07 EM Electronic Mail
  869A PER07 EX Telephone Extension Use immediately following code AU, IT, or TE to identify the telephone extension.
  869A PER07 FX Facsimile
  869A PER07 IT International Telephone Include country and city code.
  869A PER07 TE Telephone
  869A PER07 TL Telex
  869A PER07 TX TWX
  869A 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.
  869A 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 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.
  869A LQ01 78 Project Code Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes Future streamlined data; see introductory DLMS note 2c.
  869A 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) Future streamlined data; see introductory DLMS note 2c.
  869A LQ01 80 Advice Code Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action Future streamlined data; see introductory DLMS note 2c.
  869A LQ01 98 Reason for Requisitioning Code Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  869A 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 supplemental address/data. 2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the MILSTRIP Supplemented Address (SUPAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 2d. 3. Expanded use of this field for supplemental data with out size restriction is a DLMS enhancement; see introductory DLMS note 2a. 4. Under full DLMS, the requirement to pass activity address information within the supplement 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 2c.
  869A 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.
  869A LQ01 AK Distribution Code
Page 104  of  141 First   Previous   100  101  102  103  [104]  105  106  107  108  109  Next   Last