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
  511M LQ01 A6 Freight Forwarder Number Must use in FMS transactions to modify, or in the case of an unmatched modification, use to identify the country representative or freight forwarder to receive shipments and documentation.
  511M LQ01 A7 Record Control Number Must use in MAP/GA transactions to identify the program line item number.
  511M LQ01 A8 Program Year Code Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was approved and funded.
  511M LQ01 A9 Supplemental Data A distinctive identification of specific units, activities and organizations within the Department of Defense (DoD), commercial activities which enter into materiel and service contracts with the DoD and activities of other Federal agencies which maintain logistics support arrangements with the DoD 1. Use to identify, or to modify, supplementary address/supplemental data. 2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the MILSTRIP Supplementary Address (SUPAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 3d. 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 3a. 4. Under full DLMS, the requirement to pass activity address information within the supplemental data field will be streamlined. Activity address data previously contained in the SUPAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c. 5. During legacy MILSTRIP/DLMS transition, use on a referral order modification to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel and no billing. Cite Signal Code M and Project Code CYK in conjunction with the supplemental data field constructed as follows: Service/Agency Code Y followed by the old (from) ownership code, the RIC to which ownership is transferred, and the new/gaining (to) ownership code. Refer to ADC 1020.
  511M LQ01 AJ Utilization Code Use to identify a specialized purpose of the transaction 1. Use to identify a specialized purpose for which the requisition is submitted. 2. Under legacy MILSTRIP, this is the first position of the document serial number within the document number. 3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 4. DLMS enhancement; see introductory DLMS note.
  511M LQ01 AK Distribution Code 1. Use to modify, or in the case of an unmatched modification, use to identify the distribution code. Modifier transactions may not be used to change this field for Government Furnished Materiel (GFM) requisitions. 2. Future streamlined data; see introductory DLMS note 3c.
  511M LQ01 AL Special Requirements Code Use to identify precedence, special handling, and processing requirements 1. Under legacy MILSTRIP, this is caried in the required delivery date field. 2. DLMS enhancement; see introductory DLMS note 3a. 3. Use in conjunction with 2/LQ01/Code RC, Requirement Code, to complete the Air Force unique NMCS/MICAP data requirement.
  511M LQ01 BD Transportation Priority Code 1. Use to identify a transportation priority which is different than that associated with the requisition priority. 2. DLMS enhancement; see introductory DLMS note 3a.
  511M LQ01 DE Signal Code Use to indicate the bill-to and ship-to DoDAAC (Department of Defense Activity Address Code) for an item 1. Use to modify, or in the case of an unmatched modification, use to identify the signal code. Modifier transactions may not be used to change this field for Government Furnished Materiel (GFM) requisitions. 2. Future streamlined data; see introductory DLMS note 3c.
  511M LQ01 DF Media and Status Code Identifies the desired status recipient(s) and the type of status to be provided 1. Use to modify, or in the case of an unmatched modification, use to identify the media and status code. Modifier transactions may not be used to change this field for Government Furnished Materiel (GFM) requisitions. 2. Future streamlined data; see introductory DLMS note 3c.
  511M LQ01 DJ Remedial Action Code Use to indicate the actions required by the receiving system in order to accurately process transactions and direct the types of follow-on actions authorized to occur Use temporary qualifier DJ - Remedial Action Code to identify Army Edit Action Code indicating the actions required by the receiving system in order to accurately process transactions and direct the types of follow-on actions authorized to occur. This is an Army unique data element, and is meaningful to the Army only. The code source is identified as the U.S. Army Materiel Command Single Stock Fund Functional User Manual, 3rd Edition. An ANSI data maintenance request has been prepared to establish a new data element 1270 code qualifier assignment for Army Edit Action Code.
  511M LQ01 GQ Group Qualifier Code Use to identify the Materiel Management Aggregation Code (MMAC) for National Stock Number (NSN) to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group) Use to identify the Materiel Management Aggregation Code (MAC) for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. A - data maintenance action was approved in version 5010. The approved code/name is "MAC - Material Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN) 23-10, Volumes 1 and 2.
  511M LQ01 KJ Assured Delivery Indicator Use to communicate special processing and/or priority requirements 1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an urgency of need within the maintenance shop and must be delivered within one hour of receipt of the issue request. Value will be X (1 hour issue) when applicable. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 3. A data maintenance action was approved in version 5030. The approved code/name is DPC - Delivery Priority Code. DoD systems will continue to use Qualifier KJ to represent the Delivery Priority/Special Processing Code until such time as a new ADC directs otherwise.
  511M LQ01 RC Requirement Code Use to identify the urgency of need and type of requirement (justification) related to a not mission capable supply/mission impaired capability awaiting parts condition 1. Use to identify the Air Force Urgency Justification Code indicating the urgency of need and type of requirement (justification) related to a Not Mission Capable Supply/Mission Impaired Capability Awaiting Parts (NMCS/MICAP) condition. 2. Use in conjunction with Special Requirements Code N (2/LQ01/Code ALL or perpetuated from legacy MILSTRIP Required Delivery Date field). This is an Air Force unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. The code source is identified as the Air Force Manual (AFMAN) 23-10, Volume 1 and 2. A - data maintenance action was approved in version 5010. The approved code/name is "UJC - Urgency Justification Code".
  511M LQ01 RD Property Ownership Type Code Use only on a referral order modification to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify, or to modify, the old (from) ownership code. DLMS enhancement. Refer to ADC 1020.
  511M 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 1. 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. 2. DLMS enhancement.
  511M LQ01 DSI Disposition Services Indicator Code 1. DLA Disposition Services uses to provide (or modify) relevant information applicable to the DLA Disposition Services business process supported by this transaction on an intra-DLA basis. Use multiple repetitions of the LQ Segment to include all applicable codes. Authorized DLMS enhancement for use by DLA Disposition Services. Refer to ADC 466. 2. The following Disposition Services Indicator values are available for use in the requisition transaction: MRA - Materiel Receipt Acknowledgment Required. DMIL - DEMIL Certification Required. MUTL - Mutilation Certification Required. RCYL - Certificate of Recycling Required. CIF - Container Issued in Full. WALK - Walk-in Customer. PICK - Customer Pick-up Required. CS - DEMIL Condition of Sale Indicator 3. Qualifier DSI is a migration code approved for use in X12 version 6050. The approved code/name is "DSI- Disposition Services Indicator".
  511M LQ01 EWR Evaluate Work Candidate Reason Lookup 1. Use to identify, or to modify, the Requirement Churn Reason Code to identify materiel orders required by the industrial site to complete planed work above what was originally identified during the pre-planed process, ordered and delivered after the start of the availability. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  511M LQ01 IMC Item Management Code Use to indicate whether an item of supply shall be subject to integrated management or shall be retained by the individual military service or other DoD Component for their management 1. Use for integrated material management. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. DLMS enhancement.
  511M LQ01 MCC Material Control Code Use to denote the expendability, repairability, recoverability, and cost category employed in the management of an item of supply within the Navy 1. Use for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. DLMS enhancement.
  511M LQ01 SEC Stock Exchange Code Use to identify the Exchange Pricing Indicator for intra-Army transactions to identify that the Customer and National Item Identification Number (NIIN) on the transaction are Exchange Pricing relevant Use to identify the Exchange Pricing Indicator for intra-Army transactions to identify that the Customer and NIIN on the transaction are Exchange Pricing relevant. When applicable, cite code value EP (Exchange Pricing). Refer to ADC 274. A - data maintenance action was approved in version 6010. The approved code/name is "EPI - Exchange Pricing Indicator".
  511M LQ01 SMI Special Material Identification Code Use to categorize material on the basis of requirements for source or quality control; technical design or configuration control; procurement, stocking, and issue control; special receipt, inspection, testing, storage, or handling 1. Use to identify an end item. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. DLMS enhancement.
  511M LQ01 T05 Inspection Parameters 1. Use to identify, or to modify, the Quality Inspection Code indicating the level of quality inspection to which the item must be procured and inspected. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  511M QTY01 OC Order Count DLA Disposition Services uses to identify the total number of DTIDs in a specified container (i.e., the container count) when the entire container is being requisitioned. DLMS enhancement; Refer to ADC 466.
  511M 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.
  511M N101 BS Bill and Ship To Use either this code, or both codes BT and ST, for reimbursable materiel. Use to modify, or in the case of an unmatched modification, use to identify the organization which receives both the materiel and the billing for the materiel. Modifier transactions may not be used to change this field for GFM requisitions.
  511M N101 BT Bill-to-Party 1. Use with code ST for reimbursable materiel. Use to modify, or in the case of an unmatched modification, use to identify the organization to receive billing for materiel when different form the organization receiving the materiel. Use precludes the use of Code BS for the Bill-to DODAAC. Modifier transactions may not be used to change this field for GFM requisitions. 2. 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. 3. Authorized DLMS enhancement; see introductory DLMS note 3g.
  511M N101 DA Delivery Address 1. Use with 2/N2/190, 2/N3/20, and 2/N4/210 to fully identify or modify in-the-clear exception ship-to address information under authorized conditions. 2. Use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code ST) for exception ship-to address information. See introductory DLMS note 3f. 3. DLMS enhancement; see introductory DLMS note 3a.
  511M N101 DZ Delivery Zone 1. Use to provide the DELIVERY LOCATION indicating where the materiel is to be staged/stored. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  511M N101 IF International Freight Forwarder Use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code NA) Notice of Availability (NOA) address information. See introductory DLMS note 3f.
  511M N101 MF Manufacturer of Goods Use to identify the manufacturer of the identified item
  511M N101 PK Party to Receive Copy 1. Use as needed to identify an organization to be provided a copy of this transaction. Use with N103, qualifier M4 (Routing Identifier) and N106, qualifier To (Message To). 2. Must be used between Army and DLA for their integrated set assembly program, when an assembly component part being ordered by the Army is not managed by DLA, and DLA is acquiring it in support of the Army medical mission. Refer to ADC 276. 3. Used between Navy and DLA for Navy requisitions submitted directly to other Component SoS, so that DLA will be able to support follow-on actions on behalf of the Navy industrial activity (IA) under a DLA industrial activity support agreement. Refer to ADC 377. 4. DLMS enhancement; see introductory DLMS Note 3a.
  511M N101 ST Ship To Use with code BT for reimbursable materiel. Use to modify, or in the case of an unmatched modification, use to identify the organization to receive the materiel when different from the activity being billed for the materiel. Use precludes the use of Code BS. Modifier transactions may not be used to change this field for GFM requisitions.
  511M N101 UQ Subsequent Owner Use only on a referral order modification to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify, or to modify, the RIC to which ownership is being transferred (the New Owner RIC). DLMS enhancement. Refer to ADC 1020.
  511M 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.
  511M N101 Z1 Party to Receive Status The entity to receive status for the designated document number 1. Use to modify, or in the case of an unmatched modification, use when different from Service/Agency prescribed status recipient. Use multiple iterations to identify all status recipients, as required. 2. The DLMS provides the capability to carry additional status recipients beyond those identified by legacy MILSTRIP. The Media and Status Code and the Distribution Code will be retained in the DLMS to facilitate transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Additional status recipients identified here cannot be passed to legacy MILSTRIP users.
  511M N101 Z2 Unserviceable Material Consignee Use when requisitioning from a reclamation organization to indicate the Consignee for unserviceable materiel. .
  511M N101 Z3 Potential Source of Supply Use when requisitioning nonstandard materiel identified in PO106 only with code FT or MG to identify potential supply sources.
  511M N101 Z4 Owning Inventory Control Point Use to indicate the source of supply Must use to identify the owning ICP.
  511M N101 Z5 Management Control Activity Use for GFM or CFM requisitions.
  511M N101 Z7 Mark-for Party 1. Use to identify or modify an entity located within the ship-to address that is to actually receive the materiel. 2. The Mark-for Party may be identified by DODAAC, RIC, clear text, or a combination of these. Only one of DODAAC or RIC may be used. 3. Maximum length of the Mark-for Party is 24 positions: Mark-for clear text (with no DODAAC or RIC) displays on DoD shipment documents as two lines of 12 characters each. If text is combined with a DODAAC, up to 17 clear text characters will be allowed. If text is combined with a RIC, up to 20 clear text characters will be allowed. A slash (/) will be inserted during printing of shipment documentation to separate the DODAAC or RIC from clear text; do not perpetuate the slash (/) in the DLMS transaction. 4. Authorized DLMS enhancement; see introductory DLMS note 3g. Refer to ADC 109A. 5. Also use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MF) to identify mark-for delivery information. See introductory DLMS note 3f.
  511M N101 3 Application Party Used with Supply Status CX to identify the Routing Identifier of the internet ordering application in notification to DAS that the requisition modifier failed to receive authorization for continued processing under funds verification procedures. DAS shall prepare CX Supply Status on behalf of the identified internet ordering application rather than continue processing the requisition modifier. Refer to ADC 328.
  511M N101 IAD Foreign Office 1. Use for clear-text exception data FMS in-country address. 2. Use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MA) FOR FMS in-country mark-for address. See introductory DLMS note 3f.
  511M 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.
  511M N103 33 Commercial and Government Entity (CAGE)
  511M 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 3g.
  511M 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.
  511M 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. 2. DLMS enhancement; see introductory DLMS note 3a.
  511M 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
  511M N106 TO Message To Use to identify the party to receive the transaction set Must use with the appropriate 2/N101/180 code to indicate the organization cited in N104 is receiving the transaction.
Page 7  of  141 First   Previous   3  4  5  6  [7]  8  9  10  11  12  Next   Last