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
  940R N101 BS Bill and Ship To Use either this code, or both codes BT and ST, for reimbursable materiel. Use in redistribution orders, materiel release orders, historical materiel release orders, materiel release order modifications, disposal release orders, and historical disposal release orders to identify the organization which receives both the materiel and the billing for the materiel. BT - Bill-to-Party: 1. Use with code ST for reimbursable materiel. Use in redistribution orders, materiel release orders, historical materiel release orders, materiel release order , modifications, disposal release orders, and historical disposal release orders to identify the organization to receive the billing for the materiel when different from the organization receiving the materiel. Use precludes the use of code BS for the Bill-to DODAAC. 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 4f.
  940R N101 CA Carrier 1. Use as needed for directed returns to identify the carrier to be used for the return shipment. Refer to ADC 164. 2. The carrier is identified by name (N102) and Standard Carrier Alpha Code (SCAC) using Code 2 (N103), when available. 3. Authorized DLMS enhancement; see introductory DLMS note 4f.
  940R N101 CN Consignee Use to identify an entity that is named on shipping documents as the recipient of a shipment Use in materiel release order cancelations to identify the new Consignee to which a shipment should be diverted.
  940R N101 DA Delivery Address 1. Use with 2/N2/101, 2/N3/102, and 2/N4/103 to fully identify in-the-clear exception ship-to address information under authorized conditions. 2. Use for MRO Exception Data Transaction to indicate the ship-to clear-text exception address is a MRO Type Address Code (TAC) 2 (ship-to) freight address. 3. DLMS enhancement; see introductory DLMS notes 4a and 4e. 4. Use when this transaction supports the Retail Transportation and Supply Receipt and Acknowledgement Interchange SBS interface with CMOS to provide the shipping address when not associated with a DODAAC.
  940R N101 IF International Freight Forwarder 1. Use for MRO clear-text exception data FMS Notice of Availability (NOA) address. 2. Use when transaction includes Component-unique MRO exception data; may be referred to as MAPAC “TAC” 3 address. See introductory DLMS note 4e.
  940R N101 KK Registering Party 1. Use to identify the Component UIT registry. May be used by a Component when their UIT process requires that a copy of the transaction should also be sent to a UIT registry for information purposes. Must be used with 2/N106/10 code ‘PK-Party to Receive Copy’ to identify that this is only an information copy of the transaction, for use with the Component UIT registry. Cite the applicable Routing Identifier in 2/N104. , 2. Authorized DLMS enhancement for Air Force use with PIC NWRM UIT program. For PIC UIT, must use in conjunction with 2/N106 code PK and cite the applicable Routing Identifier in 2/N104. 3. Except noted as above, DLMS enhancement; see introductory DLMS note 4a.
  940R N101 LG Location of Goods For LROs, use to identify an alternative supply source.
  940R N101 MQ Delivery Location 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.
  940R N101 RC Receiving Location Use for Disposal Shipment Confirmation Follow-up (W0506=NH, DIC AFX/AFZ) to identify the DLA Disposition Services Field Office responsible for this follow-up action. This is the receiving activity, or intended receiving activity, for property shipped to DLA Disposition Services. This is an authorized DLMS enhancement. Refer to ADC 464.
  940R N101 SB Storage Area 1. Use to identify the storage facility to receive the transaction set. 2. Use for Disposal Shipment Confirmation Follow-up (W0506=NH, DIC AFX/AFZ) to identify the activity to receive the transaction. This will normally be the shipping activity identified by RIC. If the RIC is not available, the transaction may be directed to the DODAAC identified in the Document Number. In this usage, the transaction may be transmitted to the ICP/IM that directed the disposal action. ICPs/IMs receiving this Follow-up shall either retransmit this transaction to the shipping activity or coordinate with the shipping activity to prepare the appropriate response. Refer to ADC 464.
  940R N101 ST Ship To 1. Use with code BT for reimbursable materiel. Use in redistribution orders, materiel release orders, historical materiel release orders, disposal release orders, and historical disposal release orders 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. 2. May be used with clear text address for excess plant property requisitions only. See introductory DLMS note 4e.
  940R N101 UQ Subsequent Owner Use only for inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify the RIC to which ownership is being transferred (the New Owner RIC). DLMS enhancement. Refer to ADC 1020.
  940R N101 WL Wholesaler , 1. Use for lateral redistribution of non-Integrated Material Manager (IM) or Primary Inventory Control Activity (PICA) owned materiel, to identify the materiel owner to receive the transaction set under single stock fund concept. Use with 2/N101/10 Code LG to identify the activity at which the materiel is Physically located. (Note: This is the owning activity as identified in the Asset Status Reporting transaction (DIC DZF rp 31-3). 2. DLMS enhancement: see introductory DLMS note 4a. This activity derived under legacy MILSTRIP by referencing DAS table.
  940R 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.
  940R N101 Z1 Party to Receive Status The entity to receive status for the designated document number 1. Use to indicate the organization to receive shipment status as identified on the original requisition. 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.
  940R N101 Z7 Mark-for Party 1. Use in redistribution orders, materiel release orders, historical materiel release orders, and materiel release order modifications, to identify an entity located within the ship-to address that is to actually receive the materiel. Total field length is restricted to 24 clear text characters, when not used in combination with a DODAAC or RIC. If combined with a Mark-for DODAAC, restrict clear text to 17 characters. If combined with a Mark-for RIC, restrict clear text to 20 characters. Authorized DLMS enhancement; see introductory DLMS note 4f. Refer to ADC 109A. 2. For DLA Disposition Services public sales, the customer shall be identified as the Mark-for Party using N102. Use in conjunction with N101, Code BS, Bill and Ship To, identifying the unique DLA Disposition Services public sales DODAAC. No physical shipment is involved; public sales are designated for pick-up only. Refer to ADC 463. 3. DLA Disposition Services uses to identify the Reutilization/Transfer/Donation (RTD) Web Application customer for pick-up of requisitioned property. The customer’s requisitioning DODAAC will be identified as the Mark-For Party and the customer name and phone number will be provided in the subsequent Point of Contact information (PER Segment). Refer to ADC 466. 4. DLMS enhancement; see introductory DLMS note 4a.
  940R N101 IAD Foreign Office , 1. Use for MRO clear-text exception data FMS in-country address. 2. Use when transaction includes Component-unique MRO exception data; may be referred to as MAPAC “TAC M” address. See introductory DLMS note 4e.
  940R N101 SUS Supply Source Use only when this transaction supports the Retail Transportation and Supply Receipt and Acknowledgement Interchange SBS interface with CMOS to provide the Routing Identifier Code of the Source of Supply when FLIS item data is not otherwise available to CMOS.
  940R N103 2 Standard Carrier Alpha Code (SCAC) Use with N101 Code CA to identify the commercial carrier by code. Identify the value of the SCAC in N104.
  940R 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 4a.
  940R 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 4f.
  940R N103 92 Assigned by Buyer or Buyer's Agent Use with N101 Entity Identifier Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer to ADCs 284A, 381, and 1454.
  940R 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 4a.
  940R 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
  940R N103 UR Uniform Resource Locator (URL) DLMS enhancement; see introductory DLMS note 4a.
  940R N106 PK Party to Receive Copy 1. Use when appropriate to send an information copy to a Component UIT registry. For use with N101 code ‘K’. 2. Authorized DLMS enhancement for Air Force use with PIC NWRM UIT program. For PIC UIT, must use in conjunction with 2/N101 code ‘K’ and cite the applicable Routing Identifier in 2/N104. 3. Except as noted above, DLMS enhancement; see introductory DLMS note 4a.
  940R N106 TO Message To , Must use with the appropriate 2/N101/10 code to indicate the organization cited in N104 is receiving the transaction.
  940R N405 IP Postal Use when transaction includes Component-unique MRO exception data to identify the secondary (parcel post) nine-position postal code associated with the ship-to address (N101 Code DA).
  940R PER01 IC Information Contact 1. Use to identify the point of contact. 2. DLA Disposition Services uses to perpetuate the customer contact name and phone number provided by the RTD Web Application to the DLA Disposition Services Field Office. Use in the N1 Segment identifying the Mark For Party. Refer to ADC 466.
  940R PER03 TE Telephone
  940R 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.
  940R 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. 2. Future streamlined data; see introductory DLMS note 4c.
  940R LQ01 61 Information Indicator Code Use when transaction includes Component-unique exception to indicate the specific type of exception data as identified by the exception data record type.
  940R LQ01 67 Type of Assistance Code 1. For SA materiel release order and historical materiel release order use when the coded address in the transaction number does not identify the type of assistance and financing. 2. DLMS enhancement; see introductory DLMS note 4a.
  940R LQ01 78 Project Code , 1. Use in redistribution orders, materiel release orders, disposal release orders and historical materiel release orders, but only to identify special programs, exercises, projects, operations, and other purposes. Use in materiel release order modifications to identify the revised project code. 2. Use of a project code in a disposal release order is an authorized DLMS enhancement; see introductory DLMS note 4b. 3. For DoD SLOA/Accounting Classification compliance the Project Code may be repeated as a Project Identifier (FA201 Qualifier 90). Refer to ADC 1043. 4. For the warehouse project code, use 2/N901/040 qualifier P4.
  940R LQ01 79 Priority Designator Code A code to communicate the relative importance to the requisitioner's mission based upon its force activity designator (FAD) and urgency of need designator (UND) Use in redistribution orders, materiel release orders, historical materiel release orders, disposal release orders, and historical disposal release orders, to identify the supply priority assigned to this transaction. Use in materiel release order modifications to identify the revised priority.
  940R LQ01 80 Advice Code Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action Use in redistribution orders, materiel release orders, historical materiel release orders, and disposal release inquiries, to convey information considered essential to the supply action. Use in materiel release order modifications to identify the revised Advice Code.
  940R LQ01 83 Supply Condition Code Classifies materiel in terms of readiness for issue and use or to identify action underway to change the status of materiel Use in redistribution orders, materiel release orders, historical materiel release orders, disposal release orders, and historical disposal release orders, to identify the supply condition code of the materiel to be selected for shipment.
  940R LQ01 84 Management Code Use in redistribution orders, materiel release orders, historical materiel release orders, disposal release orders, and historical disposal release orders to identify applicable management information.
  940R LQ01 87 Subsistence Type of Pack Code Use to indicate the degree of protection to be provided subsistence items Use with subsistence items only, in redistribution orders, materiel release orders, historical materiel release orders, disposal release orders, and historical disposal release orders to identify the specific subsistence type of pack to select for shipment.
  940R LQ01 88 Disposal Authority Code Use in disposal release orders and historical disposal release orders, to indicate that the designated materiel is authorized for shipment to a disposal or reutilization facility.
  940R LQ01 90 Precious Metals Indicator Code 1. Use in disposal release orders and historical disposal release orders, to identify the precious metal content of the specified materiel. , 2. Use when this transaction supports the Retail Transportation and Supply Receipt and Acknowledgement Interchange SBS interface with CMOS when FLIS item data is not otherwise available to CMOS.
  940R LQ01 91 Automated Data Processing Equipment Identification Code Use in disposal release orders and historical disposal release orders, to identify ADPE identification information.
  940R LQ01 92 Reason for Disposal Code 1. Use in disposal release orders and historical disposal release orders, to identify the reason the disposal action is required. 2. DLMS enhancement; see introductory DLMS note 4a.
  940R LQ01 93 Type of Storage Code 1. Use in redistribution orders, materiel release orders, and historical materiel release orders, to identify the minimum storage requirements associated with the materiel. 2. DLMS enhancement; see introductory DLMS note 4a.
  940R LQ01 94 Identification Code Use in FMS transactions to identify the customer country's requisitioning Service Code Must use in FMS transactions to identify the customer country's requisitioning Service Code: B, D, K, P, or T. This is the SA program Customer Service Designator (codes derived from Qualifier 71, Service and Agency Code). A - DM will be submitted to create a new qualifier for this data element.
  940R LQ01 95 Offer and Release Option Code Use in FMS materiel release orders and historical materiel release orders, to identify the type of notice required prior to materiel shipment. Use in materiel release order modifications to identify the revised offer and release option.
  940R LQ01 97 Ultimate Recipient Code 1. Use in materiel release orders and historical materiel release orders, to identify the buyer of DoD materiel, to allow full payment for materiel supplied to the non-DoD customer. Use in materiel release order modifications to identify the revised Ultimate Recipient Code. 2. DLMS enhancement; see introductory DLMS note 4a.
  940R LQ01 98 Reason for Requisitioning Code 1. Use to identify Reason for Requisitioning Code identifying the use of the materiel. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
  940R LQ01 99 Purpose Code , 1. May be used for LRO if required based on Service/Agency agreement. 2. For all other uses, this is a DLMS enhancement, see introductory DLMS note 4a.
Page 129  of  141 First   Previous   125  126  127  128  [129]  130  131  132  133  134  Next   Last