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
  846I BIA02 TI Asset Status Inquiry Use to identify a Request for Asset Status Report transaction. (MILSTRAP DIC DZE functionality) .
  846I BIA02 TJ Asset Status Advice Use to identify an Asset Status Report transaction. (MILSTRAP DIC DZA and DZF functionality).
  846I BIA06 EO End of Day Processing 1. Use to identify that an end-of-day Asset Status Report transaction is being provided. Authorized DLMS enhancement for use by DLA industrial activity support agreement; see introductory DLMS note 4e. Refer to ADC 374. 2. Approved for use in X12 version 5030. 3. DLMS enhancement, except as noted for DLA industrial activity support agreement. See introductory DLMS note 4a.
  846I N101 RL Reporting Location For Intra-Army use to identify the DODAAC of the contractor reporting GFM consumption (BIA02=62/DIC BZE functionality). Refer to ADC 431.
  846I N101 SB Storage Area Use to indicate a depot or storage activity.
  846I N101 Z4 Owning Inventory Control Point Use to indicate the source of supply
  846I 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 DLMS enhancement. See introductory DLMS note 4a.
  846I 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
  846I N106 FR Message From Use to identify the party originating the transaction set 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.
  846I LIN02 A2 Department of Defense Identification Code (DoDIC) Use to identify specific types of ammunition and explosives, indicating both the item and its packaging 1. Use to identify ammunition items. 2. DLMS enhancement. See introductory DLMS note 4a.
  846I LIN02 A4 Subsistence Identification Number Use to identify a brand name resale subsistence item 1. Use to identify subsistence items. 2. DLMS enhancement. See introductory DLMS note 4a.
  846I LIN02 DS Group ID Use with 1/BIA02/20 code QT (Asset Status Count Transaction) to comply with ANSI syntax requirement. Indicate Z in LIN03. Refer to ADC 481.
  846I LIN02 F4 Series Identifier 1. Use to identify the manufacturer's series number of the end item. 2. DLMS enhancement. See introductory DLMS note 4a.
  846I LIN02 FB Form Number A unique stock number associated with a specific Approved Code form 1. Use to identify the form stock number. 2. DLMS enhancement. See introductory DLMS note 4a.
  846I LIN02 FS National Stock Number A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification
  846I LIN02 MG Manufacturer's Part Number A number assigned by a manufacturer to an item of production Use to identify nonstandard materiel.
  846I LIN02 MN Model Number 1. Use to identify the manufacturer's model number of the end item. 2. DLMS enhancement. See introductory DLMS note 4a.
  846I LIN02 SN Serial Number A value assigned for identification of an item 1. Use to identify the manufacturer's serial number of the end item. 2. DLMS enhancement. See introductory DLMS note 4a.
  846I LIN02 SW Stock Number 1. Use to identify the local stock number (LSN). 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  846I LIN02 YP Publication Number Reference number assigned to a publication or catalog 1. Use to identify the publication stock number. 2. DLMS enhancement. See introductory DLMS note 4a.
  846I LIN02 ZR Service Control Identification Use to identify Materiel Control Tracking (MCT) tag number. The MCT tag number is an authorized DLMS enhancement for DLA industrial activity support agreement only; see introductory DLMS note 4e. Refer to ADC 374.
  846I LIN04 EP Buyer's End Product Number For Intra-Army, use with LIN02=FS to indicate NSN of the associated end item (BIA02=62/DIC BZE functionality) Refer to ADC 431.
  846I LIN04 FS National Stock Number A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification The NSN is provided as a cross-reference when unit of use indicator is included and the Local Stock Number (LSN) is identified as the primary materiel identification. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  846I LIN04 ZB Commercial and Government Entity (CAGE) Code Code assigned to establishments which either fabricates items of production and/or have design control of items procured by the federal government, or to identify certain military specifications or standards, and certain numbering systems developed by government agencies, panels or committees Use only with LIN02 code MG to uniquely identify a manufacturer's part number.
  846I DTM01 90 Report Start Use in asset status inquiries to identify the start date for inventory reporting.
  846I DTM01 91 Report End Use in asset status inquiries to identify the stop date for inventory reporting.
  846I DTM01 106 Required By Use in asset status inquiries to identify the date by which a one-time asset status report is required.
  846I DTM01 600 As Of 1. Use for asset status reports to identify the date associated with the inventory information (date transaction was prepared). Express this date in Universal Time Coordinate. 2. Used between the Army and DLA to determine the most current asset posture for assets stored under DLA/SMS ownership when more than one asset report is received within the same cycle. 3. Navy uses this date intra-Navy to determine the most current asset posture when more than one asset report is received within the same cycle. This equates to intra-Navy prescribed data in MILSTRAP DZA multiuse field, rp 73-75. Refer to ADC 35. 4. Used to support DLA industrial activity support agreement. 5. Ammunition and ammunition related transactions use this date to determine the most current asset posture when more than one asset report is received within the same cycle. This equates to Ammunition transaction prescribed data in MILSTRAP DZA multiuse field, rp 73-75. Refer to ADC 4.
  846I DTM04 UT Universal Time Coordinate
  846I REF01 6 System Number Navy uses to cite the type of system the activity is using to manage their materiel. Authorized for intra-Navy use only, to identify the system type. For all other use this is a DLMS enhancement; see introductory DLMS note 4a. Refer to ADC 356.
  846I REF01 55 Sequence Number For Intra-Army use to identify the report sequence number associated with the report of GFM consumption. Number each report sequentially through duration of the contract, beginning with 01. (BIA02=62/DIC BZE functionality) Refer to ADC 431.
  846I REF01 86 Operation Number 1. Use to identify the key operation (KO) number. For use with Navy Shipyards. 2. Authorized DLMS enhancement for DLA industrial activity support agreement; see introductory DLMS note 4e. Refer to ADC 374.
  846I REF01 9R Job Order Number 1. For use with Navy Shipyards. 2. Authorized DLMS enhancement for DLA industrial activity support agreement; see introductory DLMS note 4e. Refer to ADC 374.
  846I REF01 BO Bin Location Number 1. Authorized for intra-Navy use. Refer to ADC 356. 2. DLA uses to pass the physical location of materiel at S&D IMSP sites. Authorized for use to support DLA industrial activity support agreement; see introductory DLMS note 4e. Refer to ADC 374. 3. Except as noted above, this is a DLMS enhancement; see introductory DLMS note 4a.
  846I REF01 CO Customer Order Number 1. Use to identify the Customer Order Acceptance Record (COAR). 2. Authorized DLMS enhancement for DLA industrial activity support agreement; see introductory DLMS note 4e. Refer to ADC 374.
  846I REF01 TN Transaction Reference Number A unique number generated by the original submitter of a pre-defined transaction and assigned to any pre-defined information exchange within the department of defense The transaction reference number retains its identity for the life of the generated transaction Use to identify the transaction number. Authorized DLMS migration enhancement. See introductory DLMS note 4e.
  846I REF01 W8 Suffix Use to identify supply transaction partial actions taken on the original document without duplicating or causing loss of identity of the original document number Used in a mixed DLMS/ DLS environment for asset status reports to accommodate conversion to DLS when quantities exceed allowable DLS positions. Equates to MILSTRAP DIC DZA record position 7. Enter A through Z (except I and O). Future streamlined data which will be eliminated in a full DLMS environment when the expanded quantity field size is used.
  846I REF01 YL Allowance Recipient Identification Authorized for intra-Navy use only, to identify the Allowance Type Indicator. Values are O’ for General Stores and ‘Q’ for Restricted Stores. For all other use this is a DLMS enhancement; see introductory DLMS note 4a. Refer to ADC 356.
  846I REF01 FSN Assigned Sequence Number Authorized for intra-Navy use only, to identify the Automated Shore Interface Sequence Number of the last allowance calculated for the activity. For all other use this is a DLMS enhancement; see introductory DLMS note 4a. Refer to ADC 356.
  846I REF01 PWC Preliminary Work Candidate Number 1. Use to identify Requisition Alert Document Number. For use with Navy Shipyards. 2. Authorized DLMS enhancement for DLA industrial activity support agreement; see introductory DLMS note 4e. Refer to ADC 374.
  846I REF04-01 W8 Suffix Use to identify supply transaction partial actions taken on the original document without duplicating or causing loss of identity of the original document number 1. Use with REF01 code PWC to identify the Requisition Alert Document Number suffix. For use with Navy Shipyards. 2. Authorized DLMS enhancement for DLA industrial activity support agreement; see introductory DLMS note 4e. Refer to ADC 374.
  846I CS04 C7 Contract Line Item Number For Intra-Army use to identify the CLIN (or CLIN including the Sub Contract Line Item Number (SUBCLIN), as appropriate, when reporting GFM/GFE consumption.
  846I DD08 N No DLMS enhancement. See introductory DLMS note 4a.
  846I DD08 Y Yes DLMS enhancement. See introductory DLMS note 4a.
  846I 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.
  846I 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 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.
  846I 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 DLS/DLMS transition, this field will be used to perpetuate/populate the DLS Supplemental Address (SUPAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 4d. 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 4a. 4. Under full DLMS, the requirement to pass activity address information within the supplemental 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 4c.
  846I LQ01 AJ Utilization Code Use to identify a specialized purpose of the transaction 1. Under DLS, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 4a.
  846I LQ01 EA Asset Status or Transaction Reporting Code Use to identify the type of asset status report required.
  846I LQ01 GQ Group Qualifier Code Use to identify the Materiel Management Aggregation Code (MMAC) for National Stock Number (NSN) to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group) 1. Use to identify the Material Management Aggregation Code (MAC). 2. Use to identify the MAC for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. A - data maintenance action was approved in version 5010. The approved code/name is "MAC –Material Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN) 23-10, Volumes 1 and 2.
Page 74  of  141 First   Previous   70  71  72  73  [74]  75  76  77  78  79  Next   Last