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     

View ICSorted by ascending REF CODE X12 CODE NAME GENERAL CODE DEFINITION CODE DLMS NOTE DLMS MIN MAX
  869F FA201 S1 Security Cooperation Customer Code Used to represent the country, international organization, region, or program authority associated with transactions recorded in security cooperation systems and associated programs implemented in the foreign military sales (FMS) 1. For DoD SLOA/Accounting Classification use to identify �Security Cooperation Customer Code�. Refer to ADC 1043. 2. DLMS enhancement; see introductory DLMS note 4d. A field size exceeding 2 positions is not supportable under current MILSTRIP and MAPAC processes. Three character codes are not authorized at this time. 2/2
  869F FA201 S2 Security Cooperation Case Designator Use with the Security Cooperation customer code to identify a particular foreign military sale 1. For DoD SLOA/Accounting Classification use to identify �Security Cooperation Case Designator�. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 4g. A field size exceeding 3 positions is not supportable under current MILSTRIP processes. Four character codes are not authorized at this time. 3/3
  869F FA201 WO Work Order Number An individual unit of work, batch, or lot of a distinct product or service 1. For DoD SLOA/Accounting Classification use to identify �Work Order Number�. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 4g. 1/16
  869F FA201 YB Beginning Period of Availability In annual and multi-year accounts, identifies the first year of availability under law that an account may incur new obligations 1. Use to identify the Requesting Agency Component TAS BPOA (Beginning Period of Availability) in G-Invoicing related transactions. Refer to ADC 1465. 2. For DoD SLOA/Accounting Classification use to identify �Beginning Period of Availability Fiscal Year Date�. Refer to ADC 1043. 3. Use as appropriate to represent Program Year. Availability Type Code must be �X�. Refer to ADC 1043B. 4. Authorized DLMS enhancement; see introductory DLMS not 4g. 4/4
  869F FA201 YE Ending Period of Availability Use to identify the last year of availability under law that an account may incur new obligations 1. Use to identify the Requesting Agency Component TAS EPOA (Ending Period of Availability) in G-Invoicing related transactions. Refer to ADC 1465. 2. For DoD SLOA/Accounting Classification use to identify �Ending Period of Availability Fiscal Year Date�. Refer to ADC 1043. 3. Authorized DLMS enhancement; see introductory DLMS note 4g. 4/4
  869F FA202 N/A
  869F SE01 N/A
  869F SE02 N/A
  870L ST01 870 Order Status Report Organizations use this transaction set to provide status on Special Program Requirements and to notify the organization originating the transaction that the Federal Supply Classification (FSC) provided on the original transaction was incorrect. Use a single occurrence of this transaction set to transmit supply status to one or more organizations. Use one occurrence of this transaction set to transmit a single or multiple transactions. N/A
  870L ST02 N/A
  870L BSR01 3 Unsolicited Report Use to provide status Status Notification. DLA Transaction Services uses Status Notification transactions to notify the submitter that an SPR transaction was rerouted or that the FSC changed. (MILSTRAP DIC DZ9 functionality.) N/A
  870L BSR01 9 Response to a Requirement Forecast Use to convey the status of a forecast 1. SPR Status. ICP/IMM uses SPR Status transactions to provide SPR status to a forecasting activity in response to a DLMS 830R SPR transaction. (MILSTRAP DIC DYK functionality.) 2. For DDE, GDP, ASP status, use to provide status to a forecasting requirement in response to DLMS 830D Demand Data Exchange Projected Supply Plan transaction. N/A
  870L BSR02 CA All Orders - All Items Use to indicate the response applies to all specified items Use to indicate the response applies to all specified items. N/A
  870L BSR03 N/A
  870L BSR04 N/A
  870L BSR07 N/A
  870L BSR11 00 Original Indicates the initial transaction N/A
  870L BSR11 77 Simulation Exercise Use to identify a simulated mobilization exercise transaction set Activities initiating simulated mobilization exercises must ensure complete coordination with all activities involved. All transaction set recipients must use caution to ensure that transactions do not process as action documents which affect accountable records. N/A
  870L N101 GP Gateway Provider Use to identify the Routing Identifier of the Defense Automatic Addressing System (DAAS) as the intended recipient for distribution or posting to the historical record This is DLA Transaction Services. DLA Transaction Services uses when providing Status Notification that an SPR transaction was rerouted or that the FSC has changed (BSR01 Status Report Code 3.) 3/3
  870L N101 Z4 Owning Inventory Control Point Use to indicate the source of supply 1. Use to identify the ICP or IMM providing SPR status (BSR01 Status Report Code 9). 2. Use to identify the source of supply providing DDE, GDP or ASP status (BSR01 Status Report Code 9). 1/60
  870L N101 ZN Losing Inventory Manager Use for delinquent due-in, due-in reconciliation inquiry, due-in reconciliation advice, and memorandum due-in transactions to identify the Losing Inventory Manager (LIM) Use with BSR01 Status Report Code 9 when the LIM is providing SPR status. 1/60
  870L N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations DLMS enhancement. See introductory DLMS note 3a. 6/6
  870L 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 3/3
  870L N104 N/A
  870L N106 FR Message From Use to identify the party originating the transaction set Must use with the appropriate 1/N101/050 code to indicate the organization cited in N104 originating the transaction set. 1/60
  870L HL01 N/A
  870L HL03 W Transaction Reference Number Use to identify the individual SPR transaction status loops. N/A
  870L DTM01 097 Transaction Creation Use to identify the date of transaction preparation 8/8
  870L DTM02 N/A
  870L REF01 FG Fund Identification Number Use to identify the fund purpose code. Describes the purpose or intended use of funds or financial accounting classification data identified on DLMS transactions For Navy use, this is the Program Funding Indicator associated to a Gross Demand Plan (GDP). See ADC 1267. 2/2
  870L 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 Must use to identify the customer assigned transaction number. This is the document number. 14/14
  870L REF01 WL Federal Supply Classification Code Use to identify the supply classification of an item of supply identified under the federal cataloging program, an item of production and/or a homogeneous area of commodities in respect to their physical or performance characteristics. The first two digits identify the federal supply group and the last two digits identify the specific class within the specified group Use for Status Notification transactions to identify the correct FSC associated with the materiel cited in an SPR transaction. 4/4
  870L REF02 N/A
  870L N101 78 Service Requester Must use to indicate the activity submitting the original SPR transaction. N/A
  870L N101 ZA Corrected Address Use to identify the source of supply to whom DLA Transaction Services has rerouted the transaction. N/A
  870L N101 ZP Gaining Inventory Manager Use for delinquent due-in, due-in reconciliation inquiry, due-in reconciliation advice, and memorandum due-in transactions to identify the Gaining Inventory Manager (GIM) Use for SPR Status transactions to identify the Gaining Item Manager (GIM) for those items of supply involved in logistics reassignment. 1/60
  870L N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations DLMS enhancement. See introductory DLMS note 3a. 6/6
  870L 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 3/3
  870L N104 N/A
  870L N106 TO Message To Use to identify the party to receive the transaction set Must use with 2/N101/090 code 78 to indicate the organization cited in N104 is receiving the transaction set. 1/60
  870L 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. N/A
  870L LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data Use a second iteration with BSR01 code 3 to identify the DIC of the original transaction for which status is being provided. 3/3
  870L LQ01 78 Project Code Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes 3/3
  870L 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) Recommend using in all requisitions. 2/2
  870L LQ01 81 Status Code Use to inform activities of action taken or being taken on materiel requisitioned but not shipped, shipment consignments instructions, or disposition instructions for materiel offered under the materiel returns program (MRP) Use multiple repetitions when needed to identify status associated with the transaction number to notify of an FSC change (Status Code BG) and/or that DLA Transaction Services rerouted an SPR transaction (Status Code BM); otherwise do not use. Use with Status Notification transactions (BSR01 code 3). 2/2
  870L LQ01 83 Supply Condition Code Classifies materiel in terms of readiness for issue and use or to identify action underway to change the status of materiel 1/1
  870L 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 DLSS/DLMS transition, this field will be used to perpetuate/populate the DLSS Supplementary Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 3d. 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 3a. 4. Under full DLMS, the requirement to pass activity address information within the supplemental data field will be streamlined. Activity address data previous ly contained in the SUPAAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c. 6/6
  870L LQ01 AJ Utilization Code Use to identify a specialized purpose of the transaction 1. Under DLSS, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 3a. 1/1
  870L LQ01 ED Coast Designation Code Identifies specific areas of the world for purposes of summarizing Military Transportation Evaluation Reports 1/1
  870L 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 Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). 2. This is an AirForce-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. 3. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volumes 1 and 2. 2/2
Page 149  of  190 First   Previous   145  146  147  148  [149]  150  151  152  153  154  Next   Last