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
  846P LIN04 SW Stock Number Use to identify a unique identifier for a product in a warehouse or inventory system 1. Use to identify the local stock number (LSN). 2. The LSN is provided as a cross-reference when unit of use indicator is included and the unit of use LSN is identified as the primary materiel identification. Authorized DLMS enhancement under DLA industrial activity support agreement. 13/13
  846P 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 with LIN02 code MG to uniquely identify a manufacturer's part number. 5/5
  846P LIN05 N/A
  846P DTM01 090 Report Start Use to identify reporting start date Use in transaction history requests to identify the transaction history reporting start date. (Report start date equates to MILSTRAP DIC DZJ rp 25-28 transaction history start date.) 8/8
  846P DTM01 091 Report End Use to identify the reporting stop or end date Use in transaction history requests to identify the transaction history reporting end date. (Report end date is a date equivalent for MILSTRAP DIC DZJ rp 29-31 which is the total number of prior days transaction history required. Accordingly, the report end date will precede the report start date.) 8/8
  846P DTM01 097 Transaction Creation Use to identify the date of transaction preparation Use to identify the date the transaction was prepared. 8/8
  846P DTM01 197 End Use to identify an end or cutoff date Use to identify the Physical Inventory Cutoff Date (PICD). 8/8
  846P DTM01 501 Expected Reply For Air Force Government Furnished Property (GFP) accountability, use to identify the due date established by the Air Force program manager for the CICP response to the requested physical inventory 1. For Air Force GFP accountability, use to identify the due date established by the Air Force program manager for the CICP response to the requested physical inventory. Use in conjunction with document number assigned to this specific request (REF01 Code TN). Refer to ADC 1224. 2. DLMS enhancement; See introductory DLMS note 4a. 8/8
  846P DTM02 N/A
  846P DTM03 N/A
  846P 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. Refer to ADC 1224. 13/13
  846P REF01 8X Transaction Category or Type Use to identify the specific transaction types for which transaction counts are being provided Use to identify the specific transaction types for which transaction counts are being provided in 2/QTY/320 (i.e., receipt, issue, inventory adjustment increase, inventory adjustment decrease, inventory adjustment dual and release confirmations). For Receipts (DLMS IC 527R with 1/BR02 Code D4); Issues (DLMS IC 867I); Inventory Adjustment-Increases (DLMS IC 947I with 2/W1916 Code AJ); Inventory Adjustment-Decreases (DLMS IC 947I with 2/W1916 Code AD); Inventory Adjustments-Dual (DLMS IC 947I with 2/W1916 Code DU) Cite the appropriate code in REF02 as follows: For Receipts, cite 527R in REF02. For Issues, cite 867I in REF02. For Inventory Adjustment Increases, cite 947IAJ in REF02. For Inventory Adjustment Decreases, cite 947IAD in REF02. For Inventory Adjustments Dual, cite 947IDU in REF02. For intra-Air Force use, USAF CICP also provides transaction count for non-accountable transactions: For Materiel Release Advice (DLMS 945A with 1/W0611 code NJ or NM); For Receipt Acknowledge (DLMS 527R with BR 02 Code TH or CJ. Cite the appropriate code in REF02 as follows: For Materiel Release Advice, cite 945A MRC/DRC in REF02. Refer to ADC 1228. For Receipt Acknowledgement, cite 527R MRA/TRA in REF02. Refer to ADC 1228. For intra-Navy use, Navy also provides transaction counts for non-accountable Asset Status Report transactions (DLMS IC 846I with BIA02 code TJ), cite 846I in REF02. Refer to ADC 320. 1/30
  846P REF01 DO Delivery Order Number Use to identify the Contract Delivery Order number For GFP, use delivery order number for contracts that have an A, G, or D in the 9th position. Please note that the delivery order numbers are required for contracts with A and G. 13/13
  846P REF01 FI File Identifier Use to indicate that the number of different types of accountable transactions is being reported Use with 1/BIA02/20 code B1. Use to indicate that the number of different types of accountable transactions is being reported in 2/QTY01-02/320. Enter �1� in REF02 for this purpose. 1/30
  846P REF01 L1 Letters or Notes Use to identify that End of Day Transaction Count transaction was generated by applications other than CAV II For Intra-Navy use only, Navy uses to identify that End of Day Transaction Count transaction was generated by applications other than CAV II. Navy cites �C� in REF02 to indicate non CAV II transactions. Navy uses with 1/BIA02/20 Code B1. Refer to ADC 320. 1/30
  846P 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 1. Use to identify the document number assigned by the materiel owner/manager as part of an physical inventory request. The storage activity must perpetuate the document number in the response when provided. Required for capital equipment candidates and UIT programs. Authorized DLMS enhancement for all other commodities. Refer to ADC 1244. 2. For Air Force GFP accountability, use to identify the document number assigned by the Air Force program manager in the accountable property system of record (APSR ). The CICP must perpetuate the document number to the response. Refer to ADC 1224. 3. DLMS enhancement; See introductory DLMS note 4a. 14/14
  846P REF02 N/A
  846P 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
  846P 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 DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 3/3
  846P LQ01 78 Project Code Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes 1. Enter the project code in LQ02 if stocks are segregated and maintained by project codes. 2. Future Streamlined data; see introductory DLMS note 4c. 3/3
  846P 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
  846P LQ01 84 Management Code Use to provide supplemental data not indicated through the transaction coding structure Use in physical inventory request, physical inventory report/response, to provide supplemental management information. 1/1
  846P LQ01 87 Subsistence Type of Pack Code Use to indicate the degree of protection to be provided subsistence items Use in physical inventory request and physical inventory response transactions. 1/1
  846P LQ01 99 Purpose Code Provides the owner of materiel with a means of identifying the purpose or reason for which an inventory balance is reserved 1. Enter the purpose code in LQ02 if stocks are segregated and maintained by purpose codes. 1/1
  846P LQ01 A1 Ownership Code Provides a means of segmenting inventory balances, accounted for in inventory control records of a Military Service/DLA, but which are owned by others 1. Enter the ownership code in LQ02 if stocks are segregated and maintained by ownership codes. 1/1
  846P 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. Future streamlined data; see introductory DLMS note 4c. 6/6
  846P 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 4a. 1/1
  846P LQ01 AK Distribution Code Use to identify the activity that will receive a supply status and other management data 1. Enter the distribution code in LQ02 if stocks are segregated and maintained by distribution codes. 2. Future Streamlined data; see introductory DLMS note 4c. 1/3
  846P LQ01 DF Media and Status Code Identifies the desired status recipient(s) and the type of status to be provided The DLMS provides the capability to carry additional status recipients beyond those identified by the DLSS. The Media and Status Code and the Distribution Code will be retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Additional status recipients identified here cannot be passed to DLSS users. 1/1
  846P LQ01 FC Type Physical Inventory or Transaction History Code Use to identify the specific reason, trigger, or context for Type Physical Inventory or Transaction History Code 1. For Physical Inventory Request Transaction, Response to Physical Inventory Request Transaction, and Transaction History Request (1/BIA02/20 Report Type Codes TC, DD, and TF respectively), cite appropriate code. 2. For Response to Transaction History Request (No History Available) (BIA02 Report Type Code AD), code value 8 or 9 is required; in addition, a second iteration of qualifier FC is used to perpetuate the code which appeared on the Transaction History Request or cite code W or Y (DLA only) for a utomatic submission of transaction history. Refer to ADC 198 and ADC 393. 1/1
  846P 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
  846P LQ01 COG Cognizance Symbol Use for internal Navy management purposes to classify items by technical program, type of fund, and to indicate the cognizant Inventory Control Point (ICP) and technically responsible command Use to identify the material cognizance symbol (COG) of the end item. Indicate NSL for non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2/2
  846P LQ01 IMC Item Management Code Use to indicate whether an item of supply shall be subject to integrated management or shall be retained by the individual military service or other DoD Component for their management Use for integrated material management. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 1/1
  846P LQ01 MCC Material Control Code Use to denote the expendability, repairability, recoverability, and cost category employed in the management of an item of supply within the Navy Use for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 1/1
  846P LQ01 SMI Special Material Identification Code Use to categorize material on the basis of requirements for source or quality control; technical design or configuration control; procurement, stocking, and issue control; special receipt, inspection, testing, storage, or handling Use for an end item. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2/2
  846P LQ02 N/A
  846P QTY01 02 Cumulative Quantity Use to identify the summary quantity for the transactions being reported For intra-Navy use only, Navy Commercial Asset Visibility (CAV) uses with 1/BIA02/20 code �B1-End of Day Transaction Count�, to identify the summary quantity for the transactions being reported. This equates to Navy DIC BZC, rp 7-11. Not used with intra-Navy BIA06 Action Code �ND�. Refer to ADC 320. 1/15
  846P QTY01 46 Total transactions Use to identify the total number of transactions or files Use with BIA02 code B1 End of Day Transaction Count and 2/REF01 code FI to indicate the total number of balance affecting transaction types being reported in this transaction. For the purpose of this transaction there are 5 possible transaction types for which end of day counts can be reported (receipts, issues, inventory adjustment increases, inventory adjustment decreases, and inventory adjustment dual.). Not used with intra-Navy BIA06 Action Code �ND�. 1/15
  846P QTY01 TT Total Production Volume A numerical value of the quantity of waste projected for turn-in annually Use with BIA02 code B1 End of Day Transaction Count to indicate the daily volume of balance affecting transactions applicable to the transaction category/type identified in 2/REF01/140 code 8X (e.g. if 36 receipt transactions are being reported, REF01 = 8X; REF02 = 527R; QTY01 = TT; QTY02 = 36.) Not used with intra-Navy BIA06 Action Code �ND�. 1/15
  846P QTY01 UU Used For BIA02 codes AD, DD, TC, DF, and BIA06 Action Code ND, use to comply with X12 syntax requirements. Cite �1� in QTY02. Do not use with BIA02 code B1 (except when B1 is used in conjunction with intra-Navy BIA06 Action Code �ND�). N/A
  846P QTY02 N/A
  846P QTY03 N/A
  846P QTY03-01 N/A
  846P N101 LG Location of Goods Use to identify the physical activity or facility where the material is currently stored, particularly when that location differs from the organization preparing the logistics transaction 1. Use to identify the physical location of GFP while in CICP custody. The location may be the CICP, the CICP�s warehouse or subcontractor. This location must be identified by DoDAAC. 2. Must use for Air Force GFP accountability. Refer to ADC 1224. 1/60
  846P N101 OW Owner of Property or Unit Use to identify the property owner, material owner or owning program manager 1. For Air Force GFP accountability, use to identify the Air Force program manager in the accountable property system of record (APSR). Refer to ADC 1224 2. For transactions directed to the APSR, must identify the program manager by RIC. If the program manager DoDAAC does not have an assigned RIC, use the generic Air Force GFP APSR RIC with 2/N106=TO and use a second iteration of the N1 loop (repeating Code OW without 2/N106=TO) to provide the program manager DoDAAC. 3. For transactions sent from the APSR using the generic Air Force GFP APSR RIC 1/N101/80 Code OW), use to identify the program manager DoDAAC. 1/60
  846P N101 SB Storage Area Use to identify the distribution depot/storage activity 1. Use to indicate the depot or storage activity. 2. For Air Force GFP accountability, use to identify the CICP as the responsible custodial activity. Refer to ADC 1224. 1/60
  846P 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
  846P N101 Z4 Owning Inventory Control Point Use to indicate the source of supply 1/60
  846P N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations 1. DLMS enhancement; see introductory DLMS note 4a. 2. Authorized for use by Air Force CICP to identify other organizations associated with the transaction by DODAAC. 6/6
  846P 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
Page 101  of  190 First   Previous   97  98  99  100  [101]  102  103  104  105  106  Next   Last