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 REFSorted by ascending CODE X12 CODE NAME GENERAL CODE DEFINITION CODE DLMS NOTE DLMS MIN MAX
  947I FA201 L1 Accounting Installation Number Use to indicate the Authorization Accounting Authority (AAA)/Accounting and Disbursing Station Number (ADSN)/Fiscal Station Number (FSN) Use to indicate the Authorization Accounting Authority (AAA)/Accounting and Disbursing Station Number (ADSN)/Fiscal Station Number (FSN). 6/6
  180M FA202
  511M FA202
  511R FA202
  517G FA202
  517M FA202
  527D FA202
  527R FA202
  810L FA202
  810L FA202
  812L FA202
  812R FA202
  842AR FA202
  842SR FA202
  867D FA202
  867I FA202
  869A FA202
  869C FA202
  869F FA202
  940R FA202
  945A FA202
  947I FA202
  856P FOB01 DF Defined by Buyer and Seller
  856P FOB02 DE Destination (Shipping) Use to indicate the transportation responsibility shipping destination 1/80
  856P FOB02 IT Intermediate FOB Point The acceptance point address 1/80
  856P FOB02 OR Origin (Shipping Point) Use to identify the location where the seller hands off goods to a carrier and the buyer assumes responsibility for them 1/80
  830D FST01
  830R FST01
  830W 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)
  830R FST02 D Planning Use only for SPR, SPR SA, SPR substitute acceptance, SPR substitute rejection, and SPR inquiry transactions.
  830R FST02 W Cancellation Use only for SPR cancellation transactions.
  830R FST02 X Modification Use only for SPR modification transactions.
  830W FST02 D Planning Use for all Other War Reserve Materiel Requirements (OWMR), repairable return, and Pre-positioned War Reserve Materiel Requirements (PWRMR) (non-protected) transactions to indicate the requirement reflects a planning requirement forecast.
  830W FST02 S Strike Protection Use for all PWRMR (protected) transactions to indicate the requirement reflects a protected requirement forecast.
  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.
  830R FST03 D Discrete Use to indicate all forecast quantities are discrete quantities.
  830W FST03 M Monthly Bucket (Calendar Months) Use to indicate quantities are reflected in monthly increments Use to indicate quantities are reflected in monthly increments. 8/8
  830D FST04 N/A
  830R FST04 N/A
  830W FST04 N/A
  830R FST08 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 1. Use to identify the suffix code associated with the 2/REF/140 transaction number and quantity. 2. Future Streamlined data; see DLMS introductory note 4c. 1/1
  830R FST09
  888M G3901
  888N G3901
  888I G3902 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 introductory DLMS note 4a. 4/4
Page 35  of  195 First   Previous   31  32  33  34  [35]  36  37  38  39  40  Next   Last