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 NAMESorted by descending GENERAL CODE DEFINITION CODE DLMS NOTE DLMS MIN MAX
  842SR REF01 8V Credit Reference Use to provide the original billed document number when requesting credit for non-manager owned suspended stock 1. Use with Reply Code 524 to provide the original billed document number when requesting credit for non-manager owned suspended stock. Use multiple repetitions as needed. 2. If the original billed document number is not available, a constructed document number must be provided. Refer to ADC 1084. 1/50
  940R W0506 CC Credit Commission Invoice Use this code to indicate Cargo Release Cancellation to submit a request for cancellation of a previously submitted cargo release order. This is a borrowed code. This is not a balance affecting transaction type. There is no legacy MILS equivalent.
  842AW REF04-01 PSM Credit Card Identifies when a deferred payment is made to a financial account upon which deferred payment is accepted Only send this value when citing the requisition number (using Transaction Reference Number, Code TN) and enter a "Y" indicator in REF04-02 to indicate payment by either Government purchase card or commercial credit card. Do not use for FedMall requisitions (See code URL) and do not provide “N” indication. Refer to ADC 1467. 1/1
  842P REF01 PSM Credit Card Identifies when a deferred payment is made to a financial account upon which deferred payment is accepted 1. Use to indicate payment by either Government purchase card or commercial credit card. Cite Y in REF02 when applicable. 2. This field may only be populated by the Originating Point or Screening Point. For inter-service transactions, only the Screening Point can update this element. 1/1
  812L DTM01 188 Credit Advice Use to identify the date credit was issued Use to identify the credit date. 8/8
  812R DTM01 188 Credit Advice Use to identify the date credit was issued 1. Use to indicate the credit date. 2. DLMS enhancement; see introductory DLMS note 5a. 8/8
  842P DTM01 188 Credit Advice Use to identify the date credit was issued 1. Use to identify the date credit was issued, Credit Date. 2. Use in the Document Number Loop (HL01=W). 3. If multiple document numbers are applicable, identify the credit date applicable to the document number included in the Report Loop (HL01=RP) and use a separate Document Number Loop (HL01=W) for each additional document number and credit date combination. 4. When providing a credit date, also provide the credit value (AMT01=PD) (and the DLA Credit Memo Number, when applicable) in the same loop. 5. This element may only be populated/updated by the Action Point. 8/8
  842AW AMT03 E Credit (Estimated) 1. Use to indicate that the dollar amount provided represents an estimated cost. 2. Approved for use in X12 version 7050.
  842AW AMT03 A Credit (Actual) 1. Use to indicate that the dollar amount provided represents the actual cost. 2. Approved for use in X12 version 7050.
  567C AMT03 C Credit Use to indicate the amount cited in AMT02 is an over payment to the contractor.
  812L BCD05 C Credit Use when credits or refunds are sought Use when credits or refunds are sought. Also, when adjustments are not involved e.g., request for copies. 1/1
  812R BCD05 C Credit Use when credits or refunds are sought DLMS enhancement; see introductory DLMS note 5a. 1/1
  812R CDD02 C Credit Use when credits or refunds are sought DLMS enhancement; see introductory DLMS note 5a. 1/1
  842P AMT01 PD Credit Use to indicate the amount of credit/debit being authorized or recommended (also known as DLA Credit Value) 1. Use to indicate the amount of credit/debit being authorized or recommended (also known as DLA Credit Value). 2. Use in the Document Number Loop (HL01=W). 3. If multiple document numbers are applicable, identify the credit amount applicable to the document number included in the Report Loop (HL01=RP) and use a separate Document Number Loop (HL01=W) for each additional document number and credit amount combination. 4. When providing a credit amount, also provide the credit date (DTM01=188) (and the DLA Credit Memo Number, when applicable) in the same loop. 5. This element may only be populated/updated by the Action Point. 1/18
  870M SAC02 B800 Credit Use to indicate expected credit 1. Use to indicate expected credit. 2. For intra-Army use, this will be the credit granted. 1/15
  650A BGN08 17 Create For Medical use in transaction for initial transmission of a request for assembly maintenance action.
  842AR LQ01 D Court Document Type Code Use to identify the Type Document Code 1. Must use to identify the Discrepancy Report Document Type Code to identify the type of discrepancy report and type of shipment involved. This data element is required for the DoD WebSDR interface. 2. Valid entries are for SDR types are: • 5 - Storage Quality Control Report • 6 - Customer originated, direct vendor/contractor delivery. This type is used primarily for shipment of requisitioned materiel sourced by the item manager by contracted vendor shipment rather than from stock. • 7 - Customer originated, depot/lateral shipment/other. This type is used primarily for shipment of requisitioned materiel sourced by the item manager from stock; may be used for other customer SDRs. • V - Customer originated, lateral shipment under TAV. This type is used exclusively for customer reported discrepancies resulting from item manager directed lateral redistribution (initiated via MILSTRIP DIC Code A4_ with Distribution Code 2 or 3). • 8 - Depot originated, depot receipt from non-procurement source other than RDO. • A - Storage site receipt, customer return/other (Note: Comparable to Type 8, but originated outside DSS; requires authorization prior to use.) • 9 - Depot originated procurement source receipt • D - DLA Distribution Field Office originated (Note: Used in conjunction with Disposition Services SDR Type Code to further distinguish the type of shipment scenario involved.) • P - Storage site receipt procurement source receipt (Note: Comparable to Type 9, but originated outside DSS; requires authorization prior to use.) • R - Depot originated, redistribution order receipt • N - Storage site receipt, depot shipment (RDO) (Note: Comparable to Type R, but originated outside DSS; requires authorization prior to use. • W - Transshipper originated SDR. This type is used by ports and CCPs for discrepancies discovered while materiel is intransit. Because this type of SDR may apply to a shipment unit (rather than a single document number), data element requirements differ significantly from other SDR types. 3. For future consideration, a data maintenance action was approved in version 5030. The approved code/name is "TDC - Discrepancy Report Type Code". 1/1
  842AW LQ01 D Court Document Type Code Use to identify the Type Document Code 1. Must use to identify the Discrepancy Report Document Type Code to identify the type of discrepancy report and type of shipment involved. This data element is required for the DoD WebSDR interface. 2. Valid entries are for SDR types are: • 5 - Storage Quality Control Report (SQCR) • 6 - Customer originated, direct vendor/contractor delivery. This type is used primarily for shipment of requisitioned materiel sourced by the item manger by contracted vendor shipment rather than from stock. • 7 - Customer o riginated, depot/lateral shipment/other. This type is used primarily for shipment of requisitioned materiel sourced by the item manager from stock; may be used for other customer SDRs. • V - Customer originated, lateral shipment under TAV. This type is used exclusively for customer reported discrepancies resulting from item manager directed lateral redistribution (initiated via MILSTRIP DIC Code A4_ with Distribution Code 2 or 3). • 8 - Depot originated, depot receipt from non-procurement source other than RDO. • A - Storage site receipt, customer return/other (Note: Comparable to Type 8, but originated outside DSS; requires authorization prior to use.) • 9 - Depot originated procurement source receipt • D - DLA Distribution Field Office originated (Note: Used in conjunction with Disposition Services SDR Type Code to further distinguish the type of shipment scenario involved.) • P - Storage site receipt procurement source receipt (Note: Comparable to Type 9, but originated outside DSS; requires authorization prior to use.) • R - Depot originated, redistribution order receipt. • N - Storage site receipt, depot shipment (RDO) (Note: Comparable to Type R, but originated outside DSS; requires authorization prior to use. • W - Transshipper originated SDR. This type is used exclusively by ports and CCPs for discrepancies discovered while materiel is in transit. Because this type of SDR may apply to a shipment unit (rather than a single document number), data element requirements differ significantly from other SDR ty pes. 3. For future consideration, a data maintenance action was approved in version 5030. The approved code/name is "TDC - Discrepancy Report Type Code". 1/1
  842CI LQ01 D Court Document Type Code Use to identify the Type Document Code 1. Must use to identify the Type Document Code. 2. Type Document Code S is the only valid entry in LQ02 for this transaction. 1/1
  842CR LQ01 D Court Document Type Code Use to identify the Type Document Code 1. Must use to identify the Type Document Code. 2. Type Document Code S is the only valid entry in LQ02 for this transaction. 1/1
  842SQ LQ01 D Court Document Type Code Use to identify the Type Document Code 1. Use to identify the Type Document Code. This is a DLA unique data element. Code list is available in DLAH 4140.4, CDCS Handbook. 2. For SQCR indicate Document Type 5. 3. A data maintenance action was approved in version 5030. The approved code/name is "TDC - Discrepancy Report Type Code". 1/1
  842SR LQ01 D Court Document Type Code Use to identify the Type Document Code 1. Use to identify the Type Document Code. The SQCR process is identified by Document Type 5. 2. A data maintenance action was approved in version 5030. The approved code/name is "TDC - Discrepancy Report Type Code". 1/1
  846C MEA01 CT Counts Use with Commercial Venture processing to indicate that Consecutive Delivery Order Count and Maximum Delivery Order Number information is provided.
  856S MEA01 CT Counts Use in the HL03 code W loop to identify the number of containers. Enter the quantity in the MEA03.
  856P LIN02 CH Country of Origin Code An alphabetic code that represents a country 1/48
  870N N103 38 Country Code The geopolitical entities, names, and codes (GENC) standard. The GENC standard is the US Government profile of ISO 3166 (parts 1 and 2) names and code elements, with modifications only where necessary to comply with US law and US Government recognition policy Use with N101 Qualifier CY to identify the Security Cooperation Customer Code applicable to the NOA reply. (Must be consistent with the NOA and original requisition content). 2/3
  810L 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. Use to identify the country. Pending transition to the new country code standard (refer to ADC 448B for future implementation). 1/30
  842AW 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. Use to identify the Security Cooperation Customer Code. 1/30
  856N 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. Use to identify the Security Cooperation Customer Code. Refer to ADC 1075. 1/30
  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
  870S 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. 1. Use to identify the Security Cooperation Customer Code. 2. DLMS enhancement; see introductory DLMS note 3a. 1/30
  945A 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. 1. Use with N901 code 4C to indicate the country code for the carrier address when outside the U.S. 2. DLMS enhancement; see introductory DLMS note 4a. 1/30
  856N N101 CY Country Use to identify the Security Cooperation Customer Code associated with the Notice of Availability (NOA) reply Use to identify the designated CR to receive the transaction set. 2/60
  870N N101 CY Country Use to identify the Security Cooperation Customer Code associated with the Notice of Availability (NOA) reply 1. Use to identify the SC Customer Code associated with the NOA reply. 2. Use to identify the CR originating the transaction set. Authorized DLMS enhancement; see DLMS Introductory Note 3e. Refer to ADC 1098. 2/60
  856S REF01 91 Cost Element 1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 2f.
  180M FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 2f. 1/15
  511M FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 3g. 1/15
  511R FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 3f. 1/15
  517M FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 3f. 1/15
  810L FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 6e. 1/15
  842SR FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Implementation deferred; refer to ADC 1084. 1/15
  867I FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 5e. 1/15
  869F FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 4g. 1/15
  940R FA201 H1 Cost Code Use to identify the classification of an organization's revenues, expenses or consumable resources 1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Cost Element Code”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 4f. 1/15
  180M FA201 CC Cost Center Identifier Used to track and accumulate costs associated with a specific organizational unit or project, and is typically included on documents like contracts, inventory requisitions, and labor distribution forms 1. For DoD SLOA/Accounting Classification. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 2f. 3. Approved for use in X12 version 7020. 1/16
  511M FA201 CC Cost Center Identifier Used to track and accumulate costs associated with a specific organizational unit or project, and is typically included on documents like contracts, inventory requisitions, and labor distribution forms 1. For DoD SLOA/Accounting Classification use to identify, or to modify, “Cost Center Identifier”. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 3g. 3. Approved for use in X12 version 7020. 1/16
  511R FA201 CC Cost Center Identifier Used to track and accumulate costs associated with a specific organizational unit or project, and is typically included on documents like contracts, inventory requisitions, and labor distribution forms 1. For DoD SLOA/Accounting Classification. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 3f. 3. Approved for use in X12 version 7020. 1/16
  517M FA201 CC Cost Center Identifier Used to track and accumulate costs associated with a specific organizational unit or project, and is typically included on documents like contracts, inventory requisitions, and labor distribution forms 1. For DoD SLOA/Accounting Classification.Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 3f. 3. Approved for use in X12 version 7020. 1/16
  810L FA201 CC Cost Center Identifier Used to track and accumulate costs associated with a specific organizational unit or project, and is typically included on documents like contracts, inventory requisitions, and labor distribution forms 1. For DoD SLOA/Accounting Classification. Refer to ADC 1043. 2. Authorized DLMS enhancement; see introductory DLMS note 6e. 3. Approved for use in X12 version 7020. 1/16
  842SR FA201 CC Cost Center Identifier Used to track and accumulate costs associated with a specific organizational unit or project, and is typically included on documents like contracts, inventory requisitions, and labor distribution forms 1. For DoD SLOA/Accounting Classification. Implementation deferred; refer to ADC 1084. 2. Approved for use in X12 version 7020. 1/16
Page 123  of  195 First   Previous   119  120  121  122  [123]  124  125  126  127  128  Next   Last