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 ICSorted by ascending REF CODE X12 CODE NAME GENERAL CODE DEFINITION CODE DLMS NOTE DLMS MIN MAX
  870M BSR11 ZZ Mutually Defined Use to where there is no suitable X12 code in the data element. 1. Use to identify the Unit of Use Indicator. When included, the quantity, price, and unit of measure values associated with this transaction are applicable to the unit of use. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. N/A
  870M N101 GP Gateway Provider Use to identify the Routing Identifier of the Defense Automatic Addressing System (DAAS) as the intended recipient for distribution or posting to the historical record Use to identify the Defense Automatic Addressing Systems (DAAS) providing customer excess report informative status. Also use to identify DAASC providing rerouting, rejection, or modification status. 3/3
  870M N101 RL Reporting Location Use to indicate the reporting organization when providing status on open materiel returns reports Use with BSR01 code 3 to indicate the reporting organization when providing status on open materiel returns reports. N/A
  870M N101 Z4 Owning Inventory Control Point Use to indicate the source of supply Use to identify the ICP/IMM. 1/60
  870M N101 ZQ Screening Point Use to identify the Department of Defense Activity Address Code (DoDAAC) of the current Screening Point activity Use to identify the Defense Program for the Redistribution of Assets (DEPRA). (Use code J2 Authorized Entity in future versions of this IC.) 6/6
  870M N101 ZS Monitoring Party Use to identify the International Logistics Control Office (ILCO) Use to identify the International Logistics Control Office (ILCO) providing status. 1/60
  870M N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations DLMS enhancement; see introductory DLMS note 4a. 6/6
  870M 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) Use with code RL to indicate the Security Assistance (SA) structured address data. Interpretation of this data may require additional codes cited elsewhere in the transaction. 6/6
  870M 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 3/3
  870M N104 N/A
  870M N106 FR Message From Use to identify the party originating the transaction set Must use with the appropriate 1/N101/050 code to indicate that the organization cited in N104 is originating the transaction set. 1/60
  870M HL01 N/A
  870M HL03 W Transaction Reference Number Use to identify the individual transaction status loops. N/A
  870M REF01 86 Operation Number Use to identify a discrete, sequenced task or step within a larger Job Order (JO) that must be completed to achieve a specific mission objective 1. Use to identify the Key Operation (KO) Number associated with the JO. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 1/30
  870M REF01 9R Job Order Number Use to identify Job Order (JO) Number Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 1/50
  870M REF01 CO Customer Order Number Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 1. Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381 (or as applicable). 5/5
  870M 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 Must use to identify the materiel returns transaction number. 14/14
  870M 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. Use to identify a Requisition Alert Document Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 15/15
  870M REF02 N/A
  870M REF03 N/A
  870M REF04 N/A
  870M REF04-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
  870M REF04-02 N/A
  870M N101 77 Service Location Use for materiel availability reports and automatic shipment notifications to identify the party to receive packing, crating , and handling credit when different from the party to receive credit for materiel Use for materiel availability reports and automatic shipment notifications to identify the party to receive packing, crating , and handling credit when different from the party to receive credit for materiel. Data maintenance action to add qualifier CRP for this purpose has been approved for version 4020. 1/60
  870M N101 KK Registering Party Use to identify the Component UIT registry 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 also be sent to a UIT registry for information purposes. Must be used with 2/N106/90 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. 2. DLMS enhancement. See introductory DLMS note 4a. 1/60
  870M N101 N1 Notify Party no. 1 The 10-digit NDC will be in one of the following configurations: 4-4-2, 5-3-2, or 5-4-1, meaning that there are 4 or 5 digits for the labeler code, 4 or 3 digits for the product code and 2 or 1 digit(s) for the package code Use to identify the organization to receive packing, crating, and handling credit. Data Maintenance action has been initiated to obtain an appropriate qualifier. 10/10
  870M N101 N2 Notify Party no. 2 Use to identify the organization to receive transportation credit. Data Maintenance action has been initiated to obtain an appropriate qualifier. N/A
  870M N101 RL Reporting Location Use to indicate the reporting organization when providing status on open materiel returns reports Use to indicate the reporting organization when providing status on open materiel returns reports. N/A
  870M N101 ST Ship To Used to identify a organization to which material is shipped as identified in the requisition or other initiating transaction ICPs/IMMs use to identify the receiving depot to which the reported materiel is to be shipped. 1/60
  870M N101 Z1 Party to Receive Status The entity to receive status for the designated document number Use multiple iterations to identify all additional status recipients, as required. 1/60
  870M N101 Z4 Owning Inventory Control Point Use to indicate the source of supply 1. Use to identify the ICP/IMM. 2. Authorized DLMS enhancement for Army use to identify the Inventory Control Point that the transaction is to be routed to when acting as an Exchange Pricing Delta Bill Trigger (used in conjunction with LQ01/330 = SEC (Stock Exchange Code). 1/60
  870M N101 Z8 Last Known Source of Supply Use to identify the supply source Use to identify the ICP/IMM to receive all future transactions. 1/60
  870M N101 ZB Party to Receive Credit Use to identify the Business Partner Number (BPN) of the party to receive credit Use to identify the organization to receive materiel credit. 1/60
  870M N101 ZS Monitoring Party Use to identify the International Logistics Control Office (ILCO) Use to identify the ILCO. 1/60
  870M N101 ZZ Mutually Defined Use to where there is no suitable X12 code in the data element. Use for materiel availability reports and automatic shipment notifications to identify the party to receive transportation credit when different from the party to receive credit for materiel. An ANSI data maintenance was approved in version 5010. The approved code/name is �AEJ - Party to Receive Transportation Credit". N/A
  870M N103 10 Department of Defense Activity Address Code (DODAAC) Use to identify specific units, activities, and/or organizations DLMS enhancement; see introductory DLMS note 4a. 6/6
  870M 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) Use to indicate the SA structured address data. Interpretation of this data may require additional codes cited elsewhere in the transaction. 6/6
  870M 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 3/3
  870M N103 UR Uniform Resource Locator (URL) Use when appropriate to identify the Component Unique Item Tracking (UIT) registry 1. Use when appropriate to identify the Component UIT registry. 2. DLMS enhancement; see introductory DLMS note 4.a. 2/80
  870M N104 N/A
  870M N106 PK Party to Receive Copy An organization to be provided an informational copy of a transaction 1. Use when appropriate to send an information copy of the transaction to a Component UIT registry. For use with N101 code KK. 2. DLMS enhancement. See introductory DLMS note 4a. 1/60
  870M N106 TO Message To Use to identify the party to receive the transaction set Use in conjunction with the appropriate 2/N101/090 code to indicate the organization cited in N104 is to receive the transaction. 1/60
  870M 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. N/A
  870M LQ01 0 Document Identification Code Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data 3/3
  870M LQ01 67 Type of Assistance Code Use when the coded address in the transaction number does not identify the type of assistance and financing For Security Assistance (SA) transactions, use when the coded address in the transaction number does not identify the type of assistance. 1/30
  870M LQ01 78 Project Code Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes ICPs/IMMs use to identify the project code assigned when shipment of the reported materiel is directed. 3/3
  870M 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) Recommend using in all requisitions. 2/2
  870M LQ01 85 Country and Activity Code Use to identify country, international organization, region, or program authority associated with transactions recorded in Security Cooperation systems and associated programs implemented in the Foreign Military Sales. For SA, use when the coded address in the transaction number does not identify the country or activity. 1/30
  870M LQ01 87 Subsistence Type of Pack Code Use to indicate the degree of protection to be provided subsistence items ICPs/IMMs and reporting organizations use to identify the type of pack associated with the reported subsistence items. 1/1
  870M LQ01 89 Cooperative Logistics Program Support Code Provides information as to whether or not supply support on a Cooperative Logistics Supply Support Arrangement (CLSSA) requisition or passing order should be made on a programmed or un-programmed basis For SA, use as applicable. 1/1
Page 151  of  190 First   Previous   147  148  149  150  [151]  152  153  154  155  156  Next   Last