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
  846P LIN04 SW Stock Number 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.
  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.
  846P DTM01 90 Report Start 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.).
  846P DTM01 91 Report End 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.).
  846P DTM01 97 Transaction Creation Use to identify the date the transaction was prepared.
  846P DTM01 197 End Use to identify the Physical Inventory Cutoff Date (PICD).
  846P DTM01 501 Expected Reply 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 124. 2. DLMS enhancement; See introductory DLMS note 4a.
  846P REF01 6L Agent Contract Number 1. Use in GFP-related transactions to identify the procurement instrument identifier (PID) applicable to the contract authorizing the contractor to have custody of GFP. Use the legacy procurement instrument identification number (PIN) pending transition to the PID. 2. If GFP is authorized under a PID call/order number (F in 9th position), provide the PID call/order number in the PID field. 3. Required for Air Force GFP accountability to identify the CICP’s contract number. 4. Authorized DLMS enhancement. Refer to ADC 124.
  846P REF01 8X Transaction Category or Type 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/W061 code NJ or NM); For Receipt Acknowledge (DLMS 527R with BR02 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 128. For Receipt Acknowledgement, cite 527R MRA/TRA in REF02. Refer to ADC 128. 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.
  846P REF01 DO Delivery Order Number 1. Use in conjunction with the PIN (Code 6L) for GFP-related transactions to identify the legacy four position call/order number associated with the PIN applicable to the contract authorizing the contractor to have custody of GFP. 2. Do not use for the PID call/order number. The PID call/order number is mapped to Code 6L. 3. Authorized DLMS enhancement; see introductory DLMS note 4e. on IC cover page. Refer to ADC 124.
  846P REF01 FI File Identifier 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.
  846P REF01 L1 Letters or Notes For Intra-Navy use only, Navy uses to identify that End of Day Transaction Count transaction was generated by applications other than CAV I. Navy cites ‘C’ in REF02 to indicate non CAV I transactions. Navy uses with 1/BIA02/20 Code B1. Refer to ADC 320.
  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 124. 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 124. 3. DLMS enhancement; See introductory DLMS note 4a.
  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.
  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 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.
  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.
  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
  846P LQ01 84 Management Code Use in physical inventory request, physical inventory report/response, to provide supplemental management information.
  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.
  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.
  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.
  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.
  846P 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.
  846P LQ01 AK Distribution Code 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.
  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 DLS. The Media and Status Code and the Distribution Code will be retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Additional status recipients identified here cannot be passed to DLS users.
  846P LQ01 FC 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, D, 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 automatic submission of transaction history. Refer to ADC 198 and ADC 393.
  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) Use to identify the Material Management Aggregation Code (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.
  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.
  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.
  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.
  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.
  846P QTY01 2 Cumulative Quantity 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-1. Not used with intra-Navy BIA06 Action Code ‘ND’. Refer to ADC 320.
  846P QTY01 46 Total transactions 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’.
  846P QTY01 TT Total Production Volume 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 = T; QTY02 = 36.) Not used with intra-Navy BIA06 Action Code ‘ND’.
  846P QTY01 UU Used For BIA02 codes AD, D, 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’).
  846P N101 LG Location of Goods 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 124.
  846P N101 OW Owner of Property or Unit 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 124 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.
  846P N101 SB Storage Area 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 124.
  846P 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.
  846P N101 Z4 Owning Inventory Control Point Use to indicate the source of supply
  846P 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 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.
  846P 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.
  846P 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
  846P N106 TO Message To Use to identify the party to receive the transaction set Must use with the appropriate 2/N101/450 code to indicate the organization cited in N104 is receiving the transaction.
  846R ST01 846 Inventory Inquiry/Advice
  846R BIA01 0 Original Indicates the initial transaction
  846R BIA01 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.
  846R BIA01 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.
  846R BIA02 LC Location Inventory Report Use to identify a Location Reconciliation Request Transaction. From distribution center/storage activity to the owner/manger to reconcile storage activity and owner/manager records. (MILSTRAP DIC DZH functionality.).
  846R BIA02 X4 Summary Report Use to identify a Location Reconciliation Notification Transaction. Distribution center/storage activity sends to owner/manager to advise of the number of Location Reconciliation Request transactions being forwarded. (MILSTRAP DIC DZN functionality.).
Page 77  of  141 First   Previous   73  74  75  76  [77]  78  79  80  81  82  Next   Last