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 NOTESorted by descending DLMS MIN MAX
  856S LQ01 A8 Program Year Code Use in Military Assistance Program (MAP)/grant aid (GA) transactions to indicate the program year in which the requisitioned item was Approved Code and funded 1. Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was approved and funded. 2. DLMS enhancement; see introductory DLMS note 2a. 1/80
  870S LQ01 A7 Record Control Number Use to identify a specific item or service within a government contract Military Assistance Program (MAP) Grant Aid (GA) case 1. Must use in MAP/GA transactions to identify the program line item number. 2. DLMS enhancement; see introductory DLMS note 3a. 4/4
  856S LQ01 A7 Record Control Number Use to identify a specific item or service within a government contract Military Assistance Program (MAP) Grant Aid (GA) case 1. Must use in MAP/GA transactions to identify the program line item number. 2. DLMS enhancement; see introductory DLMS note 2a. 4/4
  940R N901 CT Contract Number A standard unique identification of a DoD procurement contract (contract number) that specifically differentiates one contract from all other contracts 1. Must use in GFM related transactions to provide the (PIID). Use the legacy procurement instrument identification number (PIIN) pending transition to the PIID. When GFM is authorized under a PIID call/order number (F in 9th position), provide the value in the PIID field. For Other Transaction (OT) agreements, the type of instrument (9th position of PIID) will be a 3 for Research OTs or 9 for Prototype and Production OTs. Refer to ADC 1161A or ADC 1420. 2. Use to provide contract information for shipmen ts of GFP to the contractor. 3. Use for directed release of contractor shipments of GFP into DoD inventory. 4. Authorized DLMS enhancement. Refer to ADC 1014. 1/13
  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). 2. DLMS enhancement; see introductory DLMS note 5a. 1/2
  870S LQ01 A6 Freight Forwarder Number Use in Foreign Military Sales (FMS) transactions to identify the country representative or freight forwarder to receive shipments and documentation 1. Must use in FMS transactions to identify the country representative or freight forwarder to receive shipments and documentation. 2. DLMS enhancement; see introductory DLMS note 3a. 1/30
  856S LQ01 A6 Freight Forwarder Number Use in Foreign Military Sales (FMS) transactions to identify the country representative or freight forwarder to receive shipments and documentation 1. Must use in FMS transactions to identify the country representative or freight forwarder to receive shipments and documentation. 2. DLMS enhancement; see introductory DLMS note 2a. 1/30
  856R REF01 TG Transportation Control Number (TCN) A 17-position alphanumeric assigned to control and manage every shipment unit throughout the transportation pipeline 1. Must use in every 2/HL/0100 transaction reference number loop to identify the shipment unit TCN. 2. Reuse/duplication of a previously used TCN is not permitted. If the controlling document number for the retrograde or directed return is the same as the original shipment, a unique TCN (not derived from the original document number) must be identified. 17/17
  536L N901 QR Quality Report Number Use to identify the Product Quality Deficiency Reporting (PQDR) Report Control Number (RCN) that is comprised of the six-position originating activity Department of Defense Activity Address Code (DoDAAC), a two-digit calendar year, and a unique four-position serial number 1. Must use in every 2/HL/010 quality characteristics loop to identify the PQDR report control number assigned by the originator of the PQDR. 2. DLMS enhancement; see introductory DLMS note 4a. 12/12
  536L N101 MF Manufacturer of Goods Use to identify the manufacturer of the identified item 1. Must use in every 2/HL/010 quality characteristics loop to identify the manufacturer or prime contractor for the materiel reported on the PQDR. 2. DLMS enhancement; see introductory DLMS note 4a. 1/60
  536L N901 55 Sequence Number A unique identifier assigned to an item, task, or process to denote its specific order or position within a larger sequence 1. Must use in every 2/HL/010 line detail loop to identify the complaint sequence number for each complaint cited on the PQDR. In the first 2/HL/010 line detail loop iteration, cite numeric 1 in N902. In each subsequent 2/HL/010 loop iteration, increase the N902 value incrementally by 1. 2. DLMS enhancement; see introductory DLMS note 4a. 1/30
  846I N106 FR Message From Use to identify the party originating the transaction set 1. Must use in conjunction with the appropriate 1/N101/080 code to indicate the organization cited in N104 is originating the transaction set. 2. Use to identify the activity preparing the consumption report (GFM) or asset status report, except as noted below. 3. For DLA industrial activity support agreement, cite code ‘SB’ to identify the DLA DSS storage activity preparing the Asset Status Report on behalf of the owning ICP. The owning ICP, when not the activity originating the transaction set, appears in 2/N101/450. 4. For Army/DLA DDKS interface in a mixed DLSS/DLMS environment, based upon agreement, the DLA storage activity may prepare the 846I on behalf of the DLA ICP, with the DLA ICP RI Code SMS entered as the ‘Message From’ activity originating the transaction. This is an interim DDKS approach in the mixed DLMS/DLSS environment to accommodate Army’s requirement for the owning ICP to map to the DLSS DIC DZA rp 67-69, which is identified as the RI Code of the ICP preparing the transaction. As Army transitions to DLMS, the 1/N106/080 FR should reflect the true activity preparing the transaction set, and the appropriate qualifier for storage activity or ICP preparing the transaction should be used. The information on the owning ICP or storage activity, when not the activity originating the transaction set, should appear in 2/N101/450. See ADC 250. Any future DLA Distribution Standard System (DSS) implementation should use the alternative approach documented in ADC 250. 1/60
  869A 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 in 2/HL/010 transaction loops to identify the document number. 2. When used with the requisition alert indicator (BSI09=83), this will be the requisition alert document number. The requisition alert is an authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 14/14
  869F 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 in 2/HL/010 transaction loops to identify a transaction number assigned to the transaction. This is the document number. 2. When used in the requisition alert follow-up (BSI09=83), this will be the requisition alert document number. The requisition alert is an Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 14/14
  856S REF04-01 CT Contract Number A standard unique identification of a DoD procurement contract (contract number) that specifically differentiates one contract from all other contracts 1. Must use for CAV shipment status, to identify the procurement instrument identifier (PIID) authorizing repair/return of GFP. Use the legacy procurement instrument identification number (PIIN) pending transition to the PIID. When procurement is authorized under a PIID call/order number (F in 9th position), provide the value in the PIID field. For Other Transaction (OT) agreements, the type of instrument (9th position of PIID) will be a 3 for Research OTs or 9 for Prototype and Production OTs. Refer to ADC 1161A or ADC 1420. 2. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF Segment. Delayed implementation is authorized. 3. Authorized DLMS enhancement; see introductory DLMS 2a. 1/13
  856S REF04-05 C7 Contract Line Item Number A number that identifies all items of supply or services in a contract 1. Must use for CAV shipment status with contract number (REF04-01 code CT) to identify the application CLIN/SubCLIN. 2. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF Segment. Delayed implementation is authorized. 3. Authorized DLMS enhancement. 4/6
  856S N101 RN Repair or Refurbish Location Use to identify the Commercial and Government Entity (CAGE) or Department of Defense Activity Address Code (DoDAAC) Last Repair Facility 1. Must use for CAV shipment status to identify the CAV repair site. 2. Use two iterations of the N1 Loop to identify the repair site by both RIC and DoDAAC. Associate the Message From (N106) with the repair site RIC. Refer to ADC 344. 1/6
  888W N901 W2 Weapon System Number Identifies a three-position alphanumeric code used by the Defense Logistics Agency (DLA) within its Weapon System Support Program (WSSP). It is comprised of a two-position Weapon System Designator (WSD) and a one-position Service Code (SVC)/Activity 1. Must be used to indicate the three-digit or expanded-length four-digit Weapon System Designator (WSD) assigned and/or authorized by DLA to identify the weapon system supported by the identified item. The Service/Agency Code associated with WSD is identified in the last position of the WSDC. Refer to the DLAI 4140.38 Weapon System Support Program (WSSP). Currently authorized Service/Agency Codes are: A - Army F - Air Force M - Marine Corps N - Navy B - Federal Aviation Agency R - National Weather Service Z - Coast Guard 2. DLMS enhancement; see introductory DLMS note 3a. The four-digit WSD is a planned DLMS enhancement during logistics system modernization. It will only be assigned by agreement between DLA and the requesting Service or Agency. 3/3
  842AW QTY01 86 Nonconformance Quantity Use to indicate the discrepant/deficient quantity 1. Must be used to indicate the discrepant/deficient quantity for SDRs/SQCRs. 2. By exception, may be blank for CCP originated SDRs (Document Type= W). Refer to ADC 282. 1/9
  940R N901 AEM Distribution Center Number Use to identify the Distribution Center Number (DCN) when directing storage activities to release discrepant/quality deficient materiel 1. Must be used by the materiel owner ICP to identify the Distribution Center Number (DCN) in N902 when directing storage activities to release discrepant/quality deficient materiel. 2. Perpetuate value from the DLMS 842A/W, 2/REF02/0700 with Qualifier NN in 2/REF01/0700. 3. DCN must not exceed 20 alphanumeric characters. 1/20
  870S REF01 SE Serial Number A value assigned for identification of an item 1. May not exceed 30 characters in accordance with IUID policy. 2. Serial number may be used alone for legacy items when UII is not assigned, otherwise use two occurrences of this segment to identify both the serial number and the UII. A maximum of 60 items may be identified for the CMOS interface. Refer to ADC 407. 1/50
  527R FA201 B5 Fund Code Designation of the billing method (interfund or non-interfund) and the fund account to be charged (disbursed) or credited (refunded) 1. May be used with nonprocurement source receipt transactions when applicable. 2. DLA uses with AMMA procurement source receipt transactions when applicable. Refer to ADC 351 2/2
  940R AMT01 AVA Average Acquisition Cost Use to provide the average acquisition cost per unit of materiel to be used by the reporting activity to bill the materiel manager for any quantity filled 1. Materiel managers perpetuate from the DLMS 511R in LROs to provide the average acquisition cost per unit of materiel to be used by the reporting activity to bill the materiel manager for any quantity filled. 2. Approved for use in X12 version 8060. 1/15
  842P QTY01 T9 Time Since Installation Use to describes how long a part has been operational since installation 1. It describes how long a part has been operational since installation. Equates to SF368, Block 7. 2. Field size = 15 3. This element may only be populated by the Originating Point, Screening Point or Action Point. For inter-service transactions, only the Screening Point and Action Point can update this element. 4. Approved for use in X12 version 8060. 1/15
  842P QTY01 1K Time Units Use to describes how long a part has been operating since it was overhauled 1. It describes how long a part has been operating since it was overhauled. Equates to SF368, Block 7. This is mandatory if 2/REF/0700/=BY=N/R/O. 2. This element may be populated by all processing points. 7/7
  947I W1901 AA Physical Count "Inventory Adjustment (Physical Inventory) Gain or loss disclosed as a result of physical count of stock, single adjustment " 1. Inventory Adjustment (Physical Inventory). Gain or loss disclosed as a result of physical count of stock, single adjustment (DIC D8A or D9A functionality). The use of reason code AA for an inventory adjustment gain combined with a quantity of 0 (zero) indicates that a physical inventory has taken place, and no record adjustment was necessary. 2. For Capital Equipment and UIT Programs, identify all serial numbers corresponding to the NSN, Condition Code, and Owner from the initial physical inventory re quest when using in combination with quantity of 0 (zero). The use of reason code AA in combination with zero quantity indicates to the owner the completion of the inventory. See ADC 1244. 1/10
  940R N901 TAL Aircraft Tail Number 1. Intra-US Air Force. Use to convey the aircraft tail number that the item will be placed on. See introductory note 4a. 2. At this time TAL is established for use in 940R version 4030. A data maintenance action will be submitted to ASC X12 to establish TAL, Aircraft Tail Number, in a future version. 3. Components must coordinate implementation with DEDSO prior to use. 1/50
  832N 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. Indicates the security classification and/or security risk or pilferage controls for storage and transportation of DOD assets (FLIS DRN 2863). 2. For Air Force GFP-A, must use when LIN01 = LA. Otherwise, use only when value changes. Refer to ADC 1227 and ADC 1227B. 1/1
  832N N101 SU Supplier/Manufacturer Use to identify the manufacturer/supplier in various process areas 1. Identifies the manufacturer/supplier of part-numbered items assigned to an LSN where the manufacturer’s CAGE is not known or not assigned. Use N102 for the text name allowing up to 25 positions 2. Use to identify the scrap sales contractor. Use N102 for the clear text name of the contractor. Refer to ADC 1234. 1/60
  846S 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. Future Streamlined data; see introductory DLMS note 5c. 2. 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. 3/3
  846D 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. Future Streamlined data; see introductory DLMS note 5c. 2. 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. 3/3
  846I 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. Future Streamlined data; see introductory DLMS note 4c. 2. 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. 3/3
  846P 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. Future Streamlined data; see introductory DLMS note 4c. 2. 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. 3/3
  830W 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. Future Streamlined data; see introductory DLMS note 3c. 2. 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. 3/3
  846F 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. Future Streamlined data; see DLMS Introductory note 4c. 2. 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. 3/3
  830R 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. Future Streamlined data; see DLMS introductory note 4c. 2. 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. 3/3
  842P LQ01 PCD Detailed Cause Code 1. Fourth- Sixth Positions of the PQDR Summary Code. AKA Detailed Cause Code. 2. Definition: Refer to DLAR 4155.24 or Refer to Reference (g) detailed cause of deficiency. 3. Approved for use in X12 version 8060.
  856P BSN01 01 Cancellation Use to indicates the reversal, cancellation, or voiding of a prior submission or status 1. For WAWF, use to indicate a “Void Only” submission. 2. Restricted use during DCMA pilot. Applicable to source inspection and acceptance, DCMA administered and MOCAS paid, where documents have been signed in WAWF by the inspector. 2/30
  856P BSN01 05 Replace Use to indicate a "Void and Create" to void a previously submitted advanced shipping notice (ASN)/Receiving Report (RR) and concurrently create a new one 1. For WAWF, use to indicate a “Void and Create” to void a previously submitted ASN/Receiving Report (RR) and concurrently create a new one. 2. Restricted use during DCMA pilot. Applicable to source inspection and acceptance, DCMA administered and MOCAS paid, where documents have been signed in WAWF by the inspector. 2/30
  856P HL03 G Quality Characteristics 1. For WAWF, use to identify the supply condition code associated with the human readable serial number or UII. This loop can be a child loop to the I Item loop (individual line item), or the D UID Loop. 2. The following detail segments and elements are applicable to the G loop, 2/REF/150 and 2/LM/340, 2/LQ/350.
  856P REF01 SE Serial Number A value assigned for identification of an item 1. For WAWF, use to identify the human readable serial number in the Quality Characteristics loop (HL03=G) and the HL03=P). Enter the actual serial number in REF02. 2. For the Pack loop, use the Mark Indicator “W9” in REF04-01 and enter “Yes” in REF04-02 for item serial number that is packed across multiple boxes; there must be one, and only one, mark indicator per item. 1/50
  856P 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 1. For WAWF, use in the IUID Loop (2/HL/010, HL03 = D) to identify the supply condition code (SCC) associated with serial number or UII in 2/REF/150. Provide the SCC value in 2/LQ02/350. Only provide one SCC per serial number or UII. 2. For WAWF, use in the Item loop (2/HL/010, HL03 = I) to identify the SCC associated with all items. 3. The Distribution Standard System (DSS) does not use SCC in the DLMS 856P ASN; therefore, DSS may drop the SCC upon processing. 1/1
  536L N901 9H Packaging Group Number Use to identify the Package Sequence Number 1. For use with the Item, Order, Quantity, and Contract loops to identify the MILSTRAP Package Sequence Number. 2. Future streamlined data; see introductory DLMS note 4c. 1/30
  527R N901 OR Order/Paragraph Number Use to identify the legacy four-position call/order number associated with the PIIN 1. For use with CAV receipt, to identify the legacy 4-position call/order number associated with a PIIN. Authorized DLMS migration enhancement for CAV use. See DLMS introductory note 5g. 2. Do not use for the PIID call/order number. Refer to ADC 1161. 4/4
  527R N901 55 Sequence Number A unique identifier assigned to an item, task, or process to denote its specific order or position within a larger sequence 1. For USAMMA Medical use in ARI/receipt transactions to identify the sort sequence number. 2. DLMS Component-unique enhancement. See introductory DLMS note 5e. 1/30
  527R N101 WZ Final Maintenance Organization Use to communicate that the customer/site does not expect additional receipts 1. For USAMMA Medical use in ARI/Receipt transactions to identify the assembly/maintenance organization for medical/surgical component assembly. This organization will complete kit assemblies and ship to final destination activity. 2. DLMS Component-unique enhancement. See introductory DLMS note 5e. 1/60
  856S 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 1. For turn-ins to a DLA Disposition Services Field Office, the supply condition code is mandatory. DLMS enhancement, see ADC 422 and 1399. 2. For all other shipments, this is an authorized DLMS enhancement; see introductory DLMS note 2f. 1/1
  842AW 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. For SQCR, use to identify a Requisition Alert Document Number to protect materiel for use by authorized local users at industrial work sites. 2. For SQCR, Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 15/15
  856S N101 Z1 Party to Receive Status 1. For shipment status forwarded for DAAS distribution to status recipients under MILSTRIP/DLMS distribution rules (AS8), the recipients will be identified on the DAAS-generated transactions and will not appear on the original transaction. 2. As a DLMS enhancement, may be used to identify recipients other than the prescribed status recipients under DLMS/MILSTRIP distribution rules. Use multiple iterations of the 2/N1/2200 loop to identify shipment recipients, as needed. Use with N106=TO to indicate that the value in N104 is receiving the transaction. See introductory DLMS note 2a. 3. Use to provide shipment status to Product Data Reporting and Evaluation Program-Automated Information System (PDREP-AIS) for PQDR exhibit tracking when the PQDR RCN is included. For use with DoDAAC N45112. Refer to ADC 1007. 1/60
  870S LQ01 67 Type of Assistance Code Use when the coded address in the transaction number does not identify the type of assistance and financing 1. For Security Assistance (SA) transactions, 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 3a. 1/30
Page 100  of  195 First   Previous   96  97  98  99  [100]  101  102  103  104  105  Next   Last