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
  856S N101 PW Pick Up Address Use when the HL03 code V loop to identify the Pickup DODAAC.
  856S N101 RN Repair or Refurbish Location 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 34.
  856S N101 SB Storage Area 1. Use to identify the initial shipping activity. 2. For Army Total Package Fielding (TPF), use to identify the Routing Identifier of the Unit Materiel Fielding Point (UMFP) or staging site originating the UMFP shipment document. 3. Use for LRO shipment status to identify the organization responsible for release of the retail assets. 4. For conversion processing this will be understood to be the originating activity as identified by the Supplemental Address. 5. A DLMS enhancement allows specific separate identification of the party to receive credit and the party originating the LRO shipment status/shipping the materiel. DoDACs associated with qualifier SB and ZB are expected to be the same at this time. However, when using originated in DLMS, the LRO originator may be a different party and will be identified by a Routing Identifier. Refer to ADC 29. 6. When implemented as a DLMS enhancement in the shipment loop to allow specific separate identification of owner/manager and storage activity RIC for ammunition and ammunition related transactions, a second instance of the SB in the shipment loop must be used to identify the storage activity by DODAAC (N103 = 10). Refer to Approved Addendum to ADC 41A.
  856S N101 ST Ship To 1. Use to identify the organization to receive the materiel. 2. For shipment status in response to LROs (DIC AS6), use to identify the ship to activity as directed in the LRO. Authorized DLMS enhancement. See ADC 1030. 3. Use for HL03 code V loop for disposal shipments use to identify the Disposition Services Field Office. For HHMM/HW shipments provide the RIC.
  856S 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.
  856S N101 Z1 Party to Receive Status 1. For shipment status forwarded for DAS distribution to status recipients under MILSTRIP/DLMS distribution rules (AS8), the recipients will be identified on the DAS-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/20 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 N4512. Refer to ADC 107.
  856S N101 Z4 Owning Inventory Control Point 1. Use to identify the Routing Identifier of the supply source or applicable owner/manager as the originator of the shipment status. This includes shipment status prepared by the Distribution Depot on behalf of the owner/manager, for owner/manager directed shipments, and CP/Consolidation shipment status. Additionally, this includes shipment status prepared by Army storage activities on behalf of the owner/manager for ammunition and ammunition related shipments. 2. Use to identify the recipient for LRO Shipment Status. 3. Use to identify the recipient Fielding Command for Army Total Package Fielding shipments.
  856S N101 Z5 Management Control Activity Use for submission of all GFM requisitions.
  856S N101 Z7 Mark-for Party 1. Use to identify 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 2f. Refer to ADC 109A.
  856S N101 ZB Party to Receive Credit 1. Use to identify the party to receive credit for materiel, transportation, and PC&H. 2. For conversion processing this will be the activity as identified by the Supplemental Address and the same activity identified to release the materiel. 3. A DLMS enhancement allows specific separate identification of the party to receive credit and the party originating the LRO shipment status/shipping the materiel. Refer to ADC 29. 4. Use for SFIS compliant systems to identify the BPN of the party to receive credit. 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. 5. Authorized DLMS enhancement; see introductory DLMS note 2f.
  856S N103 2 Standard Carrier Alpha Code (SCAC) Use as needed to identify the commercial carrier.
  856S N103 8 UC/EAN Global Product Identification Prefix Corresponds to IAC '0-9'.
  856S N103 10 Department of Defense Activity Address Code (DODAAC) 1. Use as needed to identify the organizations listed to include: ship-to, bill-to, and shipping activity. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S N103 33 Commercial and Government Entity (CAGE)
  856S N103 50 Business License Number 1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the seller’s BPN in N104. 2. Authorized DLMS enhancement; see introductory DLMS note 2f.
  856S 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.
  856S N103 A2 Military Assistance Program Address Code (MAPAC) 1. Use to indicate the SA structured address data. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S N103 M4 Department of Defense Routing Identifier Code (RIC)
  856S N103 UR Uniform Resource Locator (URL) 1. Use when appropriate to identify the Component UIT registry. 2. DLMS enhancement; see introductory DLMS note 2.a.
  856S N106 FR Message From 1. Must use with the appropriate 2/N101/20 code to indicate the organization cited in N104 is sending the transaction set. 2. For LRO shipment status, use with 2/N1/20 code SB, otherwise use with code Z4 (or GP when originator not known) to indicate the organization cited in N104 is originating the transaction.
  856S N106 PK Party to Receive Copy 1. Use when appropriate to send an information copy of the transaction to a Component UIT registry. For use with N101 code K. 2. DLMS enhancement. See introductory DLMS note 2.a.
  856S N106 TO Message To 1. Use with the appropriate 2/N101/20 code to indicate the organization cited in N101 is receiving the transaction set. 2. Use with 2/N1/20 code GP (for DASC) or Z1 to indicate the organization cited in N104 is receiving the transaction.
  856S SAC01 C Charge
  856S SAC03 DL Defense Logistics Agency
  856S GF01 C7 Contract Line Item Number Use as directed to associate a Contract Line Item Number with the Contract Number.
  856S LM01 DF Department of Defense (DoD)
  856S LQ01 0 Document Identification Code 1. The legacy 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. Navy unique Document Identifier POS is authorized for CAV shipment status. 3. Future streamlined data; see introductory DLMS note 2c.
  856S LQ01 36 Air Terminal Identifier Code 1. Use to identify port of embarkation (POE) air terminal identifier codes for Outside Continental United States (OCONUS) shipments made via Defense Transportation System (DTS) air modes. 2. Authorized DLMS migration enhancement; see introductory DLMS 2f. 3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, Shipment Status, will carry this information in REF01, qualifier T, Terminal Code, due to the translator's inability to distinguish among code types.
  856S LQ01 37 Water Terminal Identifier Code 1. Use to identify port of embarkation (POE) water terminal identifier codes for OCONUS shipments made via DTS water modes. 2. Authorized DLMS migration enhancement; see introductory DLMS 2f. 3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, Shipment Status, will carry this information in REF01, qualifier T, Terminal Code, due to the translator's inability to distinguish among code types.
  856S LQ01 38 Consolidation and Containerization Point Code 1. Used to identify the SEAVAN CP code for OCONUS shipments made via DTS. 2. Authorized DLMS migration enhancement; see introductory DLMS 2f. 3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, Shipment Status, will carry this information in REF01, qualifier T, Terminal Code, due to the translator's inability to distinguish among code types.
  856S LQ01 58 Transportation Bill Code Use for FMS shipments, to identify the applicable shipment Transportation Bill Code (TBC).
  856S LQ01 67 Type of Assistance Code 1. For Security Assistance (SA) transactions, use only when the coded address in the transaction number does not identify the type of assistance and financing. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 78 Project Code 1. Must use to provide the project code when applicable. 2. Required when applicable to communicate the project code associated with the Army Total Package Fielding Unit Materiel Fielding Point or staging site shipment document. 3. For DoD SLOA/Accounting Classification compliance (2/HL/010 Finance loop) the Project Code may be repeated as a Project Identifier (REF01 Qualifier JB). Refer to ADC 1043. 4. Authorized DLMS migration enhancement; see introductory DLMS 2f.
  856S LQ01 79 Priority Designator Code 1. Must use to identify the applicable priority designator. 2. Authorized DLMS migration enhancement; see introductory DLMS 2f.
  856S LQ01 81 Status Code 1. Use to identify additional status information related to the shipment unit. 2. For shipment status other than those resulting from conversion from the legacy MILSTRIP ASY this is a DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 83 Supply Condition Code 1. For turn-ins to a DLA Disposition Services Field Office, the supply condition code is mandatory. DLMS enhancement, see ADC 42 and 139. 2. For all other shipments, this is an authorized DLMS enhancement; see introductory DLMS note 2f.
  856S LQ01 84 Management Code 1. Use to communicate the management code associated with Army Total Package Fielding Unit Materiel Fielding Point or staging site shipment document. 2. DLMS Component-unique enhancement. See introductory DLMS note 5e.
  856S LQ01 88 Disposal Authority Code For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter the disposal authority code to indicate that the designated materiel is authorized for shipment to a DLA Disposition Service Field Office per the Generator Communication (GenCom) Standard. DLMS enhancement, see ADC 42.
  856S LQ01 89 Cooperative Logistics Program Support Code 1. For FMS transactions, must use to identify programed, nonprogrammed, and termination/drawdown requirements. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 92 Reason for Disposal Code 1. Use for materiel transferred to a Defense Reutilization and Marketing Service (DRMS) to identify the reason for transfer of the shipment unit. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 93 Type of Storage Code 1. Use to identify the minimum level of storage environment required for shipment unit. 2. DLA Disposition Services uses three to five position alphanumeric code to identify building number of the pickup DODAAC. Use LQ02 to identify the Storage Building Number. Refer to ADC 1428. 3. DLMS enhancement; see introductory DLMS Note 2a.
  856S LQ01 94 Identification Code Use in FMS transactions to identify the customer country's requisitioning Service Code 1. 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 has been submitted to create a new qualifier for this data element. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 95 Offer and Release Option Code 1. For FMS transactions, must use to advise the supply source of the type of notice required prior to shipping the materiel. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S 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.
  856S LQ01 A2 Customer Within Country Code 1. For SA transactions, use only when the coded address in the transaction number does not identify the customer-within-country. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 A3 Delivery Term Code 1. For FMS transactions, use only when the coded address in the transaction number does not identify the delivery term. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 A5 Subcase Number 1. Use in FMS transactions based on Service requirements. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 A6 Freight Forwarder Number 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.
  856S LQ01 A7 Record Control Number 1. Must use in MAP/GA transactions to identify the program line item number. 2. DLMS enhancement; see introductory DLMS note 2a.
  856S LQ01 A8 Program Year Code 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.
Page 92  of  141 First   Previous   88  89  90  91  [92]  93  94  95  96  97  Next   Last