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
  527R N904
  527R N907
  527R N907-01 08 Carrier Assigned Package Identification Number Use to identify the commercial carrier-assigned tracking number Use to identify the shipment unit small package identification number. 1/17
  527R N907-01 97 Package Number Use to identify the shipment unit package identification number Use to identify the shipment unit package identification number. 1/30
  527R N907-01 AW Air Waybill Number Use to identify air waybill document prepared by a transportation line at the point of origin of a shipment showing the point of origin, destination, route, consignor, consignee, description of shipment and amount charged for the transportation service 11/11
  527R N907-01 BL Government Bill of Lading A number assigned to a document by a consignor which represents a limited liability contract covering transportation of property from one place to another 7/17
  527R N907-01 BM Bill of Lading Number Use to identify the shipment unit commercial bill of lading number 1/16
  527R N907-01 C7 Contract Line Item Number A number that identifies all items of supply or services in a contract For use in Commercial Asset Visibility (CAV) receipts to identify the CLIN/SUBCLIN. Use in conjunction with N901 code CT. Authorized DLMS migration enhancement for CAV use. See DLMS introductory note 5g. 4/6
  527R N907-01 IZ Insured Parcel Post Number Assigned to a package being shipped when the article being sent has a value and accountability is required Use to identify the shipment unit registered mail number. 1/17
  527R N907-01 K1 Foreign Military Sales Notice Number Use to identify the number assigned to control the shipment between the shipper and consignee 1/30
  527R N907-01 K2 Certified Mail Number Number assigned by the US Postal Service (USPS) certifying proof of delivery 1/17
  527R N907-01 K3 Registered Mail Number A number assigned by the US Postal Service to identify mailed items that require additional protection and security in dispatch and conveyance in the united states Use to identify the shipment unit registered mail number. 1/17
  527R N907-01 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 When used in association with the Requisition Alert Document Number (Qualifier PWC, above), this will be the requisition alert document suffix. The Requisition Alert Document Number Suffix is an Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 1/1
  527R N907-01 WY Waybill Number Use to identify a carrier accounting number of the waybill for the inbound movement 8/11
  527R N907-01 ZH Carrier Assigned Reference Number Use to identify the shipment unit express mail number Use to identify the shipment unit express mail number. 1/9
  527R N907-01 BCI Basic Contract Line Item Number Use to identify the Sales Contract Line Item Number This is used to represent DLMS Data element ''Sales Contract Line Item Number”. DLA Disposition Services uses in conjunction with the Sales Contract Number at 2/N901/090/FCN. 6/6
  527R N907-02
  527R AMT01 29 Estimated Price Use to identify the estimated unit cost or estimated unit price Use when needed in receipt and historical receipt transactions to cite the estimated unit price of the item received. 1/18
  527R AMT01 JJ Cost Basis Use to identify the Latest Acquisition Cost (LAC) 1. Use to identify the Latest Acquisition Cost (LAC). Under DLMS, express the latest acquisition cost as R9.2. R is the data element type indicating a decimal numeric data element. Pass the decimal point within the transaction; do not transmit leading and trailing zeros. 2. Except as noted below, this is a DLMS enhancement; see introductory DLMS note 5a. 3. Use for AMMA receipts to identify the acquisition unit price of the materiel. This price will allow valuation of inventory for receipts not against a purchase order. 4. For intra-Air Force use in wholesale receipts of property by the Air Force CICP to identify the updated latest acquisition cost for the item received. 1/18
  527R AMT01 NT Unit Value Use to identify the standard unit price 1. Use when needed in receipt and historical receipt transactions to cite the standard unit price of the item received. 2. Use as needed for DLA industrial activity support agreement. Refer to ADC 1128. 1/18
  527R AMT02
  527R NTE01 NPD Nameplate Data Used to provide the item name DLA Disposition Services Field Office uses to provide the item name. The field office uses one repetition of the NTE segment to provide item name in the disposition services turn-in receipt acknowledgement (TRA) transaction to identify property received. Item name can be up to 48 characters. Authorized DLMS enhancement. Refer to ADC 1111. 1/80
  527R NTE01 OCA Other Current Asset Description DLA Disposition Services uses with receipt and historical receipt transactions DLA Disposition Services users may use up to 5 repetitions of the NTE segment to provide a description of Disposal Turn-in document (DTID) materiel. DLA Disposition Services uses with receipt and historical receipt transactions. Not used with TRA transactions. Authorized DLMS enhancement for use by DLA Disposition Services. Refer to ADC 442 and ADC 1111. 1/80
  527R NTE01 OTH Other Instructions Use to provide other instructions 1/2000
  527R NTE02
  527R G6602
  527R 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.
  527R 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 DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. In a mixed DLSS-DLMS environment, when including BG1/BG2 data for Inter-Service Ammunition interface, must use 2 iterations of LQ to provide DIC D6_ as well as either DIC BG1 or BG2 as applicable, to alert DAAS of BG1/ BG2 requirement for non-DLMS Ammunition system trading partners: Naval Operational Logistics Support Center (NOLSC) Ordnance Information System-Wholesale (OIS-W), Program Manager for Ammunition, Marine Corps Systems Command (MARCORSYSCOM) Ordnance Information System-Marine Corps (OIS-M),and Warner Robins Air Logistics Complex Combat Ammunition System (CAS). 3. Future streamlined data; see introductory DLMS note 5c. 3/3
  527R LQ01 42 Estimated Time of Arrival Code Use to denotes the number of days a shipment is estimated to arrive 1/1
  527R LQ01 71 Service and Agency Code Use to identify the Service or Agency that initiates or receives documentation related to supply, finance, procurement, etc. 1. For all SA transactions, use to identify the Service ILCO managing the case or program line when the ILCO is not identified in the coded address in the transaction number. 2. DLMS enhancement; see introductory DLMS note 5a. 1/2
  527R LQ01 78 Project Code Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes 3/3
  527R 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) 1. Army uses in nonprocurement source receipts to identify priority designator. Use of this data is meaningful to Army only. Army cites data in multiuse rp 60-61 of MILSTRAP legacy DIC D6_. Army authorized DLMS migration enhancement. See DLMS introductory note 5g. 2. Army also uses to communicate the priority designator associated with Army Total Package Fielding receipt. 2/2
  527R LQ01 80 Advice Code Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action 1. Use when submitting a duplicate receipt in reply to a receipt inquiry (Advice Code 3P); when submitting a response to a receipt inquiry when there is a receipt in process (Advice Code 3K); when there is no receipt in process and no prepositioned materiel receipt (PMR) file (Advice Code 3N); and when there is no receipt in process but there is a PMR file (Advice Code 3M). Otherwise do not use except as noted below. DLMS enhancement, see DLMS introductory note 5a. Refer to ADC 313. 2. Army uses in nonprocurement source receipts to identify Army return advice codes. Use of Army return advice code in receipts is meaningful to Army only. Army cites data in multiuse rp 65-66 of MILSTRAP legacy DIC D6_. Army authorized DLMS migration enhancement. See DLMS introductory note 5g. 2/2
  527R 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 to identify the materiel condition for the 2/RCD02/040 quantity. Must use in receipt and historical receipt, receipt inquiry, response to receipt inquiry, and disposition services turn-in receipt acknowledgement (TRA) transactions. 1/1
  527R LQ01 84 Management Code Provides supplemental data not indicated through the transaction coding structure Use multiple repetitions to identify all applicable management codes. Do not use with MRA or inquiries for delinquent MRA. 1/1
  527R LQ01 87 Subsistence Type of Pack Code Use to indicate the degree of protection to be provided subsistence items Use for subsistence items only. 1/1
  527R LQ01 92 Reason for Disposal Code Identifies the reason an item is being transferred to a defense reutilization and marketing office 1. Use in receipt and historical receipt transactions to cite the reason when materiel is shipped to Defense Reutilization and Marketing Office (DRMO) upon receipt. 2. DLMS enhancement; see introductory DLMS note 5a. 1/1
  527R LQ01 94 Identification Code Use in FMS transactions to identify the customer country's requisitioning Service Code 1. 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. 2. DLMS enhancement; see introductory DLMS note 5a. 1/2
  527R LQ01 98 Reason for Requisitioning Code Identifies the reason for submission of the requisition or the type of materiel requirement applicable to a requisition, requisition alert, or materiel release order 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. 1/2
  527R LQ01 99 Purpose Code Provides the owner of materiel with a means of identifying the purpose or reason for which an inventory balance is reserved Use in receipt, historical receipt, receipt inquiry and response to receipt inquiry when known. 1/1
  527R LQ01 A1 Ownership Code Provides a means of segmenting inventory balances, accounted for in inventory control records of a Military Service/DLA, but which are owned by others Use in receipt, historical receipt, receipt inquiry and response to receipt inquiry when known. 1/1
  527R 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 supplemental address/data. 2. During the DLSS/DLMS transition, this field will be used to perpetuate/populate the DLSS Supplementary Address (SUPPADD) field During this time, field size is restricted to 6 positions; see introductory DLMS note 5d. For receipt, historical receipt, receipt inquiry, and response to receipt inquiry transactions, enter or perpetuate SUPPADD, otherwise leave blank. For MRA transactions, perpetuate from receipt transaction; or for total or partial nonreceipt, perpetuate from due-in record. For TRA transactions, perpetuate from receipt transaction. Refer to ADC 1111. 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 5a. 4. Under full DLMS, the requirement to pass activity address information within the supplement data field will be streamlined. Activity address data previously contained in the SUPPAAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 5c. 6/6
  527R LQ01 AK Distribution Code Use to identify the activity that will receive a supply status and other management data Future streamlined data; see introductory DLMS note 5c. 1/3
  527R LQ01 DE Signal Code In requisition related documents, it designates the fields containing the intended consignee (ship-to), and the activity to receive and effect payment of bills, when applicable. In the case of the Material Returns Program (MRP), it designates the fields containing the intended consignor (ship-from) and the activity to receive and process credits, when applicable 1. For receipt, historical receipt, receipt inquiry, and response to receipt inquiry transactions, enter or perpetuate signal code, otherwise leave blank. For MRA transactions, perpetuate from receipt transaction; or for total or partial nonreceipt, perpetuate from due-in record. For TRA transactions, perpetuate from receipt transaction. Refer to ADC 1111. 2. Future streamlined data; see introductory DLMS note 5c. 1/1
  527R LQ01 DF Media and Status Code Identifies the desired status recipient(s) and the type of status to be provided Future streamlined data; see introductory DLMS note 5c. 1/1
  527R LQ01 EI Discrepancy Indicator Code Use to indicate when a supply or transportation discrepancy or product quality deficiency affects the receipt posting and/or process 1. Use in MRA transactions to acknowledge receipt of a discrepant shipment. 2. DLA Disposition Field Office uses in TRA transaction to acknowledge receipt of a discrepant shipment. Refer to ADC 1111. 3. Use for intra-Army receipt transactions from other than procurement instrument source to identify the type of materiel discrepancy that exists upon receipt of materiel for the Army Single Stock Fund. Army enters this code in MILSTRAP legacy DIC D6_ multiuse field at rp 80. Authorized Army DLMS migration enhancement for intra-Army use in receipt (other than procurement instrument source) transactions. Refer to ADC 272. 1/1
  527R LQ01 EQ Controlled Inventory Item Code Use to indicate the security classification and/or security risk or pilferage control for storage and transportation of Department of Defense assets 1. For mapping products, use to identify the Controlled Inventory Item Code. Authorized DLMS migration enhancement. See DLMS introductory note 5g. 2. Authorized DLMS enhancement for use by DLA Disposition Services in receipt, historical receipt and TRA transactions. Refer to ADC 442 and ADC 1111. 1/1
  527R LQ01 FC Type Physical Inventory or Transaction History Code 1. Use only with 1/BR06/20 Action Code W1. 2. DLMS enhancement. See introductory DLMS note 5a. 1/1
  527R LQ01 FD Demilitarization Code Use to define the requirements for removal of the military characteristics of a weapon or munition and the type of demilitarization needed to meet those requirements Authorized DLMS enhancement for use by DLA Disposition Services in receipt, historical receipt and TRA transactions. Refer to ADC 442 and ADC 1111. 1/1
  527R 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 Material Management Aggregation Code (MMAC) 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-110, Volumes 1 and 2. 2/2
Page 32  of  195 First   Previous   28  29  30  31  [32]  33  34  35  36  37  Next   Last