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
  830D LIN02 FS National Stock Number A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification
  830D LIN02 SW Stock Number Use to identify a local stock number (LSN).
  830D LIN02 ZZ Mutually Defined Use to identify the National Item Identification Number (NIIN) for Demand Data Exchange transactions. A - data maintenance action was approved in version 5020. The approved code/name is "N - National Item Identification Number".
  830D PWK01 R6 Miscellaneous Information
  830D REF01 FG Fund Identification Number For Navy, this is a Program Funding Indicator associated to a Gross Demand Plan (GDP). See ADC 1267.
  830D 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 transaction document number.
  830D PER01 IC Information Contact Use to identify the point of contact.
  830D PER03 AU Defense Switched Network
  830D PER03 EM Electronic Mail
  830D PER03 EX Telephone Extension Use immediately following codes AU, IT or TE to identify a telephone extension.
  830D PER03 FX Facsimile Demand Data Exchange (DE) Projected Supply Plan
  830D PER03 IT International Telephone Include country and city code.
  830D PER03 TE Telephone
  830D PER03 WF Work Facsimile Number
  830D PER05 AU Defense Switched Network
  830D PER05 EM Electronic Mail
  830D PER05 EX Telephone Extension Use immediately following codes AU, IT or TE to identify a telephone extension.
  830D PER05 FX Facsimile
  830D PER05 IT International Telephone Include country and city code.
  830D PER05 TE Telephone
  830D PER05 WF Work Facsimile Number
  830D PER07 AU Defense Switched Network
  830D PER07 EM Electronic Mail
  830D PER07 EX Telephone Extension Use immediately following codes AU, IT or TE to identify a telephone extension. Demand Data Exchange (DE) Projected Supply Plan.
  830D PER07 FX Facsimile
  830D PER07 IT International Telephone Include country and city code.
  830D PER07 TE Telephone
  830D PER07 WF Work Facsimile Number
  830D N101 KA Item Manager Must use to identify the ICP/IM.
  830D N101 LW Customer Use to identify the requisitioner (Sold-to) DODAAC for DE Projected Supply Plan transactions. This is the DODAAC of the requisitioning (customer) organization. The requisitioner (Sold-to) DODAAC is found in the first six positions of a requisition document number. In many cases the requisitioner (Sold-to) DODAAC and the Ship-to DODAAC will be the same in the transaction.
  830D N101 ST Ship To Must use to identify the Ship-to DODAAC. In many cases the requisitioner (Sold-to) DODAAC and Ship-to DODAAC will be the same in the transaction.
  830D 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.
  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 with N101 codes LW and ST.
  830D 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.
  830D N103 A2 Military Assistance Program Address Code (MAPAC) Use to identify the consignee in transportation documents and to obtain clear-text address and other shipment information from the military assistance program address directory (MAPAD) Use to indicate the Security Assistance structured address data.
  830D 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 1. Use with existing code KA. 2. Use RIC-TO SGA when the item manager (source of supply) is unknown.
  830D N106 TO Message To Use to identify the party to receive the transaction set Must use with 2/N101/320 code KA to identify the organization cited in N104 is receiving the transaction.
  830D 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.
  830D LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data Use “CD” to indicate the data reflects DE Projected Supply Plan requirements. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
  830D LQ01 ZZ Mutually Defined 1. Use with DE Projected Supply Plan transactions to identify the planning code. 2. Planning Code is optional data that the customer may use as they determine is needed. Planning Code is an intra-Component, five-position code, which is under development by the Services. Accordingly, although the data will be meaningful to the customer and will be visible to customers in the Collaborate web toll, it won’t neccessarily be meaningful to DLA or the other Services. A - data maintenance action was approved in version 5030. The approved code/name is "PCL - Planning Code Lookup".
  830D FST02 D Planning Use in conjunction with DE Submission transactions (2/LIN01/010 Code H- Submission).
  830D FST02 W Cancelation Use in conjunction with DE Cancelation transactions (2/LIN01/010 Code C - Canceled).
  830D FST03 A Annually (Calendar Year) Use to submit up to 5 years (5 annual periods) of projected supply plan data. (e.g., for a 5 year projection, 5 annual periods will be submitted, to include zero entries for plan years with no data; for a 4 year projection, 4 annual periods will be submitted, etc.). The beginning segment defines the projected supply plan period start and end dates (BFR06 and BFR07 respectively). The annual buckets must be provided in chronological sequence in the transaction and zero quantity projections must be included. Use of “Annually” is a DLMS enhancement. See introductory DLMS note 4a.
  830D FST03 M Monthly Bucket (Calendar Months) 1. Use to submit up to 5 years (60 months) of projected supply plan data. (e.g., for a 5 year projection, 60 monthly buckets will be submitted, to include zero entries for plan months with no data; for a 3 year projection, 36 monthly buckets will be submitted, to include zero entries, etc.). The beginning segment defines the projected supply plan period start and end dates (BFR06 and BFR07 respectively). The monthly buckets must be provided in chronological sequence in the transaction and must include zero quantity projections. 2. While DE projected supply plans can be as short as 12 months, DLA recommends that DE projected supply plans have 60 months plan periods, citing a 0 ( zero) for months with no plan.
  830D FST03 Q Quarterly (Calendar Quarters) Use to submit up to 5 years (20 quarters) of projected supply plan data. (e.g., for a 5 year projection, 20 quarters will be submitted, to include zero entries for plan quarters with no data; for a 4 year projection, 16 quarters will be submitted, etc.). The beginning segment defines the projected supply plan period start and end dates (BFR06 and BFR07 respectively). The quarterly buckets must be provided in chronological sequence in the transaction and zero quantity projections must be included. Use of “Quarterly” is a DLMS enhancement. See introductory DLMS note 4a.
  830D FST03 S Semi-Annually (Calendar Year) Use to submit up to 5 years (10 semi-annual periods) of projected supply plan data (e.g., for a 5 year projection, 10 semi-annual periods will be submitted, to include zero entries for semi-annual plan periods with no plan data; for a 3 year projection, 6 semi-annual periods will be submitted, etc.). The beginning segment defines the projected supply plan period start and end dates (BFR06 and BFR07 respectively). The semi-annual buckets must be provided in chronological sequence in the transaction and zero quantity projections must be included. Use of “Semi-Annually” is a DLMS enhancement. See introductory DLMS note 4a.
  830R ST01 830 Planning Schedule with Release Capability
  830R BFR01 0 Original Indicates the initial transaction
  830R 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.
  830R BFR04 PR Planed Requirement Based Use to indicate requirements data reflecting planed program requirement projections not based on historical demand.
Page 45  of  141 First   Previous   41  42  43  44  [45]  46  47  48  49  50  Next   Last