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
  830D FST01
  830D FST02 D Planning Use in conjunction with DDE Submission transactions (2/LIN01/0100 Code H- Submission)
  830D FST02 W Cancellation Use in conjunction with DDE Cancellation transactions (2/LIN01/0100 Code C - Cancelled)
  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) Use to indicate quantities are reflected in monthly increments 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 DDE projected supply plans can be as short as 12 months, DLA recommends that DDE projected supply plans have 60 months plan periods, citing a 0 ( zero) for months with no plan. 8/8
  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.
  830D FST04
  830D SDQ01
  830D SDQ03
  830D SDQ04
  830D SE01
  830D SE02
  830R ST01 830 Planning Schedule with Release Capability Organizations use this transaction set to transmit Special Program Requirements (SPRs) to Inventory Control Points (ICPs)/Integrated Material Managers (IMMs). In using this transaction set, use a single occurrence of this transaction set to transmit SPR transactions to one or more ICPs/IMMs. This transaction encompasses the functionality of MILSTRAP Document Identifier Codes (DIC) DYA, DYB, DYC, DYD, DYG, DYH, DYJ, DYL, and DYM. Additionally, use one occurrence of this transaction set to transmit a single or multiple transactions.
  830R ST02
  830R BFR01 00 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 BFR02
  830R BFR04 PR Planned Requirement Based Use to indicate requirements data reflecting planned program requirement projections not based on historical demand.
  830R BFR05 A Actual Discrete Quantities Use to indicate that quantities reflect discrete requirements.
  830R BFR06
  830R BFR07
  830R BFR08
  830R BFR12 XA Requirement Forecast Must use to indicate the transaction is an SPR forecast.
  830R BFR13 OT Other Unlisted Action Exception Data. Use only with 2/LIN01/010 codes “A” and “B”. Use only when exception data is to be provided. (Associated with MILSTRAP DIC DYB functionality when used with LIN01 code “A”. Associated with DIC DYM functionality when used with LIN01 code “B”.)
  830R N101 41 Submitter Use to identify participating activity which submits proposed data directly to the DLA logistics information service for approval. The submitting activity may be the activity which originates the data, or an intermediate monitoring activity, e.g., DLA supply center, defense atomic support agency, through which the originating activity is required to submit its proposals to DLA logistics information service
  830R N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations DLMS enhancement; see DLMS introductory note 4a. 6/6
  830R 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
  830R N104
  830R 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. 1/60
  830R LIN01
  830R LIN02 A2 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. 2. DLMS enhancement; see DLMS introductory note 4a. 4/4
  830R LIN02 A4 Subsistence Identification Number Use to identify a brand name resale subsistence item 15/15
  830R LIN02 F4 Series Identifier Use to identify the manufacturer's series number of the applicable end item Use to identify the manufacturer's series number of the end item. 1/48
  830R LIN02 FB Form Number A unique stock number associated with a specific Approved Code form 1. Use to identify the form stock number. 2. DLMS enhancement; see DLMS introductory note 4a. 1/30
  830R LIN02 FS National Stock Number A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification 13/13
  830R LIN02 MG Manufacturer's Part Number A number assigned by a manufacturer to an item of production 1. Use to identify nonstandard materiel. 2. DLMS enhancement; see DLMS introductory note 4a. 1/48
  830R LIN02 MN Model Number Use as a second level identifier assigned by a manufacturer which identifies one of several types of a basic equipment Use to identify the manufacturer's model number of the end item. 15/15
  830R LIN02 SN Serial Number A value assigned for identification of an item Use to identify the manufacturer's serial number of the end item. 1/50
  830R LIN02 TP Product Type Code For clothing and footwear, use to identify the NSN when the materiel requested represents a generic requirement for which the quantity should be distributed across a predefined range of sizes For clothing and footwear, use to identify the NSN when the materiel requested represents a generic requirement for which the quantity should be distributed across a predefined range of sizes. 13/13
  830R LIN02 YP Publication Number Reference number assigned to a publication or catalog 1. Use to identify the publication stock number. 2. DLMS enhancement; see DLMS introductory note 4a. 1/48
  830R LIN03
  830R 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 1. Use with LIN02 code MG to uniquely identify a manufacturer's part number. 2. DLMS enhancement; see DLMS introductory note 4a. 5/5
  830R LIN05
  830R PWK01 R6 Miscellaneous Information Use to indicate that additional information is being submitted to the action activity 1/80
  830R PWK07
  830R 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 This is the document number. 14/14
  830R REF02
  830R N101 KA Item Manager Use to indicate the government inventory manager Must use to identify the ICP/IMM. 1/60
  830R N101 P1 Preparer Use to identify the originator of the Special Program Requirements (SPR) when different from the submitting activity identified Use to identify the originator of the SPR when different from the submitting activity identified by 1/N101/230 code 41. 1/60
Page 61  of  195 First   Previous   57  58  59  60  [61]  62  63  64  65  66  Next   Last