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
  870S BSR11 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.
  870S BSR11 ZZ Mutually Defined 1. Use to identify the Unit of Use Indicator. When included, the quantity and unit of measure values associated with this transaction are applicable to the unit of use. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  870S N101 1Q Military Facility For intra-AF supply status for lateral movements, to identify the activity shipping the materiel and providing supply status.
  870S N101 GP Gateway Provider Use to identify the Routing Identifier of the Defense Automatic Addressing System (DAAS) as the intended recipient for distribution or posting to the historical record Use to indicate DLA Transaction Services is providing rerouting of status. 3/3
  870S N101 SB Storage Area Use to identify the distribution depot/storage activity 1. Use to identify the distribution center generating the supply status. 2. Used when providing Materiel Processing Center (MPC) status. 3. Use to identify the storage activity when the storage activity is the originator of the transaction implemented. This is applicable as a DLMS enhancement to allow specific separate identification of owner/manager and storage activity RIC for ammunition and ammunition related transactions. Refer to Approved Addendum to ADC 441A. 1/60
  870S N101 Z4 Owning Inventory Control Point Use to indicate the source of supply Use to indicate the source of supply furnishing status. 1/60
  870S N101 Z5 Management Control Activity A DoD Component, DoD activity, or non-DoD activity, if participating by separate agreement (e.g., the Coast Guard), designated to receive, screen, and validate Military Service-initiated and contractor- initiated requisitions from the wholesale supply system to support DoD contracts or requirements Use to identify the MCA furnishing the status. 1/60
  870S N101 ZS Monitoring Party Use to identify the International Logistics Control Office (ILCO) Use to identify the International Logistics Control Office furnishing the status. 1/60
  870S N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations 6/6
  870S 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
  870S N104
  870S N106 FR Message From Use to identify the party originating the transaction set Must use with the appropriate 1/N101/050 code to indicate the organization cited in N104 is originating the transaction set. 1/60
  870S HL01
  870S HL03 W Transaction Reference Number Use to identify the individual transaction supply status loops.
  870S DTM01 097 Transaction Creation Use to identify the date of transaction preparation Use to indicate the date of transaction preparation. 8/8
  870S DTM02 N/A
  870S CS01
  870S CS02
  870S CS03
  870S 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 ELIN, or the ELIN including the Sub Exhibit Line Item Number (SUBELIN), as appropriate. 4/4
  870S CS04 C7 Contract Line Item Number A number that identifies all items of supply or services in a contract Use to identify the CLIN, or the CLIN including the Sub Contract Line Item Number (SUBCLIN), as appropriate. 4/6
  870S CS05
  870S CS07 AD Accept at Destination
  870S CS07 AO Accept at Origin
  870S CS07 ZZ Mutually Defined Use ZZ to indicate Acceptance by Other when destination acceptance shall be performed by an activity other than the ship-to activity.
  870S CS09
  870S CS10
  870S CS11
  870S CS13 IM Inspect at Destination Use when origin inspection does not apply and inspection requirements shall be satisfied by the ship-to activity.
  870S CS13 IO Inspect at Origin
  870S CS13 G0052 Government Inspection Use code G0052 to indicate Inspection Performed by Other when origin inspection does not apply and inspection requirements shall be satisfied by an activity other than the ship-to activity.
  870S CS14
  870S CS15
  870S CS17 N No
  870S CS17 Y Yes
  870S CS18 N No
  870S CS18 Y Yes
  870S REF01 43 Supporting Document Number Use to identify, track, and reference a document or transaction across various processes, including procurement, receipts, and maintenance Used to perpetuate/convey a Supporting Maintenance Document Number as necessary. The content in this field may only be meaningful to the receiver of this transaction. May be used to convey maintenance control/document numbers. 1/30
  870S REF01 86 Operation Number Use to identify a discrete, sequenced task or step within a larger Job Order (JO) that must be completed to achieve a specific mission objective 1. Use to identify the Key Operation (KO) Number associated with the JO. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 1/30
  870S REF01 9R Job Order Number Use to identify Job Order (JO) Number Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 1/50
  870S REF01 CO Customer Order Number Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 1. Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381 (or as applicable). 5/5
  870S REF01 FG Fund Identification Number Use to identify the fund purpose code. Describes the purpose or intended use of funds or financial accounting classification data identified on DLMS transactions Use to identify the fund purpose code. Cite any fund purpose code in REF02 except CR or DR. 2/2
  870S 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 1. Must use to identify the customer assigned transaction number. 2. This is the document number. 3. When status is applicable to a requisition alert, this field will perpetuate the alert document number. The requisition alert is an Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 14/14
  870S REF01 WO Work Order Number Number assigned by a maintenance facility identifying the repair requirement 1. Use to identify a maintenance work order number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 379 1/30
  870S REF01 BDG Badge Number Use with local industrial activity worksite delivery status of the artisan to whom the materiel was delivered. Refer to ADC 379
  870S REF01 PWC Preliminary Work Candidate Number Used for preliminary notification that an order for material (requisition) is being prepared for future submission to a supply source Applicable for DLA industrial activity support agreements 1. Use to identify a Requisition Alert Document Number. 2. Used in support of Navy Shipyards to associate the funded requisition with a previously submitted requisition alert. 3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 15/15
  870S REF01 X17 General Terms and Conditions Identifier 1. Use to identify the Fiscal Service (FS) Form 7600A General Terms and Conditions (GT& C) number when taking on an order from a government customer covered by a G-Invoicing agreement. Refer to PDC 1465B. 2. DLMS enhancement; see introductory DLMS note 3a. 3. Approved for use in X12 version 8060.
  870S REF02
  870S REF03
  870S REF04
Page 160  of  195 First   Previous   156  157  158  159  [160]  161  162  163  164  165  Next   Last