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 IC REF CODE X12 CODE NAME GENERAL CODE DEFINITION CODE DLMS NOTE DLMS MIN MAX
  867I BPT01 ZZ Mutually Defined 1. Use to identify the Unit of Use Indicator. When included, the quantity and unit of measure values associated with this transaction are applicable to the unit of use. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  867I BPT03
  867I BPT04 01 Product Transfer Use to identify issue transactions. (MILSTRAP DIC D7_functionality.)
  867I BPT07 FI File Authorized for Air Force and DSS use with PIC NWRM UIT. Use to identify an issue image transaction where the original issue transaction has bypassed the normal DAAS transaction flow. All transaction set recipients must use extreme caution to ensure that individual transactions with this code do not process as action documents which affect accountable records. Must use with 2/N101/50 code ‘KK’ and 2/N106/50 code ‘PK’. There will be no 2/N106/50 code ‘TO’ for this transaction. Refer to ADC 347.
  867I BPT07 W1 Reconcile Historical Records Use to indicate the submission of historical information on previously reported issues. Recipients may not reject these transactions.
  867I BPT08
  867I N101 BT Bill-to-Party The organization to receive the billing for goods and/or services 1. Use for SFIS compliant systems to identify the BPN of the party to receive the bill. BPN may only be used when the corresponding DoDAAC is also provided. This will require a second iteration of the N1 loop with the same qualifier. 2. Authorized DLMS enhancement; see introductory DLMS note 5e. 3/6
  867I N101 SB Storage Area Use to identify the distribution depot/storage activity 1. Use to identify the depot or storage activity. Use the Routing Identifier Code (RIC) for the activity unless otherwise authorized. 2. For Air Force GFP accountability, use to identify the CICP as the responsible custodial activity. Refer to ADC 1224. 1/60
  867I N101 XN Planning/Maintenance Organization Use to identify the entity designated to carry Mission Support Material for distribution to End-Use shops and other customers 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. 1/3
  867I N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations DLMS enhancement; see introductory DLMS note 5a. 6/6
  867I N103 50 Business License Number Use to identify buying or selling entities processing intragovernmental transactions 1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the buyer’s BPN in N104. 2. Authorized DLMS enhancement; see introductory DLMS note 5e. 9/9
  867I N103 92 Assigned by Buyer or Buyer's Agent Use to identify the user assigned Shop Service Center/Shop Store Identifier Use with N101 Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer to ADCs 284A, 381, and 1454. 2/80
  867I 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
  867I N104
  867I N106 FR Message From Use to identify the party originating the transaction set Must use to indicate the organization cited in N104 is originating the transaction set. 1/60
  867I PTD01 BC Issue - Other Agency Issue (Non-DoD Activities) - Use to identify issues to non-DoD activities. Excludes issues of end items to be repaired. (Corresponds to MILSTRAP DIC D7C.)
  867I PTD01 BD Issue - Other Department Issue (DoD Activities) - Use to identify issues to other DoD activities. Excludes issues of end items to be repaired. (Corresponds to MILSTRAP DIC D7B.)
  867I PTD01 BE Grant Aid Issue (Grant Aid) - Use to identify issues to a Security Assistance (SA) (Grant Aid) program. (Corresponds to MILSTRAP DIC D7D.)
  867I PTD01 BF Foreign Military Sale Issue (Foreign Military Sales) - Use to identify issues to a SA (Foreign Military Sales (FMS)) program. (Corresponds to MILSTRAP DIC D7E.)
  867I PTD01 BG Test and Evaluation Issue (Destructive Test/Evaluation) Use to identify issues for destructive test and/or evaluation when the item is not expected to be returned. (Corresponds to MILSTRAP DIC D7G.)
  867I PTD01 BH Furnished Goods and Services Issue (Furnished Materiel for Consumption) - Issue of materiel furnished by the owner to be consumed or expended in the manufacturing or maintenance process. Includes issues from inventory or by direct delivery from a vendor. Excludes materiel furnished for incorporation in the deliverable item. (Corresponds to MILSTRAP DIC D7H.)
  867I PTD01 BI Reutilization and Marketing Issue (Reutilization and Marketing) - Use to identify issues to a Defense Reutilization and Marketing Office (DRMO). (Corresponds to MILSTRAP DIC D7J.)
  867I PTD01 BJ Relocation Issue (Relocation) - Use to identify issues for relocation between storage activities without change in ownership. Excludes issues of items for repair or test/evaluation. (Corresponds to MILSTRAP DIC D7K.)
  867I PTD01 BK Modification Issue (Assembly/Disassembly/Reclamation/Conversion/Modification) - Use to identify issues of components for assembly or items for disassembly, reclamation, conversion, or modification furnished by the owner from inventory or by direct delivery from vendor. Includes materiel furnished for incorporation in a deliverable item. Excludes issue of materiel furnished to be consumed or expended during the manufacture or maintenance process. (Corresponds to MILSTRAP DIC D7L.)
  867I PTD01 BL Repair or Nondestructive Testing Issue (Repair or Nondestructive Test/Evaluation) - Use to identify issues from inventory for repair or nondestructive test/evaluation and expected return of the same item. (Corresponds to MILSTRAP DIC D7M.)
  867I PTD01 BM Loan Issue (Loan) - Use to identify issues from inventory for loan to authorized recipients. Includes Government-owned equipment furnished for use in performing a contract. (Corresponds to MILSTRAP DIC D7N.)
  867I PTD01 BN Return Issue (Returned Purchases) - Use to identify issues of returned purchases from inventory to suppliers for credit or reimbursement. (Corresponds to MILSTRAP DIC D7P.)
  867I PTD01 BO Designated Items Issue (Designated Items) - Use to identify issues of designated items from inventory for installation on a principal item/weapon system. (Corresponds to MILSTRAP DIC D7Q.)
  867I PTD01 BQ Other Use to identify issues from inventory when a specific Product Transfer Type Code is not otherwise provided. Assignor of code will maintain detailed intelligence pertaining to its use. (Corresponds to MILSTRAP DIC D7Z.)
  867I PTD01 BR Exchange Issue (Exchange Items) - Use to identify issues when a like item is returned on an exchange basis. (Corresponds to MILSTRAP DIC D7R.)
  867I PTD01 OE Ordnance Expenditure Issue (Ordnance Expenditure) – Use to identify the issue as being related to an ordnance expenditure.
  867I PTD01 SM Sample Used for CAV Detail Record. Authorized for INTERIM USE by Navy as a flag to identify CAV non-balance affecting ‘detail’ issue transactions. The balance affecting CAV “summary” issue transaction must use the appropriate standard product transfer type code. Code ‘SM’ is nonstandard and is authorized for intra-Navy interim use pending implementation of “detail” information within a standard DLMS issue transaction through looping structure. Navy will address CAV becoming compliant with DLMS standard after Navy ERP completes the Single Supply Solution Release 1.1 implementation in 2012. PTD01 code ‘SM’ will be deleted from 867I at that time. Refer to ADC 341.
  867I PTD01 SS Stock Sale Issue (Own Service/Agency) - Use to identify issues to own service or agency. Excludes issues of end items to be repaired. (Corresponds to MILSTRAP DIC D7A.)
  867I DTM01 011 Shipped Use to identify the date released to carrier/shipment date, regardless of shipment method 1. Use with Commercial Asset Visibility (CAV) transactions to indicate date shipped. 2. DLMS enhancement; see introductory DLMS note 5a. 8/8
  867I DTM01 102 Issue Usse to identify the materiel issue date 1. Use to identify the materiel issue date (date materiel was dropped from the custodial “available-for-issue” balance). 2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page. 8/8
  867I DTM01 140 Actual Use to identify date transaction was prepared Use to identify date transaction was prepared. 8/8
  867I DTM01 938 Order Use to indicate an order date Use in commercial asset visibility (CAV). 8/8
  867I DTM02
  867I DTM03
  867I REF01 16 Military Interdepartmental Purchase Request (MIPR) Number Use to establish the availability of funds and to procure, perform services, or furnish material to or for the required service 1. Use when tracking in-process maintenance; otherwise do not use. 2. DLMS enhancement; see introductory DLMS note 5a. 1/20
  867I REF01 1I 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 5a. 4/4
  867I REF01 43 Supporting Document Number Use to identify, track, and reference a document or transaction across various processes, including procurement, receipts, and maintenance Used to perpetuate/convey a Supporting Maintenance Document Number as necessary. The content in this field may only be meaningful to the receiver of this transaction. May be used to convey maintenance control/document numbers. 1/30
  867I REF01 6L Agent Contract Number Use in Government Furnished Property (GFP)-related transactions to identify the procurement instrument identifier (PIID) applicable to the contract authorizing the contractor to have custody of Government Furnished Property (GFP) 1. Use in GFP-related transactions to identify the procurement instrument identifier (PIID) applicable to the contract authorizing the contractor to have custody of GFP. Use the legacy procurement instrument identification number (PIIN) pending transition to the PIID. 2. If GFP is authorized under a PIID call/order number (F in 9th position), provide the PIID call/order number in the PIID field. 3. Required for Air Force GFP accountability to identify the CICP’s contract number. 4. Authorized DLMS enhancement; see introductory DLMS note 5e on IC cover page. Refer to ADC 1224. 13/13
  867I REF01 77 Work Package Use to identify a maintenance work order number 1. Use to identify a maintenance work order number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 1/30
  867I REF01 86 Operation Number Use to identify the Key Operation (KO) Number associated with the JO 1. Use to identify the Key Operation (KO) Number associated with the JO. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 1/50
  867I REF01 9R Job Order Number Use to identify Job Order (JO) Number 1. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 2. For DoD SLOA/Accounting Classification compliance the Job Order Number may be repeated as a Work Order Number (FA201 Qualifier WO). Refer to ADC 1043. 1/50
  867I REF01 AH Agreement Number Use to identify the Depot Maintenance Inter-Service Support Agreement (DMISA) number when tracking in-process maintenance or materiel 1. Use to identify the Depot Maintenance Inter-Service Support Agreement. Use when tracking in-process maintenance, otherwise do not use. 2. DLMS enhancement; see introductory DLMS note 5a. 1/30
  867I REF01 CO Customer Order Number Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 1. Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381 (or as applicable). 5/5
  867I REF01 CT Contract Number A standard unique identification of a DoD procurement contract (contract number) that specifically differentiates one contract from all other contracts 1. Use in GFP-related transactions to provide contract information associated with the authorizing shipment of GFP to the contractor. 2. Use to identify the procurement instrument identifier (PIID). Use the legacy procurement instrument identification number (PIIN) pending transition to the PIID. When GFP is authorized under a PIID call/order number (F in 9th position), provide the value in the PIID field. For Other Transaction (OT) agreements, the type of instrument (9th position of PIID) will be a 3 for Research OTs or 9 for Prototype and Production OTs. Refer to ADC 1161A or ADC 1420. 3. Authorized DLMS enhancement. Refer to ADC 1014 and ADC 1224. 1/13
  867I REF01 CU Clear Text Clause Use to provide a clear text description that is not otherwise described by authorized codes 1. Use with 2/PTD01/010 code BQ to provide a clear text description that is not otherwise described by authorized codes. 2. DLMS enhancement; see introductory DLMS note 5a. 1/30
Page 136  of  195 First   Previous   132  133  134  135  [136]  137  138  139  140  141  Next   Last