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
  824R PER07 EM Electronic Mail
  824R PER07 FX Facsimile
  824R PER07 TE Telephone Use to indicate the commercial telephone number of the party cited in PER02.
  824R PER07 WF Work Facsimile Number
  824R OTI01 IA Item Accept Use in conjunction with OTI02 = WPN to indicate acceptance of the HHMM/HW profile identified in OTI03.
  824R OTI01 TR Transaction Set Reject
  824R OTI02 CT Contract Number Use to identify the procurement instrument identifier (PID). Use the legacy procurement instrument identification number (PIN) pending transition to the PID. When procurement is authorized under a PID call/order number (F in 9th position), provide the value in the PID field. For Other Transaction (OT) agreements, the type of instrument (9th position of PID) will be a 3 for Research OTs or 9 for Prototype and Production OTs. Refer to ADC 1161A or ADC 1420.
  824R OTI02 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 document number.
  824R OTI02 WPN Waste Disposal Number Use on the HHMM/HW profile.
  824R REF01 0E Subject Property Reference Number Use to identify the assigned local stock number (LSN).
  824R REF01 17 Client Reporting Category Use to identify the specific purpose or function of a transaction Use to identify the Report Type Code (Data Element 75) from the Beginning Segment of the transaction being rejected, when applicable. A data maintenance action was approved in version 5050. The approved code/name is "X13 - Report Type Code ".
  824R 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 when used in the transaction being rejected. 2. DLMS enhancement; see introductory DLMS note 6a. 824R Reject Advice and.
  824R REF01 78 Planning Package Use to identify the Planning Schedule Type Code (Data Element 783) from the Beginning Segment of the transaction being rejected, when applicable. A data maintenance action was approved in version 5050. The approved code/name is "X10 - Planning Schedule Type Code". 83 - Extended (or Exhibit) Line Item Number (ELIN): Use to identify the ELIN associated with 2/OTI02/010 Code CT.
  824R REF01 8X Transaction Category or Type Use to identify the Inventory Transaction Type Code (Data Element 529) from the transaction being rejected, when DLMS 947I is being rejected. A data maintenance action was approved in version 5050. The approved code/name is "X12 - Inventory Transaction Type Code”.
  824R REF01 C7 Contract Line Item Number Use to identify the CLIN associated with 2/OTI02/010 Code CT.
  824R REF01 FQ Form Number A unique stock number associated with a specific Approved Code form 1. Use to identify the form stock number when used in the transaction being rejected. Enter the form number in REF03. Refer to ADC 1287. 2. DLMS enhancement; see introductory DLMS note 6a.
  824R REF01 MF Manufacturers Part Number A number assigned by a manufacturer to an item of production 1. Use for nonstandard materiel when used in the transaction being rejected. Enter the manufacturer’s part number in REF03. Refer to ADC 1287. 2. Authorized DLMS enhancement; see introductory DLMS Note 6e.
  824R REF01 NS National Stock Number Use NSN when used in the transaction being rejected.
  824R REF01 S6 Stock Number 1. Use to identify the publication stock number when used in the transaction being rejected. 2. DLMS enhancement; see introductory DLMS note 6a.
  824R REF01 SJ Set Number Use for the transaction being rejected to include the variant code when applicable (e.g., 527R).
  824R REF01 W8 Suffix Use to identify supply transaction partial actions taken on the original document without duplicating or causing loss of identity of the original document number Use to identify the suffix code associated with 2/OTI02/010 Code TN.
  824R REF01 WL Federal Supply Classification Code 1. Use for nonstandard materiel when used in the transaction being rejected. Use REF03 to provide the appropriate description. 2. DLMS enhancement; see introductory DLMS note 6a.
  824R REF01 X7 Batch Sequence Number Use to identify the batch control number from the beginning segment of the transaction being rejected, when DLMS 517M is being rejected.
  824R REF01 XD Subsistence Identification Number Use to identify a brand name resale subsistence item Use to identify subsistence items when used in the transaction being rejected. 824R Reject Advice and.
  824R REF01 ZZ Mutually Defined 1. Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be determined (includes management control numbers and locally assigned control numbers) when used in the transaction being rejected. 2. DLMS enhancement; see introductory DLMS note 6a.
  824R REF01 ACC Status Use to identify the current state, i.e. availability, condition, or progress Use to identify the Status Report Code (Data Element 850) from the Beginning Segment of the transaction being rejected, when applicable. A data maintenance action was approved in version 5050. The approved code/name is "X1 - Status Report Code ".
  824R REF01 PRT Product Type Use to identify the Schedule Type Qualifier (Data Element 675) from the Beginning Segment of the transaction being rejected, when applicable. A data maintenance action was approved in version 5040. The approved code/name is "X7 - Schedule Type Code".
  824R REF04-01 OQ Order Number 1. Use to identify the legacy four position call/order number associated with the CLIN in 2/REF01/020 Code C7. 2. Do not use for the PID call/order number. The PID call/order number is mapped to OTI02 Code CT. Refer to ADC 161.
  824R REF04-01 W7 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 1. Use with REF01 code MF to uniquely identify the manufacturer's part number when cited in the transaction being rejected. 2. Authorized DLMS enhancement; see introductory DLMS note 6e.
  824R DTM01 97 Transaction Creation
  824R NM101 Z4 Owning Inventory Control Point Use to indicate the source of supply For use with 2/LQ01/086 qualifier ET (Reject Advice Code), code value ‘AB’ (Rejected, submitted to incorrect manager), to identify the Correct manager.
  824R NM102 6 Organization
  824R NM108 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 DLMS enhancement; See introductory DLMS note 6a.
  824R NM108 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
  824R TED01 848 Incorrect Data Use to indicate that specific reject advice is conveyed under 2/LQ01/086. Qualifier ET.
  824R TED01 OTH Other 1. DLA Transaction Services uses to provide narrative message reject information. Use with the 2/NTE/080 segment 2. DLMS enhancement. See introductory DLMS note 6a.
  824R NTE01 OTH Other Instructions
  824R 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.
  824R 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. 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. 2. The DIC is not to be applicable to every rejection transaction. 3. May use 2 iterations of LQ01 code 0 when the rejected transaction contained an LQ01 code 0. Use one iteration with LQ02 code value DZG, when applicable, to represent DLMS 824R equated to MILSTRAP DIC DZG in a mixed DLS/DLMS environment. Use another iteration of LQ01 code 0 with the code value from the transaction being rejected when applicable. 4. Future Streamlined data; See introductory DLMS note 6c.
  824R LQ01 ET Reject Advice Code Use to identify reason original transaction was rejected.
  830D ST01 830 Planning Schedule with Release Capability
  830D BFR01 0 Original Indicates the initial transaction
  830D BFR01 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.
  830D BFR04 PR Planed Requirement Based Use to indicate that data reflect DE Projected Supply Plan requirements.
  830D BFR05 A Actual Discrete Quantities Use to indicate that quantities reflect discrete requirements.
  830D BFR12 AA Customized Ordering Forecast Must use to indicate the transaction is a DE Projected Supply Plan.
  830D BFR13 FI File Authorized only for DAS use to provide an information only image of the demand data exchange projected supply plan transaction to DLA RIC-TO SMS when DLA is not the source of supply.
  830D N101 41 Submitter Must use to identify the submitter of the DE requirement.
  830D 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 Use to identify the submitter.
  830D 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.
Page 44  of  141 First   Previous   40  41  42  43  [44]  45  46  47  48  49  Next   Last