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
  846C 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
  846C N104
  846C N106 TO Message To Use to identify the party to receive the transaction set Must use in conjunction with 2/N101/4500 code SB or Z4 to identify that the organization cited in N104 is organization the transaction set is being sent to. 1/60
  846C SE01
  846C SE02
  846D ST01 846 Inventory Inquiry/Advice Organizations use this transaction to provide inventory information from one location to another and to inquire as to the availability of inventory. Use one occurrence of this transaction set to transmit a single or multiple transactions.
  846D ST02
  846D BIA01 00 Original Indicates the initial transaction
  846D 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 actions documents which affect accountable records.
  846D BIA02 TK Logistics Transfer Inquiry Use to identify an LR transfer/decapitalization inquiry. (MILSTRAP DIC DLA functionality.)
  846D BIA02 TL Logistics Transfer Advice Use to identify an LR transfer/decapitalization transaction. (MILSTRAP DIC DEE/DEF functionality.)
  846D BIA03
  846D BIA04
  846D BIA05
  846D BIA06 FI File 1. Authorized for Air Force contractor inventory control point (CICP) use to provide an image of the LR transfer/decapitalization transaction to the Air Force accountable property system record (APSR), only when the CICP is providing the APSR an image of a transaction that the CICP received from an external system. There will be no 2/N106/450 code TO for this transaction image. Refer to ADC 1232. 2. Authorized for DAAS use when DAAS creates an image for the Air Force APSR, of a transaction that the Air Force CICP sent to a GIM or LIM. DAAS creates the image when CICP sends an 846D transaction to an external system other than the APSR and includes 2/N101/450/ZD and 2/N106/450/PK. There will be no 2/N106/450 code TO for this transaction image. Refer to ADC 1232.
  846D 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 for LR transfer/decapitalization transactions. 1/60
  846D 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 LR transfer/decapitalization transactions. 1/60
  846D 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
  846D 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
  846D N104
  846D N106 FR Message From Use to identify the party originating the transaction set Must use with the appropriate 1/N101/080 code to indicate the organization cited in N104 is originating the transaction set. 1/60
  846D LIN02 FS National Stock Number A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification Use in LR transfer/decapitalization transactions. 13/13
  846D LIN03
  846D DTM01 007 Effective Use to identify the Effective Date Use to identify the Effective Transfer Date (ETD). 8/8
  846D DTM01 097 Transaction Creation Use to identify the date of transaction preparation 1. Use to identify the transaction preparation date. Correspond date to the Universal Time Coordinate (UTC). 2. Authorized DLMS enhancement; see introductory DLMS note 5e on IC cover page. 8/8
  846D DTM02
  846D DTM03
  846D CTP02 CON Contract Price Use to identify the contract unit price Use to identify the contract unit price for intra-DLA transactions when applicable IAW DLA procedures. Data required to accommodate a Component–unique requirement. 1/17
  846D CTP02 STA Standard Price Use to identify a predetermined price for a product or service 1. Use to cite the unit price in effect for valuing the inventory. 2. For transactions within a Service or Agency, this field may be left blank. 1/17
  846D CTP03
  846D REF01 43 Supporting Document Number Use to identify, track, and reference a document or transaction across various processes, including procurement, receipts, and maintenance 1. Must use to identify the document number from the associated receipt transaction when processing an LR transfer/decapitalization transaction for a nonprocurement source receipt processed after the ETD. Identifying the document number of the receipt establishes an audit trail between the receipt of the item and its subsequent transfer/decapitalization. 2. DLMS enhancement; see introductory DLMS note 5a. 1/30
  846D 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. The Air Force uses for Air Force GFP accountability transactions to identify the Procurement Instrument Identifier (PIID) applicable to the contract authorizing the Air Force CICP 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 this field. 3. Required for Air Force GFP accountability. 4. Authorized DLMS enhancement. Refer to ADC 1232. 13/13
  846D REF01 DO Delivery Order Number Use to identify the Contract Delivery Order number 1. Use in conjunction with the PIIN (Code 6L) for GFP-related transactions to identify the legacy four position call/order number associated with the PIIN applicable to the contract authorizing the contractor to have custody of GFP. 2. Do not use for the PIID call/order number. The PIID call/order number is mapped to Code 6L. 3. Authorized DLMS enhancement. Refer to ADC 1232.
  846D 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 controlling document number for this transaction. 14/14
  846D REF02
  846D CS01
  846D CS03
  846D CS04 83 Extended (or Exhibit) Line Item Number (ELIN) Use to identify the Exhibit Line Item Number (ELIN), or the ELIN including the Subcontract Exhibit Line Item Number (SUBELIN) Use to identify the Exhibit Line Item Number (ELIN), or the ELIN including the Subexhibit Line Item Number (SUBELIN), as appropriate. 4/4
  846D CS04 C7 Contract Line Item Number A number that identifies all items of supply or services in a contract Use to identify the Contract Line Item Number (CLIN), or the CLIN including the Subcontract Line Item Number (SUBCLIN), as appropriate. 4/6
  846D CS05
  846D 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.
  846D 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 5c. 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
  846D LQ01 78 Project Code Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes Army uses to identify the Project Code associated with LR actions. Use of this data is meaningful to Army only. In MILS, Army cites data in multiuse rp 57-59 of MILSTRAP DIC DEE and DEF. DLMS enhancement authorized for Army use. Other Components not using this data should ensure that inclusion of this data in a DLMS transaction does not cause inappropriate rejection of the transaction. For other than Army use, see introductory DLMS note 5a. 3/3
  846D LQ01 80 Advice Code Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action 1. Use when submitting a duplicate LR transfer/decapitalization transaction in response to an inquiry for LR transfer/decapitalization data. 2. DLMS enhancement. See introductory DLMS note 5a. 2/2
  846D LQ01 84 Management Code Provides supplemental data not indicated through the transaction coding structure Army uses for intra-Army LR to identify the Management Code associated with Logistics Reassignment actions. Use of this data is meaningful to Army only. Army cites data in multiuse rp 72 of MILSTRAP DIC DEE and DEF. DLMS enhancement authorized for Army use. Other Components not using this data should ensure that inclusion of this data in a DLMS transaction does not cause inappropriate rejection of the transaction. For other than Army use, see introductory DLMS note 5a. 1/1
  846D 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 5c. 6/6
  846D 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 5a. 1/1
  846D LQ01 AK Distribution Code Use to identify the activity that will receive a supply status and other management data 1. Use to identify the DLSS distribution code. 2. Future Streamlined data; see introductory DLMS note 5c. 1/3
  846D LQ02
  846D QTY01 78 Stock Transfers Out Use to identify the quantity for an Logistics Reassignment (LR) transfer transaction Use to identify the quantity for an LR transfer transaction. 1/15
Page 99  of  195 First   Previous   95  96  97  98  [99]  100  101  102  103  104  Next   Last