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
  517G FA102 A170 Adjustments Use only for adjustments not specified by any other code Use only for adjustments not specified by any other code.
  517G FA102 A520 Base Charge Use for materiel charges only Use for materiel charges only.
  517G FA102 C930 Export Shipping Charge Charge for goods or services transferred across national borders
  517G FA102 D340 Goods and Services Charge Use for both materiels and related services Use for both materiel and related services.
  517G FA102 F060 Other Accessorial Service Charge Use for accessorial costs
  517G FA102 F560 Premium Transportation Use for expedited or high-security shipping methods that are faster and more expensive than standard transport
  517G FA102 I260 Transportation Direct Billing Use for non-premium or credit for transportation Use for non-premium transportation.
  517G FA102 R060 Packing, Crating, and Handling Charge Use for costs associated with preparing and securing goods for shipment, including labor, materials, and the expenses of order fulfillment
  517G FA201 B5 Fund Code Designation of the billing method (interfund or non-interfund) and the fund account to be charged (disbursed) or credited (refunded)
  517M ST01 517 Material Obligation Validation
  517M BR01 0 Original Indicates the initial transaction
  517M BR01 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.
  517M BR02 AN Material Obligation Inquiry Use alone to indicate an original MOV request. Also may use with BR06 codes A3 and RU and T.
  517M BR02 AP Material Obligation Advice 1. Use to indicate the transaction set contains MOV response transactions. 2. Use with BR06 Code 9 to identify organization(s) exempt from the current MOV cycle. 3. Use with BR06 Code V to confirm receipt of MOV request(s). 4. Use with BR06 Code 51 to indicate that all MOV requests requiring changes are considered complete and verified as valid.
  517M BR02 AQ Quantity Verification Inquiry Use to indicate the transaction set contains excessive quantity verification inquiry transactions.
  517M BR02 AV Quantity Verification Advice Use to indicate the transaction set contains excessive quantity verification response transactions.
  517M BR02 AW Material Obligation Reinstatement Use to indicate the transaction set contains MOV reinstatement requests.
  517M BR06 9 Not Capable of Taking Action Use with BR02 Code AP to indicate the organizations specified in the 1/N1/060 loop are exempt from the current MOV reporting cycle.
  517M BR06 T Status Query Use with BR02 code AN to indicate a follow-up to an original MOV. V - Respond: Use with BR02 Code AP to indicate the transaction set is a confirmation of receipt of MOV requests.
  517M BR06 51 Complete Use with BR02 Code AP to indicate all MOV requests requiring changes are considered and verified as valid.
  517M BR06 A3 Not Certified Use with BR02 Code AN to indicate the organization, specified in the 1/N1/060 loop, failed to provide an MOV response for materiel scheduled for direct delivery from procurement.
  517M BR06 RU Return Use with BR02 code AN to indicate customer nonresponse to MOV requests for backordered materiel in preaward (BZ) status.
  517M BR07 X7 Batch Sequence Number 1. Use to identify the batch control number assigned to each batch of transactions forwarded to a single activity for validation. The first two positions will contain the batch number and the second two positions will contain the total number of batches being forwarded. 2. Future streamlined data; see introductory DLMS note 3c.
  517M BR10 XM Issuer Number 1. Use to identify the actual number of individual detail transactions included in this batch from 01 to 493 maximum. 2. Future streamlined data; see introductory DLMS note 3c.
  517M G6201 64 Must Respond By Use in quantity verification inquiries to indicate the response due date.
  517M G6201 BS Product Receipt Date Use in MOV responses to indicate date of receipt of MOV requests.
  517M G6201 CA Cutoff Date Use for MOV requests to identify the last date of record against which the open orders were obtained from the supply source's records.
  517M 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.
  517M 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 MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. (Applicable only to DIC AP8 and AP9). 2. Future streamlined data; see introductory DLMS note 3c.
  517M LQ01 AK Distribution Code Use to identify the distribution of the MOV transaction set.
  517M LQ01 COG Cognizance Symbol Use for internal Navy management purposes to classify items by technical program, type of fund, and to indicate the cognizant Inventory Control Point (ICP) and technically responsible command Use to identify the material cognizance symbol (COG) of the end item. Indicate NSL for non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.
  517M N101 97 Party Waiving Requirements Use multiple iterations for MOV exemption transactions to identify those organizations exempt from the current MOV cycle.
  517M N101 BG Buying Group Use to identify the G-Invoicing Group Name Description 1. Use to identify the G-Invoicing Group Name Description. Refer ADC 1465. 2. DLMS enhancement; see introductory DLMS note 3a.
  517M N101 BT Bill-to-Party 1. Use for SFIS compliant systems to identify the BPN of the party to receive the bill. BPN may only be used when the corresponding DODAAC is also provided. This will require a second iteration of the N1 loop with the same qualifier. 2. Authorized DLMS enhancement; see introductory DLMS note 3f.
  517M N101 PK Party to Receive Copy
  517M N101 Z4 Owning Inventory Control Point Use to indicate the source of supply
  517M N101 ZK Reporter Use to identify the organization accomplishing actions on behalf of the customer.
  517M N101 ZR Validating Party
  517M 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 DLMS enhancement; see introductory DLMS note 3a.
  517M N103 50 Business License Number Use to identify buying or selling entities processing intragovernmental transactions 1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the buyer’s BPN in N104. 2. Authorized DLMS enhancement; see introductory DLMS note 3f.
  517M 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) 1. Use to indicate the Security Assistance (SA) structured address data. Interpretation of this data may require additional codes cited elsewhere in the transaction. 2. DLMS enhancement; see introductory DLMS note 3a.
  517M 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
  517M N106 FR Message From Use to identify the party originating the transaction set Use with the appropriate 1/N101/060 code to indicate that the organization cited in N104 is originating the transaction set.
  517M N106 TO Message To Use to identify the party to receive the transaction set Use with the appropriate 1/N101/060 code to indicate that the organization cited in N104 is the action organization receiving the transaction set.
  517M G6101 IC Information Contact Must use in the first repetition to identify the primary POC and their primary communication number.
  517M G6103 AU Defense Switched Network
  517M G6103 EM Electronic Mail
  517M G6103 EX Telephone Extension Use in a repetition immediately following AU, IT, or TE to identify a telephone extension.
  517M G6103 FX Facsimile
  517M G6103 IT International Telephone Include country and city code.
Page 16  of  141 First   Previous   12  13  14  15  [16]  17  18  19  20  21  Next   Last